- 8
- March
What if SAP, Oracle, Odoo, and Saeree ERP could exchange data instantly — without forcing everyone onto the same platform? The answer isn't building a universal platform, but using "universal standards" for data exchange — just as countries don't all speak the same language, but agree to use English as a "lingua franca" for international trade.
In brief: Universal standards like Peppol (e-Invoice), EDI (procurement & shipping), ISO 20022 (finance) enable every ERP vendor to exchange data — already deployed across 111 countries with over 2.5 million organizations | Enterprises lose an average of $370 million/year from disconnected systems
What's the Problem? — Why Can't ERP Systems Understand Each Other
Most organizations run multiple systems — one ERP, a separate accounting system, another vendor for warehouse management. Each one "speaks a different language." Data from SAP can't be sent directly to Oracle — someone has to manually convert the format every time.
| Figure | Detail |
|---|---|
| 897 apps | Average number of applications used by enterprises (2024) |
| 29% | Are integrated — the other 71% remain siloed |
| $370M/year | Average cost enterprises lose from disconnected systems (Integration Debt) |
| 30-40% | Share of IT budget spent managing complexity of disconnected systems (Gartner) |
With 10 systems, you need 45 connections (n×(n-1)/2) — with just 20 systems, that's 190! This is the "Spaghetti Architecture" trap many organizations fall into.
The Answer: Use "Universal Standards," Not a "Universal Platform"
Instead of forcing every organization onto the same ERP (which is impossible) — have every system agree: "when exchanging data, use the same format."
┌─────────┐ Peppol/UBL ┌─────────┐
│ SAP │ ←──────────────→ │ Odoo │
└─────────┘ Standard Format └─────────┘
↑ ↑
│ API Gateway │
│ (translates for all) │
↓ ↓
┌─────────┐ ISO 20022 ┌─────────┐
│ Saeree │ ←──────────────→ │ Oracle │
└─────────┘ └─────────┘
Each ERP doesn't need to change its internal system — just build an "adapter" that converts data to the universal standard before sending, and converts back when receiving.
6 Universal Standards Used Worldwide
| Standard | Purpose | Status |
|---|---|---|
| Peppol (UBL) | e-Invoice, PO, Delivery Note | 2.5M organizations, 111 countries |
| EDI (X12/EDIFACT) | Purchase orders, shipments, payments | $34B market, 50+ years in use |
| ISO 20022 | Cross-bank/international transfers | SWIFT mandated (Nov 2025) |
| xBRL | Financial reporting/statements | Mandated in 50+ countries |
| GS1 | Product codes (GTIN), locations (GLN) | 2M companies worldwide |
| OData | API for ERP data query/exchange | Primarily used by SAP, Microsoft |
1. Peppol — The Fastest-Growing e-Invoice Standard
Peppol (Pan-European Public Procurement OnLine) is a digital business document exchange network — for invoices, purchase orders, and delivery notes — built on UBL (Universal Business Language), which is ISO/IEC 19845.
Remarkable growth: Peppol grew from 110,000 organizations (2019) to 2.5 million organizations across 111 countries — a 1,173% increase in just 5 years.
| Country | e-Invoice Status | Mandate Timeline |
|---|---|---|
| Singapore | InvoiceNow (Peppol) — mandatory for GST businesses | Apr 2028 - 2031 |
| Malaysia | MyInvois (Peppol) — mandatory for all businesses | Aug 2024 onwards (phased) |
| Belgium | Peppol BIS 3.0 — all B2B businesses | Jan 2026 |
| All EU | ViDA (VAT in the Digital Age) | Jul 2030 (cross-border) |
| Thailand | e-Tax Invoice (ETDA standard) — not yet mandatory | Voluntary (tax incentives available) |
For Thailand: The Revenue Department's e-Tax Invoice system uses XML based on the ETDA standard — currently processing 1.5 million invoices/month (+40% YoY). While not yet mandatory, trends from ASEAN (Singapore and Malaysia already mandated) may lead Thailand to join the Peppol network in the future.
2. EDI — The Veteran That's Still Going Strong
EDI (Electronic Data Interchange) has been in use for over 50 years — split into two families: ANSI X12 (Americas) and EDIFACT (UN/Europe/Asia). The global EDI market is worth $34 billion (2024) and is projected to reach $74 billion by 2031.
The automotive industry is the most sophisticated EDI user — driving Just-in-Time Manufacturing across OEMs, every tier of suppliers, and the entire logistics chain.
3. ISO 20022 — The Lingua Franca of Finance
ISO 20022 is the messaging standard for financial systems — covering payments, securities, trade finance, and FX. Every accounting system that connects to banks needs to understand this standard.
Key milestone: SWIFT completed its migration from MT → MX (ISO 20022) on 22 November 2025 — over 11,000 banks worldwide must now use the new format. ISO 20022 carries 10x more data than the legacy MT format — significantly improving AML screening and straight-through processing.
4. xBRL — Cross-System Financial Reporting
xBRL (eXtensible Business Reporting Language) is used in 50+ countries. The SEC (US) has mandated it for all listed companies since 2018, and the EU mandated it through ESEF since 2022. The advantage: ERP systems can automatically export financial statements as xBRL — eliminating manual tagging and reducing errors.
5. GS1 — One Standard for Products and Locations
GS1 defines standard codes for products (GTIN), locations (GLN), and shipments (SSCC) — used by 2 million companies. ERP systems integrated with GS1 barcodes achieve warehouse accuracy of 95%+, reduce stock-outs by 50%, and can respond to recalls within 1 hour.
Important: GS1 Sunrise 2027 — by the end of 2027, all retailers must be able to read 2D barcodes (QR codes) at the point of sale, replacing traditional 1D barcodes.
6. OData — The Standard API for ERP
OData (Open Data Protocol) is an ISO/IEC 20802 standard for APIs, primarily used by SAP and Microsoft — with a built-in query language ($filter, $select, $expand) that lets ERPs from different vendors query each other's data without building custom integrations.
How to Connect ERP Systems — 4 Approaches
| Approach | Best For | Cost |
|---|---|---|
| 1. Custom Point-to-Point | 1-2 systems | $5K-50K per connection + 15-20%/year maintenance |
| 2. iPaaS (MuleSoft, Boomi) | 10-50+ systems | $15K-100K/year + $400-800/connector/month |
| 3. Event-Driven (Kafka) | Real-time, multiple consumers | EDA market $8.6B (2024) → $21.4B (2035) |
| 4. Open Standards (Peppol/EDI) | Entire supply chain | Lowest — shared infrastructure + network effect |
Recommendation: For organizations choosing an ERP — select one that supports open API standards (OData/REST) and can export/import data in UBL or EDI format. This will significantly reduce integration costs in the long run.
5 Challenges and Solutions
| Challenge | Solution |
|---|---|
| Different data formats — SAP uses IDOC, Oracle uses BOD, Odoo uses JSON API | Use a Canonical Data Model (OAGIS/ConnectSpec) as a "common language" |
| Spaghetti Architecture — 10 systems = 45 connections | Use an API Gateway as a central hub → reduces to n connections |
| Security — system integration = increased attack surface | API Gateway manages OAuth 2.0, TLS 1.3, centralized audit logs |
| Customization Lock-in — heavily customized ERPs can't expose APIs | "Clean Core" — move customizations to sidecar apps using standard APIs |
| Batch vs Real-time — legacy EDI runs in batch (daily/hourly) | Event-Driven Architecture (Kafka) for real-time inventory |
PINT — The Next-Generation Standard to Watch
PINT (Peppol INTernational) was launched in July 2023 and became mandatory in March 2025 — addressing the limitation that BIS 3.0 was designed only for the EU (supporting only VAT). PINT has a 3-layer architecture:
| Layer | Description |
|---|---|
| 1. PINT Core | Mandatory fields at the global level (required by all countries) |
| 2. Regional Rules | e.g., GST (Singapore), SST (Malaysia), VAT (EU) |
| 3. Country-Level Extensions | Country-specific fields (e.g., Thai tax ID number) |
If Thailand joins the Peppol network in the future, PINT will serve as the base — ERPs that support PINT will be ready immediately.
Real-World Example: EU ViDA — Saving €4.1 Billion
The EU passed ViDA (VAT in the Digital Age) on 11 March 2025:
- Cross-border e-Invoice mandate: July 2030
- Full harmonization: January 2035
- Reduces VAT fraud by €11 billion/year
- Saves €4.1 billion in administrative costs over 10 years
This is proof that universal standards aren't just theory — they deliver real ROI at the continental scale.
What About Saeree ERP?
Saeree ERP is designed for easy integration with other systems — supporting data export/import in standard formats and providing APIs for connecting with external systems. No matter what ERP your trading partners use, data exchange is seamless.
Summary: Comparing 3 Approaches
| Approach | Pros | Cons | Best For |
|---|---|---|---|
| Build (Custom) | 100% tailored to needs | Most expensive long-term, Spaghetti | 1-2 connections |
| Buy (iPaaS) | Fast, pre-built connectors | High license fees | 10-50+ systems |
| Standards (Peppol/EDI) | Lowest cost, Network effect | Ecosystem dependency | Entire supply chain |
"The future isn't forcing everyone onto one ERP — it's making every ERP multilingual. Like a person who speaks Chinese in China and English in America. The internal language doesn't need to change — just translate correctly when talking to others."
