Key Takeaways

• Draft is the only state where correcting an invoice costs nothing. After finalization, a correction needs a credit memo or a void and reissue.

• Finalization is the event that assigns the invoice number, locks the amounts, and starts the payment clock.

• Usage-based billing needs a longer draft window than subscription billing, because subscription amounts are known on day one and metered amounts aren't.

• A draft invoice and an invoice preview are different objects: the draft persists and becomes the real document, the preview is a calculation that's thrown away.

• Holding a draft for two to five days after the period closes catches most late usage without pushing the due date into the next cycle.

What can you change while an invoice is in draft?

Effectively everything, which is the entire point of the state. Line items, quantities, prices, credits, discounts, the billed entity, and the currency all stay mutable until finalization, and none of those changes leave a correction trail because nothing has been issued.

What each state allows:

Finalization is a one-way door, and the things it does are worth knowing precisely:

1. Assigns the next number in the invoice sequence, which can't be reused.

2. Freezes line items, quantities, and rates as they stood at that instant.

3. Snapshots the tax treatment, the billed entity, and the currency.

4. Starts the payment terms clock, making the due date real.

5. Emits the event that triggers delivery, dunning, and revenue recognition.

Step 1 is why editing a finalized invoice isn't an option even when the system technically allows it. The number is a sequential document of record, and changing what sits behind an already-issued number is an audit finding.

How long should an invoice stay in draft?

Long enough for usage to settle, and no longer. For metered billing that's typically two to five days after the period closes, set by how late your events actually arrive rather than by a number that sounded reasonable.

What decides the window:

• Event arrival distribution. Measure the tail. If 99.9% of events for a period land within 36 hours of the period end, a two-day draft window covers you and a five-day one just delays cash.

• The watermark. Systems that track a watermark can finalize as soon as it passes the period boundary, which is more precise than a fixed delay.

• Payment terms. A five-day draft on net-30 terms means collecting on day 65 rather than day 60. That's real working capital under billing in arrears.

• Reconciliation. Any check comparing metered usage against the invoice has to finish inside the draft window, or it's finding problems too late to fix cheaply.

Finalizing too early is the more expensive mistake. An invoice finalized on day 1 and corrected on day 3 costs a credit memo, a customer conversation, and a ticket. Waiting two days costs two days of float, and I'd take the float. The automated billing software guide covers scheduling the close.

Draft invoice vs invoice preview: what's the difference?

A draft persists and becomes the finalized document. A preview is a calculation you run and discard. Systems that offer both use them for different jobs, and conflating them leads teams to expect a preview to hold state it never had.

The practical differences:

• Persistence. The draft has an ID and a lifecycle. The preview exists for the duration of the request.

• Timing. A draft usually appears when the period closes. A preview can run mid-period, answering "what would this customer owe if we billed right now".

• Mutability. You edit a draft. You re-run a preview with different inputs.

• Audience. Drafts are internal until finalization. Previews often go to customers, powering the "current month estimate" figure in a dashboard.

• Effect. Finalizing a draft creates an obligation. Running a preview creates nothing.

Mid-period previews are how customers see spend before the invoice arrives, which is the single best way to prevent bill shock. Flexprice's Billing and Invoicing supports previewing an invoice before it finalizes, which is the capability that makes both the internal check and the customer-facing estimate possible from the same calculation.

Related terms

The draft window exists to absorb the problems these terms describe.

• Billing in arrears is why a draft window is necessary at all.

• Late-arriving events are what the draft window is holding open for.

• Re-rating is what you do when usage changes after the draft has already closed.

• Credit memo is the instrument for corrections you didn't catch in draft.

• Billing vs invoicing explains why finalization is the handoff between two different concerns.

FAQ

Can you delete a draft invoice?

Yes, and that's one of the properties that defines the state. A draft has no assigned number and no legal standing, so deleting one leaves no gap in the invoice sequence and needs no explanation. Deleting a finalized invoice isn't an option in a compliant system; you void it, and the number stays on record.

Does the customer see a draft invoice?

Usually not, and they shouldn't by default, because the amounts can still change and showing a number that later moves creates a dispute. Some teams do expose drafts to enterprise customers deliberately, as a review window before finalization, which works when both sides understand the number isn't committed.

What triggers finalization?

Either a schedule or an explicit action. Most systems finalize automatically a configured number of days after the period ends, and most also allow finalizing on demand, which finance uses to close a period early or to issue an invoice a customer is waiting on.

Can a draft invoice have a zero total?

Yes, and it's common for usage-based plans where a customer consumed nothing in the period. Whether you finalize and send it is a policy choice. Sending zero invoices gives customers a complete record, and suppressing them reduces noise.