# Invoice-to-payment missing context: before/after | SourceX

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

A single-system invoice-to-payment export loses the reason for the delay. An SAP export alone shows the invoice, its match to the order and goods receipt, any payment block and the release date. It does not show that the order changed after approval, which version of the order the reviewer was looking at, or what finally cleared the hold. That context sits in Ariba, where order versions live, and in the SharePoint library where review packets are kept.

This page belongs to the [invoice-to-payment guide](/guides/chain-invoice-to-payment). It reads one Illustrative invoice twice, first through the SAP export alone and then with the other two systems beside it, so a partner knows what to ask before describing an accounts payable history.

## Before: the invoice as the SAP export shows it

Illustrative: a 520-person food distributor buys packaging film. Every number, date and identifier is fictional.

Pulled from SAP alone, the record for purchase order PO-5140 reads as a short, tidy sequence:

| Date | SAP record | What it says |
|---|---|---|
| February 16 | Goods receipt | 1,200 cases received against PO-5140 |
| February 18 | Invoice posted | $39,000, matched to the order and the receipt |
| February 18 | Payment block | Invoice blocked for payment |
| March 6 | Block released | Released, paid in the next payment run |

A reader concludes that a correct invoice sat blocked for 16 days for no recorded reason. Perhaps a block reason code was set, perhaps not. SAP's documentation describes blocks as applying to the whole invoice, with release as a separate step, so the release date is its own record. Nothing here explains the decision in between.

## After: the same invoice with Ariba and SharePoint beside it

| Date | System | What the connected history adds |
|---|---|---|
| February 2 | Ariba | PO-5140 version 1 approved: 1,200 cases at $30, $36,000 |
| February 9 | Ariba | Change order approved after a resin surcharge: version 2 at $32.50 a case, $39,000, sent to the supplier |
| February 18 | SharePoint | Review packet for invoices over $35,000 created with the version 1 order PDF |
| February 18 | SAP and SharePoint | Budget owner compares $39,000 with $36,000 and asks for the block |
| February 26 | SharePoint | Accounts payable adds the version 2 PDF to the packet |
| March 2 | SharePoint | Budget owner approves in the packet |

Read together, the story changes completely. The invoice was right the whole time. The amended order never reached the reviewer, whose packet held a snapshot from before the change. Most of the 16 days went to resolving a discrepancy that did not exist in SAP. SAP's Ariba documentation explains why the gap is easy to miss: an order change creates a new requisition version that goes through approval, and once approved, the new order version is sent to the supplier. The supplier and SAP both had version 2. The person reviewing the invoice did not.

## What the standalone export loses, and which system holds it

| Question about the invoice | SAP export alone | Where the missing context lives |
|---|---|---|
| Was the invoice correct? | Yes, matched to order and receipt | Same answer, now against version 2 |
| Why was it blocked? | A block reason code, if one was set | SharePoint packet: the reviewer compared against version 1 |
| What did the reviewer see? | Not held | SharePoint version history: version 1 PDF until February 26 |
| When did the order change, and who approved it? | Current order values only, unless change history is pulled | Ariba: version 2 approved February 9 |
| What cleared the hold? | A release date | SharePoint: version 2 added, then approval on March 2 |
| What did the delay cost? | Invoice date and payment date | The 16 days, with the cause named |

The rows SAP cannot answer on its own are exactly the ones that make the record useful for training or evaluating a finance agent. A model that sees only the before view learns that matched invoices get blocked at random. A model that sees the after view learns to check which order version the reviewer had. The general point, that the reasons behind business records are what public data lacks, is made in [what data is missing from AI training](/questions/what-data-is-missing-from-ai-training).

## Why the middle of the story sits in SharePoint version history

The packet library supplies the middle rows only if it kept its history. Microsoft's documentation says SharePoint version history lists each earlier version of a file with the date and the person who saved it, and that restoring an older version makes a copy of it the latest version rather than deleting what came after. That is what lets the packet show the version 1 PDF sitting there until February 26, and who added version 2.

Two habits can erase that middle. If staff replace an order PDF by deleting the old file and uploading a new one under a different name, version history has nothing to show, and the trace of what the reviewer saw disappears. If packets are named by supplier and month instead of by order number, the packet cannot be found from the invoice at all. Both are questions to ask the SharePoint administrator, not things to test. The [SharePoint systems page](/systems/microsoft-sharepoint) covers the library on its own, and the [accounts payable exceptions page](/data-types/accounts-payable-exception-handling-process) covers exception records as a data type.

## Who can describe the gap in an introduction

The accounts payable manager can say whether holds on matched invoices happen after order changes, and whether review packets keep version history. The SAP and SharePoint administrators can confirm configuration. None of them can authorize a licensing discussion; the CEO can, often with the CFO or controller preparing the case. Supplier agreements and personal data in approvals go to SourceX's rights 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. Demand for this record type, what preparation would involve and any offer stay unknown until SourceX reviews it. To describe the three systems in a short form, use the [invoice-to-payment metadata packet](/resources/invoice-to-payment-metadata-packet); to grade the trail, use the [completeness scorecard](/resources/invoice-to-payment-completeness-checklist). SAP partners have their own overview on the [SAP partner referral page](/for/sap-partner-referral-program).

## 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 tell you whether its reviewers ever worked from an outdated order version, and whether the packets kept their history, [register as a partner](/register), check the company against [who qualifies](/who-qualifies), and read the [program terms](/terms) before introducing its CEO.

## Sources

- https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/ed84b70c199d4470ae2e5ccb93b2e45b/7870b6531de6b64ce10000000a174cb4.html
- https://help.sap.com/docs/buying-invoicing/purchasing-guide-for-procurement-professionals/change-and-cancel-order-processes
- 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
