The whole revenue lifecycle.One package. One data model. Inside Salesforce.
Kugamon Subscription Billing is Quote to Cash and Subscription Management in one managed data model: recurring invoice schedules, a payment terminal with Stripe, Authorize.Net, PayPal and eWay, saved payment profiles, and automated renewals — from $125 per user per month.
Every record is a native Salesforce record.
Kugamon stores quotes, orders, invoices, payments, subscriptions and assets as native objects in your org, on the standard Product and Price Book. Your reports, your permissions, your Agentforce agents see them like any other Salesforce data.
Kugamon Subscription Billing is Quote to Cash and Subscription Management in one managed data model. Quotes, Orders, Shipments, Invoices, Payments, Contracts, Subscriptions, Assets and Renewal Opportunities are all native Salesforce records, created by the same Order Release, related to the same Account. There is no billing system to reconcile against the CRM, because the billing system is the CRM.
That is the point of buying the two halves together. A CPQ that hands off to a separate billing platform has to agree with it about every amendment, every proration, every cancellation — and the agreement is an integration someone maintains. Here the Expansion Order that co-terms a new line to the Contract End Date is the same record that generates the prorated invoice. Cancel the Contract and the Subscriptions deactivate, the Renewal Opportunity closes lost and the invoices are where they always were.
The flow
Opportunity → Quote → Order → Order Release → Contract + Subscriptions + Assets + Shipments + Invoices → Payment → Renewal Opportunity → Renewal Order → Release. The invoice schedule comes from the Account's Additional Account Info record, or an override on the Order; service lines are split by their unit of term into the right number of invoices. Payments are taken on the Invoice through Stripe, Authorize.Net, PayPal or eWay — ACH included — or scheduled as a Recurring Charge. When the renewal Order is released, the next term's invoice is generated and the next Renewal Opportunity created.
What finance gets
ARR, MRR and TCV rolled up on the standard Contract. Invoice Age in days for aging. Applied Payment and Balance Due on every Invoice, and the balance on the Account. Payment status set by the processor, with declines readable by a report or a Flow the moment they happen. Optional Revenue records by month from the Revenue Management add-on. All of it in standard Salesforce reports and dashboards, with field-level security applied on every transaction.
What stays an admin's job
Invoice schedules, payment terms, tax locations and the renewal uplift are records and settings. Whether a product ships, creates an Asset or a Subscription, renews, or uplifts is a field on the product. The renewal emails are Salesforce email templates. Dunning sequences, credit holds and approval routing are Flows on native fields. No Apex is required for standard use.
When it is the wrong edition
If your accounting system already invoices and you only need the renewal engine, Subscription Management is the better fit. If you sell one-time products and services, Quote to Cash covers the billing without the subscription objects. Subscription Billing is the Startup edition (1–200 employees); the pricing page has the full matrix.
What it does, in the order your reps use it.
Both lifecycles, one release
- Releasing a New Order creates the Contract, Subscriptions, Assets, Shipments, Invoices and the future Renewal Opportunity — one data model, so nothing is reconciled between a CPQ and a billing system
- New, Expansion and Renewal record types on Opportunities, Quotes and Orders; expansions co-term and prorate to the Contract End Date
- Un-release and cancel reverse the whole cascade — Contract, Assets, Subscriptions, Invoices — as long as nothing has shipped and no Invoice is posted
Recurring invoice schedules
- Yearly, semi-annual, quarterly, monthly, weekly or daily invoices generated on Order Release, from the account's default schedule or an override on the Order
- Service lines are split by their unit of term, so a three-year subscription invoiced annually creates the right three invoices with the right dates
- Releasing the Renewal Order generates the next term's invoice; Age (days) and Balance Due on every Invoice; Posted locks the Order
Payments, saved payment methods and recurring charges
- Lightning payment terminal on Orders and Invoices with Stripe, Authorize.Net, PayPal and eWay; ACH processed through Authorize.Net eCheck and Stripe ACH Direct Debit
- Saved payment methods per contact with a default — off by default, enabled by Kugamon Support — and one payment applied across many invoices
- Recurring Charges schedule an automated charge against the billing contact's card on any day, at any frequency, for a set number of occurrences, with Cancel, Suspend, Update and Bill-outstanding controls
Collections on native data
- A declined, errored or expired payment is a Salesforce Payment record with the processor's message in the memo, the moment it lands
- Invoice Age (days) is blank until past due, so the aging report is a list view; completed payments apply to the invoice and roll up to the account balance
- Past-due tasks, declined-card alerts and credit-hold rules are Salesforce Flows on those fields — admin work, not an integration
Renewals, uplifts and the numbers finance asks for
- Renewal notices, automated renewal orders and renewal price uplifts on the schedule you set once in Kugamon Settings
- ARR, MRR, subscription count and term dates roll up on the standard Contract; a Kugamon Opportunity Amount field factors term into pipeline
- The optional Revenue Management add-on creates monthly Revenue records from Orders or Invoices for recognition and reporting
We're not the only option, and we don't pretend to be.
Neutral, source-cited comparisons on architecture, cost and time to value — with each competitor's genuine strengths conceded.
Subscription Billing is CPQ plus Billing plus Subscription Management: quotes, orders, shipments, invoice schedules, payments and processor connections, tax, contracts, subscriptions, assets and automated renewals. It is the Startup edition (1–200 employees) for subscription revenue, at $125 per user per month on a 12-month term with annual billing, a 10-user minimum and KugamonCare standard support included.
Subscription Management covers contracts, subscriptions, assets and renewals but does not invoice or take payment. Subscription Billing adds the billing half — invoice schedules, the payment terminal, saved payment methods, recurring charges and tax — in the same data model. The two editions share every object; you are choosing how much of the lifecycle Kugamon runs.
Not as a separate module. Payment status is set by the processor's response and stored on the Payment record with the processor's message; invoices carry a past-due Age field; completed payments roll up to the account balance; and Recurring Charges expose their next payment date and Cancel, Suspend and Update controls. Retry tasks, declined-payment alerts and credit holds are built with Salesforce Flow on those fields, which is standard admin work because the data is native.
Yes. A Recurring Charge, started from an Approved or Released Order, schedules an automated recurring payment against the billing contact's card through the configured processor, on a chosen start day, at a daily, weekly, monthly or yearly frequency, for a set number of occurrences. It is independent of one-time payments, so if a customer pays part of the balance separately, Kugamon recommends canceling and re-creating the Recurring Charge for the updated amount.
For the invoicing, payment and renewal work described on this page, no — it runs inside the same managed package as the quoting. Billing-first platforms remain the better fit for requirements Kugamon does not cover, and the comparison pages say where those lines are, with sources.
The Revenue Management add-on creates Revenue records — one per month of service — either on Order Release or as each Invoice is sent or posted, with an optional separate initial-revenue percentage. Revenue records feed standard Salesforce reports and dashboards, and a Posted/Locked flag prevents the Order from being un-released.
What Salesforce admins say on AppExchange
Quoted verbatim from the Kugamon listing on AppExchange. Reviewer names and dates as published there. Read all 134, including the critical ones →
★★★★★Clear & Intuitive
“The Kugamon team is incredibly responsive and handle support questions very quickly. It’s clear they genuinely value customer feedback and are always innovating.”
★★★★★A new bar for RevOps
“As someone who has set up Salesforce CPQ before, I found Kugamon to be much more straightforward and easier to use. It took us just a few weeks to get going, rather than the few months or even years required by other systems.”
★★★★★Easy to understand, easy to implement
“This SFDC-native platform is lightweight but powerful, bringing the entire sales process onto one pane of glass. No more disconnected Opportunities and Quotes/Orders, no more fractured approval processes, just more control over everything. Implementation is a breeze.”
Configure, price, quote, sign, bill, collect, and renew.
All natively in Salesforce. Deploys in weeks, not months, usually without a systems integrator.