Golden trajectories review packet: seven tabs a finance team fills in before its exception history is reviewed

Short answer

A golden trajectories review packet is seven short tabs that describe a company's invoice exception history well enough for SourceX to judge it, using metadata the finance team already has. The tabs run in order: task specification, starting state, allowed actions, action log fields, acceptance check, volume and span, and rights and sensitivity. The controller owns most of it; the ERP administrator fills in two tabs, and the finance systems lead and counsel one each. No invoice, voucher or supplier record goes in.

Visual briefFull-size diagram
Seven tabbed sheets, from task specification to rights and sensitivity, rise one at a time into a binder labelled description only, with the acceptance check tab highlighted as written in advance.
Illustrative packet for a fictional distributor's invoice exceptions. The binder describes the records; no invoice or voucher is inside.

This packet is part of the guide to golden trajectories in an ordinary workflow, which follows one invoice exception from mismatch to posting. That guide shows what a single golden trajectory looks like. This page describes the binder that would introduce a whole history of them, so the owner's team can see the work involved before a review starts.

Contents, tab by tab

Each tab answers one question a reviewer would otherwise have to ask in a meeting. The right-hand column says where the answer normally comes from, so nobody has to invent anything.

TabTitleQuestion it answersPrepared byWhere the answer comes from
1Task specificationWhat job do these records show people doing?ControllerAP procedures
2Starting stateWhat does a case look like when it begins?ERP administratorField list of invoice, PO and receipt lines
3Allowed actionsWhat may each role do to resolve it?Controller, with the warehouse leadAP policy and system role setup
4Action log fieldsWhich steps leave a timestamped record, and where?ERP administratorAudit and workflow settings
5Acceptance checkHow would anyone know a case ended correctly?Controller, reviewed by SourceXWritten fresh, before outcomes are counted
6Volume and spanHow many cases, over how many years, on which systems?Finance systems leadException reports and migration dates
7Rights and sensitivityWhat personal or contractual limits apply?Counsel or CFOSupplier contracts, privacy notices

Tabs 1 to 3 define the task. Tabs 4 and 5 make it checkable. Tabs 6 and 7 say how much exists and whether it can be licensed.

Tabs 1 to 3: the task, where it starts, and who may act

Tab 1, task specification. One or two sentences, narrow enough to check. For the main guide's case: "Resolve a quantity-received matching hold so the invoice posts for what was received, or is credited for what was not." A broad task such as "handle supplier problems" cannot be tested against records.

Tab 2, starting state. The fields present when the task begins: invoice lines, purchase order lines, receipt lines, and the mismatch between them. Microsoft's documentation for Dynamics 365 Finance describes three-way matching as comparing invoice unit price with PO price and receipt quantity with invoice quantity; tab 2 says which of those comparisons the company's system runs and which fields hold the result. It lists field names, not values.

Tab 3, allowed actions. The menu each role chooses from, with limits:

  • AP clerk: investigate, contact supplier, request credit.
  • Warehouse: record a late or missed receipt, the only role allowed to do so.
  • AP manager: release a hold with a reason code, within a stated amount.
  • Controller: approve posting above that amount.

Authority is part of the trajectory. If the record cannot show that the warehouse, not AP, entered the corrected receipt, a reviewer cannot tell a proper fix from a shortcut. Tab 3 is where the company says how roles are meant to work, so the log in tab 4 can be read against it.

Tabs 4 and 5: log fields and the acceptance check

Tab 4, action log fields. For each step, the fields that record it: user, role, timestamp, hold type, release type, attachment flag. Oracle Payables, as one example, uses predefined matching hold and release reasons, and an invoice cannot be paid until its holds are released; a company on a system like that can usually list these fields quickly. The tab should also say plainly which steps are not logged, typically the investigation, which tends to happen in email.

Tab 5, acceptance check. The test a case must pass to count as golden, written before anyone looks at outcomes. An Illustrative check, all conditions required:

  1. Posted quantity equals received quantity.
  2. Posted unit price is within the company's price tolerance of the PO price.
  3. No hold or variance remains open on the invoice.
  4. No reversal or credit against the voucher within 90 days.

Two cautions belong on this tab. First, a check drafted after looking at outcomes simply describes what happened. Second, the packet should count failures and alternative branches, not only clean wins. Appen describes golden trajectories as expert-demonstrated, step-by-step completions with reasoning annotated at each step, and notes that it collects demonstrations across different solution paths where a task has several. An exception resolved by a supplier credit is a different valid path from one resolved by finding a missing receipt, and both belong in the counts.

Tabs 6 and 7: how much exists and who may license it

Tab 6, volume and span. Rough numbers are fine: exceptions per year by hold type, years of history, and every ERP migration with its date and whether closed documents moved across. A cutover that carried only open items cuts every trajectory that spans it.

Tab 7, rights and sensitivity. Which sensitive data appears (supplier names, negotiated prices, employee identifiers), whether any supplier or customer contract limits use, and who can authorize a licensing discussion. Usually the CFO or controller owns finance records, and the CEO (in an owner-run company, the owner) signs off. This tab lists questions for review, not legal conclusions.

The company must also 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.

A filled-in contents page (Illustrative)

A fictional 410-person building-materials distributor summarizes its packet on one page. Every figure is invented.

TabSummary entry
1. TaskResolve quantity and price matching holds on stock purchase invoices
2. Starting stateInvoice, PO and receipt lines; match status field
3. Allowed actionsSix actions across four roles (AP clerk, warehouse, AP manager, controller), with a release limit
4. Log fieldsHolds, releases, receipts and approvals logged with user and time; investigation notes in a shared mailbox
5. Acceptance checkFour conditions, drafted by the controller, not yet reviewed
6. Volume and spanAbout 2,400 holds a year; ERP since 2018; no migration
7. RightsSupplier pricing confidential under some contracts; CEO authorizes

The page claims nothing the team cannot support and lists its weak spot, the mailbox, in plain view. That honesty saves time in review.

What stays outside the binder

Partners never assemble packets and never receive invoices, exports or screenshots. Their part ends at metadata: which system, roughly how many exceptions, how far back, and who owns them. Inside the company, nothing in the packet is a record either; the records move only under an agreement with SourceX. What the packet cannot settle: how many cases pass the acceptance check, how supplier pricing is handled, and whether any buyer wants this task type. Those are measured in review.

Before a packet is worth starting, score the company with the golden trajectories qualification scorecard, and describe any weak spots using the golden trajectories evidence gaps analysis. Useful background: what a golden dataset is, why synthetic data rarely replaces real exceptions, whether a company can license its data to AI companies, and what happens after data delivery.

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 controller could fill in these seven tabs from policy and system settings they already know, register as a partner, check who qualifies, and read the terms before introducing the 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

Who should own the packet inside the company?

The controller is the natural owner, because tabs 1, 3 and 5 are finance policy. The ERP administrator fills in tabs 2 and 4, the finance systems lead tab 6, and counsel or the CFO tab 7. The introducer only helps the owner see that the packet exists.

Can the acceptance check be changed after review starts?

It can be refined with SourceX, but it should not be rewritten to fit the outcomes. Writing it first, and recording any later change with a reason, keeps the check honest.

Do failed or reversed exceptions belong in the packet?

Yes, described by count. A history that shows credits, partial payments and reversals alongside clean resolutions tells a reviewer more than one that reports only successes.

Sources

  1. appen.com/agentic-ai-golden-trajectories
  2. docs.oracle.com/en/cloud/saas/financials/25b/fappp/invoice-h…
  3. learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/t…
  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