Every number in a set of financial statements has to prove where it came from. Tie-out is the check for that: does the figure on the face of the accounts match the working paper behind it, the trial balance, and the source document underneath both.

If your name goes on the file, tie-out is the part you can't take on trust. An associate or senior does the tying. You're the one who answers for it when a reviewer, or a regulator, opens the file in three years and finds a number that doesn't agree. This is a plain account of what tie-out is, how it works, and why it eats a reviewer's afternoon on a manual file.

What is audit tie-out?

Audit tie-out is the process of checking that every number, note reference, and cross-reference in a set of financial statements agrees with the working paper, trial balance, or source document it's drawn from. It's a mechanical check, done right before an auditor signs off that the report matches the file.

“Mechanical” doesn't mean unimportant. It's the last check against the kind of error judgment never catches: a rounding slip in a note, a prior-year comparative that didn't get updated, a total that changed in one place and not the other three. Auditors call the result "tied and agreed": the number has been traced to its source, and it agrees.

Audit documentation is defined in ISA 230 as the record of the audit procedures performed, the relevant evidence obtained, and the conclusions the auditor reached. Tie-out is the check that keeps that record internally consistent.

Tick and tie

"Tick and tie" is the older, more literal name for the same thing. You tie a number to its source, then you tick it: a small mark next to the figure that says "I checked this, and it agrees." On paper that was a colored pencil. On PDFs it's a digital stamp or a typed legend at the bottom of the page. The tie is the check; the tick is the record that the check happened.

Why tie-out matters in financial statement audit

Get it wrong and the number in the published report doesn't match the number the audit actually tested. It's the kind of gap a regulator or an external reviewer finds first, because it's the easiest thing in the file to check.

For the file to hold, an experienced auditor with no previous connection to the engagement has to be able to understand the procedures performed, the evidence obtained, and the conclusions reached, without anyone explaining it out loud. That's the test ISA 230 sets. A file can be complete and still fail it if the numbers in it don't connect to the numbers in the report.

This is why tie-out sits so close to sign-off. Firms assemble the final audit file on a timely basis after the report date. Under ISQM 1, firm policy ordinarily allows no more than 60 days for it, and ISA 230 carries the same window in its application material. After that, nothing gets added or changed without recording who did it, when, and why. There's not much room to find a mismatch late, and even less to fix it quietly.

How the tie-out process usually works

A tie-out pass moves in roughly this order:

1. Cast the numbers. Check that columns and totals within the statements and notes add up.

2. Tie the face of the accounts to the trial balance. Every line on the balance sheet, income statement, and cash flow statement should trace to a trial balance account or group of accounts.

3. Tie the notes to the face of the accounts. A note breaking down "other receivables" should sum to the number it's explaining.

4. Check cross-references. Page references, note numbers, and "see note X" callouts have to point to the right place, every time.

5. Tie comparatives. Prior-year figures should match what was reported last year, adjusted only for anything restated.

6. Run a final pass on the near-final draft. The version that's actually going out, not the first draft and not every draft in between.

Auditors mark each check with a short code as they go: MA for mathematical accuracy, PY for prior year, IC for internal consistency. The shorthand varies by firm. The point is that someone reviewing the file later can see at a glance what was checked and how.

This is also where a test of details differs from tie-out, and it's worth being precise. A test of details is a substantive procedure that gathers evidence about a balance or transaction: confirming a receivable with a customer, recalculating depreciation, vouching a sample of invoices. Tie-out happens after that evidence exists. It checks that the resulting number made it into the financial statements correctly.

Where tie-out breaks down

The failure point is usually version control. A client sends a new draft, one number in one note changes, and the team has to work out what else that number touches before they can trust that the rest of the file still ties.

Manual tools make this harder than it needs to be. A PDF compare tool breaks the moment a page shifts, and page shifts happen on nearly every draft of a financial statement. Teams re-check things that didn't change, because they can't easily tell what did. Multiply that by five or six drafts on one engagement, and the tie-out gets redone almost as many times as the numbers do.

This is the kind of recalculation work that eats a reviewer's afternoon without needing much judgment. Purpose-built tie-out tooling keeps every number tied to its source as the draft changes, so a late page shift doesn't mean re-checking the whole file: a new draft doesn't mean starting over.

None of this removes the judgment. Automation won't catch everything, and a reviewer still has to eyeball a section a draft added or dropped between versions. That part stays with the auditor, which is where it belongs.

See tie-out without manual re-checking →