Briefings

Notes from examinations, not product news.

Short pieces on what we actually see inside invoice processing applications used by Malaysian finance teams.

Person at a desk reviewing documents on a laptop

An invoice export is not an audit trail

A spreadsheet dump from the invoice application can be sorted, filtered, and still fail to show who approved what, and when the record changed.

Colleagues discussing papers in a bright meeting room

Override buttons that quietly break three-way matching

A matching rule can be strict in the policy manual and optional in the application. The difference usually lives on a small button with a large effect.

Close-up of printed financial figures and a pen

SST codes that survive the demo and fail at month-end

Tax codes in an invoice application are only as good as the defaults that fire when a clerk is busy. Month-end spreadsheets often hide the gap.

Organised folders and documents on an office shelf

Sampling supplier invoices in a Malaysian mid-market AP team

A useful sample is not a random handful of PDFs. It is a plan that covers vendors, amounts, tax treatments, and the messy invoices nobody puts in a demo.

Notebook, laptop, and coffee on a desk during writing work

What a findings letter from this kind of engagement contains

Our letter is written for people who have to decide whether to keep relying on the application. It is not a dashboard and it is not a vendor scorecard.

Quiet office interior with desks and large windows

Cutover week: invoices in two systems at once

The dangerous week is not go-live Monday. It is the stretch when the old application, the new one, and a spreadsheet can all look like the truth.