Skip to main content
FinTrace

Working Papers for Forensic Accounting Matters

Make financial working papers reproducible. Link instructions, source records, calculations, judgement and review while keeping the final report distinct.

Published
Updated

Working papers record the work performed, evidence obtained and conclusions reached in a forensic accounting matter. They let another competent accountant follow the reasoning and reproduce the calculations behind a finding. A clear file also shows where the evidence leaves a question unresolved.

Define the Working File and Its Purpose

The working file contains the instructions, source records and analysis that support the engagement’s conclusions. The delivered report communicates the results to its intended readers. A report’s concise payment finding can therefore depend on several underlying schedules and review notes.

For Australian professional accountants within its scope, APES 215 Forensic Accounting Services, paragraph 7.3, requires working papers explaining the work and the basis and methods behind calculations, determinations or estimates. A spreadsheet total without its inputs or method leaves that basis unexplained.

The preparer records what they did and why. A reviewer tests the evidence and reasoning, then records unresolved points and their resolution. The responsible forensic accountant uses that file to support their conclusions. Instructing lawyers can need access to relevant material when considering advice or production obligations.

These are professional engagement records. Academic working papers are research papers circulated for discussion and have a different purpose. In an expert engagement, the financial expert witness report is an output supported by the working file.

Organise Instructions, Sources and Procedures

Start the matter index with the accepted questions. Each question needs a route through the source register to the procedure and resulting schedule. Preserve the engagement instructions and any agreed changes beside that index.

For a disputed supplier payment, the index might identify question Q1, bank source B01, invoice source I01 and schedule WP-04. Record who supplied each document and retain its original filename. Add the account, statement period and page reference so a reviewer can find the cited entry without guessing.

Use the following sequence when building each schedule.

  1. Record the accepted question and the financial period being examined.
  2. Identify the records received and the records still needed to answer it.
  3. Describe the procedure, including any filters or exclusions applied to the records.
  4. Link the result to the calculation and the preparer’s reasoning.
  5. Assign a reviewer and carry unresolved exceptions into a review-points register.

A missing invoice belongs beside the affected payment, even if the source register also records the gap. If two statements conflict, preserve both and explain which figure the schedule uses. A complete folder tree cannot establish that every required record was supplied.

For a large statement bundle, FinTrace saves hours of conversion and review by delivering a searchable ledger and findings with direct PDF references. Forensic accountants can incorporate these outputs into their analysis file and document the procedures and professional judgements for their engagement. The source references keep the underlying transaction evidence at hand.

Record Calculations and Professional Judgement

Show the inputs and method before stating the conclusion. Explain the meaning of each amount, including whether it is a debit, credit or offset. Keep any tax or currency assumption beside the calculation it changes.

A bank debit establishes that money left an account. An invoice records the supplier’s stated charge. Matching the amounts can support a payment explanation, but the match alone does not establish that the work occurred or the payment was authorised.

Record alternative explanations that could change the finding. An apparent overpayment might be an advance for another job, a duplicate payment or a settlement of earlier invoices. State which records support each explanation and why it was accepted, rejected or left open.

Keep source facts separate from assumptions and inferences in the schedule. Identify an oral explanation as an explanation, including who gave it and where the note is retained. A specific finding’s audit trail connects that analysis to the underlying records and subsequent changes.

Work Through a Reviewable Payment Schedule

This fictional example concerns a payment to Harbour Repairs. The accepted question is whether the supplied records explain a $13,200 debit. The example assumes both amounts use the same currency and compares their gross values without a tax adjustment.

Payment Schedule WP-04

File itemSource or methodRecorded result
Bank paymentB01, trading-account.pdf, PDF page 8, debit row carrying reference HR-318$13,200 paid to Harbour Repairs
Supporting invoiceI01, invoice-HR-318.pdf, PDF page 1Gross invoice total of $12,100
Initial calculation$13,200 less $12,100$1,100 difference requiring explanation
Preparation notePrepared by Alex, with preparation date and version recorded in the filePayment reference matches the invoice number. The extra $1,100 has no identified explanation in B01 or I01.
Reviewer exception R1Reviewed by Morgan against B01 and I01Arithmetic agrees. Request evidence of another charge or a refund before resolving the difference.
Additional sourceB02, following-statement.pdf, PDF page 2, credit row carrying reference HR-318 refund$1,100 returned by Harbour Repairs
Revised calculation$13,200 payment less $1,100 refundNet cash outflow of $12,100, matching I01
Review resolutionMorgan reproduces both calculations from B01, B02 and I01Amount difference resolved. Whether the work was performed and authorised remains outside this payment reconciliation.

The preparer initially records a $1,100 unexplained difference. Calling that difference a loss would go beyond the records then available. After B02 arrives, the revised schedule explains the net outflow while preserving the original finding and the refund evidence.

The reviewer opens the cited pages, checks the payment and refund references, then recalculates the net outflow. The review note records that work and its result. A tick beside the total would leave the reader unable to tell what the reviewer checked.

If the refund reference were absent or the payer differed, the reviewer would leave R1 open and request evidence connecting the credit to this payment. An equal amount by itself would not settle the exception.

Preserve Review and Later Changes

Identify the preparer and reviewer for each schedule and record when their work occurs. Give each review point a location, owner and status. Resolve it with the additional evidence or reasoning, including any effect on the conclusion.

Keep completed versions distinguishable when new records arrive. For WP-04, retain the original schedule, add B02 to the source register and issue a revised version. Record that the refund changes the unexplained difference from $1,100 to zero and identify any report passage that needs updating.

Separate a correction to a copied figure from a changed conclusion based on new evidence. Both need an explanation, but they have different causes. Preserve the superseded version so a later reader can reconstruct what the accountant knew at each stage.

For applicable non-assurance firms, APES 320 addresses engagement-documentation controls. Paragraphs 4.49 and 4.53 cover file assembly and protection, including identifying who creates, changes or reviews records. Restrict editing of completed files, retain backups and test that archived schedules and their supporting records remain retrievable.

Assess Retention, Access and Production Separately

Apply the engagement terms and relevant professional framework alongside the law governing the matter. Retention, ownership and permission to disclose are separate questions. Owning a schedule does not decide whether it must be produced.

APES 320 ties retention to the firm’s needs and legal or regulatory requirements, without prescribing one universal period for every forensic file. It generally treats engagement documentation as firm property, subject to law or regulation. Original source documents supplied by the client remain the client’s property.

Restrict confidential material to authorised people and record any release. A document request needs assessment against its actual scope and the applicable legal process. APES 215 also recognises that forensic working papers can be required as evidence.

An internal label does not establish legal professional privilege. The Australian Government Solicitor’s privilege guidance explains the relevance of confidentiality and the dominant purpose of obtaining legal advice or legal services for litigation. The applicable rules and any waiver need document-specific assessment.

When a request arrives, preserve the file and send the request to the responsible lawyer. Identify the requested schedules, source records and relevant correspondence so the lawyer can assess production and any privilege claim. Record the resulting release decision separately from the accountant’s financial conclusion.

FinTrace

Statements in. Evidence out.

FinTrace turns your bank statements into one searchable Excel ledger and a written findings report, with every finding cited to its source page.

See how FinTrace worksNo software to learn · Every finding sourced