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.
Free download · No account needed
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
| Status | What is true |
|---|---|
| Open | The item has an owner and a date. Nothing else yet |
| Tied | The schedule agrees with the trial balance, or the difference is inside tolerance and has a named cause |
| Provided | Delivered under the auditor's own number, in the format asked for |
| Accepted | The 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
| Kind | What it means | What happens |
|---|---|---|
| Schedule | The schedule was wrong | Fix it, re-run the tie, nothing leaves wrong |
| Ledger | The ledger was wrong | Proposed 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.
What's in the pack
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.
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.
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.
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.
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.
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.
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.
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.
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
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
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
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
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.
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