You Sent the Documents, So Why Is the Auditor Asking for More?
Your finance team has spent several days preparing for the annual audit. Bank statements have been downloaded, supplier invoices organised, customer records exported, contracts placed into folders and the latest financial statements sent to the auditor. Everyone feels relieved because the difficult part appears to be over. Then an email arrives from the audit team containing another list of requests. They want supporting documents for selected transactions, explanations for several balances, copies of agreements and additional information about certain customers and suppliers. Your finance employee sends everything requested, only for another email to arrive two days later asking follow-up questions about some of the documents already provided. For a business going through an audit, this can be frustrating. Management may reasonably wonder why the auditor cannot simply examine the documents that were initially provided and complete the work. The answer is that professional audit services Singapore involve much more than collecting documents. Auditors need to obtain sufficient appropriate audit evidence to support their conclusions, and sometimes one document answers one question while creating several others.
An Audit Is Not a Document Collection Exercise
It is easy to imagine an audit as a process where the company hands over its accounting records and the auditor checks whether everything looks correct. In reality, the auditor is trying to obtain evidence about the financial statements. A document is useful only to the extent that it helps address the relevant audit objective. For example, an invoice can provide information about what a supplier billed the company, but that does not necessarily answer every question relating to the transaction. Depending on the circumstances, the auditor may also need evidence regarding whether the goods or services were actually received, whether the transaction belongs in the correct accounting period, whether the amount was appropriately recorded and whether the company had an obligation relating to it. The number of documents requested therefore does not necessarily indicate that something is wrong. It may simply reflect the different pieces of evidence needed to understand and test a transaction properly.
The First Document May Prove Only One Part of the Story
Suppose a company purchases equipment for S$100,000 and provides the supplier invoice when the auditor requests supporting documentation. The invoice establishes useful information such as the supplier, description, amount and invoice date. However, the auditor may still need to understand whether the equipment was delivered, whether the company owns it, when it became available for use and how the amount was accounted for. Depending on the nature of the transaction, additional documentation could include purchase agreements, delivery documents, payment records or other relevant evidence. The invoice itself is not necessarily inadequate. It simply answers certain questions and not others. This is why businesses should avoid assuming that sending one document with the correct amount automatically resolves every audit question relating to that balance.
A Matching Number Is Helpful, but It Does Not Prove Everything
One of the most common misunderstandings is that if the amount on an invoice matches the amount recorded in the accounting system, the auditor should be satisfied. Matching is certainly useful, but financial statement audits involve more than mathematical agreement. Imagine the accounts contain a S$50,000 expense and the company produces a S$50,000 invoice. The numbers match perfectly. But what if the invoice actually relates to a service that will be provided during the next financial year? What if part of the amount represents an asset rather than an immediate expense? What if the transaction belongs to another entity in the group? The auditor may need additional information to understand whether the accounting treatment is appropriate. The question is therefore not merely, “Does this document contain the same number?” It is also, “What does this transaction represent, and has it been reflected appropriately in the financial statements?”
The Auditor May Need Evidence That Comes From Outside the Company
Evidence created internally by the company can be valuable, but auditors may also obtain information from independent external sources depending on the circumstances. This is why businesses sometimes receive requests involving bank confirmations, customer confirmations, legal information or other third-party evidence. Management may wonder why a bank statement already provided is not always enough, or why the auditor wants confirmation from a customer when invoices and payment records exist. Independent evidence can provide a different perspective from information generated within the business. The appropriate evidence depends on the audit procedure and risk being addressed, which is why the audit team may request information that appears repetitive from management’s perspective but serves a different purpose in the audit.
Your Invoice Shows What Was Billed, Not Necessarily What Happened
Consider a consulting company that receives a supplier invoice dated 30 December for S$40,000. The invoice appears to belong to the financial year ending 31 December. However, the underlying consulting work may actually be scheduled for January and February. Alternatively, the work may have been completed in December even though the supplier does not issue the invoice until January. Looking only at the invoice date could therefore produce the wrong conclusion. The auditor may ask for a contract, service agreement, correspondence or other information to understand when the underlying activity occurred. What feels like an unnecessary second document may actually answer a different accounting question from the first.
Year-End Transactions Naturally Attract More Questions
Transactions occurring close to the financial year-end often receive additional attention because timing can affect which reporting period includes the revenue, expense, asset or liability. If a company’s year ends on 31 December, transactions from late December and early January may be particularly relevant. A supplier invoice dated 3 January might relate to goods delivered on 29 December. A customer invoice dated 30 December might relate to services performed in January. Simply relying on invoice dates could therefore misstate the financial results of either period. This is why auditors may ask for delivery orders, contracts, service completion records or other supporting information around year-end. The objective is not to make the process unnecessarily complicated. It is to understand whether transactions have been recorded in the appropriate period.
Customer Receivables Can Require More Than an Invoice
Suppose the company reports that a customer owes S$200,000 at year-end. Management provides the invoice, and the invoice agrees exactly with the accounting records. The auditor may still need additional evidence about the receivable. Has the customer acknowledged the balance? Was the underlying sale genuine? Has the customer subsequently paid? Is the amount disputed? Has the balance remained outstanding for a long time? These questions become especially important when receivables are old or significant. A subsequent bank receipt may provide useful evidence that the customer ultimately paid. A customer confirmation may provide another form of evidence. If the balance remains unpaid long after year-end, the auditor may need further information about its recoverability. The original invoice remains important, but it cannot necessarily answer all these questions.
“The Customer Will Pay” May Lead to Another Question
Business owners often know their customers personally and may be confident that an outstanding amount will eventually be collected. From management’s perspective, saying “They always pay, just slowly” may feel like a perfectly reasonable explanation. The auditor, however, may need evidence supporting management’s assessment, particularly when the amount is significant or has been overdue for a long period. That can lead to requests for subsequent payment records, correspondence with the customer, repayment arrangements or other relevant information. This does not necessarily mean the auditor distrusts management. Professional scepticism requires auditors to evaluate evidence rather than relying solely on verbal assurances.
Supplier Balances Can Create the Opposite Problem
With customer receivables, one concern may involve whether recorded balances exist and can be recovered. Supplier balances can create a different concern because businesses also need to consider whether all relevant obligations have been recorded. Imagine a supplier completed S$80,000 of work before year-end but did not send the invoice until several weeks later. If finance did not know about the transaction, the liability might not appear in the initial accounts. The auditor may therefore examine payments and invoices after year-end or ask management about goods and services received before the reporting date. This can create requests for January or February documents even though the audit concerns a December year-end. Management may ask why the auditor is looking at next year’s invoices, but those documents can provide information about obligations that existed before the previous year ended.
Bank Statements Tell the Auditor Where the Money Went, Not Always Why
A bank statement can show that S$70,000 was transferred to a supplier. It does not necessarily explain the commercial purpose of the payment. Was it payment for an invoice? A refundable deposit? Purchase of equipment? Repayment of a loan? An advance for services to be provided next year? The same cash movement could have very different accounting implications. This is why an auditor may request the bank statement and then ask for the invoice, agreement or explanation relating to the transaction. From the client’s perspective, it may feel like the auditor already has evidence of the payment. From the audit perspective, the payment is only one part of understanding what the transaction represents.
Contracts Often Explain What Invoices Cannot
Invoices usually contain relatively limited information. A contract can provide details about payment terms, obligations, milestones, cancellation rights, service periods and other commercial conditions that may affect accounting. For significant or unusual transactions, auditors may therefore request the underlying agreement even when invoices have already been provided. This is particularly relevant for arrangements that extend across multiple reporting periods or contain several components. Management may see the contract as a legal document unrelated to the accounting process, but its terms can be essential for understanding the economic substance of the transaction.
Large Transactions Usually Deserve More Attention
Not every transaction receives the same level of audit attention. A S$100 monthly subscription and a S$1 million asset purchase do not necessarily create the same level of financial statement risk. Auditors plan their procedures based on factors such as materiality, risk and the nature of balances and transactions. Significant or unusual items may therefore result in more extensive requests. This does not mean that the auditor believes a large transaction is suspicious. It simply means that a material error involving a large amount could have a greater effect on the financial statements than an error involving an insignificant amount.
An Unusual Transaction Can Matter Even When the Amount Is Small
Size is not the only factor that can influence audit attention. A transaction may be unusual because of who was involved, how it was structured or when it occurred. Related-party transactions, unusual journal entries or transactions outside the normal course of business may require additional understanding depending on the circumstances. The auditor may ask questions even when management considers the amount relatively small. This is another reason businesses should not interpret the length of an audit request as a direct indication of the amount involved. Audit procedures consider the nature and risk of transactions as well as their monetary value.
The Auditor Does Not Normally Check Every Single Transaction
Many companies process thousands or even millions of transactions each year. Checking every invoice, payment and receipt individually would often be impractical and unnecessary. Auditors therefore use approaches that can include sampling, analytical procedures, controls testing and other audit techniques depending on the engagement. This is why the audit team may request supporting documents for particular transactions rather than asking for every document in the company. The selection may include significant items, unusual transactions, representative samples or items identified through other audit procedures. If your transaction appears on the list, it does not automatically mean the auditor thinks something is wrong with it.
Why Did the Auditor Choose This Particular Invoice?
This is a common question from finance teams. They may see thousands of perfectly ordinary transactions in the ledger and wonder why the auditor selected a particular S$8,000 invoice. Audit selections can arise for different reasons. Some items may be selected because of their size, some because they meet particular characteristics and others as part of a sample intended to obtain evidence about a wider population. Businesses therefore should not spend too much time trying to interpret every selection as a hidden signal. The best approach is usually to provide the requested supporting information clearly and promptly, and ask for clarification when the request itself is unclear.
Follow-Up Questions Do Not Automatically Mean the First Answer Was Wrong
Imagine the auditor asks why the company paid S$120,000 to a particular supplier. Finance replies that the payment relates to new machinery and provides the invoice. The auditor then asks when the machinery was delivered. Finance provides a delivery document. The auditor then asks when it became available for use. To the finance employee, this can feel like the auditor keeps moving the goalposts. In reality, each answer may provide information that determines the next relevant question. Audit work often develops as evidence is obtained. A follow-up request therefore does not necessarily mean the previous response was inadequate. It may simply mean the auditor now understands enough about the transaction to identify what additional evidence is required.
Sometimes Your Answer Creates the Next Question
Suppose management explains that a S$300,000 payment relates to a loan from a related company. That answer immediately creates several potential questions. Is there a loan agreement? What are the repayment terms? Is interest charged? Has interest been recorded? How is the related party disclosed? The initial explanation may be completely correct, but understanding the nature of the transaction naturally leads to additional audit considerations. Businesses can reduce frustration by recognising that an audit is an investigative process in the neutral sense of understanding transactions, not a fixed checklist where every question can always be predicted at the beginning.
Poorly Organised Documents Can Multiply Audit Requests
Sometimes the auditor is not asking for genuinely new information. The information may already have been provided but is difficult to identify. A company might upload hundreds of files named “scan001.pdf”, “invoice final.pdf”, “document2.pdf” and “WhatsApp Image.pdf”. The audit team then spends time trying to determine which document supports which transaction. When evidence cannot be linked clearly to a request, follow-up questions become more likely. A simple naming structure can make a surprisingly large difference. Files can be labelled with supplier names, invoice numbers or audit-request references so that both the company and auditor can identify them quickly.
Sending Everything Is Not Always Better Than Sending the Right Thing
Some finance teams respond to audit requests by uploading an enormous folder containing every document they can find. This feels efficient because the auditor now has everything. In practice, it can make the process slower if the audit team has to search through hundreds of irrelevant documents to locate the evidence requested. A more effective response is usually organised and specific. If the auditor requests supporting documentation for ten transactions, clearly identify the documents corresponding to each transaction. Good audit preparation is not measured by how many gigabytes of files are uploaded. It is measured by how easily the relevant evidence can be understood and traced.
Missing Explanations Can Make Good Documents Difficult to Understand
A document that makes perfect sense to an employee may not be self-explanatory to someone outside the daily operations of the business. An internal spreadsheet might contain abbreviations everyone in the company understands. A payment may relate to a commercial arrangement the managing director remembers immediately. The auditor does not necessarily have that background knowledge. Providing a brief explanation alongside complex or unusual documents can therefore save time. The goal is not to write an essay for every invoice but to give enough context for the evidence to be understood.
Different Versions of the Same Spreadsheet Create Confusion
Another common problem occurs when finance sends a schedule, updates it later and sends a second version without clearly identifying what changed. The auditor may have already performed procedures using the first version. If balances change, the audit team may need to understand why and potentially redo work. File names such as “Final.xlsx”, “Final2.xlsx”, “Final Latest.xlsx” and “Final Latest NEW.xlsx” are familiar in many offices, but they create unnecessary uncertainty. Businesses can improve audit efficiency through simple version control and by clearly communicating when schedules have been updated.
The Trial Balance Is the Beginning, Not the Entire Audit
The trial balance provides an important summary of the company’s accounting records, but it does not independently prove that every balance is appropriate. An account labelled “Professional Fees S$250,000” tells the auditor the amount recorded under that category. It does not explain which suppliers were involved, what services were received, whether amounts relate to the current period or whether any unusual items exist within the balance. Auditors therefore analyse the underlying transactions and supporting information for relevant areas. Management should expect the audit to move from summary numbers into detailed evidence where necessary.
Reconciliations Can Answer Questions Before They Are Asked
Well-prepared reconciliations can make an audit significantly easier. A bank reconciliation explains differences between the accounting balance and bank statement. An accounts receivable schedule shows which customers make up the total receivable balance. A fixed asset register explains the assets underlying the financial statement balance. When these schedules agree with the accounting records and contain useful supporting detail, auditors can understand balances more efficiently. Poor or incomplete reconciliations often create additional questions because the audit team first needs to determine why different sources of information do not agree.
A S$10 Difference and a S$100,000 Difference Are Not the Same Problem
Companies sometimes spend significant time trying to make every schedule agree perfectly to the cent while larger unexplained differences remain elsewhere. Audit preparation should focus on accuracy, but management should also understand that the significance of differences depends on context. Auditors consider materiality when planning and evaluating audit work, although qualitative considerations can also matter. The practical lesson for finance teams is not to ignore small errors, but to prioritise meaningful discrepancies and ensure significant balances can be supported clearly.
Internal Controls Can Affect the Audit Approach
Auditors may ask questions about who prepares transactions, who approves them, who can access banking systems and how reconciliations are reviewed. Management sometimes wonders why these questions are necessary when the company has already provided the financial records. Understanding relevant internal controls helps auditors assess how financial information is produced and where risks of material misstatement may arise. If one employee can create suppliers, change bank details, prepare payments and approve those payments without independent review, that process may present different risks from a process with appropriate segregation and oversight.
Small Companies May Not Have Perfect Segregation of Duties
A small SME may not have enough finance employees to separate every responsibility among different people. One employee might handle bookkeeping, bank reconciliations and supplier records because hiring five people solely to create ideal segregation would be unrealistic. Auditors understand that smaller organisations can operate differently from large corporations. Management can still implement compensating controls, such as director review of bank payments, periodic review of reconciliations or restrictions on sensitive system changes. The objective is to design controls appropriate to the size and circumstances of the business rather than copying a multinational corporation’s finance department.
Journal Entries Can Generate Additional Questions
Manual journal entries may receive audit attention because they can directly change accounting balances without following the same transaction flow as ordinary sales or purchases. A year-end journal for S$500,000 with a description such as “adjustment” naturally provides limited information. The auditor may ask who prepared it, why it was necessary, who approved it and what evidence supports the amount. Finance teams can reduce unnecessary follow-up by maintaining clear descriptions and supporting documentation when significant adjustments are recorded. Six months later, even the employee who prepared the journal may struggle to remember what “adjustment” meant.
Accounting Estimates Cannot Always Be Supported by a Single Invoice
Some financial statement amounts are estimates rather than direct totals from invoices. Examples can include impairment assessments, provisions, depreciation-related estimates and certain fair-value measurements depending on the business. These balances often require management assumptions and judgement. An auditor may therefore request calculations, historical information, management explanations or external information rather than a conventional invoice. The fact that several documents are required does not mean the estimate is automatically problematic. Estimates are inherently different from simple cash transactions and may require broader evidence.
Group Companies Can Create Even More Documentation
Audit complexity can increase when a Singapore company belongs to a larger corporate group. Intercompany transactions need to be understood, balances may need to be reconciled between entities and reporting packages may need to satisfy group requirements. A Singapore subsidiary may also receive instructions connected to its parent company’s group audit. Kazuma’s audit services include statutory financial statement audits as well as support for group audits, head-office reporting and consolidation packages, making these situations particularly relevant for businesses operating within international groups. Kazuma Public Accounting Corporation
Head Office May Need Information Before the Singapore Deadline
A Singapore subsidiary of an overseas group can face two different timelines. Local statutory requirements may provide one deadline, while the parent company’s consolidation timetable requires financial information much earlier. The group auditor may request specific procedures or reporting information from the Singapore audit team. This can make the process feel more demanding because management is not only preparing information for local purposes. Companies operating within international groups should therefore coordinate reporting calendars early so that finance teams understand both local and group requirements.
Waiting Until the Audit Starts Usually Creates More Work
The easiest time to prepare audit evidence is often when the transaction occurs. A contract signed in March is easier to locate in March than the following February. An unusual payment is easier to explain while everyone remembers why it happened. If businesses wait until the annual audit to organise an entire year’s documentation, finance employees may spend days searching old emails and asking colleagues what transactions were for. Maintaining organised supporting records throughout the year can therefore reduce the pressure associated with audit season.
Ask the Auditor What Will Be Needed Before Year-End
Businesses do not always need to wait for the first audit request list before preparing. For recurring audits, many information requirements are predictable from year to year, although the exact procedures can change based on circumstances and risk. Finance teams can review previous requests, organise major contracts, reconcile key balances and identify unusual transactions before fieldwork begins. Communication with the auditor can also help management understand the expected timetable and major information requirements. Early preparation does not eliminate every follow-up question, but it can reduce avoidable delays.
One Person Should Coordinate Audit Requests
When several employees respond independently to auditors, information can become duplicated or inconsistent. Finance sends one version of a schedule, operations sends another and management provides a third explanation. A central audit coordinator can help track requests, assign responsibilities and confirm that responses are complete before submission. This does not mean one employee must personally prepare everything. The coordinator simply provides structure so everyone knows which requests remain outstanding and which documents have already been sent.
A Request Tracker Can Save Everyone Time
For larger audits, a simple request tracker can be extremely useful. Each request can have an owner, due date, status and reference to the documents provided. If the auditor asks a follow-up question, it can be linked to the original request. This prevents employees from searching through long email chains trying to remember whether something was already submitted. Good organisation can make the audit feel considerably less disruptive even when the underlying amount of audit work remains unchanged.
Responding Quickly Is Helpful, but Responding Clearly Is Better
Finance teams sometimes rush to respond because they want to avoid being blamed for audit delays. Speed is useful, but incomplete responses can create additional rounds of questions. If the auditor requests an invoice and proof of payment, sending only the invoice within five minutes may be less efficient than sending both documents an hour later. Businesses should read requests carefully and ensure responses address what is actually being asked. When a request is unclear, asking for clarification can be more productive than guessing.
Audit Delays Are Often a Shared Problem
When an audit takes longer than expected, it is tempting for each side to blame the other. Management says the auditor keeps asking questions. The auditor says the client has outstanding documents. In reality, delays can arise from both sides and from the complexity of the underlying issues. A productive audit relationship focuses on resolving outstanding matters rather than assigning blame. Clear communication, realistic deadlines and organised documentation can make a significant difference, particularly during busy reporting periods.
More Questions Do Not Necessarily Mean Your Accounts Are Bad
This point is worth emphasising because audit requests can make management nervous. Receiving 50 questions does not mean the auditor has found 50 errors. Many questions are simply requests for evidence or explanations necessary to complete planned audit procedures. A complex business may naturally generate more questions than a simple business even when both maintain good accounting records. Conversely, receiving few questions does not automatically prove that a company’s accounting is perfect. The quantity of correspondence should not be interpreted as an informal audit score.
But Repeated Questions About the Same Area Can Reveal a Process Problem
Although follow-up questions are normal, patterns can still be useful. If auditors repeatedly struggle to obtain support for fixed assets every year, perhaps the fixed asset register needs improvement. If customer balances are constantly difficult to reconcile, the receivables process may need attention. If contracts cannot be located, document management may be weak. Management can use recurring audit difficulties as an opportunity to improve internal processes. The objective should not merely be to survive this year’s audit but to make next year’s financial administration stronger.
The Audit Request List Can Be a Mirror of Your Finance Function
A well-organised finance function often produces evidence relatively easily because transactions have clear supporting documents, balances are reconciled and responsibilities are understood. A disorganised finance function may spend weeks reconstructing information that should already exist. In that sense, audit preparation can reveal how accessible and understandable the company’s financial records really are. If management cannot explain a major transaction six months after it occurred, that is potentially a management-information problem even before considering the audit.
Good Audit Preparation Benefits the Business After the Auditor Leaves
The improvements made for audit purposes can create benefits throughout the year. Better document organisation helps employees answer supplier and customer questions. Cleaner reconciliations improve management reporting. Stronger approval processes reduce financial risk. Better fixed asset records support insurance and budgeting. Clear contracts help management understand commercial obligations. Businesses therefore should not view audit preparation purely as work performed for an external auditor. Many of the practices that make audits easier also make financial management more reliable.
The Goal Is Not to Eliminate Every Audit Question
Even a company with excellent records should expect questions during an audit. If auditors could complete the engagement without understanding transactions, examining evidence or communicating with management, the process would provide little value as an independent examination. The realistic objective is therefore not “zero questions.” It is to ensure questions can be answered efficiently because information is available, organised and understandable. A smooth audit can still involve many requests. The difference is that those requests do not turn into weeks of searching, confusion and repeated corrections.
Conclusion: The Second Request Does Not Mean the First Document Failed
You send the auditor an invoice.
The auditor asks for the contract.
You send the contract.
The auditor asks for proof of delivery.
You send the delivery document.
Then another question arrives.
It can feel as though the process will never end.
But each piece of evidence can answer a different question.
The invoice may show what was billed.
The contract may explain what the parties agreed.
The delivery document may show when goods arrived.
The bank statement may show when payment occurred.
A customer confirmation may provide independent evidence of a balance.
A reconciliation may explain how detailed transactions connect to the financial statements.
Management explanations may provide context that documents alone cannot show.
Professional audit services Singapore are therefore not based on simply collecting a large folder of paperwork and checking whether the numbers match. The auditor needs sufficient appropriate evidence to support the conclusions reached during the audit. Depending on the transaction, one document may be enough for a particular purpose. In other situations, several pieces of information may be necessary.
Businesses can make the process significantly easier by maintaining organised records throughout the year, preparing reconciliations before fieldwork, clearly labelling supporting documents, keeping important contracts accessible and responding to audit requests with the information actually requested. Significant or unusual transactions should be documented when they happen rather than reconstructed months later.
Most importantly, businesses should not automatically interpret every follow-up request as a sign that the auditor has discovered a problem.
Sometimes the first document was perfectly useful.
It simply answered the first question.
The second document answers the next one.
At Kazuma Public Accounting Corporation, businesses can obtain professional audit and assurance support, including statutory financial statement audits and services relating to group and head-office reporting requirements. Preparing reliable financial records and supporting documentation before the audit begins can help make the process more organised for both management and the audit team.
So when your auditor sends another email asking:
“Could you please provide the supporting documents for the following items?”
Do not immediately assume they ignored the folder you sent yesterday.
The better question is:
“What is the auditor trying to establish that the first document could not show?”
Once businesses understand that distinction, many audit requests begin to make considerably more sense.