Why now
An audit firm has sent you an engagement letter, the document confirming they will audit your financial statements, the reports that show your company's results and position. Maybe a lender required the audit as part of a loan covenant, a condition written into your loan agreement, or an investor asked for it before your next raise. Maybe your revenue crossed a level written into one of your agreements.
Whatever the reason, the audit firm will soon send a request list, often called a PBC list, short for "prepared by client." It lists the documents and schedules they expect you to produce. Many first-time teams focus on just getting through the audit, but a better goal is to have proof ready for every balance before the list arrives.
What the request list actually contains
A request list is not one document but a set of asks tied to each line on your balance sheet. The balance sheet shows what you own, what you owe, and what is left over on a given date, and each line on it is called a balance.
For cash, auditors will ask for bank statements and a reconciliation, a check that your books match the bank's records. For accounts receivable, the money customers owe you, they will ask for invoices, customer agreements, and a list of who has not paid. For accounts payable, the money you owe vendors, they will ask for vendor invoices, the agreement or price reference behind each one, and proof of what you have paid. A price reference is any document that sets a price, such as an order form or a lease.
For payroll, they will ask for pay registers and your agreement with your PEO; a PEO, or professional employer organization, runs payroll and benefits on your behalf.
Every one of these asks has the same shape: there is a number on your books, and a document that proves the number is right. If you keep that pairing current all year, the request list becomes a task you can finish quickly instead of a scramble.
Proof for every balance, not just the big ones
First-time audits often stall because teams prepare the largest balances and leave the small ones loose. Auditors test across many balances, and one messy small balance can slow down the whole audit. For every balance, you should be able to answer three questions: what is the number, what document proves it, and where is that document stored?
For cloud spend, the hosting and computing you pay for, often billed by usage, the proof is the invoice and the order form, which sets the agreed price and terms. For contractors, the proof is the agreement or statement of work and the invoice. For your lease, it is the lease itself, the agreement that sets your rent.
If a number does not match the agreement or price reference behind it, that is more than an audit risk, because it is often money you overpaid, meaning charges above the price you agreed to.
The gap between a yearly scramble and being ready all year
Most finance teams at this stage are one to three people. Many have no controller, the senior accountant who owns the monthly close, and most have no internal audit, a team that checks processes all year. That is normal at this size, but it means audit readiness has to come from habits, not headcount.
The habit that matters most is simple: check each invoice against its agreement or price reference as it comes in, not once a year. If a vendor's invoice does not match the price on the order form, catch it the week it arrives. If a contractor bills more hours than the agreement allows, catch it before you pay. This is what audit-ready should mean: a steady state all year, not a sprint before the audit.
Where the money comes back
When you check every transaction against its agreement or price reference, you find two kinds of problems. The first is overpayment: a vendor billed above the agreed price, or billed for something the agreement does not cover. The second is undercharging: you billed a customer less than your agreement set, which is money you are owed and have not collected. Each case may be small, but they can add up across a year of invoices.
The same checks can also detect fraud and embezzlement early; embezzlement is theft by someone trusted to handle the money. Warning signs include duplicate invoices, unusual payments, and vendors with no agreement on file. Catching these early means you spot a pattern while it is still small, and that you can show the auditor what happened and when you found it.
A practical place to start
You do not need a long project plan: pick one agreement or price reference you already have. It could be a vendor agreement, an order form, your lease, or an agency statement of work. Then pick one invoice billed against it and check whether the invoice matches the price on the page. That one comparison is the whole method, repeated across every transaction.
Ressura's free Procure-to-Pay check does this with no setup; Procure-to-Pay is the process of ordering, receiving, and paying for goods and services. Upload one agreement and one invoice, and get a dollar finding in minutes. Every figure is recomputed, so you can check the arithmetic yourself. There is nothing to connect, no sales call, and no cost to start, and you see a real result from your own data before you have an account.
Building the habit the auditor expects
An audit firm's request list asks one question, over and over, for every balance: can you prove this number? The teams that answer quickly already check invoices and agreements as they arrive, rather than building a folder the week before the audit starts.
That habit also prepares you for the next demand on your numbers. It might be a lender's compliance certificate, a document confirming you meet your loan terms. It might be an investor's request list before a raise, or a buyer's diligence list, the documents an acquirer asks for during a deal.
Always-on financial assurance. Ready for every demand on your numbers, and paid for by the money it finds.
Start free.