Cloud ERP in Singapore and Malaysia: InvoiceNow, MyInvois, GST, SST and Go-Live Costs
Singapore sends invoice data over Peppol; Malaysia requires the tax authority to validate each e-invoice. What that means for one ERP across both countries: vendor shortlists, partners, deadlines and realistic go-live budgets.
One ERP, Two E-Invoicing Models: The Decision Groups Face
If your group runs a Singapore entity and a Malaysian entity, your ERP has to meet two e-invoicing regimes that look alike on a slide but work very differently. Singapore's InvoiceNow is a Peppol-based exchange network, and IRAS receives GST invoice data through it. Malaysia's MyInvois is a clearance-style system: the Inland Revenue Board of Malaysia (LHDN) validates each e-invoice before it counts as valid. A cloud ERP Singapore rollout that handles InvoiceNow well can still fall short in Malaysia, and the reverse happens too.
The practical question is whether one platform plus one partner can cover both entities, or whether you'll end up with a separate connector, separate tax logic and a separate support contract for each country. For most mid-sized groups, one ERP with certified connectors in each market is the better fit. Consolidation, intercompany billing and transfer-pricing documentation get much simpler on a single ledger. The catch: check each country's connector on its own merits. Don't take one vendor's word for both.
How InvoiceNow Works and Who Must Comply in Singapore
InvoiceNow runs on the Peppol network, and IMDA is Singapore's Peppol Authority. Your ERP sends a structured invoice in the Singapore PINT format to an accredited Access Point. That Access Point delivers it to the buyer's Access Point and, under the GST InvoiceNow Requirement, sends a copy of the invoice data to IRAS. IRAS doesn't approve each invoice before it reaches the buyer. The network carries the invoice and IRAS receives a copy; it isn't a gatekeeper.
The requirement is being phased in through GST registration, starting with newly registered voluntary registrants and extending to other GST-registered businesses in later phases. Any business can adopt it voluntarily before its date. Check the current IRAS timeline before you sign a contract, because those dates decide how urgent your Singapore work really is.
For an InvoiceNow ERP setup, ask:
- Is the ERP, or its connector, listed by IMDA as an InvoiceNow-Ready Solution?
- Does it send GST data to IRAS automatically, or does someone trigger it by hand?
- Can it receive Peppol invoices into accounts payable, not just send them?
- Does it handle credit notes, multi-currency invoices and the GST treatment of imported services correctly?
How MyInvois Works and Malaysia's Phased Rollout
MyInvois is a clearance model. Your ERP sends each e-invoice, in UBL XML or JSON format, to LHDN through the MyInvois API, either directly or through a middleware provider. LHDN validates it in near real time and returns a unique identifier, and a QR code goes on the visual invoice. After validation, the buyer has a short window to reject the invoice, and the supplier can cancel within that window. Confirm the current window length with LHDN. That reject-and-cancel cycle has to be built into your order-to-cash and procure-to-pay workflows.
The rollout is phased by annual turnover, with the largest taxpayers first and smaller bands following through 2025 and 2026. Dates, thresholds and transitional relief for smaller businesses have been adjusted more than once, and very small businesses are exempt. Check LHDN's latest guidance instead of relying on a vendor's sales deck.
MyInvois e-invoicing ERP work involves more than sales invoices. Your system also has to cover:
- Self-billed e-invoices for some purchases, including those from foreign suppliers. This matters for intercompany flows from Singapore into Malaysia.
- Consolidated e-invoices for B2C sales, submitted within the deadline after month-end.
- LHDN-prescribed generic taxpayer IDs for foreign buyers and the general public.
- Buyer master data that includes the tax identification number (TIN) and business registration number. Missing or wrong data is a leading cause of validation failures.
GST Versus SST: What the Tax Engine Must Handle
The two tax systems differ as much as the invoicing models. Singapore's GST is a broad value-added tax with input tax credits, reverse charge on imported services, and zero-rating for exports. Malaysia's Sales and Service Tax (SST) is a single-stage tax, not a VAT. Sales tax applies to taxable goods at set rates, and service tax applies to specified services. Rates and scope have been widened in recent years, so confirm current rates and categories with a Malaysian tax adviser.
For ERP Malaysia SST configuration, that means:
- Separate tax codes for sales tax on manufacture or import, and for service tax by service category.
- Handling of exemptions and special schemes, including manufacturer exemptions on raw materials, where they apply.
- No assumption that a general input credit exists. A tax engine designed for VAT can post SST incorrectly.
- Tax codes on the MyInvois payload that match the ones on your SST return.
Ask every shortlisted vendor to demonstrate one Malaysian service-tax invoice and one Singapore reverse-charge purchase, live, on the same tenant. If they can't, budget for custom tax configuration. Your tax adviser in each country should sign off the code mapping before go-live.
Shortlisting Vendors and Implementation Partners for Both Entities
Most international cloud ERPs are sold and supported in both countries, but maturity varies by product and by partner. The table is a starting framework, not a certification list. Confirm current status with the vendor and with IMDA or LHDN.
| Platform | Typical fit | InvoiceNow approach | MyInvois approach | Partner depth (SG / MY) |
|---|---|---|---|---|
| SAP S/4HANA Cloud | Larger groups, manufacturers | Vendor compliance service | Vendor compliance service | Deep / Deep |
| Oracle NetSuite | Mid-market distributors, multi-entity | Localization plus connector apps | Partner or third-party connector | Good / Good |
| Microsoft Dynamics 365 Business Central | Mid-market, partner-led | Partner extension | Partner extension | Good / Good, quality varies |
| Microsoft Dynamics 365 Finance and Supply Chain | Larger multi-country groups | Electronic invoicing service plus partner | Electronic invoicing service plus partner | Moderate / Moderate |
| Odoo | Smaller groups, cost-sensitive | Localization modules | Localization modules | Good / Good |
Partner availability often decides the shortlist more than product features do. Many Singapore partners can deliver InvoiceNow but have little MyInvois experience, and Malaysian partners often have the opposite gap. Ask each partner to describe a live project they've delivered under each regime, anonymized if necessary. Ask where their consultants sit: Kuala Lumpur, Singapore or offshore. And confirm whether one partner is accountable for both entities or a subcontractor handles one.
Go-Live Costs for a Two-Country Rollout
The figures below are typical 2026 market ranges for a mid-market group running one entity in each country. They vary widely by contract, user count and scope, so confirm with vendors and partners.
| Cost item | Indicative range (USD) | Main driver |
|---|---|---|
| ERP subscription, 25–75 users | $30,000–$150,000 per year | Edition, user types, modules |
| Implementation, both entities | $80,000–$350,000 | Manufacturing scope, data migration, integrations |
| InvoiceNow Access Point / connector | $1,000–$10,000 per year | Invoice volume, inbound and outbound |
| MyInvois middleware / connector | $2,000–$20,000 per year | Volume, self-billing, consolidation features |
| E-invoicing setup and testing, both countries | $10,000–$50,000 | Master-data cleanup, tax code mapping |
| Local tax adviser review | $5,000–$25,000 | SST and GST complexity |
Buyers most often underestimate master data, not software. Malaysian validation rejects invoices when buyer TINs or registration numbers are missing, and older customer files are often incomplete. Budget internal time to collect and verify these details before go-live. Singapore grant schemes have at times subsidized pre-approved InvoiceNow solutions for smaller firms. Check what's currently available, but don't build your business case around a grant.
Realistic Timelines and a Worked Example
Adding InvoiceNow to an ERP that's already live often takes 4 to 8 weeks. A MyInvois integration often takes 8 to 16 weeks, because of LHDN sandbox testing, self-billing scenarios and master-data fixes. A full new ERP across both entities typically takes 5 to 10 months.
Hypothetical example: Say a group has a GST-registered Singapore trading entity and a Malaysian manufacturing subsidiary with about RM60 million turnover, which puts it in scope for MyInvois. The Singapore entity bills the subsidiary for management services and sells it imported components.
- Months 1–2: Fix the Malaysian side first, because it's already under the mandate. Map SST codes, clean buyer master data and test MyInvois in the sandbox.
- Months 2–4: Build intercompany flows. When the Malaysian entity buys from its Singapore parent, a self-billed e-invoice may be needed. Confirm this with your adviser.
- Months 4–6: Set up InvoiceNow for the Singapore entity before its compliance date, including receiving Peppol invoices from suppliers.
- Month 6 onward: Run both entities in parallel for a month, with daily checks of rejected and failed submissions.
Sequence by deadline, not by where headquarters sits. A Singapore HQ that starts at home can leave its Malaysian subsidiary out of compliance.
Red Flags and a Decision Rule for Your Shortlist
Walk away from, or renegotiate with, any vendor or partner who shows these signs:
- They say one connector covers both countries. InvoiceNow and MyInvois need different payloads, endpoints and workflows.
- They can't show a MyInvois rejection or cancellation handled inside the ERP rather than in a portal.
- The SST setup copies a VAT template, with input credits switched on by default.
- The InvoiceNow solution sends invoices but can't receive them into accounts payable.
- Connector fees aren't quoted per invoice, so a volume spike can blow your budget.
- No named consultant has delivered each regime.
The decision rule: shortlist a platform only if it demonstrates both regimes live on one tenant and the partner names delivery staff for both countries. If none of your finalists clears that bar, keep the ERP and buy specialist e-invoicing middleware for Malaysia. Then have your Malaysian and Singapore tax advisers confirm scope before you sign.
Common questions
Can one cloud ERP handle both InvoiceNow and MyInvois?
Yes. Most major cloud ERPs support both through native compliance services or certified connectors. They're still separate integrations with different formats and workflows, so test each one on its own. Ask for a live demonstration of both on the same tenant.
Is Singapore's InvoiceNow the same as Malaysia's Peppol network?
No. Malaysia has its own Peppol framework for exchanging invoices between businesses, but the legal e-invoicing requirement there runs through LHDN's MyInvois validation. Sending an invoice over Peppol in Malaysia doesn't by itself meet the MyInvois requirement unless your provider also submits it to LHDN.
Do intercompany invoices between our Singapore and Malaysian entities need e-invoices?
Generally yes, on the Malaysian side. Sales to the Singapore entity need validated e-invoices, and some purchases from it may need self-billed e-invoices. On the Singapore side, InvoiceNow obligations depend on the entity's GST status and phase. Have a licensed tax adviser in each country confirm how this applies to your flows.
What happens if a MyInvois submission fails validation?
The invoice isn't valid until it passes, so you fix the data, usually missing or wrong buyer details, and resubmit. Your ERP should flag failures in a queue that finance checks every day. Repeated failures usually point to master-data problems, not software bugs.
How long does it take to add InvoiceNow to an existing ERP?
Often 4 to 8 weeks if your ERP already has an IMDA-listed InvoiceNow-Ready connector. It takes longer if you need custom work for multi-currency invoices, credit notes or receiving supplier invoices into accounts payable. Finish Peppol registration and testing well before your compliance date.
Are local accounting packages a better fit than international cloud ERPs?
For a single small entity in one country, local packages can be cheaper and well localized. For groups running entities in both countries, an international cloud ERP usually wins on consolidation, intercompany billing and multi-currency control. Compare total three-year cost, including connector fees and partner support, before you decide.
Written by the Carrier Mesh HQ editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.