Compiled financial statements can solve a narrow but important problem: a business needs professionally presented numbers, but it does not need the cost or depth of a review or audit. In U.S. practice, the distinction between preparation and compilation matters because one service ends with no report at all, while the other produces a formal compilation report without assurance. I focus here on what the accountant actually does, when the service is useful, and where the line becomes too thin for lenders, boards, or investors.
The practical difference is the level of confidence behind the numbers
- Compilation is a no-assurance service; the CPA presents management’s numbers in financial statement form.
- Preparation and compilation are not the same: preparation can end without a report, while compilation adds one.
- Management remains responsible for the books, judgments, and disclosures.
- Compilations are often used for small private businesses, bank packages, and basic governance reporting.
- When users need limited or reasonable assurance, a review or audit is the better fit.
Why preparation and compilation are not interchangeable
The terms get blended together, but U.S. standards treat them differently. AR-C 70 is about preparing financial statements; AR-C 80 is about compilation engagements. The first can end with no report, while the second adds a CPA report but still provides no assurance. That difference matters because a bank, board member, or investor reads the package differently depending on which service produced it.
I think of preparation as the lighter touch and compilation as the first step into formal reporting. Once someone outside management will rely on the package, the report itself starts to matter.
Current SSARS guidance keeps preparation, compilation, and review in separate buckets for a reason. Each service answers a different business need, and confusing them leads to bad expectations.
What a compilation actually does
In a compilation, the CPA takes information supplied by management and arranges it into financial statement form. The accountant is not verifying the ledger, not testing controls, and not giving an opinion or conclusion about whether the statements are free of misstatement. What the user gets is a professionally presented package, and usually enough comfort that the statements are in the right form, but no assurance.
I think of it as a presentation service, not a verification service. That keeps everyone honest about what the CPA did and did not do.
Management still owns the numbers. That includes the accounting records, the judgments behind estimates, and the disclosures that belong in the statements. If the underlying books are weak, a compilation does not magically fix them; it only packages them more cleanly.
Independence is another point people miss. A CPA does not have to be independent to perform a compilation, but if independence is impaired, that fact has to be disclosed in the report. That is one reason the service is practical for closely held businesses and advisory relationships where a review would not be allowed.
Compilations can also be prepared under a special purpose framework instead of GAAP when that better fits the business and the reader. In plain English, that means the statements can be built on a non-GAAP basis such as cash or tax basis when the circumstances call for it. The next question is when that lighter service is actually the right commercial choice.
When it makes sense for a U.S. business
In practice, I see this service work best where the user wants disciplined presentation, not deep assurance. AICPA guidance and practice materials still tie compilations to situations where a business needs professionally prepared statements for lower-stakes external use, and they are often used when a company is pursuing initial or smaller financing. That is the right mental model: useful, but not exhaustive.
- A small business seeking a modest line of credit may need a clean year-end package without the expense of a review.
- A family-owned company may want statements for a bank, board, or owner group that expects consistency more than assurance.
- A nonprofit or closely held company may need annual statements for governance, covenant tracking, or internal discipline.
- An owner-managed business with good books may prefer the optics and structure of a CPA report even when no one is demanding assurance.
There are also situations where I would push harder than a compilation. If the statements will support a sale process, outside investor diligence, or a financing package with tight covenants, the user is usually asking for more confidence than a compilation can deliver. That is where the assurance ladder starts to matter.
How compilations compare with preparation, reviews, and audits
The cleanest way to understand the service is to compare it with the two neighboring options. The AICPA’s current SSARS materials keep these engagements separate because the amount of work, the independence requirement, and the level of user confidence are not the same.
| Service | What the CPA does | Assurance level | Typical use | Independence |
|---|---|---|---|---|
| Preparation | Helps prepare the statements; no formal compilation report | None | Internal reporting and management packets | Not required |
| Compilation | Places management’s information into financial statement form and issues a compilation report | None | Small business lenders, board packs, routine external presentation | Not required, but impairment must be disclosed |
| Review | Performs inquiry and analytical procedures | Limited assurance | Users needing more confidence without a full audit | Required |
| Audit | Performs broader procedures, including evidence testing and internal control understanding | Reasonable assurance | Investors, M&A, complex financing, higher scrutiny | Required |
The practical takeaway is simple: as the outside reader’s reliance increases, the engagement has to deliver more than a neat presentation. A compilation can be enough when the request is modest; it becomes less appropriate when the decision on the other side is material.
Where compilations go wrong in practice
The biggest mistakes are usually not technical. They are expectation problems.
- Treating the report as if it certifies accuracy. It does not.
- Submitting messy books and hoping the compilation will make them credible. It will not.
- Ignoring framework choices. GAAP, cash basis, and other special purpose frameworks can lead to very different presentations.
- Skipping the disclosure conversation. Even in a lighter engagement, users still need enough context to read the numbers correctly.
- Assuming every lender accepts the same level of reporting. Some do; others do not, and covenant language often settles the issue.
The good news is that these problems are preventable. When management and the CPA agree early on the audience, framework, and purpose, the compilation tends to work exactly as intended. If that conversation is skipped, the result is often a polished package that still misses the decision it was supposed to support.
How I decide whether a compilation is enough
When I’m advising on this, I usually walk through five questions.
- Who is going to read the statements?
- What decision will they make from them?
- Does a lender agreement, investor request, or governance policy require more than a compilation?
- Are the books and disclosures in a condition that can support a clean presentation?
- Is the business comfortable with a no-assurance service, even if a CPA signs the report?
If the answer to the first two questions points to high-stakes reliance, I usually move up to a review or audit. If the audience mainly wants a disciplined, professional package, and the business does not need assurance, a compilation is often the efficient answer. That choice is less about saving money than about matching the service to the real use case.
The decision points that usually settle it
The best use of a compilation is to create a clear, credible financial package without pretending it says more than it does. That means clean records, a deliberate accounting framework, a report the reader understands, and a lender or board that is actually satisfied with no assurance. If any one of those pieces is missing, the service may still be possible, but it may not be the right tool.
One useful discipline is to ask the intended reader to state the decision the statements must support in one sentence. If the answer is merely “we want clean year-end numbers,” a compilation may be enough. If the answer is “we need to rely on these numbers to commit capital, waive covenants, or sell the business,” the engagement should usually move higher.
For governance, the right standard is not the cheapest one available; it is the one that matches how much trust the reader needs to place in the package. If they need comfort, move up to a review or audit; if they need disciplined presentation, a compilation can do the job.
