A director submits a hotel bill and asks the company to reimburse it. The bill identifies the supplier, date and amount. It may say little about the trip's business purpose, who paid, whether any part was personal, or who approved the claim. Those questions matter to the finance team preparing the record and to any accountant, tax agent or auditor who later reviews it.
There is no universal packet of documents that makes every director's claim acceptable. Start with the transaction and the decision someone needs to make. Keep the original document, the director's explanation, any follow-up and the review outcome connected, while showing what remains unresolved.
Start with the director's role and the transaction
Before applying a rule about employee expense claims, establish the director's actual capacity in this transaction. Is the person also an employee under a contract of service? Was the purchase made on the company's behalf? Was the company the buyer, or did it later decide to reimburse a personal purchase? Who paid the supplier, and who received the reimbursement?
The word director on a claim form does not answer those questions. Nor does a receipt in the director's name automatically settle the company's accounting, e-Invoice or tax treatment. The supporting record should allow the appropriate professional to assess the facts rather than force a conclusion from a label.
A practical supporting-record checklist
The following is GetZenta's recommended practice, adapted to the engagement, not an LHDN-prescribed list for all director claims. Which items matter depends on the expense and the review question.
| Question for the reviewer | Records that may help | Keep visible if unresolved |
|---|---|---|
| What was bought, when and from whom? | Original receipt, invoice or e-Invoice; itemisation; transaction reference | Missing items, unclear supplier or inconsistent dates |
| Who paid and what was reimbursed? | Payment record, claim form, reimbursement entry and amount reconciliation | Differences between the purchase and the amount claimed |
| Why was it for the business? | Specific purpose, project or client context; itinerary, meeting record or other contemporaneous explanation | A generic description such as “business trip” without a clear link |
| Who authorised the expense? | Applicable company policy, approval request and an attributed approval or review record | Approval by the claimant alone, missing authority or later changes |
| Was any part personal or mixed use? | Itemised charges, trip dates, accompanying persons and a proposed allocation with its basis | Personal days, family expenses or an allocation that cannot be explained |
| Are there director-related considerations? | Nature of the relationship, company policy and any relevant approval or disclosure context | Matters an accountant, tax agent or auditor needs to assess separately |
| What did the reviewer decide? | Clarification request, director's response, reviewer identity, reasoning and open questions | A “cleared” status without the supporting rationale |
An itinerary can help connect travel dates to a meeting. It does not, on its own, prove every charge was business related. A payment record can show money moved; it does not establish the purpose of the purchase. Keep those limits next to the records rather than silently turning them into approval.
Fictional example: one hotel claim, several questions
A director claims RM1,860 for a trip described as “client meetings.” The hotel invoice and card statement agree on the total. An itinerary indicates two meeting days, but the invoice also includes an extra night after the meetings. The claim does not explain whether that night was for business or personal reasons.
The finance preparer can preserve the original invoice and payment evidence, ask for the meeting context and reason for the extra night, and record the director's response. A reviewer can then assess the stated purpose, any allocation and the applicable policy. If the additional night remains unexplained, the question stays open. Matching totals and a meeting entry do not by themselves establish the treatment of the whole claim.
For the auditor-facing version of a director travel example, see From Fragmented Evidence to Review-Ready Working Papers. That article addresses the later evidence-to-working-paper handoff; this guide addresses the records to collect and questions to resolve when preparing the claim.
Where does LHDN's e-Invoice guidance fit?
Section 7 of LHDN's e-Invoice Specific Guideline, version 4.9, published 7 September 2026, addresses certain expenses incurred by an individual under a contract of service (employment) on behalf of the employer. It describes supporting documents for employee claims, seeking an e-Invoice in the employer's name where possible, and a concession for certain transactions supported by an e-Invoice in the employee's name or existing documentation. The exception depends on the employer being able to show that the employee acted on its behalf. Check the full current Section 7 and the actual relationship before applying it to a director's claim.
The same guideline's Section 5 addresses supplier and intermediary disbursement or reimbursement arrangements. Its examples serve a different transaction pattern; the word “reimbursement” alone does not make those examples the rule for a director's company expense claim.
An e-Invoice or MyInvois validation status is one part of the record. Whether the evidence answers a reviewer's question and whether the expense receives a particular tax treatment are separate assessments. Read MyInvois Validation, Audit Evidence, and Tax Deductibility: Three Different Questions for that distinction. This article does not decide deductibility, accounting classification or audit evidence sufficiency for a particular claim.
Make the handoff understandable to someone new to the file
A useful claim record shows the source, what the claimant said, what the preparer checked, what the reviewer asked, and who made any decision. Preserve the original material separately from later explanations and human decisions. If a purpose, amount or allocation is corrected, retain what changed and why.
This follows the same idea as the documentation test in ISA 230, paragraph 8: documentation should let an experienced auditor with no prior connection to the engagement understand the procedures performed, the results and evidence obtained, and the significant matters and judgments reached. That requirement is broader than preserving receipt records; a claim file is one part of it.
That is the practical application of GetZenta's Review-First Principle: weak, incomplete or conflicting evidence is routed to professional review, not auto-approved. GetZenta's receipt-evidence approach is designed to connect source material, exceptions and attributed review decisions. It does not approve a director's claim automatically, determine tax deductibility or replace professional judgement.
For a general handoff checklist covering any SME transaction, read From Receipt to Reviewer: What Should Travel With an SME Transaction?
Continue reading
- From Fragmented Evidence to Review-Ready Working Papers — the auditor-facing director travel example, from evidence to working-paper handoff.
- MyInvois Validation, Audit Evidence, and Tax Deductibility: Three Different Questions — why validation, evidence and tax treatment are separate assessments.
- From Receipt to Reviewer: What Should Travel With an SME Transaction? — a general handoff checklist for any SME transaction.
- Audit Evidence for Malaysian Receipt Workflows: Why OCR Alone Is Not Enough — the normative home of GetZenta's Review-First Principle.
- Audit Evidence — GetZenta's evidence model for audit practices.
- Auditor Workflow — how audit firms hand evidence to a reviewer.
Discuss the workflow
If your SME, finance team, accountant or tax agent repeatedly has to reconstruct the purpose and approval of expense claims, contact GetZenta about your receipt-evidence workflow. Describe the process and the questions that get lost; do not send client receipts or personal data in an initial enquiry.
Discuss your firm’s evidence handoff
GetZenta is preparing selected-auditor Alpha workflow validation with Malaysian audit firms. Initial discussions can use synthetic or appropriately redacted examples. Participation, scope and any use of client records require separate agreement.
Discuss Alpha suitability →