Finance & FP&A

How to prepare audit and tax workpapers as Professional Services Founders

Finance & FP&AFor Professional Services Founders2 apps12 steps~24 min to set up

Audit prep season means your senior consultant is rebuilding the same support schedules in Excel she rebuilt last year — pulling bank transactions from Plaid manually, reconciling against QuickBooks line items, chasing down the Stripe payout that hit the account three days after month-end. Tax workpapers live in a Google Drive folder that nobody can find, with filenames like 'final_FINAL_v3.' Your CPA asks for a vendor expense detail, and someone spends half a day formatting a QuickBooks export that still doesn't match the bank statement. At 12 people, you don't have a controller — you have a founder who knows where the bodies are buried and a bookkeeper who's done their best. Every year you say you'll build a proper workpaper package. Every year you don't.

Build this on Starch → See the apps used

Finance & FP&AFor Professional Services Founders2 apps12 steps~24 min to set up

Outcome

What you'll set up

A living audit workpaper that pulls categorized transactions from Plaid and entity-level data from QuickBooks — reconciled, formatted, and ready to hand to your CPA without a spreadsheet relay race.

A spend anomaly layer that flags vendors, amounts, or timing that look out of place before your auditor asks about them — so you're explaining context, not discovering surprises.

A searchable repository of supporting documents, prior-year workpapers, and chart-of-accounts notes that your team (or a new hire) can actually find in under 60 seconds.

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 Plaid bank transaction data and your QuickBooks invoices, bills, payments, vendors, and journal entries on a schedule — so both sources are current when any workpaper app or dashboard runs. For document storage and search, Starch connects directly to your Notion workspace so prior-year workpapers and CPA notes are indexed and searchable alongside live transaction data. If your CPA uses a portal that requires manual upload, Starch automates that through your browser — no API needed.

Prompts to copy

Pull every transaction from my connected Plaid accounts for Q4 2025, categorize them by vendor and expense type, and flag any transaction over $5,000 or any vendor that appears fewer than three times this year as needing a supporting note.

Cross-reference my Plaid transactions against QuickBooks invoices, bills, and payments for the same period. Show me any amount that appears in one source but not the other, and any timing difference greater than 5 days between a Stripe payout and its corresponding bank deposit.

Build me a workpaper index for the 2025 tax year — list each schedule (cash reconciliation, vendor detail, payroll summary, fixed asset additions), what data source populates it, who owns it, and whether it's complete.

Store all my audit support documents — bank statements, prior-year workpapers, CPA correspondence, signed engagement letters — in a searchable knowledge base organized by tax year and document type.

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

Walkthrough

Step-by-step

1 Connect Plaid and QuickBooks: Starch syncs your bank transactions (categorized, with institution and balance data) and your QuickBooks entity data — invoices, bills, payments, vendors, journal entries — on a schedule. Both sources refresh automatically, so you're not manually exporting anything.

2 Open Transaction Insights and set the date range to your audit period (e.g., January 1 – December 31, 2025). The app surfaces every transaction by category and vendor, with month-over-month trend lines and automatic anomaly flags for amounts or vendors that look out of pattern.

3 Tell Starch: 'Flag every transaction over $5,000 with no corresponding QuickBooks bill or invoice, and every vendor that billed us more than twice what they billed in the prior year.' This becomes your first auditor question list — built before your CPA even sends the PBC request.

4 Run the cross-source reconciliation prompt: ask Starch to compare Plaid deposits against Stripe payouts for the same period and surface any timing gap greater than five days or any payout with no matching transaction in QuickBooks. This catches the classic Stripe-to-bank timing issues that throw off cash reconciliations.

5 Build the payroll workpaper: if you run payroll through Paylocity or ADP, Starch syncs payroll runs, employee records, and benefit data on a schedule. Ask Starch to reconcile total payroll disbursements against QuickBooks payroll expense journal entries by month and flag discrepancies.

6 Generate the vendor expense detail schedule: tell Starch, 'Give me a vendor-by-vendor summary of all bills and payments in QuickBooks for 2025, sorted by total spend, with a column for whether we have a W-9 on file.' The W-9 column is a manual field you populate — but the rest is automated.

7 Set up Knowledge Management with your Notion connection: Starch connects directly to your Notion workspace and indexes all your existing pages and databases. Drop your prior-year workpapers, CPA engagement letters, chart-of-accounts documentation, and audit notes into a dedicated Notion section. Starch makes it searchable in plain English — 'find the 2024 fixed asset schedule' returns the right page in seconds.

8 Build a workpaper index app: tell Starch, 'Create a tracker that lists every workpaper schedule for the 2025 tax year, the data source that populates it, the team member responsible, the current status (not started / in progress / complete / reviewed), and the date it was last updated.' This becomes your audit project manager.

9 Set up a weekly automation: 'Every Monday, check whether any new vendor has charged my Plaid-connected accounts in the past 7 days that doesn't appear in QuickBooks as a bill or vendor record, and Slack me a summary.' This keeps the books clean through the year, not just at close.

10 When your CPA sends the PBC (prepared-by-client) list, paste it into Starch: 'Map each item on this PBC list to the workpaper or data source in my setup that covers it, and flag anything we don't have a clear answer for.' You get a coverage map before you've opened a single spreadsheet.

11 For supporting documents that need to be uploaded to your CPA's portal, Starch automates the upload through your browser — no API needed. Describe the portal, the file naming convention your CPA wants, and Starch handles the repetitive uploading.

12 At sign-off, archive the complete workpaper package: tell Starch to export the final reconciliations, anomaly notes, and index to a dated Notion page structured as '2025 Audit Workpapers — Final.' Next year, this becomes the prior-year reference your team actually finds.

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

2025 Annual Audit Prep — 12-Person Strategy Consultancy, March 2026 Close

Sample numbers from a real run

Plaid transactions synced (full year)	1,847
QuickBooks bills and payments matched	312
Unmatched transactions flagged for review	23
Vendors over $10k with no W-9 on file	4
Stripe-to-bank timing gaps over 5 days	7
Hours saved vs. prior-year manual process	18

In March 2026, the firm's founder connected Plaid (two operating accounts, one credit card) and QuickBooks (entity data syncing on a schedule) and ran the cross-source reconciliation. Starch surfaced 23 transactions in Plaid with no corresponding QuickBooks entry — 16 were credit card charges that the bookkeeper had categorized to a different period, 5 were bank fees that had never been recorded, and 2 were a duplicate payment to a vendor that had already been partially credited. Finding those 2 duplicates alone recovered $3,400. The W-9 screen flagged four vendors paid more than $10,000 in 2025 with no 1099-eligible documentation on file — two of them were individuals the firm had been treating as LLC vendors without verifying their entity status. The CPA's PBC list had 31 line items; Starch mapped 27 to existing workpapers or data sources automatically, leaving 4 items that needed manual pulls (two prior-year comparison schedules and two signed client contracts). The founder uploaded those 4 items to the CPA's portal using browser automation rather than doing it manually. Total time from 'connect the integrations' to 'hand the package to the CPA': one afternoon for the founder and about 3 hours for the bookkeeper to clear the flagged items — versus the prior year's two-week scramble.

Measurement

How you'll know it's working

Days from fiscal year-end to complete PBC package delivery to CPA

Number of unmatched transactions between bank and QuickBooks at close (target: zero)

Vendors paid over $600 without a W-9 on file going into 1099 season

Audit adjustment entries required after initial CPA review (measures workpaper accuracy)

Hours of senior staff time spent on audit prep vs. billable client work

Comparison

What this replaces

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

QuickBooks + manual Excel reconciliation

QuickBooks holds the accounting records, but cross-referencing against bank data, building support schedules, and flagging anomalies still requires someone to pull exports and build formulas — Starch automates the comparison and surfaces exceptions without that manual layer.

Keeper or Botkeeper

Designed for accounting firms managing multiple client books, not for a founder who needs to prep their own workpapers and hand them off — the workflow and pricing assume a different user.

Notion + Google Drive folder system

Good for storing documents, but there's no live data connection, no cross-source reconciliation, and 'searchable' depends entirely on how disciplined your team was about naming files — Starch adds AI search and live data on top of what you're already putting in Notion.

Karbon or Financial Cents

Workflow management tools built for CPA firms managing clients, not for the operator founder who is the client — feature set is oriented toward the accountant's side of the relationship, not your side.

Hiring a fractional controller at $150–$200/hr for audit season

Fractional controller brings judgment that Starch doesn't replace — but the hours they'd spend pulling and formatting data can be cut significantly before they ever sit down, which means you're paying for their expertise instead of their spreadsheet time.

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 have access to my QuickBooks data, or does it just connect to it?

Starch syncs your QuickBooks data on a schedule — invoices, bills, payments, vendors, and journal entries all land in Starch's database and refresh automatically. There is a current limit: QuickBooks report views like the P&L and Transaction List are temporarily unavailable due to an upstream connector issue, but entity-level data (the individual bills, invoices, payments, and vendors) syncs normally. For most audit workpaper work — reconciliations, vendor detail, payment matching — that's the data you actually need.

What if my CPA uses a specific client portal that doesn't have an API?

Starch automates browser-based workflows through your browser — no API needed. If your CPA's portal is a website you log into and upload files to, Starch can handle the upload workflow. Describe the portal and the file naming convention your CPA wants, and Starch automates the repetitive part.

Is Starch SOC 2 certified? My CPA and some enterprise clients ask about that.

Not yet — Starch is not SOC 2 Type II certified today. That's worth knowing upfront. If a client engagement requires SOC 2 certification from all your software vendors, that's a real constraint. Most 12-person consultancies preparing their own internal workpapers aren't blocked by this, but it's an honest limit.

We use Xero instead of QuickBooks. Does that work?

Xero is available through Starch's integration catalog of 3,000+ apps — the agent queries it live when your workpaper apps run. It's not a scheduled-sync provider the way QuickBooks is, so Xero data is queried on demand rather than pre-synced to Starch's database. For most reconciliation workflows that's fine; just know the data isn't pre-cached.

Can Starch handle the actual accounting — making journal entries, correcting coding errors in QuickBooks?

No. Starch reads and analyzes your QuickBooks data (read-only sync) and surfaces what needs attention, but it doesn't write back to QuickBooks. The corrections still happen in QuickBooks — Starch just tells you clearly where to look and what to fix, so the time your bookkeeper spends is on actual decisions rather than hunting for discrepancies.

What about Contract Lifecycle Management — I've seen that listed on Starch?

Contract Lifecycle Management is currently in development — it's coming soon, not available today. You can request beta access to get notified when it launches. For now, the Knowledge Management app with your Notion connection is the practical way to store, organize, and search your contracts and engagement letters.

How long does setup actually take for a firm our size?

Connecting Plaid and QuickBooks takes about 15 minutes — OAuth connections, then Starch starts syncing. Building the first reconciliation app (describe what you want in plain English, Starch assembles it) takes another 30–60 minutes to tune the prompts and get the output formatted the way your CPA expects. The Knowledge Management setup with Notion is a one-time indexing step. Most founders at your stage have a working workpaper draft in an afternoon.