Ready to begin
The team felt good about the start.
One item didn’t quite make sense
One of the first procedures involved testing revenue. The team received the client’s revenue report and began selecting items for testing. The report looked familiar. The numbers looked reasonable. So the work continued.
So they went back to the client.
Back to the audit plan
The procedure had been designed around the assumption that the report represented the complete population. Now they had to understand:
A procedure that looked straightforward suddenly required more work.
Nobody withheld anything
None of this was caused by the client withholding information. In fact, the client had provided exactly what the audit team had requested. That was what made the issue easy to miss.
- “We didn’t receive the information.”
- “We hadn’t understood the information before deciding how we were going to use it.”
The report had a name. It had a date. It had numbers. It looked complete. But the team hadn’t initially asked:
What exactly does this population represent?
And that question mattered. Because an audit procedure can be perfectly designed for the wrong population.
The real cost
The team eventually resolved the issue. But the cost was more than the additional questions.
Receiving information is not the same as understanding information. A PBC list can be fully cleared while important questions remain unanswered.
Before relying on client-generated information
Tap each one you can answer with confidence.
- What exactly does this report represent?
- Where did it come from?
- How was it generated?
- Is anything manually changed or excluded?
- Does it reconcile to another reliable source?
- Is it actually appropriate for the procedure we intend to perform?
Continue the series
Schedule Your Personalised Consultation
Talk to our team about offshore audit and finance support for your firm.