Separate the models
Mapped the SaaS and marketplace transaction flows, contracts, billing events and the points at which each revenue stream should be recognised.
Start a conversationTransformation · SaaS & marketplace
Two revenue models were being recognised differently, controls lived in people’s heads and the group was approaching its first audit.
What had to change
How the work moved
Mapped the SaaS and marketplace transaction flows, contracts, billing events and the points at which each revenue stream should be recognised.
Documented a single revenue framework, supporting schedules and review evidence so treatment no longer changed with the person answering.
Established owners, reconciliations, cut-offs and a repeatable monthly close across the group.
Organised the consolidation and evidence required for the first group audit, with issues resolved through a tracked request list.
How execution stayed controlled
Questions, owners, evidence, decisions and open items stayed in one tracked view.
Working schedules and approved outputs remained accessible rather than being distributed across inboxes.
Items that could affect timing, interpretation or the outcome were escalated while there was still time to act.
What changed for the business
Management, auditors and the finance team could work from one revenue treatment and one controlled reporting process.
The value was not only closing the first audit; it was leaving behind a finance function able to repeat the work.
The work stayed with the problem through execution. That is the distinction: the output was not advice about what should happen, but a controlled process that helped make it happen.