Invoice deposits, due dates, and cleaner payment follow-up

A deposit is part of the invoice, not an extra charge

If a $4,000 invoice requires a $1,000 deposit, the customer still owes $4,000 in total. Recording the deposit should increase the paid amount to $1,000 and reduce the balance to $3,000. It should not turn the job into $5,000 of revenue.

Store the required deposit amount, its optional due date, and each actual payment separately. This lets the team distinguish “deposit requested” from “deposit received” and keeps the payment history understandable.

Give the remaining balance a real due date

An invoice creation date tells you when the document was made. It does not necessarily tell you when payment is expected. Add a balance due date based on the agreed terms—due on receipt, seven days, fourteen days, thirty days, or a specific contract date.

Use company-level default terms to reduce repetitive setup, while allowing an individual invoice to be adjusted when the agreement is different.

Forecast only money that is actually due soon

A useful short-term forecast separates three ideas:

• Outstanding: every unpaid customer balance.
• Due soon: unpaid balances with a due date inside the forecast window.
• Overdue: unpaid balances whose due date has passed.

Calling every outstanding invoice “expected in the next 30 days” can overstate near-term cash. The due date is what makes that forecast defensible.

Make follow-up specific

Before sending a reminder, verify the remaining balance, due date, previous payments, and customer email. A good reminder states what is due and gives the customer a direct way to review the invoice or pay. Avoid reminders on invoices that are not yet due unless the message is intentionally a friendly upcoming-payment notice.

When the customer pays, record the amount, date, method, type, and a useful reference such as a check number. Send a receipt from the updated invoice so the customer sees the same balance as the business.

Review aging without losing context

Aging groups such as 1–30, 31–60, and 61+ days past due help prioritize collections, but the job and customer context still matter. A disputed change order needs a different response than a forgotten invoice. Use the aging view to decide where to look, then use the connected job and interaction history to decide what to do.