This gap analysis is part of the guide to golden trajectories in an ordinary workflow. Here the same accounts payable task is used the other way round: start from what a reviewer would expect to find, compare it with what companies usually hold, and decide how to describe the shortfall to SourceX without overselling it.
Expected evidence against what companies usually hold
A golden trajectory needs six kinds of evidence. The middle columns reflect how common ERP setups behave; they describe typical patterns, not a survey result.
| Evidence a review expects | What companies usually have | What is usually missing |
|---|---|---|
| Starting state: the three documents that disagree | Almost always, because automated matching depends on them | Rarely missing, except after a system migration |
| Step log: each stop, inquiry, correction and override with user and time | System-generated stop and override events | The inquiry, which happens in a mailbox or chat |
| Supporting paperwork: delivery notes, supplier emails, credit requests | Stored somewhere, often a shared drive | The attachment linking paperwork to the transaction |
| Release authority: who cleared the stop, under which rule | The clearing event | A reason code or approver on manual overrides |
| Document versions: which order revision the bill was compared with | The current order | Revision history, if amendments overwrite |
| Final outcome: a result that stayed final | The booked entry | A link from later reversals or credits to that entry |
The pattern is consistent: systems keep what the software forced, and lose what people did around it. Microsoft's documentation for Dynamics 365 Finance describes three-way matching as comparing invoice price with purchase order price and invoice quantity with receipt quantity, which is why the starting state is nearly always there. No matching rule enforces the inquiry, which is why it is the first thing to vanish.
Four gaps that turn a trajectory back into a story
These four appear in almost every AP archive to some degree. The examples use the main guide's fictional case: an invoice for 120 units meeting a receipt for 100.
| Gap | How it shows up in the invoice case | Why it hurts assessment | Question that exposes it |
|---|---|---|---|
| Missing context | The second delivery note was checked but never attached | The correcting receipt looks unexplained | "Are supporting documents stored with the transaction?" |
| Missing permissions | A manager released the hold manually with no reason code | Nobody can tell if the release was allowed or a shortcut | "Do manual releases require a reason and an approver?" |
| Unclear versions | The purchase order was revised after the invoice arrived | It is unclear which version the invoice matched | "Does the system keep PO revision history?" |
| Unproven outcome | The invoice posted, then was reversed a month later | The "golden" ending was not final | "Are reversals and credits linked to the original voucher?" |
Settings can close some of these gaps going forward. Microsoft's training material notes that Dynamics 365 Finance can be set so that posting an invoice with discrepancies requires approval; where a company uses a setting like that, the approval becomes part of the trajectory. Oracle Payables uses predefined matching hold and release reasons, and some holds can only be released by the system once the exception is fixed, which removes the silent manual release altogether. Where a company has neither, expect SourceX to find more manual releases that need explaining.
Two quieter gaps: no failures, no roles
Some archives pass the four checks above and still fall short, for reasons an owner seldom mentions.
Only clean successes. Appen describes golden trajectories as expert-demonstrated, step-by-step completions, and notes that it gathers demonstrations across different solution paths when a task can be solved more than one way. An AP archive that keeps only exceptions resolved by finding the missing receipt, and not those resolved by a supplier credit, shows one path. Ask whether credits, partial payments and rejected invoices are kept as fully as clean resolutions.
Actions without entitlements. A log may show that a user recorded a receipt, without showing that the user was the warehouse clerk entitled to do so. If system roles were loose, or one shared login was used, the record cannot show that the right person acted. Ask how user roles are set up, not who did what.
A gap profile for one archive (Illustrative)
A fictional 260-person electrical wholesaler answers the six evidence questions in a discovery call. Nothing is shared but answers.
| Evidence | Answer given | Gap status |
|---|---|---|
| Starting state | All three documents in the ERP since 2019 | Covered |
| Step log | Holds and releases logged; investigation in a shared AP mailbox | Partial: the middle is outside the system |
| Supporting documents | Scanned to a shared drive by invoice number | Partial: linkable by number, not attached |
| Release authority | Manual releases need a reason code since a 2023 policy change | Covered from 2023, missing before |
| Document versions | PO changes overwrite the original | Missing |
| Final outcome | Credits reference the original voucher | Covered |
This is not a weak company. It has ERP records back to 2019: three evidence items are covered, two more can be linked by invoice number, release authority is covered only from 2023, and one item, PO revisions, is missing. The profile tells SourceX where to look, and tells the owner what to expect.
Describing the gap honestly in an introduction
The goal is a short, accurate note, not a sales pitch. Three rules help:
- Name the gap, the years it affects, and who knows more. "Manual releases before 2023 have no reason code; the AP manager can explain the policy change."
- Separate missing from unconfirmed. "PO revisions are overwritten" is a gap. "Supplier terms have not been reviewed" is an open question.
- Do not estimate usable volume. Gaps change what share of the records can be used, and only SourceX's review can measure that.
A note for the wholesaler might read: "260 staff, ERP since 2019, roughly 1,500 matching exceptions a year. Holds, releases and credits are logged and linked. Investigation sits in a shared mailbox; PO revisions overwrite. Controller and CFO available; CEO can authorize." That is enough for a first conversation and claims nothing the company cannot support.
The company still has to qualify: 50 or more 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. To score a client before writing the note, use the golden trajectories qualification scorecard; for what the company's team prepares later, see the golden trajectories review packet. Background on why AI developers license records like these is in AI companies pay for data, and the broader record family is covered in accounts payable exception handling.
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's gap profile shows logged holds, linked credits and a named executive, even with a gap or two described plainly, register as a partner, check who qualifies, and read the terms before sending your introduction note.