The audit committee asks a simple question: are all statutory filings across the group up to date? Group finance opens the compliance calendar. It is a spreadsheet with a tab per country, edited by a dozen people over several years. The status column says "done" for most lines. Nothing shows who checked them, what was filed or whether the payment went out. Two tabs were last touched by people who have left.
Every multi-country group reaches this point. A spreadsheet compliance calendar works for a handful of entities. Take a group with entities in ten jurisdictions, each with VAT or GST, payroll, withholding, corporate tax and annual accounts, some monthly and some quarterly, and the obligations run into the hundreds a year. At that scale the file still looks complete. It has just stopped being reliable.
Why a spreadsheet compliance calendar fails at scale
Status is self-reported. A cell that says "filed" is a claim, not evidence. Nobody can tell from the file whether a return was reviewed before submission.
Evidence lives elsewhere. Acknowledgements, payment confirmations and working papers sit in email, shared drives and local advisers' portals. Pulling them together for an auditor or a buyer takes days.
Nothing escalates. A spreadsheet does not notice that a filing due in three days has not been started. Someone has to look, and the person who should look is often the person who is behind.
Copies multiply. Local teams keep their own versions. Group finance keeps a master. They drift apart.
Rules change faster than the file. New mandates, new thresholds and new deadlines reach the spreadsheet when someone remembers, or when a penalty notice arrives.
Key-person risk. One person often understands the whole file. When they leave, so does the knowledge of which lines matter.
Start with an obligations register
The register is the foundation. Each line is one obligation for one entity, and every field earns its place.
| Field | Example | Why it matters |
|---|---|---|
| Entity and jurisdiction | UK operating company | Obligations attach to legal entities, not to the group |
| Obligation | VAT return, payroll filing, withholding tax return, annual accounts | What has to be done |
| Legal source | Link to the official guidance or statute | Lets anyone check the rule, and shows when it changes |
| Frequency and due-date rule | Monthly, a set number of days after period end | Generates each instance automatically, including holiday shifts |
| Preparer | Local accountant or external adviser | Who does the work |
| Reviewer | Country finance lead | Second pair of eyes before submission |
| Approver | Country head or group tax | Authority to submit and to pay |
| Payment step | Yes or no, with the bank and approver | Filing and paying are separate deadlines with separate risks |
| Evidence required | Submission acknowledgement, payment confirmation, reconciliation to ledger | Defines what "done" means |
| Last checked | Date the legal source was last reviewed | Shows whether the line is still current |
Build the register from the obligations, not from last year's spreadsheet. Ask each country's adviser for a full list per entity, then compare it with what the group has been tracking. The gaps are usually where the risk is.
Owners and maker-checker
Every instance of an obligation should move through the same stages: prepare, review, approve, filed, and, where tax is due, paid. Each stage has a named person, and the preparer and reviewer are never the same person.
When an adviser prepares. Many groups use local firms to prepare returns. That is sensible, but group finance still owns the review. A return prepared outside the company and submitted without anyone inside checking it against the ledger is a control gap.
Filed is not paid. A return filed on time but paid late, or paid to the wrong reference, can still attract a penalty. Keep them as separate stages with separate evidence.
Cover for absence. Each line needs a deputy for the preparer and the reviewer. Deadlines do not move for holidays.
Evidence and the audit trail
Define "done" as evidence attached, not a status changed. For most obligations that means three items: the submission acknowledgement from the authority or portal, the payment confirmation from the bank, and a reconciliation of the return to the ledger.
Store the evidence against the line in the register. When an auditor, a lender or a buyer asks for proof of compliance, the answer is a filtered view rather than a project. It also makes the next filing easier, because last period's working papers are where the preparer expects to find them.
Escalation that reaches the right person
Reminders that go only to the owner fail exactly when they are needed, because the owner is the person who is behind. A ladder sends late items up the line while there is still time.
| Timing | Who is notified | What is expected |
|---|---|---|
| Ten working days before due | Preparer | Start, or confirm the work is under way |
| Five working days before | Preparer and team lead | Draft ready for review |
| Two working days before | Team lead and country head | Review complete, approval scheduled |
| Due date, not filed | Country head and group CFO | Decision on filing, extension or disclosure |
| After due date | Group CFO and, where relevant, the audit committee | Penalty assessment and remedial plan |
The specific days are a design choice; set them per obligation, with longer lead times for annual filings and anything that needs board approval. What matters is that the ladder is written down and runs without anyone remembering to trigger it.
Monitoring change when rules change
A compliance calendar is only as current as its sources. Rule changes alter more than dates: they change formats, systems and who has to do what. Recent e-invoicing mandates show how much moves at once.
| Jurisdiction | Change | What it alters in the process |
|---|---|---|
| Belgium | Between Belgian VAT-liable enterprises, structured e-invoices compulsory from 1 January 2026 for almost every transaction; sales to consumers excluded | Invoice format and sending route for domestic B2B sales |
| Poland | KSeF from 1 February 2026 where a firm's 2024 sales exceeded PLN 200 million, VAT included; everyone else from 1 April 2026 | Invoices issued through a national system; a new rejection step |
| France | From 1 September 2026, every business has to be ready to receive e-invoices, while large companies and ETIs have to issue them; SMEs and micro-enterprises start issuing on 1 September 2027 | Receiving process for every entity, then issuing by size |
| India | Since 1 April 2025, e-invoices more than 30 days old can no longer be reported on the IRP by taxpayers whose AATO is ₹10 crore or more | A hard time limit on reporting, which turns a backlog into a compliance failure |
A routine that keeps up:
Link every line to its source. Official guidance or statute, not an adviser's newsletter alone.
Review sources on a schedule. Monthly for jurisdictions with active reforms, quarterly for the rest. Record the date checked.
Log every change. What changed, from when, which register lines it affects, and who approved the update.
Ask advisers to confirm. Each quarter, ask local advisers to confirm that the register for their entities is complete and current, in writing.
Where AI helps
Watching sources. AI can check official pages for changes and draft a summary of what changed for the register owner. The owner verifies against the source before anything in the register moves.
Mapping changes to obligations. Given a new notice, a model can suggest which entities and register lines it affects, using the register's own fields.
Drafting reminders and status notes. Escalation messages and monthly status summaries for the audit committee, drafted for a person to send.
What it should not do: interpret law, decide whether an entity is in scope, or mark anything as filed. A model can misread a threshold or confuse two similar rules, and in compliance a confident wrong summary is worse than none. Official sources and local advisers remain the authority.
What a compliance calendar will not do
It will not make a return correct. The calendar shows that a filing was prepared, reviewed and submitted on time. Whether the numbers in it are right depends on the ledger, the reconciliation and the reviewer.
It will not replace local advice. Scope, thresholds and interpretation are questions for advisers in each jurisdiction. The calendar makes sure the questions get asked in time and the answers are recorded.
Frequently asked questions
What is a compliance calendar?
A compliance calendar is a schedule of every statutory filing and payment a group owes, by entity and jurisdiction, with due dates, owners and status. For multi-country groups it works best built on an obligations register rather than a spreadsheet.
Why do spreadsheet compliance calendars fail?
They fail at scale because status is self-reported, evidence is stored elsewhere, nothing escalates automatically, copies drift apart and rule changes reach the file late.
What should an obligations register include?
At minimum the entity, the obligation, the legal source, the due-date rule, the preparer, reviewer and approver, the payment step, the evidence required and the date the source was last checked.
How should compliance deadlines be escalated?
On a written ladder tied to working days before the due date, moving from the preparer to the team lead, the country head and the CFO, so a late item reaches someone with authority in time.
How do you keep a compliance calendar current when rules change?
Link every line to its official source, review sources on a schedule, log each change with its effective date and approver, and ask local advisers to confirm the register in writing each quarter.
Can AI manage statutory compliance?
No, AI can watch sources, suggest which obligations a change affects and draft reminders, but people must verify changes against official sources and approve every filing.
Where CFOLogic fits
Our role here is to design and build: compliance views that read from a group's existing systems, read-only by default, where a person signs off anything sent outside the team. CFOLogic is not a CPA firm, so the tax filings themselves go through a partner CPA firm and local advisers. Our Compliance Command Center is a demo built on fictional data: one calendar of statutory deadlines for a manufacturer with UK, India and Vietnam entities, with prepare, review, approve, filed and paid stages and reminders that escalate to the owner, team lead and country head.