This scorecard belongs to the guide on golden trajectories in an ordinary workflow, which follows one invoice exception from mismatch to posting. That guide explains what a golden trajectory is. This page turns it into a short scoring exercise an introducer can run with a controller or AP manager, using only answers, never files.
Three gates to clear before scoring
A gate is pass or fail. If any gate fails, stop scoring: the records may be excellent, but the company cannot be introduced yet.
| Gate | Passes when | The question that settles it |
|---|---|---|
| Size | 50 or more full-time employees at peak, contractors excluded | "What was your full-time headcount at its highest?" |
| Authority | A named executive could authorize a discussion about licensing finance records | "Who would sign off on anything involving the ERP data?" |
| Location and English share | The company is in a covered country; outside the U.S., Canada and the EU, at least 70% of the records are in English | "Where is the company based, and are invoices, notes and approvals written in English?" |
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. The company also needs a documented operating history and rights to license, which the scored criteria below test in more detail.
Six criteria, each scored 0, 1 or 2
Each criterion comes from one discovery question. Ask them in this order, because the first three establish that trajectories could exist and the last three establish that they could be checked.
| Criterion | 2 points: strong | 1 point: borderline | 0 points: weak |
|---|---|---|---|
| 1. Controlled task volume | A task such as a matching hold, credit hold or returns approval happens hundreds of times a year | Dozens a year, or only in one business unit | Rare, or exceptions are fixed before anything is recorded |
| 2. Step logging | Holds, releases, field changes and approvals carry a user and a timestamp in the system | Some steps are logged; the investigation lives in email | Steps are reconstructed from memory or inboxes |
| 3. Verifiable end check | The final state can be checked against records, such as a posted voucher that ties to a receipt | The end is recorded but only as a sign-off | Cases close with "resolved" and nothing to compare |
| 4. Document linkage | Invoice, purchase order, receipt, credit and voucher share references; reversals point to the original | Most links exist; credits or reversals are matched by hand | Each team keeps its own numbering |
| 5. Unbroken history | Five or more years on the same system, or a migration that carried closed documents | Two to four years, or a cutover that kept only open items | Under two years of usable history |
| 6. Rights clarity | The company owns its finance records and no known supplier term limits use of pricing | Supplier or customer terms have not been reviewed | A parent company, client or outsourcer controls the records |
Two of these deserve a note. Step logging is often better than owners expect, because the software enforces it. Oracle Payables, for example, uses predefined hold and release types such as matching hold and release reasons, and an invoice cannot be paid until its holds are released. Where a company has turned on a setting like the one in Dynamics 365 Finance that requires approval before posting an invoice with discrepancies, the approval is a logged step too. The end check is the criterion most often missing: a trajectory is only golden if someone can verify the outcome from the record rather than take it on trust.
Reading the total: strong, borderline and weak fits
Add the six scores for a total out of 12.
| Total | Fit | What it usually means | What to do |
|---|---|---|---|
| 10 to 12 | Strong | Controlled tasks repeat often, steps are logged, endings can be checked, and history runs for years | Introduce the CFO or controller |
| 6 to 9 | Borderline | Trajectories probably exist, but one or two joins, years or rights need confirming | Ask the owner to confirm the weak criterion first, then decide |
| 0 to 5 | Weak | The workflow is interesting but the record is thin | Hold the introduction; note what would have to change |
One override applies: a 0 on criterion 3, the verifiable end check, caps the result at borderline whatever the total. Without a checkable ending, the records describe what happened, not what was right. Appen describes golden trajectories as expert-demonstrated, step-by-step completions with each step annotated with reasoning, used as an imitation signal in early agent training. A sequence nobody can verify does not serve that purpose, however complete it looks.
Three wholesale and trade companies, scored (Illustrative)
All three companies are fictional, and the scores came from a conversation, not from looking at records.
| Criterion | 340-person industrial parts distributor | 210-person medical supplies wholesaler | 160-person specialty contractor |
|---|---|---|---|
| Gates | All pass | All pass | All pass |
| 1. Controlled task volume | 2: about 1,800 matching holds a year | 2: frequent returns approvals | 1: a few dozen change-order holds |
| 2. Step logging | 2: holds and releases logged with users | 1: investigation by email | 0: approvals by email |
| 3. Verifiable end check | 2: voucher ties to receipt | 2: credit memo ties to return | 1: project manager sign-off |
| 4. Document linkage | 2: shared PO references | 1: credits matched by hand | 1: partial references |
| 5. Unbroken history | 1: ERP cutover in 2022 kept open items only | 2: seven years on one system | 1: three years |
| 6. Rights clarity | 1: supplier terms not reviewed | 2: owns records, no limits known | 0: records held by a parent company |
| Total and fit | 10 of 12: strong | 10 of 12: strong | 4 of 12: weak |
The parts distributor and the wholesaler reach the same total by different routes, which is why the criteria matter more than the number. The distributor's history break means only four years may be usable; the wholesaler's email investigations mean the middle of each trajectory may be thin. Both are worth introducing, and both gaps are worth naming. The guide to golden trajectories evidence gaps shows how to describe weak spots honestly.
What the scorecard leaves to SourceX's review
The score is a reason to start a conversation, not a result. It cannot tell anyone how many trajectories pass an acceptance check, whether supplier pricing must be removed, how employee names are handled, or whether any buyer wants this task type. Those are measured in SourceX's review with the company, which is also where an acceptance check gets written down. The golden trajectories review packet lists what the company's team would prepare at that stage.
Partners stay at metadata level throughout: which system, roughly how many exceptions a year, how far back, and who owns the records. They never request exports, screenshots or a sample invoice. Ownership usually splits between the AP team and controller (invoices, holds, postings), the warehouse (receipts) and IT (the ERP); the CEO authorizes a licensing discussion. For the company-level basics, use the company qualification checklist, and the owner can prepare with questions to ask before licensing company data. The difference between a single checked sequence and a reviewed set of examples is explained in what a golden dataset is, and agent trajectory data covers the wider category.
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 clears the three gates and scores 10 or more with a verifiable end check, register as a partner, confirm the details on who qualifies, and read the terms before you introduce the controller's executive sponsor.