The case that ruins every management app

You invoice €5,400 on the 5th of the month on NET_30 terms. Your client, who is OK and a reliable payer, tells you explicitly: "Our internal payment cycle has an issue this month, we'll pay you on the 20th of next month. Not before."

It's agreed. It's documented. Everything's fine.

Except every management app shows you a red OVERDUE alert from the 5th of the next month. And it stays red for 15 days. And you see it on your dashboard 15 times a day.

Dumb usual fix: manually change the invoice date to shift things. But that ruins your bookkeeping (the invoice was really issued on the 5th).

Snoozing, or how to tell the app "I know, keep quiet"

The mechanism:

  • You keep the invoice with its actual issue date (5th of the month)
  • You indicate "snooze until the 20th of next month"
  • Optionally you add a reason ("client promised the 20th")
  • The app hides the overdue alert until that date
  • If the 20th arrives and you still haven't been paid, the alert returns

Concretely, you keep the bookkeeping info correct AND your dashboard stays clean.

When to snooze (and when not)

Snooze when:

  • The client explicitly promised a date (verbal or written)
  • The delay exceeds your usual 15-day tolerance but stays within 60 days
  • You want the alert to resurface only if the deadline isn't met

Don't snooze when:

  • Client hasn't promised anything, you're just waiting silently — that's a real late, keep the alert
  • Delay > 60 days without structural reason — that's a business red flag, the alert is valuable
  • You want to "hide the problem" so you don't think about it — bad idea, snooze isn't denial

The nuance that changes everything: the timer comes back

When you snooze to the 20th and the 20th arrives:

  • If paid: invoice marked PAID, snooze becomes irrelevant, everything's clean.
  • If not paid: the alert returns instantly, in red, with a special "still overdue despite accepted snooze" mention. At that point, you know the client broke their promise and you escalate.

That's exactly what we want. Snoozing isn't a highway to forgetfulness — it's a respectful pause until the agreed date.

Difference with "mark as paid in advance"

Tempting alternative: marking the invoice as PAID on the 5th even though you know it'll be paid on the 20th. Very bad idea:

  • Your treasury shows cash you don't have (you risk spending it)
  • Your collected VAT (cash basis) is declared too early — fiscal risk
  • Your health score is falsified (recovery at 100% instead of reality)

Snoozing doesn't touch the cash. The invoice stays PENDING. The treasury projection knows it's waiting for €5,400 by the 20th. Everything stays honest.

The client-side flip: the negotiated postponement

Variant: your client asks to postpone the payment (in advance or during the term). You accept? You update the expected payment date (not the invoice date), you note the postponement reason, and the reconciliation engine absorbs it when the payment arrives.

Same mechanism, seen from the other side: an accepted delay isn't a suffered delay.

What makes the difference

Many SaaS management tools don't have this feature. Either they force you to lie (change the date), or they leave you in perpetual red.

Freelance Budget tracks snooze cleanly: snoozedUntil + snoozeReason fields at the invoice level, alert hidden in the dashboard and notification badges, but the info stays in the treasury projection. The best of both worlds.