Salesforce Billing Explained: How to Automate Invoicing and Payments
Salesforce Billing turns orders into invoices, payments and accounting data without retyping them. But "Salesforce Billing" now means two different products, and only one of them is still being developed. This guide explains how each one works, what changed, and how to choose the right billing setup for your business.
Key Takeaways
- "Salesforce Billing" is two products: the original managed package built on Salesforce CPQ, and Billing in Agentforce Revenue Management (sold as Revenue Cloud Billing), which runs on the core platform.
- The managed package is still supported for existing customers, but Salesforce says it gets no new feature development. New billing work happens in Agentforce Revenue Management.
- Neither product has a "create invoice" button. Invoices are generated from activated orders, either on demand or by scheduled invoice runs.
- Payment gateways and tax engines connect through integration packages. Card data stays with the gateway; Salesforce stores a token.
- The ERP usually stays the system of record for the general ledger. Plan the billing-to-ERP handoff before configuring anything.
- Not every company needs Salesforce Billing. ERP-led invoicing, a subscription billing platform, or targeted Flow automation can be a better fit.
Most invoicing problems in a growing company don't come from the invoice. They come from the gap between the deal and the invoice: a closed opportunity retyped into an accounting system, a renewal date tracked in a spreadsheet, a payment nobody in sales can see. Salesforce Billing closes that gap by producing invoices, payments and accounting records directly from Salesforce orders.
This guide is for finance, revenue operations and sales operations leaders at growing and mid-market companies, and it applies equally to enterprise teams. It replaces our 2024 quick guide, because a lot has changed since then: the product line has split, it has been renamed, and the original package is no longer being developed. Every product fact below links to Salesforce's own documentation, so you can check it.
What Is Salesforce Billing?
Salesforce Billing is Salesforce's invoicing, payments and revenue product for orders captured in Salesforce. Today the name covers two products. One is the Salesforce Billing managed package, an add-on to Salesforce CPQ. The other is Billing in Agentforce Revenue Management, which is built into the core platform and sold as Revenue Cloud Billing.
Both do the same basic job. They take an activated order, decide what to bill and when, create invoices, collect and allocate payments, calculate tax, and send the financial results to accounting. Where they differ is architecture, licensing and future direction. Salesforce's Help states that the managed package "inherits key records and information from Salesforce CPQ" and picks up the order "for invoicing, payment, and revenue recognition" (Salesforce Billing overview).
Salesforce Billing (Managed Package)
The original product. It is installed on top of Salesforce CPQ and uses the blng__ namespace. It is available to existing customers, supported, and no longer receiving new features.
Billing in Agentforce Revenue Management
The current product, formerly Revenue Cloud and sold as Revenue Cloud Billing. It is native to the core platform and is where Salesforce now invests in billing.
Is Salesforce Billing Being Discontinued?
The Salesforce Billing managed package isn't being switched off, but it has stopped evolving. Salesforce says it remains available to existing customers, with support for the length of the contract, extra billing blocks and renewals, but no new feature development. Salesforce recommends Billing in Agentforce Revenue Management as the next-generation billing product.
The wording on the Salesforce Billing Help page is worth reading exactly: "The Salesforce Billing managed package continues to be available for existing customers, however, there is no longer any new feature development. We will continue to provide support and services for the duration of your contract. You can also add more billing blocks to your Salesforce org during your current subscription term and renew existing subscriptions."
Salesforce CPQ, which the managed package depends on, has the same status. Salesforce's CPQ end-of-sale page (dated July 10, 2026) says CPQ "is end of sale, not end of life", that "there is no forced migration from Salesforce CPQ to Revenue Cloud", and that new product innovation is focused on Revenue Cloud Advanced and Revenue Cloud Billing.
If you already run the managed package, there is no deadline forcing a move. Keep it stable, fix what hurts, and plan a migration around a natural trigger such as a renewal, a new product line or an acquisition. Salesforce also documents a path to run Salesforce Billing alongside Revenue Cloud during a transition.
If you are buying billing now, evaluate Billing in Agentforce Revenue Management, not the managed package. Expect mixed naming while you do. Trailhead says "Revenue Cloud is now Agentforce Revenue Management", but licences and product pages still say Revenue Cloud Billing and Revenue Cloud Advanced.
Salesforce Billing Managed Package vs Billing in Agentforce Revenue Management
The managed package is a CPQ add-on built from custom objects and rules. Billing in Agentforce Revenue Management is built on standard platform objects, with billing policies, batch schedulers, APIs, collections and Agentforce actions. Both produce invoices from orders. The newer product covers more of the order-to-cash cycle without add-ons, if you hold the right licence.
| Area | Salesforce Billing (managed package) | Billing in Agentforce Revenue Management |
|---|---|---|
| Architecture | Managed package on top of Salesforce CPQ ("Salesforce Billing requires Salesforce CPQ") | Native to the core platform, alongside Revenue Cloud Advanced |
| Status | Supported for existing customers; no new features | Where Salesforce's billing development is focused |
| Billing setup | Billing, tax and revenue recognition rules, each with treatments matched by legal entity | Legal entities, billing policies and treatments, payment terms and billing profiles |
| Invoicing | Bill Now on an order, or an invoice scheduler that creates invoice runs | Invoice batch runs (daily, weekly or monthly), on-demand invoices, and an Invoice Ingestion API |
| Payments | Gateway integration packages, payment runs and the Payment Center | Salesforce Payments objects, payments, refunds and payment promises |
| Collections | Payment runs, plus credit and debit notes | Collection plans and dunning, disputes and write-offs |
| Accounting | Finance books, finance periods and GL rules; ERP stays the system of record | Accounting periods, chart of accounts and automated journal entries |
| Reporting | Tableau dashboards and Finance Logging | Billing Central Dashboard (ARR, MRR, DSO, aging) and the Billing Operations Console |
| AI | None documented | Agentforce actions such as Explain Invoice Line and Get Invoice Document PDF (add-ons required) |
Sources: the Billing in Agentforce Revenue Management overview, the Trailhead billing lifecycle unit and the standard Agentforce actions reference.
Check the licence before you scope. According to Salesforce's Revenue Management licence guide, billing is not available with the Revenue Cloud Growth licence and has "limited features" with Revenue Cloud Advanced. The Revenue Cloud Billing licence is needed for usage-based and milestone invoices, invoice PDFs, emailing invoices, sequential numbering, payments and refunds, collections, write-offs and disputes. Our Revenue Cloud guide covers the editions in more depth.
How Does Salesforce Billing Automate Invoicing?
Salesforce Billing automates invoicing by turning each activated order into a billing schedule, then generating invoices from that schedule automatically. Billing rules decide what is billed and when, tax rules decide what is taxed, and revenue rules decide how revenue is recognised. Payments are then allocated against invoice lines, and the results flow to accounting.
In the managed package, the order is the meeting point: "The order object lives in the CPQ package and acts as the intersection between Salesforce CPQ and Salesforce Billing" (Salesforce Help). Three rules are set on each product and passed down to its order products, and each rule holds treatments that apply by legal entity (prepare your org):
Whether to create an invoice line, and how
Sets the billing frequency, timing (in advance or in arrears) and how the order product becomes invoice lines. An invoice plan handles non-standard intervals, such as one payment ten days after the sale and another two months later.
Whether to apply tax, and which engine calculates it
Points to the internal tax engine or to an external integration such as Avalara or Vertex.
Whether to create a revenue schedule, and how revenue is spread
Sets when the revenue schedule is created and how revenue is distributed. A GL treatment links each transaction to credit and debit GL accounts.
Billing in Agentforce Revenue Management follows the same sequence with different building blocks. Trailhead describes five stages: the quote becomes an order; billing schedules are created automatically when the order is activated; invoices are generated on schedule or on demand; payments are collected by card or bank account; and journal entries are recorded automatically (Trailhead: Get Started with Billing). Schedules can bill monthly, quarterly, semi-annually, annually, by milestone or by usage, and amendments or cancellations create new schedules in the same group.
How Are Invoices Created in Salesforce Billing?
Invoices are created from activated orders, either one order at a time or in scheduled batches. In the managed package you invoice a single order with the Bill Now field, or you automate it with an invoice scheduler that creates invoice runs. In Agentforce Revenue Management you schedule invoice batch runs, invoice on demand, or ingest invoices from another system.
Managed package: Bill Now and invoice runs
blng__Use for: existing CPQ and Billing orgs.
To invoice one order, select Bill Now on an active order and save. Only active orders can be invoiced. The invoice takes the order creation date as its invoice date, its due date comes from the payment terms, and it starts in Draft status so it can be reviewed (invoice an order manually). For volume, an invoice scheduler creates invoice runs. A run groups order products by billing account, then payment terms, then the order's invoice grouping (contract, order, PO number, legal entity, separate invoice or a custom group ID), and it creates a separate invoice for each currency (invoice grouping).
Once an invoice is posted, certain fields can no longer be edited or deleted because, in Salesforce's words, "Salesforce Billing follows Generally Accepted Accounting Principles". To reverse a posted invoice, you cancel it, and Billing creates a credit note for the remaining balance (invoice generation).
Agentforce Revenue Management: batch runs, on demand and APIs
Core platformUse for: new implementations and high-volume invoicing.
The Billing Batch Scheduler runs invoicing daily, weekly or monthly. It has a Run Now option for ad hoc runs, a way to stop the recurrence, and currency selection. Users invoice a single account or order on demand. The Invoice Ingestion API brings invoices created elsewhere into Billing, and other APIs and Flow actions post drafts, void posted invoices, email posted invoices and recover failed runs (invoice APIs and actions). A Default Invoice Template produces a branded PDF that can be emailed to the customer. The PDF requires the Revenue Cloud Billing licence.
One design rule from Salesforce's documentation is worth keeping in mind: automation that runs on generated invoices should be asynchronous, because "synchronous automation in this context can cause performance issues, timeouts, or failures."
Which Payment Gateways Work With Salesforce Billing?
Salesforce Billing processes card and ACH payments through gateway integration packages, not a built-in processor. For the managed package, Salesforce offers integrations for CyberSource, Authorize.Net and Payeezy through your account representative. Other gateways, including those for Stripe or PayPal, come from AppExchange vendors and are supported by them.
Salesforce's payment gateway documentation says that to use a gateway, you "install that gateway's Salesforce Billing integration package into your org". It also says these integrations "aren't available on the AppExchange", and that other gateway apps are found on the AppExchange. Our 2024 guide listed Stripe and PayPal as if they were built in. They are not, so check any third-party gateway package for support, currencies and payment methods before you commit to it.
Tokens, not card numbers
"Neither Salesforce Billing nor the core Salesforce platform store Credit Card Numbers, Personal Account Numbers, CVV, or CVS information." The payment method holds a token from the processor.
Three ways to record payments
AR users enter payments manually, scheduled payment runs charge saved methods, or customers pay in the Payment Center. Payments can also be imported, for example from lockbox files (payments overview).
Invoice locking
During a gateway charge or payment run, Billing locks the invoice until it gets a valid response, so nobody pays twice when the result is uncertain (locked invoices).
Credit and debit notes
Credit notes reduce what is owed on an invoice line; debit notes add to it, for example for a late fee. A posted debit note is corrected with an equal credit note, then reissued.
In Agentforce Revenue Management, payments use the Salesforce Payments objects, such as payment gateway, payment method and payment authorization, which "you can access … with the Revenue Cloud Billing license" (billing payments objects). Payments, refunds, payment promises and collection plans with reminder emails sit in the same product.
How Does Salesforce Billing Calculate Sales Tax and VAT?
Salesforce Billing calculates tax with either its internal engine or an external tax engine such as Avalara or Vertex. Tax on a quote or order is an estimate; Billing performs the final calculation on the invoice. The internal engine suits lightweight needs. Multi-state, multi-country or VAT and GST obligations usually call for an external engine.
Salesforce's CPQ and Billing tax comparison lists the options and limits: an external engine "like Avalara or Vertex", a custom integration, or the internal engine. External engines ignore unposted transactions, and Avalara can calculate tax for up to 2,200 invoice lines. Setting up an external engine means creating a tax integration, an active tax rule and a tax treatment that points to it, then installing the provider's package (tax setup). Avalara publishes Avalara for Salesforce Billing on the AppExchange as a paid app.
One sentence in that setup guide should shape your support plan: "Salesforce Billing doesn't own support for external tax calculation services or their Salesforce packages." Tax issues go to the tax vendor, so make sure your contract and runbook say so.
Does Salesforce Billing Handle Revenue Recognition and Replace the ERP?
Salesforce Billing creates revenue schedules and GL-ready transactions, but it is designed to work with an ERP, not replace one. Salesforce describes the managed package as complementing ERP platforms and upholding "the ERP as the system of record for GL and financial reporting". Billing owns customer-facing finance; the ERP owns the books.
In the managed package, revenue recognition rules decide whether an invoiced order product gets a revenue schedule (revenue recognition rules). Finance books group transactions by accounting or revenue period. Salesforce's example is a revenue book that tracks ASC 606 revenue each month. Finance periods control what can still be posted: "Only open periods receive transactions", and closing a period stops new ones (finance periods). Invoice lines, payments and adjustments are then passed to the ERP for reporting and revenue recognition.
Agentforce Revenue Management adds accounting periods, a chart of accounts and automated journal entries that "capture revenue, taxes, credits, and liabilities". Salesforce's Revenue Cloud page says the product supports ASC 606 and IFRS 15 compliance and that billing data flows into your ERP. In practice, decide early which system issues the invoice number, which one owns the customer's balance, and how often the two are reconciled. If NetSuite is your ERP, our Salesforce NetSuite billing integration page explains one common split.
Can Salesforce Billing Handle Usage-Based Pricing?
Yes. Both products bill for consumption, but usage data usually starts outside Salesforce. Your platform or a mediation system counts the usage; Salesforce Billing rates it against the contracted price and invoices it, typically in arrears. Plan the usage feed, its timing and its error handling as carefully as the pricing.
In the managed package, usage products are order products with a Charge Type of Usage. Usage records are grouped into usage summaries for invoicing, and Help notes that aggregation is "usually" done by third parties (usage in Salesforce Billing). Two rating methods exist: On Trigger and By Process, and Salesforce recommends By Process for large, range-priced volumes. One constraint surprises teams: with consumption schedules "you can't amend to increase quantity. You can only cancel." In Agentforce Revenue Management, usage-based invoices need the Revenue Cloud Billing licence, and the Revenue Cloud Billing page describes a digital wallet for prepaid, virtual-currency and rollover consumption models.
Do You Need Salesforce Billing, or Another Billing Setup?
You need Salesforce Billing when sales, contracts and billing must share one data model inside Salesforce, especially with subscriptions, amendments and usage. If finance already invoices well from an ERP or a billing platform, connecting that system to Salesforce is often cheaper and faster. Simple invoicing can be automated with Flow or Apex alone.
Answer these questions in order. The first "yes" is usually the right starting point:
How Do You Implement Salesforce Billing Step by Step?
Implement Salesforce Billing in this order: decide which system owns each stage of quote-to-cash, confirm licences, model legal entities and billing policies, connect tax and payments, set up invoice runs and templates, integrate the ERP, then test with real scenarios. Configuration is the easy part; design decisions take most of the time.
- 1
Map quote-to-cash and name a system of record per stage. Pricing, contract, invoice, payment, revenue and GL each need one owner. Write down where the invoice number and the customer balance live.
- 2
Confirm licences and prerequisites. The managed package needs Salesforce CPQ at the same release. In Agentforce Revenue Management, check what the Revenue Cloud Advanced licence covers before assuming you need, or don't need, the Billing licence.
- 3
Model legal entities, policies and periods. Set up legal entities, billing policies and treatments, payment terms, billing profiles and accounting periods. Trailhead's setup steps start with turning Billing on, assigning permission sets and creating a default legal entity (Set Up Billing Basics).
- 4
Connect the tax engine and payment gateway. Install and test the vendor packages in a sandbox, including failure responses and refunds.
- 5
Configure invoicing. Set up the invoice template, numbering, grouping, the batch schedule and who reviews draft invoices before they are posted.
- 6
Integrate the ERP and payment status. Decide what flows to the ERP (invoice lines, payments, journal entries) and what flows back to sales (payment status, aging, credit holds).
- 7
Test real scenarios, then run in parallel. Test upgrades, downgrades, cancellations, co-terming, multi-currency and usage. Then run one billing cycle alongside the old process and reconcile every invoice before switching over.
What Are the Most Common Salesforce Billing Mistakes?
Most Salesforce Billing problems come from treating it as a reporting add-on instead of a financial system. Posted records are locked, periods close, scheduled jobs keep running, and tax and payment vendors own their own support. Teams that design for those rules avoid most incidents. These are the mistakes we see most often:
How Twopir Consulting Helps With Salesforce Invoicing and Billing
Twopir Consulting designs the quote-to-cash architecture first, then builds whichever billing setup fits it: Salesforce billing, ERP-led invoicing, a subscription billing platform, or targeted automation. We implement, rescue, optimize, and integrate complex CRM and revenue systems, and billing is where CRM and finance meet.
Our published case studies show the range:
Automated invoicing from quotes
For a US mid-market manufacturer, a bulk-safe Batch Apex engine creates invoices from approved quotes on weekly, monthly and bi-monthly cycles, with duplicate prevention. Read the case study.
Salesforce to QuickBooks invoicing
For a US and Canadian SaaS company, one-click invoices from opportunities are routed by currency to two QuickBooks companies, with payment status synced back. Read the case study.
Stripe invoices and payment status
Record-triggered flows create and finalise Stripe invoices from opportunities and update payment status through webhooks, with 30-day reminders. It was built without custom Apex. Read the case study.
Quote-to-cash with Chargebee
For a US SaaS company, Salesforce, Chargebee and PandaDoc became one workflow. Post-signature invoicing and subscription creation are automated without custom middleware. Read the case study.
The common thread is the architecture decision, not the tool: one system of record per stage, no retyping between systems, and payment status visible to the people who own the customer. If you run a subscription business, our Salesforce for SaaS and revenue operations services cover the wider revenue system around billing.
The Bottom Line on Salesforce Billing
Salesforce Billing can remove most manual invoicing work, but only once you know which product you are on and which system owns each stage. Existing managed-package customers can keep running and improving it. New buyers should evaluate Billing in Agentforce Revenue Management, and should also consider whether an ERP or billing platform already does the job.
- 1
Confirm which "Salesforce Billing" you have, or are buying, and what your licence includes.
- 2
Name a system of record for pricing, invoices, payments, revenue and the general ledger.
- 3
Invoice from activated orders with scheduled runs, and review drafts before posting.
- 4
Use vendor packages for gateways and tax, and agree who supports them.
- 5
Give one person ownership of invoice-run monitoring and the monthly period close.
Get a Clear Quote-to-Cash Plan
On a 30-minute discovery call, a Twopir consultant will review how deals become invoices and cash today, and recommend whether Salesforce billing, an ERP integration or targeted automation fits best.
Schedule a Discovery CallFrequently Asked Questions
Not discontinued, but frozen. Salesforce says the Salesforce Billing managed package remains available to existing customers, who can renew and add billing blocks, with support for the length of their contract. There is no new feature development. Salesforce recommends Billing in Agentforce Revenue Management, sold as Revenue Cloud Billing, as its next-generation billing product.
For the managed package, yes. Salesforce Help states that Salesforce Billing requires Salesforce CPQ, ideally on the same release, because Billing picks up CPQ orders for invoicing. Billing in Agentforce Revenue Management is different: it runs on the core platform and works with Revenue Cloud Advanced rather than the CPQ managed package.
Salesforce Billing usually means the older managed package built on Salesforce CPQ. Revenue Cloud Billing is the licence for Billing in Agentforce Revenue Management, the newer product built into the core platform. It adds billing policies, batch scheduling, invoice APIs, collections, disputes, journal entries and Agentforce actions, and it is where Salesforce now develops billing.
The managed package connects to gateways through integration packages. Salesforce offers CyberSource, Authorize.Net and Payeezy integrations through your account representative, and other gateways come from AppExchange vendors. Billing in Agentforce Revenue Management uses Salesforce Payments objects. In both, card details stay with the gateway and Salesforce stores a token.
Yes. It can use an internal engine for lightweight tax, or an external engine such as Avalara or Vertex through the provider's package. Tax on quotes and orders is an estimate; the final calculation happens on the invoice. Salesforce notes it doesn't own support for external tax services, so the tax vendor supports them.
No. Salesforce Billing handles customer-facing finance: invoices, payments, credit notes and revenue schedules. Salesforce positions the ERP as the system of record for the general ledger and financial reporting, and Billing passes invoice lines, payments and journal data to it. Most companies keep their ERP and integrate the two.
Salesforce doesn't publish a list price for Revenue Cloud Billing; its product page offers pricing on request. Total cost also depends on the licence mix (Revenue Cloud Advanced, Revenue Cloud Billing and any Agentforce add-ons), on gateway and tax packages, and on implementation and ERP integration work. Get a scoped estimate before committing.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems on Salesforce and HubSpot, including quote-to-cash, billing and accounting integrations.