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.
| Area | Check | Metadata-level test | Pass (2) | Partial (1) | Fail (0) |
|---|---|---|---|---|---|
| Coverage | K1. Years in all three systems | Which years are held in Ariba, SAP and the review library at the same time? | Three or more overlapping years | One to two overlapping years | No overlap, or unknown |
| Coverage | K2. Packets for reviewed invoices | Does every manually reviewed invoice get a packet? | Yes, by written rule | Above a threshold only | No consistent packet |
| Linkage | K3. Packet found from order number | Can a packet be found from the order number alone? | Yes, packets are named or tagged by order number | Sometimes; older packets named by supplier and month | No; found by searching |
| Linkage | K4. Version number carried | Does the packet or the invoice record say which order version was used? | Yes, in a field or file name | Only in the document text | Not recorded |
| Timestamps | K5. Packet history survives | Does the review library keep version history for packet files? | Yes, since the start of the period | For recent years only | Files replaced without history |
| Timestamps | K6. Block and release dates | Are block and release recorded as separate dated events? | Yes, both | Release only | Neither |
| Outcomes | K7. Release reason recorded | Is the reason for releasing a block written anywhere structured? | Yes, a reason field or packet note | In email only | Not recorded |
| Gaps | K8. Amended-order holds findable | Can the team find holds on matched invoices that followed an order change? | Yes, and they can say roughly how often | They know it happens, cannot find them | Never 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.
| Check | Result | Points |
|---|---|---|
| K1. Years in all three systems | Pass: 2020 to now in all three | 2 |
| K2. Packets for reviewed invoices | Partial: packets above a threshold only | 1 |
| K3. Packet found from order number | Partial: packets before 2023 named by supplier and month | 1 |
| K4. Version number carried | Fail: not recorded in packets | 0 |
| K5. Packet history survives | Pass | 2 |
| K6. Block and release dates | Pass | 2 |
| K7. Release reason recorded | Partial: in email only | 1 |
| K8. Amended-order holds findable | Pass: the team found such holds in its test | 2 |
| Total | 4 pass, 3 partial, 1 fail | 11 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.