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...

·3 min read·28 views·NetSuite 2026.2·View Oracle Docs

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 documentTransaction type
UBL invoiceVendor bill
UBL credit noteVendor 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:

FieldRequired value
StatusPending or Failed
Document TypeInvoiceDetailRequestUBL
Raw DocumentXML 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?
No. Electronic Invoicing SuiteApp 10.6.0 determines the transaction type from the inbound UBL XML, not the Document Subtype field. A UBL invoice converts to a vendor bill, while a UBL credit note converts to a vendor credit.
Which NSEB inbound documents does the converter process, and how often does it run?
The NSEB Inbound Converter MR runs every 15 minutes and picks up documents with a Pending or Failed status, a Document Type of InvoiceDetailRequestUBL, and XML content in the Raw Document field. Meeting these conditions makes a document eligible, but successful conversion also requires supported, valid XML and an appropriate template.
What happens if the inbound UBL XML is missing, malformed, or not a supported document type?
Conversion stops, 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 UBL credit note; check the XML when troubleshooting rather than changing Document Subtype.
Why can’t an inbound e-document template be selected, and what configuration is required?
The appropriate inbound e-document template must have an XSD file selected on its template record. The XSD lets the conversion process obtain the template details and automatically select the template in the inbound record’s E-Document Template field; without it, the document will not convert.

Weekly Update History (1)

Order Management SuiteAppsadded

Added an entry for Electronic Invoicing Version 10.6.0.

View Oracle Docs
Source: Electronic Invoicing Version 10.6.0 — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Order Management

View all Order Management articles →

Also from NetSuite 2026.2

View all NetSuite 2026.2 changes →