·Fintech Accounting
Defense Tech Accounting in Estonia: What Military-Tech Startups Need From Their Books
Estonia has quietly become one of Europe's densest defence-tech ecosystems: two NATO DIANA test centres, a national defence-industry push, and a wave of dual-use startups raising from specialised defence VCs. The accounting that supports this is not standard SaaS bookkeeping. Export-control licences must reconcile with invoices, government contracts pay on milestones that stretch across financial years, grants carry audit trails, and investors expect data-room-ready numbers under strict confidentiality. This post walks through what defense tech accounting in Estonia actually involves.
Why is Estonia becoming a defence-tech hub?
Estonia combines three things defence founders care about: proximity to the problem, institutional backing, and a company structure built for reinvestment. NATO's DIANA accelerator network includes Estonian test centres, the government runs a dedicated defence-industry programme, and the border with Russia keeps procurement urgency real rather than theoretical. Add e-Residency, and a founder anywhere in Europe can run an Estonian OÜ fully remotely with €1 minimum share capital.
The tax layer matters just as much for a hardware-heavy, long-cycle sector. Estonian corporate income tax is 22% and applies only to distributed profits: profit retained and reinvested into prototypes, test campaigns, and certification is taxed at 0% until it is paid out. For a defence startup that will not distribute dividends for a decade, that is a structural advantage over classic annual CIT regimes, and it is exactly the kind of detail defence VCs ask about in diligence.
What makes defence-tech accounting different?
The short answer: the paperwork around each transaction is part of the product. Dual-use and military items fall under export-control rules, which means licences, end-user certificates, and documented end-use statements sit alongside ordinary invoices. Your bookkeeping has to be able to tie a specific sales invoice to a specific licence and a specific declared end user, because that is the trail an export-control audit follows. A generic bookkeeper who files the invoice and discards the context creates compliance risk that surfaces years later.
In practice this means the chart of accounts and the document archive are designed together: controlled-item revenue is separated from unrestricted revenue, licence references are recorded on the transaction level, and the monthly close includes a check that shipments, licences, and invoices reconcile. It is not exotic accounting, but it is disciplined accounting, and the discipline has to start before the first controlled sale, not after.
How do long government procurement cycles change revenue recognition?
Government and defence-agency contracts rarely pay on delivery of a single product. They pay against milestones: design review passed, prototype accepted, trial campaign completed, batch delivered. A contract signed this year may produce cash and recognisable revenue over three or four financial years, and the two rarely move together. Milestone prepayments arrive before the work is done; acceptance-based payments arrive long after the cost was incurred.
The accounting answer is percentage-of-completion or milestone-based revenue recognition with honest work-in-progress balances, plus a cash-flow model that survives a slipped acceptance date. This is where defence startups most often need help: the annual report to RIK is mandatory in Estonia, and an auditor or an investor reading it will immediately ask how contract revenue was recognised. Getting the policy right in month one is far cheaper than restating in year three.
How should grants and MoD contracts be booked?
Most Estonian defence-tech startups stack several public funding sources: national defence-industry grants, EAS and Enterprise Estonia instruments, European Defence Fund consortium work, and direct ministry-of-defence development contracts. Each comes with its own eligible-cost rules, reporting periods, and clawback conditions. The books need cost-centre accounting per grant, so every salary hour and component purchase charged to a project can be evidenced in a funder audit.
Two habits keep this clean. First, book grant income against the matching costs in the right period rather than as a lump when cash lands, so margins per project stay truthful. Second, never let grant-funded and commercially funded work share an undivided cost line: co-funding percentages are recalculated during audits, and a blurred allocation is how startups end up repaying money they properly spent.
What should you expect from an accounting partner on confidentiality?
Defence work raises the bar on who sees your numbers and your counterparties. Contract values, customer names, and shipment details can themselves be sensitive, and some prime contractors impose confidentiality terms on every vendor in the chain, including your accountant. Expect your accounting partner to sign contract-specific NDAs, restrict access to named staff, keep data in EU-hosted systems, and understand that "who is the end customer" is sometimes a question they should not put in an email.
This is a real selection criterion, not a formality. An accounting firm that already works with fintech AML obligations and regulated clients is used to handling need-to-know information and documented access control; a general practice that forwards ledgers over unencrypted channels is a diligence finding waiting to happen.
What do defence VCs expect in investor reporting at seed and beyond?
Defence-focused funds underwrite long sales cycles, so they scrutinise the numbers that prove you can survive them: monthly burn rate, contracted-versus-pipeline revenue, milestone schedules with cash dates, grant dependency ratio, and runway under a "procurement slips six months" scenario. From seed onwards, they expect investor-ready books: monthly closes that are data-room-ready, ESOP accounting and TSD payroll filings handled correctly, and clean separation of R&D spend for both grant reporting and the equity story.
This is the layer TechAccounting builds for tech companies in Tallinn and remotely across the EU. The Accounting package at €499/month covers the full monthly close, payroll and TSD, and RIK annual reporting; Compliance at €1,500/month adds contract, grant, and export-documentation discipline for companies selling to governments; and a €150/hour consultation is the fastest way to sanity-check a contract's revenue-recognition treatment before you sign it. If your cap table includes a defence VC, your books are part of the product you are selling. Treat them that way from day one.