Write-up work automation hands the repetitive steps of a monthly or quarterly write-up to software: collecting statements, sorting them, reading transactions and tying balances from one month to the next. Classification judgments, adjusting entries and the final review of the financial statements still need an accountant, so plan the work up front around both.
What is write-up work in accounting?
Write-up work in accounting is the engagement where a firm takes a client's raw records, such as bank statements, credit card statements, receipts and payroll reports, and turns them into a general ledger and periodic financial statements. It usually runs monthly or quarterly for small businesses that do not keep their own books.
The deliverable is a set of books plus statements. At the end of each period the client receives a balance sheet and income statement, sometimes with a general ledger detail report and a trial balance. The firm's working papers show how each balance was reached.
Write-up differs from bookkeeping support in who holds the pen. In write-up, the firm records the transactions. In a review of client bookkeeping, the client records them and the firm checks the result; that work has its own process, covered in the post on client-prepared financial statements review.
Write-up also differs from catch-up work. Catch-up rebuilds months or years of missing books at once, usually from a stack of old statements. The post on catch-up bookkeeping from bank statements covers that project. Write-up is the steady state that follows, one period at a time.
The write-up work steps from source documents to statements
Write-up work runs through the same steps every period: collect the source documents, sort them, record the transactions, reconcile each account, post adjusting entries, prepare the statements, and review them before they go to the client. Each step depends on the one before, so a gap early in the chain shows up later as a balance that will not tie.
- Collect. Gather every statement, receipt, invoice and payroll report for the period from the client.
- Sort. Group documents by type, account and period, and spot anything missing, such as one month of a credit card account.
- Record. Enter each transaction into the ledger with an account, date, amount and memo.
- Reconcile. Agree each bank, card and loan account to its statement balance.
- Adjust. Post period-end entries for accruals, depreciation, prepaid items and corrections.
- Prepare. Produce the trial balance, balance sheet and income statement.
- Review. Read the statements against the prior period and the client's business, then issue them.
One month of write-up for an example client
Harbor Lane Florist, a fictional client, has one checking account ending XXXX-4821, one credit card ending XXXX-3307 and a payroll provider. For March, the firm expects three documents: the checking statement, the card statement and the payroll register. Two arrive in the first week of April. The card statement does not, so step two stops there and a request goes back to the client before any recording starts.
Once all three are in, recording takes the bulk of the time. The checking statement holds 64 transactions and the card statement 41. Most are repeat payees, such as the flower wholesaler, the delivery van lease and the utility company. A handful are new, such as a one-off purchase from a hardware store that could be supplies or a small equipment item.
Reconciliation follows. The checking account's ledger balance should match the statement's closing balance after outstanding checks. Adjusting entries come next: a month of depreciation on the van and the cooler, and an accrual for wages earned in the last days of March but paid in April. Only then do the statements get prepared and read against February.
The order matters for automation. Every step after the first depends on the documents being complete and sorted, so the earliest steps are where missing paper does the most damage.
Getting the client's existing ledger into a spreadsheet is a common first task when a firm takes over a write-up client; see which general ledger formats clients send for the shapes to expect.
Which write-up work steps can software automate today?
Software can automate the mechanical write-up steps: collecting documents into one place, sorting them by type and period, reading transactions off statements and tying statement balances month to month. It can assist with categorizing transactions and matching them to accounts. It should not decide adjusting entries or approve the statements.
The test for automation is whether the step has one right answer that the documents themselves contain. A statement's ending balance is printed on the page. Whether a 4,000 payment to a contractor is a repair or an improvement is a judgment about facts the page does not hold.
Write-up steps by level of automation
This table sorts the steps by what software can take, with what the reviewer checks at each one. The dollar figures in the reviewer column come from a fictional client, Harbor Lane Florist, and are examples only.
| Step | Automate | Assist | Keep manual | What the reviewer checks |
|---|---|---|---|---|
| Collect documents | Yes | Every expected account has a statement for every month | ||
| Sort by type, account and period | Yes | No document sorted into the wrong account or month | ||
| Read transactions from statements | Yes | Extracted rows total to the statement's deposits and withdrawals | ||
| Tie balances month to month | Yes | March opening balance of 18,240 equals February closing balance of 18,240 | ||
| Categorize transactions | Yes | Suggested accounts for new payees and unusual amounts | ||
| Reconcile to the ledger | Yes | Reconciled balance agrees with the ledger; reconciling items are explained | ||
| Post adjusting entries | Yes | Each entry has support and a reason | ||
| Prepare statements | Yes | Balance sheet balances; net income agrees with the change in retained earnings | ||
| Review and issue | Yes | Swings against prior periods have an explanation |
Statement continuity is where the "tie balances" step earns its place. If the February statement for account XXXX-4821 closes at 18,240 and the March statement opens at 18,420, either a statement was misread or a month is missing. Catching that before transactions are recorded saves a reconciliation that will never balance.
Schema CPA covers the first four rows: one upload link per client, every page sorted by type, issuer and period, statement balances tied month to month with gaps called out, and export to Excel or CSV. QuickBooks Online and Xero connections are on the roadmap, as the workflow section of the homepage says.
Write-up work automation that still needs a reviewer
Write-up work automation still needs a reviewer wherever a step involves a judgment the documents do not settle: assigning an account to an unfamiliar payee, deciding whether a cost is an expense or an asset, recording accruals, and reading the finished statements for sense. Software can suggest an answer in those places, but a person should approve it.
Categorization is the largest grey area. Rules that map a payee to an account work well for recurring vendors, such as the same utility every month. They fail on new payees, on vendors who sell more than one kind of thing, and on owner purchases mixed into business accounts. A reviewer should look at every transaction where the rule had no prior match and every amount well outside the payee's usual range.
Adjusting entries stay manual because they rest on facts outside the statements. Depreciation depends on what assets the client holds and how the firm records them. Accruals depend on what was owed at period end but not yet paid. The entries that come up every year end are covered in which adjusting journal entries come up every year-end.
The final read cannot be automated away. Comparing this period with the last few is how a reviewer spots a miscategorized payment or a missing accrual. The post on multi-year financial statement comparison shows how to lay out that comparison in Excel.
Keep a record of what the reviewer approved. A short log of overridden categories and approved adjustments makes next month faster, because the same decisions do not have to be made twice.
When write-up work automation is not worth it
Write-up work automation is not worth setting up when a client has very few transactions, when records arrive so incomplete that most of the work is chasing and interpreting them, or when a client is a one-time job. In those cases the setup and checking take longer than doing the work by hand.
Low volume is the clearest case. A client with one bank account and twenty transactions a month can be recorded by hand in less time than it takes to review automated suggestions. Automation pays back on repetition: the same accounts, the same vendors, month after month.
Messy records are the second case. If a client sends shoebox receipts with no statements, or statements with pages missing, the bottleneck is not reading the documents. It is getting the right ones. Software that sorts and reads pages helps only after the pages exist, though flagging a missing month early still shortens the chase.
One-time engagements are the third. Setting up categorization rules, payee mappings and templates is an investment that pays over many periods. For a single year of catch-up work with no ongoing engagement, simpler tools may be enough.
Mistakes firms make when automating write-up
The first mistake is automating recording before collection. If documents still arrive by email, text and the occasional paper envelope, faster transaction entry only moves the wait. Fix intake first, so every statement for every account lands in one place and a missing month is visible on day one.
The second is trusting categorization rules without an exception list. A rule that sent a payee to office supplies last year keeps doing so after the client starts buying inventory from the same vendor. Review new payees and unusual amounts every period, and retire rules that keep getting overridden.
The third is skipping the continuity check because the reconciliation balanced. A reconciliation can balance on a month that was keyed from the wrong statement, if the wrong statement happened to be internally consistent. Tying each opening balance to the prior closing balance catches that case.
Watch the cost of checking, too. If every automated result needs a line-by-line review because the client's records are inconsistent, the time saved on entry is spent again on review. The hours calculator on the homepage estimates what manual entry currently costs your team, which is the baseline any automation has to beat. When the numbers favor it, get started with one write-up client and compare the month against your usual process.