Collections that know the whole account

Nobody wants to chase a customer who already promised to pay, or one in the middle of a dispute. duebird watches every open invoice, reads the whole account before it writes, and drafts the follow-up a careful person would send.

Messages / Drafts
To: Dana Ruiz, Accounts Payable · Northline SupplyRe: Invoice INV-00377

Hi Dana, a quick note on INV-00377 for the March service visits, now 14 days past due. I've attached the invoice and the signed work orders again. Could you let me know when it's scheduled?

Drafted by duebirdSendEdit
INV-00385 is disputed, so it is left out

How it runs

From an invoice going late to the money arriving

  1. 01

    Every open invoice is watched

    Several times a day duebird checks each customer with money out for anything new: an invoice coming due, one crossing a days-late mark, a promise broken, or the customer writing back about an invoice.

    Due within three days1, 7, 14, 30, 45 and 60 days lateEach moment looked at once

  2. 02

    It reads the whole position

    Before writing anything, duebird reads every open invoice with its balance, the promises and disputes, the emails already exchanged, the reminders already sent and how this customer usually pays.

    No reminder for a disputed invoiceNo reminder for a promise still in dateOne message can cover several invoices

  3. 03

    The follow-up is drafted, not sent

    The draft lands in your mailbox, in the right thread, to the right contact, with the invoice attached. It says it was drafted by duebird and what to check. You edit if you like and press Send.

    Sent from your own mailbox or your company addressThe customer's tone and history taken into accountNothing goes out unattended

  4. 04

    Replies become records

    When the customer answers, duebird reads the reply and proposes what it means: a promise to pay by a date, a dispute about an invoice, a new AP contact. You confirm it once, and the next follow-up respects it.

  5. 05

    The right accounts get a call

    A customer 30 or more days overdue, with no dispute and no promise in date, is put on your list of people somebody should call. Drafts that are no longer needed (paid, cancelled, disputed or promised) are withdrawn by themselves.

What it handles

Receivables, without the chasing spreadsheet

Context-aware drafts

Each follow-up is written from the customer's position and history, in the thread where the conversation already is.

in-threadmulti-invoice

Promises to pay

Recorded from replies, checked against what arrives, kept when paid in full and marked broken the day after they lapse.

promise tracking

Disputes

A disputed invoice is held out of every reminder until the dispute is resolved.

dispute hold

Statements and aging

A customer statement on screen or as a PDF, and an aging view by bucket for every customer and currency.

statementsaging buckets

Payment behaviour

Days to pay, punctuality, trend and promises kept, calculated from the invoices themselves, never guessed.

days to paytrend

Customer memory

Past emails, documents and notes are searchable, and standing instructions ("never chase before the 15th") are followed.

searchinstructions

Per-customer settings

Turn drafting off for a customer you'd rather handle personally.

drafting off

Always current

A draft is withdrawn if what it asks about gets paid, cancelled, disputed or promised, and checked again at send.

self-retiring drafts

Sales can see it too

Anyone on the account can ask "is Northline up to date?" and get an answer from the records.

read-only seats

30 minutes, your paperwork

Bring your aging report

We'll show you what duebird would draft for your oldest accounts.