Invoices
The Invoice Delivery Checklist: What “Sent” Should Actually Mean
Changing an invoice status to sent is not delivery. A dependable workflow creates the customer communication, the intended document and access path, and a visible result the employee can trust.
Key takeaways
- Review invoice content and recipient on the server before delivery
- Create the PDF and secure customer page as part of the send operation
- Record delivery provider results and surface failures
- Make retries safe so they do not create duplicate sends
Review the invoice as the customer will receive it
Confirm the legal company name, customer recipient, billing address, invoice number, dates, line descriptions, quantities, totals, tax, payment terms, and contact path. If the invoice came from a signed proposal, compare it with the approved scope and identify every legitimate extra charge.
A required deposit and a received payment are different. The document can show the deposit rule, but the balance should be reduced only by a confirmed payment record that identifies the amount, date, method, and recording source.
Make send one auditable server operation
The server should authorize the user, workspace, company, pipeline, job, and invoice again. It should render or retrieve the intended PDF, create the scoped customer invoice URL, send the message through the configured provider, and save the provider result.
Only then should the interface show Sent. A provider rejection, timeout, missing recipient, or PDF failure should produce a clear error with a safe retry action, not a green status that asks the employee to assume delivery.
- Authorized sender and workspace
- Validated recipient
- Current invoice version
- Customer page and PDF
- Provider message ID
- Sent or failed timestamp
Design for retries and customer questions
Use an idempotency key so a double click or timeout retry does not silently create several emails. Keep the delivery history visible to staff and avoid exposing unrelated customer or workspace data through the public URL.
When the customer opens the invoice, show the company contact, invoice details, amount due, recorded payments, and a trustworthy way to ask a question. Do not advertise online payment checkout unless the live customer page can actually complete it.
Practical answers
Frequently asked questions
What does it mean when an invoice is sent?
Sent should mean the system successfully created the intended customer communication and recorded the delivery provider result, not merely that an internal status changed.
Should an invoice email include a PDF?
A PDF is useful for records, while a secure customer page can show the current status. The company should deliver the formats promised in its workflow.
What happens if invoice delivery fails?
Show a meaningful failure, preserve the invoice draft, log the operation, and offer an idempotent retry after the recipient or provider issue is corrected.