Numbers finance can sign off on.Because they live where the sale was recorded.
Finance usually meets the CPQ at month end, as an export that does not tie out. Kugamon is built so the invoice comes from the same Order the rep released, the payment is applied to that invoice, the subscription rolls up to the Contract, and the revenue record is created from one of them — all in Salesforce, all reportable, all dated.
In Kugamon the invoice is generated from the released Order, the payment is applied to the invoice, the subscription rolls up to the standard Salesforce Contract, and the Revenue Management add-on writes monthly Revenue records from the Order or the Invoice. Nothing is exported to be reconciled later, and every step stamps a date finance can audit.
Roll-ups on the Contract, not in a spreadsheet
ARR that lives in a spreadsheet is a snapshot; ARR that lives on the Contract is a fact. With the Subscription Management add-on, releasing a New Order creates a Contract — Salesforce's standard object — as the container for everything that follows: the Subscriptions created from the service lines, the Assets created from the product lines, the contributing Orders, and the next Renewal Opportunity. The Contract carries the roll-ups finance asks for — ARR, MRR and TCV, subscription count, total quantity, start and end dates — and a Duration field that shows how long the account has been a customer.
Expansions co-term to the Contract End Date and update the same Contract. Renewals extend it or, if you prefer, create a new one. Because the roll-up is a field on a Salesforce record, it appears in the report, the dashboard and the forecast without a step in between. Kugamon also adds an Opportunity Amount field that factors the service term into the calculation, because the standard Amount field does not.
Invoices from the Order, payments applied to the invoice
Releasing an Order creates its invoices on the schedule set for the account — One-Time, Yearly, Semi-Annual, Quarterly, Monthly, Weekly or Daily — with the service lines split by unit of term so a 12-month subscription invoiced monthly produces twelve invoices with the right dates. Each invoice carries line subtotal, discounts, additional charges and credits, tax and VAT/GST, Net Amount, Applied Payment Amount and Balance Due Amount. Once past due, an Age field shows the days.
Payments are taken against Approved or Released Orders and Unsent or Sent Invoices, through Stripe, Authorize.Net, PayPal or eWay, or recorded manually for wire and check. One payment can be applied to many invoices. Completed payments apply to the balance; voids and refunds un-apply it and are communicated to the processor. Account-level balance roll-ups give receivables by customer without a report you have to build.
| Event | What finance gets |
|---|---|
| Order approved | Assets created with purchase price and date |
| Order released | Invoices on the account's schedule; Contract, Subscriptions and Renewal Opportunity with the add-on; Revenue records if set to release |
| Invoice sent | Date Sent; online invoice with checkout; Age once past due |
| Payment completed | Applied Payment Amount and Balance Due updated; processor status on the Payment record |
| Invoice posted | Date Posted; Order can no longer be un-released |
| Contract active | ARR, MRR, subscription count and dates rolled up |
Revenue recognition with the Revenue Management add-on
The Revenue Management add-on creates monthly Revenue records at one of three events you choose in Kugamon Settings: Order Release, Invoice Sent or Invoice Posted. A three-year order invoiced annually creates 36 monthly records on release, or 12 as each yearly invoice is processed. Products, one-time services, subscription services and additional charges are each set to create revenue per record, and a subscription can recognize a larger share in its first month if that is your policy. A Posted/Locked flag on the Revenue record prevents edits and prevents the Order from being un-released. Reports for revenue by Order and by Account over time ship in the Kugamon report folder.
Be clear about what this is. It is a recognition and reporting layer that gives finance monthly revenue rows inside Salesforce. It is not a revenue subledger: it does not automate the five-step ASC 606 or IFRS 15 model or allocate standalone selling prices. Companies that need that use Zuora Revenue or their ERP, and the Zuora comparison says so plainly.
Reports, dashboards and the audit trail
Every Kugamon object carries a Record Status field intended as the basis for reports and dashboards, and every status change stamps a date: Date Sent, Date Approved, Date Released, Date Posted, Date Cancelled. Because Quotes, Orders, Invoices, Payments, Subscriptions and Revenue are objects in your own org, Salesforce field history tracking, sharing rules and field-level security apply to them exactly as they do to an Opportunity — nothing is held in a second system with a different permission model. The security page covers the controls.
Two rules keep the books clean. An Order with a Posted invoice or a shipped shipment cannot be un-released. And a cancelled Contract deactivates its subscriptions and closes the renewal opportunity as lost while leaving the subscription lines in place, so churn can be reported rather than erased.
“Compared Kugamon to Zuora and it was a no-brainer.”
When Kugamon is not the right choice
If revenue is usage-metered at very high volume, you need a rating engine and Kugamon does not include one. If finance needs a subledger that automates ASC 606 with SSP allocation, or multi-entity billing with e-invoicing and tax compliance across many countries, Zuora is built for that and Kugamon is not. Kugamon is also not a general ledger: it produces the invoice, the payment and the revenue row, and your accounting system books them.
If your business is subscription or one-time sales on Salesforce and the problem is that the invoice, the payment and the ARR number live in three places, the Subscription Billing edition puts them on one record. The business case is written for the CFO who has to approve it.
From the standard Salesforce Contract. With the Subscription Management add-on, releasing a New Order creates a Contract that acts as the container for its Subscriptions, Assets, contributing Orders and the next Renewal Opportunity, and the Contract carries roll-ups for ARR, MRR, subscription count, total quantity and start and end dates. Expansions and renewals update the same Contract, so the roll-up is always the current view.
Invoices are created when an Order is released, on the invoice schedule set for the account — One-Time, Yearly, Semi-Annual, Quarterly, Monthly, Weekly or Daily. Each invoice carries Invoice Date, Due Date, Age in days once past due, Applied Payment Amount and Balance Due Amount. Posting an invoice records it as booked and prevents the related Order from being un-released.
The Revenue Management add-on creates monthly Revenue records from Orders on release or from Invoices when they are sent or posted — a three-year order invoiced annually creates 36 monthly records on release, or 12 as each invoice is processed — and those records feed standard reports and dashboards. It is a recognition and reporting layer, not a revenue subledger; it does not automate the five-step ASC 606 model or allocate standalone selling prices.
Every transaction object stamps its own dates — Date Sent, Date Approved, Date Released, Date Posted, Date Cancelled — and the Posted flag locks an invoice against un-release. Because Quotes, Orders, Invoices, Payments and Revenue are objects in your Salesforce org, Salesforce field history tracking, sharing rules and field-level security apply to them exactly as they do to an Opportunity.
When revenue is usage-metered at very high volume and needs a rating engine, when you need a finance-owned ASC 606 subledger with SSP allocation, or when you run multi-entity global billing with e-invoicing mandates — Zuora is built for those and Kugamon is not. Kugamon is also not a general ledger; it feeds your accounting system rather than standing in for it.
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 →
★★★★★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.”
★★★★★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.”
Configure, price, quote, sign, bill, collect, and renew.
All natively in Salesforce. Deploys in weeks, not months, usually without a systems integrator.