Invoice-to-payment completeness scorecard: eight checks before you describe an AP trail

Short answer

An invoice-to-payment evidence trail breaks in four ways: a missing identifier (the review packet cannot be found from the order number), a missing timestamp (an order PDF was replaced without history), a version mismatch (the packet held one order version while SAP matched another) and a missing outcome (the block was released with no reason recorded). The scorecard below turns those, plus coverage and known gaps, into eight checks with a pass, partial or fail guide, so a partner can describe the trail without opening a record.

Visual briefFull-size diagram
A row of eight check tiles, grouped as coverage, linkage, timestamps, outcomes and gaps, turning green, amber or orange one by one while a semicircular gauge climbs to 11 of 16 points.
Illustrative score for a fictional company: 11 of 16 points.

This scorecard is part of the invoice-to-payment guide. The metadata packet describes what exists; this page grades whether it holds together.

The scorecard

Score each check 2 for pass, 1 for partial and 0 for fail or unknown. Eight checks, 16 points in all.

AreaCheckMetadata-level testPass (2)Partial (1)Fail (0)
CoverageK1. Years in all three systemsWhich years are held in Ariba, SAP and the review library at the same time?Three or more overlapping yearsOne to two overlapping yearsNo overlap, or unknown
CoverageK2. Packets for reviewed invoicesDoes every manually reviewed invoice get a packet?Yes, by written ruleAbove a threshold onlyNo consistent packet
LinkageK3. Packet found from order numberCan a packet be found from the order number alone?Yes, packets are named or tagged by order numberSometimes; older packets named by supplier and monthNo; found by searching
LinkageK4. Version number carriedDoes the packet or the invoice record say which order version was used?Yes, in a field or file nameOnly in the document textNot recorded
TimestampsK5. Packet history survivesDoes the review library keep version history for packet files?Yes, since the start of the periodFor recent years onlyFiles replaced without history
TimestampsK6. Block and release datesAre block and release recorded as separate dated events?Yes, bothRelease onlyNeither
OutcomesK7. Release reason recordedIs the reason for releasing a block written anywhere structured?Yes, a reason field or packet noteIn email onlyNot recorded
GapsK8. Amended-order holds findableCan the team find holds on matched invoices that followed an order change?Yes, and they can say roughly how oftenThey know it happens, cannot find themNever considered

Running the tests on a handful of blocked invoices

The company can test each check against a small number of its own blocked invoices; five is plenty. The partner records only whether the test could be run and what it showed, in words like "K3: found 4 of 5 packets from the order number." The invoices themselves never leave the AP team.

Several checks depend on documented system behavior worth knowing in advance:

  • K4 and K8, order versions. SAP's documentation says that in Ariba, changing an order creates a new requisition version that goes through approval, and once approved a new version of the order is sent to the supplier. Changes to accounting fields create a version that by default is not sent to the supplier. One order can therefore have several versions, and the test is whether the reviewer's version was recorded.
  • K5, packet 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 restoring an older version makes a copy of it the latest version rather than deleting later ones. If versioning was in use, the library can show when a corrected order arrived in the packet.
  • K6, blocks. In SAP invoice verification, a variance above tolerance posts the invoice but blocks it for payment, release is a separate step, and a block applies to all items on the invoice. Release is therefore a record in its own right, and the question is whether its date and reason survive.

The amended-order check, asked by name

K8 is the one to ask about directly, using these words: "Do you ever see holds on invoices that SAP had already matched, after the order was changed?" A company that says "yes, and we can find them" is describing a labeled exception, a particularly useful kind of record in an accounts payable history. A company that says "probably, but we could not find them" scores partial, which is still an honest description.

Do not estimate how often it happens yourself, and do not suggest a number. The missing-context page shows one such hold read with and without the systems around it, and the accounts payable exceptions page covers exception records as a data type.

Reading the score: an Illustrative result

Illustrative: a fictional 610-person building products distributor scored its trail with the AP manager and the SharePoint administrator.

CheckResultPoints
K1. Years in all three systemsPass: 2020 to now in all three2
K2. Packets for reviewed invoicesPartial: packets above a threshold only1
K3. Packet found from order numberPartial: packets before 2023 named by supplier and month1
K4. Version number carriedFail: not recorded in packets0
K5. Packet history survivesPass2
K6. Block and release datesPass2
K7. Release reason recordedPartial: in email only1
K8. Amended-order holds findablePass: the team found such holds in its test2
Total4 pass, 3 partial, 1 fail11 of 16

Read the pattern, not just the total. This trail is strong on timestamps and has the amended-order case in view, but the version number is never written down, so every amended-order hold has to be reconstructed from packet history. That is exactly the kind of note SourceX needs, and it is more useful than a higher score with no explanation. For the general idea of judging data quality before any commitment, see data quality due diligence.

Before you describe the result to anyone

Share the score only with the people who answered it and the sponsor. The CFO or controller usually owns finance records, and the CEO can authorize a licensing discussion; the AP manager and administrators answer the checks but cannot approve anything. Supplier agreements and personal data in approvals are for 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, preparation effort and any offer stay unknown until SourceX reviews an application. If an ERP replacement is planned, run the scorecard before cutover; the ERP replacement handoff checklist helps with timing.

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 the scorecard shows the company can find its amended-order holds and say where its trail breaks, register as a partner, check the company against who qualifies, and read the program terms before introducing its CFO.

  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

Does the partner run the tests on real invoices?

No. The company runs any test against its own blocked invoices if it chooses to. The partner records only whether the test can be run and what the answer was, never the invoices themselves.

Is a low score a reason not to introduce the company?

Not by itself. A score describes the trail; it does not decide fit. A company that knows exactly where its trail breaks is easier to discuss than one that has never looked.

Why does the amended-order check carry so much weight?

Because it is the case that looks ordinary in a single system and turns out to be a labeled exception once the systems are joined. A company that can find those holds is describing a useful record; one that cannot is describing ordinary invoices.

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