Tax codes, SST and what LHDN actually sees

For the whole-system operator — you run the books. Level 3 — configure and own.

By the end you can say where the tax type on a submitted e-invoice line comes from — recomputed from the line’s tax amount, not read from the item — trace any invoice line’s rate back to the one record of four that gave it, name the single tick that decides whether an item’s tax codes apply at all and which document types honour it, recognise the six seeded rows in Tax Configuration that look like the answer and are read by nothing, and prove a tax setup from the submitted record rather than from the screens you configured it on.

Before this series: Get your items ready for e-invoice

Presentations

1. The taxable type LHDN receives is arithmetic — about 13 minutes, narrated
2. One tax rate, four copies, and the one that charged — about 14 minutes, narrated
3. Tax Applicable is the switch, and most items have it off — about 13 minutes, narrated
4. Six rows in Tax Configuration that are not tax codes — about 13 minutes, narrated
5. Proving a tax setup from the only place that can prove it — about 14 minutes, narrated

Modules this series draws on

• E-Invoice & PEPPOL Module
• Financial Accounting Module
• Core Module

Reference pages this series draws on

Every screen a presentation mentions is documented on one of these pages; the series does not re-document it.

• My E-Invoice Admin Applet
• Doc Item Maintenance
• Tax Configuration
• E-Invoice Validation Rules & Troubleshooting
• E-Invoice Submission Mechanics

All presentations · Presentations for the whole-system operator