How to keep a compliance calendar for a multi-entity group

Most groups that miss a filing did not miss it because nobody cared. The obligation lived in one person's inbox, or in a registered agent's reminder that went to an address nobody checks, or in a spreadsheet that stopped being updated the year a new subsidiary was formed. A compliance calendar fixes that only if it is built from the right source and kept current as the group changes.

This is a practical guide for whoever owns that problem: the general counsel, the company secretary, the CFO, or the person who gets the call when a state writes to say an entity is no longer in good standing.

Start with the entity register, not the calendar

Every date on the calendar traces back to a fact about an entity. Before adding a single deadline, build one register that records, for each entity:

• legal name and any trade names
• entity type and state of formation
• every state where it is registered to do business as a foreign entity
• the registered agent in each of those states, and where its notices actually end up
• fiscal year end
• federal and state tax registrations, including payroll and sales tax accounts
• officers, directors or managers, and who can sign for it
• status: active, dormant, or being wound up

Dormant entities belong on the register too. An LLC that holds nothing usually still owes its annual report and fees, and the bills keep coming until it is formally dissolved or withdrawn from each state.

Know where obligations come from

For a US group, most recurring obligations come from five places.

• State entity maintenance. Annual or biennial reports and franchise taxes. Due dates vary by state and sometimes by entity type. Delaware, for example, expects a corporation's annual report and franchise tax by 1 March and an LLC's annual tax by 1 June. Each foreign registration generally brings its own report in that state.
• Federal and state tax. Income tax returns, estimated payments, payroll filings, and sales and use tax returns. Many of these key off the fiscal year end, so the same form can fall in different months for different entities.
• Licences and permits. Professional, industry and local business licences, each on its own renewal cycle.
• Corporate housekeeping. Annual meetings of shareholders or members, board meetings the bylaws or operating agreement require, and approvals that have to happen before something else can (accounts, auditor appointments, distributions).
• Contracts. Renewal and termination notice windows, covenant reporting under loan agreements, insurance renewals. These are the ones most often left off, because no regulator sends a reminder.

Store the rule, not just the date

A date is the output. What you want to store is the rule that produces it: “15th day of the 4th month after year end”, “last day of the anniversary month”, “60 days before renewal”. Store the rule and next year's calendar generates itself, and stays right when an entity changes its year end. Store only the date and someone has to retype it every year, which is where the errors come from.

Keep the source beside each rule (the statute, the regulator's page, or the contract clause) so anyone can check it, because rules change. Also record what happens when a deadline lands on a weekend or holiday. Federal tax deadlines generally move to the next business day; states are not uniform, so note each state's rule rather than assuming.

Give every item an owner, a lead time and proof

Each obligation needs four more fields before it is useful.

1. Owner. A named person, not a team, plus a backup. The owner will be on leave the week it matters.
2. Internal due date. Early enough to collect information, get sign-off and survive a failed upload. If the filing needs board approval, the date that matters is the board meeting, not the state's deadline.
3. Status. Not started, in progress, filed, confirmed.
4. Evidence. The receipt, confirmation number or stamped copy, attached to the item. “Done” without evidence is a claim, and the person who made it may have left by the time an auditor or a buyer's counsel asks.

Tie the calendar to the events that change it

Calendars go stale at predictable moments. Treat each of these as a prompt to review it:

• an entity is formed, acquired, merged or dissolved
• an entity registers in a new state or withdraws from one
• an entity changes its fiscal year end
• a registered agent, officer or signatory changes
• a new licence, loan or significant contract is signed

Once a quarter, reconcile the register against your registered agent's records and order good-standing certificates for a sample of entities. A certificate that comes back with a problem tells you something the calendar did not.

Watch the newer obligations

Two kinds of obligation are easy to miss because they are recent or still moving.

The first is beneficial ownership reporting under the Corporate Transparency Act. FinCEN's interim final rule of March 2025 removed the requirement for companies created in the United States and kept it for certain foreign companies registered to do business here. The rules have changed more than once, so confirm the current position with counsel instead of relying on an earlier decision.

The second is AI regulation. If any entity in the group builds or uses AI systems that affect customers, employees, or people in the EU, those obligations belong on the same calendar. The EU AI Act applies in stages from 2025 to 2027, and several US states have passed AI laws with their own effective dates. AsymiLink Meta keeps a plain-language summary of the main AI regulatory frameworks and their key dates, which is a sensible place to start working out which ones apply to you.

Report it upwards

The calendar is an operating tool, but a one-page summary of it belongs in front of the board or audit committee: what fell due since the last meeting and whether it was met, what is overdue and why, and what is coming up that needs a decision or a signature. For more on how to structure that kind of reporting, see what a good board pack looks like.