Finance & FP&A

How to prepare audit and tax workpapers as Small Finance Teams

Finance & FP&AFor Small Finance Teams2 apps12 steps~24 min to set up

At close, your three-person team is pulling trial balances out of NetSuite or QuickBooks, copying journal entry detail into a workpaper template someone built in Excel two years ago, and then manually tying every number back to source. Auditors want a lead schedule for every balance sheet account, a flux analysis with explanations, and a tidy folder of support. You're exporting the same GL data four different times into four different tabs. A single auditor comment kicks off another two hours of re-tracing. Tax season layers on top: you're pulling categorized transaction detail out of Plaid or Stripe to support Schedule C items, reconciling bank deposits to revenue, and hunting down the Q4 prepaid amortization entry that got buried. There is no system. There's a folder in Google Drive and institutional memory.

Build this on Starch → See the apps used

Finance & FP&AFor Small Finance Teams2 apps12 steps~24 min to set up

Outcome

What you'll set up

A live workpaper hub that auto-pulls from your QuickBooks or NetSuite GL on a schedule — lead schedules, account reconciliations, and flux commentary generated from actual numbers, not copied-and-pasted exports

A transaction-level support package that ties every material balance sheet account to categorized Plaid or Stripe activity, ready to hand to an auditor or CPA on demand

An audit-trail log that documents what changed, when, and why — so when an auditor asks 'why did accounts payable move $48K quarter-over-quarter,' you have the answer in two clicks, not two hours

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 — invoices, bills, payments, vendors, journal entries, and all entity-level GL data refresh automatically and live in Starch's database. Starch also syncs your Plaid transaction and balance data on a schedule, giving you categorized bank activity tied to the same period. For teams on NetSuite, Starch syncs invoices, expenses, journal entries, balance sheets, and income statements on the same scheduled basis. Supporting schedules that reference Notion documentation (workpaper notes, prior-year adjustments) pull from Notion via Starch's scheduled sync. Any government filing portal or auditor document portal that doesn't have an API can be automated through your browser — no API needed.

Prompts to copy

Pull all QuickBooks transactions for accounts 2000–2999 (current liabilities) for the period October 1 – December 31, 2025. Group by account, show opening balance, total debits, total credits, and ending balance. Flag any account where the ending balance moved more than 20% versus the prior quarter and add a column for me to type in the explanation.

Build me a workpaper index that lists every balance sheet account we need to reconcile for the Q4 2025 audit, shows the GL balance from QuickBooks, the tied balance from our support doc, and a status column (open / tied / reviewed). Auto-populate the GL balance column from our synced QuickBooks data.

Show me every Plaid transaction tagged as 'Professional Services' between January 1 and December 31, 2025, sorted by vendor and then by date. I need this as a support schedule for our tax prep — flag any vendor where total annual spend exceeded $600 so I know who needs a 1099.

Create a flux analysis table for our income statement accounts comparing Q3 2025 actual vs Q4 2025 actual vs Q4 2024 actual. Pull from QuickBooks. For any line item where the quarter-over-quarter variance exceeds 15%, add a blank 'Management Explanation' field I can fill in.

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

Walkthrough

Step-by-step

1 Connect QuickBooks or NetSuite so Starch syncs your GL data on a schedule — entity-level data (invoices, bills, payments, vendors, journal entries) refreshes automatically and is available for every workpaper you build.

2 Connect Plaid so Starch syncs your bank transactions on a schedule — categorized activity from every account feeds the cash and revenue reconciliation workpapers without manual export.

3 If you use Stripe for revenue, connect Stripe so Starch syncs charges, invoices, and payouts — this is your audit support for recognized revenue and the tie-out to your bank deposits.

4 Tell Starch to build your balance sheet lead schedule: describe the accounts, the period, and the variance threshold you want flagged. Starch pulls from your synced GL and generates the lead schedule with opening balances, movements, and ending balances.

5 For each material account (AR, AP, prepaids, accrued liabilities), tell Starch to build a supporting reconciliation that ties the GL balance to your transaction detail — Plaid for cash, Stripe for AR, QuickBooks AP subledger for payables.

6 Build your flux analysis by telling Starch which periods to compare and what variance percentage triggers a flag. Starch generates the table; you type explanations directly into the management commentary column it creates for you.

7 Use Knowledge Management — available in the Starch App Store — to store your workpaper methodology notes, prior-year adjustments, and auditor PBC (prepared by client) responses so the whole team has context, not just the person who did it last year.

8 For 1099 prep, tell Starch to pull all Plaid transactions categorized as contractor or professional services payments over the year, group by vendor, and flag every vendor above $600 — this replaces the manual export-and-sort step that currently takes half a day.

9 When auditors send comments or open items, log them directly into your workpaper hub in Starch and assign status. Because the underlying data is live-synced, re-running a schedule after an adjustment is a prompt, not a re-export.

10 For tax workpapers, build a transaction support package by telling Starch to pull all Plaid and Stripe activity for the fiscal year, organized by tax category, with totals by category and flagged anomalies — hand this directly to your CPA.

11 At year-end, tell Starch to generate a workpaper index listing every account reconciled, the tie-out status, and the name of the support schedule — this is your PBC list and your audit binder table of contents in one step.

12 Archive the finalized workpaper set by saving all Starch-generated schedules and your management commentary to Notion via the scheduled sync, so next year's team (or a new hire) can open last year's binder without asking you to explain it.

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

Q4 2025 Audit Prep — 200-person SaaS company, December 31 fiscal year-end

Sample numbers from a real run

Cash (Plaid tie-out to GL)	1,842,300
Accounts Receivable (Stripe invoices vs. GL)	614,750
Prepaid Expenses (QuickBooks schedule)	88,200
Accounts Payable (QuickBooks AP subledger)	203,400
Accrued Liabilities (manual + GL tie)	97,600
Deferred Revenue (Stripe subscriptions)	441,000

Your auditors have a January 20 fieldwork start date. On January 3, you tell Starch: 'Build a balance sheet lead schedule for all accounts as of December 31, 2025, pulling from QuickBooks. Show prior-year balance, current-year balance, dollar change, and percentage change. Flag anything over 15% variance.' Starch pulls from your synced QuickBooks data and generates the full lead schedule in minutes — you get a table showing, for example, that Deferred Revenue jumped $441K to $441K from $312K, a 41% increase that will absolutely get an auditor question. You fill in the explanation column: 'Annual subscription renewal cohort shifted to Q4; see Stripe invoice detail.' For cash, you tell Starch: 'Reconcile our QuickBooks cash balance of $1,842,300 to Plaid bank activity as of December 31. Show any timing differences.' It pulls both synced data sets and flags a $4,200 deposit-in-transit that cleared January 2. For AR, you tell Starch: 'Show all open Stripe invoices as of December 31 with customer name, invoice date, due date, and amount. Tie to QuickBooks AR balance of $614,750.' The tie-out takes 20 minutes instead of the usual day-and-a-half of export, paste, VLOOKUP. For 1099s running concurrently, you tell Starch: 'Pull all Plaid transactions tagged as Professional Services or Contractors for calendar year 2025, group by vendor, sum by vendor, flag vendors over $600.' You get the list immediately — 14 vendors, three of which you didn't realize crossed the threshold.

Measurement

How you'll know it's working

Days to deliver PBC (prepared-by-client) list after auditor engagement letter — target under 3 business days

Number of auditor open items at fieldwork start — teams using Starch target fewer than 5 vs. the industry norm of 15–20 for companies this size

Hours spent on workpaper preparation per close cycle — baseline for most 3-person teams is 60–80 hours; manual reconciliation is the biggest driver

Percentage of balance sheet accounts with tied, documented support vs. 'pending' at fieldwork kickoff

1099 filing accuracy rate — vendors correctly identified and amounts matched to source transactions before CPA handoff

Comparison

What this replaces

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

Excel + manual GL exports

You own every formula and every export step; one stale export or broken VLOOKUP quietly corrupts the workpaper, and there's no audit trail showing when data was pulled or who changed what.

Floqast or Blackline

Purpose-built close management tools with good reconciliation workflows, but they're priced for larger finance teams, require IT implementation, and don't let you build custom schedules in plain language — you get their templates, not yours.

Your ERP's native reports (NetSuite, QuickBooks)

Great for ledger work; terrible at producing the auditor-ready lead schedules, flux analyses, and cross-system tie-outs that actually take up your time — and QuickBooks P&L report views are currently limited in Starch too (entity-level data syncs fine; report views are a known constraint).

Outsourced bookkeeper + CPA firm handling workpapers

Takes the work off your plate entirely but removes your team's visibility into where numbers come from, makes late audit adjustments more expensive, and doesn't help you answer the CFO's mid-close questions any faster.

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 sync QuickBooks P&L and balance sheet report views?

Honest answer: QuickBooks report views — P&L, Transaction List, Vendor Expenses — are temporarily disabled in Starch pending an upstream fix. Entity-level data syncs normally: invoices, bills, payments, vendors, journal entries, and account balances. In practice, this means Starch can build your lead schedules and flux analyses from entity-level data, but it can't pull a pre-formatted QuickBooks P&L report directly. For most audit workpaper needs, the entity-level sync is what you actually need.

Can Starch access our NetSuite instance?

Yes. Starch syncs your NetSuite data on a schedule — invoices, expenses, journal entries, balance sheets, and income statements. If your team runs NetSuite as the system of record, workpapers pull from the same synced dataset as everything else you build in Starch.

We use Ramp or Bill.com for AP — can Starch pull that data?

Ramp and Bill.com are reachable through Starch's integration catalog of 3,000+ apps; the agent queries them live when your workpaper or automation needs the data. If you want to reconcile AP in Ramp against your QuickBooks AP subledger, you tell Starch what you want and it queries both. Note that live-queried apps are not stored in Starch the way scheduled-sync providers are — data is fetched on demand rather than archived.

Is this SOC 2 certified? Our auditors will ask.

Starch is not currently SOC 2 Type II certified. If your auditors require a SOC 2 report from every tool that touches financial data, that's worth flagging before you connect your QuickBooks or NetSuite instance. It's on the roadmap; we'd rather you know now than find out at fieldwork.

Can Starch submit files directly to our auditors' portal?

If your auditors use a document portal that's accessible through a browser — most do — Starch can automate uploads through browser automation, no API needed. You'd tell Starch: 'Log into the auditor portal and upload these support files to the open items folder.' If the portal requires specific credentials or MFA, you'll walk Starch through that setup once.

What happens if the auditors come back with adjustments after we've built the workpapers?

Because your underlying data is live-synced from QuickBooks, NetSuite, Plaid, and Stripe, re-running a schedule after a journal entry adjustment is a prompt, not a rebuild. You tell Starch 'refresh the AP lead schedule as of December 31 with the corrected accrual' and it re-pulls. You're not re-exporting and re-pasting.

We have a new hire joining the team right after audit. Can any of this help with knowledge transfer?

Yes — this is one of the cleaner use cases for Knowledge Management in the Starch App Store. Store your workpaper methodology, recurring audit adjustments, auditor contact notes, and PBC checklist in one searchable place. The AI surfaces answers across all your docs, so a new hire can find 'how do we handle the deferred revenue roll-forward' without asking you every time.