Overdue invoice reminders from Jurnal, checked by finance first

Every morning, Sambung reads the invoices in Jurnal that are past their due date and prepares one WhatsApp message per customer. Your finance team strikes off anyone who has already paid, approves the rest, and only then do they go out.

Biissa team · Updated 16 November 2026

In short

  • Before: someone exports overdue invoices from Jurnal and sends reminders one by one, often from a personal phone.
  • With Sambung: each morning the messages are ready, with invoice numbers and amounts from Jurnal.
  • Finance strikes off customers who have already paid and approves the rest before anything is sent.
  • It only reads from Jurnal and writes nothing into it, which makes it a good first job.

The job today

For a company that sells on credit terms, chasing overdue invoices is a weekly chore. Someone exports the list from Jurnal, checks who has paid, and writes the reminders by hand.

  • Reminders go out late, or not at all, when the week is busy.
  • A customer who paid yesterday still gets a reminder.
  • Messages sent from a personal number leave the company no record.

How it runs with Sambung

This is an example, not a customer story.

  1. Every morning

    Overdue invoices are read from Jurnal

    Each invoice past its due date, with its number, amount and due date.

  2. Before the AI reads them

    Names become codes

    Customer names are replaced with codes before the messages are prepared, and the step is logged.

  3. Ready for finance

    One message per customer

    Each customer’s overdue invoices go into one message, with the numbers and amounts from Jurnal and a line asking them to ignore it if they have already paid.

  4. Before anything is sent

    Finance checks and approves

    Customers who have paid since are struck off, any message can be edited, and the rest are approved.

  5. After approval

    Sent from the company’s number

    Each send is logged, so finance can see who was reminded and when.

What comes from where

Which invoices are overdue
Comes fromJurnal
HowRead from the due dates in Jurnal
Invoice numbers and amounts
Comes fromJurnal
HowCopied from Jurnal, never worked out by the AI
The message
Comes fromYour template
HowA message template approved by Meta, with the details from Jurnal filled in
One message per customer
Comes fromSambung
HowA customer’s overdue invoices are grouped together
Who has paid since, and the final yes
Comes fromYour finance team
HowStruck off before approval; nothing is sent until finance approves
Where each part of a reminder comes from

What you need to start

  • Jurnal (by Mekari), where your invoices and due dates are.
  • A WhatsApp Business number for the company, and a reminder message template approved by Meta.
  • Customers who have agreed to receive WhatsApp messages from your company.
  • A person in finance who approves the messages.

Common questions

Are the reminders sent without anyone checking?

No. Finance checks the messages each morning, strikes off customers who have paid, and approves the rest. Nothing is sent before that.

Does Sambung change anything in Jurnal?

No. This job only reads invoices from Jurnal. Your team still records payments in Jurnal.

Why is a message template needed?

WhatsApp lets a business start a conversation only with a message template that Meta has approved. Each company has its own template, and its customers must have agreed to messages from it.

How do we start?

With a free first chat, then Cek Alur Kerja: a free workflow check of about 10 working days. A test on your past invoices comes before a 4-week pilot.

Tell us about one job.

  • The Biissa team replies the same day, in office hours.
  • The first chat and the workflow check are free.
  • We ask how the work flows first, then tell you honestly whether AI can help.