Reconcile Stripe billing with contracted revenue.
Stripe knows what was billed. CRM knows what was sold. SixDegree resolves both claims to the same customer, product, and period without overwriting either source.
What SixDegree reads from Stripe
This page is generated from the connector contract in the SixDegree molecule registry. The entities below reflect the integration implementation, not a generic compatibility claim.
SixDegree reads Stripe customers, subscriptions, products, and invoices. For invoices that includes the amount due, amount paid, status, due date, and linked subscription; for subscriptions, the status, current billing period, trial end, and whether it cancels at the end of the period; for customers, whether they are delinquent.
Billed revenue comes from invoices, not from subscription records, so SixDegree compares what was invoiced and paid with the contracted value in your CRM. Stripe customers are resolved to the same account in Salesforce or HubSpot by shared identifiers such as email domain, and each match is visible.
Customer
A customer in Stripe representing a paying entity
Subscription
A recurring billing subscription in Stripe
Product
A product or service offered in Stripe
Invoice
An invoice in Stripe representing a billing document
Questions it answers with Stripe
- Which accounts were billed less this month than their contracted value in the CRM?
- Which renewals in the next 90 days have a past-due or unpaid invoice?
- Which subscriptions are set to cancel at the end of the period on accounts the CRM still shows as healthy?
- Which customers are delinquent while sales is working an expansion deal?
Use case: contracted ARR versus billed revenue
Finance reports one ARR number and the CRM implies another. The gap is a few percent, and nobody can say which accounts cause it.
SixDegree resolves each Stripe customer to its CRM account and compares closed-won contract value with invoiced and paid amounts. Twelve accounts explain most of the gap: some had seats removed without a CRM update, two have invoices unpaid for over 60 days, and one subscription is set to cancel at period end. Each account comes with the invoice and opportunity records behind it.
Finance and RevOps agree on the definitions once, then watch new gaps as they appear instead of finding them at quarter end. The accounts with quiet seat reductions and unpaid invoices also go to the CSM, because they are renewal risks as much as accounting differences.
Stripe integration FAQ
- Can SixDegree flag renewal risk from billing data?
- Yes. Past-due invoices, delinquent customers, seat reductions, and subscriptions set to cancel at period end are all early renewal signals. SixDegree ties them to the renewal and contract value for the same customer.
- What Stripe data does SixDegree read?
- Customers, subscriptions, products, and invoices, including invoice amounts due and paid, invoice status, subscription status and billing period, cancel-at-period-end, and customer delinquency.
- Can SixDegree reconcile Stripe with Salesforce ARR?
- Yes. It compares invoiced and paid amounts in Stripe with contracted value in Salesforce for the same customer and shows which accounts and invoices explain the difference.
- How are Stripe customers matched to CRM accounts?
- By shared identifiers such as email domain and name, resolved to the same account in Salesforce or HubSpot. Each match stays visible so it can be checked.
- Does SixDegree change anything in Stripe?
- Connections start read-only. The integration includes actions such as creating a customer or cancelling a subscription; whether to use any of them is agreed with your team when production is scoped.