Invoice Review: Keep a Draft Separate From a Payment Outcome
Question: How should a team review an invoice without confusing a draft, a sent request, and a completed payment?
Keep the states distinct
An invoice draft is a record to review. A sent invoice is a communication step. A payment outcome requires confirmation in the appropriate payment record. Do not use one status as proof of another.
Before sending or updating
- Confirm the invoice is linked to the correct customer and work record.
- Check the description of work against the approved scope.
- Use only approved financial data and terms.
- Confirm who may review, send, or correct it.
- Make any pending issue visible through a task or follow-up.
- Verify the displayed invoice after saving.
If there is uncertainty about tax, payment status, terms, or authorization, pause and ask the responsible person to review it.
Clear wording
| State | Safe wording |
|---|---|
| Draft under review | “Invoice requires internal review.” |
| Communication needed | “Customer update is pending approval.” |
| Payment unknown | “Payment status needs verification.” |
| Correction required | “Invoice record requires a factual correction.” |
Never put card details, bank details, authentication codes, or unnecessary personal data in a general note or screenshot.
For the full invoice workflow, see Invoices: Keep Billing Records Clear Before You Ask for Payment. For next-contact discipline, see Follow-Up Queue.
Boundaries
This is a billing-record review checklist. It does not prove that an invoice was received, accepted, delivered, paid, refunded, collected, tax-compliant, or legally enforceable. Verify the appropriate record and approved process.