Dunning Done. DSO Down
Aging trigger → customer segmentation → multi-channel cadence (email/SMS/call) → escalation paths → dispute → legal handoff. The dunning workflow finance teams keep building in spreadsheets, finally pre-wired.
By the numbers
The use case
Dunning runs in Excel. The same email goes to first-time-late and chronic-late. DSO crept from 35 days to 51 days and the AR team is firefighting. Disputes aren't tracked until the customer escalates — then it's too late. Dunning compliance differs per country and the team has one template. Collections is a cost center that's quietly bleeding cash.
Pre-built collections workflow: aging trigger fires the moment a threshold is crossed → customer segmented via Astral (strategic, mid-market, long-tail, chronic-late) → multi-channel cadence kicks in (email, SMS, queued call list) → disputes detected from inbound replies and routed with full context → escalation paths trigger automatically (manager → AR director → legal) → DSO, CEI, and aging surface in real time per entity, per segment. DSO drops 30%. Disputes resolve in days. The AR team stops firefighting.
For who
Capabilities
Workflow fires the moment an invoice crosses an aging threshold — not at the next batch run. 30 / 45 / 60 / 90 day buckets each get their own playbook. First-time-late and chronic-late receive different cadences from day one.
Strategic key account, mid-market, long-tail, and chronic-late accounts all need different tones. Astral segments customers by payment history, deal size, relationship signal, and country — the cadence adapts automatically. No more 'same email to everyone' dunning.
Email-only dunning has hit its limit. Workflow orchestrates email reminders, SMS nudges for mobile-first contacts, and queued call lists for the AR team — with full conversation history captured per customer. Channel choice adapts to country and customer profile.
Customer replies 'this invoice is wrong' — the workflow detects the dispute, opens a case, pauses the cadence, and routes to AR ops with the original invoice, the PO, the delivery proof, and the matching engine's verdict attached. Disputes resolve in days, not the moment they escalate.
Continue exploring
Invoice arrives → AI matches against PO + receipt → policy validation → auto-post if clean, exception queue if not.
Bank statements → AI matches to GL transactions → exception queue for unmatched → escalation rules → close.
Bank statement arrives → remittance data parsed → AI matches against open invoices → exception queue for ambiguous matches → auto-posted to GL.
ISO 27001:2022 · GDPR · EU-hosted · Full audit trails · Trust Center →
Start free. See your first workflow run before the next quarter close.