> 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/billing-and-payments/zuora-integration.md). # Zuora **Zuora** is a subscription billing and revenue platform, and one of the billing systems PeakCommerce integrates with natively. Connecting it makes Zuora the system of record for your product catalog, subscriptions, invoices, and payments — while PeakCommerce owns the buying experience that feeds it. ## Why the integration matters Subscription commerce splits naturally in two: the experience a customer moves through (choosing a plan, changing it, cancelling it) and the billing system that has to represent the result correctly for the rest of the business. Wiring those together by hand is where most subscription programs break — a plan change that looks right in the storefront but prorates wrong on the invoice, or a catalog that drifts out of sync between the two systems. PeakCommerce closes that gap. Journeys, storefronts, CSR flows, and the Agent API all commit through the same governed path into Zuora, so a self-service upgrade, a CSR-assisted plan change, and an API-driven order all produce the same billing outcome. ## How the pieces fit * **Catalog** — products and rate plans are synced from Zuora into the PeakCommerce Commerce catalog. A nightly drift watcher compares the two and can resync automatically, so the plans customers see stay true to what Zuora will actually bill. * **Orders and subscriptions** — journey commerce actions (create order, update order, cancel order, record order) commit against Zuora, with proration and change timing governed by your Business Rules rather than hard-coded per flow. * **Custom fields** — values captured during a journey can be written back to Zuora custom fields, so data collected at the point of sale lands on the account, subscription, or order it belongs to. * **Invoices and payments** — invoices and payment records are read back from Zuora to power the customer portal, CSR account timeline, and the Agent API. ## Setting it up Connecting Zuora is one of the provisioning steps for a PeakCommerce production or sandbox tenant. Start with [Zuora Billing Integration](/integrations/billing-and-payments/zuora-integration/zuora-billing-integration.md) for the full connection walkthrough, then check [Supported Zuora Charge Models](/integrations/billing-and-payments/zuora-integration/supported-zuora-charge-models.md) to confirm the charge models in your catalog are ones PeakCommerce can represent. ## In this section * [Zuora Billing Integration](/integrations/billing-and-payments/zuora-integration/zuora-billing-integration.md) — connect a Zuora tenant to PeakCommerce, and the settings that govern how the two stay in sync. * [Supported Zuora Charge Models](/integrations/billing-and-payments/zuora-integration/supported-zuora-charge-models.md) — which Zuora charge models PeakCommerce supports, and the caveats on each. * [Custom Field Sync to Billing Systems](/integrations/billing-and-payments/zuora-integration/custom-field-sync-to-billing-systems-e.g.-zuora.md) — push values captured in a journey into Zuora custom fields. * [Zuora Central Sandbox Refresh](/integrations/billing-and-payments/zuora-integration/zuora-central-sandbox-refresh.md) — what to plan for when your Zuora Central Sandbox is refreshed from production. ## Related * [Billing & Payments overview](/integrations/billing-and-payments/billing-and-payments.md) — the other billing and payment integrations PeakCommerce supports. * [Integrating Billing Systems with PeakCommerce](/integrations/billing-and-payments/integrating-billing-systems-with-peakcommerce.md) — the general shape of a billing integration, if you are not on Zuora. --- # 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/billing-and-payments/zuora-integration.md?ask=&goal= ``` `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.