This guide is designed for practical implementation planning. Adapt each step to the legal entity, source system, transaction profile and current LHDN guidance.
Implementation checklist
- 1
Identify when a TIN is required
Record the owner, evidence, unresolved exceptions and completion date before moving forward.
- 2
Collect the identifier through controlled channels
Record the owner, evidence, unresolved exceptions and completion date before moving forward.
- 3
Validate format and ownership where supported
Record the owner, evidence, unresolved exceptions and completion date before moving forward.
- 4
Avoid overwriting verified data with unreviewed input
Record the owner, evidence, unresolved exceptions and completion date before moving forward.
- 5
Store validation status and date
Record the owner, evidence, unresolved exceptions and completion date before moving forward.
- 6
Route conflicts to a responsible user
Record the owner, evidence, unresolved exceptions and completion date before moving forward.
How to use this guide
Do not treat a checked box as proof of production readiness. Review real transaction samples, confirm user ownership and retain evidence from testing. Revisit the checklist when a source system, legal entity or official validation rule changes.
Official references
Use the latest HASiL e-Invoice Guideline, Specific Guideline, FAQs and MyInvois SDK for authoritative rules and technical requirements.