Can an AI agent handle revenue recognition?

It can handle the mechanics. An AI agent can read sales contracts, identify what was promised, propose how the price is allocated, build the recognition schedule and draft the monthly journal. The judgements that move revenue between periods, and the approval of each schedule, belong to a revenue accountant who sits outside the sales team.

Which parts are mechanics, and which are judgement?

Revenue recognition under the accounting standard your business follows usually comes down to a sequence: identify the contract, identify each distinct promise in it, set the price, allocate the price across the promises, and recognise each part when it is delivered. Much of that, for a standard contract, is reading and arithmetic.

The judgement sits in a handful of places: whether two promises are distinct, how to estimate variable amounts such as usage fees or rebates, whether the business is acting as principal or agent, how to treat a contract change, and when control actually passes for a bespoke deliverable. These decisions change the revenue figure, sometimes by a lot, and they are where auditors focus.

What may the agent prepare?

• Contract reading. Extract parties, term, price, payment schedule, deliverables, acceptance clauses, renewal and termination terms. For scanned contracts this relies on optical character recognition, so the agent should flag any field it read with low confidence.
• Promise identification. Propose the distinct obligations, citing the clause for each.
• Allocation. Propose an allocation using the standalone prices on your price list.
• Schedule. Build the month-by-month recognition schedule.
• Journal. Draft the monthly entry moving amounts from deferred to recognised revenue.
• Exceptions. Flag any non-standard term: a side letter, an acceptance clause, a refund right, a bundled discount.

All of this is depth 2. The agent drafts; a person approves.

Which step keeps the separation of duties?

The approval of each new schedule, by someone independent of the sale. Sales teams are paid on bookings and often on revenue. A salesperson, or a sales operations team reporting to sales, should not be the one deciding when revenue is recognised. The revenue accountant approves each schedule, and the financial controller approves anything with a judgement flag.

Once a schedule is approved, the agent may post the routine monthly release from it at depth 3, because that release only follows a decision a person already made. Any change to the schedule goes back for approval. The method for this, step by step, is in how to prepare revenue recognition schedules with an AI agent.

An illustrative example

Take a software company that signs a three-year contract worth 360,000. The contract bundles a software licence, implementation services and support. The customer has a right to reject the implementation if it fails acceptance testing.

The agent reads the contract and proposes three obligations. It allocates the price using the standalone prices on the price list, which sum to more than 360,000, so it spreads the bundle discount across all three. It proposes recognising support evenly over three years and implementation as the work is done.

It flags two things. The acceptance clause may mean implementation revenue should wait until acceptance. And the contract's appendix references a side letter offering a free fourth year of support, which is not attached. The revenue accountant requests the side letter, decides implementation revenue waits for acceptance, and approves the revised schedule. The full approach to reading these terms is in how to review sales contracts for revenue recognition terms.

What controls make it safe?

• Contracts from the signed repository. The agent reads executed contracts, not drafts in an email thread.
• Every proposal cites its clause. The approver can check any decision against the contract text.
• Judgement flags route upward. Variable pricing, principal or agent questions and contract changes go to the controller.
• Sales cannot approve. The approver is named and outside sales reporting lines.
• Schedules are versioned. Each change is recorded with its approver and reason.

Where Pryme fits

In Pryme, drafting a schedule and posting a release from an approved schedule are separate capabilities. Attest certifies the agent on your own past contracts, including ones with side letters and acceptance clauses, and the posting capability is bounded to schedules a person has already approved.

The wider controls are in AI agents for finance: books you can audit.