Revenue Cloud and SAP: who owns what in quote to cash?
In quote to cash with Revenue Cloud and SAP S/4HANA, Salesforce should own what sales changes every day: the catalog for selling, the configuration, the quote and its approval. SAP should keep the material master, the sales order for delivery and, for machine sales, the invoice. Revenue Cloud Billing only belongs in the picture when recurring or usage-based revenue is sold and changed in Salesforce, and then Salesforce becomes a subledger that sends journal entries to SAP. Pick one of three cuts, name an owner per object, and get the split signed by sales, finance and IT before a partner starts building.
Which pattern does Salesforce document for SAP?
The closest official pattern is use case 3a of the MuleSoft Accelerator for SAP1, quote to cash between Salesforce and SAP S/4HANA. It has two variants. In the CPQ variant, the page says “SAP S/4HANA is the system of record pricing conditions.” When a sales rep clicks Calculate on the quote, the integration fetches the net price per line from SAP and validates any additional discount against discount thresholds configured in SAP. Creating the order in Salesforce then triggers the order in SAP S/4HANA, and the SAP order number is synced back.
Three details from that page matter for a manufacturer:
- Products come from a PIM in the accelerator, with global IDs kept in an MDM system. If your material master lives in SAP, SAP plays that role.
- Complex pricing is out of scope, explicitly including SAP Variant Configuration. If your machines are configured in SAP today, the accelerator does not answer that question.
- Revenue Cloud is not mentioned. The accelerator covers Sales Cloud and Salesforce CPQ and was published in December 2021.
The pattern still carries over to Revenue Cloud, which Salesforce’s Winter ’27 documentation also calls Revenue Management and which started as Revenue Lifecycle Management. Revenue Cloud works on standard objects: the quote data model2 and the order data model3 list Quote, Quote Line Item, Order, Order Item, Asset, Product2 and Pricebook Entry. So the integration points are the same, but the design is your partner’s, and someone on your side should review it.
Quote only, quote and order, or all the way to the invoice
I see three cuts that work. Each one moves the line between Salesforce and SAP one step further to the right.
| Step | Cut 1: quote only | Cut 2: quote and order | Cut 3: full quote to cash |
|---|---|---|---|
| Catalog for selling, configuration | Revenue Cloud | Revenue Cloud | Revenue Cloud |
| Price | SAP or Revenue Cloud, one master | same | same |
| Quote and approval | Revenue Cloud | Revenue Cloud | Revenue Cloud |
| Order | SAP, created from the accepted quote | Revenue Cloud, handed to SAP | Revenue Cloud, handed to SAP |
| Amendments and renewals | SAP or manual | Revenue Cloud on assets | Revenue Cloud on assets |
| Invoice | SAP | SAP | Revenue Cloud Billing, journals to SAP |
Cut 1 fits when the order is a one-off machine sale and everything after the signature is logistics. Salesforce hands over an accepted quote, SAP creates the order.
Cut 2 fits when the same customer keeps buying and changing things: options added later, service packages, subscriptions for remote monitoring. Revenue Cloud then holds the order and the assets, so an amendment starts from what the customer already has. According to Trailhead4, an activated order goes to Dynamic Revenue Orchestrator, which can make a callout to a third-party system. That callout is where SAP gets its order. Details are in handing orders to SAP with Dynamic Revenue Orchestrator.
Cut 3 adds Revenue Cloud Billing5. Salesforce writes that it can “function as a sub-ledger”, powering journal entries, closing periods and currency conversions, and that billing data and journal entries can be synchronised to the ERP. That makes sense for recurring revenue sold in Salesforce. For a machine invoice with delivery, customs and down payments, I would leave the invoice in SAP. The trade-offs are in Revenue Cloud Billing or SAP invoicing.
Who owns which object?
Cutting by process step is not enough. Partners build on objects, so the split has to be written per object as well. This is the same idea as the object ownership matrix, applied to the systems instead of the teams.
| Object | Owner | What crosses the line |
|---|---|---|
| Product2 | SAP or PIM for material number and status; Revenue Cloud for selling attributes and catalog placement | Material number, status, units into Salesforce |
| Pricebook Entry | SAP for list prices | List price per currency, scheduled |
| Customer prices and discounts | One master, SAP conditions or Revenue Cloud pricing | Net price live from SAP, or nothing |
| Quote | Revenue Cloud | Accepted quote to SAP in cut 1 |
| Order | Revenue Cloud in cuts 2 and 3; SAP sales order for delivery | Order to SAP, SAP order number and status back |
| Asset | Revenue Cloud for what was sold and its term | Serial number from SAP or Field Service |
| Invoice | SAP in cuts 1 and 2; Revenue Cloud Billing in cut 3 | Invoice status back, or journal entries to SAP |
The price row causes the most trouble. Two systems that both calculate customer prices will disagree, and the customer will see it when the order confirmation from SAP differs from the quote PDF. Which route fits your conditions is covered in customer prices: SAP conditions or Salesforce Pricing.
What does Revenue Cloud Billing mean for finance?
It means a second accounting structure. The Revenue Management Developer Guide lists the billing objects to deploy6, among them LegalEntity, AccountingPeriod, LegalEntityAccountingPeriod, GeneralLedgerAccount, TaxPolicy and PaymentTerm. Trailhead7 explains that legal entities make sure all billing transactions are related to accounting periods and general ledger accounts.
Every one of these records already exists in SAP. So before cut 3, finance has to decide:
- Which legal entities invoice from Salesforce, and which stay in SAP.
- How Salesforce accounting periods follow the SAP periods, and who closes them.
- How general ledger accounts map, and who changes the mapping when the chart of accounts changes.
- Which invoice format the customer receives. From 2027, according to the IHK Köln8, only companies with prior-year turnover up to €800,000 may still send domestic business customers a PDF with their consent, and from 2028 the e-invoice requirements apply to everyone. What that means for Revenue Cloud is in e-invoicing in Germany from 2027.
If finance has not been in the room for these four points, cut 3 is not ready.
Worked example: machines, spare parts and remote monitoring
A machine builder with SAP S/4HANA sells 40 base machines with options, spare parts and a remote monitoring subscription per machine. Customer prices for spare parts are SAP conditions maintained for years. Machine prices follow list prices plus option surcharges.
I would choose cut 2. Revenue Cloud holds catalog, configuration and quote for machines and subscriptions. Machine prices are calculated in Revenue Cloud on list prices synced from SAP. Spare parts on the same quote get their net price from SAP through an API, because nobody should rebuild those conditions. The activated order goes to SAP with a callout, and the SAP order number comes back. The subscription stays an asset in Salesforce, so renewals and amendments start there. The invoice for machine and subscription comes from SAP in year one. Billing in Salesforce becomes a question only if subscriptions grow into a business of their own.
What the sales desk then needs on top, live order status from SAP for example, follows the pattern in Agentforce and SAP: order status through MuleSoft.
One table with an owner per object
On one page, in a form that a new partner understands in ten minutes:
- Per process step: which system leads, from catalog to cash receipt.
- Per object: owner, as in the table above, plus a named person.
- Per interface: direction, trigger, live or scheduled, and what happens when SAP does not answer.
- Per error: who fixes an order that SAP rejects. Order fallout without an owner ends up with the sales rep, who cannot fix it.
- Sign-off: heads of sales and finance and the IT lead, recorded in the decision log.
Designing these interfaces is a large part of my work on Salesforce integration. The wider decision of whether Revenue Cloud fits at all is in the masterclass chapter Revenue Cloud overview and decision.
Settle the unclear rows with finance
List your quote-to-cash steps in one column and write SAP or Salesforce next to each, as things work today. Then mark the three rows where the answer is unclear: in most companies that is the price, the order and the invoice. Settle those three with finance before you ask partners for estimates, because each answer changes the scope by weeks.
Sources8
- 1use case 3a of the MuleSoft Accelerator for SAP (opens in a new tab)anypoint.mulesoft.com
- 2quote data model (opens in a new tab)developer.salesforce.com
- 3order data model (opens in a new tab)developer.salesforce.com
- 4Trailhead (opens in a new tab)trailhead.salesforce.com
- 5Revenue Cloud Billing (opens in a new tab)salesforce.com
- 6billing objects to deploy (opens in a new tab)developer.salesforce.com
- 7Trailhead (opens in a new tab)trailhead.salesforce.com
- 8IHK Köln (opens in a new tab)ihk.de
Frequently asked questions
Should SAP or Revenue Cloud be the price master?
Exactly one of them. If SAP pricing conditions already hold customer prices and discounts, I keep SAP as the master and fetch the net price for the quote through an API. Revenue Cloud pricing pays off when the logic lives in sales anyway, for example for subscriptions and bundles.
Does Revenue Cloud replace the SAP sales order?
Usually not. Revenue Cloud creates and orchestrates the order in Salesforce, and an integration creates the sales order in SAP for delivery, with the SAP order number written back. The order in SAP stays the basis for delivery and the machine invoice.
Can invoices come from Revenue Cloud Billing while SAP stays the general ledger?
Yes. Salesforce describes Revenue Cloud Billing as a subledger that powers journal entries and closing periods and syncs billing data to the ERP. Finance then has to agree on legal entities, accounting periods and who closes the period.
Is there a Salesforce reference architecture for Revenue Cloud with SAP S/4HANA?
I have not found one. The MuleSoft Accelerator for SAP describes quote to cash with SAP S/4HANA for Sales Cloud and Salesforce CPQ. The pattern carries over, but the design for Revenue Cloud is your partner's work and needs a review on your side.