In practice, compliance risk is rarely one missing posting. It is usually a weak routine around evidence, approvals, access and review. A compliance calendar for an Estonian company should therefore combine fixed filing dates with business events: hiring a person, crossing a VAT threshold, paying dividends, starting cross-border sales, taking financing or preparing the annual report.
The useful version is not a decorative calendar. It names the deadline, the document pack, the reviewer, the official rule to check and the decision that has to be made before filing. That is what turns compliance from a last-week rush into a monthly owner control.
Start with the legal trigger and the real transaction flow
Start by separating dates that repeat every month from triggers that appear only when the business changes. For many Estonian companies the recurring dates are simple: payroll and other payments reported on TSD are reviewed before the 10th day of the following month, VAT and intra-Community supply reporting are reviewed before the 20th day, and the annual report is normally due within six months after the financial year end.
- payments to employees, board members, contractors and dividend recipients create cash-basis review points
- VAT status, VAT returns and intra-Community sales need a monthly check when the company is VAT registered
- cross-border sales, marketplace activity and payment-service-provider data should be separated before the return is prepared
- annual report work should start from reconciled monthly balances, not from a June scramble
The calendar becomes useful when every event has an owner. If nobody owns the last review step, the deadline still exists, but the company has no control.
The filing logic depends on clean source data
Each obligation needs its own evidence pack. VAT needs sales and purchase invoices, credit notes, country logic, customer VAT status, marketplace reports and payment-provider reconciliation. Payroll needs employment or board-member data, working time, benefits, reimbursements and the actual payment date. Dividend tax needs the profit-allocation decision, retained earnings check, recipient data, payment date and TSD Annex 7/INF 1 logic.
- keep VAT, payroll, dividend and annual-report evidence in separate folders or workflow states
- record why an exception belongs to the selected month before the return is filed
- check e-MTA and e-Business Register access before the filing week
- store the calculation and approval behind every declaration, not only the submitted PDF
This is where outsourced bookkeeping works or fails. The accountant can prepare the filing, but the owner still has to confirm business facts that are not visible from invoices alone.
Where companies usually misread the risk
Most errors come from treating the calendar as a date list. The real risk sits in the trigger: a new employee was hired, a board-member payment was made, a dividend was paid, EU sales started, a VAT threshold was approached, or a shareholder loan changed the balance sheet. If the trigger is not logged, the filing date arrives with missing context.
- VAT thresholds and cross-border flows are monitored too late, after invoices already went out
- TSD is prepared from payroll numbers, but benefits, board fees or reimbursements are not reviewed
- dividends are discussed as profit distribution, while tax follows the actual payment moment
- annual-report issues are postponed even though they were visible in monthly reconciliations
The warning sign is not that a question appears. Real companies always have questions. The warning sign is that the same question appears every month without a named owner and a stored answer.
How I would build the control routine
I would keep the routine short enough to run every month. In the first working days, collect documents, reconcile bank and payment-provider data, and update the trigger log. Before the 10th, review payments, payroll, benefits, board fees and dividends. Before the 20th, review VAT, intra-Community sales and the evidence behind the return. Once a quarter, check whether cross-border sales or OSS/IOSS logic changed. Once a year, test whether the annual report can be prepared from clean balances.
- use one calendar line per obligation: trigger, deadline, evidence, reviewer, filing system and archive location
- make access checks part of the routine, especially when accountants, board members or e-residents change
- mark items as blocked only when the missing business fact is named
- review the calendar whenever the company adds a sales channel, employee, lender or owner payment
This turns the calendar into a management tool. It also makes service quality measurable: the owner can see what was ready, what was late and which decisions were escalated before filing.
When to check the rule before filing
Do not wait for the filing deadline when the underlying rule is uncertain. Check the official rule before the first affected transaction if the company hires abroad, starts EU sales, pays a dividend, grants or repays a shareholder loan, changes VAT status, adds marketplace activity or prepares an annual report with unusual balances.
- VAT: confirm registration status, taxable period, KMD/VD reporting and place-of-supply logic before invoices are issued
- payroll and TSD: confirm the payment date, recipient status, benefit treatment and Annex requirements before the 10th
- dividends: confirm distributable profit, equity, payment date, recipient data and the 22/78 company-level tax treatment
- annual report: confirm access, category, signatures, notes and approval path well before the six-month deadline
A short written decision is usually enough. What matters is that the basis for filing is visible before the return is submitted.
A practical 30-day implementation plan
Treat the next month as a controlled test. Do not redesign the whole finance function. Build one working compliance calendar and prove that the company can use it.
- week one: list recurring deadlines and business triggers for VAT, TSD, dividends, payroll, annual report and cross-border sales
- week two: assign an owner, reviewer, evidence pack and archive location to each item
- week three: test the 10th and 20th day routines with actual documents and access rights
- week four: review blocked items with the owner and update the calendar before the next month starts
After one cycle, the company should know whether the problem was missing evidence, unclear ownership, weak access control or a service-scope gap.
A useful compliance calendar is not a wall of dates. It is a trigger log with evidence, ownership and review steps that are visible before the deadline week.
Frequently asked questions
When should the owner get involved?
When the question changes tax, cash, reporting, or responsibility. Routine postings can be delegated; unclear business decisions cannot. Related topic: Month-End Owner Review.
Is this only relevant for larger companies?
No. Small companies feel weak routines faster because one missing explanation can block the whole month-end process. Related topic: Accounting for IT Companies in Estonia.
What should be written down first?
Write down the trigger, responsible person, document cut-off, review date, filing system and cases that must be escalated before filing. See also: e-Äriregister decision templates.
Can this be handled with outsourced bookkeeping?
Yes, if the internal owner and the accounting provider agree scope, evidence, deadlines, access rights and communication rhythm explicitly. See also: driving logbook in Estonia.
Official sources
Use these official pages to confirm the current rules before acting:
A good accounting routine should make the next decision easier, not just make the previous month look tidy. If this topic is active in your company, compare it with our accounting services in Estonia or contact us before the next deadline turns a small gap into correction work.