Estonian e-invoices, integrations and simpler bookkeeping

Enter company details once and review the same company and period in the dashboard, financial reports and annual-report prefill. An external integration is usable only after access, authorisations and tests are confirmed.

Reviewed 13 November 2026

An e-invoice is not a PDF sent by email

XML export exists; operator delivery is not enabled

A PDF is for people to read. An e-invoice contains machine-readable data for the recipient's system. MinuTulu can export an invoice XML file. A file alone does not prove that an operator accepts it or that the recipient has received the invoice.

Before connecting an operator, verify seller and buyer registry codes, VAT details, invoice number, dates, IBAN and line totals. A credit note must reference its original invoice. Operator delivery needs its own send log, duplicate-send protection and acknowledgement.

The next step is to agree an operator, access rights and a test environment. Never send an API secret in chat or include it in an invoice. Until test delivery is confirmed, use the existing PDF or XML checked against the recipient's instructions.

Use bank imports for reconciliation, not duplicate revenue

File import and manually reviewed matching

Import a statement for the correct company in a supported format. Check dates, currency, row count and duplicates. A file import is not a direct bank connection and does not authorise payments from an account.

An issued invoice is the source of accrual revenue; its payment is a cash movement. They are not added together as two sales. Match incoming funds to the correct company's invoice and outgoing funds to the correct expense. Different amounts, currencies and partial payments require review.

The sum of bank movements is not automatically a closing balance. Opening balance, statement completeness and account scope must be known. The dashboard links to source rows and a CSV export for review.

From monthly checks to annual reports without duplicate entry

Shared company and period financial overview

Select the same company and reporting year. Issued invoices, confirmed expenses, recorded employer payroll costs and posted manual ledger adjustments form a preliminary result. Draft invoices and unreviewed OCR values are not confirmed revenue or costs.

The annual-report questionnaire is prefilled from these sources. A manually confirmed answer, including zero, remains unchanged. The system does not invent missing bank balances, assets, loans or share capital. Confirm them using source documents or the ledger.

Before completion, review receivables, payables, stock, depreciation, payroll, equity and the comparative period. A calculated summary is not a final statutory annual report or a board approval. Specialist work and its price require a separate agreement.

VAT source data and readiness for EMTA reporting

VAT source overview exists; automatic EMTA filing is not enabled

The normal Estonian VAT reporting period is a calendar month, with the general deadline on the 20th of the following month. An exceptional period approved by the tax authority must be handled separately. MinuTulu's monthly view compares calculated invoice output VAT and input VAT requiring review.

Input VAT on a document does not automatically mean full deductibility. Private expenses, mixed use, foreign transactions, reverse charge and other special cases need substantive review. A MinuTulu overview is not marked as a filed return.

An EMTA connection requires service-specific access, authorisations and testing. X-Road, XBRL GL and annual-report filing in the Business Register are separate technical workflows, not one universal API. The presence of a configuration key cannot demonstrate support for a new reporting format.

Ask about an integration or report