How to review sales contracts for revenue recognition terms with an AI agent

Revenue accountants need a short list from each contract: what was promised, the price and how it can change, when control passes, and any exit or refund rights. The agent reads every signed contract and amendment, extracts those clauses, checks them with your standard terms and drafts an accounting memo. The revenue accountant makes the judgements and approves the memo.

What is this review for, and who owns it?

Revenue standards turn on contract terms. Whether a set-up fee is earned at the start or over the contract, whether a licence is recognised at once or over time, whether a volume rebate reduces revenue now: each depends on specific clauses, often buried in schedules or side letters. Finance usually sees contracts late, after sales has closed them, and reviews only the large ones.

The revenue accountant or technical accounting team owns the conclusions. Legal owns the contract. Sales owns the relationship and often the non-standard terms. Whether an agent can handle revenue recognition depends on getting this reading right; the schedules that follow, as in preparing revenue recognition schedules, are only as good as the memo.

What does the agent prepare?

1. Agent, depth 1: collects the full contract. The executed agreement, order forms, statements of work, amendments and any side letters, linked to the customer and deal record.
2. Agent, depth 1: extracts revenue-relevant terms. Deliverables and services; licence terms; prices and how they are split; discounts, rebates, credits and penalties; acceptance clauses; payment terms; rights of return or refund; termination for convenience; renewal and price change clauses; exclusivity or most-favoured terms.
3. Agent, depth 1: compares with your standard. Clause by clause against the approved template, listing every deviation.
4. Agent, depth 2: drafts the memo. Proposed performance obligations, a draft allocation basis, timing for each obligation and the clauses that create variable amounts, each with the clause reference and the question the accountant must answer.
5. Person, revenue accountant: makes the judgements. Confirms or changes each proposal and records the reasoning.
6. Person, technical accounting lead: reviews non-standard contracts. Above a value or with unusual terms.
7. Agent, depth 1: watches for changes. New amendments or side letters on the same customer trigger a fresh review.

What does the accountant approve?

The accountant approves the conclusions: the obligations, the allocation, the timing and the estimate of variable amounts. These are judgements under the revenue standard, and auditors will ask who made them and why. The agent's draft is a starting point, never the conclusion; each proposal shows the clause it rests on so the accountant can check it quickly.

Signed versions only. Evidence: signature status and version for each document.

Clause references. Every extracted term links to its clause. Evidence: references in the memo.

Deviation list. Evidence: the comparison with the standard template.

Approved memo. Evidence: the accountant's approval and any changes from the draft.

What does an extracted term look like?

Take an illustrative three-year software contract. The agent finds a set-up fee of 50,000 billed on signature; a clause letting the customer terminate after year one with ninety days' notice and a refund of prepaid fees; a 10,000 service credit if uptime falls below an agreed level; and payment terms of 120 days against a standard of 30. The memo proposes that the enforceable term may be one year rather than three, that the set-up fee may need to be spread rather than recognised up front, that service credits are variable consideration, and flags the long payment terms. The accountant decides each.

Where does it usually go wrong?

Side letters outside the system. A sales director agrees extra rights in an email or a letter that never reaches the contract repository. The agent can only read what it is given. Make sales confirm, at booking, that no other documents exist.

Unsigned versions. The repository holds the last draft, not the executed copy. The agent should check signature status and stop if it is missing.

Payment terms ignored. Long payment terms affect cash and can affect revenue measurement. They also drive days sales outstanding. The agent should flag terms beyond your standard.

Compliance mixed with accounting. Reviewing a contract for legal or regulatory compliance asks different questions; see whether an AI agent can review contracts for compliance. Keep the capabilities apart so each memo has one purpose.

Bundled renewals. A renewal signed together with an upgrade at a discount may change the allocation for the remaining term. The agent should treat a renewal with new products as a modification for the accountant, not as a simple extension.

Purchasing contracts. The same reading skills apply to supplier contracts before signature, covered in reviewing supplier contract terms before signature, but the questions there are about cost and risk, not revenue.

What should you measure?

• Contracts reviewed against contracts signed.
• Proposals changed by the accountant, by type.
• Side letters or amendments found late.
• Audit adjustments on revenue.

Where Pryme fits

In Pryme, collecting documents, extracting terms and drafting memos are separate capabilities, certified through Attest on your own past contracts and the memos your accountants wrote for them. Executed contracts arrive as signed sources, and sales notes as declared, so the memo shows when a proposal rests on something other than the contract. Every memo and approval is filed. The finance bounds are in AI agents for finance.