Understand the system’s role
MyInvois provides a way to submit documents to HASiL and obtain processing results. Its SDK describes APIs that business systems can use to connect their document workflows.
A software project should distinguish generating invoices in the source system, submitting the required data and recording the result. Keeping those steps separate helps your team identify where a problem occurred.
Prepare your source data
- Review customer and supplier identifiers and required contact details.
- Check line descriptions, amounts and the document types your business actually uses.
- Identify where records originate and who is responsible for correcting them.
- Use representative samples to identify missing or inconsistent information early.
Design submission and follow-up together
The official API documentation covers document submission and related document operations. Plan how your application tracks processing states, shows validation feedback and links returned references to the original business record.
Retries need care: a network problem does not always mean that a submission failed. Agree how the application checks results and avoids unintended duplicate processing.
Test before operational rollout
Use the appropriate test environment and sample transactions to verify data mapping, authentication and the full workflow. Include unsuccessful submissions and the actions a staff member should take next.
Review the current SDK integration notes and changes before implementation, and confirm that any example still applies.
Confirm current official requirements
This guide addresses software planning. Implementation dates, exemptions and tax treatment depend on the current HASiL guidance and your business circumstances. Use the official guidance page and your finance or tax adviser to confirm those obligations.