Before · Without Lunari
A point tool, in isolation.
Evidence lives in an email thread, a shared drive, and a spreadsheet someone owns. When the auditor asks, three people stop their day to assemble the trail.
← Suite · Order-to-Cash
Revenue recognition (ASC 606).
Five steps, applied consistently, evidenced for audit.
Performance obligations, transaction-price allocation, recognition schedules and contract modifications — all derived from the contract data already in the system, not re-entered.
It belongs to Order-to-Cash, but the evidence it produces is visible everywhere — same record at close, in fieldwork, and on the board deck.
One ledger · One evidence trail
Chapter I · The shift
What changes when Revenue recognition (ASC 606) runs on one ledger.
After · With Lunari
A by-product of the work.
Revenue recognition (ASC 606) runs against the same ledger, the same period, and the same identity layer. The evidence is produced automatically — already attached, already signed, already queryable.
Chapter II · What you can do
Features, named plainly.
06 concrete things this capability does — no marketing verbs.
- 01Performance obligation identification with templates
- 02SSP (standalone selling price) library and allocation
- 03Time-based and milestone-based recognition schedules
- 04Contract modifications with prospective and catch-up logic
- 05Variable consideration with constraint testing
- 06Audit-ready disclosure schedules
Chapter III · How it works
Three steps, end to end.
I
Step · 01
Identify
Performance obligations parsed from contract structure.
II
Step · 02
Allocate
Transaction price split using SSP library.
III
Step · 03
Recognise
Schedules drive monthly journals with full traceability.
Chapter IV · Pairs naturally with
Adopt these together — they strengthen each other.
Chapter V · Frequent questions
What teams ask before they switch.
Ready when you are
Try Revenue recognition (ASC 606) on your data.
We onboard a small cohort each cycle. Request a demo and we'll be in touch within two business days.