Here’s a scene that plays out in a lot of companies every month. A sales rep closes a deal in Salesforce and celebrates. A week later, someone in finance retypes the order into Oracle or NetSuite, notices the discount doesn’t match the price list, and emails the rep to ask what was agreed. The customer gets an invoice that’s slightly wrong. Payment slips by 30 days while it gets sorted out.
Nobody did anything badly. The problem is that the two systems that matter most to revenue, the CRM where deals are made and the ERP where money is collected, don’t really talk to each other.
We spend a lot of our time at Selectiva on exactly this gap, because we work on both sides of it. Our view is simple: agree which system owns which data, then fix the one handoff that hurts most before you try to connect everything else. This post covers where the money leaks, why the problem is getting more urgent, and what a sensible fix looks like.
Where the money actually leaks
Revenue leakage rarely shows up as one big loss. It’s lots of small ones, spread across the handoff between sales and finance.
Prices that don’t match. Sales quotes from a price book in Salesforce while finance invoices from a different one in the ERP. When the two drift apart, someone is either undercharging customers or arguing with them.
Discounts nobody approved. If approval rules live in Salesforce but the ERP just accepts whatever arrives, an unapproved discount goes straight onto the invoice.
Renewals and usage that get missed. Subscription renewals, price increases and usage-based charges depend on contract data being accurate in both systems. When it isn’t, you bill late, bill wrong, or don’t bill at all.
Reps selling blind. Your sales team can’t see that a customer is 90 days overdue, has a credit hold, or that the product they’re quoting is out of stock. They find out after the deal closes, which is the worst possible time.
Slow close. Every order that has to be rekeyed or corrected adds days between signature and cash. Multiply that across a quarter and it shows up in your working capital.
Why this is getting more urgent
Three things are forcing the issue in 2026.
First, a lot of companies are rebuilding their quoting anyway. Salesforce CPQ is in end of sale, not end of life. Existing customers keep their support and can renew, but Salesforce no longer sells new CPQ licenses to new customers, and new development is going into Revenue Cloud Advanced, which Salesforce has also marketed as Agentforce Revenue Management. If you’re migrating, you’re redesigning products, pricing and contracts from scratch. That’s the cheapest moment you’ll ever get to fix the ERP connection, and it would be a shame to rebuild the quoting side and leave the old manual handoff in place. We covered the migration itself in CPQ End-of-Sale Is No Longer a Future Problem.
Second, many Oracle customers are deciding whether to stay on E-Business Suite or move to Fusion. Either way, the integrations need attention, and it’s much easier to design them properly than to patch them later.
Third, AI agents make the gap more visible. An agent that answers “when will my order ship?” or “can I extend this contract?” needs information from both systems. If it only sees Salesforce, it will give confident answers that are half right. That’s worse than no answer at all.
What good looks like
The single most useful decision in any CRM–ERP project isn’t technical. It’s agreeing which system owns which piece of data. Once that’s settled, most of the integration design follows naturally.
Here’s the split we see work for most B2B companies:
| Data | Owned by | Shared with |
| Accounts, contacts, opportunities | Salesforce | ERP, when an order is placed |
| Products and price books | Usually the ERP | Salesforce, for quoting |
| Quotes and discount approvals | Salesforce | ERP, on the final order |
| Orders, invoices, payments | ERP | Salesforce, so reps can see status |
| Credit limits and holds | ERP | Salesforce, before a quote goes out |
| Inventory and delivery dates | ERP | Salesforce, at quote time |
Your split may differ, and that’s fine. What matters is that everyone agrees, it’s written down, and the integration enforces it. The worst setup is two systems that both think they own the price list.
With ownership clear, the aim is simple. When a deal closes, a clean order lands in the ERP without anyone retyping it. And when something changes in the ERP, such as a shipment, an invoice or a late payment, the account team sees it in Salesforce the same day.
Picking the right integration tool
We work with all four of the major platforms, so we don’t have a favourite to push. Each fits a different situation.
MuleSoft makes the most sense when Salesforce is at the centre of your world and you’re planning many integrations over time, not just one. It’s owned by Salesforce, handles complex, high-volume work well, and encourages reusable APIs. It also costs more than the alternatives, so it pays off at scale.
Oracle Integration Cloud (OIC) is the natural choice if your ERP is Oracle Fusion or EBS and you already have an Oracle subscription. It has prebuilt adapters for both Oracle and Salesforce, and your Oracle team will find it familiar.
Boomi suits mid-sized companies that want to get connected quickly, with a visual builder and a big library of ready-made connectors. It’s often the fastest route to a working Salesforce–NetSuite link.
Informatica is strongest when data quality is the real problem: merging duplicate customers, standardising product records, and feeding a data warehouse alongside the live integration.
One honest piece of advice: point-to-point custom code, written by a contractor years ago, is often what companies are trying to escape. Whatever tool you choose, make sure someone on your team can see when a sync fails and fix it without calling the original developer.
Where to start
You don’t need to connect everything at once. In fact, you shouldn’t.
Start by following one real deal from quote to cash. Sit with the sales rep, the deal desk and the finance analyst, and note every point where someone copies, checks or corrects information by hand. That list is your business case, and it’s usually longer than anyone expects.
Then fix the flow that hurts most. For most companies, that’s getting a closed deal into the ERP as a clean order, with the right prices and approvals attached. The second step is usually sending invoice and payment status back to Salesforce, so reps stop being surprised by overdue customers.
Measure before and after. Days from signature to invoice, the number of corrected invoices each month, and hours of manual order entry are all easy to track and hard to argue with.
Where Selectiva fits
Most consulting firms are either a Salesforce shop or an Oracle shop. We’re both. As a Salesforce Crest Partner, we implement Sales Cloud, CPQ and Revenue Cloud Advanced. On the ERP side, we’ve worked with Oracle E-Business Suite, Oracle Fusion and NetSuite since 1999. And we build the integrations between them on MuleSoft, Boomi, Oracle Integration Cloud and Informatica.
That means one team can look at the whole quote-to-cash process, rather than two vendors pointing at each other when a sync breaks. You can see the kind of quoting problem we solve in our case study on building a centralized quote estimator.
Selectiva can trace one of your deals from quote to cash, show where data is being rekeyed or lost, and scope the integration that fixes it. Talk to our team and one of our consultants will get back to you within 24 hours.
