Taman Tasek Baru · Ipoh · Perak
We examine the financial truth inside invoice processing applications.
Not a software tour. A sampled look at how supplier invoices are captured, matched, coded, approved, and posted — then a letter your finance lead can act on.
Begin with a scoping conversation
Primary engagement
Invoice application financial audit
Companies in Perak and across Peninsular Malaysia ask us to look at the application that now sits between a supplier bill and the ledger. You receive fieldwork, a findings letter, and a close meeting. You do not receive a product, a dashboard, or an implementation plan.
- Written findings
- Exceptions with evidence references, written for finance leadership.
- Sampling worksheets
- The population, the plan, and the invoices actually opened.
- Control exception log
- Override paths, matching skips, tax-code defaults, duplicate leaks.
- Close meeting
- In Ipoh or at your premises, including what we would re-test later.
Also requested
Related examinations
Each of these can stand alone or follow the primary audit. Fees are quoted in Malaysian ringgit after intake. Nothing is purchased online.
-
Three-way matching and approval-path review
Purchase order, goods receipt, and invoice alignment — plus the override buttons, parked invoices, and substitute approvers that policy never quite describes.
-
SST and withholding treatment in the application
Whether sales tax, service tax, exempt supplies, and withholding are applied inside the invoice flow the same way finance explains them at month-end.
-
Duplicate, split, and round-trip payment testing
Sampling for duplicate invoices, split approvals that dodge thresholds, and payments that leave the company and return under another reference.
-
Pre-go-live financial readiness
A control and cutover review before a new invoice application is relied on for the ledger — master data, opening invoices, and the week when two systems both look true.
-
Follow-up examination
Re-testing previously raised exceptions after management says they are closed — same samples where possible, same evidence standard.
From finance teams we have sat with
What they asked us to look at
They sat with our AP clerks for a morning in Ipoh and then sampled the invoices that never appear in a vendor demo. The findings letter was specific enough to act on.
We were about to cut over. They made us name which system was allowed to pay during the overlap week. That single question prevented a dual payment run.
The SST coding review did not try to replace our tax agent. It showed where the application’s defaults disagreed with the return workbook.
See how an examination proceeds
Six steps from conflict check to findings letter, including what we will not do.