What are working papers?
Working papers are the records an auditor or accountant keeps to show the work done on an engagement: the planning, the procedures performed, the evidence obtained, the analysis and the conclusions reached. In an audit they support the opinion and must let an experienced auditor with no previous connection to the engagement understand what was done and why.
Also calledworkpapersaudit documentationaudit file
Compare the softwareBest audit software →All 8 audit vendors →
- Audit standard
- ISA 230; PCAOB AS 1215
- ISA file assembly
- Usually within 60 days
- Retention
- 5 years (ISA), 7 years (PCAOB)
What working papers contain and how they are kept
A typical file holds the engagement letter and planning, risk assessment and materiality, a lead schedule for each area tied to the trial balance, the detailed testing with references to evidence, notes of discussions with management, review points and their resolution, and the final financial statements. Each paper shows who prepared and reviewed it and when. International Standard on Auditing 230 sets the documentation rules for audits under ISAs: the final file is normally assembled within 60 days of the auditor's report and retained for at least five years. PCAOB AS 1215 requires auditors of US public companies to keep documentation for seven years. Accountants preparing accounts without an audit keep similar papers for their own quality control. Caseware has long been the standard desktop file; Inflo, Fieldguide and DataSnipper move working papers into the cloud and automate parts of the testing.
Workpapers vs working papers
Workpapers and working papers mean the same thing, and both spellings are used across audit and accounting software, standards and firm methodology.
What a complete working paper file contains
A complete file for an audit or an accounts production engagement holds four groups of papers. Lead schedules come first: one for each area of the accounts, such as receivables, payables, fixed assets, cash and equity, each agreed to the trial balance and showing the adjustments and the final figure. Reconciliations come second: bank accounts, debtor and creditor control accounts, payroll and tax balances and loans, each tied to the ledger balance with reconciling items explained. Supporting evidence comes third: the bank statements, invoices, confirmations, agreements and client schedules that the testing refers to, indexed so a reviewer can trace each figure back to its source. Review sign-offs come last: a record on each paper of who prepared it and when, who reviewed it and when, and how every review point was cleared. Around these sit the engagement letter, the planning and risk assessment, the materiality calculation, the conclusion for each area and the final financial statements agreed to the lead schedules.
Working paper structure and referencing
Every area of the file follows the same chain: the trial balance feeds a lead schedule, the lead schedule points to supporting schedules, and the supporting schedules point to evidence. ISA 230 does not prescribe an index system, so the reference codes below are a common firm convention, not a requirement of the standard. Take receivables as an illustration. The trial balance shows receivables of 1,250,000 and carries the reference C1 beside the line. Lead schedule C1 lists that balance, a proposed adjustment of (30,000) for a bad debt provision, and a final figure of 1,220,000, and it states the conclusion for the area. Supporting schedule C2 is the receivables ledger listing, agreed in total to the control account. C3 holds the confirmation and subsequent receipts testing on selected balances. C4 calculates the provision behind the adjustment. Cross-references run in both directions. C1 carries a reference to C2, C3 and C4 beside each figure those papers support, and each of those papers carries C1 in its header so a reviewer can move up or down the chain. Source documents such as bank statements and signed confirmations are indexed under the schedule that relies on them. A tickmark legend on each page or at the front of the file explains every symbol used, for example one for agreed to the ledger and one for agreed to a bank statement. Each paper also names its purpose, source, work done and conclusion, together with the preparer and reviewer initials and dates.
Year-end working paper checklist
A practice normally prepares the same set of schedules for each client file at year end. The working trial balance comes first, with adjusting journals listed and the final balances agreed to the draft accounts. Fixed asset schedules follow, showing cost, additions, disposals, depreciation and net book value, with the depreciation charge reconciled to the profit and loss account. Bank reconciliations for every account are agreed to the statement balance at the year-end date. Debtors and creditors schedules list the open items behind each control account and support any bad debt provision. A stock or inventory schedule records the count date, the valuation basis and any write-downs. Accruals and prepayments schedules show how each estimate was calculated. Payroll and tax schedules reconcile wages, payroll tax liabilities and sales tax or VAT control accounts to the returns filed. Loan and lease schedules agree balances to lender statements and split amounts due within and after one year. Equity and director or owner loan account schedules trace the movements in the year. Income tax or corporate tax computations close the file, together with a completion checklist and a record of who prepared and reviewed each schedule.
Cloud workpaper workflow
In a cloud workpaper tool the engagement file sits in one place and the whole team works in it at the same time. The trial balance is imported from the client's accounting system rather than retyped, and lead schedules link back to it, so a change to a balance or an adjustment updates the schedules and workpapers that depend on it. That linkage is the tie-out: the figure on each lead schedule is agreed to the trial balance, and the detailed testing behind it is referenced from the schedule. Review runs inside the file. In Silverfin, reviewers leave review notes, changes are tracked and tasks are assigned to named team members within the working paper. Sign-off follows the documentation rule in ISA 230: each paper records who performed the work and when, and who reviewed it and when. Where testing relies on source documents, tools such as DataSnipper let the reviewer see what the automation did, while the preparer stays responsible for the conclusion and the reviewer for the sign-off.
Linking working papers to the ledger
Linking a working paper file to the client's ledger removes the retyping of balances and the transcription errors that come with it. Xero Workpapers extracts client data from Xero automatically, shows account groupings and a trial balance in a working format, and lets staff draft adjustments and tax calculations without changing the ledger. CaseWare Working Papers imports a trial balance or general ledger detail from more than 60 accounting systems, and its cloud financial statements product can import directly from online packages such as QuickBooks Online and Xero. Silverfin connects to bookkeeping systems including Xero and builds working papers from the client data. In IRIS Elements Accounts Production, the Professional and Enterprise plans import a trial balance from Xero through an API, and adjustments are posted after import to complete the final trial balance. In each case the imported trial balance is the starting point: adjustments sit in the working paper file, and the accountant agrees the final figures back to the ledger before the accounts are signed.
Paper vs digital working papers
The format of the file does not change the obligations. Paper and digital files must both show who did the work, who reviewed it and when, and both must be kept for the full retention period. In the UK, ICAEW's audit regulations require audit working papers to be kept for six years, and for statutory audits the final file must be completed no later than 60 days after the audit report date. ICAEW also tells firms to consider data protection law when deciding how long to keep papers, to keep a record of files they destroy, and to take care that papers which also serve tax purposes are not destroyed while a longer period applies. Its guidance on audit file assembly sets out what regulators look for at inspection. In the US, PCAOB AS 1215 requires auditors of public companies to keep documentation for seven years. The PCAOB has cut the time allowed to assemble a complete and final set of documentation from 45 days to 14 days after the report release date, phased in from 2025 audits for firms with more than 100 public company audit clients and a year later for other firms. For audits of private companies under AICPA standards, the assembly window is 60 days. Digital files make the review trail easier to prove, because the system timestamps each preparer action and reviewer sign-off and keeps a record of later changes, which a paper file can only show through handwritten initials and dates.
Paper to digital workpapers
Moving from paper to software turns tick marks into symbols held in the file, cross-references into links between papers, and review notes into tracked comments that stay attached to the paper they relate to.
Digital working papers: Caseware, Inflo and Silverfin
Cloud and desktop engagement tools replace the folder of separate spreadsheets, scanned PDFs and emailed review points with one engagement file in which papers are linked to each other. In CaseWare Working Papers the trial balance connects to adjustments, lead schedules and financial statements, and linked workpapers keep totals, notes and cross-references consistent when a value changes. Caseware's annotation features add notes, tickmarks and references to accounts, totals and document lines. Notes are numbered automatically, tickmarks are kept in a single worksheet and show who created them and when, and a document reference links straight to another paper in the file. Inflo Workpapers centralizes engagement management and audit documentation in one workflow, with content packs that firms can use as supplied or customize, and tie-ins and dashboards that give engagement leads a live view of progress. Silverfin builds working papers from the client's bookkeeping data, and reviewers leave review notes, changes are tracked and tasks are assigned to named team members inside the paper. The review and sign-off trail is the main gain over an Excel binder. Each preparer action and reviewer clearance sits in the same file as the work, attached to the paper it relates to, so an inspector can see who signed what and when without reconstructing it from email. The tool records the trail, but the standards still place responsibility on people: the preparer for the work and the reviewer for the sign-off.
Workpaper software
Workpaper software covers three jobs: preparing the papers, referencing them to each other and to evidence, and recording review and sign-off. CaseWare Working Papers prepares papers in one engagement file where the trial balance links to adjustments, lead schedules and financial statements, and it rolls prior-year files forward with documents and mappings reused. Its annotation tools handle referencing, with tickmarks that show who created them and when and document references that link to other papers. Silverfin prepares papers from client bookkeeping data, and reviewers leave review notes, changes are tracked and tasks are assigned to named team members inside the paper. Aprilis works from source documents such as contracts, leases and trial balances, and produces Excel workpapers with live formulas, supporting schedules and source references. Users review the workbook tab by tab and cell by cell, and an optional review by licensed CPAs is available.
Retention and review rules: ISA (UK) 230 and AU-C 230
Both standards rest on the same test: documentation must be enough for an experienced auditor with no previous connection to the engagement to understand the procedures performed, the evidence obtained and the conclusions reached. Both require the auditor to record who performed the work and when, and who reviewed it and when. ISA (UK) 230, issued by the UK Financial Reporting Council, requires the auditor to complete the administrative assembly of the final audit file on a timely basis after the date of the auditor's report. ICAEW sets that at no later than 60 days for statutory audits and requires audit working papers to be kept for six years. If exceptional circumstances after the report date call for new or additional procedures, the auditor documents the circumstances, the procedures performed, the conclusions reached, and who made and reviewed any change to the file and when. In the US, AU-C 230, issued by the AICPA, applies to audits of private companies. It requires the final audit file to be assembled no later than 60 days after the report release date. After the documentation completion date the auditor may not delete or discard audit documentation before the end of the retention period, and that period may not be shorter than five years from the report release date. Audits of US public companies fall under PCAOB AS 1215, which sets seven years.
Retention rules by region
UK audit firms keep audit working papers for six years under ICAEW's audit regulations. US firms keep them for at least five years from the report release date for private company audits under AU-C 230, and for seven years for public company audits under PCAOB AS 1215. In the EU, Regulation (EU) No 537/2014 requires auditors of public interest entities to keep the documents and information it lists for at least five years, and member states may require a longer period.
Common questions
Who owns audit working papers?+
The audit firm. Clients can be given copies of schedules they provided or that are useful to them, but the file belongs to the auditor and is subject to professional confidentiality and regulatory inspection.
What is a lead schedule?+
A summary working paper for one area of the accounts, such as receivables, showing the balances from the trial balance, any adjustments and the final figures, with references to the detailed testing behind them.
Can working papers be changed after the audit report is signed?+
Only in limited ways. After the final file is assembled, documentation cannot be deleted before the end of the retention period, and any later addition must be dated and record who made it and why.
Working paper software
Workpaper software compared
| Software | What it produces | Who it suits |
|---|---|---|
| CaseWare Working Papers | Linked trial balance, lead schedules and workpapers, with financial statement packages exported to PDF | Accounting and audit firms, including tax, review and client advisory engagements |
| Silverfin | Working papers fed by client bookkeeping data, which pre-populate accounts production and tax files | Accountancy firms doing compliance and advisory work |
| Inflo | Audit working papers, data analytics across all transactions and a client collaboration workspace | Audit firms of all sizes, from small practices to global networks |
| DataSnipper | Evidence extracted from documents and matched inside Excel, with audit reports built in Excel | Audit and finance teams, including external audit, internal audit and tax |
Working paper software for accountants
Caseware, Silverfin and IRIS take different routes to a finished working paper file. CaseWare Working Papers is a desktop engagement product that keeps assurance and accounting working papers in a single engagement file. Trial balance data links to adjustments, lead schedules and financial statements, so an update flows through each of them. Firms can build their own templates or use Caseware's pre-built ones, and prior-year files are rolled forward with documents and mappings reused. Silverfin starts from client bookkeeping data: it connects to bookkeeping systems, builds working papers from that data and feeds them into its accounts production templates. IRIS Elements Accounts Production is sold as cloud accountancy software. It produces accounts from an imported trial balance, with adjustments posted afterwards, and shares client data and trial balance information with IRIS Elements Tax. Basic, detailed and variance trial balance reports export to PDF and Excel, with the detailed and variance reports limited to the higher plans. Caseware is built around the engagement file, Silverfin around the client data feed, and IRIS around the accounts and tax workflow.
Working papers software for accountants
Four names come up most often when accountants look for working papers software for year-end and accounts production files. Silverfin connects to bookkeeping systems including Xero, builds working papers from the client data and feeds them into its accounts production templates, which produce iXBRL-tagged statutory accounts. CaseWare Working Papers imports a trial balance or general ledger detail from more than 60 accounting systems, links it to adjustments, lead schedules and supporting workpapers, rolls prior-year files forward and exports financial statement packages to PDF, with a client portal for requests for prepared-by-client documents. Wolters Kluwer sells CCH ProSystem fx Engagement as the on-premise product and CCH Axcess Engagement as the cloud version, both managing workpapers and trial balances, with trial balances linked to lead sheets and financial statements. Xero Workpapers is a practice tool that pulls client balances directly from Xero. Xero has announced a new version built with BGL, planned for selected practices from January 2026 and for all partners during 2026. It adds a working trial balance, draft adjustments that do not change the ledger, prior-year rollover and bulk updates of statuses, preparers and reviewers. Practices can stay on the existing product or move to the new one.
Part of Accountio’s accounting technology coverage · Glossary
