Collections
Every overdue invoice, prioritized, chased, and logged.
Collections runs on the same finance data as treasury: the invoice, the payment that settles it, and the account behind both are one record instead of three systems. Nobody rebuilds a spreadsheet to see where a customer stands.
Work lists built from live AR data
Each collector opens a queue that is already ordered, not an aging report to triage first. You choose what sets the order: aging bucket, open value, credit risk grade, payment behavior. Managers assign the accounts and set the weighting.
- One queue per collector, rebuilt every morning
- Payment behavior read from real payment history
- Self-queued tasks sit alongside the assigned list
- Next action and amount at stake on every line
Meridian Foods
High priorityGlobex Packaging
High priorityAcme Logistics
Medium priorityYour collections mailbox, inside Nilus
Connect the shared mailbox and every thread lands in Nilus, in both directions, with replies sent from your own address. The AI reads each reply and proposes the action: a dispute for the contested amount, a promise to pay for the rest.
- Nothing is recorded until the collector approves it
- One approval updates account, work list, and audit log
- Reason codes captured from the correspondence
- Internal notes from Slack or Teams land on the account
"We are holding 12,000 of the freight surcharge pending a credit note. The balance is in the Sep 28 payment run."
AI proposed
Logged to the account and the work list once the collector approves.
Reminder policies, escalation, and voice agents
Keep the dunning schedule you run today and layer strategies on top: high-value escalation past 90 days, a referral for legal hold, different treatment for high-risk accounts. Any step can require a human before it goes out.
- Voice agents call customers on your script, recorded
- Calls a person makes are logged the same way
- Templates for reminders, escalations, and tone
- A full audit log behind every strategy
Voice agents cover the call steps; every send is on the audit log.
Disputes, credit exposure, and DSO
Disputes are logged against the invoice, so a collector never chases an amount the customer already questioned. Credit sits beside it, scored in Nilus or pulled from your ERP master data, and the reporting on DSO, aging, and collector performance is built off the same records.
- Exposure, limit, headroom, and utilization per customer
- Promises kept and broken, by account and by collector
- Promised dates feed the 13-week cash forecast
- Status written back to your ERP for teams outside Nilus
Promises kept and collector performance sit on the same data.
The agentic layer
Agents do the work. You make the calls.
Schedule them, or just ask. The agents below work this module continuously, building the position, watching for risk, and surfacing what needs a decision. You come in to review the analysis and approve, instead of assembling it by hand.
Overdue Items
Surfaces every open and overdue item in scope and ranks what to work first.
DSO & Collections
Tracks DSO trends and turns the aging report into a prioritized action list.
Collection Probability
Scores how likely each open item is to be paid on time, from payment history and current signals.
Collections & Dependency Monitor
Watches accounts where a late payment puts something else at risk and raises it early.
Request Invoice Info
Chases the missing invoice or remittance detail needed to get a payment released.
Communication Hub
Keeps every email, call, and internal note against the account in one thread.
See it on your real data in 24 hours.
Connect your real bank accounts. No sandbox, no slide deck: your position, forecast, and idle cash, live.