Pause one invoice, or a whole client
A disputed job goes on hold on its own. A client you'd rather ring yourself goes on hold entirely. The scan skips both, no matter how overdue they get, and picks up again when you say so.
It watches your unpaid invoices. The day one goes past due it starts a reminder sequence that opens politely and gets firmer as the debt ages — and it stops the moment the invoice is marked paid.
Free plan, one connected client account, no card details.
Hi Danielle,
Invoice INV-2041 for $4,180.00 was due on 21 July and is now 14 days overdue. We've sent two reminders and haven't heard back, so I wanted to raise it with you directly.
Could you confirm today when payment will be made? If there's something wrong with the invoice, tell me what it is and I'll sort it out.
You can view and pay it here: invoices.haldenjoinery.com.au/2041
Thanks,
Marcus — Halden Joinery
Highlighted values are merge fields, filled from the invoice when the reminder is written. Illustration — not a real customer.
Made for Australian sole traders and small teams — the one or two people who send the invoices, and end up chasing them.
Stripe invoice sync is live today. Xero and QuickBooks connect over standard OAuth — both are built end to end and currently in testing. Reminders leave through your own mail server, or as signed webhooks into your own system.
It shouldn't be your job.
You did the work. You sent the invoice. Now you're the one writing the awkward email — rewriting it twice so it doesn't read as shirty, then waiting, then writing it again. Meanwhile money that is already yours sits in somebody else's account.
Because you can't get the tone right, and every hour you leave it the email gets harder to send.
You water it down so far that the client reads it as a friendly hello and files it under later.
Nobody chased it, because you were busy doing the work that earns the next invoice.
Nudger does all three, on schedule, in the same even tone. Every time, without a single uncomfortable moment.
Stripe hands every invoice to Nudger as it's raised, goes past due or gets paid — that part is live today. Xero and QuickBooks connect the same way over standard OAuth, and both are in testing.
Four graded reminders come ready-made. Change the timing, change the wording, change how firm the last one gets. Merge fields drop in the invoice number, the amount owing, the due date and how many days late it is.
Add your own SMTP details and fire a test email to prove they work. From then on reminders go out under your own name, on schedule, and stop the moment the money lands.
Straight answer first: once an invoice goes past due, reminders go out automatically. There's no per-send approval screen — that's the entire point of handing it over. So the controls are the rails, and you set them before anything is overdue.
A disputed job goes on hold on its own. A client you'd rather ring yourself goes on hold entirely. The scan skips both, no matter how overdue they get, and picks up again when you say so.
Set a floor per client account and anything below it is filtered out before a reminder is even written. Nobody gets a firm notice over twelve dollars, and no relationship is spent on rounding.
Every management route goes through a single workspace-scoped layer, and an automated test proves a second business gets a 404 on every one of your routes. Sign-in uses server-side, revocable sessions in a cookie your browser's JavaScript can't read.
It won't hold each reminder for your approval — there is no review queue. It won't read your mailbox. It won't collect a debt on your behalf or give you legal advice. And it's deliberately small: one sign-in per workspace, no roles, no single sign-on, no audit log.
If a client pays by bank transfer and you haven't reconciled it yet, Nudger doesn't know the money arrived and the next rung will still go out. Mark the invoice paid, or pause it. Closing that gap automatically — by forwarding the remittance advice in — is built but not switched on, and even then a person will always approve it, because a forged remittance would silently switch your chasing off.
Sending email is easy. Not sending the wrong email is the whole job.
When an invoice is marked paid, every reminder still queued against it is cancelled in the same operation. Not skipped later — cancelled then and there.
One step fires once per invoice, enforced by a database constraint rather than hopeful code. A crash, a retry or two copies of the service running at once still can't produce a duplicate.
You supply your own mail server and from-address, so replies land in your inbox and your sending reputation stays yours. There's no shared sending domain, and a test send proves the credentials before you rely on them.
Rather handle reminders in your own system? Nudger posts a signed JSON payload instead — HMAC-SHA256, a secret per account — and retries with backoff if your endpoint is having a bad afternoon.
Company name, ABN, phone, and the two people who actually deal with the money — your bookkeeper and the owner — live in your profile instead of in your head.
Every customer gets a rating out of five, worked out only from your own invoice and reminder history. A private read on who to chase early. Not a credit file, and it never leaves your workspace.
Everything in this column is written and tested in the product. None of it is running for customers today, so don't sign up expecting it.
Free is live now. Starter and Pro are the structure we're building to. Sign up and you land on Free.
Being straight with you: paid plans aren't purchasable yet. Sign-up works today and lands you on Free — the sequence, the templates, the pause controls and the customer scoring all run. The figures above are the intended structure rather than a quote: inside the product they appear as plain dollar amounts with no currency marker, and the currency, GST treatment and billing cycle aren't settled. The only limit enforced right now is the number of connected client accounts, so when one isn't enough, email us and we'll sort it out with you directly rather than pointing you at a checkout that doesn't finish.
No. The first step is a genuinely friendly note, and you write it yourself — the defaults are a starting point, not a script you're stuck with. You can hold a single invoice the moment a job is disputed, hold an entire client, and set a minimum amount so small balances are never chased at all. The final notice is the only tone allowed to get pointed, and only if you wrote it that way.
No, and we'd rather say that plainly than imply a review step exists. Once an invoice is past due, reminders send automatically on schedule. What you control is everything upstream: the timing, the wording, the minimum amount, and two independent pause switches you can hit at any moment.
If the payment comes through a connected provider, the invoice flips to paid and every queued reminder for it is cancelled in the same operation — not skipped, cancelled.
Here's the honest gap: a bank transfer you haven't reconciled anywhere is something Nudger simply can't see, so mark the invoice paid or pause it. Forwarding remittances in is built to close that gap, and it isn't running yet.
Yours. You supply your own mail server and from-address, so replies come straight back to you and your deliverability stays your own rather than somebody else's shared domain. There's a test-send button to prove the credentials work before you rely on them.
No. Every workspace is isolated through a single scoped data layer that all management routes pass through, and an automated test proves a second workspace receives a 404 on every route belonging to the first. Customer ratings are calculated only from your own history — they are explicitly not a shared credit file, and they never cross a workspace boundary.
Nudger never sees your accounting password — it's standard OAuth with rotating refresh tokens, and the callback state is signed to stop anyone forging a connection. The caveat worth stating: both integrations are code-complete but haven't yet been run against a live Xero or QuickBooks app, so treat them as in testing. Stripe is the connection that's live today.
No. Nothing reads your mailbox. There's a forward-an-invoice address in the product that only ever sees mail you deliberately forward to it, it requires you to tick explicit terms before anything is stored, and it isn't running yet either.
The company details it collects are Australian — company name, ABN, your bookkeeper and the owner — and the reminders are yours to word however you like. But Nudger is a reminder service, not a debt collector.
The recovery documents inside the product — demand letters, interest and late-fee workings, small-claims guidance — are built around United States jurisdictions and are not suitable here. Nothing Nudger produces is legal or financial advice. For genuine recovery in Australia, speak to your accountant or a solicitor.
You can sign up today and use the free plan with one connected client account. You can't buy a paid plan yet — checkout isn't finished. Three tiers exist in the product and the figures are set, but the currency, GST treatment and billing cycle aren't finalised, so read them as a shape rather than a price.
It's deployed and running around the clock with health checks, the reminder logic is covered by an automated test suite, and the full pipeline has been run end to end against a real database.
It is also deliberately small: a single instance, one sign-in per workspace, no roles, no single sign-on and no audit log. If you need those things, it isn't for you yet.
Create a free workspace, connect one client and read every line of the sequence first. Nothing sends until an invoice actually goes past due — and you can pause any invoice, or any client, at any time.