Practices and firms

Accounting firms: the document chase, prepared for review

For office managers and partners at accounting and bookkeeping firms with 2 to 15 staff. Workflows list what is missing and draft the request; the firm sends it.

Your week, in your words

iSystematic works with accounting and bookkeeping firms whose week goes on chasing documents in tax season, missing slips, engagement letters, onboarding new clients, payment reminders and notices from the tax authority.

Omar (fictional), the office manager at a ten-person firm, keeps a spreadsheet of which clients still owe which documents, and writes every reminder by hand. The workflows on this page are written for a week like his.

Where most start

Most firms start with the document chase, before the next filing season: W12 Client Onboarding lists what is missing and prepares the request, and W16 Invoice Reminder Preparation prepares payment reminders. Both are configured with you in a setup session.

A different start fits firms that want workflows built and run for them: an implementation of up to three workflows in your own accounts, with tests, training and 30 days of support. Firms that want their site, client guides and inquiries rebuilt together can take the Practice Platform.

Works with your systems

Checklists and request drafts need no integration; reading your client portal or practice software is assessed first.

What it doesWhat it needs
Checklists and request draftsNo integration. They run in the firm's own assistant account.
Reading your client portal or practice softwareA connector (level 3) or a custom integration (level 5), assessed first.

Software is named here only to say what has been tested with it. Nothing on this page implies an integration that has not been built.

Your clients' documents

No client returns, slips or identity numbers go into any assistant account the firm has not reviewed, and identity numbers never do. The workflows work from the list of what is missing, not from the documents.

How it is built

Every system we build for a firm keeps the promises below; each is the plain-words form of a framework explained on How we build.

What we promiseWhat stands behind it
It never promises a client anything you have not approvedThe Boundary Invariant
It checks every answer against your own sources before anyone sees itPEVG: the verifier
It cannot change its own instructions; you approve what it learnsPARA: adaptation bounded like action
Nothing goes live until a named person at your firm signs it offFive-Gate Deployment Model™: G3 Approval
Confidential questions go only to the AI services you approved, in Canada where requiredGoverned Routing Policy; Cross-Border AI Architecture Patterns™
It has a monthly spending limit it cannot exceedBudget as Boundary
We check every service we put into your setupAI Vendor Risk Framework (AVRF)™
If something goes wrong, we can show exactly what happened, and fix the causeAI Incident Response Protocol (AIRP)™ and the event identity
You can see what it did and whyThe BOE Declaration

These promises describe the systems we build and run for you. A free card is a manual routine: you run it and check its output yourself.

What always stays with you

The firm decides these, every time.

  • Every client message
  • Every amount
  • Every engagement term
  • Anything filed

What we never do

We never build any of these into a firm's setup.

  • Tax advice generated for clients
  • Figures entered that the client did not supply
  • Reminders for items not confirmed outstanding

Omar is a fictional persona. Workflows prepare; people decide.

Start

Start before the next filing season

Tell us which documents you chase most. We reply with one recommended start.