Revenue Cloud Billing or SAP: where should invoices live?

For a manufacturer, the machine invoice should usually stay in SAP, and Revenue Cloud Billing should only create invoices for revenue that is sold and changed in Salesforce: subscriptions, service contracts and usage-based fees. Billing turns Salesforce into a subledger with its own legal entities, accounting periods and journal entries, which are then synchronised to the ERP. That is a second accounting structure next to SAP. It pays off when the recurring business is large and changes often. The decision belongs to finance, and the CRM team prepares it.

What does Revenue Cloud Billing do?

Revenue Cloud Billing is the billing add-on for Revenue Cloud. Salesforce Help and the Winter ’27 developer documentation call the product family Revenue Management, and its earlier name was Revenue Lifecycle Management. According to the product page1, Billing covers:

• Invoices “on any schedule, with traceability to the quote and order”.
• Tax through external tax engines that calculate tax per invoice line.
• Payments across electronic payment methods and gateways.
• Collections, meaning automated follow-up for overdue accounts.
• An accounting subledger for journal entries, closing periods and currency conversion.

The mechanics follow the order. According to Trailhead2, activating an order creates billing schedule groups and billing schedules. Invoice runs pick up the schedules that are ready for invoicing and use the Data Processing Engine for large volumes. Posting an invoice triggers the tax calculation in the external engine. The Billing module on Trailhead3 adds invoice previews, credit memos, payment runs and invoice PDFs that can be emailed to the bill-to contact.

The developer guide4 describes standard objects for billing and tax configuration, credit memos, invoices and “accounting periods for legal entities”, plus payment objects that require the Revenue Cloud Billing licence. The price is on request. How Billing is charged by invoice amount is covered in Revenue Cloud Billing costs.

What does “Salesforce as a subledger” mean for finance?

Salesforce writes that Billing allows “Salesforce to function as a sub-ledger while synchronizing journal entries”. A subledger records the detail of receivables, here every invoice, credit memo and payment, and passes journal entries to the general ledger. The general ledger stays in SAP.

That sounds harmless until you look at the configuration. The list of billing objects to deploy5 starts with LegalEntity and continues with billing policies, tax engines and tax policies, payment terms, AccountingPeriod, LegalEntityAccountingPeriod, GeneralLedgerAccount and rules for journal entries. Trailhead6 puts it plainly: “In Billing, all transactions relate to legal entity records that define how an organization is structured.” Each of these records already exists in SAP, as company codes, fiscal periods and G/L accounts.

So finance has to answer questions it has probably never discussed with the CRM team:

1. Which company codes invoice from Salesforce, and which legal entity records match them?
2. Who closes a Salesforce accounting period, and in which order relative to the SAP period close? According to Trailhead, a Data Processing Engine definition closes the period per legal entity.
3. Who maintains the mapping of general ledger accounts when the chart of accounts changes?
4. How are receivables in Salesforce and in SAP reconciled at month end, and who looks into differences?

Trailhead lists an Accounts Receivable Admin role7 that “manages accounting periods, journal entries, and financial reporting”. In a manufacturing company that person sits in finance. If nobody in finance takes on that role, Billing should not go live.

The machine invoice stays in SAP

For one-off machine sales I keep the invoice in SAP. The reasons are practical:

• Delivery drives the invoice. Machines are invoiced after shipment or acceptance, and shipping, customs and acceptance run in SAP.
• Down payments and milestones are booked against the SAP order. Billing has billing milestone plans in its data model, but moving down payment accounting out of SAP for one product line rarely pays off.
• Cost. Billing is charged by invoice amount. A €2 million machine invoice posted in Salesforce consumes billing events for the full amount, for an invoice SAP could create anyway.
• E-invoicing. From 2027, German companies with more than €800,000 turnover in the previous year must send domestic business customers structured e-invoices. If SAP already produces them, a second invoicing system means a second compliance project. Details are in e-invoicing in Germany from 2027.

The same applies to spare parts that are invoiced with the delivery. Payment in a B2B store is a separate question, covered in B2B checkout: purchase order, card or invoice.

When does Revenue Cloud Billing pay off?

Billing pays off where the invoice follows the contract more than the delivery:

• Subscriptions such as remote monitoring, software options or data services, billed monthly or quarterly.
• Service and maintenance contracts with a fixed fee per period, amended when machines are added or retired. How to bill them is in maintenance contracts with recurring billing.
• Usage-based fees such as machine hours or output, where Revenue Cloud rates the usage and passes it to billing. The machine case is in pay-per-use for machines.
• Frequent amendments. In Revenue Cloud an amendment creates a quote and an order on the existing assets, and the billing schedules follow. If SAP invoices instead, every amendment has to reach SAP through an interface before the next invoice run.

The signal I look for: if sales changes contracts every week and finance corrects invoices every month because SAP did not hear about a change, Billing in Salesforce removes a hand-over. If the recurring business is a few hundred contracts with one invoice a year, invoicing from SAP is usually enough.

Worked example: the split at a machine builder

Assume a machine builder with SAP S/4HANA sells machines, spare parts, a remote monitoring subscription per machine and maintenance contracts. Sales quotes all of it in Revenue Cloud.

I would split it like this:

Revenue	Invoice from	Why
Machine	SAP	Delivery, acceptance, down payments
Spare parts	SAP	Invoiced with the delivery
Remote monitoring subscription	Revenue Cloud Billing	Sold, amended and renewed in Salesforce
Maintenance contract fee	Revenue Cloud Billing	Fixed fee per period, amendments from sales
Usage beyond included hours	Revenue Cloud Billing	Rated in Salesforce

For subscription and contract invoices, Billing creates the journal entries and SAP receives them through the interface:

The customer gets two kinds of invoices, which customer service has to be able to explain. If that is not acceptable, the alternative is to keep every invoice in SAP and send it the billing data from Revenue Cloud, which needs a reliable interface for amendments. Which system owns which object is in Revenue Cloud and SAP: who owns what in quote to cash.

Finance draws the line

Finance. The CRM team can show what Billing does, but finance carries the consequences: a second receivables ledger, a second period close and a second place auditors look at. The object ownership matrix helps here as well: every billing object needs an owner, and for legal entities, accounting periods and general ledger accounts that owner sits in finance.

I would bring the head of accounting into the first architecture workshop, not into user acceptance testing.

The interfaces for journal entries and invoice status are part of my work on Salesforce integration.

List revenue types with their invoice source

List your revenue types and note for each who invoices today and how often the contract changes. Rows with recurring fees and frequent changes are candidates for Billing, everything else stays in SAP. The masterclass chapter billing and usage-based pricing puts this decision into the whole quote-to-cash process.

Sources7

1. 1product page (opens in a new tab)salesforce.com
2. 2Trailhead (opens in a new tab)trailhead.salesforce.com
3. 3Billing module on Trailhead (opens in a new tab)trailhead.salesforce.com
4. 4developer guide (opens in a new tab)developer.salesforce.com
5. 5list of billing objects to deploy (opens in a new tab)developer.salesforce.com
6. 6Trailhead (opens in a new tab)trailhead.salesforce.com
7. 7Accounts Receivable Admin role (opens in a new tab)trailhead.salesforce.com