AI uses for records
Revenue recognition evidence dataset: linking contract terms to delivery records
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Connect contract terms and delivery evidence by building each revenue task around one performance obligation. Link the contract version and amendments that created it, the delivery or acceptance record showing when control passed, invoices and cash, and the journal entries as finally booked. The answer is the reviewer-approved timing and allocation, and it must reconcile to documents, signing authority and the final financial state.
License terms
Revenue recognition evidence
Key takeaways
- Build each revenue task around one performance obligation and the records that show when it was satisfied.
- Contracts cover what was promised; delivery, receipt and acceptance records show when control transferred.
- Invoice dates and shipping terms are evidence, not the recognition answer.
- Every packet must reconcile to its documents, to signing authority and to the final booked state after corrections.
- Accountants approve links and labels; counsel clears privilege, confidentiality and personal data before records leave finance.
How do you connect contract terms and delivery evidence in a revenue task?
Build each revenue task around one performance obligation. Link the contract version that created it, every amendment that changed it, the delivery or acceptance record showing when the customer obtained control, the invoice and cash records, and the journal entries as finally booked after corrections. The task's answer is the timing and allocation an accountable reviewer approved, and it has to reconcile to every one of those documents.
That structure follows the revenue standard itself. FASB's Topic 606 sets out a five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate it, and recognize revenue when or as each obligation is satisfied. The first four steps live mostly in the contract. The fifth depends on what happened afterwards, which is why a dataset built from contracts alone cannot teach or test the full judgment.
This page describes how finance teams can assemble those links into task packets, whether for internal automation, for evaluating an AI system, or for licensing de-identified records. It is a data method, not accounting advice; the company's accountants decide the policy questions and counsel decides what may leave the company.
Why the contract alone cannot answer when revenue is recognized
A contract tells you what was promised and on what terms, but for an obligation satisfied at a point in time, the recognition date turns on when control transferred. IFRS 15 lists indicators of that transfer: a present right to payment, legal title, physical possession, the significant risks and rewards of ownership, and customer acceptance. Topic 606 lists the same indicators. Each one is evidenced by a different document, often held in a different system.
Shipping terms add a further layer. Under the ICC's Incoterms 2020 rules, the named place of delivery marks where risk passes from seller to buyer, and with the C rules risk passes at shipment even though the seller still pays carriage to the destination. Risk transfer is one indicator among several, so an Incoterms rule on the order is evidence for the revenue question, not the answer to it.
The invoice date is the most common wrong label. Billing can precede delivery, follow acceptance or run on a schedule unrelated to either, and a dataset that treats invoices as revenue events will teach exactly the shortcut a reviewer is trying to catch.
Which documents belong in one revenue evidence packet?
A packet contains every record a reviewer would open to reach and defend the answer, joined by keys that survive export. Fulfillment documents are often the weakest link because they come from logistics, field service or customer portals rather than the finance system.
At a glance
Which documents belong in one revenue evidence packet
Standard business document formats show how these records are meant to connect. In the OASIS Universal Business Language, a Despatch Advice is sent by the despatching party to confirm shipment, a Receipt Advice confirms what the receiving party got and can report shortages or damage, and an Invoice can refer back to the order, the despatch advice or the receipt advice. Most companies do not exchange UBL documents, but their order, shipping and receiving records carry the same references, and those references are the joins a packet needs.
- Contract, order form or statement of work, plus every amendment, with signatories and effective dates.
- The company's revenue policy version applied in the period and any memo identifying performance obligations.
- Fulfillment records: shipment confirmations, proof of delivery, installation or service completion records.
- Customer acceptance or receipt records, including any reported shortage, damage or rejection.
- Invoices, credit memos and the cash application showing which invoice a payment settled.
- Revenue schedule, journal entries and the period-close sign-off, including later corrections.
- Reviewer conclusion: the answer, the documents relied on and who approved it.
The evidence linkage brief, field by field
The brief below is the asset: each row is one link a packet must carry, the keys that make it, and the check a reviewer applies. The last column shows whether counsel, an accountant or both should approve the link before any packet built on it is used outside the finance team. It is an editorial template, version 1.0, to be adapted with your own advisers.
The keys matter more than the documents. Contract IDs, order numbers, shipment IDs and invoice numbers are usually assigned by different systems, and exports often drop the cross-references that let one record point to another. Before building packets, list the systems that hold each link, confirm which field carries the reference, and test a small batch of obligations end to end. Where a reference exists only in free text, such as a PO number typed into an invoice memo, record how it was matched and treat the match as weaker evidence than a system-held reference.
| Link | Records and keys | Reviewer check | Approved by |
|---|---|---|---|
| Contract to obligation | Contract ID and version, clause or line reference, obligation ID | Each obligation traces to signed text in force on the relevant date | Accountant; counsel for ambiguous terms |
| Amendment to obligation | Amendment ID, effective date, obligation IDs affected | Modification is reflected before the delivery it affects | Accountant and counsel |
| Obligation to fulfillment | Obligation ID, shipment or service record ID, timestamp, quantity | Delivered quantity and date match the obligation, not just the order | Accountant |
| Fulfillment to acceptance | Shipment ID, receipt or acceptance record ID, exceptions reported | Acceptance terms are met or shown to be a formality, with evidence | Accountant; counsel if acceptance is disputed |
| Acceptance to invoice | Invoice ID, referenced order, shipment or receipt IDs | Billing is linked but not used as the recognition date | Accountant |
| Invoice to cash | Payment ID, cash application record, invoice ID | Collection pattern does not contradict the contract's validity or price | Accountant |
| Obligation to journal entry | Entry ID, period, account, obligation ID or schedule line | Recognized timing and allocation match the reviewer conclusion | Accountant |
| Correction to final state | Credit memo, reversal or restatement entry IDs and reasons | The label is the final booked state, with the correction history kept | Accountant |
| Packet to release | Packet ID, rights review reference, de-identification log, release ID | Confidentiality, privilege and personal data are cleared for the intended use | Counsel |
Which delivery and acceptance records carry the most weight?
Prefer records created by someone independent of the sales process, at the time of the event, in original form. The PCAOB's audit evidence standard, AS 1105, treats evidence from knowledgeable sources outside the company as generally more reliable than internal evidence, and original documents as more reliable than copies or digitized versions, whose reliability depends on controls over the conversion.
Applied to revenue packets, that gives a working order. A receipt or acceptance record created by the customer ranks highest, followed by a carrier's proof of delivery, then the company's own shipment or completion record from its operational system, and last an email or note from the account team saying the work was done. Packets that rest only on the last kind should be flagged, because they are the cases where an automated system is most likely to learn the wrong signal.
Record the weight in the packet itself. A field showing which kind of evidence supports the delivery date lets a team evaluating an AI system separate cases where the answer was well evidenced from cases where the reviewer made a judgment on thin records.
Does the answer reconcile to the documents, the signers and the books?
Every packet should pass three reconciliations before it is used. The answer reconciles to documents when each fact in the reviewer conclusion points to a record in the packet. It reconciles to authority when the signatories on the contract and on any amendment, credit or concession had the power to agree it, which the company's approval matrix or delegation records show. It reconciles to the final financial state when the recognized amounts by period equal what was booked after every correction.
The third check catches the most problems. Credit memos, returns and late price concessions often post in later periods, and a packet labeled from the first journal entry will disagree with the books. Keep both: the final state as the label and the correction history as context, because the path to the right answer is itself useful evidence for anyone studying where judgments go wrong.
Packets that fail any reconciliation are not discarded silently. Log them with the reason, so the share of excluded cases is visible to whoever relies on the dataset.
Choose which packets to build with the same care. A set drawn only from simple, single-obligation sales will look clean and teach little. Include contracts with several obligations, amendments mid-delivery, partial shipments, rejected goods and periods that close with corrections, and record the selection rule so anyone using the set knows what it does and does not represent.
Worked example: equipment, installation and support in one contract
Illustrative scenario with invented details. A manufacturer signs a contract for 40 units of equipment, on-site installation and twelve months of support. The accountant identifies three performance obligations, with equipment recognized at a point in time, installation when completed and support over the support term. The contract includes a customer acceptance clause for the equipment.
The units ship in two lots under a shipping term that passes risk at the seller's dock. The first lot of 25 units arrives complete; the customer's receiving record reports two damaged units in the second lot of 15. Installation completion records show the work finished six weeks after the second delivery, and the customer signs the acceptance certificate a week later.
The packet links each lot's shipment and receipt records to the equipment obligation, the replacement shipment for the two damaged units to the same obligation, and the acceptance certificate to all three. The reviewer concludes, in this illustration, that the acceptance clause is substantive, so equipment revenue waits for acceptance rather than following the shipping term. That conclusion, the acceptance record it rests on and the accountant who approved it are all in the packet.
The exception is a support renewal signed by a regional manager whose authority under the approval matrix did not cover multi-year terms. The renewal is booked, but the authority reconciliation fails, so the support obligation's packet is held out of the dataset until the finance team documents a ratification.
What to keep out of a revenue task dataset
Exclude anything privileged, and keep customer confidentiality in view. Counsel memos on disputed terms are usually privileged and should never enter a packet; the reviewer conclusion should restate the accounting judgment without quoting legal advice. Customer contracts often restrict disclosure of their terms, so a rights review decides whether contract text can be included, summarized or only referenced.
Signatory names, customer contacts, delivery addresses and bank details in payment records are personal or sensitive information. Replace them with stable pseudonymous IDs that keep the joins intact. Commercial terms that identify a customer, such as a distinctive product list or contract structure, may need generalizing as well. De-identifying a packet reduces privacy risk; it does not give the company a right to license records its customer contracts keep confidential.
Judgments the packet should record but not make
Some questions in every revenue task are policy judgments: whether goods and services are distinct, whether the company is principal or agent, how to estimate variable consideration and whether an acceptance clause is substantive. The packet records who made each judgment, under which policy version and on what evidence. It does not encode a rule of its own, and a model trained or tested on it should be judged against the reviewer's documented reasoning, not against a shortcut inferred from the data.
When packets are used to evaluate an AI system, score more than the final date and allocation. Check whether the system cited the same evidence the reviewer relied on, whether it noticed an acceptance clause or an amendment, and whether it flagged the cases a reviewer would have escalated. A correct answer reached from the invoice date alone is a lucky guess, and the packet structure makes that visible because the supporting links are recorded for every case.
Bring in an accountant before relying on packets from periods with a policy change, a restatement or an audit adjustment, and bring in counsel whenever packets will leave the finance function or the company.
Licensing linked revenue records
Revenue packets that join contracts, fulfillment and outcomes are a kind of operating history SourceX can license directly from a company, taking on sourcing, rights review, contracting, preparation, delivery and payment. The company signs off on scope and terms before any delivery, and SourceX de-identifies the records through approved processing routes.
A short assessment of the company, with nothing uploaded, shows whether its records qualify.
Frequently asked questions
Is the invoice date the same as the revenue recognition date?
Not necessarily. Revenue is recognized when or as a performance obligation is satisfied, which for many sales means when the customer obtains control. Invoicing can happen before delivery, after acceptance or on an unrelated schedule, so a packet should link the invoice without using it as the answer.
Who should review a revenue recognition evidence dataset?
An accountant who knows the company's revenue policy should approve the links and labels, and a finance process expert should confirm the source systems and keys. Counsel should review anything leaving the finance function for privilege, confidentiality and personal data. A data quality reviewer can test that every packet reconciles.
Can a revenue task be built from contracts alone?
Only the first four steps of the five-step model can, and even those depend on amendments being complete. Timing for point-in-time obligations depends on delivery, acceptance and transfer of control, which sit in fulfillment and customer records rather than the contract.
How should corrected or restated entries be labeled?
Label the final booked state and keep the correction history in the packet. A label from the first entry will disagree with the books, while the history shows where the original judgment changed, which is useful context for reviewers and evaluators.
Do shipping terms such as Incoterms decide when revenue is recognized?
No. Incoterms rules allocate costs and the point where risk passes between seller and buyer. Risk transfer is one indicator of control among several, so the reviewer weighs it alongside title, right to payment, possession and acceptance.
Sources
- Topic 606 sets a five-step model (identify the contract, identify performance obligations, determine and allocate the transaction price, recognize revenue when or as obligations are satisfied) and lists indicators of transfer of control. Source
- IFRS 15 paragraph 38 lists indicators of transfer of control: present right to payment, legal title, physical possession, significant risks and rewards of ownership, and customer acceptance. Source
- AS 1105 treats evidence from knowledgeable independent outside sources as generally more reliable and original documents as more reliable than copies or converted versions. Source
- UBL 2.1 defines a Despatch Advice confirming shipment, a Receipt Advice confirming receipt and able to report shortages or damage, and an Invoice that can reference the order, despatch advice or receipt advice. Source
- Under Incoterms 2020 the place of delivery marks where risk transfers from seller to buyer, and under the C rules risk passes at shipment while the seller pays carriage to the destination. Source
See if your company qualifies
A short company assessment. No data uploads are needed.