# Invoice-to-payment records across systems | SourceX

Canonical: https://refer.sourcex.si/guides/chain-invoice-to-payment
Last updated: 2026-11-04

A company connects invoice-to-payment records by carrying the purchase order number and its version from procurement into receiving, invoice verification, any review file and the payment run, and by noting which version each person actually looked at. In a setup with SAP Ariba for ordering, SAP for receipts and invoices, and SharePoint for review files, the weak join is the version. When a changed order never reaches the person approving the bill, the bill is correct and still gets held.

## The business task behind the chain

Pay the right amount for what was ordered and received, once, on time. Most bills clear a three-way match of order, receipt and invoice without anyone looking at them. The rest stop for a human: a price above tolerance, a quantity nobody expected, a supplier who changed bank details, an approver who is on leave. Every stop leaves a decision in the record, such as a hold, a question to the buyer, a correction or a release, and each decision has a date, a person and a reason.

Those decisions, joined to the order version and the outcome, are what makes an accounts payable history useful as training and evaluation material for finance agents. A model that only sees cleared bills learns nothing about judgment. One that sees why a bill waited, who decided and what changed learns how a finance team actually works. The [accounts payable exceptions page](/data-types/accounts-payable-exception-handling-process) covers the exception records themselves; this page is about the links between tools, and the one link that most often fails.

Orders change for ordinary reasons: a freight charge added after quoting, a partial delivery split into two shipments, a substitute part at a different unit cost, a quantity raised once a project scope is confirmed. Each change is small and legitimate. What turns it into a delay is timing. If the person who approves the bill is working from an earlier copy, they see an overcharge that is not there, and an early-payment discount or a supplier's goodwill can be lost while the question goes round.

## How can a company connect invoice-to-payment records across systems?

With one joined timeline per invoice, keyed on the purchase order number, with a column that says which order version each step used. The table below is an Illustrative example built for this page. A 420-person industrial services company orders valve kits. Procurement runs in Ariba, receipts and invoice verification in SAP, and review files in a document library.

| Date | Tool | Event | Order version used |
|---|---|---|---|
| March 3 | Procurement | Purchase order PO-7731 approved: 400 kits at $120, $48,000 | Version 1 |
| March 10 | Procurement | Change order approved and sent to the supplier: 460 kits, $55,200 | Version 2 |
| March 18 | ERP | Goods receipt for 460 kits | Version 2 |
| March 20 | ERP | Invoice for $55,200 posted and matched to order and receipt | Version 2 |
| March 20 | Document library | Review file for invoices over $40,000 created with the order PDF saved on March 3 | Version 1 |
| March 20 | ERP | Budget owner sees $55,200 against $48,000; invoice blocked for payment pending review | Version 1 |
| March 27 | Document library | Accounts payable adds the version 2 order PDF to the file | Version 2 |
| April 2 | Document library | Budget owner approves | Version 2 |
| April 8 | ERP | Block released; paid in the next payment run | Version 2 |

Each tool did its job. Procurement versioned the change and sent the approved new version to the supplier. The ERP matched the invoice. The reviewer's file held a snapshot from before the change. Most of the 19 days between invoice and payment went to a question the current order had already answered.

## What breaks when an amended order never reaches the reviewer

The match succeeds and the review fails. In the timeline above, the ERP matched the $55,200 invoice to version 2 of the order and the receipt for 460 kits. The budget owner, reading a file built from the March 3 PDF, compared $55,200 with $48,000 and stopped the payment. Nothing in the ERP or procurement tool recorded which version the reviewer saw. Only the review file did, and only if its version history survived.

That makes the review packet the deciding record, and the one most often treated as disposable. SharePoint version history lists earlier versions of a file with the date and the user who saved each, and restoring an old version adds a copy as the latest version rather than deleting later ones. Where packets live in a library with versioning on, the March 20 and March 27 states can both be shown. Where reviewers work from email attachments, the version they saw is gone.

Two documented behaviors explain where to look. In Ariba, an order change creates a new requisition version that goes through approval before the new order version is sent; changes to accounting fields also create a version, but by default it is not sent to the supplier. In SAP invoice verification, a block applies to the whole invoice and release is a separate step, so the release date is its own record.

Four metadata questions tell you whether the company can rebuild the version column for its own invoices:

| Question | Strong answer | Weak answer |
|---|---|---|
| Where are review packets kept? | A SharePoint library per fiscal year, versioning on | Email attachments |
| Does the packet name the order version? | The version number is in the file name | Only the order number |
| Is the block reason recorded in SAP? | A reason code on every blocked invoice | Free text, sometimes |
| How many invoices a year go to manual review? | A stated band, such as 3,000 to 5,000 | Not known |

None of these needs an invoice, a supplier name or an amount. They describe whether the chain can be joined, which is what SourceX reviews first.

## Who can sponsor the introduction, and what stays unknown

The CFO or controller usually owns the finance records and can sponsor the introduction, while the CEO authorizes a licensing discussion; the AP manager and the SAP and SharePoint administrators can answer the packet but cannot approve anything. Supplier agreements, personal data in approvals and any group-level IT policy are flagged for SourceX's rights review; whether there is demand for this record type, and what preparation would involve, stay unknown until that review.

The company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. SAP partners have a dedicated overview on the [SAP partner referral page](/for/sap-partner-referral-program); other system guides are in the [systems hub](/systems).

## Go deeper on invoice-to-payment records

- [What a single-system invoice export leaves out](/guides/invoice-to-payment-missing-context): one Illustrative case read before and after its surrounding context is added.
- [Invoice-to-payment metadata packet](/resources/invoice-to-payment-metadata-packet): the fields a partner can share without touching raw records, with an Illustrative filled packet.
- [Invoice-to-payment completeness checklist](/resources/invoice-to-payment-completeness-checklist): a pass, partial or fail scorecard for judging whether the records are complete enough to discuss.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client can say whether its reviewers see the current order version and who owns each of the three systems, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its CFO; [what you need to receive a referral payment](/resources/what-do-i-need-to-receive-a-referral-payment) lists the paperwork on your side.

## Sources

- https://help.sap.com/docs/buying-invoicing/purchasing-guide-for-procurement-professionals/change-and-cancel-order-processes
- https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/ed84b70c199d4470ae2e5ccb93b2e45b/7870b6531de6b64ce10000000a174cb4.html
- https://support.microsoft.com/en-us/sharepoint/documents-and-library/restore-a-previous-version-of-an-item-or-file-in-sharepoint
- https://refer.sourcex.si/terms
