Skip to main content
2026
Search
Search Indirect Tax Support Help and Support.

This article applies to:

  • Product: ONESOURCE E-Invoicing

ONESOURCE-Pagero Global E-Invoicing for Coupa Version 1.0.0.0

Update summary

ONESOURCE Pagero Global E-Invoicing for Coupa version 1.0.0.0 is the initial general availability (GA) release of the integration between Pagero Network / ONESOURCE E-Invoicing (Pagero/OEI) and Coupa Procurement (AP/Invoicing module). This release establishes the baseline, certified integration that receives compliant e-invoices and credit notes from the Pagero Network and creates corresponding invoice records in Coupa, with invoice lifecycle status synchronized back to Pagero for supplier visibility.
This release includes the following core capabilities
  • API-based invoice ingestion
     from Pagero/OEI to Coupa using a secure, OAuth-protected REST API, supporting near real-time, one-invoice-per-request processing.
  • Support for unbacked (non-PO) and PO-backed invoices and credit notes
    , including single-line and multi-line, quantity-based and amount-based variations, and invoices referencing multiple purchase orders.
  • Attachment handling
     for the original legal e-invoice document, a human-readable PDF rendering (image scan), and additional supporting documentation.
  • Tax processing
     for no-tax and line-level tax scenarios, including Peppol/BIS tax category to Coupa tax code mapping.
  • Remit-to address and tax ID mapping
    , including support for single and multiple remit-to entries per supplier.
  • Error handling
     visibility mapped to supplier-facing messages in ONESOURCE Integration UI.
  • Invoice lifecycle status synchronization
     from Coupa back to supplier through ONESOURCE integration.
  • Country compliance certification
     completed for Belgium and other BIS 3.0/EN16931 countries.

Functional change

Invoice & credit note ingestion
Overview
This release establishes the ability to ingest compliant e-invoices and credit notes from the Pagero Network and create corresponding records in Coupa in real time, without manual intervention.
Capability
Pagero/OEI pushes invoice and credit note payloads to Coupa through a dedicated REST API secured with OAuth. Requests are throttled to respect Coupa's platform limits (approximately 20 requests per second, one invoice per API call, up to 500 lines per invoice).
The following document types and line-item patterns are supported in this release:
Document Category
Supported Line Patterns
Unbacked (non-PO) invoices
Single amount-based line; single quantity-based line; multiple amount-based lines; multiple quantity-based lines
PO-backed invoices
Single amount-based line; single quantity-based line; multiple amount-based lines; multiple quantity-based lines
Unbacked (non-PO) credit notes
Single amount-based line; single quantity-based line; multiple amount-based lines; multiple quantity-based lines
PO-backed credit notes
Single amount-based line; single quantity-based line; multiple amount-based lines; multiple quantity-based lines
PO-backed invoices and credit notes are validated against Coupa's standard two-way matching (invoice vs. purchase order); invoices are created in Pending Approval status and classified as PO-backed or non-PO based on the references provided in the source document.
Attachments
Overview
This release supports carrying the legally relevant invoice document and a human-readable rendering through to Coupa, alongside optional supporting documentation.
Attachment Type
Coupa Placement
Requirement
Original legal e-invoice (UBL/XML)
Invoice attachment
Mandatory
Human-readable invoice rendering (PDF)
Image scan
Mandatory
Embedded supporting documents (e.g., proof of delivery)
Invoice attachment
Optional
Original email containing the invoice
Invoice attachment
Optional
Attachments are supported up to Coupa's 250 MB per-attachment limit, with a recommended target of 16 MB or less per attachment for optimal performance. Where an attachment exceeds the applicable limit, the invoice is still created in Coupa and the attachment failure is reported back to Pagero.
Taxes
Overview
This release supports the tax scenarios required for standard Coupa invoice processing and certification.
  • No-tax invoices
     — invoices without tax elements are accepted with Coupa tax recorded as zero.
  • Line-level tax
     — each invoice line carries its own tax code and rate, mapped from the Peppol/BIS tax category to the corresponding Coupa tax code.
Peppol/BIS tax categories are mapped to Coupa tax codes as follows (Belgium shown as the certified example; the same design pattern applies to other in-scope countries): Header-level tax and multi-tax/summary-charge tax scenarios are not supported in this release.
Remit-to addresses and tax IDs
Overview
This release supports mapping supplier remittance information, including associated tax identifiers, so that invoices are routed to the correct Coupa remit-to record.
  • Single remit-to address
     with an associated tax ID is matched to the corresponding Coupa remit-to record.
  • Multiple remit-to addresses
     with tax IDs are supported, with the applicable entry selected based on buyer entity and country rules.
Data enrichment
Overview
This release supports enrichment of invoices with data that is not always provided by the supplier but is required for successful invoice creation and processing in Coupa, including missing payment terms and net due date through Pagero.
Error handling
Overview
This release includes controls to prevent duplicate invoice creation and to surface Coupa validation errors to suppliers in an actionable way.
  • Duplicate prevention
     — invoices matching an existing combination of supplier, invoice number, and invoice date are rejected on resubmission.
  • Error handling
     — Coupa validation errors (for example, an invalid tax code) are mapped to clear, supplier-facing messages returned through Pagero.
Master data prerequisites
Overview
Supplier, purchase order, chart-of-accounts, currency, and look-up-value master data synchronization is out of scope for this integration. A deterministic mapping between the Pagero supplier and the Coupa supplier (preferably keyed on Coupa Supplier ID and/or VAT ID) must exist as a prerequisite before invoices for that supplier can be processed.
Invoice status synchronization
Overview
This release synchronizes key invoice lifecycle events from Coupa back to Pagero so that suppliers have visibility into the status of submitted invoices.
Coupa Trigger
Status Returned to Pagero
Notes
Invoice successfully created
Notification
Coupa invoice ID and Pagero document ID are linked
Pending Approval
In process
Default status after successful submission
Approved
Accepted
May be reached automatically where no approval workflow is configured
Disputed
Rejected
Includes mandatory reason code and reason text
Rejected
Rejected
Includes mandatory reason code and reason text
Void
Rejected
Includes reason code and reason text
On-hold
On-hold
Paid
Paid
Includes payment date; payment amount optional

Known limitations/out of scope for v1.0.0.0

The following behaviors and scenarios apply to this release and are candidates for future enhancement:
  • Header-level PO ID
     from the Peppol/BIS billing document is not mapped to Coupa in this release; only line-level PO references are supported.
  • Billing account defaulting
     relies on a customer-maintained default value configured in the ONESOURCE integration solution, rather than Coupa's own default billing account configuration.
  • Header-level tax distribution
     is not supported in this release; only line-level tax is certified.
  • Multi-tax and summary-charge tax scenarios
     (e.g., tax on shipping, handling, or miscellaneous charges) are not included in this release.
  • Network-outage retry and queue behavior
     is pending confirmation and validation with Coupa and is not yet certified.
  • Supplier, PO, chart-of-accounts, and other master data synchronization
     is out of scope; the relevant master data must be available in Coupa.
  • 3-way matching
     (PO > Receipt > Invoice) is out of scope for this release.

Customer prerequisites

Customers need to complete the following before using this release:
  • Maintain supplier master data and the Pagero-to-Coupa supplier mapping in Coupa and/or the integration middleware prior to invoice submission.
  • Ensure required legal entity, tax, and chart-of-accounts configuration exists in Coupa for all in-scope buyer entities.
  • Confirm attachment size and file-type settings align with Coupa's supported file types and the recommended 16 MB attachment target.