Skip to the page

Solutions

Chase late payments. Every morning, with one yes.

Find your overdue invoices, keep them in view, and send each customer a reminder in your own words, once a person has read it and said yes.

Your own words, no AI

Read each reminder
before it goes

Remind about unpaid invoicesFlows · Tarnwick Supply Co.Sample data
Every morning08:00
Unpaid invoicesAccounting · 212 rows
Past due52 kept
Write the reminderyour words, no AI · 52 drafts
Ask firstSend 52 reminders? · Dana OrtizNot sent · you said no
Send the reminders
  1. 1Try it first: nothing is sent

Sounds familiar?

In the words finance teams use:

  • The chasing list is made by hand, every time.
  • At month end someone exports the ageing report, sorts it in a spreadsheet and writes the e-mails one by one.
  • Nobody is sure who was already chased, or what was said.

How it works at Tarnwick.

On Tarnwick Supply Co., sample data. Each step names what you see.

  1. 1

    Ask. “Which invoices are more than 60 days overdue?” The answer: 14 invoices, the amount outstanding, and the list. Download it to Excel if you want it.

    AI Assistant
  2. 2

    Keep it in view. A board “Receivables”: the overdue balance by customer, grouped by how late. Build it in the designer, or ask for it. A click on an invoice row opens that invoice in your accounting system.

    Dashboards
  3. 3

    Copy the ready flow. Under Flows, starter flows, pick “Remind about unpaid invoices”. The copy is yours. It starts switched off and lists what you choose before it runs: your accounting system, and a mailbox to send from.

    Workflows
  4. 4

    Make the words yours. Each reminder is written from your own words, with no AI, so the same invoice always gives the same message. The invoice number, the amount and the due date come from each invoice.

    Workflows
  5. 5

    Try it without sending. The test reads your real invoices and shows each reminder it would send. Nothing is sent and nothing is changed.

    Workflows
  6. 6

    Say yes each morning. The “Ask first” step puts one card on your Waiting page: “Send 52 reminders?” You read each reminder as it will go out, and you may fix its subject or its words before you say yes. Say no, and nothing is sent.

    Workflows
  7. 7

    See what happened. Each run’s page shows what each step received and passed on. A failed run can carry on from the step that failed, and nothing it already sent goes out twice.

    Workflows

3Copy the ready flow

Remind about unpaid invoicesYour copySample data
Remind about unpaid invoicesOff
Before it runs, choose:
your accounting systemChoose
a mailbox to send fromChoose
Choose two things, then switch it on

6Say yes each morning

WaitingAsk firstSample data
Send 52 reminders?Dana Ortiz
SubjectInvoice INV-20901Edit

Dear Quellmark Foods,

Our records show that invoice INV-20901, for $8,460, was due on 2 October. If you have paid it already, thank you, and please ignore this message.

Kind regards

Edit
1 of 52DeclineApprove
Fix the words before you say yes

7See what happened

Run · this morningRemind about unpaid invoicesSample data
Unpaid invoices
212
Past due
52
Write the reminder
52
Ask first
approved
Send the reminders52 sent
Send the reminders
Received52 reminders, approved by Dana Ortiz
Passed on52 sent
With analysis & prediction

Get ahead of the next one.

  • Who is likely to pay late. For each open invoice, the chance it is paid late, learned from your own history, with three reasons and an honest range.
  • Money by month. The cash expected each month, with a range, in one currency.
  • “Maybe paid”. Where a customer has paid money not yet matched to an invoice, its invoices are flagged “maybe paid”, so you can check before you chase.
Analysis & prediction
Paid late · open invoicesPredictionSample data
CustomerOpenChance paid lateWhy
Lumora Hotels$7,88081 in 100Paid its last 4 invoices late
Quellmark Foods$6,21557 in 100Pays 12 days late on average
Fenwright Builders$9,615maybe paidA payment of $9,615 is not matched to an invoice yet
Patterns in your history, not proof

What you get.

  • The overdue list as an answer, and as an Excel file when you want one.

  • A receivables board your team opens, private until you share it. Export it as a picture, a PDF or an Excel workbook, one sheet per chart or table.

  • A reminder flow that runs every morning and waits for a person’s yes.

  • One card a day on your Waiting page, with every reminder as it will go out.

  • A page for each run: what it found, what it sent and who approved it.

Before you start.

  • The flow reads invoices from an accounting system with an API, or from a ready-made connector. It cannot read a connected database today.
  • Ready-made connectors include Xero, QuickBooks and Odoo. Xero and QuickBooks first ask you to register an app with them.
  • It sends from your company’s Microsoft 365 mailbox when one is connected, otherwise through our messaging service.
  • A company owner copies the flow and switches it on. Members can see it, and run it when it is shared with Edit.
  • A run is one time a flow runs, from its start to its end, however many rows it handles: a morning that sends 52 reminders is one run.
  • When a list holds several currencies, the board gives one total per currency.
  • Writing back to your accounting system, such as marking an invoice as chased, is off until your owner switches it on for that system. Then each write waits for a person’s approval.

What it does not do yet.

So you know before the demo.

  • It does not send reminders from the chat.A flow sends them.
  • Flows that start when a payment e-mail arrives are not ready for customers yet.
  • Asking about your own Outlook mail is not ready yet.

For the whole finance picture, see Finance. Finance

Bring the overdue list you make by hand today.

In the demo we connect one of your systems, and you ask the questions.