River
Y CombinatorBacked by Y Combinator
Log InStart Free
FREE TEMPLATE

Audit Preparation Checklist Template

Three documents and four sheets, kept under the auditor's own numbering, where an item cannot be marked provided until its schedule ties to the ledger.

Edit with AIDownload (.docx + .csv)

Free download  ·  No account needed

What you get

Pack of 7 files: 3 documents, 4 spreadsheets

Audit Preparation Checklist Template
  • PBC Response ProcedureDocument
  • Readiness MemoDocument
  • Management Representation NotesDocument
  • PBC TrackerSpreadsheet
  • Open ItemsSpreadsheet
  • Tie Out LogSpreadsheet
  • Lead Schedule IndexSpreadsheet
RiverAudit Preparation Checklist Template

PBC Response Procedure

[Entity] — the gate every schedule passes

An item that supports a trial balance line is not ready to send until it agrees with that line.

Four statuses, and Tied cannot be skipped

StatusWhat is true
OpenThe item has an owner and a date. Nothing else yet
TiedThe schedule agrees with the trial balance, or the difference is inside tolerance and has a named cause
ProvidedDelivered under the auditor's own number, in the format asked for
AcceptedThe auditor has said they have what they need

Open straight to Provided is not a permitted move. Items with nothing to tie to, meaning minutes, contracts and policies, skip Tied and are marked as having skipped it.

The tie

schedule total−trial balance balance=difference

Recorded even when it is zero, because a blank difference column is indistinguishable from an untested one. Tolerance is set per line against a stated basis before fieldwork, so the threshold cannot move later to admit a difference somebody would rather not resolve.

Two kinds of cause, and the split is the output

KindWhat it meansWhat happens
ScheduleThe schedule was wrongFix it, re-run the tie, nothing leaves wrong
LedgerThe ledger was wrongProposed adjusting entry, sent with the schedule

Tolerance is not materiality. The auditor sets their own threshold and may ask about a difference this gate accepted. The named cause is the answer.

Every audit preparation checklist on page one has the same three columns: the request, an owner, a status. The better ones add a document reference or a reviewed box, and the firm-written guides walk the same fourteen areas from cash down to equity. All of them treat a request as finished when it is sent. That is why an item gets marked done in January, comes back in February, and gets marked done again, with nobody counting how often.

Here an item that supports a trial balance line cannot reach Provided until the schedule agrees with that line, inside a tolerance written down before fieldwork, with one named cause from a closed list of eight. Kestrel Valve and Fitting, an illustrative industrial distributor, ran 61 of its 148 requests through that gate. Twenty did not tie, 1,808,540 of gross difference, and 17 of the twenty were outside their own tolerance. The other three still needed a cause.

Fourteen of the twenty were the schedule being wrong, so they were fixed before anything was sent. Six were the ledger being wrong, which is 205,950 of proposed adjustments and 169,050 off pre-tax income, handed over rather than found. An auditor has to test the accuracy and completeness of what a company produces, and separately obtain written representations from management. Get the trial balance into one shape first, because the tie means nothing against a balance still moving.

One audit through the gate, item by item

The closed list of causes, the twenty differences, two reconciliations in full, the adjustments found and the returns either side.

Audit Preparation Checklist Template
RiverCauses

The closed list of eight

Kestrel Valve and Fitting, Inc. FY2026 audit. An illustrative industrial valve and fitting distributor.

#CauseKindItems
1Subledger extract taken before late postingsSchedule3
2Manual journal not in the subledgerSchedule3
3Reclassification between accountsSchedule2
4Adjusting entry not yet postedLedger5
5Extract filter wrong: dates, entity or statusSchedule2
6Schedule arithmetic errorSchedule3
7Account mapped to the wrong statement lineSchedule1
8Genuine ledger errorLedger1

What the first internal pass found

Items on the auditor's list, numbering as issued148
Items carrying a tie to a trial balance line61
Documents with nothing to tie to87
Items that did not tie on the first pass20
Gross absolute difference, before anything was sent1,808,540
Outside their own tolerance17 of 20
The schedule was wrong14 items, 1,602,590
The ledger was wrong6 items, 205,950

One cause per difference, never two. A difference with two causes is two differences and gets decomposed until each part has one.

RiverTie out log

Tie Out Log

Every difference found on the first internal pass, against the tolerance set before fieldwork.

ItemTrial balance lineDifferenceToleranceOverCause
A-03Operating cash14,26012,022yes1
B-01Accounts receivable, net275,75029,542yes2
B-04Allowance for doubtful accounts16,2005,000yes4
C-02Inventory233,36038,045yes2
C-05Inventory reserve(27,500)5,000yes4
C-08Work in process6,1205,994yes6
D-01Prepaid expenses31,8405,000yes1
D-03Other current assets(9,600)5,000yes7
E-01Property, plant and equipment214,80092,136yes5
E-04Accumulated depreciation(48,220)46,834yes2
E-07Construction in progress386,5005,379yes3
F-01Accounts payable(62,140)21,406yes1
F-05Accrued purchases18,4505,000yes4
G-02Accrued compensation74,6005,000yes4
G-06Accrued warranty42,8005,000yes8
H-03Operating lease liability118,90015,338yes6
I-02Additional paid in capital3,20062,384no6
J-01Net revenue186,200240,151no3
J-06Deferred revenue26,4005,000yes4
K-02Payroll expense11,70045,864no5
20Gross absolute difference1,808,540 17 over6 ledger

Three differences sat inside tolerance and still carry a cause. An unexplained small difference is the one that grows.

RiverReconciled

Two reconciliations in full

A single difference number is not a tie. B-01 and C-02 each decompose into components that each have one cause.

B-01 Accounts receivable, net

ComponentAmountRunningCause
AR aging total, subledger6,184,2206,184,220Start
Allowance for doubtful accounts, booked at the GL only(214,600)5,969,6202
Credit memos issued 30 and 31 Dec, not applied in the aging(38,150)5,931,4701
Unapplied cash receipts held in suspense(23,000)5,908,4703
Trial balance, accounts receivable net5,908,4700Tied

C-02 Inventory

ComponentAmountRunningCause
Perpetual inventory, subledger7,842,3007,842,300Start
Obsolescence reserve booked at the GL only(186,000)7,656,3002
December standard cost revaluation, manual journal(88,560)7,567,7402
Goods in transit FOB shipping point, received in January41,2007,608,9401
Trial balance, inventory7,608,9400Tied

The 275,750 on B-01 is not one problem. It is a reserve that lives only in the ledger, two late credit memos and a suspense account, and only the second of those is a schedule defect.

RiverAdjustments

What the ledger causes became

Six of the twenty differences were the ledger, not the schedule. Those are proposed adjusting entries.

ItemProposed entryPre-tax
B-04Allowance understated against the aged balances(16,200)
C-05Inventory reserve understated on slow moving valve bodies(27,500)
F-05Accrued purchases overstated, two receipts double accrued18,450
G-02Accrued compensation understated, Q4 bonus at the revised rate(74,600)
G-06Warranty accrual understated against the claims history(42,800)
J-06Deferred revenue understated, one installation not yet accepted(26,400)
 Net effect on pre-tax income(169,050)

What that does to the year

Pre-tax income before the adjustments4,182,600
After the adjustments4,013,550
Reduction4.04 percent
Gross adjustments across the six205,950

Same six entries either way. Handed over with the schedules they belong to, they are evidence the close works. Found by the engagement team in week two, they are a finding about the close, and every remaining schedule gets read differently afterwards.

RiverReturns

Returns, either side of the gate

FY2025 was run on a status tracker. FY2026 was run through the tie-out gate.

 ItemsCame backReturn rateAccepted first pass
FY20251523825.0%75.0%
FY202614896.1%93.9%

The 38 FY2025 returns, in the auditor's own words

Stated reasonCountShare
Schedule did not agree to the trial balance2155.3%
Wrong period or entity in the extract718.4%
Item incomplete, a component missing615.8%
Format the auditor could not use410.5%

Twenty one of the 38, 55 percent, were the one thing the gate tests. Those are the returns that arrive in fieldwork week two, when the schedule owner has moved on to something else and the trial balance has been closed for a month.

The return log is the only forward-looking artifact here. Every other number says what happened this year. The reasons say what to fix before next year, and the count is the argument for keeping the gate when somebody proposes skipping it to save a week.

Edit with AI

What's in the pack

01

PBC Tracker sheet

One row per request under the auditor's own number, with the request in their wording, the owner, whether a tie is required, the schedule total, the trial balance balance, the difference, the tolerance, the cause and the return count. The tie columns are what makes the status column mean something.

02

Space rule

An item is not provided until it ties. Four statuses with Tied unskippable, the difference recorded even at zero, tolerance set against a written basis before fieldwork, one cause per difference from a closed list of eight, and the schedule against ledger split. It governs every prompt here.

03

Tie Out Log sheet

Where a difference stops being one number. Each reconciling component gets its own row, its own amount, its own cause and a running balance down to the trial balance, so a 275,750 gap resolves into a ledger-only reserve, two late credit memos and a suspense account.

04

Lead Schedule Index sheet

One row per trial balance line: the balance, the tolerance and the basis it came from, the owner, how many items point at it and how many differences it produced. The account-level support underneath belongs in the balance sheet substantiation pack.

05

PBC Response Procedure

How the list gets processed. Numbering discipline, the tolerance basis, the eight causes and what each one obliges you to do, owner assignment by schedule, the sequence a single item moves through, return handling, and the four triggers that escalate to the engagement partner.

06

Open Items sheet

What is still outstanding, whether the blocker is internal or a third party, the date it was requested and the last action taken. Third-party rows are the ones that slip, and the letters and follow-up schedule behind them come from the confirmation tracker.

07

Readiness Memo

What the engagement team opens first. Items provided, differences accepted inside tolerance with their causes, the proposed adjustments with the net pre-tax effect, open items with owners and dates, and last year's return reasons. The filing dates it protects sit in the covenant reporting pack.

08

Management Representation Notes

The representations grouped as they usually arrive: financial statements, information provided, fraud, estimates and related parties. Each carries who can actually affirm it and the evidence behind it, drafted from what the tie-out found rather than from last year's letter.

09

Owner chasers

The space chases item owners on the dates their items are due, and the message names the item number, the balance it has to tie to and what is missing. A chase that says an item is overdue tells the owner nothing they did not know.

How to use it

  1. 1

    Take the files, or open the pack

    Download the three documents and four sheets as Word and CSV with no account. Or open the pack in River and hand it the auditor's list, and the tracker builds itself under their numbering.

  2. 2

    Send the request list and the trial balance

    The list in whatever form it arrived, a spreadsheet, a PDF, a portal export or the body of a mail. The trial balance can be a draft, and the tie reruns against the final. Normalising it first helps, which is what the close pack already produced.

  3. 3

    Run the tie-out before anything is sent

    Every item supporting a balance is reconciled against it, and each difference gets one cause. Schedule causes get fixed. Ledger causes become proposed entries with their pre-tax effect, and go over with the schedule they belong to.

  4. 4

    Provide, then log every return

    Items move to Provided under the auditor's own number, and to Accepted when they say so. Anything that comes back is logged with the auditor's stated reason in their words, because that record is what changes next year's preparation.

Frequently asked questions

Is this template free?

Yes. The three documents and four sheets download as Word and CSV with no account, no card and no trial. The optional Edit with AI path exists for people who would rather hand over the auditor's list and the trial balance than remap 148 rows by hand. The rest of the library is at free templates.

Our tolerance is not the auditor's materiality. Does that matter?

No, and the pack never claims otherwise. Tolerance here is an internal gate for deciding what to resolve before sending. The auditor sets their own threshold, it may be lower, and they may ask about a difference you accepted. The named cause is the answer to that question, which is why every difference gets one even inside tolerance.

What if the schedule is right and the ledger is wrong?

Then it is not a schedule problem. Six of the eight causes mean the schedule was wrong and you fix the schedule. The other two mean the ledger was wrong, and those become proposed adjusting entries. Six items landed there in the worked example, 205,950 gross and 169,050 off pre-tax income, handed over with the schedules rather than found in week two.

Do I have to keep the auditor's numbering?

Yes, and it is the cheapest rule here to follow. Item C-04 stays C-04 in the tracker, the file name, the folder and the mail subject, because the moment the two sides cannot name the same thing every question becomes a paragraph of description. If a request genuinely covers two things, ask them to split it.

Most of our items are documents, not schedules. Does the gate apply?

No. Board minutes, contracts, policies and narratives have nothing to tie to, so they skip Tied and go from Open straight to Provided. The tracker marks which ones did, because a gate most items bypass has to show that plainly. In the worked example 87 of 148 were documents and 61 carried a tie.

Does this replace the close, or the controls documentation?

Neither. The year end close drafts the statements this gate ties to, and the control narratives your auditor asks for in the same window come out of the segregation of duties review. This space starts the day the request list arrives and ends when the last item is accepted.

Why count returns? The audit is over by then.

Because the return log is the only forward-looking thing the process produces. Everything else says what happened this year. In the worked example 21 of the prior year's 38 returns were schedules that did not agree with the trial balance, which is 55 percent of the rework this one gate removes.

Sources

  1. PCAOBTest the accuracy and completeness (opens in a new tab)
  2. PCAOBObtain written representations (opens in a new tab)

Written by

Chandler Supple

Co-founder & CEO, River

Chandler has spent the last six years working in AI, building tools for millions of users and Fortune 100 companies. In 2025, he co-founded River to build a new kind of operating system for AI agents.

LinkedInGitHubX

Reviewed by

Brian Joseff, Co-founder, River

LinkedInX

Related workspaces

Audit confirmation tracker

The bank, customer and legal confirmations that sit on the same request list and run on different rules.

Balance sheet substantiation pack

The account-level support underneath each lead schedule, built before the request list arrives.

Segregation of duties review

The controls half of the same fieldwork, tested against the transactions each conflict actually reaches.

More free templates

Accounting Policy Manual Template

Free accounting policy manual template. Every policy cites its real source, a memo or the chart of accounts, and keeps its own review date, not the manual's.

Audit Finding Remediation Plan Template

Free audit finding remediation plan template. Builds the register from your letter; a finding closes once the fix is proven, not asserted.

Audit Lead Schedule Template

Free audit lead schedule template. Builds schedules from your trial balance, with reference codes that carry forward instead of getting reissued.

Internal Controls Documentation Template

Free internal controls documentation template. Puts each control on the exact narrative step it protects, then carries the same code into testing and severity.

Tie it before you send it

Download the blank pack as Word and CSV files, or open this exact pack in River and let it load the auditor's list and run the tie-out against your trial balance.

Edit with AI