Guide
Your first audit: what the PBC list actually asks for, and how much of it your close already made
A PBC list, short for prepared by client, is the schedule of documents your auditor expects you to hand over. For a first audit it usually runs 60 to 120 line items, and most of it is not new work: reconciliations, support for material balances, and explanations of what moved are all things a monthly close already produces. The items that hurt are the ones nobody made during the year, such as a signed revenue contract file, equity documents that agree to the cap table, and written explanations of variances that were only ever discussed in chat. The way to make a first audit cheap is not to prepare harder in February. It is to close in a way that leaves the support attached the other eleven months.
By Vanward. Published 2026-09-19. Updated 2026-09-19.
The first audit is usually the first time anyone outside the company reads the books closely. That is why it feels adversarial and why it mostly is not. An auditor is trying to get comfortable with a number, and every question they ask is a version of the same one: how do you know this is right, and what would you show me.
What the list contains
The shape is consistent across firms even though the formatting is not. Roughly a third is company information, a third is balance sheet support, and a third is transaction testing material.
| Section | Typical items | Comes out of your close? |
|---|---|---|
| Company and governance | Formation documents, bylaws, board minutes, equity agreements, debt agreements | No. These are kept, not produced monthly |
| Cash | Bank statements, reconciliations, outstanding item detail, bank confirmations | Yes, entirely, if the statement travels with the reconciliation |
| Revenue and receivables | Revenue by customer, signed contracts, AR aging, subsequent collections, deferred revenue rollforward | Partly. The schedules yes, the contract file usually no |
| Expenses and payables | AP aging, accrual support, search for unrecorded liabilities, expense detail | Yes, if accruals carry their calculation |
| Payroll | Registers, quarterly filings, agreement to the ledger, bonus and commission accruals | Yes |
| Equity | Cap table, option grants and board approvals, 409A, stock compensation calculation | No. This is the other common gap |
| Analytics | Variance explanations, trend schedules, unusual entries and who approved them | Yes, if the explanations were written down when they happened |
The four items that cause most of the pain
Contracts that agree to revenue
Not a folder of contracts. A file where each material revenue stream points to the signed document that supports how it was recognized, including the amendments. Companies lose weeks here because the contracts live in three places and nobody has ever tied them to the ledger.
Equity that agrees to itself
The cap table, the board approvals for each grant, and the stock compensation expense in the ledger all have to tell the same story. They frequently do not, usually because a grant was promised in one month, approved in another, and recorded from an email.
Who reviewed it
Auditors ask about segregation of duties in the first meeting, and a small company answers honestly that one person does most of it. That is workable. What is not workable is having no record of who reviewed anything, because then the control does not exist for testing purposes even if a review happened.
Explanations written after the fact
An explanation composed in February for a variance from the previous May is not wrong, but it reads as reconstructed, and reconstructed explanations invite more testing. An explanation written the week it happened, by the person who knew why, ends the question.
What to do this year if the audit is next year
Three things, in this order, and none requires new software to start.
Attach support to the close rather than storing it separately. The reconciliation and the statement it ties to should be one thing a year from now, not two things someone has to match up.
Record a reviewer on each material step, even when the reviewer is your outside accountant or your CEO. A named reviewer who is not the preparer is the cheapest control you can add.
Write the variance explanation in the month it occurs, in a sentence that names the cause and the amount. Ten minutes then saves an hour in fieldwork, and it saves your credibility on the items where it matters.
What the auditor is actually deciding
Whether to rely on your process or work around it. A client whose support is assembled, whose reviewers are named, and whose explanations are contemporaneous gets tested lightly and finishes on the quoted fee. A client who hands over a drive folder gets a substantive approach, which means more transactions, more questions and more hours billed to you.
That decision is largely made in the first two weeks, from how the PBC list comes back. It is worth treating the first response as the most important deliverable of the engagement, because it sets the cost of everything after it.
Questions founders ask
- How long does a first audit take?
- Plan on eight to sixteen weeks from kickoff to a signed opinion for a company under $50M in revenue, and expect the first four to be mostly you. The variable is not the auditor. It is how long you take to answer the PBC list, and that depends on whether the support exists already or has to be rebuilt.
- What makes a first audit more expensive than the quote?
- Scope creep from missing support. A fee quote assumes the client produces what is asked; when reconciliations have to be rebuilt or explanations invented after the fact, the hours move and so does the fee. Ask your auditor directly what drives an overrun and they will describe the same list.
- Do we need an audit at all, or will a review do?
- Read your documents before you assume. Audits are usually triggered by a credit agreement, a priced round, or a large customer, and a review satisfies a surprising number of them. Reviews cost less and ask for less. Nothing here changes based on which one you get, because the support is the same support.
- Who should own the PBC list internally?
- One person, and not your CEO. A controller or a fractional CFO with the authority to chase other departments. Audits stall when ownership is shared, because a shared item is an unowned item and the auditor has no way to tell which of you they are waiting on.
- Can we give the auditor access to our systems instead of sending files?
- Often yes for the ledger, rarely for everything. The practical answer is a shared, organized folder that mirrors the PBC list, because an auditor working from your file structure asks fewer clarifying questions. What matters is that each file is the version you stand behind and that it does not change underneath them mid-fieldwork.
- What is the single item most first-time clients are missing?
- A complete signed contract file that agrees to how revenue was recognized. Companies have the contracts somewhere, usually across email and a drive folder, but not assembled against the revenue they support. That assembly is the most common reason a first audit runs long.
How ready is your close?
Eight yes-or-no questions, two minutes, no account. You get a score out of 100 and the three gaps most likely to come up in an audit or a diligence request.
Take the free close checkRelated