Quote-to-Order Handoff from Salesforce to ERP
The O2C process begins when a sales rep creates a Quote in Salesforce, typically using Salesforce CPQ or native Quote objects. When the customer accepts the quote, it converts to an Order that must flow into the ERP as a sales order with accurate pricing, terms, and line-item detail. This handoff is the most error-prone step in the cycle because field mappings, approval workflows, and validation rules differ between systems.
- Salesforce Quote object or CPQ Quote__c converts to Order upon customer acceptance with a status trigger
- Order line items map to ERP sales order lines with item number, quantity, negotiated price, and requested date
- Payment terms from Salesforce Account (Net 30, Net 60) carry through to ERP order header for AR processing
- Discount structures and tiered pricing from CPQ must translate to ERP price adjustment codes or manual overrides
- Approval routing in Salesforce must complete before the order releases to ERP to prevent unauthorized commitments
Fulfillment, Shipment, and Invoice Sync
Once the ERP accepts the sales order, fulfillment processes including picking, packing, shipping, and invoicing execute within the ERP. Salesforce needs visibility into these downstream events so that sales reps and customer service teams can answer status inquiries. Shipment confirmations, tracking numbers, and invoice documents flow back to Salesforce as related records on the original Order or Account.
- ERP shipment confirmation creates or updates a Salesforce Fulfillment__c or Shipment__c custom object with tracking details
- Invoice data syncs to Salesforce as Invoice__c records linked to the Account and original Order for full traceability
- Partial shipments in the ERP generate multiple Salesforce fulfillment records against a single Order
- ERP backorder notifications update Salesforce Order line status so reps can proactively communicate delays
- ASN (Advanced Shipping Notice) data from the ERP populates Salesforce fields for drop-ship and third-party logistics scenarios
Payment and Revenue Recognition Closure
The final leg of O2C covers payment collection and revenue recognition. Payments received in the ERP's accounts receivable module update the outstanding balance visible in Salesforce. For subscription or milestone-based billing, revenue recognition schedules in the ERP must align with Salesforce revenue schedules to ensure reporting consistency across CRM and finance.
- AR payment postings in the ERP update Salesforce Account.Outstanding_Balance__c and Payment_History__c records
- Credit memos and deductions in the ERP sync back to Salesforce to adjust opportunity value and forecast accuracy
- Salesforce Revenue Schedules align with ERP revenue recognition entries for ASC 606 compliance
- Collections workflow triggers in Salesforce create Tasks for account managers when AR aging exceeds thresholds
- Cash application data from the ERP closes the loop, marking Salesforce Invoices as Paid with payment date and method
Try it here, free
Customer Lead Time Quote Calculator
Estimate the lead time to quote a customer from queue load, setup, run time, material wait, outside processing, transit and a safety buffer.
Want to eliminate O2C handoff failures between Salesforce and your ERP? Talk to our process integration consultants.