Key takeaways
- Integration lets sales see orders, invoices and credit status in Salesforce, and lets finance receive clean orders without re-keying.
- Decide which system owns each piece of data before choosing tools.
- Common options are point-to-point APIs, middleware such as MuleSoft, or a native ERP on Salesforce such as Certinia.
- UAE e-invoicing becomes mandatory in phases from 1 January 2027, so invoice data must be complete and structured at source.
Why integrate Salesforce with your ERP?
Salesforce manages customers and the sales process. Your ERP manages orders, inventory, invoicing and accounting. Without integration, staff copy data between the two, which causes delays, errors and arguments about whose numbers are right. Integration typically aims to:
- Turn closed opportunities into sales orders without re-keying
- Show order status, invoices and payments to account managers in Salesforce
- Keep customer, product and price data consistent across both systems
- Give leadership one view of pipeline, bookings and revenue
Step 1: Decide which system owns which data
| Data | Usual system of record | Typical direction |
|---|---|---|
| Leads, opportunities, activities | Salesforce | Stays in Salesforce |
| Customer master (legal name, TRN, billing address) | Often the ERP, after the account is approved | Two-way with clear ownership per field |
| Products and price lists | ERP | ERP to Salesforce |
| Quotes | Salesforce (or CPQ) | Stays in Salesforce |
| Sales orders | ERP | Salesforce to ERP on close |
| Invoices, payments, credit limits | ERP | ERP to Salesforce for visibility |
Agreeing this table with sales and finance before any build prevents most integration disputes later.
Step 2: Choose an integration pattern
- Real-time request and reply: Salesforce calls the ERP when a user needs live data, such as stock or credit status.
- Event-driven: a change in one system publishes an event that the other consumes, for example an order created on opportunity close.
- Scheduled batch: data syncs at set intervals, suitable for price lists or invoice history.
- Data virtualisation: Salesforce displays ERP data without storing it, useful for large invoice histories.
Most real projects combine several patterns.
Step 3: Choose the tools
| Approach | When it fits | Trade-offs |
|---|---|---|
| Direct APIs (Apex callouts, ERP APIs) | One ERP, few data flows | Quick to start, harder to maintain as flows grow |
| Middleware or iPaaS (for example MuleSoft) | Several systems, complex mapping, monitoring needs | More setup and licence cost, much easier to scale and monitor |
| Pre-built connectors | Common ERPs with standard processes | Fast, but limited when processes are customised |
| Native ERP on Salesforce (for example Certinia) | Services businesses wanting CRM and finance on one platform | Removes CRM-ERP sync, but is an ERP decision in itself |
Salesforce completed its acquisition of Informatica in November 2025, adding data integration, data quality and master data management capabilities alongside MuleSoft. These are worth considering for larger data programmes.
UAE e-invoicing: what it means for your integration
The UAE Ministry of Finance is introducing mandatory e-invoicing in phases. According to the timeline published in July 2026:
| Phase | Who | Appoint an Accredited Service Provider by | Mandatory from |
|---|---|---|---|
| 1 | Businesses with annual revenue of AED 50 million or more | 30 October 2026 | 1 January 2027 |
| 2 | Businesses with annual revenue below AED 50 million | 31 March 2027 | 1 July 2027 |
| 3 | Government entities | 31 March 2027 | 1 October 2027 |
E-invoices are issued in a structured format through Accredited Service Providers under a five-corner model. E-invoicing is usually handled by the ERP or finance system, not by Salesforce. But the data that flows from Salesforce into the ERP must be complete enough to produce a compliant invoice. In practice, review:
- Customer legal names, addresses and Tax Registration Numbers captured in Salesforce
- Product and tax codes on quote and order lines
- Validation rules that stop incomplete orders reaching the ERP
- How credit notes and amendments flow between systems
Confirm your obligations and dates with your tax adviser and the Ministry of Finance guidance, as details continue to be updated.
Testing and monitoring
- Test with realistic volumes and edge cases: partial deliveries, cancellations, credit notes, multi-currency orders.
- Log every integration error with a clear owner and alert.
- Build a reconciliation report comparing orders and invoices across both systems.
How we can help
Our Salesforce implementation team designs and builds integrations as part of rollouts, and our Salesforce developers can extend existing ones. If you are considering a Salesforce-native ERP, read what Certinia is and how it works, or see our Certinia and Salesforce case study.
Frequently asked questions
Which ERPs can Salesforce integrate with?
Salesforce can integrate with most ERPs that offer APIs, including SAP, Oracle, Microsoft Dynamics, NetSuite and Odoo, either directly, through middleware or through pre-built connectors.
Does Salesforce handle UAE e-invoicing?
E-invoicing is normally produced by the ERP or finance system through an Accredited Service Provider. Salesforce must still pass complete and accurate customer, product and tax data to that system.
Do we need MuleSoft?
Not always. Simple integrations can use direct APIs. Middleware such as MuleSoft becomes valuable when you connect several systems, need complex transformations or want central monitoring.
How long does an ERP integration take?
A single, well-defined data flow can take a few weeks. A full quote-to-cash integration with several flows, testing and reconciliation typically takes a few months.
Connecting Salesforce to your ERP?
We can help you define data ownership, choose the right pattern and build an integration your finance team can trust.
Related articles
Sources