Log three kinds of dates for each state client: when a renewal window opens, when a license expires, and when each filing is due. Partners and operations leads at small accounting firms usually know the big deadlines by heart. The trouble is the smaller items: a state license that runs on its own calendar, a payroll-related report that is due at the end of the month after a quarter, a notice that goes to a client's old mailbox. When a firm handles dozens of client files across several states, those dates pile up in inboxes, sticky notes, and someone's memory.
Key takeaways
- Build the inventory of client and state pairs first, and give each client one owner.
- Log each renewal window, expiration, and recurring filing as its own entry, with separate fields.
- Store the rule behind a recurring deadline, then generate the dates from it.
- Set at least two reminders for each expiration, and record the date you last checked each agency page.
- Review the log monthly, and check each agency page against your entries every quarter.
This post also shows how to keep those dates separate, where to store them, and how to review them so slips get caught early.
Nothing here replaces the official rules. Each state sets its own calendar. The examples below come from two state pages we checked, and they are meant as a model for the questions to ask. Confirm every date on the agency's own site before it goes into your log.
Start with an inventory of client and state pairs
Before you log a single date, build a list of every client and state pair. A client based in one state that has employees working in another, or a client with a branch office, can create a second state obligation that never appears in the engagement letter. Ask each client four plain questions: where is the business registered, where does it have employees, where does it hold a license, and which agencies have sent it mail in the last few years. For the intake questions themselves, see Accounting Client Intake Checklist for a Clear Handoff.
Useful columns include the client name, the state, the agency name, the account or license number, the person at the client who receives agency mail, and the date you last checked the agency's page. That last column matters. A date copied from an old email may be wrong, and a date you checked six months ago may have changed since.
Many firms find, at this stage, that the same state agency appears under two or three names across their files. A withholding account, a reemployment tax account, and a general business license can all sit with the same department but get tracked as if they were unrelated. Log each one on its own line. Merging them makes it harder to see which item is due when.
Do not skip the clients you think are simple. A single-owner business with one employee may still have a payroll account with a state agency if it pays wages there, and the owner may not realize that reminders go to a personal address. The inventory is where those gaps show up.
Once the list is complete, assign an owner to each client, not to each state. One person who knows the client's business should be accountable for every state row on that client's file, even if a specialist prepares the actual returns. That owner receives the reminders and answers when an agency writes back. Owning the client rather than the state avoids the situation where three people each assume another one is watching a deadline.
Date one: when the renewal window opens
Renewal dates are not always the dates that matter most. For many state licenses and permits, the agency opens an ordering or renewal window well before the new credential takes effect. If your log records only the expiration date, you will miss the window in which a client can order the next year's credential.
North Carolina's withholding tax page gives a clear example. It says, "Beginning September 1, 2026 you may begin ordering your 2027 license and decals." The same page says, "Licenses and decals are valid for one calendar year ONLY." Two things follow for the log. First, the opening date of the ordering window is its own entry, separate from the year the license covers. Second, because the license is tied to the calendar year, the expiration entry should reflect that calendar year and not a date twelve months after the day the client bought it.
Today is November 1, 2026. That means the 2027 ordering window described on that page has already opened. If your log has no entry for it, add one now and flag it for the client conversation, not only for your own files.
Give every window entry three pieces of information: the date it opens, the date it closes if the agency lists one, and what the client needs in hand to place the order. Write the last item down in plain words, such as the account number, a signed form, or any proof the agency asks for before it will issue a new credential. A team member should be able to act on the entry without rereading the agency's page.
Window entries also need a contact on the client side. Name the person who can sign or send the request, and note whether that person is the owner, a bookkeeper, or an outside adviser. Add a short note on how the client has responded in the past. If a client has always needed two reminders before sending documents, the log should say so, so the next window opens earlier on the team's calendar.
Date two: when the license or permit expires
The second date is the expiration itself. Log it as a hard deadline and set reminders against it. Then add a note about what happens if the credential lapses. Some lapses are a paperwork inconvenience. Others stop a client from doing business in the normal way, or stop it from ordering the materials it needs. Your log should tell the team which kind of lapse applies to each client.
A simple scale helps. Mark a license as critical if a lapse stops the client's work, important if a lapse brings a fee or a penalty, and routine if a lapse only means a renewal form has to be filed late. The team member who owns the client should be able to see the mark at a glance.
Be realistic about lapses that look small. A late renewal for a credential the client rarely uses may cost little, but a lapse on a credential the client needs to bid on work, sign contracts, or buy supplies can cost far more than the fee. Your scale should reflect what the client actually does, not only what the agency charges.
Keep the expiration date and the ordering window in separate fields. The window is the action date, when someone needs to start paperwork. The expiration is the deadline. Mixing them up is the usual way a credential ends up expired even though the firm had a reminder set. The reminder went off on the wrong date.
Set at least two reminders for each expiration. One should fire when the ordering window opens, so the team starts the request while there is still time. The second should fire a few weeks before expiration, as a check that the request actually went through. Adjust the timing to how long your clients usually take to respond, which your own history will show within a year or two of keeping this log.
Illustrative example: one license entry
Suppose a client holds a license that is valid for one calendar year, and the agency opens its ordering window on September 1 (an illustrative date). The log gets three entries for that license: the window opening on September 1, the expiration at the end of the calendar year, and a note on what the client must have ready to order. A reminder fires on the day the window opens, so the team starts the request. A second reminder fires two weeks before the expiration, to confirm the request went through. If this client has always needed two reminders before sending documents, the window reminder moves earlier.
Date three: when each periodic filing is due
The third kind of date is the recurring filing deadline, the one that returns every month, quarter, or year. These are often the easiest to log and the easiest to forget, because they look routine. They also tend to have the most visible consequences, since a late filing can show up as a penalty on a client's bank statement.
Florida's reemployment tax page is a good model for how to log one of these. It says the quarterly report, Form RT-6, is due "by the end of each month following the end of the quarter." Read literally, that means a quarter that ends December 31 produces a due date at the end of January. Logged this way, the entry is not a single fixed date. It is a rule that produces a date every quarter. Store the rule, then generate the dates from it, so the log does not depend on someone remembering to add the next quarter by hand.
The same page includes the phrase "Previously liable for reemployment tax in the State of Florida." Treat that as a reminder that a client's history with a state can matter, not only where it is located today. A client that has moved, changed its payroll setup, or taken over another business may have a history that changes which obligations apply. Read the full page for the conditions before you decide whether a new client needs to register or not, and write the answer into the inventory with the date you checked it.
Sometimes a filing is already late when you find it. When that happens, log the missed due date, the date the filing was actually made, and any notice the agency sent in response. Do not overwrite the original due date. The record of the miss is useful for the client conversation and for deciding whether the client needs a different reminder process. Tell the client promptly and plainly what happened, what is being done about it, and what the team will change so the same miss does not repeat.
Every recurring filing entry should carry the period it covers, the due date, the filing method, the person who prepares it, and a blank field for the date it was actually filed. That last field is what separates a log from a calendar. A calendar tells you what is coming. A log shows you what was done. For the payroll side of these filings, Check 8 state reporting steps before payroll starts lists items to confirm first.
Choose where the log lives
Once the fields are settled, choose a home for the dates. Small firms usually end up with one of three setups. The comparison below looks at each one on the points that matter most to a team that shares client work.
| Setup | Best for | Main strength | Main weak point |
|---|---|---|---|
| Shared spreadsheet | A small number of client and state pairs, with one person who owns the log | Easy to edit, filter, and sort by state or deadline | Depends on someone updating it, and sends no reminders unless you add them |
Most small firms should start with a spreadsheet. Move to a calendar or a service when the spreadsheet starts to need constant repair, or when reminders keep reaching the wrong person. Whichever setup you choose, keep the same fields across all of them so a move later does not lose history.
Build a review routine that catches slips
Logs fail when nobody looks at them. Set a standing review once a month and a larger check at the start of each quarter. In the monthly review, the owner of each row confirms that the next thirty days of dates are covered, that the documents are ready, and that any window which has opened has been acted on. Keep the meeting short. Its job is to find the rows that are stuck, not to re-audit the whole list.
The quarterly check goes deeper. Confirm that each inventory row still matches the client's current facts, including its entity type, its payroll setup, and its locations. Pull the agency page for each state and compare it to the dates you logged. Note the date you checked each page, even if nothing changed. When a page does change, update the log the same day and tell the client what is different and why it matters for them. For a separate look at employer forms with year-end checkpoints, see Year-end employer forms: 4 calendar checkpoints.
Assign a backup for every row. Someone is always out during busy season, and a row with one owner and no backup is a single point of failure. The backup should be named in the log, and should know where the documents for that client are kept.
Staff changes need their own step. When someone leaves the firm or moves to another team, walk through the rows they owned and reassign each one before their last day. Ask them which windows are open, which clients are slow to respond, and where the documents live. Those answers rarely appear in the log unless someone wrote them down, so make the handover part of the log review rather than a separate task.
Set an escalation point too. If a client has not sent the documents a set number of days before a window closes, the owner should escalate to the partner on that engagement rather than wait. Decide the number ahead of time, write it in the review notes, and use it the same way for every client so that no one has to make the call alone on a busy afternoon.
Keep the log honest over time
A log decays unless someone maintains it. When a client changes its entity type, moves to a new state, or closes an account, update the row rather than deleting it. Keep the old entry with an end date, and record who made the change and when. The history matters if an agency later asks about a past filing or a past license.
Log agency notices on the day they arrive, even when a notice looks minor. A notice that says a mailing address has changed, or that an account needs review, is often the first sign that a date has moved. If a notice arrives at a client's address instead of yours, ask the client to forward it, and add a line to the inventory saying where agency mail goes.
Partners should look at the log at least once each quarter. The goal is not to check every entry. It is to see whether the team is keeping up with the windows, the expirations, and the filings that matter most. A partner who sees a row marked critical with no recent update knows to ask about it before the window closes.
What changes from state to state is the rule that produces those dates. Log the rule along with the date, check it against the official page, and keep a record of when you checked. That habit does more to prevent a missed deadline than any single reminder you could set.
Next step for today: Pick one client and list every state agency that has written to it in the last few years. Add one row for each agency, and check its page before you log any date.
Related guides: Bad debt claims: 3 deadline checks before filing · Check 6 rules for married filing separately clients.
Frequently asked questions
Do I need a separate entry for the ordering window?
Yes. The window is the date someone starts the request, while the expiration is the deadline, so each one needs its own field.
How often should the log be reviewed?
Review it once a month, with a larger check at the start of each quarter.
What should I do when a filing is already late?
Log the missed due date, the date the filing was actually made, and any agency notice, and do not overwrite the original due date.
General information, not legal or tax advice.
Tracking returns this season? Tax Season Return Status Board gives each return a row with its preparer, its stage, the days it has sat in that stage and past deadline or due soon flags.