# AI for Accounting and Bookkeeping Firms Client Chasing, Onboarding, Queries, and Surviving Deadline Season ## Overview The constraint in a small accounting practice is almost never technical skill. It is that a large share of the week goes to chasing clients for records, tracking who owes what, onboarding that stalls on a predecessor handover, and answering the same routine questions across a client base. That work has no owner, it peaks exactly when the technical work peaks, and it is why adding another qualified person often increases throughput less than expected. Sistava takes the administrative layer. Every professional judgement stays with qualified people: advice, verification, filing, and anything client-specific. What changes is that your team spends deadline season doing the work rather than asking for the inputs to it. ## At a Glance - **Per client** Outstanding records tracked - **Readiness** Not just the deadline date - **Second net** Alongside your practice system - **99/mo** Starting price ## Before / After - **Before:** Six weeks of asking the same clients for the same documents **After:** Tracked per client, chased on a real escalating schedule - **Before:** Chasing a client for something they already sent **After:** Arrivals marked off before the next chaser goes out - **Before:** Onboarding stalled on a predecessor handover nobody owns **After:** Tracked from signature with the handover actively chased - **Before:** The same routine questions answered from scratch **After:** Answered with that client context already pulled - **Before:** Discovering in January that January is oversubscribed **After:** Capacity crunch visible weeks out, while options exist - **Before:** Knowing a client is painful but not what it costs **After:** Time against fee per client, with absorbed scope visible ## Benefits ### Outstanding Records Tracking What each client owes, what has arrived, and escalating chasers with only the genuinely stuck escalated to you. ### Onboarding Checklists Tracked from signature including predecessor handover, with real blockers separated and a definite ready point. ### Answered Routine Queries Deadline and process questions answered with client context pulled, advisory questions prepared for a qualified person. ### Obligation and Risk View Every client deadline combined with how much work is outstanding, so risk reflects readiness rather than date alone. ### Capacity Forecast Volume due in a window against what the team can deliver, surfaced early enough to bring work forward or add help. ### Per-Client Profitability Time against fee, absorbed extras made visible, revenue mix tracked, and fee reviews backed by specific evidence. ## Benefits ### Information Answered, Advice Prepared Deadlines and process go out directly. Anything about a client specific position is prepared for a qualified person, structurally rather than by judgement in the moment. ### Reconciles Before Chasing What arrived is marked off before the next reminder, because chasing someone for a document they already sent is the fastest way to lose a good client. ### Risk From Readiness Deadline proximity combined with outstanding work, so the at-risk list is genuinely at risk rather than merely soon. ### A Second Net Built to sit alongside your practice management system, not replace it, because filing deadlines justify redundancy. ## How It Works 1. **Bring In the Client Base**: Entity types, year ends, registrations, and your existing outstanding lists. Gaps in the records surface immediately, which is useful in itself. 2. **Start With the Chase**: It is the fastest return in the practice and the thing consuming most of deadline season. Onboarding and profitability work follow once it is steady. 3. **Keep Every Judgement With Your People**: Advice, verification, filing, and client-specific positions stay with qualified staff. The administration around them stops competing for their hours. ## Comparison | Dimension | Traditional | With Sista | |---|---|---| | Chasing records | Repeated emails, tracked in someone head | Per-client tracking with escalating, reconciled chasers | | Onboarding | A checklist nobody owns, stalled on handover | Tracked from signature with the handover chased | | Routine questions | Answered from scratch, inconsistently | Answered with client context, consistently | | Deadline view | A date-sorted list everyone scans | Risk from readiness, ranked by exposure | | Capacity | Discovered during the crunch | Visible weeks out while options remain | | Client profitability | A feeling the team shares | Time against fee with absorbed scope visible | ## The Bottleneck Is Administrative, Not Technical Practices assume growth requires more qualified capacity, and then find that adding it moves throughput less than expected. The reason is that a large share of elapsed time on a job is not technical work at all. It is waiting for records, asking again, tracking what arrived, and answering questions while waiting. That means the practice is constrained by an administrative layer that a qualified hire is expensive and poorly suited to absorb. It is also the layer that scales worst, because chasing effort grows directly with client count while technical efficiency does not. Handling it separately is what lets the qualified people spend deadline season on the work that requires them, which is both better economics and a considerably better January. ## Where the Regulated Line Sits Accounting practice carries professional obligations that make the boundary here worth stating explicitly rather than leaving implied. Advice on a client specific position, professional judgement about verification and risk, filing, and anything a client will rely on stays with qualified people. That is not a limitation being apologised for, it is what makes the arrangement safe to use inside a regulated practice. What is handled is gathering, tracking, chasing, reconciling, preparing, and answering questions that are matters of public fact rather than advice. That layer is where the hours go, and none of it requires the professional judgement clients are paying for. ## FAQ ### Does this give tax advice? No. It answers questions of fact such as when a deadline falls or what a form is for, and prepares anything client-specific for a qualified person. Advice carries liability and stays with someone who can be held to it. ### Can we rely on it for filing deadlines? As a second net alongside your practice management system, never instead of it. Penalties and professional consequences justify two independent systems checking each other. ### Will it email clients directly? Routine record chasers can go directly where you allow it. Anything client-specific, or to a client who is already unhappy, is drafted and waits for review. ### How is client data handled? It stays inside your workspace and is not used to train anything. Given the confidentiality obligations in practice, the detail on our trust pages is worth reading properly. ### We use a practice management system already. Does this overlap? It complements rather than replaces. Your system holds the record; the gap it does not fill is that nobody is actively watching and chasing during a busy month, which is what this does. ## Specialists - **[Chasing Client Records](/en/use-cases/accounting-firms/chasing-client-records)** — The job that consumes deadline season - **[Client Onboarding](/en/use-cases/accounting-firms/client-onboarding)** — From signed engagement to ready to work - **[Client Queries and Advisory Prep](/en/use-cases/accounting-firms/client-queries)** — Answer the routine, prepare the rest - **[Deadline and Compliance Tracking](/en/use-cases/accounting-firms/deadline-tracking)** — Every client, every obligation, with lead time - **[Practice Reporting and Profitability](/en/use-cases/accounting-firms/practice-reporting)** — Which clients are worth the work