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.