Results, Analytics and Automation
Three pages answer three different questions. Results answers “are we winning?” for a manager or a customer. Credit Control Analytics answers “what exactly is happening?” for the person running the function. Automation answers “what did the machine do last night?”
All three respect your Team or Mine scope, and hide figures your permissions do not cover rather than showing you a wrong number.
Results
Section titled “Results”Results tells the exposure-to-outcome story with no tables at all.
Filter: the period - last 90 days, 6 months, 12 months (the default) or all history - and the currency where you have more than one.
Hero cards:
| Card | Meaning |
|---|---|
| Recovered | Debt paid on or after the first chase contact |
| Settled without contact | Items that cleared before chasing reached them |
| Overdue exposure now | The live collectible position |
| Recovery rate | Recovered items as a share of the total |
| Median days to recover | From enrolment to recovery |
| Promises kept | Kept against broken. Amber below half |
Charts and panels: enrolled against recovered by month; aged debt now; how fast recoveries land (within 7, 14 and 30 days); contact effort by channel and outcome; and an outcome mix showing recovered, settled without contact, still open, escalated, written off and excluded as one bar.
Two things to understand about the period:
- It selects debt items by when they entered chasing, not by when they were paid.
- Overdue exposure now ignores the period entirely. It is always the live figure, because a current exposure number for “last September” would be meaningless.
Full numbers links through to the analytics page carrying your period.
Credit Control Analytics
Section titled “Credit Control Analytics”The management view: exposure, the stage funnel, timings, outcomes, contact effort, operational controls and late-payment charges.
Filters: Team or Mine, currency, pipeline, safeguard class, the window (opened in the last 90 days, 6 months, 12 months or any time) and the breakdown dimension (by safeguard class, pipeline, owner or outcome). Download CSV exports it.
Exposure cards: gross overdue exposure before pending credits; pending refund credits; raised credit-note offsets; collectible overdue exposure after those credits; how much sits below the policy minimum; and how much has an action due.
Performance cards: recovery rate, settled without contact, median days to recover, pre-handoff recoveries and late handoff.
Panels:
- Stage reach and roll-forward - how many items reached each stage, how many were recovered or settled there, and how many moved on. Stage reach comes only from recorded events; a skipped stage is never inferred.
- Time in stage - median days, with contact-blocking hold periods excluded and overlapping holds counted once.
- Recovery cohorts - within 7, 14 and 30 days. Each window only includes items old enough to have reached that horizon, so the figures are comparable.
- Outcomes and a management breakdown by your chosen dimension.
- Communications - what was sent, by channel and outcome.
- Operational controls - customer service changes, holds, arrangements and restriction reviews.
- Late-payment charges - assessments, fixed fees, interest and the total.
Live figures versus period figures: current exposure and open control queues are always live and ignore the period. Cohorts use the date the debt item opened; communications and controls use their own event date.
When something is hidden, the page says so rather than showing a blank: financial totals need invoice list access, stage history needs chase activity access, and hold, arrangement and review metrics follow their own list permissions.
Automation
Section titled “Automation”Automation is the audit trail of the daily Credit Control run.
Filters: which run (the last 14, each labelled with its date and whether it succeeded) and the outcome - all items, processed, blocked, skipped or errors.
The run line tells you when it started, who released it and when (or that it released automatically at the forced hour, or is still awaiting release), and when it finished.
Cards: cases enrolled, correspondence queued, manual tasks created for the Chase Run, items closed as paid, items blocked and errors.
Automated correspondence breaks the queued sends down by channel: sent and delivered, pending, awaiting approval, and blocked or failed. Operator batch sends are deliberately excluded, because this panel is about what the machine did.
Payment reminders covers the customer notifications queued for the run date - invoice issued, invoice due, expected payment due, payment promise due, card collection due, Direct Debit collection due and auto-topup - with emails sent, SMS sent, pending and failed or suppressed.
The item log lists each thing the run touched: the customer (or Run level for a run-wide item), the chase case, the type of work, the outcome and the detail. Errors are listed first, then blocked, then skipped.
Things to know:
- Run-level rows, such as reconciliation and run-wide errors, are shown only to operators with Credit Control team scope. Case-linked rows follow your normal account access.
- The page is read-only. Everything on it has already happened.
- The Sales side has its own Automation page.