Building a claim population export that auditors can use
A usable export needs claim IDs, timestamps, approver names, and receipt links — not a flat total by cost centre.
Before any reimbursement sample testing begins, someone has to extract the population. The quality of that file decides how long testing takes.
Minimum fields
Ask your systems team for one row per claim line with: unique claim ID, employee ID, cost centre, category, transaction date, submission date, approval date, approver name, merchant, amount in original currency, HKD amount, and a link or filename for the receipt image.
Totals by department are useless for compliance checks. So are screenshots.
Common export traps
- Approval date missing when the workflow sits outside the claim tool
- Multi-currency amounts without a rate date
- Soft-deleted claims still in the table without a status flag
- Receipt images stored in a separate drive with no join key
What we do with a clean file
For reimbursement sample testing we can draw the sample the same day the file arrives. For a full compliance audit we still spend time agreeing category mapping — “entertainment” in one entity may be “client development” in another.
Invest an afternoon in the extract before you commission external testing. It usually pays for itself in fewer query rounds.