E-invoicing for the shop you run
For the branch operator — you run one shop end to end. Level 1 — orientation.
By the end you can say what one receipt at your counter sets off, why a sale of yours went into the monthly batch instead of to LHDN on its own, whether your branch is a block on the finished e-invoice or invisible inside one, which of your sales LHDN will never hear about at all, and what only your branch can still put right before the month closes.
Presentations
- What one receipt at your counter sets off — about 9 minutes, narrated
- Why that sale went into the monthly batch — about 10 minutes, narrated
- Is your branch a block on the e-invoice, or invisible inside one? — about 10 minutes, narrated
- The sales LHDN never hears about from your branch — about 10 minutes, narrated
- Close your branch’s month before the 1st — about 10 minutes, narrated
Modules this series draws on
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
- MY E-Invoice Portal Applet
- Organization
- POS General
- What am I supposed to do between the 1st and the 7th? The month-end e-invoice cycle
- E-Invoice Pools: Consolidating by Document or by Branch
- E-Invoice Pools: The Monthly Consolidation Cycle and Backdated Documents
- E-Invoice Pools: Submission Types, the RM 10,000 Rule and Where a Finalised Document Goes
- E-Invoice Pools: What You Can Do in Each Pool, and the Questions That Come Up Most
- E-Invoice Validation: What BigLedger and LHDN Check — the Buyer’s Identity, the Mandatory Fields and the General TINs
- Consolidated e-invoices
- Pools and queues
- E-Invoice Submission Mechanics
- Core Concepts