Invoice drafts vs automatic sending: where should a person review?
Invoicing workflows
The short answer
Automatically preparing an invoice draft is different from sending it or collecting payment. Keep human review where customer identity, changed scope, deposits, partial work or unusual terms need judgment. Consider automatic sending only for a well-defined, tested class of routine invoices with reliable inputs and visible exceptions. State exactly which action is approved, who can perform it and what happens if the workflow fails or the source record changes.
An automation can copy correct data and still do the wrong thing at the wrong time. Choosing the review boundary is a business decision, not just a setting in a connector.
Name the action before deciding whether to automate it
List the steps your tools perform: create a draft, approve or finalize it, send the document, collect a payment and update the job status. A button labeled 'create invoice' may do more than its name suggests. Inspect the destination settings and test the actual result.
Stripe's invoice lifecycle illustrates distinct draft, open and paid states. Those labels are product-specific, but the separation is useful. Confirm that creating a draft cannot unexpectedly release a customer email or start collection under an existing setting. Permission to prepare information is not automatically permission to charge a customer.
Keep judgment where the invoice can depart from the agreement
A person should review unresolved scope changes, uncertain customer matches, partial completion, earlier billing and unusual terms. Also consider whether a small input error could create a difficult customer conversation. The importance of review is not determined solely by invoice size.
| Situation | Practical starting point |
|---|---|
| Approved fixed work, complete records | Prepare a draft; evaluate routine sending only after testing. |
| Pending extra or disputed quantity | Hold for a named reviewer. |
| Deposit or previous stage invoice | Check the authoritative financial records. |
| New billing contact or changed instructions | Verify through the agreed business process. |
| Failed or repeated handoff | Check for an existing invoice before retrying. |
Give the reviewer evidence and a short checklist
Link the draft to its accepted quote, job completion and approved changes. Show what differs from the original agreement and identify earlier invoices or payment references. A reviewer should not have to search several inboxes before making a routine decision.
- Correct customer, recipient and required billing reference.
- Correct accepted scope, quantities and approved changes.
- Work or milestone ready for billing.
- No duplicate or previously billed lines.
- Financial treatment and terms follow the configured accounting process.
- Customer-facing descriptions contain no internal notes.
Record approval against the reviewed version. If someone changes the amount, recipient or scope afterward, require the appropriate recheck rather than carrying an old approval onto a different invoice.
Illustrative routing rule for routine work and exceptions
In this illustrative example, a business has one repeat service type. It uses a fixed accepted price, one known billing account and a completion checklist. The business chooses to prepare drafts automatically, while a person checks them before sending.
Its exception rule is explicit: a changed quantity, missing reference, proposed extra or unmatched customer holds the record for review. If the business later considers automatic sending, only this tested service class is considered. Other job types remain draft-only. The business first checks settings, failure handling and authorization; it does not expand sending simply because a few routine drafts happened to be correct.
Look for native approval controls before adding another layer
Your existing billing tool may already separate preparation and approval. Xero documents saving converted invoices as drafts or submitting them for approval. Check the permissions and workflow available in your actual account rather than assuming all staff can approve or all plans behave alike.
Use one clear approval location where possible. Requiring a person to approve in a job tool, a message thread and accounting can add uncertainty if the records disagree. If operational sign-off and financial release are genuinely different responsibilities, name them separately and specify what each approval confirms. Do not make every approval mean 'everything is correct.'
Plan for absence, changed records and uncertain sends
Assign a backup reviewer and a visible queue for waiting drafts. Define how rejected drafts return for correction and who receives failures. If sending times out, inspect the destination's activity before sending again. A timeout does not prove that the email was never released.
Keep a stable source-event reference and destination invoice identifier. Prevent a repeated event from making another invoice. A correction after issuing a document belongs in the accounting tool's approved correction process, not an overwrite designed to make a job screen look tidy. See our automation failure and recovery guide for the wider operational checks.
Agree acceptance tests before enabling customer-facing actions
Test a clean job, incomplete job, changed quote, previously billed stage, wrong customer match and retry after failure. Confirm that a rejected record cannot bypass review. Check what the customer would actually receive, including the recipient and attachments, using safe test destinations.
We scope invoice preparation and approval workflows around your existing accounting controls. A successful implementation may stop at a reliable draft handoff. Automatic sending is appropriate only when it is explicitly agreed and supported; payment collection is a separate decision again. The aim is to remove repeated preparation while preserving the decisions that still need a person.
A few follow-up questions
Does approving an invoice authorize automatic payment collection?
Not by itself. Approval, sending and collection are separate permissions and actions. Check your billing settings and the authorization required by your business and payment process.
Can the person creating a draft also approve it?
That depends on your business's financial controls and role structure. A small team can still use a deliberate checklist, but the appropriate approval responsibilities should be agreed with its accounting professional.
What should happen if a draft changes after approval?
Identify which changes require a new review and record the approved version. Changes to customer, price, scope or payment instructions should not quietly inherit an unrelated earlier approval.
Sources and further reading
Set the right invoice review boundary
Tell us which invoices are routine, which need judgment and who approves sending today. We can scope a draft-first workflow and clear exception handling.
Discuss invoice approval See what our invoicing workflows service includes