Get your customers ready for e-invoice

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

By the end you can say which GadgetSphere customer records LHDN will ever see and which never reach it, key the buyer identity that each kind of customer needs so the sale passes first time, flag the one address BigLedger actually sends, turn on the settings that stop a clerk saving a broken record, correct a whole book of customers in one upload instead of one at a time, and hand the job to your customers through the portal so the details arrive instead of being chased.

Before this series: Run the month-end e-invoice cycle

Presentations

1. Which customer records ever reach LHDN — about 14 minutes, narrated
2. The identity each kind of customer needs — about 13 minutes, narrated
3. The address BigLedger actually sends — about 11 minutes, narrated
4. Make a broken record impossible to save — about 12 minutes, narrated
5. Fix a whole book of customers at once — about 16 minutes, narrated
6. Let your customers key their own details — about 12 minutes, narrated

Modules this series draws on

• E-Invoice & PEPPOL 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
• MY E-Invoice Portal Applet
• Customer Maintenance
• Organization
• E-Invoice Pools & Submission Routing
• E-Invoice Validation Rules & Troubleshooting
• Best Practices
• Consolidated e-invoices
• Pools and queues
• Configuration

All presentations · Presentations for the whole-system operator