Quote to invoice workflow — commercial lifecycle

From offer to payment claim

Most B2B revenue follows a predictable commercial arc: you propose terms, the client agrees, you deliver, and you invoice. That sequence sounds obvious, yet many accounting and VAT problems trace back to skipping or blurring steps — treating a quote like an invoice, reusing numbers across document types, or sending Peppol messages at the wrong stage.

This article walks through the quote → acceptance → delivery → invoice lifecycle as a pan-European commercial pattern, with Belgian practice notes where they clarify VAT and e-invoicing expectations. For how each document type differs in purpose, see Invoice, credit note, and quote.

Stage 1: The quote as a commercial offer

A quote (devis, offerte, Angebot) is an offer: prices, scope, validity period, and often payment or delivery assumptions. It invites acceptance; it does not by itself create a VAT event or a receivable in your books.

Good quote practice:

• State a validity date so stale prices are not silently assumed
• Distinguish estimates from firm offers where your business model requires it
• Keep quotes in a separate numbering sequence from invoices (or clearly prefixed codes)
• Record who accepted and when — email confirmation, signed PDF, portal click, or contract reference

Quotes are normally exchanged as PDF, email, or in-app previews. They are not Peppol billing documents under Peppol BIS Billing profiles. Sending a quote through a Peppol Access Point would be unusual and is not what the Belgian structured e-invoicing mandate targets.

Stage 2: Acceptance — when the deal becomes real

Acceptance is the hinge between marketing and execution. Legally and operationally, something changes when the client agrees: you may have a contractual obligation to deliver, and your internal project or order record should open.

Capture acceptance explicitly:

Acceptance alone still does not replace an invoice. Even when a deposit is due on signature, Belgian VAT practice typically expects a proper invoice (or in some cases a specific advance invoice document) with mandatory mentions — not merely the quote re-labelled.

Stage 3: Delivery — goods or services supplied

Delivery is when the taxable supply happens (or progresses, for long projects). Your operations team marks work complete, goods ship, or milestones are reached. Accounting needs this signal to know when to invoice, especially where VAT time of supply rules link to delivery rather than quote date.

For project businesses, align:

• Timesheets or milestone sign-off with what the quote described
• Partial delivery with partial invoicing where contracts allow
• Change orders with revised quotes or addenda before extra work is invoiced

Invoicing before delivery can be valid in some cases (prepayments, specific industries), but it should be a conscious choice with correct VAT treatment — not an accidental early invoice because the quote was converted too soon.

Stage 4: The invoice — payment claim and VAT document

The invoice is the document that claims payment and, for VAT-liable businesses, serves as core VAT evidence. It must carry legal mentions (parties, description, dates, amounts, VAT breakdown, continuous numbering, and other fields depending on jurisdiction and regime).

This is the stage where Peppol structured exchange enters for many Belgian B2B relationships from 1 January 2026: domestic invoices between Belgian VAT-liable parties must travel as structured electronic documents on Peppol, not as informal PDF email alone. The quote and acceptance trail remain internal or conventional; the invoice is what crosses the Peppol network when the mandate applies.

If the delivered scope differs from the quote, issue the invoice against what was actually supplied, with lines that match delivery records. Material deviations should be reflected in an updated quote or change note before invoicing, preserving audit clarity.

Numbering discipline across the lifecycle

Pan-European practice — and Belgian audit expectation in particular — favours strict, gap-free numbering for invoices. Quotes and pro forma documents should not consume invoice numbers or share the same sequence without clear prefixes.

Recommended discipline:

1. One invoice sequence per legal entity (or per branch only where formally separated)
2. Separate credit note sequence linked back to original invoice numbers
3. Quote codes that never look like final invoice numbers to clients or tax reviewers
4. No retroactive edits to issued invoices — use credit notes and re-issue

Structured e-invoicing reinforces this: Peppol payloads expose invoice numbers and issue dates to counterparties and Access Points immediately. Renumbering or silently editing a sent invoice creates reconciliation pain on both sides.

When Peppol applies — invoice stage only

Peppol BIS Billing covers invoices and credit notes, not preliminary commercial offers. Your workflow should assume:

• Quotes and estimates stay in your invoicing or CRM tool until converted
• Conversion to invoice generates the structured UBL (or equivalent) payload when required
• Credit notes follow the same Peppol path when correcting a sent invoice

If you only register on Peppol for outbound invoices but skip inbound reception, supplier-side compliance is equally affected by the mandate — but that is separate from the quote stage. The key point for this lifecycle: do not postpone Peppol readiness until after you have been issuing informal PDFs as if they were compliant B2B invoices.

Cross-border B2B outside the Belgian domestic mandate may still use Peppol voluntarily or by counterparty policy; quotes remain outside that exchange either way.

Belgian practice notes

Belgian SMEs commonly:

• Send a French or Dutch PDF quote, receive oral or email acceptance, then issue a facture / factuur after work completion
• Use advance invoices for deposits; these are invoices, not quotes, with their own VAT timing rules
• Rely on continuous invoice numbering checked during VAT audit
• From 2026, route B2B invoices through an Access Point while keeping quotes in traditional channels

When a client asks to "invoice exactly as the quote," ensure the invoice duplicates line structure but uses invoice metadata (invoice date, invoice number, Peppol document type) — not a quote template with a new title.

A workflow that scales

A robust end-to-end process:

1. Issue quote with validity and clear scope
2. Log acceptance and any PO reference
3. Deliver and confirm completion internally
4. Generate invoice from accepted quote + delivery data
5. Send via Peppol when the Belgian obligation (or counterparty requirement) applies
6. If amounts change after invoicing, issue a credit note and a corrected invoice rather than editing the original

OrdoGrid models this lifecycle so quotes can convert to invoices without re-keying, while keeping document types and numbering rules separate. That separation protects VAT evidence and Peppol compliance even when the commercial content looks identical on screen.

Related reading

For document definitions and credit note behaviour, continue with Invoice, credit note, and quote — Belgian practice. For the legal scope of structured exchange at invoice stage, see the Belgian e-invoicing obligation (2026).

Tax invoice

A formal billing document that records a supply of goods or services, claims payment, and — for VAT-liable businesses — serves as primary VAT evidence. Distinct from a quote or pro forma offer.