Accounting and audit practices have to prove independence with respect to every attest client, from every employee, on a schedule. TATER runs that whole cycle — roster, attestations, conflicts, and engagement reviews — as a system of record instead of a workbook and a reminder email.
Independence is not a checkbox on a policy — it is a recurring, per-person, per-client attestation with a real audit trail behind it. TATER models the actual process: a client roster employees attest against, cycles that go out annually in full and monthly by delta, a sign-off from every employee even when they have nothing to declare, and conflicts recorded against the specific person and the specific client. It is a separately licensed module, because it is a whole vertical rather than a feature.
The master list of attest clients employees declare against. Seed it with a bulk CSV or Excel import, then maintain it record by record — duplicates are caught on the way in, matched by external ID first and then by name.
An Annual cycle covers the full roster. A Monthly cycle computes its own delta — just the clients added since the previous cycle — so recurring attestation stays proportionate to what actually changed.
Everyone signs off, including the people with nothing to declare — a clean attestation is the evidence. Outstanding sign-offs are visible as a live list, not reconstructed from replies.
A declared conflict becomes its own record, linked to both the employee and the client it concerns, so it can be reviewed, tracked and evidenced rather than living in an inbox.
Engagement-level independence assessments covering threats and safeguards, per-staff confirmations, and partner rotation — aligned to AICPA and PCAOB independence requirements.
The roster, cycles and attestations are queryable from the Insights report builder and reachable over MCP, so status reporting and reminders don’t depend on someone opening the module.
The same three steps run annually in full and monthly by exception — the module works out which clients are in scope so the firm doesn’t have to.
Import the attest client list, then keep it current. Each client carries the date it was added, which is what the monthly delta is computed from.
Open an Annual cycle across the full roster, or a Monthly cycle that resolves to only the clients added since the last one. A newer annual supersedes the prior cycle without discarding its signatures.
Every employee signs off — declaring conflicts where they exist. Conflicts file as linked records; the cycle shows what is still outstanding.
It’s independence season: the whole roster goes out to every employee, and the tracking is a spreadsheet of who has and hasn’t replied.
Open an Annual cycle against the current roster. Every employee gets their own attestation, and the outstanding list is the product — not a column someone maintains by hand.
Four new attest clients were onboarded since the annual. Re-sending the entire roster to everyone is absurd; sending nothing is a gap.
A Monthly cycle computes its own delta from the roster — only the clients added since the last cycle — so people attest to what actually changed.
A staff member flags a personal financial interest in a client mid-engagement.
The conflict is filed as its own record, linked to both the person and the specific client, and stays attached to the engagement review instead of living in an email thread.
The guide covers importing the client roster, opening annual and monthly cycles, and how the delta and conflict records work.
See the attestation cycle run against your own client roster in a walkthrough built for accounting and audit practices.