Skip to main content
Hitaji 360 can chase your overdue receivables for you. Each accounting book can send your finance team a recurring digest of overdue invoices (and debts) to follow up on — how many, how much, how old, and the worst offenders — so nothing slips through the cracks. You control whether it runs, how often, and how it’s delivered. You can also send the digest on demand, and quiet individual invoices that don’t need chasing yet.
Reminder settings are per accounting book. Each business has its own book, so the cadence and channels you set here apply only to the business you’re currently working in.
You’ll find this at: Settings → ERP → Finance → Overdue reminders (route /settings/erp/finance/invoice-reminders).
📷 Screenshot: Overdue reminders settings card with the enable toggle, frequency selector, channels, and the Save / Send digest now buttons — to be added.

What the digest contains

When a digest is sent it summarises every still-collectable, overdue invoice in the book:
  • How many overdue invoices and the total amount due.
  • The oldest overdue age in days.
  • An aging breakdown into buckets: 0–30 days, 31–60 days, and 60+ days (count and amount per bucket).
  • The top overdue invoices, oldest first.
“Overdue and collectable” means an invoice whose due date has passed, that still has a balance owing, and that is in a chaseable state (sent, partially paid, or already marked overdue). Snoozed invoices (see below) are excluded until their snooze ends.

Turn reminders on or off and set the cadence

About cadence: the system runs a sweep every morning, but your chosen frequency decides whether this book is actually due. The digest goes out no more often than the frequency you pick — Daily chases every day; Weekly waits about a week between sends; Every 2 weeks waits about two weeks; Monthly waits about four weeks. (Sending the digest manually with Send digest now bypasses the cadence — see below.) Channels: You must leave at least one channel enabled for a digest to be deliverable.

To change these settings

  1. Open Settings → ERP → Finance → Overdue reminders.
  2. Confirm the business in the switcher is the book you want to configure.
  3. Toggle Send overdue reminders, choose How often, and tick the Channels you want.
  4. Click Save Changes. (Frequency and channel edits are saved together when you click Save — they don’t auto-apply.)
📷 Screenshot: Frequency dropdown open (Daily / Weekly / Every 2 weeks / Monthly) with the channels checklist below it — to be added.

Who receives the digest

Recipients are everyone bound to the finance role for this book — you don’t maintain a recipient list on this screen for the standard digest. If no one is bound to that role, the digest has nowhere to go and won’t send (you’ll see a “no recipients” message if you try Send digest now). The page also shows when the last digest was sent, so you can confirm it’s running.

Send the digest now

Click Send digest now to dispatch the digest immediately, without waiting for the next scheduled run. This is handy after a billing push or before a collections meeting. It bypasses both the once-per-day guard and the frequency cadence. If nothing is sent, the button tells you why:
📷 Screenshot: “Send digest now” result toast, e.g. “Digest sent for 5 overdue item(s)” — to be added.

Quiet a single invoice (per-invoice controls)

You don’t have to chase every overdue invoice. On the Invoices page (/accounting/invoices), overdue invoices expose two quick actions: Snoozed invoices drop out of the digest’s overdue set until the snooze period ends, then reappear automatically if still unpaid. The current button snoozes for a fixed 7 days.
📷 Screenshot: An overdue invoice row on the Invoices page showing the “Mark followed up” and “Snooze 7 days” hover actions — to be added.

Who can change it

If you can see the settings but the controls are read-only, you have view access without the finance-configuration permission — the page tells you so. Ask a finance administrator to grant accounting:config.

How it runs automatically (for reference)

  • A background sweep runs every morning and, for each book with overdue invoices, sends the digest if the book is enabled, due per its cadence, and hasn’t already been sent today.
  • A separate overnight job first marks newly-overdue invoices as overdue so they’re included by the time the digest is built.
  • A book is only swept if it actually has overdue, collectable, un-snoozed invoices — quiet books generate no noise.