Hi HN,

I’m Tanin. For about four years, I worked on the Revenue Recognition and Analytics teams at Stripe. Today, I'm open-sourcing Book of Revenue, a self-hosted revenue engine and drop-in alternative to Stripe Revenue Recognition (with optional support for Metronome).

### The Problem:

Most founders track MRR or cash collected in Stripe and assume that reflects revenue. But cash collected isn't revenue, and MRR isn't an accounting metric. Once you hit scale, raise institutional capital, or prep for an audit, ASC 606 / IFRS 15 rules kick in:

- Annual upfront subscriptions must be amortized monthly as deferred revenue.

- Mid-cycle upgrades, prorations, usage overages, refunds, and disputes quickly turn into messy manual spreadsheets.

- Finance and engineering end up arguing because Stripe dashboard numbers never match QuickBooks or NetSuite during month-end close.

### What Book of Revenue Does:

- Automated Revenue Recognition: Computes GAAP/IFRS-compliant revenue schedules from your Stripe billing and payment events out of the box.

- Unified Financial Truth: Aligns founder analytics with your accountant’s ledger so both sides look at the exact same numbers.

- Full Data Ownership: Self-hosted with no vendor lock-in. You retain complete custody of your customer financial records and intermediate data models.

### Looking for Early Users:

I’m looking for early design partners—particularly companies processing over $100k in annual volume who dread month-end reconciliations.

I'm offering free hands-on deployment and a complimentary audit of your current Stripe/Metronome billing architecture. If you’d like to test it out, drop a comment below or email me directly at tanin@bookofrevenue.com.

Website: https://bookofrevenue.com

GitHub: https://github.com/tanin47/book-of-revenue

Show HN: Open-source revenue recognition and analytics for Stripe and Metronome