The Short Answer
Lead-to-Cash is a process that spans four groups – Marketing, Sales, Finance, and Operations – and therefore breaks down at the boundaries, not in the middle. The three transition points that determine everything are: when a lead becomes an opportunity, when a quote becomes approved, and when a closed-won opportunity becomes an order in the operational system.
For each of these, three questions need written answers: who decides, what is required to pass, and what happens if the transition fails. If even one of these is missing, a workaround spreadsheet emerges, and from it stems most of the discrepancies between what was sold and what was billed.
Transition Point 1: From Lead to Opportunity
This boundary determines the quality of the entire pipeline. The common failure is to automatically convert every lead, which inflates the forecast and renders conversion history useless.
What's required: Written conversion criteria (authorized contact, articulated need, timeframe), defined owner for each side of the boundary, and a rule for handling leads that don't meet the criteria – Nurture, not deletion. Further details on this topic can be found in Sales Cloud Implementation.
Transition Point 2: From Quote to Approved Quote
This is where most of the process delay concentrates, almost always due to undefined approval hierarchies rather than the tool itself.
| Component | What Must Be Defined | What Happens Without It |
|---|---|---|
| Catalog and Price List | Single source of truth for pricing | Quotes with manual prices |
| Discount Threshold | Tiered structure by percentage and customer type | Every discount goes to the CEO or none at all |
| Approval Response Time | Defined target, e.g., one business day | Phone bypass and retroactive documentation |
| Non-Price Terms | Payment terms, warranty, SLA | Commitments that don't reach Finance |
The last point is usually neglected: organizations build meticulous discount control but allow representatives to commit to net +90 payment terms without any approval.
Transition Point 3: From Closed-Won Opportunity to Order
This is the most technical point and also where failures are most costly. Three questions determine the architecture:
- Who issues the order – typically the ERP. Salesforce sends a request and receives an identifier, not managing inventory or billing.
- What happens on failure – a visible status on the opportunity, an alert to the process owner, and an idempotent resubmission mechanism that won't create a duplicate order.
- What is sent back – at minimum, an order ID, delivery status, and billing status. Without this feedback, sales reps call Finance to answer customers.
Principles for designing the integration itself are detailed in Salesforce and ERP Integration, and error handling in Handling Errors in Integrations.
The Quiet Problem: Product Alignment Between Systems
Most discrepancies between quotes and invoices aren't due to price but to products. An item code existing in the ERP but not in Salesforce, a product discontinued on one side but remaining active on the other, or a different unit of measure.
The rule: The product catalog is owned by only one side – typically the ERP – and synchronized to Salesforce at a defined frequency, including marking discontinued products instead of deleting them. Deletion breaks historical opportunities and skews analytics.
What to Measure
| Metric | What It Reveals |
|---|---|
| Average Quote Approval Time | Most common bottleneck |
| Rate of Re-created Quotes | Sign of unclear pricing or incomplete catalog |
| Order Creation Failures | Integration stability |
| Discrepancy Between Opportunity Amount and Invoice Amount | End-to-end process quality |
| Closed-Won Opportunities Without an Order within 48 Hours | Leads that fell between systems |
The last metric is the simplest check for process health, and few organizations monitor it regularly.
Implementation Order
First, implement one end-to-end sales path – one customer type, one product category – until a successful order is created in the ERP. Only after this path is stable should configurations, currencies, legal entities, and renewals be added. Premature expansion solidifies pricing decisions before they are field-tested.
Summary
Lead-to-Cash is not a technology project but an agreement between four groups on three boundaries. Those who define these boundaries in writing – including failure paths – get a measurable process; those who start with the tools get a chain that works in demos and relies on phone calls in practice.