·Fintech Accounting
SaaS Startup Accounting in Estonia: From MRR to Investor-Ready Books
SaaS accounting is where the numbers founders pitch (MRR, ARR, net revenue retention) meet the numbers the law requires (recognised revenue, deferred revenue, VAT). For an Estonian OÜ selling software subscriptions across the EU and beyond, getting the two sets to reconcile is not optional: it is what a seed+ investor checks first in the data room. This post covers why your Stripe dashboard is not your income statement, how annual prepayments create deferred revenue, which VAT regime applies to B2C versus B2B digital sales, and the metrics package venture investors expect a funded SaaS company to produce every month.
Why is MRR not the same as recognised revenue?
MRR and ARR are operating metrics: they answer the question "what is the current run rate of our subscriptions?". Recognised revenue answers a different question: "how much service did we actually deliver this period?". A customer who signs a €12,000 annual contract in January does not generate €12,000 of January revenue. The service is delivered over twelve months, so the books show €1,000 of revenue per month, regardless of when the cash landed. Booking the full invoice as revenue on day one overstates growth, inflates gross margin, and produces an income statement that no diligence team will accept.
For a VC-funded startup this distinction is not academic. At seed and Series A, investors routinely ask for a bridge between the metrics deck and the statutory accounts. If MRR in the pitch says €40k and the ledger cannot reproduce that figure from recognised subscription revenue, every other number in the deck becomes suspect. Clean SaaS accounting means the metrics and the books are two views of the same underlying revenue schedule, not two separate spreadsheets maintained by two different people.
How does deferred revenue work for annual prepayments?
When a customer prepays a year upfront, the cash arrives immediately but the obligation to deliver stretches twelve months forward. The correct treatment is to record the unearned portion as deferred revenue, a liability on the balance sheet, and release it to the income statement month by month as the service is delivered. A SaaS company with strong annual-prepay motion will show a large deferred revenue balance: that is a feature, not a bug. It tells an investor that customers commit for a year and that future revenue is already contracted.
The trap is conflating cash with revenue when modelling runway. Annual prepay improves cash position dramatically while recognised revenue stays flat, which is exactly why burn and runway must be computed from actual cash movements while growth is measured on recognised or committed revenue. We set up the deferral schedules so that both views come out of the same ledger: cash for the runway model, recognised revenue for the P&L, and contracted ARR for the board deck.
What VAT applies when an Estonian OÜ sells SaaS across borders?
The rule set depends on who buys. For B2C sales of digital services to consumers in other EU countries, VAT is due in the customer's country at that country's rate, and the practical way to handle it is the EU One Stop Shop (OSS): one quarterly OSS return filed through Estonia instead of VAT registrations in every member state. For B2B sales to VAT-registered EU businesses, the reverse charge applies: you invoice without VAT, the customer self-accounts in their country, and you report the transaction in your EC sales listing. Domestic Estonian sales carry the standard Estonian VAT of 24%.
Sales outside the EU are generally outside the scope of EU VAT, though local digital-tax regimes (UK, Norway, some US states' sales taxes) can create separate registration duties as volume grows. The operational point: your billing system must capture customer country and VAT status at checkout, because the invoice logic and the reporting obligation are decided at that moment. Our SaaS and digital-services VAT practice covers OSS registration, place-of-supply analysis, and the quarterly filings, so the founder never has to become a VAT specialist.
How do you reconcile Stripe payouts to the ledger?
Stripe, Paddle and similar processors pay out net amounts: gross charges minus processor fees, refunds, disputes and currency adjustments. The most common SaaS bookkeeping error we see is booking the net payout as revenue. That understates gross revenue, hides payment costs that belong in cost of revenue, and makes gross margin unmeasurable. The correct pattern is to book gross charges as revenue, fees as an expense line, and refunds and chargebacks as contra-revenue, then reconcile the resulting balance to the actual bank payout every month.
At any real transaction volume this reconciliation has to be automated: processor reports imported into the ledger, mapped to revenue categories, and tied to the deferral schedule. A monthly close that includes a completed Stripe reconciliation is one of the quiet signals of a well-run SaaS company, and it is one of the first things a diligence team samples.
Which metrics do VCs expect in a seed+ data room?
By the time a SaaS company raises a seed round or later, investors expect a standard metrics package: net revenue retention (NRR), gross margin, CAC payback, and burn multiple (net burn divided by net new ARR). Every one of these depends on accounting choices. NRR requires cohort-level revenue schedules. Gross margin requires COGS to be defined consistently: hosting, third-party API costs, payment processing and customer support in; R&D and sales out. Burn multiple requires a clean cash burn figure that is not distorted by one-off items or prepayments.
This is why we treat investor reporting as an accounting deliverable, not a founder side project. A funded SaaS client gets a monthly close that produces the P&L, the deferred revenue rollforward, burn and runway, and budget versus actual, in a format that can go straight into the board pack and, later, into the Series A data room. When the diligence request list arrives, the answers already exist.
Why run a SaaS startup on an Estonian OÜ, and who keeps the books?
Estonia remains one of the most efficient bases for a SaaS company. Corporate income tax is 22% and is charged only on distributed profits: profit retained and reinvested in product and growth is taxed at 0% until it is paid out, which suits venture-backed companies that reinvest everything. An OÜ takes €1 of minimum share capital to found, e-Residency lets foreign founders run it fully remotely, and the annual report to RIK keeps the company in good standing. The compliance obligations are real but light, provided the bookkeeping behind them is done monthly, not rescued annually.
TechAccounting works specifically with tech companies: SaaS revenue recognition, OSS VAT, processor reconciliation, ESOP payroll via TSD, and investor-grade monthly reporting are the day job, not an exception. Fixed-fee packages start at €499 per month for accounting, with compliance and fintech/AML tiers for regulated businesses, and consultations at €150 per hour. If your metrics deck and your ledger currently disagree, that is exactly the gap we close.