Invoice Lifecycle: Stages from Draft to Payment
The invoice lifecycle follows an outgoing invoice from an approved draft through scheduling, sending, payment follow-up, settlement and archiving. Track the evidence and next action at each stage: a scheduled send, a client payment promise and a filed PDF each describe different events.
Free editable text file with a blank control sheet and a filled example. No signup required.
InvoiceAgent includes a 7-day free trial. No credit card required.
At a glance
Follow the invoice lifecycle from draft to payment with stage checks, a partial-payment example and a free editable invoice lifecycle control sheet.
Best for
Freelancers and service billing teams tracking client invoices from preparation to confirmed payment.
Evaluation method
Reviewed 2026-10-28
Original outgoing-invoice control sheet and fictional worked example. Product delivery, payment and follow-up behavior checked against the implementation on October 28, 2026. Worksheet stages are an operational model; they are not additional product statuses or measured customer results.
Using InvoiceAgent
Use InvoiceAgent to preview and schedule outgoing invoices, review delivery states, record eligible payments and control follow-ups. Keep agreement approvals, disputes and supporting evidence alongside the invoice.
Illustrative example
One USD 1,200 invoice, a partial payment and a dispute
- October 1 · draft and review
- Cedar Studio checks INV-120 v1 for Northstar Services against APP-120: USD 1,200, issued October 2, due October 16. The billing lead verifies the PDF, billing recipient and separate owner test.
- October 2 · scheduled, then sent
- The target is 09:00 SAST. Record SEND-120 only after observing the actual provider outcome. An accepted send does not prove the client read the message.
- October 9 · partially paid
- Confirm receipt PAY-401 and allocate USD 400 once. Remaining balance: USD 1,200 − USD 400 = USD 800. Do not keep asking for USD 1,200.
- October 16–17 · disputed and overdue
- The client questions USD 200 of the remaining USD 800; USD 600 is undisputed. The billing lead records the question, pauses eligible follow-ups and checks the actual pause. After the original due date, USD 800 remains open; the pause is not a Paid status.
- October 20–21 · resolved and settled
- Evidence RES-120 resolves the question with no change to the invoice total. Confirm PAY-402 for USD 800. Receipts of USD 400 + USD 800 reconcile to USD 1,200; outstanding balance is zero. Check the payment record and future reminder state.
- October 22 · retained
- Keep the exact sent PDF, SEND-120, both receipt references and RES-120 together. Filing the records did not settle the invoice; the confirmed payment allocation did.
Fictional single-currency example with no credits, fees, tax, interest or FX. Dates and evidence IDs illustrate the method, not actual sends or receipts. Resolve credits, excess receipts and currency differences separately before using the simple balance formula.
See the recorded product workflowInvoice lifecycle stages: evidence and the next action
| Stage | Evidence to keep | Next action |
|---|---|---|
| Draft | Agreed work, amount, currency, service period and invoice reference. | Resolve missing approvals or client requirements before release. |
| Reviewed | Approved PDF version, recipient and payment terms; separate test outcome. | Check the actual attachment and client route, then choose the send time. |
| Scheduled | Planned send date, timezone and current schedule state. | Check actual sending outcome; a planned time is not proof of sending. |
| Sent / open | Actual send/provider reference and the exact document sent. | Monitor exceptions and confirmed receipts. Sending does not establish inbox reading or payment. |
| Partially paid | Unique confirmed receipts and their allocation to this invoice. | Calculate the remaining balance; follow up only for the reconciled amount. |
| Overdue | Due date has passed and a balance remains under the agreed terms. | Review receipts, any dispute and the actual follow-up state before another message. |
| Dispute / agreed payment plan | Client question or approved plan, amount, owner and next review date. | Record the decision and check follow-up controls. A hold does not settle the balance. |
| Settled | Confirmed allocations and approved adjustments reconcile the full amount. | Verify the payment record and that future follow-ups are stopped. |
| Archived | Exact sent version plus delivery, receipt and exception references. | Retain retrieval and access details. An archive can also contain an invoice that is still open. |
Track three things, not just one status
For each invoice, keep document and delivery progress, money received, and the next follow-up decision visible. A single label cannot explain all three. An invoice may have been sent successfully while its balance remains open and its reminders are deliberately paused. Record each event with an owner and evidence rather than overwriting the history.
This page covers invoices you issue to clients. Incoming supplier-invoice approval is a separate accounts-payable workflow. The wider billing workflow also includes work acceptance and agreed terms before the invoice exists, while payment-cycle measurement counts elapsed time between specified dates. Use the lifecycle sheet to track an individual outgoing document through those handoffs.
InvoiceAgent uses Pending, Processing, Sent, Failed and Paid as invoice status labels. Preparation and review happen before delivery; the worksheet's Reviewed, Partially paid, Overdue and Archived categories do not add product statuses. A partially paid sent invoice keeps a separate recorded-paid amount and outstanding balance. A follow-up pause is a separate control. Review the actual record instead of assuming every worksheet row has a matching dashboard label.
In InvoiceAgent, successful sending records the send outcome and timestamp. A failed send needs its error reviewed. An uncertain delivery can remain Processing with a review message and automatic retries stopped; check existing send evidence before attempting a resend. A provider-accepted email is not proof of inbox placement, reading, client acceptance or receipt of funds.
For eligible sent invoices, confirmed manual payment records use the invoice billing currency. Partial payments reduce the balance; recording settlement marks the invoice Paid and cancels outstanding follow-ups. Wise-linked invoices use their provider reconciliation path to avoid counting payments twice. A client saying a transfer was initiated is supporting information to check, not a reason to invent a receipt or mark an invoice Paid.
Use this workflow when your main need is controlled outgoing invoice delivery and follow-up. Keep contract approvals, dispute decisions, credit authority and supporting payment evidence in your agreed records. The downloaded text file does not update InvoiceAgent or create an accounting ledger. Google Drive filing, when configured, preserves a copy under its sync policy; an archived copy does not prove settlement.
Quick context
Section
Concept pages that explain invoice automation, accounts receivable workflows, recurring billing, and international invoicing.
Best for
Freelancers and service billing teams tracking client invoices from preparation to confirmed payment.
Outcome
Use this page to move from general research into a calmer, more repeatable invoicing process.
Build a traceable lifecycle record
Establish one invoice identity
Record the client, invoice ID, currency, total, issue date, service period and payment deadline. Reference the approved work and document version. Resolve a missing PO, disputed charge or recipient requirement before treating the invoice as ready.
Separate review, scheduling and sending
Check the actual PDF and recipient. Keep the owner test result separate from the client send. Record the planned time and timezone, then add the actual send outcome when available. Assign a reviewer for failed or uncertain delivery instead of creating an unverified duplicate send.
Reconcile receipts before follow-up
For an invoice without adjustments, subtract confirmed amounts allocated once from its total. Record each unique receipt reference and date. Keep unknown, excess or different-currency receipts for review. In the example, a USD 400 receipt leaves USD 800, regardless of the original reminder amount.
Give exceptions an owner and next check
Write the disputed amount or approved plan, supporting evidence and next review date. Inspect and verify the actual follow-up pause. In InvoiceAgent, resuming follow-ups does not move pending reminder dates: review stages already due before resuming. Do not use Paid to suppress messages for an unsettled invoice.
Close the balance and retain the trail
Confirm final allocations and approved adjustments, verify settlement and future reminder cancellation, then retain the exact sent PDF and supporting records. If an invoice is still open when filed, preserve its balance, owner and next action visibly.
Preview the lifecycle control sheet
Replace the bracketed fields with your client’s details. The download also includes the filled example shown on this page.
OUTGOING INVOICE LIFECYCLE CONTROL SHEET Snapshot date / billing owner / backup: [details] Client / invoice ID / currency / service period: [details] Agreement / approved charges / recipient requirements: [references] Original invoice total / issue date / due date: [details] Current document version / approval evidence: [references] STAGE RECORD — retain earlier entries when the state changes Date and time / timezone | stage | evidence reference | owner | next action / review date [one row per transition; use actual events, not planned events] Suggested stages: draft / reviewed / scheduled / sent / open / partially paid / overdue / dispute or payment-plan hold / settled / archived These are worksheet categories, not a list of InvoiceAgent status labels. DELIVERY CHECK Approved PDF version / recipient / attachment reviewed: [details] Test recipient and test outcome (separate from client send): [details] Planned send / timezone / actual send evidence: [details] Provider outcome / delivery question / follow-up owner: [details] Uncertain or failed send: [check existing evidence before any resend] PAYMENT CHECK — one invoice and one currency Confirmed receipt ID | received date | amount allocated | evidence reference [one row per unique receipt; keep unclear or unallocated receipts separate] Original total: [amount] Confirmed receipts allocated once: [sum] Outstanding balance: [original total minus confirmed allocations] Approved credits, excess receipts or currency differences: [reconcile separately] Client transfer notice / promise (not confirmed receipt): [reference] EXCEPTION AND FOLLOW-UP CHECK Disputed amount / reason / evidence / owner: [details] Actual follow-up enabled or paused state / pending stages reviewed: [details] Pause or resume decision / authority / date: [details] Next manual check / owner: [details] Settlement evidence / remaining balance / final payment record: [details] Reminder state checked after settlement: [details] ARCHIVE CHECK Exact sent PDF / version / delivery record: [references] Receipt and adjustment evidence / unresolved items: [references] Archive location / access owner / next review: [details] Filing is separate from settlement; retain any open balance visibly. This sheet does not send, pause, settle or archive an invoice in any application.
Free resource
Keep evidence and next actions together
Editable text with a blank sheet and the filled USD 1,200 example. Adapt it to your actual billing records; it changes no invoice or reminder settings.
Download the control sheetWhere teams usually lose momentum.
Avoid this
Treating a scheduled or test email as the client send
Both are preparation evidence. Check the actual client send outcome and attachment. If delivery is uncertain, inspect existing records before deciding whether a resend is needed.
Avoid this
Counting a payment notice twice
A remittance message and a bank receipt can describe one payment. Confirm the funds and record their allocation once; keep a promise or initiated transfer separate from confirmed receipt.
Avoid this
Editing away the original document
After sending, follow the applicable correction and approval process. Preserve the original sent version and link any approved replacement or adjustment. Renaming or archiving a PDF does not change what the client received.
Move from reading about the workflow to running it.
InvoiceAgent is designed for the last mile of getting paid: scheduled invoice delivery, reminder timing, professional PDFs, and send-time FX conversion when global billing is involved.
Related topics
Find more invoicing and practical tools in the resources below.
Questions people usually have before changing the workflow.
What is the invoice lifecycle?
It is the progression of an outgoing invoice from preparation and review through scheduling, sending, payment follow-up, settlement and retention. Track the evidence, outstanding balance and next owner action at each stage.
Is a sent invoice the same as a paid invoice?
No. Sent records a delivery event. Payment requires confirmed receipts allocated to the invoice and reconciliation of the remaining balance. Email acceptance or a client payment promise does not establish settlement.
Where do partial payments fit?
They reduce the outstanding balance while the invoice remains open. A USD 1,200 invoice with USD 400 confirmed and allocated has USD 800 remaining if there are no adjustments. InvoiceAgent tracks recorded payments separately from its invoice status; Partially paid is a worksheet category here.
Does overdue mean the invoice failed to send?
No. Overdue means the payment deadline has passed with a balance remaining under the agreed terms. Failed describes a delivery problem. Check the actual due date, payment record and send evidence separately.
Does the sheet pause reminders or mark an invoice Paid?
No. It is an editable text record. Use the product's eligible payment and follow-up controls, then verify their actual state. Resuming InvoiceAgent follow-ups does not reschedule pending reminder dates.
Is archiving the last step for every invoice?
Retention usually follows settlement in a simple completed example, but a filed invoice can still be unpaid or disputed. Keep open balances and next actions visible. An archive location is not payment evidence.
Related pages
Useful tools
Decision pages
Compare software by the delivery, payment, and follow-up features you need.