Invoice
An Invoice in Salesforce is a record representing a billing document sent to a customer for goods or services delivered.
Definition
An Invoice in Salesforce is a record representing a billing document sent to a customer for goods or services delivered. The platform supports invoices in several products: Salesforce Billing (now part of Revenue Cloud) for subscription-billing scenarios, Salesforce Order Management for B2C and B2B retail flows, Financial Services Cloud for advisor-billing scenarios, and Industries-specific implementations (Health Cloud patient billing, Communications Cloud subscriber billing). Each product layers its own data model on top of the standard Invoice and Invoice Line objects, but the core concept is the same: a periodic billing document driven by underlying Orders, Order Products, and pricing rules.
The Invoice object stores the invoice number, the billing account, the invoice date, the due date, the total amount, the tax, and the status (Draft, Posted, Paid, Cancelled). Invoice Lines store the line-by-line breakdown linked to Order Products, Subscriptions, or other source records. Most enterprise Salesforce orgs do not generate the invoice itself in Salesforce; they integrate with an ERP or billing system (NetSuite, SAP, Workday, Stripe Billing) that produces the invoice and writes it back to Salesforce for visibility. Revenue Cloud customers do generate invoices natively in Salesforce.
How Invoice fits into the Salesforce revenue lifecycle
The Order-to-Invoice flow
The canonical lifecycle: an Opportunity closes-won, an Order is generated (typically via Generate Orders in CPQ), the Order activates, and the billing process generates an Invoice for the period. The Invoice references the source Order, and each Invoice Line references an Order Product. The chain preserves traceability from sale to bill, which is essential for financial audit.
Salesforce Billing and Revenue Cloud
Salesforce Billing (the SteelBrick Billing acquisition, now part of Revenue Cloud) is the Salesforce-native invoice generation product. It supports subscription billing, prorated charges, evergreen contracts, and revenue recognition. Customers running Revenue Cloud generate invoices entirely in Salesforce; everyone else integrates with an external billing or ERP system.
External ERP integration as the common pattern
Most large enterprises do not bill in Salesforce. They bill in NetSuite, SAP, Workday, or a homegrown ERP. The integration is bidirectional: Salesforce pushes Orders to the ERP; the ERP generates the Invoice; the Invoice and its status (Paid, Overdue) push back to Salesforce for visibility. The integration runs via MuleSoft, custom Apex, or the Salesforce Connect platform.
Invoice status lifecycle
Invoices move through statuses: Draft (created, not yet sent), Posted (sent to the customer), Paid (full payment received), Partial Payment (some payment received), Overdue (past due date with balance), Disputed, Cancelled. Status transitions trigger downstream automation: send the invoice email when Posted, escalate to collections when Overdue, recognize revenue when Paid.
Revenue recognition
For subscription businesses, the Invoice connects to revenue recognition. Each Invoice Line generates Revenue Schedule entries that recognize revenue over the appropriate period (one month, one quarter, the full contract). ASC 606 and IFRS 15 compliance depend on this allocation. Revenue Cloud automates the calculation; external integrations require careful design to preserve the recognition trail.
Tax calculation
Invoices require tax. Salesforce integrates with tax engines (Avalara, Vertex, Sovos) that calculate taxes per line based on jurisdiction, product type, and customer status. The tax engine writes back to the Invoice as a separate line or as a tax amount on each Invoice Line. Without an integrated tax engine, the carrier or finance team enters tax manually, which is unsustainable at scale.
Payment processing integration
Invoices link to payment processing. Stripe, Adyen, Braintree, and customer-internal payment gateways integrate via MuleSoft or AppExchange packages. The integration captures payment events (authorized, captured, refunded) and updates Invoice status accordingly. For SaaS businesses, the payment-processor link is often the source of truth for Invoice Paid status.
Design the Invoice integration for an enterprise org
Most orgs do not generate invoices in Salesforce. The work is integration design between Salesforce and the billing system of record.
- Identify the system of record
Is Salesforce the source of truth for invoices, or is ERP? Most large enterprises put ERP in this role; SaaS startups often put Salesforce (via Revenue Cloud).
- Design the bidirectional integration
Orders flow from Salesforce to ERP. Invoices and payment status flow back. Pick MuleSoft or a custom Apex integration. Define the data mapping per field.
- Configure tax engine integration
Stand up Avalara, Vertex, or Sovos. Configure the API connection, the tax-code mapping, and the per-line tax calculation flow.
- Configure payment processing
Stand up Stripe, Adyen, or the org''s gateway. Configure the webhook from the gateway to Salesforce to update Invoice status on payment events.
- Build the customer-facing portal
Surface invoices to customers via an Experience Cloud customer portal. Let them view, download PDF, and pay online.
- Build collections automation
Schedule-triggered flows that surface overdue invoices, generate dunning emails, escalate to collections. Most orgs build this in Salesforce regardless of where invoices originate.
- Most enterprises do not bill in Salesforce. Designing a Salesforce-native invoice model when the ERP is the system of record creates duplicate data and integration confusion.
- Tax calculation at scale requires a dedicated tax engine. Manual tax entry breaks at any meaningful volume and produces audit findings.
- Payment-status updates need a webhook from the payment processor. Polling-based updates lag, causing overdue notifications to fire after the customer has already paid.
- Revenue recognition is regulated (ASC 606, IFRS 15). The Invoice and Revenue Schedule design must align with the org''s accounting policy; involve finance early.
Trust & references
Cross-checked against the following references.
- Salesforce Billing OverviewSalesforce Help
- Revenue Cloud OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Invoice.
- Invoice Standard ObjectSalesforce Developers
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is an Invoice in Salesforce?
Q2. Where do invoices fit in quote-to-cash?
Q3. What product handles native invoicing in Salesforce?
Discussion
Loading discussion…