A tick and tie audit is the two-step verification that every reported number traces to a real source document and that every total agrees with the totals it feeds. You tick at the detail level, matching individual ledger entries to invoices, statements, and receipts. You tie at the summary level, confirming that balances carry cleanly from the general ledger to the trial balance to the financial statements. The process catches transposition errors, formula mistakes, misclassifications, and the kind of inconsistencies that quietly distort a company’s reported position.
What Ticking and Tying Mean
Ticking is the detail check. You pull a single transaction from the general ledger, find the source document behind it, and confirm the amount, date, and description all match. When they do, you place a tick mark next to the entry. That mark signals to anyone reviewing the workpapers later that the item has been verified.
Tying operates one level up. Once the underlying entries are verified, you confirm that totals in one place equal totals in another. Accounts receivable in the general ledger should equal the accounts receivable line on the balance sheet. Revenue on the income statement should equal the revenue accounts in the trial balance. A matched pair gets marked as tied. The two layers together give you accurate inputs and accurate summaries.
Documents to Pull Before You Start
Gathering everything upfront is faster than hunting mid-review. On the internal side you need the general ledger, the trial balance, and any sub-ledgers covering payables, receivables, fixed assets, and similar accounts. These get compared against the balance sheet, income statement, statement of cash flows, and any footnotes or supplemental schedules.
Underneath sits the evidentiary layer: bank statements, vendor invoices, payroll records, contracts, and receipts. Each source document should show a dollar amount, a date, and enough identifying detail to match it unambiguously to a ledger entry. Confirm before you start that every sub-ledger covers the same reporting period as the financial statements. Pulling an accounts receivable aging from the wrong month-end guarantees a mismatch and wastes hours to diagnose.
Ticking Individual Transactions
Pick a specific account rather than trying to verify everything at once. Locate the source document for each ledger entry and compare the amount, date, and description. If all three agree, place your mark. Common marks are checkmarks, initials, or specific symbols defined in a legend at the front of the workpapers.
Consistency matters more than which symbols you pick. Every reviewer who later touches the workpapers needs to understand each mark without asking. A tick mark legend defining every symbol, along with who placed it and when, turns individual checks into a coherent audit trail. The PCAOB requires audit documentation to be detailed enough that an experienced auditor with no prior connection to the engagement can understand what was done and what was concluded.1Public Company Accounting Oversight Board (PCAOB). AS 1215: Audit Documentation
When a source document doesn’t match, note the nature and amount of the discrepancy immediately. Reconstructing what went wrong days later is much harder than documenting it in the moment.
Tying Summary Totals
After the underlying transactions are ticked, move to the summary level. Pull the ending balance from the general ledger and compare it to the corresponding line on the financial statement. Total accounts payable of $385,000 on the trial balance should appear as exactly $385,000 on the balance sheet. When figures agree, mark the tie-out with a symbol distinct from your transaction-level tick marks.
Work through each major line, tracing it back to the trial balance or general ledger. Pay particular attention to subtotals and grand totals, where sub-ledger balances roll into summary accounts. That consolidation step is a common failure point: individual subsidiary ledgers can be correct while the roll-up introduces a rounding difference or drops an entry.
Footnotes and supplemental schedules get the same treatment. A footnote disclosing $2.1 million in operating lease obligations should tie to the supporting schedule, which should tie to the individual lease records. Footnote figures that disagree with the face of the statements are exactly what this process is built to catch.
Cross-Footing and Roll-Forward Checks
Two math checks belong alongside tying. Cross-footing confirms that the sum of items in a row equals the row total and the sum of items in a column equals the column total. In a revenue breakdown, product-line figures should add up to total revenue both across and down. When they don’t, a formula error or misclassification is hiding in the spreadsheet.
Roll-forward testing adds the time dimension. The ending balance of the prior period should be the exact opening balance of the current period. If last year’s audited retained earnings closed at $1.4 million, this year’s opening retained earnings must be $1.4 million before any current-year activity. A gap between prior close and current opening is a serious red flag because it means someone adjusted a balance between reporting cycles without documenting the change.
When to Sample and When to Test Everything
On a small engagement with a few hundred transactions you might tick every entry. On a company with millions of transactions that isn’t realistic. Auditing standards explicitly recognize that testing less than 100 percent of items in an account balance is standard practice.2Public Company Accounting Oversight Board (PCAOB). AS 2315: Audit Sampling The auditor designs a sample large enough to draw reasonable conclusions about the full population.
Sample size depends on how much misstatement you’re willing to tolerate, how risky the account is, and what prior experience suggests you’ll find. An account with a history of errors or weak controls warrants a larger sample. A stable, well-controlled account with little inherent risk can justify a smaller one. Both statistical and non-statistical approaches are acceptable, and the choice usually comes down to cost and the precision needed.2Public Company Accounting Oversight Board (PCAOB). AS 2315: Audit Sampling
Tying is almost always done on 100 percent of summary line items. It’s comparing one number to another number, so skipping lines saves nothing. The time savings from sampling apply mainly to ticking, where each transaction requires pulling and reviewing a separate source document.
Error Patterns Worth Recognizing
Most discrepancies fall into a handful of predictable categories. Recognizing the pattern speeds up diagnosis.
- Transposition errors, where two digits get swapped during data entry. A $5,800 invoice recorded as $8,500 produces a $2,700 discrepancy. The tell is that the difference is always divisible by nine. If your out-of-balance amount divides evenly by nine, look for a digit swap.
- Slide errors, where a decimal point shifts one position and turns $1,500 into $15,000 or $150. These also produce differences divisible by nine, but the magnitude usually makes them obvious.
- Omitted entries. The transaction happened and the source document exists, but nothing in the books corresponds to it.
- Duplicate entries. The same transaction was recorded twice, doubling its effect on the account balance.
- Timing differences. A payment issued on December 31 clears the bank on January 2. The ledger and the bank statement disagree at year-end, but neither is wrong. Separating real errors from timing differences is one of the most important judgment calls in the process.
Working Through a Discrepancy
Finding a discrepancy is the start, not the end. Isolate whether the error originated in the source data, during entry, or during summarization. Trace the number backward: start at the financial statement, move to the trial balance, then to the general ledger, then to the sub-ledger, and finally to the source document. The layer where the number first diverges is where the problem lives.
Document the resolution whatever you find. The PCAOB requires that workpapers include information about any significant findings that initially appeared inconsistent with the final conclusions, along with how those inconsistencies were resolved. Evidence that contradicts your conclusions cannot be discarded. When documentation is added later to resolve a discrepancy, the addition must note the date, who prepared it, and why it was added.3Public Company Accounting Oversight Board (PCAOB). AS 1215: Audit Documentation – Appendix A
Materiality: Which Discrepancies Require Action
Not every discrepancy warrants the same response. A $12 rounding difference on a $50 million balance sheet is negligible. A $12 difference in a related-party disclosure might be significant. The concept that governs this judgment is materiality: would a reasonable investor’s decision change if they knew about the misstatement?4Public Company Accounting Oversight Board (PCAOB). AS 2105: Consideration of Materiality in Planning and Performing an Audit
Auditors set a materiality threshold at the start of the engagement, expressed as a dollar amount based on the company’s earnings, revenue, assets, and other relevant benchmarks. They also set a lower threshold called tolerable misstatement for individual accounts, so that the accumulated effect of several small errors doesn’t sneak past the overall materiality level.4Public Company Accounting Oversight Board (PCAOB). AS 2105: Consideration of Materiality in Planning and Performing an Audit
Materiality isn’t purely arithmetic. SEC guidance identifies qualitative factors that can make even a small dollar misstatement significant: whether it masks a change in earnings trends, converts a reported loss into income, affects compliance with loan covenants, or involves concealment of an unlawful transaction.5U.S. Securities and Exchange Commission. Staff Accounting Bulletin No. 99 – Materiality A discrepancy that looks trivial on a spreadsheet can become material the moment it touches one of these areas.
Red Flags That Point to Fraud
The process is built primarily to catch clerical mistakes, but the same procedures can surface patterns that suggest something worse. Management is uniquely positioned to override internal controls, and that risk exists on virtually every engagement.
Examine journal entries and manual adjustments closely, especially those recorded near the end of a reporting period. Top-side adjustments, where management posts entries directly to the consolidated statements rather than through the normal ledger process, are a classic override technique. Entries with round-dollar amounts, vague descriptions, or no supporting documentation deserve a second look.
Look at accounting estimates from prior years. If estimates consistently cluster at one end of the acceptable range and then swing to the other end, that pattern may indicate earnings management rather than good-faith estimation. Comparing current-year estimates against what actually happened in prior years can reveal systematic bias.
Investigate significant unusual transactions, particularly those involving related parties or entities created for a single purpose. A legitimate business transaction should have a clear economic rationale that someone can explain in plain terms. When the explanation requires a flowchart and three layers of intermediaries, the complexity itself is the red flag.
Correcting Errors After Discovery
How you fix an error depends on its size and when it originated. Errors immaterial to both the current and prior periods can be corrected through a simple adjusting journal entry in the current period. Record the correction, document why, move on.
Errors that were immaterial when they occurred but would distort the current period if corrected all at once require more care. The prior-period statements are revised the next time they appear as comparatives, with the opening balance of retained earnings adjusted for the correction.
Material errors in prior-period statements trigger the most disruptive outcome: a full restatement. The company reissues the affected financial statements as soon as practicable, adjusts opening balances of the earliest period presented, corrects each prior period individually, and labels each affected column as restated. The company must also disclose the nature of the error and its effect on every impacted line item.
Software That Automates the Mechanics
Tie-out software removes much of the manual work. These platforms import financial statement drafts and automatically verify that column totals, row totals, and cross-footing calculations are mathematically correct. They also scan for internal consistency, flagging instances where the same data point, such as a cash balance, appears in multiple places with different values.
Prior-year consistency checks are another core feature. The software compares current-year opening balances against the prior-period audited report, performing the roll-forward verification that would otherwise require side-by-side manual comparison. When a client provides an updated draft, the software identifies every change between versions, so you don’t re-verify the whole document from scratch.
Output is typically an exportable report that serves as the audit trail: every verified figure marked, every discrepancy flagged, the package ready to drop into the engagement file. These tools work across reporting frameworks, including U.S. GAAP and IFRS, because the underlying math is the same regardless of which standards govern presentation.
Automation doesn’t replace judgment. Software catches math errors and inconsistencies instantly, but it can’t evaluate whether an unusual journal entry makes business sense or whether an estimate reflects genuine conditions. The value is shifting time from mechanical verification to the analytical work that actually requires professional expertise.
Documentation and Retention
Workpapers need to tell a complete story on their own. Someone reviewing them years later, with no access to the original auditor, should be able to understand what was tested, what was found, and what was concluded. At minimum the documentation should include the tick mark legend, the population tested and the basis for any sampling decisions, every discrepancy identified, how each was resolved, and the final tied-out financial statements with all marks in place.
For public company audits, the PCAOB requires audit documentation to be retained for seven years from the date the auditor’s report is released.1Public Company Accounting Oversight Board (PCAOB). AS 1215: Audit Documentation If no report is issued, the seven-year clock starts from the date fieldwork was substantially completed. The retention period applies to the complete set of workpapers, not just the final report.
For tax-related records, the IRS generally requires businesses to keep records for three years from the filing date, with longer periods in specific situations and indefinitely if no return was filed. Employment tax records must be kept for at least four years.6Internal Revenue Service. How Long Should I Keep Records Anyone who destroys or falsifies records to obstruct a federal investigation faces up to 20 years in prison, which is a further reason workpapers documenting discrepancies and contradictory evidence must never be discarded.3Public Company Accounting Oversight Board (PCAOB). AS 1215: Audit Documentation – Appendix A