When you type “tax compliance calendar” into a search box, what you are looking for is, more often than not, a list of dates. What you are actually missing is something else: knowing who is handling each deadline, whether they have handled it and where the proof is. A printed list rings nobody and remembers nothing.
That is why we build the calendar as a working application, not as a spreadsheet. And we say from the start what it is not: it does not know the law. The deadlines, the frequency and the obligations that apply to each company are entered and updated by the accountant. The application makes sure they are not forgotten.
Tax compliance calendar: who writes the deadlines and who changes them
The temptation is to ask for software that “just knows” what you have to file. We do not build that, and we advise you to be wary of anyone who promises it. Obligations differ from one company to another, and the rules change. A wrong deadline, displayed with confidence, is more dangerous than no deadline at all.
In the application, the accountant works with templates: they define an obligation once (name, frequency, a rule for non-working days, steps to follow) and assign it to the companies it applies to. When something changes, they edit the template, and the application shows them which companies are affected and asks them to confirm. Every change stays in the history.
A name, a deputy and three questions for every deadline
A deadline with no owner belongs to nobody. That is why every obligation answers three questions: who prepares it, who checks it, and who takes over if the first person is away. For an entrepreneur with an external accountant, the split is usually simple: you send the documents by an internal date, and the accountant files. The application tracks both halves.
Each team chooses how often messages go out. Too many end up being ignored and help about as much as none, so we start with a few and add more only where the need becomes clear.
- Staged reminders: early on for preparation, then more often as the deadline approaches.
- Internal deadlines: the date by which documents must reach the accountant, separate from the official deadline.
- Escalation: if nobody confirms, the message goes up to the team leader or the director.
- Channels: email, a notification on the phone and, on request, a subscription from the calendar you already use.
Proof of filing, attached where someone will look for it a year from now
An obligation ticked off from memory is not worth much. To close one, the application asks for a document: the filing receipt, the confirmation of receipt, the payment order or other proof the accountant considers suitable. The file stays linked to its deadline, to the company and to the period it relates to.
When a question comes up, from a shareholder, from the bank or during an inspection, the answer is quick to find: what was filed, when, by whom and with what confirmation. Exceptions are noted here too: a correction, a delay and the reason for it.
One accounting firm, dozens of companies, a single screen
For an accounting firm, the difficulty lies in volume. The same obligation recurs across many companies, and the work is shared among several people. The overview shows all the obligations in the chosen period, grouped as you need them: by deadline, by accountant, by status.
If a colleague goes on leave in the middle of the month, the manager filters by their name, sees what they have open and reassigns the tasks, and from then on the new owners receive the notifications. The companies the firm serves can have limited access to their own data: they see which documents are being asked of them, upload them and follow progress.
- Team board: each accountant’s workload for the coming period.
- Company record: the obligations that apply to it, with their history.
- Reports: what was closed on time, what was late and the reason noted.
The technology behind it and the move from spreadsheet to application
We usually write the application in Laravel, a PHP framework well suited to roles, recurring tasks and notifications. Reminders are sent by a scheduler running on the server, so they do not depend on anyone having the application open. For personal calendars we use iCalendar, the format through which Google Calendar, Outlook and other programs can subscribe to an external calendar. They pick up changes at their own pace, sometimes a few hours late, so important alerts are sent from the application, not from the calendar.
Work starts with your current list, whatever it looks like. Together we turn it into templates, the accountant checks them, and then the application runs for a while in parallel with the old method. If you have a single company and few deadlines, an ordinary calendar with alerts, kept with discipline, may be enough.
Frequently asked questions
Does the application update itself when the legislation changes?
No, and that is a deliberate choice. Deadlines and obligations are changed only by the accountant, the person qualified to interpret the rules. The application shows them every company affected by a change and asks for their confirmation.
Can I use the calendar if I have an external accountant?
Yes, and that is precisely the situation in which splitting deadlines into internal and official ones makes the most sense. It is worth discussing with them from the start, because the application changes the way they work too.
What does the price of an application like this depend on?
On the number of roles and companies, on whether there is a portal for the companies served, and on the links with other software. A version for a single company is far simpler than one for a firm with several accountants.
This is a typical project description: it shows how we usually approach this kind of work and does not present a project carried out for a particular client. Every real project starts from your company’s situation, and the stages, timescales and price are agreed after the initial discussion.