Understanding E-Documents and E-Document Packages
The following topics describe e-documents and e-document packages according to how they are used by NetSuite and the Electronic Invoicing SuiteApp.
E-Document
An e-document is a NetSuite transaction represented as an XML or JSON document generated according to a specified standard.
E-documents are transmitted to interested external parties, such as customers, vendors, or tax agencies. E-documents can be downloaded or shared through email, or transmitted through a web service or other custom method.
Some countries legally recognize these XML or JSON files as official documents, whereas other countries recognize the printed transactions as the officially accepted documents.
For information about currently supported transactions, see Electronic Invoicing Limitations and Best Practices.
E-Document Package
An e-document package defines a set of formats used for various transactions to ensure clear communication between all stakeholders of a specific business process, such as vendors communicating with customers, and vendors communicating with tax authorities.
For example, the PEPPOL e-document package defines all possible transactions between vendors and government agencies (sales orders, invoices, credit memos, return authorizations, and others).
An e-document package specifies the following:
-
the file format and template
-
the communication medium for transmitting the e-documents
-
the process necessary for ensuring authenticity and privacy of the information
An e-document package is usually defined by a tax authority or an industry governing body. Some e-document packages are defined by independent entities such as PEPPOL and ISO.
Related Topics
- Electronic Invoicing Administrator Guide
- Installing and Setting Up Electronic Invoicing
- Defining the E-Document Country for Free Use
- Advanced PDF/HTML Template
- Granting Access Permission to the E-Documents Portlet
- Creating E-Document Packages
- Multi-subsidiary Support in the Outbound Process
- Creating E-Document Templates
- Editing E-Document Templates
- E-Document Certification in the Outbound Process
- E-Document Network Status Overview
- Creating E-Document Sending Methods
- E-Document Email Custom Templates
- Selecting a Designated E-Document Sender
- Setting Up Custom Roles to Send E-Documents
- Customizing Roles to Restrict E-Document Generation or Sending
- Deploying the Bulk Generation Script for E-Documents
- Deploying the Script for Bulk Scheduled Sending of E-Documents
- Scheduled Script for Getting Network Status of E-Documents
- Updating E-Document Certification Statuses
- Processing E-Documents Automatically for Individual Transactions
- Electronic Invoicing Inbound Email Capture
- Using SOAP Web Services for Inbound Processing
- Setting Up Custom Roles that can Convert Inbound E-Documents
- Inbound Validation Plug-ins
- Deploying Automatic Bulk Conversion Script for Inbound E-Documents