ERP Is from Mars, CRM Is from Venus
Closed, according to whom
An opportunity flips to Won in Dynamics 365 Sales. Over in Finance and Operations, nothing has happened yet: no sales order, no invoice. Sales says the deal closed. Finance says it didn’t, and neither of them is lying.
The usual explanation borrows from the old self-help shelf: ERP is from Mars, CRM is from Venus. It’s a good line. It’s also too generous, because it implies the two camps just have different personalities and could get along with a little counseling. The gap is grammatical. CRM talks in the future conditional, ERP talks in the past perfect, and neither system was ever taught to conjugate in the other’s tense.
CRM: what might happen
Everything in a CRM is a maybe with a number attached. An opportunity carries estimated revenue and a probability, and its close date is a guess that slides every time the buyer’s procurement department goes quiet. Multiply revenue by probability across the pipeline and you get a weighted forecast. Useful to a sales manager. Meaningless to a general ledger.
The vocabulary follows from that: relationships, calls, champions, next steps. A win is a statement of intent (the customer has said they mean to buy), and a loss gets a reason code and then mostly sits there, since a lost opportunity triggers nothing downstream. Nobody in sales thinks of a won deal as provisional.
ERP: what has happened
ERP doesn’t believe anything until it’s posted. A sales order in Finance and Operations is still soft; you can change the quantity or the price. Post the invoice and the record hardens. You don’t edit a posted invoice, you issue a credit note, and you don’t fix a posted journal, you reverse it and post a new one. The ledger keeps the mistake and the correction side by side, permanently, because the point of the thing is that the past stays where you put it.
Even the customer is a different animal. In CRM an account is a web of people, from the champion who pushed the deal through to the contact who left in March and is still on the newsletter list. In ERP a customer is a party with a customer group, payment terms, a credit limit and a posting profile that decides which ledger accounts get hit. Same company. One system wants to know who to call; the other wants to know whether they’ll pay.
The tense nobody owns
Between the two sits the present progressive, and it belongs to operations. A sales order released to the warehouse is no longer a possibility, and it isn’t a fact on the ledger either. Inventory is reserved. A wave is being picked. Half the order ships today and the rest is waiting on a purchase order that’s waiting on a vendor.
This is where integration projects tend to bleed. CRM stopped paying attention the moment the opportunity closed, and ERP won’t fully commit until the invoice posts, so the in-between state has no real owner. The rep asks customer service, customer service asks the warehouse, and the warehouse checks a screen the other two can’t see.
The handoff
Quote to sales order is where the two dictionaries collide. In the Dynamics stack, dual-write is Microsoft’s attempt at a shared vocabulary. It syncs Dataverse tables with Finance and Operations entities in near real time, so an account in Sales maps to a customer in F&O and a won quote can become a sales order without anyone retyping it.
Anyone who has configured it knows the field maps are the easy part. The hard part is that the two sides disagree about when a record is allowed to exist. CRM wants a customer the moment someone sounds interested. ERP wants a customer group and a credit check before it will take the call, and a prospect created in Sales with half its fields empty is exactly the kind of record that stalls a sync. Products with variants are their own afternoon.
When the future is allowed to become the past
ASC 606 is, among other things, a rule about tense. It decides when a promise to a customer becomes revenue, and the answer is when the performance obligation is satisfied, not when the rep rings the bell. IFRS 15 says much the same outside US GAAP. Sales celebrates the signature. Accounting waits for delivery, and on a subscription or a bundled deal it may wait for months, recognizing the revenue a slice at a time.
Forecasting is the one place the two tenses are forced to share a sentence. In theory the weighted pipeline from CRM is what demand plans and cash forecasts in ERP should be built on. In practice that means finance is planning around probabilities a sales rep typed in, and finance hates that. Supply chain hates it more, because they’re the ones holding the inventory when a 70 percent deal slips a quarter.
