Identify the engagement the user actually needs

A lender may request audited statements, an owner an explanation of a disputed balance, and an investor analysis of transaction risks. Obtain the intended user’s written requirements for the subject, period, format and criteria.

Under ISA 200, an audit supports an opinion on financial statements against the applicable framework in all material respects. Reasonable assurance is high, not absolute; it does not guarantee detection of every error or the company’s future.

In agreed-upon procedures, specified procedures and their factual findings are reported. That report is not a substitute for an audit opinion. Accounting diagnostics also need their own purpose and boundaries.

Define the need before commissioning
NeedClarification
Audited statementsPeriod, framework and required report
A specific figure checkedSubject, criteria, procedures and output
Accounts reconstructedPeriod, available records and deliverables
A transaction assessedDecision, scope and information limits

Statutory audit obligations and practitioner eligibility require separate consideration for the particular company. This explanation does not mean every engagement can be accepted without that assessment.

Keep preparation and audit responsibilities distinct

An audit does not transfer management’s responsibility for the statements to the auditor. Applicable independence and service-compatibility requirements must be addressed before acceptance, including previous involvement in preparing the information.

Appoint a request coordinator and owners for cash, sales, purchases, inventory, employees and contracts. The coordinator cannot reliably explain facts known only to the warehouse or project manager.

If records are incomplete, identify the reconstruction required, who will perform it and its effect on scheduling. A desired report date does not make missing information available.

Connect statements to transaction evidence

Use the chain: statement line, relevant accounts, supporting schedule, transaction and document. Label exports with entity, period, preparation date and version. Identically named files with different totals create avoidable confusion.

Preparation map
AreaMaterialsExplanation
CashStatements, reconciliations, restrictionsAccount-to-balance connection
Sales and debtsContracts, delivery and paymentsPeriods, returns and disputes
InventoryQuantities, costs and count informationCondition and discrepancies
LiabilitiesAgreements, calculations and schedulesCompleteness and timing
Estimates and unusual itemsAssumptions and decisionsBasis and economic purpose

This is a company preparation map, not a universal audit procedure list. The auditor determines further needs for the engagement. File volume does not establish quality; records must be relevant, consistent and traceable.

Example: a stock report is only the starting point

Illustration: reported inventory is TJS 500,000 and a warehouse listing matches it. That does not resolve damaged items, third-party property, slow-moving stock or unreconciled count differences.

Assemble quantities, cost support, count information, movement records and explanations of known differences. Identify inventory held by others and the evidence available. The auditor determines the specific evidence procedures.

Do not backdate missing records or create a fictitious count merely to complete a file. Disclose missing dates or evidence and discuss their implications. A hidden gap is harder to address than an identified limitation.

Manage requests and changes consistently

Maintain a log of requests, owners, agreed dates, submissions, follow-up questions and status. Sending a file does not necessarily close the question if its period or explanation is incomplete.

When statements change, provide a new version with a change list. Keep previous versions in the history. Record each adjustment’s amount, basis, accounts and reporting effects.

Use agreed transfer channels and suitable access rights. Employee records and commercial information should not be placed in a public folder for convenience. Information discipline makes the work more controlled and efficient.

Respond to findings with evidence

Distinguish an established error, an evidence request and a process recommendation. An adjustment needs a basis; a request needs information; a recommendation needs a management decision.

For disputed points, document facts, management’s position, supporting records and what remains unresolved. Wanting to retain the original figure is not an explanation for rejecting an adjustment.

Do not agree an unmodified outcome in advance. The report depends on findings, available evidence and applicable requirements. An issue may require corrections, disclosures or another response based on the engagement circumstances.

Turn the result into follow-up actions

Confirm which statement version and period the report covers, the accompanying documents and any engagement-specific use restrictions. Discuss matters communicated to management separately.

Give agreed improvements an action, owner, date and review method. “Improve receivables control” becomes actionable only when the reconciliation frequency, disputed-balance review and responsible person are defined.

For a discussion with BMS, prepare the user’s requirements, reporting period, business description, accounting status and known gaps. These support a realistic scope discussion without predetermining the result.

Support for your task

Discuss your task

Describe the situation and the output you need. Establish the work and information required to begin.