There is a difference between dunning that happens and dunning that is managed, and you can see it in one artefact: the Monday exception list. In an unmanaged operation, Monday morning brings a dashboard — a recovery rate, a count of past-due accounts, a chart trending vaguely. In a managed one, Monday brings a list of named cases that need a decision: the annual account whose card was replaced but never retried, the cluster of insufficient-funds failures all waiting on the same payday, the three subscribers whose messages have gone unanswered long enough that one more would be noise. Dashboards describe. Exception lists assign.
That artefact is the standard I judge dunning management software judged by its Monday exception list against, because management, as opposed to automation, is precisely the discipline of surfacing the cases the routine could not close and putting them in front of a person while there is still time to change the ending. Software that only automates the routine and hides the residue is not managing anything. It is sweeping, and the pile under the rug is your highest-value accounts, because value and weirdness correlate: the big annual plan fails in a way the $12 monthly never does.
Look at what a real exception list has to contain to be useful. Each case needs its family — timing, credential, information, hard stop — because the decision differs by family. It needs its age and its remaining window, because a case on day three and a case on day twenty-one with the same decline code are different situations wearing the same label. It needs to show what has already been tried, so the human decision is the next step rather than a repeat of the last one. And it needs the amount at stake in plain sight, because an operator triaging twenty cases before coffee should spend the first decision on the $1,200 renewal, not the $12 one.
The other half of management is knowing what the routine already handled and being able to prove it. A managed operation can answer, for any recovered dollar, which step recovered it: a platform retry, a network card refresh, a customer following an update link, a well-timed attempt after payday. That attribution is not bookkeeping vanity. It is how you learn which part of your system earns its keep, and it is the only defence against the blended recovery rate — the number that quietly credits your recovery layer for work your billing platform and your customers did themselves.
Management also means endings. Cases should close for reasons, not by evaporation: recovered, cancelled mid-case and counted honestly as a loss, paused by the subscriber and parked off the scoreboard, or written off at the end of a window long enough for a full pay cycle to have turned. Software that lets cases fade out uncounted will always report a prettier rate than software that counts its losses, and the prettier number is the lie you can least afford, because pricing and staffing decisions get made on it.
If you are choosing tooling, ask for the Monday artefact by name. Show me the exception list. Show me one case end to end, from failure to ending, with every step stamped. Show me the losses. A vendor who can produce those three things is selling management. A vendor who produces only a rate is selling a chart.
That is the operating picture Swipe Again was built to run: decline-aware cases woven around your platform's native attempts, card updates sensed wherever they happen, honest counting with cancellations scored as losses, at $179 a month flat — and a 30-day guarantee judged on total recovery — recover $179 or the next month is free, so the Monday list has to be real.
Top comments (0)