Payments and collections

Recording a payment

Payments are recorded against the invoice. The amount paid, the invoice status and the outstanding balance update together, so there is no separate reconciliation step.

Part payments are supported — record what actually arrived and the invoice keeps the remainder outstanding.

Advances

Money received before an invoice exists can be recorded as an advance from the customer and allocated later, rather than being held outside the system until there is something to attach it to.

Reminder schedule

A job runs once a day and sends whichever reminders are due, based on offsets you configure relative to each invoice's due date. Offsets can sit before the due date as a nudge and after it as follow-up.

Reminders are driven by the outstanding balance, so recording a payment stops them automatically.

Reminder content

Templates support placeholders that are substituted per invoice — customer name, invoice number, amount due and due date among them — so one template covers every customer.

Customer control

A customer can be excluded from reminders on their record, and every reminder email carries a one-click unsubscribe link that is honoured automatically. Reminder sends are logged, so a disputed delivery can be checked rather than argued.

Seeing what is owed

Aging reports bucket outstanding invoices by how long they have been due. A customer statement shows the transactions behind a single customer's balance and can be sent to them.

A push notification is sent on the first day an invoice tips into overdue.