Salesforce enforces an org-wide limitation of 5,000 external single email message recipients per day. If automated workflows, Apex triggers, or flows attempt to send emails after exceeding this number, the platform blocks the outbound messages and throws a SINGLE_EMAIL_LIMIT_EXCEEDED error.
There's a native platform architecture that removes this bottleneck. Emails triggered from Salesforce and directed explicitly to User IDs (instead of external email text strings or Contact IDs) are routed through a separate internal allocation mechanism. By setting up billing contacts as Experience Cloud portal users, emails with attached invoices can scale to meet high demands.
A Revenue Cloud Billing License is required to generate Invoice PDF documents and send Invoices through Email. This is not included with Revenue Cloud Growth or Revenue Cloud Advanced.
Experience Cloud licenses must be purchased in addition to Revenue Cloud; they are not bundled with Revenue Cloud Billing.
Note on Licensing Costs: If customers will only receive emails, and rarely, or never log in, choose Customer Community Per-Login licenses rather than Per-Member licenses. Per-login licenses cost approximately 2/5th of standard member licensing and can provision 20 users per license seat, dramatically reducing overhead for massive contact lists.
Define Invoice Email Delivery Configuration and Preferences
If you do not want onboarding users to trigger a welcome email:
Navigate to Setup and search for Digital Experiences.
Click All Sites and select Workspaces next to your active portal site.
Click Administration and select Emails.
Uncheck Send welcome email if you do not want consumers to receive portal registration links upon profile creation. This ensures billing contacts only receive operational transactional invoices.
005388195

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.