The sales team says the quarter closed at one number. Finance says another. Operations has a third. Everyone is looking at real data, and nobody is wrong, which is exactly what makes it so hard to fix.

For manufacturers and distributors, the gap almost always lives between the CRM and the ERP. This guide explains why the numbers drift apart, what to decide before you connect the systems, and how to build a reconciliation that leadership can trust.

Why the numbers never match

The disagreement is rarely arithmetic. It is a difference in what each system is counting.

  • Different events. The CRM counts a deal when it is marked won. The ERP counts a sales order when it is entered, a shipment when it leaves and revenue when it is invoiced or recognized. These happen on different days, sometimes in different quarters.
  • Different amounts. A deal amount is an estimate at the time of the sale. An invoice reflects final quantities, freight, discounts and changes.
  • Different identities. The same customer may exist as three company records in the CRM and one customer account in the ERP, with no shared ID to connect them.
  • Different owners. Sales owns the CRM, finance owns the ERP, and neither owns the bridge between them.

Decide before you connect anything

Most failed integrations skip these decisions and start with connectors. Settle them first, in writing.

  1. Pick a system of record for each object. Customer accounts, orders, invoices, products and pricing each need one authoritative home. The CRM usually owns prospects and pipeline. The ERP usually owns orders, invoices and shipment status.
  2. Create a shared account ID. Store the ERP customer number on the company record in the CRM, and the CRM company ID in the ERP if it allows it. This single field is what makes reconciliation possible.
  3. Define the revenue terms. Agree on what booked, invoiced and recognized mean in your company, and which one each report uses.
  4. Map the objects. Decide how a CRM deal corresponds to an ERP sales order, and how products and SKUs line up.

Choosing how to connect them

There are several ways to move data between a CRM and an ERP, and the right one depends on your systems and your budget.

  • A pre-built connector. Fastest to start and cheapest to maintain when one exists for your ERP, but often limited in what it syncs and how it handles your custom fields.
  • An integration platform. A middle path that handles mapping, scheduling and error handling, with more flexibility than a basic connector.
  • A custom integration through the systems' APIs. The most control and the most upkeep. It makes sense when your processes are unusual.
  • Scheduled file transfers. Unglamorous, but sometimes the practical answer for older ERP systems.

Whatever you choose, plan for error handling. Syncs fail, and someone must be told when they do.

What to sync, and in which direction

Resist the urge to sync everything both ways. Start with the smallest set that answers real questions.

  • ERP to CRM: order status, invoice totals, payment status and last order date on the company record. This gives sales visibility into what customers actually buy.
  • CRM to ERP: new customer details when a deal closes, so accounts are not set up twice by hand.
  • One way unless you have a reason. Two-way sync on the same field invites conflicts. Assign each field one direction.

Build the reconciliation report

Once the data flows, build a standing report that compares what each system says, by account and by period. Include closed-won value, invoiced value and the difference, plus a list of deals with no matching order and orders with no matching deal. Review the exceptions weekly. The list should shrink over time, and every remaining item should have an explanation.

Common pitfalls

  • Syncing before cleaning duplicate company records, which spreads the mess into both systems.
  • Letting reps edit fields that the ERP is supposed to control.
  • Treating a launch as the finish line instead of assigning someone to own the integration afterward.
  • Reporting on deal amount and calling it revenue.

Frequently asked questions

Do I need to replace my ERP or CRM to fix this?

Rarely. The problem is almost always definitions, identifiers and ownership, which can be fixed with the systems you already have.

Which system should be the source of truth for revenue?

For recognized revenue and invoices, the ERP. For pipeline and forecast, the CRM. The goal is a clear bridge between them, not one system replacing the other.

How long does a CRM and ERP reconciliation project take?

Defining terms and cleaning identifiers can take a few weeks. Integration build time depends on your ERP and chosen method, and is usually the longest part.

What is the first step?

Match a sample of closed deals from last quarter to their invoices by hand. The mismatches you find will show which of the problems above you actually have.

Want to see where your numbers split?

Reconciling CRM and ERP data is one of the first things I look at in a revenue diagnostic. You get a clear map of where the numbers diverge and what to fix first. Email me at gr@gtmwiz.co to talk it through.