Electronic Invoicing 10.6.0: NSEB Type Detection
Electronic Invoicing 10.6.0 detects NSEB transaction types from UBL XML during conversion: invoices become vendor bills and credit notes become vendor...
Electronic Invoicing SuiteApp version 10.6.0 determines transaction types from inbound UBL XML when converting NSEB inbound documents to inbound e-documents. It no longer relies on Document Subtype. UBL invoices become vendor bills; UBL credit notes become vendor credits. Invalid or unsupported XML stops conversion, and template XSD requirements still apply.
What's New in NSEB Transaction Type Detection?
The conversion process determines the transaction type directly from the supported UBL document:
| Inbound XML document | Transaction type |
|---|---|
| UBL invoice | Vendor bill |
| UBL credit note | Vendor credit |
The Document Subtype field on the NSEB inbound document no longer determines the transaction type during conversion. For troubleshooting, inspect the XML rather than assuming that adjusting Document Subtype will change the conversion result.
Missing, empty, malformed, or unsupported XML stops conversion. The NSEB inbound document is not converted to an inbound e-document, and an error is returned. Supported input must be a UBL invoice or credit note.
Which Documents Are Eligible for Conversion?
The NSEB Inbound Converter MR automatically converts eligible NSEB inbound documents to inbound e-documents every 15 minutes. Documents are picked up when they meet these field conditions:
| Field | Required value |
|---|---|
| Status | Pending or Failed |
| Document Type | InvoiceDetailRequestUBL |
| Raw Document | XML content |
Eligibility and successful conversion are different checks. A document with an eligible status still needs valid, supported XML and an appropriate template. When investigating a failed conversion, verify these conditions separately rather than treating a Pending or Failed status as evidence that the document can convert successfully.
What Template Setup Is Required?
An appropriate inbound e-document template must have an XSD file selected in its template record. This allows the conversion process to obtain the template details and automatically select that template in the inbound record's E-Document Template field.
Without an XSD file on the template record, the E-Document Template cannot be selected and the inbound document will not convert. The Avalara Document ID field stores the inbound document's Avalara document ID.
How Can You Verify Conversion Results?
Inbound e-documents appear in the Electronic Documents portlet under Inbound E-Documents for Conversion. Click the displayed count to open Inbound E-Documents for Conversion: Results, which lists those documents.
On an inbound e-document record, review the E-Document Audit Trail subtab for the creation date, entity, event type, owner, and details. To validate the enhancement, test both supported XML types and confirm their transaction classification, template selection, and appearance in the conversion results.
Who This Affects
- Administrators: Verify inbound template XSD configuration and monitor conversion results.
- Integration developers: Validate supplied UBL XML rather than relying on Document Subtype.
- Accounts payable teams: Check vendor bill versus vendor credit classification in the inbound electronic invoicing workflow.
Key Takeaways
- SuiteApp version 10.6.0 detects transaction types from UBL XML rather than Document Subtype.
- UBL invoices map to vendor bills; UBL credit notes map to vendor credits.
- Eligible documents are processed every 15 minutes.
- Missing, empty, malformed, or unsupported XML prevents conversion, as does a missing template XSD.
Frequently Asked Questions (4)
Does the NSEB inbound document’s Document Subtype control whether conversion creates a vendor bill or vendor credit?
Which NSEB inbound documents does the converter process, and how often does it run?
What happens if the inbound UBL XML is missing, malformed, or not a supported document type?
Why can’t an inbound e-document template be selected, and what configuration is required?
Weekly Update History (1)
Added an entry for Electronic Invoicing Version 10.6.0.
View Oracle DocsWas this article helpful?
More in Order Management
- Vendor Credit Inbound Transaction Support in NetSuite 2023.2
NetSuite 2023.2 enhances order management with inbound vendor credit transaction support, streamlining processing.
- FedEx Ship API 2026.1 Upgrade: MFA Requirement in NetSuite
MFA is now required for registering FedEx Ship API in NetSuite 2026.1. Introduction Introduction Introduction Introduction
- FedEx Account Integration Re-Registration in NetSuite 2026.1
Re-register your FedEx account in NetSuite 2026.1 using MFA for secure shipping label creation without disruptions.
- Start Order Fulfillment from Sales Order Lists in NetSuite 2026.2
Start order fulfillment directly from sales order lists in NetSuite 2026.2, streamlining the process and reducing navigation steps.
Also from NetSuite 2026.2
- Bank Matching and Reconciliation Enhancements in NetSuite 2026.2
Bank matching and reconciliation pages in NetSuite 2026.2 receive critical UI enhancements for improved transaction management.
- System Notes Enhancement for Reconciliation in NetSuite 2026.2
System notes enhancement tracks GL transaction events in NetSuite 2026.2, improving reconciliation auditing and review.
- SuiteCloud CLI License Acceptance for Automation
Set SUITECLOUD_CLI_ACCEPT_LICENSE=true to suppress the SuiteCloud CLI license prompt during scripted npm installation.
- NetSuite Next: Readiness, Preview, and Ask Oracle
Eligible administrators can request a NetSuite Next preview, set up Ask Oracle, and prepare data, roles, customizations, and navigation.
Advertising
Reach Order Management Professionals
Put your product in front of NetSuite experts who work with Order Management every day.
Sponsor This Category