Picture a six-person accounting firm with around three hundred clients. Filing deadlines live in a large spreadsheet that one senior accountant maintains, with color codes only she fully understands. Extensions are recorded in email. A client's sales tax filing frequency changed from quarterly to monthly last spring, the notice went to the client, the client forwarded it to a general inbox, and nobody updated the spreadsheet. The first anyone hears of it is a penalty letter.
Most firms have a version of this story, and it usually happens because the list of what each client must file, and when, changes constantly, while the system tracking it depends on one person remembering to update it. The fix is to track obligations and let the dates follow from them.
This article covers how to build a client obligations register, what to decide about internal deadlines, and what an automated deadline system does around Karbon, TaxDome, Canopy, Xero Practice Manager or whichever practice management tool the firm uses.
What missed and near-missed deadlines cost
The obvious cost is penalties and interest, and the awkward conversation about who pays them. Even when the firm absorbs the cost or negotiates relief, the time spent on it is unbillable and the client's confidence takes a knock.
The less obvious cost is how work bunches up. When deadlines aren't visible weeks ahead, client documents arrive late, preparation starts late, and everything converges on the final few days. Staff work evenings, reviews get rushed, and the partner spends time checking the spreadsheet instead of reviewing returns. Near-misses do almost as much damage to a team's morale as actual misses.
Fix the tracking model first
Build a register of obligations
For each client, record what they're obliged to file and pay, along with the dates. That means the entity type, fiscal year end, jurisdictions, and each obligation with its frequency: annual returns, quarterly estimated payments, payroll filings, sales tax returns, information returns and anything else that applies. Record who in the firm is responsible for each obligation and what the firm needs from the client to complete it.
Dates are then calculated from the obligations. When a client's frequency changes or they register in a new state, you update one obligation and every future date adjusts.
Set internal deadlines ahead of statutory ones
For each obligation, set internal milestones: when the document request goes out, when documents are due from the client, when preparation should be finished, and when review should be finished. A statutory deadline is the last possible moment, so the firm's plan should never aim for it.
Put extensions and changes in one place
Extensions, changes in filing frequency, new registrations and closed accounts should be recorded on the obligation itself, with the evidence attached. If they live in email, the rest of the team can't see them.
Clarify client responsibilities
Your engagement letters should say what the client must provide and by when, and what happens if they don't. That gives the automated reminders something firm to point to, and it protects the firm when a client sends their documents the day before a deadline.
Agree the roll-forward
Decide how the register is reviewed each year: confirming each client's obligations at their annual review, checking that new clients were set up fully at onboarding, and closing obligations for clients who've left.
What the automated version does
- Generates jobs. From the register, the system creates a job for each obligation and period in your practice management tool, with the internal milestones and the responsible person attached.
- Requests documents early. At the first milestone, the client gets a request listing exactly what's needed for that obligation, with a secure upload link. The checklist comes from the obligation type and the client's history.
- Reminds clients on a schedule. If documents haven't arrived, reminders go out at set intervals, getting firmer as the internal deadline approaches, and the responsible accountant gets a task to call if they're still missing.
- Shows the team what's coming. A workload view shows the jobs due each week by person, so managers can see a crunch coming a month out and rebalance work before it arrives.
- Flags risk early. A short list highlights any job where documents are late, preparation hasn't started by its milestone, or the statutory deadline is close and the job isn't in review.
- Reads notices. When a notice from a tax authority arrives, whether scanned, emailed or forwarded by the client, the system reads it, identifies the client and obligation, and proposes any change to the register, such as a new filing frequency or account number, for someone to approve.
- Records completion. When a filing is made, the confirmation is attached to the job, and the next period's job is already waiting.
Most practice management tools already support recurring jobs and client requests, and they work far better when they're set up from a proper obligations register. The pieces usually missing are the notice reading, the risk view and the link between a change in a client's circumstances and every future job that depends on it. Those are what our compliance and deadline tracking system adds around your existing tools. The accounting and tax page shows how it fits with bookkeeping, onboarding and reporting.
Where AI fits
Most of deadline tracking is plain rules and dates, and it should stay that way. AI models earn their place in the unstructured parts: reading notices and letters from tax authorities, interpreting client emails ("we've opened a second location in Ohio"), extracting the facts that affect obligations, and drafting client reminders that sound like they came from the client's accountant. Each of those is a time sink when done by hand, and each produces something a person can check quickly before it changes the register.
A worked example
Consider the firm from the opening. The team spends a few weeks building an obligations register, starting with the fifty most complex clients. The client whose sales tax frequency changed now has a monthly sales tax obligation in the register, and the next twelve months of jobs are created from it. Each job has internal milestones: the document request goes out on the first of the month, documents are due on the tenth, preparation finishes by the fifteenth and review by the eighteenth. When a notice arrives for another client announcing a change in filing frequency, the system reads it and proposes the change to the register, and the senior accountant approves it in a minute. The team's weekly meeting starts with the risk list, and the senior accountant's knowledge of who files what is now written down where everyone can see it.
What to watch out for
- Onboarding gaps. The register is only as complete as the information captured when a client joins. Make obligation setup a required step in onboarding, reviewed by someone senior.
- Changes in statutory dates. Deadlines move, for example when tax authorities grant disaster-related postponements for affected areas. Someone needs to own monitoring those announcements and updating the affected obligations.
- Two systems. If the old spreadsheet keeps running alongside the new system, people will trust whichever one they're used to. Retire it on a set date, after checking the new register against it.
- Reminder fatigue. Clients with many obligations can end up receiving a stream of separate requests. Group requests by client where you can, so they get one clear list.
- Automatic register changes. Proposed changes from notices should always be approved by a person. An extraction error that silently changes a filing frequency is exactly the kind of problem the system is meant to prevent.
How to tell whether it's working
Penalties and near-misses are the obvious measure, but they're rare enough to take time to show a trend. More immediate measures are the share of jobs where client documents arrived by the internal deadline, the share of jobs in review by their review milestone, and the number of jobs on the risk list each week. Track how many register changes come from notices and client emails each month, which shows how much the register would have drifted under the old method. And watch workload by week, because a smoother spread of due dates is one of the main benefits of seeing deadlines early.
Where to start this week
Take your fifty largest or most complex clients and build their obligations register in a simple table: client, entity type, year end, each obligation, frequency, jurisdiction and responsible person. Then compare the dates it produces with your current spreadsheet. The differences you find will show you how much the current system depends on memory, and they'll give you a list of things to fix straight away.
Then set internal milestones for your three most common obligation types and agree them with the team. Once the register and milestones exist, generating jobs, requests and reminders from them is a well-understood setup in most practice management tools, and the penalty letter becomes a much rarer event.
The free PATH report gives you a quick read on where deadline tracking sits among your firm's other administrative work. If you'd prefer to talk through your setup, book a call.