---
title: "Audit PBC List Template: What to Prepare for Your Auditors"
url: "https://goremy.ai/blog/articles/audit-pbc-list-template-prepare-for-your-external-audit"
author: Luis Chavez-Mattos
editor: Luis Chavez-Mattos
editor_title: Director, Product
published: "2026-11-20T05:40:17.306Z"
updated: "2026-11-20T05:40:17.306Z"
topic: Accounting and Month-End Close
description: "A copy-ready audit PBC list template by area, a worked example, and an AI prompt that rolls last year's request list forward so you start the audit ahead."
---

# Audit PBC List Template: What to Prepare for Your Auditors

> A copy-ready audit PBC list template by area, a worked example, and an AI prompt that rolls last year's request list forward so you start the audit ahead.

Edited by Luis Chavez-Mattos, Director, Product · Published 2026-11-20

## What is an audit PBC list?

A PBC list ("prepared by client," sometimes "provided by client") is the request list your external auditors send before and during an audit. It names every schedule, report, contract, and support document they need from your company, who owns each item, and when it is due. Controllers usually receive it from the audit firm, then assign each line to someone in accounting, tax, treasury, HR, legal, or IT and track it until every item is delivered.

## TL;DR

- A PBC list is a **tracker of documents the auditors need**, so build it as a tracker with owners, due dates, and statuses, not as a flat list.
- Most of the list repeats every year, so **start from last year's final list**, not from the auditor's blank request.
- Group requests by area (cash, revenue, payables, fixed assets, debt, equity, payroll, tax, legal, controls) and give every area one named owner.
- Every schedule you hand over should **tie to the trial balance**. Untied schedules are the top cause of follow-up questions.
- AI is useful for **rolling the list forward and drafting status emails**. It should not produce numbers, support, or descriptions of your controls.
- Agree with the audit team early on **file naming, delivery method, and sample selection** so documents are not re-sent.

## What goes on an audit PBC list? (the template)

Every audit firm has its own format, and yours will arrive with its own reference numbers. The structure below covers what most external audits of a mid-size or large company ask for. Use it as your internal master, then map your auditor's reference numbers into the first column.

### Tracker columns

Set these up in a spreadsheet or tracker once, and use them for every section.

| Ref | Request | Format / period | Owner | Reviewer | Due date | Status | Date sent | Auditor comments |
|---|---|---|---|---|---|---|---|---|

Status values to use: Not started, In progress, In review, Sent, Follow-up from auditor, Closed.

### 1. General and financial reporting

| Ref | Request | Format / period |
|---|---|---|
| G-1 | Final trial balance, with prior year comparative | Excel, year-end, mapped to financial statement lines |
| G-2 | Draft financial statements and footnote support | Current draft, with tie-out to the trial balance |
| G-3 | General ledger detail | Full year, all accounts, export from ERP |
| G-4 | Listing of all manual journal entries | Full year, with preparer, approver, date, and description |
| G-5 | Post-closing and top-side adjustments | Full year, with support |
| G-6 | Chart of accounts and any changes in the year | Current, with change log |
| G-7 | Organization chart and list of legal entities | Current, with ownership percentages |
| G-8 | Board and committee minutes | Fiscal year through report date |
| G-9 | Significant accounting policies and any changes | Memos for new or changed policies |
| G-10 | Related party listing and transactions | Year, with balances at year-end |
| G-11 | Subsequent events review | Through report date |

### 2. Cash and treasury

| Ref | Request | Format / period |
|---|---|---|
| C-1 | Bank reconciliations for every account | Year-end, signed and dated by preparer and reviewer |
| C-2 | Bank statements | Year-end and the following month |
| C-3 | List of all bank accounts, signers, and any opened or closed in the year | Current |
| C-4 | Outstanding check and deposit-in-transit listings | Year-end, with clearing evidence |
| C-5 | Investment and money market statements | Year-end |
| C-6 | Authorization to send bank confirmations | Signed form |

### 3. Revenue and receivables

| Ref | Request | Format / period |
|---|---|---|
| R-1 | Revenue by customer, product, and month | Full year, tied to the GL |
| R-2 | Accounts receivable aging | Year-end, tied to the GL |
| R-3 | Allowance for credit losses calculation | Year-end, with method and inputs |
| R-4 | Contracts for samples selected by the auditor | PDFs, including amendments and order forms |
| R-5 | Revenue recognition memos for new or unusual arrangements | Year |
| R-6 | Deferred revenue rollforward | Year, tied to the GL |
| R-7 | Credit memos issued after year-end | First weeks of next period |
| R-8 | Cash receipts after year-end | For selected open invoices |

### 4. Purchases, payables, and expenses

| Ref | Request | Format / period |
|---|---|---|
| P-1 | Accounts payable aging | Year-end, tied to the GL |
| P-2 | Accrued liabilities detail and support | Year-end |
| P-3 | Search for unrecorded liabilities support | Disbursements after year-end, as selected |
| P-4 | Vendor master changes | Full year |
| P-5 | Invoices and approvals for selected expense samples | PDFs |
| P-6 | Prepaid expense schedule and amortization | Year-end |

### 5. Inventory (if applicable)

| Ref | Request | Format / period |
|---|---|---|
| I-1 | Inventory listing by location and item | Year-end, tied to the GL |
| I-2 | Count instructions, count sheets, and count results | Year-end |
| I-3 | Reserve for excess and obsolete stock calculation | Year-end |
| I-4 | Standard cost or costing roll-up support | Year |

### 6. Fixed assets, leases, and intangibles

| Ref | Request | Format / period |
|---|---|---|
| F-1 | Fixed asset rollforward (additions, disposals, depreciation) | Year, tied to the GL |
| F-2 | Support for additions and disposals above the agreed threshold | Invoices, approvals |
| F-3 | Depreciation policy and useful life changes | Current |
| F-4 | Lease schedule and calculations (right-of-use assets and liabilities) | Year-end, with new and modified leases |
| F-5 | Capitalized software or development cost support | Year |
| F-6 | Goodwill and intangible impairment analysis | Year-end |

### 7. Debt, equity, and derivatives

| Ref | Request | Format / period |
|---|---|---|
| D-1 | Debt agreements and amendments | All, current |
| D-2 | Debt rollforward and interest calculation | Year |
| D-3 | Covenant compliance calculations | Each test date |
| D-4 | Equity rollforward | Year |
| D-5 | Stock-based compensation expense calculation and grant listing | Year |
| D-6 | Dividend declarations and support | Year |
| D-7 | Hedging documentation and valuations | Year-end, if applicable |

### 8. Payroll and benefits

| Ref | Request | Format / period |
|---|---|---|
| H-1 | Payroll register, summarized and tied to the GL | Year |
| H-2 | Headcount listing and changes | Year-end |
| H-3 | Bonus and commission accrual calculations | Year-end |
| H-4 | Vacation and PTO accrual | Year-end |
| H-5 | Benefit plan documents and actuarial reports | Current |
| H-6 | Payroll samples with approvals and rate support | As selected |

### 9. Income taxes

| Ref | Request | Format / period |
|---|---|---|
| T-1 | Tax provision workpapers | Year |
| T-2 | Deferred tax asset and liability schedule | Year-end |
| T-3 | Valuation allowance analysis | Year-end |
| T-4 | Filed returns and tax notices | Prior year and any open correspondence |
| T-5 | Uncertain tax position analysis | Year-end |
| T-6 | Sales tax and other indirect tax reconciliations | Year |

### 10. Legal, insurance, and commitments

| Ref | Request | Format / period |
|---|---|---|
| L-1 | Litigation and claims listing | Current, from legal |
| L-2 | Attorney letters authorization | Signed |
| L-3 | Insurance policy summary | Current |
| L-4 | Significant commitments and contingencies | Year-end |
| L-5 | Management representation letter draft | Report date |

### 11. IT and internal controls

| Ref | Request | Format / period |
|---|---|---|
| IT-1 | List of financial systems and owners | Current |
| IT-2 | User access listing and changes to privileged access | Year |
| IT-3 | Change management evidence for financial systems | Year |
| IT-4 | Evidence of control performance (reconciliation sign-offs, approvals, reviews) | Samples as selected |
| IT-5 | Descriptions of reports used in controls (information produced by the entity) | Current |
| IT-6 | Service organization reports and your review of them | Current |

If your company is public, add the internal control testing items your auditor and your internal audit team have already agreed on. If you are in a regulated industry, add the regulatory filings and examination correspondence.

## How do you fill in the template?

Do it in three passes: assign, date, and tie out.

1. **Assign one owner per line.** An owner is a person, not a team. Put a reviewer on anything that goes outside the company. The reviewer checks that the schedule ties to the trial balance before it is sent.
2. **Work backward from the auditor's dates.** Take the date the auditor needs each item, subtract time for review, and set the owner's due date there. Items needed at interim fieldwork (often samples of controls, journal entries, and some balances) go earlier than items that depend on the year-end close.
3. **Define "done" for every line.** For a schedule, done means it is in the agreed format, ties to the GL, and carries a preparer and reviewer sign-off.

### Worked example

Say you are the controller of a company with a December 31 year-end. Last year's list had 140 lines. This year you set up three rows like this:

| Ref | Request | Format / period | Owner | Reviewer | Due date | Status | Date sent | Auditor comments |
|---|---|---|---|---|---|---|---|---|
| C-1 | Bank reconciliations, all accounts | Dec 31, signed and dated | Treasury accountant | Assistant controller | Jan 20 | In progress | | |
| R-2 | AR aging, tied to GL | Dec 31, Excel | AR lead | Revenue accounting manager | Jan 15 | Not started | | |
| F-4 | Lease schedule and ROU calculations | Dec 31, includes two new leases | Lease accountant | Controller | Jan 25 | In review | | New leases: auditor asked for executed agreements |

The third row shows how the "Auditor comments" column earns its place. When the auditor asks for the executed agreements, you log it on the same line, so the history of that request stays in one place instead of in an email thread.

A few habits that save the most time:

- **Put the tie-out in the file.** Add a tab to each schedule showing the schedule total, the GL balance, and the difference (ideally zero).
- **Name files with the reference number.** For example, "R-2 AR Aging 2025-12-31.xlsx". The auditor finds it, and so do you next year.
- **Send in batches, not one at a time.** A weekly batch with a cover note is easier for the audit team than twenty separate emails.
- **Say how a report was produced.** If a report came from your ERP, note the report name and the filters used. Auditors have to test that reports are complete and accurate, so this prevents a second request.

## How can AI help you prepare the PBC list?

AI is a good fit for the paperwork around the audit, not the audit evidence itself. It can compare last year's list to this year's request, flag what changed, draft owner assignments and reminder emails, and turn a messy email thread into a clean status update. It saves the most time at the start, when you convert last year's list into this year's tracker.

Use only an AI tool your company has approved for finance work, and do not paste real financial data, customer names, or account numbers into it. Your list of request descriptions and owner names is usually enough.

### Prompt to roll last year's list forward

Paste this, then add last year's final PBC list and the new request from the auditor.

```
You are helping a corporate accounting team prepare for an external audit.

I will give you two lists:
A) Last year's final PBC (prepared by client) list, with owners and notes.
B) This year's PBC request list from the auditors.

Do the following:
1. Match each line in B to the closest line in A. Show the matches in a table with columns: This year's ref, This year's request, Last year's ref, Match confidence (high, medium, low).
2. List every line in B that has no match in A (new requests).
3. List every line in A that has no match in B (dropped requests), so I can confirm they are no longer needed.
4. For matched lines, carry forward the owner and reviewer from last year. Mark any line where last year's notes mention a problem, delay, or auditor follow-up.
5. Output a final tracker table with columns: Ref, Request, Format/period, Owner, Reviewer, Due date, Status, Notes. Leave Due date blank and set Status to "Not started".
6. Do not invent requests, owners, or dates. If you are unsure about a match, say so.

Here is last year's list:
[paste]

Here is this year's list:
[paste]
```

### A second prompt for status emails

```
Here is my PBC tracker as of today [paste rows with Status not equal to Closed].
Write a status email to the audit manager. Include: items sent this week, items in review, items at risk of missing their due date (with the reason in the Notes column), and what we need from the auditors. Keep it under 200 words. Use only the information in the tracker.
```

### What to check in the AI's answer

- **Matches.** Spot-check every "medium" and "low" match yourself. Similar-sounding requests (for example, accrued liabilities and unrecorded liabilities) are different tests.
- **Owners.** People change roles and leave. Confirm each carried-forward owner still holds that job.
- **New and dropped items.** Read both lists in full. A dropped item might mean the auditor changed scope, or it might mean the AI missed a match.
- **Dates.** AI will sometimes fill in dates anyway. Delete any date you did not set.
- **Counts.** Check that the number of lines in the output matches the number in the input plus the new items.

### Where not to trust AI

Do not use AI to write control descriptions, accounting policy memos, or management representations without a person who owns the content writing and approving them. Do not let it produce schedules or calculations that go to the auditors. Do not rely on it to say whether a requested item is in scope. Those are judgment calls, and the people signing the financial statements are accountable for them.

## How do you cut the back and forth with your auditors?

Most delays on a PBC list come from the same few causes, and you can address them before fieldwork starts.

- **Hold a kickoff call.** Walk through the list with the audit manager. Ask which items are needed at interim and which at year-end, and which are truly new. Get the materiality threshold for samples and support in writing.
- **Agree on one delivery channel.** Whether it is the audit firm's portal or a shared folder, settle on one place. Email attachments get lost.
- **Ask for sample selections early.** Auditors pick samples (of journal entries, invoices, payroll records) from populations you provide. Send the population first, and the support only after they select.
- **Send complete populations.** If a population does not tie to the GL, the auditor cannot rely on the sample drawn from it. Do the tie-out before sending.
- **Keep a running "open items" view.** Sort the tracker by Status = Follow-up from auditor, and review it in a short daily check-in during fieldwork.
- **Log what you learned.** At the end, add a "lessons" note on each line that caused trouble. Next year's list inherits it.

## How often should you update the template?

Update it at three points: when the auditor sends the formal request, after the audit closes, and whenever your business changes in a way that adds an accounting area (an acquisition, a new lease portfolio, a new revenue stream, a system migration). After the audit, save the final list, including comments and dates, as next year's starting file. That final version is more useful than any blank template, because it reflects your company, your systems, and your auditor's habits.

## Could you build your own PBC tracker?

Many teams run this list in a spreadsheet and chase status over email. If that is slowing you down, a small internal app can do the job better: a request list with an owner, reviewer, due date, and status per line, file uploads attached to each request, reminder emails, and sign-in so the audit team sees only their items. [Remy](https://goremy.ai) builds apps like this from a plain-English description, with a database, sign-in, and email built in, and the code stays in a git repository you own. Describe your columns and statuses, review the result with your IT and security team, and reuse it each audit cycle.

## Frequently Asked Questions

### What does PBC stand for in an audit?

PBC stands for "prepared by client" (some firms say "provided by client"). It refers to the documents, schedules, and reports the company must give the auditors. Your auditor's request list usually uses this term in its title.

### When do auditors send the PBC list?

Usually several weeks to a few months before fieldwork begins, often after planning discussions. Interim requests, such as control samples and early-year balances, tend to come first, and year-end requests follow. Ask your audit manager for the timeline at the planning meeting, since it varies by firm and company.

### Who is responsible for the PBC list?

The controller or an accounting manager typically coordinates it, but individual owners sit in accounting, tax, treasury, payroll, legal, and IT. The coordinator tracks status and acts as the single point of contact for the audit team, while each owner prepares and reviews their own items.

### Can I reuse last year's PBC list?

Yes, and you should. Start from last year's final list, then compare it with the auditor's new request to find added, changed, and dropped items. Keep the owners, formats, and notes, and update dates and any area where your accounting changed.

### What happens if we miss a PBC deadline?

Missing a date can push back fieldwork, extend the audit timeline, and increase audit fees if the team has to return later. If you expect to be late, tell the audit manager as soon as you know, explain the reason, and offer a new date. Partial deliveries with a clear note are often better than silence.
