What is revenue recognition automation?
Revenue recognition automation is software that calculates when revenue from sales should be recognised in the P&L, builds the deferred revenue schedule and then drafts the monthly recognition journal for review and approval by the finance team. Without such software a finance team must do this manually in a spreadsheet.
What revenue recognition automation is
Revenue recognition automation is the use of software to calculate and post revenue when it is earned, rather than in the period it is invoiced.
The manual version is creating a spreadsheet using excel formulas to calculate balances. As the number of contracts, mid-term changes and part-months grows, it becomes much harder for an accountant to accurately calculate the correct balances and audit the spreadsheet.
Revenue recognition automation replaces the spreadsheet and automates the posting of journals, not the accounting judgement behind it.
The term covers two fairly different jobs, and it is worth knowing which one you are shopping for.
Which kind of revenue recognition software do you need?
Revenue recognition software splits into two categories that share a name and solve different problems.
Schedule-led tools automate straightforward revenue recognition where a contract is recognised over a defined period. They take the contract value and service period, calculate the monthly recognition in line with your accounting convention, build the schedule and post the journal.
Standards-led revenue engines exist for complicated revenue recognition judgements, for example, where there are separate performance obligations, variable consideration or contract modifications.
The distinction matters commercially. A standards-led engine is a heavier, more expensive implementation, and buying one to mostly release revenue evenly over time is overkill. Going the other way, a schedule-led tool will not save time if you regularly need to identify complicated performance obligations and no amount of configuration will change that. Work out which problem you actually have before you sit through a demo.
How a deferred revenue schedule is posted automatically
Take a ÂŁ24,000 annual software subscription, net of VAT, invoiced on 1 April for the twelve months to 31 March.
When the invoice is raised, none of it is revenue yet:
- Debit Accounts Receivable ÂŁ24,000
- Credit Deferred Revenue ÂŁ24,000
Recognition software then automatically generates twelve monthly releases of ÂŁ2,000 and posts, at each month end:
- Debit Deferred Revenue ÂŁ2,000
- Credit Revenue ÂŁ2,000
The software automatically tracks the balance each month in a schedule. After the April journal, the deferred revenue balance sits at ÂŁ22,000, and revenue for the month carries ÂŁ2,000. By 31 March the deferred balance for that contract is nil.
Software ensures you don’t do this manually, but it also saves time and reduces errors by automating more complicated examples like those below:
- Part months. A contract starting on 12 April either prorates April to 19/30ths of a month or shifts the first full release to May. The method of recognition matters less than applying the same convention every time. The software knows how you treat revenue and automatically applies the correct treatment every time.
- Mid-term changes. An upgrade closes the original schedule at the change date and starts a new one for the revised value over the remaining term. Editing the original in place is what makes prior periods stop agreeing. The software can automatically create a new, accurate schedule in seconds in response to changes.
- Cancellations and refunds. The software will automatically stop releasing, clear the remaining deferred balance in the period the contract ends, and use the credit note to adjust the schedule.
- Non-straight-line contracts. Revenue should be recognised as performance obligations are met, but these may not be uniform. Revenue may need to be released based on delivery, project milestones or product usage etc. These need their own schedule, not a twelfth each month.
Deferred revenue and accrued revenue are not the same thing
Both sit between billing and delivery, in opposite directions. Getting them the wrong way round puts a liability where an asset belongs.
| Deferred revenue | Accrued revenue | |
|---|---|---|
| What happened | Billed ahead of delivery | Delivered ahead of billing |
| Balance sheet | Liability | Asset |
| Initial journal entry | Debit cash or accounts receivable, credit deferred revenue | Debit accrued revenue, credit revenue |
| What clears it | Delivering the service | Raising the invoice |
| Typical case | Annual subscription paid up front | Work done in the last week of the month, invoiced in the next |
Schedule-led revenue recognition software is aimed at the deferred side, because that is where the schedules live. If you need to automate accrued revenue, the same automation tools used for accrued costs can usually handle this too.
Where revenue recognition sits in the month end
You cannot post deferred revenue journals until invoicing has finished. Every invoice for the period needs to be raised and coded before the schedules are complete, or the following month starts with a catch-up release nobody is expecting.
A workable sequence is: close invoicing, check that every invoice hitting a deferred revenue code has a schedule attached, post the recognition journals, then reconcile the deferred revenue balance to the total of the open schedules. Only then does revenue in the P&L mean anything, which matters because variance review and consolidation both sit downstream of it.
Why deferred revenue schedules stop reconciling
The total remaining across every open schedule should equal the deferred revenue balance in the general ledger at the same date. When it does not, the cause is almost always one of four things:
- An invoice coded to deferred revenue that was never added to a schedule.
- A recognition journal posted at a different value to the schedule, usually after a manual edit.
- A schedule amended after the journal was posted, so prior periods no longer agree.
- A credit note applied to the invoice but not reflected in the schedule.
Reconciling monthly keeps each of these to one period’s worth of investigation. Leaving it until year end turns the same four causes into a search across twelve months of postings, and this is the single best argument for putting a deferred revenue schedule somewhere other than a spreadsheet.
What to look for in revenue recognition software
Beyond building the schedule, the questions worth asking of any revenue recognition tool:
- Is it schedule-led or standards-led, and does that match the contracts you actually sell?
- Does it post the journal back to your accounting system, or only produce a file to import?
- Can it handle part-months, milestones and usage alongside straight-line contracts?
- What happens on an upgrade, downgrade or cancellation mid-term?
- Does it reconcile the schedule total to the general ledger balance, or leave you to do that separately?
- Can someone other than the preparer review a period before the journals are posted?
- Does it keep an audit trail of what changed, when, and who approved it?
The last two matter more than they look. A tool that posts faster but removes the review step moves the risk rather than reducing it.
Keeping revenue codes consistent across a group
In a multi-entity group, recognition only aggregates cleanly if every entity uses the same account codes. When one entity books to 2200 Deferred Income and another to 2205 Deferred Revenue, the group balance has to be mapped before it can be consolidated and reported, each month. Aligning the codes first saves even more time at group level, and it is a large part of why chart of accounts automation tends to come up in the same conversation.
How Mayday handles deferred revenue schedules
Mayday’s revenue recognition software is schedule-led. It reduces the manual work involved in recognising revenue over time, so finance teams create deferred revenue schedules, review what is due to be released in the period, and post the recognition journals from one place at month end, rather than rebuilding a spreadsheet each cycle.
It is worth being clear about the edges. Mayday is not invoicing or billing software, and it is not a standards-led revenue engine: if your contracts need allocating across performance obligations under IFRS 15, that judgement sits outside the tool. It also does not recognise revenue without you. Schedule creation and journal posting are handled for you; review, validation and approval stay with the finance team, which is where they belong.
If you’d like to see how Mayday could take your deferred revenue schedules off a spreadsheet, sign up for a 30 day no-card free trial today or book a demo with one of the team.