My shop is still in sandbox
Every shop has a filing destination. If your documents are not appearing in MyInvois, your shop is probably still sending them somewhere else.
The three destinations
| Destination | Where documents go | Official e-invoices? |
|---|---|---|
| Internal test mock | Nowhere. envoice simulates LHDN so you can try the flow. | No |
| LHDN test system (preprod) | LHDN's test MyInvois system. | No |
| LHDN production | The real MyInvois system. | Yes |
New shops start on the internal test mock. New accounts also get a demo shop with example details, which always stays on the test system.
Check where your shop files
- Open Settings, then the Sandbox tab.
- Current filing destination shows where documents go now.
Switch to LHDN production
You need three things before envoice lets you leave the test mock.
- Verified production credentials. Open the LHDN tab, choose LHDN production system, paste your Client ID and Client Secret, and click Save and verify. Saving credentials only verifies them. It does not start filing on its own.
- Your real business identity. Open the Profile tab and replace any example details with your real TIN, BRN and MSIC code. envoice will not file to LHDN with placeholder details.
- Your confirmation. Back on the Sandbox tab, under Where should documents go?, choose LHDN production, tick "I understand future submissions will go to LHDN production as real e-invoices", and click Save destination.
If something is missing, envoice tells you which step:
- "Add and verify your LHDN credentials (preprod or production) before turning sandbox off."
- "Complete your real business identity in Profile before sending documents to LHDN."
- "Confirm the LHDN destination before switching off the internal test mock."
What about documents made in sandbox?
Documents made on the internal test mock or the LHDN test system were never filed as real e-invoices. If any of them were real sales, create them again after you switch to production. Documents sent to the internal mock still count toward your plan usage.