> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/integrations/crm-and-revops/salesforce-integration/revenue-cloud.md).

# Revenue Cloud

**Salesforce Revenue Cloud** is Salesforce's revenue-lifecycle platform — CPQ (Configure, Price, Quote), billing, and revenue management for sales-led deals. It matters because most enterprises run their quote-to-cash and revenue recognition through a system of record, and self-service commerce has to land in that same lifecycle rather than beside it. PeakCommerce complements Revenue Cloud as the buyer-facing commerce layer, and support is available today and rapidly deepening toward fully native.

## What you can do with it

* **Quote-to-cash continuity** — subscriptions and orders created in PeakCommerce flow into the revenue lifecycle so quoting, billing, and revenue recognition stay in sync with sales-led deals.
* **Shared catalog and pricing alignment** — product and pricing definitions stay consistent between the commerce surface and Revenue Cloud, so a buyer self-serving sees the same plans a rep would quote.
* **One revenue source of truth** — self-service commerce in PeakCommerce and sales-assisted deals in Salesforce land in the same revenue lifecycle, giving finance a single view.

## How it fits

PeakCommerce owns the buyer-facing motion — journeys, carts, checkout, plan changes, and cancellations — while Revenue Cloud owns CPQ and the revenue lifecycle. Commerce activity (new subscriptions, changes, cancellations) is reflected into Salesforce in real time, so the two systems describe the same revenue rather than competing copies of it. Customers keep buying and self-serving through PeakCommerce journeys; finance keeps its lifecycle records authoritative.

## Who and when

Best for organizations standardizing revenue on Salesforce that also want a modern self-service and CSR-assisted commerce experience — without forking pricing or splitting the revenue picture across systems.

## Gotchas

* Treat one system as the catalog/pricing source of truth and keep definitions aligned; divergent pricing between layers is the most common integration pain.
* Map subscription lifecycle events (change, cancel, renewal) deliberately so revenue recognition reflects them.
* PeakCommerce is the commerce surface, not the billing/CPQ engine — Revenue Cloud remains the revenue system of record.

## Related

* [Salesforce Sales Cloud Integration](/integrations/crm-and-revops/salesforce-integration/salesforce-sales-cloud-integration.md)
* [Agentforce](/integrations/crm-and-revops/salesforce-integration/agentforce.md)
* [What Salesforce apps does PeakCommerce natively integrate with?](/integrations/crm-and-revops/salesforce-integration/what-salesforce-apps-does-peakcommerce-natively-integrate-with.md)
* [CRM & RevOps](/integrations/crm-and-revops/crm-and-revops.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/integrations/crm-and-revops/salesforce-integration/revenue-cloud.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.