Finance & FP&A

How to prepare audit and tax workpapers as Small Law and Accounting Practices

Finance & FP&AFor Small Law and Accounting Practices2 apps12 steps~24 min to set up

At tax season or during a client audit, your four-person CPA practice is stitching together workpapers from QuickBooks exports, Outlook threads, and whatever the client emailed last Tuesday. Someone manually reconciles the trial balance against bank statements pulled from Plaid. Journal entry support gets re-requested because nobody tracked what was already collected. Audit ticks and tie-outs happen in a shared Excel workbook that two people edited offline. Tax deadline tracking lives in a wall calendar and a partner's memory. Every engagement is a custom assembly job. The work isn't hard — but rebuilding the same scaffolding for each client every quarter is costing you four to six hours per engagement that you can't bill.

Build this on Starch → See the apps used

Finance & FP&AFor Small Law and Accounting Practices2 apps12 steps~24 min to set up

Outcome

What you'll set up

A per-client workpaper workspace that pulls QuickBooks entity data on a schedule and surfaces trial balance, journal entries, vendor payments, and outstanding invoices in one place — ready for tick-and-tie without a manual export

An automated document-request tracker that logs what support you've asked the client for, what's arrived, and what's still outstanding — so you stop reconstructing the request chain from Outlook search

A tax deadline and deliverable dashboard across all active engagements, pulling from your calendar and QuickBooks close dates, so a partner can see at a glance what's due this week and what's at risk

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Transaction Insights Knowledge Management

Data sources & config

Starch syncs your QuickBooks data on a schedule — pulling invoices, bills, vendor payments, journal entries, and account balances for each client entity (up to 50,000 records per entity). Starch connects directly to Gmail or Outlook so the document-request tracker can log email threads and send weekly summaries. Starch connects directly to Google Calendar to surface filing deadlines and close dates. For any client portal or state tax agency filing site that lacks an API, Starch automates it through your browser — no API needed.

Prompts to copy

Build me a workpaper prep app for a client audit. Connect to QuickBooks and pull their trial balance, journal entries, vendor payments, invoices, and bills. Show me a reconciliation view where I can tick off each line as supported, flag items that need documentation, and see a running list of what's still open.

Create a document-request tracker for this engagement. Every time I log a support item we need from the client, record who requested it, the date, the account it relates to, and whether it's been received. Send me an Outlook email summary every Monday of everything still outstanding.

Build a deadline dashboard that shows all active client engagements, their filing or deliverable due dates pulled from Google Calendar, the current workpaper status, and a RAG status I can update manually. Alert me by email if any engagement is within 10 days of its deadline and still marked incomplete.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect QuickBooks to Starch as a scheduled-sync provider — Starch pulls the full entity list for each client (invoices, bills, vendors, journal entries, payments, and balance data) and refreshes it on a schedule you set.

2 Connect Gmail or Outlook so Starch can read the email thread history for each engagement and log incoming client documents against the open request list.

3 Connect Google Calendar so Starch can read filing deadlines, extension dates, and review meetings you've already entered there.

4 Tell Starch: 'Build me a workpaper workspace for [Client Name] pulling from QuickBooks. Show the trial balance with a tick column, a journal entry detail view filterable by month, and a vendor payment summary.' Starch builds it; you fork it per client in under two minutes.

5 In the same app, describe the document-request tracker: 'Add a tab where I log support requests — account, description, date requested, who requested it, and received yes/no. Flag anything open for more than 14 days.' Starch adds the tab and the logic.

6 Set up the Monday morning Outlook digest: tell Starch 'Every Monday at 8 a.m., email me a list of all open document requests across all active clients, grouped by client, sorted by days outstanding.' Starch schedules the automation.

7 Build the cross-engagement deadline dashboard: 'Show me a table of all active engagements with their due dates from Google Calendar, current workpaper status, and a color-coded completion flag I can update.' Partners get a shared link; no one needs to ask where things stand.

8 For state filing portals or client-facing document uploads that have no API, tell Starch to automate the submission through your browser — Starch navigates the portal, fills the form, and logs the confirmation number back into the workpaper app.

9 At year-end, use the Knowledge Management app to store your firm's standard workpaper templates, tick-and-tie checklists, and engagement-specific notes. New staff can search it instead of asking a senior CPA to reconstruct the process from memory.

10 After each engagement closes, tell Starch: 'Archive this client's workpaper workspace and write a one-paragraph engagement summary — what was tested, what adjustments were made, and any open items carried forward.' Store it in Knowledge Management for next year's preparer.

11 Run a final reconciliation check: tell Starch 'Compare the closing trial balance in QuickBooks against the workpaper totals I've ticked and flag any line where the amounts don't match within $1.' This replaces a manual cross-check that typically takes 45 minutes.

12 Before the engagement file is finalized, pull the Outlook thread summary: 'Summarize all email correspondence with this client since January 1 related to their audit, including document requests sent, responses received, and any open action items.' This goes into the permanent file.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Hendricks & Paoli CPA — Thornfield Medical Group 2025 Audit Workpapers, March 2026

Sample numbers from a real run

Accounts Receivable — patient billing	487,200
Medical supply vendor payments (top 10 vendors)	312,900
Payroll expense — Q4 2025	198,400
Equipment depreciation — 2025	44,700
Open journal entries requiring support	23,100

Thornfield Medical Group is a mid-sized medical practice client of Hendricks & Paoli. The engagement manager, Dana, opens the Thornfield workpaper workspace in Starch. QuickBooks has already synced overnight — the trial balance, 14 months of journal entries, vendor payment detail, and all open invoices are there. Dana sees $487,200 in accounts receivable and starts ticking: she filters journal entries to revenue recognition entries over $5,000, marks seven as supported with the reconciliation files the client sent last week, and flags three that are still open. The document-request tracker shows those three items were requested on February 18 — 22 days ago — and are highlighted in red. The Monday digest already flagged them to the partner. For the $312,900 in vendor payments, Dana tells Starch: 'Show me vendor payments over $10,000 sorted by vendor, and flag any vendor that appears in fewer than three of the last 12 months.' Two vendors flag as anomalies — both are legitimate equipment purchases, and Dana notes them as tested. The payroll reconciliation pulls Q4 payroll from QuickBooks and Dana cross-references it against the ADP summary the client uploaded. The $23,100 in unsupported journal entries is the only remaining open item. Dana sets a reminder in Starch: 'If those three journal entry support documents haven't arrived by March 12, email the client contact directly from Outlook with a follow-up.' The whole workpaper setup took 20 minutes at engagement open instead of a half-day of exports and tab-building.

Measurement

How you'll know it's working

Average hours per engagement to prepare complete workpaper file (target: under 6 hours for a mid-size client)

Open document requests outstanding more than 14 days at time of fieldwork completion

Number of audit adjustments identified during workpaper review vs. discovered post-filing

Percentage of engagements with finalized workpapers filed more than 5 days before the deadline

Staff time spent on workpaper assembly vs. actual audit judgment work (target: flip the ratio)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Karbon

Karbon is strong for workflow and client communication tracking, but it won't pull your QuickBooks trial balance, auto-reconcile journal entries, or build a tick-and-tie workpaper view — you still do the accounting assembly work manually.

TaxDome

TaxDome handles client portals, e-signatures, and tax organizers well, but the workpaper and trial balance work still happens in Excel or a separate tool — TaxDome doesn't compose data from QuickBooks into a reviewable reconciliation surface.

Excel + QuickBooks exports

This is what most four-CPA practices actually use — it works, but every engagement is a rebuild from scratch, version control is a shared filename like 'FINAL_v3_DANA.xlsx', and there's no automated deadline alerting or document-request tracking baked in.

Caseware or Thomson Reuters AdvanceFlow

Purpose-built audit workpaper platforms with strong tie-out and sign-off features, but they're priced and scoped for larger firms — a four-CPA practice is paying for complexity they don't need, and neither drafts client emails or builds cross-engagement deadline dashboards.

On Starch RECOMMENDED

One platform — transaction insights, knowledge management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch actually pull QuickBooks data, or do I have to export a CSV first?

Starch syncs your QuickBooks data directly on a schedule — invoices, bills, vendor payments, journal entries, and account balances for each client entity are pulled automatically and stored in Starch's database. No CSV exports. Note: QuickBooks' built-in report views (like P&L and Transaction List) are temporarily unavailable through the sync, but entity-level data — which is what you need for workpapers — syncs normally.

We use Outlook, not Gmail. Does the document-request tracker and digest still work?

Yes. Starch connects directly to Outlook — messages, calendars, and contacts. The Monday digest, the incoming-document logging, and any automated follow-up emails all work the same way as with Gmail.

Can I build a separate workpaper workspace per client, or is it one big combined view?

You describe what you want. You can tell Starch 'Build me a workpaper app for Thornfield Medical Group pulling only their QuickBooks entity' and then fork the same structure for each new client engagement in minutes. Each workspace is separate; you're not fighting to filter one giant view.

What about state tax filing portals that don't have an API — can Starch submit to those?

Yes. Starch automates state filing portals and any other website through your browser — no API needed. You tell Starch what to fill in and where to submit, and it navigates the site the same way a person would, then logs the confirmation back into your workpaper app.

Is Starch SOC 2 certified? Our clients ask about that for anything that touches their financial data.

Starch is not SOC 2 Type II certified yet. That's worth knowing before connecting client QuickBooks entities if your engagement letters or client contracts have specific data-handling requirements. It's on the roadmap — but we'd rather you know now than be surprised later.

We use TaxDome for client portals and document collection. Can Starch connect to that?

TaxDome is reachable through Starch's browser automation — Starch can navigate TaxDome through your browser to check document status or log received items, even without a formal API connection. If TaxDome is available as a live-query app in Starch's integration catalog of 3,000+ apps, the agent can query it directly; otherwise, browser automation covers it.

The Contract Lifecycle Management app sounds useful for engagement letters — is that available now?

Not yet. Contract Lifecycle Management is currently in development — you can request beta access to get notified when it launches. For now, you can describe a custom engagement-letter tracker to Starch and it will build it for you using your existing Outlook and Google Calendar connections.