Aura Business sends outstanding-payment reminders over WhatsApp on the rhythm you set, with the invoice number, amount and due date in the message, and takes a customer off the run the moment their receipt is entered.
A reminder run takes every invoice that is open and due, works out which customers need contacting today under the schedule you set, and sends each one a WhatsApp message with their own invoice number, amount and due date in it. When a receipt is entered against that invoice, the customer drops off the run without anybody having to remember to stop it.
In Aura Business this is the WhatsApp Business integration in the Analytics and Platform suite, driven by the Payment Tracker and the receivables ageing in the Finance suite. It matters because most overdue payments in a distribution business are not refusals. They are invoices sitting unactioned in somebody's approval queue, and a polite message with the reference in it is usually all that moves them.
A person who has to send forty individual messages by hand will send fifteen, and will send them to whoever they remember.
Each reminder is written by hand with the invoice number copied across from another screen.
A vague request for payment reaches an accounts department that handles hundreds of invoices and goes nowhere.
A customer who paid last week gets chased again and the relationship takes the damage.
One reminder goes at ninety days, when nothing goes at seven, fourteen and thirty.
The follow-up history lives on one employee's phone and leaves when they do.
Two people chase the same balance and the customer hears two different things.
The GST invoice sits unpaid with a due date set by the customer's credit days.
Your reminder rhythm decides which day each open invoice is contacted on.
Invoice number, amount, due date and your business name filled into the template.
The reminder goes to the contact recorded against that customer account.
The send is recorded against the customer so the whole team sees what went out.
Payment applied to the invoice and the balance updates in the ageing view.
A settled invoice drops out of the reminder run with no manual action.
Workflow: A reminder goes out a few days after the due date with the invoice reference, before anybody has to ring.
Result: Many invoices clear before they ever become a phone call.
Workflow: The reminder carries the invoice number, so the hospital's accounts team can locate it without ringing back for details.
Result: The approval queue moves.
Workflow: The receipt is applied in the morning and the afternoon reminder run skips that customer.
Result: No apologetic follow-up call.
Workflow: Every reminder sent is logged against the customer alongside the ageing and the follow-up notes.
Result: Two people never chase the same balance twice.
Hospital accounts departments with long approval chains.
Many small invoices per customer per month.
Sub-dealers paying against credit limits.
Contract instalments and job invoices both chased.
Site billing that ages quietly.
Problem: A distribution business run entirely on WhatsApp and Excel.
Built: Field app, manager dashboard, GST billing and payment tracking.
Stack: React Native, Supabase, WordPress.
Problem: No online store or way to manage distributors.
Built: Storefront, distributor portal, quote-to-order and 253 SEO pages.
Stack: Supabase, JavaScript, Playwright.
A short, plain message naming your business, the invoice number, the amount outstanding and the due date, with a request to confirm payment. The wording is set up for you during onboarding and is not written fresh each time.
No. Reminders are driven by the open balance, so once the receipt is applied against the invoice the customer leaves the run. This is why applying receipts promptly matters more than the reminders themselves.
On the schedule you choose, typically a light first reminder shortly after the due date and firmer ones as the balance ages. Different schedules can be used for different kinds of customers.
Yes. A customer or a single invoice can be excluded, which is what you want when a dispute is open or a payment plan has been agreed, and the exclusion is recorded.
Messages are sent through the WhatsApp Business integration so they come from your business account rather than a personal number. The account setup is done with you during implementation.
Yes. Any open invoice can enter the run, including contract instalments and service invoices. See receivables ageing for how the chase list is ordered.
Tell us how you work today. We will show you what the platform would look like for you, and give you a clear scope and timeline.
Founder-led · Chennai, India · Built and supported by the person who wrote it