SAP S/4HANA and Trace Global
Read utility vendor invoices and payments from SAP S/4HANA and post audited, coded utility invoices back to Accounts Payable.
- Vendor
- SAP
- Method
- Supplier Invoice OData API (API_SUPPLIERINVOICE_PROCESS_SRV) and INVOIC IDocs, with vendor and payment extracts
- Direction
- Bidirectional
- Typical setup
- 2 to 4 weeks
In most SAP shops, utility bills are posted as supplier invoices against a handful of utility vendor records, often with one site's charges spread across several cost centers. Trace Global reads those postings so every bill we audit is tied to what Accounts Payable actually paid.
We connect through the Supplier Invoice OData API published on the SAP Business Accelerator Hub, or through INVOIC IDocs if your team already routes utility invoices that way. For customers that want Trace Global to replace manual keying, we post audited invoices back with company code, G/L account, cost center and tax code already set.
The connection runs through a technical communication user with a role your SAP Basis team defines. We request only the authorizations needed for the objects below.
How the data feeds the audit
- Match every utility statement to a posted invoice to catch duplicate payments and unpaid bills.
- Quantify late fees by comparing utility due dates with SAP payment dates.
- Identify invoices still posting to closed or divested sites.
- Confirm that a utility refund or credit was received and cleared against the right vendor.
Setup
- 1Create a technical communication user and arrangement in S/4HANA.
- 2Assign the role covering supplier invoices, payments and supplier master read.
- 3Provide the list of utility vendor numbers in scope.
- 4Run a reconciliation of 12 months of postings against captured bills.
- 5Enable outbound posting if you want audited invoices sent to AP.
Data exchanged
| Object | Detail |
|---|---|
| Supplier invoices | Document number, posting date, invoice reference, gross amount and payment block status for utility vendors. |
| Account assignments | Company code, G/L account, cost center and WBS element per invoice line. |
| Payments | Clearing documents and payment dates, used to confirm what was paid and when. |
| Supplier master | Utility vendor numbers and remit-to details, matched to utility accounts. |
| Audited invoices (outbound) | Coded invoices posted for approval, with the bill PDF attached. |
SAP S/4HANA questions
Yes, through INVOIC IDocs or flat-file extracts. The OData API applies to S/4HANA Cloud and on-premise releases that expose it.
No. Outbound invoices enter your normal workflow and follow your approval rules.
Yes. The extract is filtered to the vendor numbers you list, and the role can be restricted to them.
Related connectors
Find out what your utilities owe you.
Connect bills for up to 50 meters. Get the findings report in about three weeks. Pay nothing unless money comes back.
- from bill access to first findings report
- 21 daysfrom bill access to first findings report
- of filed claims accepted by the utility in full or in part
- 94%of filed claims accepted by the utility in full or in part