Summary: Could your team prove who approved every invoice if an auditor asked today? This blog explores why explanations alone don’t satisfy auditors, what PCAOB and AICPA standards expect as evidence, and 6 questions controllers and CFOs should answer before audit season, from approval authority and separation of duties to exceptions, unrecorded liabilities, and changes to automated approval rules. Learn how to test your own evidence this month, before audit requests start arriving.
An auditor selects an invoice and asks a straightforward question: Who approved this?
Your team recognizes the vendor. The amount looks reasonable. Someone remembers the department head signing off. But the approval is buried in an email thread, the supporting documentation sits on a shared drive, and nobody can immediately establish whether the approver had the right authority.
The transaction may be legitimate. But demonstrating that the right controls operated is another matter.
For controllers and CFOs preparing for calendar-year closings, November is a valuable opportunity to examine that distinction. Once year-end demands intensify, investigating missing approvals and reconstructing transaction histories becomes harder.
In accounts payable (AP), the gap between confidence and evidence can surface in a familiar way. Everyone expects an invoice to have gone through the right approval steps, but the records are too scattered to show that it did.
Knowing how a process should work does not establish that it worked consistently throughout the year.
The Public Company Accounting Oversight Board’s (PCAOB) AS 1105, which governs audit evidence in PCAOB audits, makes this distinction explicit: inquiries of company personnel alone do not provide sufficient evidence to support a conclusion about a control’s effectiveness. U.S. private-company audits conducted under the American Institute of Certified Public Accountants’ (AICPA) standards follow the same principle. When auditors test whether a control operated effectively, AICPA AU-C Section 330 requires them to combine inquiry with other audit procedures. For finance leaders, the practical lesson is clear: an explanation needs supporting evidence.
The consequences of weak controls extend beyond difficult audit conversations. The Association of Certified Fraud Examiners’ Occupational Fraud 2026: A Report to the Nations examined 2,402 investigated fraud cases across 143 countries and territories. In more than half, the primary weakness was a lack of internal controls (33%) or an override of existing ones (19%). Before audit requests begin arriving, finance leaders should answer six questions.
A record showing that an invoice was approved is a starting point. Your team should also be able to identify the approver, when approval occurred, and whether that person had authority for the amount, entity, and expense involved.
Consider a manager approving an invoice above their spending limit. The presence of an approval does not resolve the control issue. Review approval thresholds, delegation rules, and backup arrangements. Confirm that workflow settings reflect current policy, including changes resulting from reorganizations or employee departures. Then inspect actual transactions. Can your team demonstrate that the required approval occurred before payment?
A segregation-of-duties policy offers limited protection if system permissions allow one person to perform conflicting activities.
Examine who can create vendors, change payment details, enter invoices, approve spending, and release payments. Pay particular attention to administrator accounts, temporary access, and employees who have accumulated permissions as their responsibilities change.
Ask whether someone could change a vendor’s bank account and then initiate and release a payment without independent review. Smaller teams may need compensating controls when complete separation is impractical. Those reviews should have a defined owner, occur consistently, and leave evidence of what was examined and how concerns were resolved.
Review permissions with IT now, while there is time to address unnecessary access.
Urgent payments, missing purchase orders, and absent approvers test whether controls remain effective under pressure.
A process can appear disciplined during routine transactions while allowing exceptions to move through email, messaging apps, or verbal instructions. Select several recent exceptions. Can your team show why each departure from standard procedure was necessary, who authorized it, and what additional review occurred? Establish a documented route for exceptions, with clear approval requirements and retained supporting information. Review patterns, too. Repeated urgent requests from the same department may indicate a process problem.
An exception should remain visible after the payment clears.
An invoice image alone does not explain the full decision.
Depending on the transaction, supporting evidence may include a purchase order, receiving documentation, coding changes, approval records, exception notes, and payment information.
Test whether those records remain connected and accessible when the person who processed the invoice is unavailable. Check whether edits and approvals have identifiable users and timestamps, and whether access and retention settings protect the records. Both PCAOB AS 1105 and AICPA AU-C Section 500 address whether information used as audit evidence has enough detail for the auditor’s purpose and how its accuracy and completeness are supported.
Audit preparation also requires looking beyond invoices already posted or paid.
Invoices waiting in inboxes, unresolved receiving discrepancies, and approvals stalled over the holidays can complicate the assessment of year-end liabilities. Review open invoices and unmatched receipts with procurement and department leaders. Establish ownership for investigating outstanding items and assessing whether accruals are needed under your accounting policies. Make sure your team can explain how it identifies invoices received outside the central AP process.
A clean payment queue offers little reassurance if obligations remain invisible elsewhere.
Pull the change log for your approval workflows. Pick a change made this year, such as an increased spending limit or a new backup approver. Can you identify who made the change, who authorized it, and when it took effect? Then trace an invoice processed after that date to see whether it followed the updated rule.
If your system uses AI to suggest invoice coding, follow a similar approach. Pick an invoice that someone flagged or corrected. Check whether you can see what the system suggested, who reviewed it, and what ultimately posted. That record gives your team something concrete to point to when an auditor asks how exceptions were handled.
A November 2026 BDO survey illustrates how easily finance practices can outpace the evidence behind them. Nearly all finance leaders surveyed (99%) said their organization used AI to generate or inform at least one financial estimate or judgment reviewed by its external auditor. Yet only 49% said they had the documentation and processes to substantiate every AI-assisted output.
This month, select a small group of transactions spanning routine invoices, significant purchases, exceptions, and payments involving changed vendor details. This internal exercise will not replace audit testing, but it can reveal practical gaps.
Ask someone outside the original processing chain to reconstruct each transaction using the retained records. Document missing evidence, assign owners, and address the underlying process.
onPhase helps AP teams build that evidence as invoices move through the process. Configurable workflows route invoices to the right approvers, role-based access limits who can take action, and timestamped audit trails show who did what and when.
Your auditors will ask who approved that invoice. Prepare now to show them.
Explore how onPhase can help strengthen control and visibility across your financial processes.