Automated revenue recognition is software that handles the repeatable parts of ASC 606 work. It reads the contract, splits it into obligations, and builds the schedule that sets when revenue enters the books. This post is a how-to: the steps, one worked example, and the checks that keep the output trustworthy. A finance person still owns the judgement calls.
How to set it up
Start with the contract. Put the signed order form, its amendments and the customer record in one place. The software needs the terms in one place before it can read them. If two documents disagree, a person decides which one governs.
List the performance obligations. Each distinct good or service that the customer can use on its own is a separate obligation. A license, a hosting service and a training session may each be its own line, depending on the terms. The software proposes the split and finance confirms it.
Set the transaction price. Take the amount the customer has agreed to pay, net of discounts. Put variable fees into the model when the amount can be estimated, and write down the estimate and the reason for it.
Allocate the price. Spread the price across the obligations in proportion to their standalone selling prices. Where no standalone price exists, the team sets an estimate and records the reason.
Recognize revenue as each obligation is met. A subscription is recognized over the period it covers. A one-time delivery is recognized when the customer takes control of it. The software moves amounts from deferred revenue into revenue as each piece is met.
Worked example: a yearly subscription with a setup fee
A customer signs one order form for a yearly subscription, plus a setup fee, billed up front.
The contract is one record. There are two candidate obligations: the subscription and the setup work. Finance decides whether setup gives the customer anything useful on its own. If it does not, setup folds into the subscription, and a person records that call.
The transaction price is the total invoice less the agreed discount. The software splits that price between the subscription and the setup work, using each one's standalone selling price.
The subscription share is recognized across the service period, one slice at each period end. The setup share is recognized when the setup work is done. The schedule shows the deferred balance falling as each slice posts.
What to check before you trust the output
Read the judgement calls first: the obligation splits and the standalone prices. These drive most of the numbers, and the software cannot know your commercial intent.
Check that the schedule ties back to the contract total. The recognized amounts plus the remaining deferred balance must equal what the customer owes.
Sample a few contracts by hand at each close. Pick the ones with discounts, amendments and setup fees, since those are where the logic breaks first.
Keep the audit trail. Each journal entry should point to the clause or order form that drove it, so an auditor can follow it without asking the team.
What the standard says
ASC 606 and IFRS 15 use the same five-step model. The steps are: identify the contract, identify the performance obligations, determine the transaction price, allocate that price to the obligations, and recognize revenue when each obligation is satisfied (FASB revenue standard). IFRS 15 sets out the same five steps.
The effective dates were staggered. Public companies came first, and private companies had a later start (FASB revenue standard). IFRS 15 took effect for annual periods beginning in 2018 (IFRS 15).
Where it fits in the close
Revenue schedules feed the same close as bank and receivables work. Teams that already run AI bank reconciliation for finance teams can reuse the same ledger checks. For subscription-heavy businesses, the subscription expense auditor covers the spend side of the same contracts.
Verslay's Revenue Analyst handles SaaS revenue and growth analysis. It is the nearest live match for this topic, not a one-to-one fit.
Frequently Asked Questions
How do I automate revenue recognition for subscriptions?
Link the signed contract, the billing record and the ledger. Then let the software build the schedule and draft the entries. A person checks the judgement calls before the entries post.
What is the difference between realized revenue and recognized revenue?
Realized revenue is cash or receivables that have been collected or billed. Recognized revenue is the amount reported on the income statement once the performance obligation has been satisfied under ASC 606.
