Sized for 1–10 staff
The workflow, roles and limits are scoped for a small or mid-size firm, not an enterprise finance department.
US bookkeeping firms with one to ten staff and thirty to sixty recurring monthly clients are who this platform is built for — not a generic file-sharing tool adapted after the fact.
The workflow, roles and limits are scoped for a small or mid-size firm, not an enterprise finance department.
A recurring client list is the assumption baked into templates, automations and the calendar itself.
The exact document types a monthly close actually needs — nothing built for one-off project work.
Once a month hands off, next month’s engagement drafts from the same template automatically.
Every bookkeeping firm running recurring clients faces the same underlying problem, whatever tools they currently use to manage it: a fixed close date arrives every month, and getting there requires statements, receipts and a handful of factual answers from every single client on the roster, most of whom aren’t thinking about their books until reminded. Left to email, that becomes a rotating set of individually-worded requests, replies scattered across a dozen threads, attachments saved into folders named things like "March2024_final_v2," and a mental tally of who’s responded that lives in one person’s head rather than anywhere searchable.
The cost of that setup isn’t visible in any single week — it shows up as the close sliding a few days later every month, as the same clarifying question getting asked to the same client three months running, and as a reviewer spending real time just figuring out whether something arrived before they can even start deciding whether it’s correct. None of that work is bookkeeping. It’s the overhead around bookkeeping, and it scales roughly linearly with client count — which is exactly why it becomes unmanageable once a firm crosses somewhere around thirty active clients without a system built for the recurrence.
Cohesio assumes a firm splits work across a small number of roles rather than one person doing everything.
Sets up templates, configures automations, and holds the roster-level view — which clients are on track, which are stuck, and where an exception has been sitting too long. The owner rarely touches individual submissions directly except when something’s escalated.
Works the queue day to day: reading evidence, accepting or correcting submissions, and resolving exceptions for the clients assigned to them. A firm with forty clients might split reviewers by client type, so payroll patterns and processor quirks become familiar rather than a surprise every time.
Handles the work that happens once a month is handed off — reconciling in the ledger, preparing statements, the actual bookkeeping the collected documents exist to support. The preparer’s starting point is a closed, reviewed month, not a scattered pile of attachments to sort through first.
By day one, last month’s handoff has already drafted this month’s engagement for every recurring client from their template. By day three, reminder cadences begin nudging clients whose due date is approaching, staggered by each client’s own schedule rather than all firing at once. Days four through seven see the bulk of submissions arrive, with routine acceptances happening the same day evidence comes in. By day eight, reviewers are down to the genuine exceptions — the mismatches and unusual patterns that need judgment, not just confirmation. Day nine is typically when the last stragglers get a direct nudge from their assigned reviewer rather than the automated cadence. By day ten, most of the roster has handed off, manifests have pushed into the ledger, and next month’s engagements are already drafting themselves in the background for the clients who just closed.
Firms don’t need to migrate everything at once. Bulk import from a CSV or QuickBooks Online populates the client roster in one pass, and a templates library scoped by client type replaces the ad-hoc checklist each staff member used to keep in their own head or their own document. The shared drive doesn’t need to be emptied out — Drive, Dropbox or SharePoint can connect so newly accepted files mirror into the existing folder structure, meaning prior years stay exactly where they are while new engagements start collecting through the checklist instead of an inbox.
Cohesio doesn’t attempt to replace the ledger. The actual bookkeeping — categorizing transactions, reconciling accounts, running reports — stays exactly where a firm already does it. What Cohesio hands off is the reviewed input to that work: a signed manifest and the original source files, attached to the matching client and closed period automatically for firms connected to either platform.
Consider a fictional four-person firm carrying 45 recurring monthly clients, split roughly 15 per reviewer across three reviewers, with one owner also acting as a fourth reviewer for a smaller book of higher-touch accounts. In a typical month, roughly 38 of the 45 packs complete with no exception at all — the reviewer’s job on those is confirming evidence that already matches. Of the remaining seven, four are simple corrections (a missing page, a wrong statement period) resolved same-day, and three are genuine judgment calls — a payroll timing mismatch, a client with an unusual one-time deposit, a seasonal closure — each taking real reviewer attention but not derailing the other 42 clients’ progress through the queue. By day ten, all 45 have handed off, and 45 new engagements have already drafted themselves for the following month.
Both use the same engagement engine: confirm requirements, collect submissions, review evidence, hand off — then draft the next month.
Payroll summary covers Feb 26 – Mar 25, not the calendar month. The model flags the period mismatch with the page reference. A staff member writes one friendly correction request; the client re-exports. Nothing was auto-accepted.
Review & handoffThe signed decision manifest and original files attach to the closed period in your ledger automatically, so the handoff isn’t just a download — it’s already where your close happens next.

It depends on how much of each pack still needs a manual look versus routine acceptance, but firms in that range commonly split review across two to three people, often by client type or alphabetically, so no single person is the bottleneck for every exception in a given week.
Each engagement moves through the queue independently, so a cluster of due dates doesn’t create a bottleneck the way a shared inbox does — a reviewer works through waiting-on-you client by client, and automations keep chasing outstanding items on each one without anyone coordinating it manually.
A firm can scope a preparer’s access to an assigned subset of clients rather than the whole roster, which matters for firms that split work by client type or by staff member’s book of business rather than giving every team member full visibility into every engagement.
No — moving intake into Cohesio doesn’t require deleting anything from an existing drive. Most firms keep prior years' files where they are and start collecting new engagements in Cohesio going forward, connecting Drive, Dropbox or SharePoint so accepted files mirror into the existing folder structure too.
The reminder cadence keeps nudging on schedule regardless of a client’s history, but a firm can tag a client for closer routing — flagging their exceptions straight to an owner rather than the general queue — so a known slow responder doesn’t quietly stall the whole month’s close.
Start your free 7-day trial of the Team plan and set up your first client and monthly pack in under ten minutes.