A finance function built from nothing

Two revenue models were being recognised differently, controls lived in people’s heads and the group was approaching its first audit.

12 monthsLed and executed by Ravi Raja

One documented revenue policy, a controlled monthly close and the first consolidated audit completed cleanly.

01

Separate the models

Mapped the SaaS and marketplace transaction flows, contracts, billing events and the points at which each revenue stream should be recognised.

02

Create one policy

Documented a single revenue framework, supporting schedules and review evidence so treatment no longer changed with the person answering.

03

Control the close

Established owners, reconciliations, cut-offs and a repeatable monthly close across the group.

04

Prepare for audit

Organised the consolidation and evidence required for the first group audit, with issues resolved through a tracked request list.

The work was managed as a live process, not a final report.

One request and action register

Questions, owners, evidence, decisions and open items stayed in one tracked view.

Current versions available

Working schedules and approved outputs remained accessible rather than being distributed across inboxes.

Exceptions surfaced early

Items that could affect timing, interpretation or the outcome were escalated while there was still time to act.

One documented revenue policy, a controlled monthly close and the first consolidated audit completed cleanly.

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.