You have an external system — a third-party ERP, a legacy billing platform, or even an SAP system not yet integrated with SAP Document and Reporting Compliance — that generates electronic invoices in Singapore. You need to submit these invoices to the Inland Revenue Authority of Singapore (IRAS) or send them to customers via the InvoiceNow/Peppol network, all through SAP Document and Reporting Compliance. The question is: how do you bridge these two worlds?SAP Document and Reporting Compliance now supports External Documents for Singapore. Your external system can upload invoice XML files into SAP DRC using the gco_external REST API, and SAP DRC handles the compliance submission end-to-end. In this blog, I'll walk you through the setup steps — from SAP Note implementation to system configuration, testing, and monitoring.
Get to know about Singapore GST InvoiceNow requirement, and Singapore Peppol eInvoice (InvoiceNow). please check the blog
GST InvoiceNow – submission of invoice data to Singapore Tax Authority
SAP Document and Reporting Compliance for Singapore Peppol eInvoices (InvoiceNow)
Supported Scenarios
The following Singapore e-invoicing scenarios are supported through External Documents:
Scenario | Description |
1A — Peppol Customer Invoice | Send a Peppol customer invoice to a customer or IRAS via InvoiceNow / Peppol Network |
1B — Peppol Supplier Invoice to IRAS | Submit a Peppol supplier invoice to IRAS |
2A/2B — Non-Peppol Customer Invoice to IRAS | Submit a customer invoice (non-Peppol) to IRAS |
3A/3B — Non-Peppol Supplier Invoice to IRAS | Submit a supplier invoice (non-Peppol) to IRAS |
Note: For detailed XML sample files for all four scenarios, refer to SAP Note 3840047 — Electronic Invoice Processing for Singapore: Preparation of External Documents XML Files.
Prerequisites
Before starting, ensure the following are in place:
- SAP S/4HANA On-Premise (S4CORE 102 or higher) or SAP ERP (SAP_APPL 606, 617, or 618)
- You have implemented Singapore DRC solution Notes.
- SSL/TLS is configured on your SAP system
- Your external system can call REST APIs
Part 1: SAP Note Implementation
SAP provides two separate SAP Notes for the Singapore External Documents feature, covering different submission scenarios. Implement the one(s) relevant to your business requirements.
SAP Note | Scenario |
3752090 | Submitting eInvoices to IRAS |
3776506 | Sending Peppol eInvoices to customers via InvoiceNow |
Step 1: Implement SAP Note 3752090 (Submission to IRAS)
Go to transaction SNOTE. Download and implement SAP Note 3752090.
Step 2: Activate BC Set EDOC_SG_C5_FACTORY_EXT_V3
After implementing the SAP Note, activate the Business Configuration Set that registers the Singapore-specific factory class for External Documents. Go to transaction SCPR20. In the BC Set field, enter EDOC_SG_C5_FACTORY_EXT_V3. Activate it! Note: The Expert Mode flag is required. Without it, the factory class will not be registered correctly for Singapore.
Step 3: Implement SAP Note 3776506 (Peppol Submission to Customers)
Go to transaction SNOTE. Download and implement SAP Note 3776506.
Part 2: System Configuration
All configuration below is done via transaction SM30 (Table View Maintenance).
Step 1: Define External Document Systems – Register your external system as a logical system in SAP. Enter view V_TBDLS. Create a new entry and save.
- Logical System: A unique identifier for your external system (e.g., QKVCLNT440).
- Name: A meaningful description.
Step 2: Maintain External Document Organizational Unit – Define the organizational unit within your external system that issues invoices. Enter view GCOV_EXT_ORGUNIT. Create a new entry and save.
- External Document Org. Unit: An identifier for the external organizational unit.
- External Document Org. Unit Description: A meaningful description.
Step 3: Assign External System and Org Unit to Company Code – Link the external system and org unit to the relevant SAP company code. Enter view GCOV_EXT_ORGCCOD. Create a new entry and save.
Step 4: Assign Process Status to External Document Status – Map external document statuses to SAP eDocument process statuses. Enter view EDOPROCEXTSTATV. Create new entries based on your requirements and save.
Step 5: Verify Factory Class Registration(Only required when you submit eInvoices to IRAS)Confirm that the Singapore factory class has been registered (this should already be in place after activating the BC Set in Step 2). Enter view EDOEXTAPIFACTV. Confirm that an entry exists for country SG (Singapore) with the correct factory class name.
eDoc. Process | Factory Class | Scenario |
SGC5INV | CL_EDOC_EXT_DOC_API_SG_C5 | Invoice submission to IRAS (C5) |
Step 6: Activate EXT_DOC Source Type per Company Code Activate the EXT_DOC source type for each relevant company code. Without this step, the eDocument framework will reject all external documents. Enter view EDOCOMPANYACTIV. Find the entry for your Singapore company code (e.g., SG01). Ensure the Active checkbox is checked for source type EXT_DOC.
Part 3: API for External Documents
For a detailed description of the API calls, please refer to the SAP Help Portal. In this blog, I will share an example of calling the Create External Document API using Bruno.
Payload:
{“logicalSystemID”: “QKVCLNT440”,
“countryRegion”: “SG”,
“externalDocuments”: [
{
“externalOrgUnit”: “SG_C5_TEST_ORG_UNIT”,
“externalDocumentType”: “CUSTOMER_INVOICE”,
“externalDocumentSubType”: “B2B”,
“externalDocumentKey”: “EXTDOCAZ2026102801”,
“contentParts”: [
{
“partType”: “main”,
“partID”: “PART1A”
}
]
}
]
}
Send request
Check in Transaction EDOC_COCKPIT or Manage Electronic Documents Fiori App
Note: Different externalDocumentType and externalDocumentSubType are required for different scenarios as below.
Scenario | externalDocumentType | externalDocumentSubType |
1A — Peppol Customer Invoice | CUSTOMER_INVOICE | B2B |
2A/2B — Non-Peppol Customer Invoice to IRAS | CUSTOMER_INVOICE | B2B_EMAIL |
1B — Peppol Supplier Invoice to IRAS | SUPPLIER_INVOICE | B2B |
3A/3B — Non-Peppol Supplier Invoice to IRAS | SUPPLIER_INVOICE | B2B_EMAIL |
Part 4: Monitoring in SAP
After submission, you can track the document's processing lifecycle in SAP through two options.
Option 1: eDocument Cockpit (Transaction EDOC_COCKPIT)
- Run transaction EDOC_COCKPIT.
- Filter by country SG to find your Singapore external documents.
- Review the processing status. Double-click a document to see details, AIF messages, and the raw XML payload.
Option 2: Manage Electronic Documents (Fiori App)
- Open the Manage Electronic Documents SAP Fiori app.
- Filter by country Singapore.
- Review statuses, drill into individual documents, and trigger resubmissions if needed.
Summary
Here's what you've configured end-to-end:
- SAP Note 3752090 implemented (IRAS submission),BC Set EDOC_SG_C5_FACTORY_EXT_V3 activated/SAP Note 3776506 implemented (Peppol submission to customers)
- External system registered as logical system, org unit defined, and assigned to company code
- Status mapping and factory class verified
- bgRFC destination, HTTP service, SSL, certificate mapping, and AIF all enabled
- External system ready to POST UBL XML invoices to SAP and have them submitted to IRAS or customers via InvoiceNow/Peppol
I hope this blog post was useful for you! If you have questions or run into issues during your setup, feel free to leave a comment below.
Related Resources
- SAP Note 3752090 — Electronic Invoice Processing for Singapore: Support for External Documents
- SAP Note 3840047 — Electronic Invoice Processing for Singapore: Preparation of External Documents XML Files
- SAP Note 3776506 — Electronic Invoice Processing for Singapore: New API-Based Approach for Submitting Electronic Invoices Created in External Systems
- SAP Help Portal: Updates to Submitting Electronic Invoices Created in External Systems
- IMDA InvoiceNow Technical Playbook: https://www.imda.gov.sg/how-we-can-help/nationwide-e-invoicing-framework/invoicenow-technical-playbook
Source link
