Integration
Where Revenue Cloud stops
ERP, accounting, documents, APIs, migration
The context service is the integration surface that matters: pricing, tax and document generation all read the same definition, so extending it once serves all three. Document generation in particular reuses the pricing context, which removes an entire data-extraction layer that older approaches needed.
Everything else is a boundary decision — what Revenue Cloud owns, and what the ERP or the accounting system owns. Draw it at a record, not at a field.
The architecture
Scroll the diagram sideways
The context service is the integration surface that matters: pricing, tax and document generation all read the same definition, so extending it once serves all three. Document generation in particular reuses the pricing context — which removes an entire data-extraction layer that older approaches needed.
Solution patterns
Document generation on the pricing context
Generate a quote document without building a data-extraction layer, by reusing the context the pricing engine already uses.
IntegrationKeeping the ERP boundary clean
Decide what Revenue Cloud owns and what the ERP owns, before the integration decides for you.