How to prepare revenue recognition schedules with an AI agent

Revenue schedules are mechanical once the judgements are made. The revenue accountant decides the performance obligations, the price allocation and the timing for each contract. The agent then builds the schedule, computes monthly revenue, deferred and accrued balances, reconciles billing to revenue and drafts the journal. Contract changes go back to a person before the schedule moves.

What is a revenue recognition schedule, and who owns it?

Many contracts bill on one pattern and earn revenue on another. A software customer may pay annually in advance for a licence, implementation and support, each recognised differently. A construction contract may bill at milestones while revenue follows progress. The schedule sets out, for each contract, how much revenue falls in each period, and the difference from billing becomes deferred revenue (billed, not yet earned) or accrued revenue (earned, not yet billed).

Under modern revenue standards, the main judgements are: what the distinct promises in the contract are, how the price is allocated between them, whether each is satisfied over time or at a point in time, and how to treat variable amounts such as rebates or penalties. The revenue accountant or technical accounting team owns those calls. Whether an agent can handle revenue recognition depends on keeping them with people, within the bounds set out in AI agents for finance.

What are the steps, and who acts at each one?

1. Agent, depth 1: reads contract terms. From the contract review, prepared as in reviewing sales contracts for revenue recognition terms. Scanned contracts are read through optical character recognition and checked against the billing system.
2. Person, revenue accountant: makes the judgements. Performance obligations, allocation, timing and variable consideration, recorded in a contract accounting memo.
3. Agent, depth 2: builds the schedule. Per contract, from the approved memo: revenue by period and obligation, with start and end dates.
4. Agent, depth 1: reconciles billing to revenue. Billed to date, earned to date, deferred and accrued balances per contract, summed and tied to the ledger.
5. Agent, depth 1: watches for changes. Amendments, renewals, cancellations, credit notes and usage data that change the schedule. Each change is sent to the accountant before the schedule is updated.
6. Agent, depth 2: drafts the monthly journal. Revenue released, deferred and accrued movements. Parked.
7. Person, revenue accountant: approves the journal and the schedule changes.
8. Agent, depth 1: produces the deferred revenue roll-forward. Opening, billed, released, closing, tied to the ledger.

Which controls matter, and what evidence do they leave?

Memo before schedule. No schedule without an approved contract memo. Evidence: memo reference and approver on each schedule.

Change detection. Any amendment or billing change not reflected in the schedule is flagged. Evidence: the change log with the accountant's decision.

Tie-out to the ledger. Deferred and accrued balances per schedule equal the ledger balances. Evidence: tie-out each month.

Cut-off. Revenue for services delivered after period end is not released. Evidence: delivery or usage dates against release dates.

Separation. The agent that drafts revenue journals does not raise customer invoices for the same contracts. Evidence: identities on each.

What should you measure?

• Contracts with schedules not matching the memo. Should be zero.
• Changes detected late, after a period has closed.
• Deferred revenue reconciling differences.
• Audit adjustments on revenue.
• Days from close to approved revenue journal.

Where does it usually go wrong?

Billing treated as revenue. A large annual invoice is released in full. The schedule exists to stop this; the reconciliation catches it.

Amendments in email. A customer agrees an extra module or a discount by email, and billing changes but the contract record does not. The agent's change detection should compare billing with schedules, not just contracts with schedules.

Stand-alone prices guessed. Allocating price needs a basis for each obligation's stand-alone value. If the basis is not documented, the agent must not invent one; the accountant sets it.

Variable amounts ignored. Rebates, service credits and usage overages change revenue. The agent should list each contract with variable terms each month so the accountant updates estimates.

Prepayments on the cost side forgotten. The mirror image of deferred revenue is prepaid cost, such as commissions or licences you pay in advance; prepayment amortisation schedules follow the same pattern.

What does a schedule look like for one contract?

Take an illustrative software contract worth 120,000 for one year: a licence, implementation and support. The accountant decides that implementation is a distinct service worth 20,000, recognised as work progresses over the first two months, and that the licence and support, worth 100,000 together, are recognised evenly over twelve months. The customer is billed the full 120,000 at the start. The agent's schedule releases 10,000 of implementation in each of the first two months plus 8,333 of licence and support every month, and shows deferred revenue falling from 120,000 to nil over the year.

Where Pryme fits

In Pryme, building schedules, reconciling billing and drafting journals are separate capabilities, each certified through Attest on your own past contracts. The approved memo reaches the agent as a signed source from the accountant, so a schedule can never rest on the agent's own reading of a contract. Journals are held and every change decision is filed.