Invoice email tracking checklist

Before sending

• Confirm the client legal name and billing contact.
• Confirm the invoice identifier, currency, amount, tax treatment, issue date, and due date.
• Confirm the billed scope matches the agreement, accepted estimate, time, or milestone.
• Give the invoice one internal owner.
• Save or generate one final issued document. Remove draft labels and avoid ambiguous final file names.
• Link the invoice to the client and related project.

At send time

• Send from the agreed channel and use the intended billing recipient.
• Record the sent time and recipient in the invoice history.
• Set the invoice state to sent only after the delivery action succeeds.
• Preserve the exact issued version.
• Set the next review date based on the due terms, not on memory.

If delivery fails, keep the invoice in an exception state. Do not mark it sent because someone clicked a button.

After sending

• Confirm receipt when the client or delivery system provides a reliable signal.
• Record questions or disputes on the invoice and client timeline.
• Reconcile payment to the correct invoice.
• Keep partial payment distinct from paid in full.
• Stop reminders once the payment is reconciled or the invoice is formally void.

Review the exception queue

A useful weekly view includes ready but unsent, send failed, due soon, overdue, disputed, partial payment, and payment received but unreconciled. These are operational states, not inbox labels.

For each exception, name the owner and next action. A status with no responsible person is only a description of the problem.

Use one ownership rule

The person who creates an invoice does not always own follow-up. Decide whether ownership stays with finance, the account lead, or a named collections role. Make the exception path clear when the owner is unavailable or the client disputes the amount.