Before and after: what a standalone SAP invoice export loses about a delayed payment

Short answer

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.

Visual briefFull-size diagram
A horizontal invoice record running from invoice posted to paid, with three blank gaps in the middle that fill in as context pieces slide down: order version 2 approved in Ariba, the review packet holding version 1 in SharePoint, and version 2 added to the packet.
Illustrative. The SAP export shows a 16-day block; Ariba and SharePoint explain it.

This page belongs to the invoice-to-payment guide. 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:

DateSAP recordWhat it says
February 16Goods receipt1,200 cases received against PO-5140
February 18Invoice posted$39,000, matched to the order and the receipt
February 18Payment blockInvoice blocked for payment
March 6Block releasedReleased, 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

DateSystemWhat the connected history adds
February 2AribaPO-5140 version 1 approved: 1,200 cases at $30, $36,000
February 9AribaChange order approved after a resin surcharge: version 2 at $32.50 a case, $39,000, sent to the supplier
February 18SharePointReview packet for invoices over $35,000 created with the version 1 order PDF
February 18SAP and SharePointBudget owner compares $39,000 with $36,000 and asks for the block
February 26SharePointAccounts payable adds the version 2 PDF to the packet
March 2SharePointBudget 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 invoiceSAP export aloneWhere the missing context lives
Was the invoice correct?Yes, matched to order and receiptSame answer, now against version 2
Why was it blocked?A block reason code, if one was setSharePoint packet: the reviewer compared against version 1
What did the reviewer see?Not heldSharePoint 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 pulledAriba: version 2 approved February 9
What cleared the hold?A release dateSharePoint: version 2 added, then approval on March 2
What did the delay cost?Invoice date and payment dateThe 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.

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 covers the library on its own, and the accounts payable exceptions page 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; to grade the trail, use the completeness scorecard. SAP partners have their own overview on the SAP partner referral page.

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, check the company against who qualifies, and read the program terms before introducing its CEO.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Is the SAP export wrong when it leaves out the reason for a block?

No. It records the system's view: the invoice, the match, the block and the release. The reason a person set or kept the block usually sits in the documents they were reading, which is why the review library matters.

What if the company keeps review packets in email instead of SharePoint?

The before-and-after comparison still works, with the mailbox as the third system. The question becomes whether the order version the reviewer saw can be identified from the email and its attachments, which is usually harder than with a versioned library.

Does the partner need to see a blocked invoice to describe this?

No. The partner asks the accounts payable manager whether holds on matched invoices happen after order changes, and whether the review documents keep version history. That is enough to describe the gap.

Sources

  1. help.sap.com/docs/SAP_S4HANA_ON-PREMISE/ed84b70c199d4470a…
  2. help.sap.com/docs/buying-invoicing/purchasing-guide-for-p…
  3. support.microsoft.com/en-us/sharepoint/documents-and-library/resto…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment