Understanding E-Document Components and Records

After installation, the Singapore PEPPOL-Ready E-Invoicing SuiteApp includes outbound and inbound e-document templates, preconfigured e-document package, sending method, a custom configuration record, an inbound e-document, and scripts. The following table lists and describes these components.

Important:

The default e-document templates, components, records, and configurations included with the SuiteApp must not be edited or customized to use for other countries. Their use is only specific to PEPPOL Singapore.

E-document Component	Description
E-documents	outbound	Outbound e-documents are XML files that you will generate from invoice or credit memo records to send to the PEPPOL API. The SuiteApp can generate the XML e-documents of invoices and credit memos. For more information, see Overview of Outbound E-Document Process.
inbound	Inbound e-documents are also XML files sent by the PEPPOL API to NetSuite and received by the SuiteApp. The SuiteApp can convert inbound e-documents into sales order, vendor bills and vendor credits. For more information, see Overview of Inbound E-Document Processing.
E-document Templates	outbound	Outbound e-document templates are XML files that store details of invoice and credit memo fields and their values. They are based on PEPPOL standard templates. The SuiteApp includes five outbound e-document templates: Singapore PEPPOL Outbound Invoice Template Singapore PEPPOL Outbound Credit Memo Template Singapore PEPPOL DataPost Outbound Invoice Template Singapore PEPPOL DataPost Outbound Credit Memo Template Singapore PEPPOL DataPost Outbound Purchase Order Template After installing and configuring the SuiteApp, five outbound e-document templates are automatically associated with the e-document package. Two of these templates are enabled depending on the access point selected during Singapore PEPPOL E-Invoicing Configuration record. For more information, see Creating E-Document Templates. Note: You can only make changes to the existing templates. The changes you make are considered during the SuiteApp upgrade.
inbound	The inbound templates are based on the PEPPOL standard template. This JSON file enables the system to map the values in the inbound e-document from PEPPOL, to the fields in the vendor bill, vendor credit, or sales order that will be created from the inbound e-document. The SuiteApp includes three inbound e-document templates: Singapore PEPPOL Inbound vendor Bill Template Singapore PEPPOL Inbound Vendor Bill Credit Template Singapore PEPPOL Inbound Sales Order Template For more information, see Creating E-Document Templates Warning: Avoid creating and using new templates, as this action may result in inbound process failure. You can only make changes to the existing templates. These changes you make are considered during the SuiteApp upgrade.
E-Document Transaction Response Template	Singapore PEPPOL Invoice & Credit Memo Response Template	Inbound invoice and credit memo transaction response template in XML format is used for creating transaction response. The generated transaction response XML must be in compliance with Singapore PEPPOL DataPost API.
Singapore PEPPOL Order Response Template	The inbound sales order response template in XML format is used for creating order response must be in compliance with Singapore PEPPOL DataPost API.
E-document Package	The SuiteApp includes the e-document package, Singapore PEPPOL E-document package. This specifies the e-document templates to be used, and the sending method, which is webservices. The e-document package is already assigned to or associated with customer and vendor records. For more information, see Understanding E-Documents and E-Document Packages.
Sending Method	The SuiteApp includes a preconfigured sending method (Singapore PEPPOL Sending Method for eInvoice.sg access point and Singapore PEPPOL DataPost Sending method for DataPost access point) which uses REST web services to send outbound e-documents to the PEPPOL API. The sending method is implemented as a plug-in, and is already assigned to or associated with the e-document package record. For more information, see Creating E-Document Sending Methods.
SG PEPPOL E-Invoicing Configuration record	The SuiteApp includes this custom record that has fields for entering the PEPPOL ID, access point, and credentials, such as API key and API secret. You must create a new instance of this record for every company or business segment that you registered and enrolled to PEPPOL Singapore. Then, enter the PEPPOL ID, access point, and credentials of each company or business segment on their corresponding configuration record. For more information, see Creating a Singapore PEPPOL E-Invoicing Configuration Record.

E-document Component

Description

E-documents

outbound

Outbound e-documents are XML files that you will generate from invoice or credit memo records to send to the PEPPOL API. The SuiteApp can generate the XML e-documents of invoices and credit memos. For more information, see Overview of Outbound E-Document Process.

inbound

Inbound e-documents are also XML files sent by the PEPPOL API to NetSuite and received by the SuiteApp. The SuiteApp can convert inbound e-documents into sales order, vendor bills and vendor credits. For more information, see Overview of Inbound E-Document Processing.

E-document Templates

outbound

Outbound e-document templates are XML files that store details of invoice and credit memo fields and their values. They are based on PEPPOL standard templates.

The SuiteApp includes five outbound e-document templates:

Singapore PEPPOL Outbound Invoice Template
Singapore PEPPOL Outbound Credit Memo Template
Singapore PEPPOL DataPost Outbound Invoice Template
Singapore PEPPOL DataPost Outbound Credit Memo Template
Singapore PEPPOL DataPost Outbound Purchase Order Template

After installing and configuring the SuiteApp, five outbound e-document templates are automatically associated with the e-document package. Two of these templates are enabled depending on the access point selected during Singapore PEPPOL E-Invoicing Configuration record.

For more information, see Creating E-Document Templates.

Note:

You can only make changes to the existing templates. The changes you make are considered during the SuiteApp upgrade.

inbound

The inbound templates are based on the PEPPOL standard template. This JSON file enables the system to map the values in the inbound e-document from PEPPOL, to the fields in the vendor bill, vendor credit, or sales order that will be created from the inbound e-document.

The SuiteApp includes three inbound e-document templates:

Singapore PEPPOL Inbound vendor Bill Template
Singapore PEPPOL Inbound Vendor Bill Credit Template
Singapore PEPPOL Inbound Sales Order Template

For more information, see Creating E-Document Templates

Warning:

Avoid creating and using new templates, as this action may result in inbound process failure. You can only make changes to the existing templates. These changes you make are considered during the SuiteApp upgrade.

E-Document Transaction Response Template

Singapore PEPPOL Invoice & Credit Memo Response Template

Inbound invoice and credit memo transaction response template in XML format is used for creating transaction response. The generated transaction response XML must be in compliance with Singapore PEPPOL DataPost API.

Singapore PEPPOL Order Response Template

The inbound sales order response template in XML format is used for creating order response must be in compliance with Singapore PEPPOL DataPost API.

E-document Package

The SuiteApp includes the e-document package, Singapore PEPPOL E-document package. This specifies the e-document templates to be used, and the sending method, which is webservices. The e-document package is already assigned to or associated with customer and vendor records.

For more information, see Understanding E-Documents and E-Document Packages.

Sending Method

The SuiteApp includes a preconfigured sending method (Singapore PEPPOL Sending Method for eInvoice.sg access point and Singapore PEPPOL DataPost Sending method for DataPost access point) which uses REST web services to send outbound e-documents to the PEPPOL API. The sending method is implemented as a plug-in, and is already assigned to or associated with the e-document package record.

For more information, see Creating E-Document Sending Methods.

SG PEPPOL E-Invoicing Configuration record

The SuiteApp includes this custom record that has fields for entering the PEPPOL ID, access point, and credentials, such as API key and API secret. You must create a new instance of this record for every company or business segment that you registered and enrolled to PEPPOL Singapore. Then, enter the PEPPOL ID, access point, and credentials of each company or business segment on their corresponding configuration record.

For more information, see Creating a Singapore PEPPOL E-Invoicing Configuration Record.

General Notices