1. Why value stream mapping matters in credit control
In the realm of debt collection, activity is not the same as progress. A team can make hundreds of calls and send thousands of reminders while cash remains unapplied, disputes wait for an owner, and customers repeat promises they cannot keep.
Value stream mapping makes this end-to-end flow visible. It traces both the work and information: from an account entering an overdue queue through customer contact, dispute or payment-plan decisions, receipt of funds and final cash application. The map shows where value is created, where work waits, and where handoffs or rework extend the time to cash.
The fundamental purpose is to design a reliable process, not simply increase collection pressure. A sound future state should improve recovery while maintaining clear customer communication, appropriate authority and compliance with applicable rules. For an overview of mapping methods, see our guide to creating a detailed process map.
2. Select a focused product family
A useful first scope is B2B trade debt for small and medium enterprise accounts, 60–120 days past due. This defines a comparable family of work without combining early reminders, major enterprise collections and legal recovery into one map.
Set clear boundaries:
- Start: account enters the 60-days-past-due work queue.
- Finish: payment is received, correctly allocated and applied to the account.
- Include: collection activity, customer responses, disputes, approvals, promises-to-pay (PTPs), receipt and cash application.
- Segment or exclude: insolvency, formal legal recovery, unapplied cash unrelated to the selected invoices, and accounts under an approved hold.
Map the actual process with collectors, credit analysts, dispute owners, cash-application staff, sales or account managers, and a process owner. Include systems and queues, not just official procedure.
3. Current state: worked numbers
The following hypothetical baseline represents one month of 400 SME accounts with a combined balance of $4.8 million. Figures are illustrative, not industry benchmarks. Confirm them from local system data before setting targets.
| Measure | Current state |
|---|---|
| Company-wide DSO | 58 days |
| Contact attempts for selected cohort | 2,400; 6 per account |
| Accounts reached at least once | 208; 52% contactability |
| PTP conversion | 73 of 208 reached; 35% |
| Broken promises | 31 of 73; 42% |
| Cohort cash applied within measurement window | $768,000; 16% recovery yield |
| Accounts rolling into the next aging bucket | 28% |
| Lead time, queue entry to cash applied | 24 calendar days |
| Touch time per account | 42 minutes |
| Team workload vs effective capacity | 280 hours vs 300; 93% |
The PTP funnel is calculated as 208 reached × 35% = about 73 promises; about 31 break, leaving about 42 kept. Measure kept promises consistently, for example, full payment by the promised date, with a defined grace period. Track partial payments separately.
The average 42 minutes includes allocated effort across attempts, account research, dispute coordination and cash-application follow-up. Three collectors with 100 productive hours each have 300 hours available; 400 accounts × 42 minutes equals 280 hours of work. At 93% planned capacity, little room remains for spikes or complex cases.
The 24-day lead time can conceal only 42 minutes of direct work. A typical observed path might include a one-day worklist delay, five days to the next reminder, a four-day contact queue, seven days waiting for dispute or authority decisions, six days between PTP and payment, and one day for cash application. Validate stage overlaps and intervals on the actual map. Also record reminder spacing: for example, messages may be scheduled 5, 7 and 10 days apart without responding to customer risk or behavior.
DSO is generally calculated as average accounts receivable divided by credit sales for the period, multiplied by days in the period. It is a company-level outcome; do not treat it as a direct measure of this cohort alone. Pair it with aging migration, recovery yield, dispute time and cash application accuracy.
A clear problem statement
For the 400-account SME trade-debt family at 60–120 days past due, the current process applies $768,000, or 16% of the $4.8 million cohort balance, within the measurement window. Accounts require an average of six contact attempts, 52% are reached at least once, 42% of recorded PTPs break, and cash is applied after an average 24-day lead time. The improvement team will identify and test changes to increase timely cash application and reduce repeat effort, while maintaining customer-care and governance controls.
4. Identify all eight wastes with DOWNTIME
Use DOWNTIME to examine every step:
- Defects: incorrect balances, outdated contacts, misapplied cash or incomplete dispute records create rework.
- Overproduction: duplicate statements or blanket reminders sent when an account already has an active response or dispute.
- Waiting: accounts sit between reminders, in dispute queues, or awaiting approval or payment allocation.
- Non-utilisation of talent: experienced collectors spend time re-keying details instead of resolving blockers.
- Transportation: unnecessary transfers of documents or cases between teams and systems.
- Inventory: overdue accounts, unresolved disputes and unapplied receipts accumulate in queues.
- Motion: staff search multiple screens for contact history, payment status or decision ownership.
- Extra-processing: repeated verification, duplicate data entry and excessive review steps that do not improve decision quality.
Distinguish necessary controls from avoidable delay. An approval checkpoint may protect the organisation, yet unclear thresholds or ownership can turn it into a bottleneck.
5. Build a future state that breaks the repeat-promise cycle
Design the future state around resolving the reason payment has not occurred, not merely generating another reminder.
- Risk-based segmentation: group accounts by balance, days past due, dispute status, customer risk, contactability and prior PTP reliability. Prioritise high-value or high-risk work using transparent rules.
- Right-channel-first contact: test email, phone, portal or other approved channels by segment. Track right-party contact and cash outcomes, not only attempts.
- Standard work for PTPs: record invoice, amount, date, payer, payment method, reason for delay and next action. Define kept, broken and partial promises consistently; schedule follow-up to the commitment.
- Payment-plan authority levels: document who can approve terms and limits. Route exceptions to a named decision-maker with a response-time target.
- Escalation triggers: specify actions for repeated broken promises, unresolved disputes, material balances or risk changes. Escalation should initiate a defined next step, not another unowned queue.
- Automate low-value reminders: use controlled reminders for eligible accounts, suppressing messages when a payment, dispute or customer response is already recorded. Maintain human review for exceptions.
These controls align with DMAIC: define the family and customer requirements, measure the baseline, analyse the causes of broken promises and delay, improve the flow, then control it with owners and a review cadence. A published Lean revenue-cycle case study illustrates how process redesign can improve service performance; its healthcare context and results should not be assumed to predict debt-collection outcomes.
6. Current state vs future state
Targets below are illustrative pilot goals, to be validated against policy, seasonality and baseline data. A DSO change is a directional, company-wide outcome, not a guaranteed result of this cohort project.
| Measure | Current | 90-day pilot goal |
|---|---|---|
| Contact attempts per account | 6 | 4 |
| Contactability | 52% | 65% |
| PTP conversion of reached accounts | 35% | 45% |
| Broken PTP rate | 42% | 25% |
| Recovery yield within window | 16% ($768k) | 22% ($1.056m) |
| Roll rate to next aging bucket | 28% | 18% |
| Lead time | 24 days | 15 days |
| Touch time | 42 min/account | 32 min/account |
| Workload / 300-hour capacity | 280 / 300 hours | 213 / 300 hours |
| Company-wide DSO | 58 days | 52-day directional target |
At 65% contactability, about 260 accounts would be reached. A 45% PTP conversion implies roughly 117 promises; a 25% broken rate means about 29 break and 88 are kept. These are linked measures, not independent guarantees of $1.056 million in collections. Validate realized cash against the cohort balance and measurement window.
7. Sequence kaizen over 90 days
| Timing | Kaizen sequence | Evidence of progress |
|---|---|---|
| Days 1–15 | Confirm scope, definitions and compliance requirements. Validate the current-state map with frontline staff; baseline attempts, reach, PTP and cash data. | Signed scope; verified baseline and operational definitions. |
| Days 16–30 | Analyse broken PTP and queue causes. Segment the cohort; set standard work, approval limits and escalation triggers. | Cause analysis; approved pilot rules and workflow. |
| Days 31–60 | Pilot channel selection, reminder automation and PTP capture with a defined account sample. Review exceptions weekly. | Reach, kept-PTP, cash yield, complaints and cycle-time trends. |
| Days 61–75 | Adjust the pilot from measured results. Confirm workload, system controls and handoffs with collectors and cash application. | Tested countermeasures; documented revisions and ownership. |
| Days 76–90 | Standardise what works, train affected roles and launch a control dashboard with weekly review. | Control plan, process owner, action log and follow-up schedule. |
Teams using SigmaFlow project workspaces can keep the charter, map, measures, actions and control-plan reviews together as project evidence. Keep project governance proportionate: the workspace supports the improvement work; it does not replace operational controls or customer safeguards.
Develop the skills to lead measurable improvement
A well-built value stream mapping project turns a vague collections concern into a visible, measurable flow: from overdue account to correctly applied cash. It gives credit-control teams a disciplined way to test better contact, clearer PTP standards and faster decisions, without mistaking activity for recovery.
Build your capability with CSSC-accredited Lean Six Sigma training, from White Belt through Master Black Belt. Explore our self-paced online courses featuring simulations, dummy data, worked examples and end-to-end case studies, and pursue the certification level suited to your role.
Kaizen. Kai-Care. Kai-Done. Lean Six Sigma
