Welcome back to our Salesforce Go for Revenue Cloud series! In Episode 3, Khaled El Halabieh explored high-tech order orchestration using Dynamic Revenue Orchestrator (DRO). In this episode, Khaled shifts the focus from order fulfillment to risk-based Dunning automated payment collection while protecting customer relationships.

What is Dunning?

Dunning is the automated process of managing unpaid, due, or overdue invoices by sending structured reminders and escalations to collect payment.

Most late payments aren't malicious: people forget, credit cards expire, or invoices get mislaid. The skill of effective collection comes down to timing and tone, firm enough to collect outstanding revenue, gentle enough to keep the customer. Rather than treating all delinquent accounts the same, modern Dunning processes balance firm collections with customer retention by segmenting outreach based on risk.

Key Concepts of Dunning

  • Order-to-Cash Context: Dunning is the final stage of the order-to-cash lifecycle. Once a deal becomes an order, billing schedules create invoices. If an invoice remains unpaid past its due date, dunning is initiated to recover the revenue.

  • Preserving Customer Relationships: Most late payments are unintentional, caused by lost invoices, expired credit cards, or minor oversights. Dunning uses progressive reminders (from gentle pre-due emails to formal overdue notices) to collect funds without damaging customer goodwill.

  • Risk-Segmented Journeys: Customers are grouped by risk level (e.g., Low, Medium, High). Lower-risk accounts receive flexible schedules and friendly reminders, while high-risk accounts trigger earlier warnings and faster escalation to collections.

What is the Dunning Orchestration Solution?

Introduced in the Salesforce Go Summer ’26 release, the Dunning Orchestration Solution automates payment reminders ranging from early reminder emails to manual recovery calls. It runs on DRO, the same module we explored in Episode 3.

Streamline Discovery Demos

With DRO and the Dunning Orchestration Solution, it’s easy to show your project stakeholders what automated, risk-based collections look like in action for Revenue Cloud. Using Salesforce Go, you can turn on Dunning Orchestration, install the preconfigured workspace and email templates, and immediately demo an unpaid invoice flowing through segment-based collection paths from early reminder emails to manual recovery calls, all without your team building anything from scratch.

What is included in the Dunning Orchestration Solution?

  • 1 Fulfillment Workspace: Collections Dunning Orchestration Workspace (Usage Type: Billing)

  • 2 Step Groups:

    • High-Risk Accounts: 8 steps, starting 10 days before the due date.

    • Low-Risk and Medium-Risk Accounts: 8 steps on a gentler schedule, starting 5 days before the due date.

  • 16 Step Definitions: Managing delays, automated tasks, and manual tasks.

  • 3 Email Templates: Early Reminder, Invoice Due Notice, and Suspension Notice.

Demo: Dunning Orchestration Solution

In this video, Khaled walks through the end-to-end process of installing the Dunning Orchestration Solution in a sandbox environment, troubleshooting common configuration errors, establishing test data, and executing a live dunning journey on Dynamic Revenue Orchestrator (DRO). 

Whether you’re new to Revenue Cloud, demoing it for the first time, scoping a DRO engagement, or sitting in a discovery session where the customer asks, “How does Salesforce manage late invoices?”, watch this before your next customer meeting.

Grab the slides: Download here

Key Takeaways

Protects Cash Flow & Customer Goodwill: Automates payment reminders and escalations, balancing revenue collection with customer retention by matching outreach tone and frequency to account risk.

Powered Out-of-the-Box by DRO: Runs natively on Salesforce's Dynamic Revenue Orchestrator (DRO), deploying preconfigured workspaces, step definitions, and email templates without building them from scratch..

Automated Risk-Based Journeys: Collection plans route into separate 8-step workflows governed by the Overdue Risk Indicator

  • High-Risk Accounts: Trigger early reminders 10 days before the due date.

  • Low/Medium-Risk Accounts: Begin outreach 5 days before the due date.

Setup & Troubleshooting

Prerequisites: Successful package installation and run-time execution requires the following core steps:

  • Enable Dunning Orchestration in Billing Settings.

  • Turn on Future-Dated Tasks in DRO Settings.

  • Assign essential permission set licenses to the installing user.

  • To execute without errors or silent step skipping, each Collection Plan must have:

    • A designated risk level

    • An assigned contact

    • Linked invoice items

    • Correct user permissions (Submit Transactions and Orchestrate User)

Troubleshooting Installation Issues: Review deployment error logs directly from the Solution Deployment Monitoring page.

Wrapping Up

Here's how we'd use it for a project:

  • Discovery Demo Org: Showing stakeholders how Salesforce automates the management of unpaid, due, or overdue invoices by sending structured reminders and escalations to collect payment.

  • Proof of Concept: Build off of this by:

    • Set Risk Segments Upfront: Decide what Low, Medium, and High mean for your customer base before tuning journey step delays.

    • Make the Emails Yours: Rebrand the three out-of-the-box templates to match your collections team's tone and brand guidelines.

    • Test with Real Plans: Run end-to-end tests in a sandbox using collection plans linked to real items and invoices, then refine step timing.

Note: Remember: do not install it straight into production. There’s no undo.


About the author

Khaled El Halabieh is a Principal Technical Architect at Stratus Carta. He has spent 10 years in the Salesforce ecosystem, working across Revenue Cloud and Steelbrick CPQ (Quote-to-Cash). Before joining Stratus Carta, he spent three years on the Revenue Cloud Practice Lead team at Salesforce, focused on delivery excellence. Connect with Khaled on LinkedIn to talk Revenue Cloud.

About Stratus Carta

Planning a Revenue Cloud rollout, or weighing your move from CPQ? Stratus Carta’s team includes former Salesforce and Vlocity practitioners who work closely with Salesforce product teams. We can help you get from foundation to first quote, and from first quote to a design that fits your business. Reach out to us on LinkedIn.