Open Collections to see who owes you. The Worklist view ranks your overdue and at-risk invoices by a composite score (amount at risk, how late, and how reliably the customer pays) so the account most worth chasing is at the top — not simply the oldest. Each row shows the customer, the open balance, days overdue, a status chip, a recommended next action, and a plain-language confidence note you can expand to see why the row ranks where it does. Switch to the Aging view for the classic Current / 1–30 / 31–60 / 61–90 / 91+ buckets per customer, with DSO and CEI summary tiles.

The score compares every invoice in your workspace's base currency. An invoice that cannot be converted, because it is in another currency with no locked rate or was issued before your workspace changed its base currency, still appears in the worklist: it is shown last, with no risk score, and a line under the list says how many there are.

When you send a reminder — manually from a row's ⋯ menu, or automatically through a dunning sequence — Laureo drafts a tone-appropriate email grounded in the actual invoice, then sends it from the assigned rep's real connected mailbox. The email threads onto the customer's contact and is logged as a normal email activity, so the customer's reply lands on the same thread. You always review and edit a manual reminder before it goes out.

A sequence is an ordered set of escalating steps — for example T+7 (friendly), T+14 (firm), T+30 (final), and a T+60 "call the decision-maker" task. Build and edit sequences in Collections → Sequences. Overdue invoices auto-enroll into your default sequence (you can turn this off in settings). Steps marked requires approval — like a final notice — always wait for a person to review and send, even when auto-send is on.

Auto-enrollment happens once per invoice. When a sequence finishes, that invoice is not enrolled again on its own, so a customer never receives the same ladder twice. To chase it again, select the invoice in the worklist and use Enroll in dunning.

Each email step can carry its own subject and message. Leave either blank and Laureo drafts it for you in the step's tone. When you write your own, five variables are filled in at send time: {{company}} (the customer's company), {{contact_name}} (the person you are writing to), {{invoice_number}}, {{amount}} and {{days_overdue}}. Anything else you type is sent exactly as written, and a variable with no value on that invoice comes out blank rather than guessing. Use Preview on a step to see how it reads with sample values. Editing sequences needs the Manage collections permission.

When a customer says "I'll pay Friday", log a promise-to-pay from the row's menu. This pauses the dunning sequence until the promised date and creates a dated follow-up task for the invoice owner. You're told how many reminders the promise paused, so a mis-keyed date is never silent. If the promise slips, the sequence resumes automatically and the invoice owner is notified; if it's kept, the sequence completes.

In Settings → Company → Collections (managers) you set the aging anchor (count days from the due date or the invoice date), the bucket boundaries (net-60/net-90 tenants widen these), the default dunning sequence, and whether overdue invoices auto-enroll. The worklist and the AR aging report both read these same settings.

In Settings → Company → Collections (managers) you can turn on automatic late fees. When enabled, an overdue invoice gets a Late fee line added once its grace window passes. Choose a percentage of the outstanding balance or a flat amount in the invoice currency, set the grace days (0 to 90) to wait after the due date, and cap how many times a fee can be added to one invoice. The fee is a normal line item, so it shows on the invoice and on the customer's pay page automatically, and the balance updates to include it.