Revenue recognition for Fintech

Revenue recognition for fintech: platform fees, transactional revenue and amendments under ASC 606

How fintech software companies produce ASC 606 / IFRS 15 revenue schedules in Bunny from the same subscriptions that bill — recurring fees recognised over the term, usage recognised as delivered, amendments recalculated — and sync journal entries to the ledger.

Get a demo Start free

What makes revenue recognition different for fintech software

Software sold to banks, lenders, payment companies and finance teams, where billing is transaction- or volume-based and the buyer expects audit-grade revenue reporting.

  • Mixed performance obligations

    A platform fee recognised ratably, implementation recognised at a point in time, transactional revenue recognised as delivered. Each contract combines them differently.

  • Amendments mid-term

    Rate changes, added products and volume commitments revised halfway through the year all change the remaining schedule. Doing that in a spreadsheet does not scale past a few dozen customers.

  • Auditors want the trail

    Fintech vendors are audited early, often by the same firms that audit their customers. The path from contract to schedule to journal entry has to be reproducible.

  • Multi-entity, multi-currency books

    Revenue recognised by the right entity in the right currency, with the ledger for each entity receiving its own entries.

How Bunny handles revenue recognition for fintech software

  1. 01

    Schedules generated from the subscription

    When a quote is accepted, Bunny creates the revenue recognition schedule from the subscription's charges: recurring charges ratably over the term, usage as it is rated and invoiced.

    Revenue recognition
  2. 02

    ASC 606 and IFRS 15

    Schedules follow the five-step model under ASC 606 and IFRS 15, with performance obligations derived from the charges on the contract.

    ASC 606
  3. 03

    Recalculation on amendment

    A mid-term upgrade, rate change or added product amends the subscription and Bunny recalculates the remaining schedule, so the waterfall reflects the current contract.

    Revenue waterfall
  4. 04

    Deferred revenue from the same data

    Annual-in-advance invoicing creates deferred revenue that unwinds on the schedule; bookings, billings and revenue are reported from one source.

    Deferred revenue
  5. 05

    Multi-entity revenue and ledger sync

    With the Advanced Billing add-on, revenue is recognised per legal entity and currency, and journal entries sync to QuickBooks Online or Xero for each entity.

    QuickBooks integration
  6. 06

    No separate rev rec product

    Revenue recognition runs on the billing data rather than as a separate product with its own integration, so there is no second system for auditors to reconcile against.

    How it is priced

One contract, one schedule, one ledger entry

The reason revenue recognition is painful for fintech vendors is rarely the accounting standard. It is that the contract lives in the CRM, the invoices live in the billing tool, and the schedule lives in a spreadsheet maintained by whoever closed the books last month. Every amendment has to be re-entered in all three.

Bunny’s position is that the subscription is the contract. The accepted quote defines the charges, the subscription bills them, and the revenue schedule is derived from the same object, so an amendment is entered once and every downstream number follows. Journal entries then go to QuickBooks or Xero as a proper revenue subledger rather than as a monthly export.

Revenue recognition for other industries

The same workflow, written up for other kinds of B2B SaaS. Browse all industries.

Free trial

The RevOps expert your team never had.

Bunny's AI agent knows your entire book of business and acts on it — flagging at-risk renewals, chasing overdue invoices, and closing upgrades automatically.
  • Type "send upgrade quotes to all starter plan accounts" — done in seconds
  • At-risk renewals flagged, chased, and closed — before you know there's a problem
  • Overdue invoices collected automatically, without an awkward conversation
Try free for 30 days

No credit card required. Cancel anytime.

FAQ

Frequently asked questions

Does Bunny recognise transactional revenue differently from platform fees?
Yes. Recurring platform or licence fees are recognised ratably over the service period; usage-based transactional charges are recognised in the period they are rated and invoiced. Both come from the same subscription.
What happens to the revenue schedule when a contract is amended?
The amendment updates the subscription and Bunny recalculates the remaining schedule from that point, so deferred revenue and the waterfall reflect the amended contract without manual rework.
Can we recognise revenue per legal entity?
Yes. With the Advanced Billing add-on, each subscription belongs to an entity and currency, revenue is recognised for that entity, and journal entries sync to its ledger in QuickBooks or Xero.
Is revenue recognition a separate product or licence?
No. It is part of the Advanced Billing add-on alongside multi-entity and multi-currency, priced at 0.2% of revenue, and runs on the same subscription data that produces invoices.