Financial Statement Compilation Software: Compiled Financial Statements for CPA Firms

What financial statement compilation software actually does

A compilation engagement has two halves. The first half is mechanical: take the client's trial balance, map every account to a statement line, group and subtotal the accounts the way an external reader expects, build the three statements in the order the numbers require, and prove that they agree with each other. The second half is professional judgment: reading the result, noticing what looks wrong, deciding whether the statements are appropriate in form, and issuing the report that carries your firm's name.

Compilation software does the first half. It does not do the second, and any vendor telling you otherwise is selling you a liability. AIStatements reads whatever the client's books export, maps the chart of accounts, produces the income statement, balance sheet and statement of cash flows, and runs the tie-outs before it hands anything back. What lands on your desk is a finished draft with the arithmetic already proven, not a blank template you still have to wire up for the fortieth client this quarter.

The mapping is the part that compounds. Every client has a different chart of accounts, and rebuilding the mapping every period is where compilation time actually goes. Once a client is mapped, the following period reuses it, so month two takes a fraction of month one. Firms running a roster of thirty or eighty compilation clients feel that difference immediately, because the work stops scaling linearly with the client count.

Alongside the statements, AIStatements writes a plain-English read of what moved: margin direction, expense categories growing faster than revenue, working capital drift, and balances that look like posting errors rather than business events. That last category is the useful one during a compilation, because reading the statements for obvious problems is exactly what the standard expects of you before the report goes out.

Compilation, preparation and review: which engagement are you actually performing

These three get used interchangeably in conversation and they are not interchangeable in the standards. Under the AICPA Statements on Standards for Accounting and Review Services, a preparation engagement falls under AR-C section 70, a compilation under AR-C section 80, and a review under AR-C section 90. An audit is not a SSARS engagement at all; it sits under the auditing standards.

A preparation engagement produces financial statements with no report attached. In fact a compilation report should not be provided in a preparation engagement. Instead the statements themselves must carry a legend on each page stating that no assurance is provided, or an accompanying disclaimer to that effect. Independence is not a consideration, because preparation is a non-attest service. A signed engagement letter is still required, and substantially all disclosures may be omitted as long as the omission is disclosed.

A compilation adds the report. Under AR-C 80 a report is required for every compilation engagement, and that report is deliberately worded to distinguish it from a review or audit report. No assurance is expressed. Independence is not required to perform a compilation, but if your firm is not independent, that lack of independence has to be disclosed in the report. That single rule is the one most often missed by firms that also do the client's bookkeeping.

A review is a different animal: it provides limited assurance, requires analytical procedures and inquiry, and requires independence. If you are being asked for a review, compilation software shortens the statement assembly but the substance of the engagement is elsewhere. We walk the full comparison in compilation vs review vs audit.

How to compile financial statements from a client's books

Start from a trial balance that actually balances and that the client has closed. Compilation is not bookkeeping cleanup, and the fastest way to lose money on a fixed-fee compilation is to absorb a month of unreconciled bank accounts inside it. If the books are not closed, close them first or bill it separately. Our month end close software page covers where that work sits.

Then map every account to a statement line. This is where presentation gets decided: operating expenses grouped into categories a reader can follow rather than in chart-of-accounts order, the current and long-term portions of debt split correctly, owner draws sitting in equity rather than in expenses, and contra accounts netted where convention expects it. Build the income statement first, because net income feeds everything downstream. Roll it into equity, then produce the balance sheet using that closing equity figure, then derive the cash flow statement from the movement between the opening and closing balance sheets. The sequence is not optional, and the order financial statements are prepared in explains why.

Prove the ties before you read anything. Net income has to agree between the income statement and the top of the cash flow statement. Assets have to equal liabilities plus equity. Ending cash on the cash flow statement has to equal the cash line on the balance sheet. Three checks, and a pack that fails any of them is not ready for a report. AIStatements runs all three automatically and shows you the failure rather than quietly producing a wrong document.

Only then does the professional work start: read the statements for anything that looks incorrect or incomplete, follow up with the client on what does not make sense, decide on disclosure level, and issue your report. The step-by-step manual version of the assembly is in preparing financial statements from a trial balance, and the tooling for that mechanical half is covered on trial balance to financial statements software.

What this software does not do, stated plainly

It is not a CPA and it does not issue your compilation report. The report is a professional communication from your firm, it carries your responsibility, and no software can sign it for you. AIStatements produces the statements that go with it.

It does not provide assurance of any kind, and it does not make the statements GAAP-compliant by itself, though it does produce them in GAAP presentation format. It formats and analyzes the data you give it. If the underlying chart of accounts is wrong or the client has misclassified a year of transactions, the output will faithfully reflect that. Reading the result for obvious problems remains your job, and it is the part of the engagement clients are actually paying for.

It does not manage your engagement letters, independence documentation, or file retention. It does not draft footnote disclosures, and it does not perform the analytical procedures or inquiries a review requires. It also does not do consolidations, so if a client has multiple entities that need combining, that consolidation happens before the export reaches us.

What it removes is the two to six hours per client per period spent assembling and formatting statements by hand in a spreadsheet, and the rework that follows every time a chart of accounts changes. That is the whole pitch. Firms that want the same engine aimed at their broader deliverable set usually land on financial statement drafting and preparation software.

What goes in the compilation report, and what an accounting compilation is not

The compilation report is the short accountant's report that travels in front of the statements, and it is deliberately brief. It identifies the entity and the statements and periods covered, states that management is responsible for the financial statements, states that the engagement was conducted in accordance with Statements on Standards for Accounting and Review Services issued by the AICPA, and then does the thing the whole report exists to do: it says the accountant did not audit or review the statements and accordingly expresses no opinion, no conclusion, and no assurance of any kind. It is signed by the firm and dated. That is the entire structure, and every compilation report sample or example you find will follow it, because the content is set by the standard rather than by house style.

The wording matters more than its length suggests, because the report is what limits the firm's exposure. A compilation says the accountant assembled the client's numbers into the right format and read them for obvious problems. It does not say the numbers are right. If the statements omit substantially all disclosures, which is common and permitted, the report has to say so and has to state that the omission could influence a reader's conclusions. If the accountant is not independent, the report must disclose that too, though the reason may be omitted. Getting either of those wrong is a peer review finding, and no software should be generating that language for you unreviewed.

Two things an accounting compilation is not, which is where most of the confusion in this category lives. It is not a preparation engagement: under AR-C 70 there is no accountant's report at all, and instead each page of the statements carries a legend saying no assurance is provided. And it is not a review: under AR-C 90 the accountant performs analytical procedures and inquiries and issues limited assurance, stating that they are not aware of any material modifications that should be made. Compilation sits between the two, with a report but with no assurance in it. Firms sometimes describe all three loosely as CPA prepared financial statements, and the deliverables, the fees and the liability are genuinely different, so it is worth naming the engagement precisely in the letter before any of them starts.

Who buys compilation software, and what changes for the firm

The buyer is almost always a small or midsize US accounting firm with a recurring compilation roster: closely held businesses that need statements for a bank, a bonding agent, a franchisor or an owner, but do not need and will not pay for an audit. The work is standardized, the deliverable is nearly identical across clients, and the fee is fixed. That combination is exactly where automation pays, because every hour saved is margin the firm keeps rather than a discount the client gets.

The second buyer is the outsourced accounting or client accounting services team that closes twenty or fifty small clients a month and issues a statement package with each close. There the constraint is not skill, it is throughput in the first two weeks of the month. Mapping that persists between periods is the feature that matters, and it is why firms usually pilot on their five messiest clients rather than their cleanest.

The third is the sole practitioner who does compilations alongside tax work and loses January through April to the return season. Compilation deadlines do not move for tax season, and a workflow that turns statement assembly into a review step is what keeps both from slipping. Firm-level pricing and the multi-client review flow are on our software for accounting firms page.

The honest measure of whether this is worth it: count the hours your firm currently bills to statement assembly and formatting, not to judgment or client conversation. If that number is small, keep your spreadsheet. If it is a meaningful share of a fixed-fee engagement, that is the number this replaces. AIStatements is software that formats and analyzes the data you provide. It is not accounting, audit or tax advice, it is not a CPA, and it does not guarantee GAAP compliance.

CPA software for write-up and compilation services

Write-up and compilation are two halves of the same monthly engagement, and firms shopping for software usually need to be clear about which half hurts. Write-up is the bookkeeping side: recording the client's activity after the fact, posting the adjustments the client cannot make themselves, and getting to a trial balance you are willing to work from. Compilation is what happens next, taking those balances to a formatted statement set and issuing the AR-C 80 report with it.

Traditionally one product did both, which is why the write-up suites carry a general ledger, client payroll and a working trial balance alongside the statement output. Thomson Reuters Accounting CS is the clearest example, and Wolters Kluwer, CaseWare and cloud entrants such as AuditFile sell the engagement equivalent, the last of these at $199 to $299 per user per month. That bundling made sense when firms held every client's books themselves. It makes less sense now that most small business clients keep their own books in QuickBooks or Xero and hand the accountant an export.

The practical split for a modern firm is to leave the ledger where the client already runs it, do the adjustments in a working trial balance, and buy the compilation output separately. That is a much smaller purchase than a write-up suite, and it is the piece that runs every single month. Firms currently paying suite pricing for that output should compare the Accounting CS alternative breakdown, which sets Accounting CS, Workpapers CS and Engagement Manager against what each one actually does, and check the licensing arithmetic in Accounting CS pricing. The working trial balance tools themselves are scored in trial balance software for accountants.

Common questions