E-Invoice & PEPPOL Guides

Set up and manage your electronic invoicing — from MyInvois registration and PEPPOL configuration to daily e-invoice operations, validation troubleshooting, and Malaysia regulatory compliance.

🚀 Get Started / Setup

New to e-invoicing? Start with these essential configuration guides.

🇲🇾 MyInvois Setup

🌐 PEPPOL Configuration

Set up PEPPOL network for cross-border electronic document exchange

What you’ll set up:

MyInvois API credentials and company registration
Digital certificate configuration
PEPPOL participant ID and access point
Tax identification number (TIN) mapping
E-invoice document type mappings (Invoice, Credit Note, Debit Note)

First time? Complete MyInvois setup first — it’s required for Malaysia compliance. PEPPOL is optional and only needed for cross-border B2B transactions.

📝 Daily Tasks

Once configured, e-invoicing integrates into your normal sales and purchasing workflows:

Typical daily workflow:

Create sales invoices / credit notes as usual
System auto-submits to MyInvois (or manually submit in batch)
Monitor submission status — Accepted ✅ / Rejected ❌
Handle rejected invoices — fix validation errors and resubmit
Receive inbound e-invoices from suppliers via PEPPOL

Seamless Integration: Once set up, e-invoicing runs in the background. Your team creates invoices normally, and the system handles submission automatically.

⚠️ Common Scenarios / Pitfalls

✅ E-Invoice Validation Rules

Understand validation requirements and fix common rejection errors

Watch out for these frequent e-invoice issues:

Scenario	What Happens	How to Handle
TIN mismatch	Buyer/supplier TIN doesn’t match LHDN records	Verify TIN with customer/supplier, update master data
Invalid tax code	Tax rate not recognized by MyInvois	Use only LHDN-approved tax codes (6%, 8%, Exempt, etc.)
Missing mandatory fields	Submission rejected by validation	Check required fields: TIN, BRN, address, line item details
API timeout	Submission hangs or fails silently	Check internet connectivity, retry after a few minutes
Duplicate submission	Same invoice submitted twice	System prevents duplicates; check submission history
Cross-border format	PEPPOL document format mismatch	Verify document format matches recipient’s PEPPOL requirements

Malaysia Deadline: E-invoicing is mandatory for businesses above the revenue threshold. Ensure your setup is complete before the enforcement date to avoid penalties.

📊 Reporting Usage

Monitor your e-invoice compliance and submission health.

🇲🇾 Malaysia E-Invoice Compliance

Complete guide to Malaysia’s e-invoicing requirements, timelines, and best practices

Key E-Invoice Reports:

Submission Status Report — Track Accepted, Rejected, and Pending submissions
Validation Error Report — Common errors and rejection reasons
Compliance Dashboard — Percentage of compliant transactions
PEPPOL Transaction Log — Inbound/outbound PEPPOL document history

Compliance tips:

Monitor rejection rates daily during initial rollout
Keep TIN and BRN data up to date for all customers/suppliers
Archive all e-invoice acknowledgements for audit purposes
Test with sandbox environment before going live

Related Resources

My E-Invoice Admin Applet — E-invoice administration reference
Sales Invoice Applet — Sales invoice documentation
Purchase Invoice Applet — Purchase invoice documentation
Compliance & Audit Guide — Regulatory compliance overview