Overview of Outbound E-Document Process

From a user’s perspective, the following steps describe the end-to-end process of generating XML or JSON e-documents from NetSuite transaction records and then sending the e-documents:

  1. Assign an e-document package to a customer or vendor by performing the following steps:

    1. Create or edit a customer or vendor record. If you are using an e-document sending method with an email channel, be sure to create or add the email recipients of the e-document. Then, on the E-Document Email Recipient subtab under the E-Document subtab, select contacts. You can select only contacts associated with the customer or vendor. Contacts must have valid email addresses. See Defining E-Document Email Recipients.

      • If the customer or vendor is a company, create one or more contact records.

      • If the customer or vendor is an individual, add a valid email address on the record.

    2. On the E-Document subtab, in the E-Document Packages field, select the e-document package to use for the customer’s or vendor’s transaction records.

      Note:

      The outbound template and sending method included in the e-document package you will select must have subsidiaries belonging to this customer or vendor. For more information, see Multi-subsidiary Support in the Outbound Process.

  2. Create or edit a transaction record. Select an e-document template and an e-document sending method. For more information, see Transactions and Processes Supported by the Electronic Invoicing SuiteApp and Selecting E-Document Packages, Templates and Sending Methods on Transactions.

    If the e-document to be generated must be sent to a certification authority for certification, make sure that a certification sending method is assigned to the transaction and subsidiary. For more information, see E-Document Certification in the Outbound Process.

  3. Generate an e-document for the transaction record. You can generate e-documents individually or in bulk. For more information, see Generating and Regenerating E-Documents.

  4. Send the e-document. You can send e-documents individually or in bulk. For more information, see Sending and Resending E-Documents.

    Note:

    If a certification sending method is assigned to the transaction and subsidiary, the Certify E-Document button is displayed, which sends the e-document to the specified certification authority. Certified e-documents can be sent again to customers, vendors or a tax agency.

    Note:

    Electronic Invoicing SuiteApp provides support to send all the eligible e-documents for certification individually or in bulk to Avalara automatically. For more information about Avalara for e-Invoicing, see Avalara for E-Invoicing.

  5. If an administrator enables and configures the automatic e-document processing feature, you can process the e-document automatically by clicking the Process E-Document button. For more information, see Processing Multiple E-Document Processes Using Automatic E-Invoicing

To understand errors that can be encountered during the generation or sending of e-documents, read the following topics:

To understand the outbound electronic invoicing process flow and e-document status definitions, see the following topics:

Related Topics

Electronic Invoicing User Guide
Displaying the E-Documents Portlet on the Home Page
Outbound E-Document Statuses
Assigning E-Document Packages to Customer or Vendor Records
Defining E-Document Email Recipients
Selecting E-Document Packages, Templates and Sending Methods on Transactions
Enabling PDF File Reference Generation
Generating and Regenerating E-Documents
Sending and Resending E-Documents
E-Document Network Status
Overview of Inbound E-Document Processing
Inbound E-Document Statuses
Receiving Inbound E-Documents by Email Capture
Receiving E-Document XML Files from Web Service
Uploading Received XML Files as Inbound E-Documents
Converting Inbound E-Documents into Transaction Records
Common Scenarios in Vendor Bill Conversion
Converting Individual Inbound E-Documents into Vendor Bills
Converting Failed Inbound E-Documents
Compatibility of Approval Workflows with Vendor Bill Conversion
Canceling Inbound E-Documents

General Notices