Quotation comes before commitment
A quotation is usually sent before work starts or before the customer confirms the price. It is there to define scope, pricing, and approval terms.
Primary keyword: invoice vs quotation
Linkable asset
Invoice vs Quotation
An invoice and a quotation are closely related, but they do different jobs. Use this comparison when you need a fast answer on which document to send first, what each one should contain, and what usually happens after a quotation is accepted.
Invoice requests payment
An invoice is sent when it is time to bill for completed work, an agreed deposit, a milestone, or a recurring billing period.
They should not be swapped casually
Using an invoice where a quotation is expected can make the process feel premature. Using a quotation after work is done can delay payment collection.
The handoff should be clear
Once a quotation is accepted, the next step is usually to create an invoice using the agreed scope, pricing, and customer details.
Use an invoice when these are true
If most of these signals are true, you are usually past the quotation stage and into billing.
The work has been completed, partially completed, or reached a billable milestone.
The price has already been agreed with the customer.
You are formally requesting payment now, not only proposing terms.
You need an invoice number, due date, and payment instructions on the document.
The customer needs a payable document for accounts processing.
Invoice vs quotation quick comparison
Use this as the short reference version when you need to explain the difference without rewriting the process every time.
Topic
Invoice
Quotation
Primary purpose
Request payment for agreed work, products, or milestones.
Propose scope, pricing, and terms before billing starts.
Typical timing
After work is completed, partially completed, or billable now.
Before work begins or before the customer approves the job.
Payment expectation
Includes due date and payment instructions because money is now due.
Usually does not request immediate payment unless tied to an approval or deposit workflow.
Pricing flexibility
Reflects agreed charges and should not feel exploratory.
Can still be reviewed, negotiated, accepted, or rejected.
Document outcome
Moves into payment, reconciliation, and reminder workflows.
Leads to acceptance, revision, rejection, or conversion into an invoice.
Quick comparison reference
Quotation first, invoice second in most custom-service workflows.
Quotation helps win approval; invoice helps collect payment.
Accepted quotations often become the source for the final invoice details.
Invoices need payment instructions and due dates; quotations usually focus on scope and offer terms.
Common mistakes
Problems to avoid before you send the invoice.
A supporting page should reduce hesitation, not just add words. These are the issues that most often make an invoice feel unfinished or harder to approve.
Sending an invoice before the customer has approved the quoted scope or price.
Treating a quotation like a payment request even though the billing stage has not started.
Letting the final invoice drift away from the scope or pricing the quotation already established.
Next step
Turn this guidance into a ready-to-send invoice.
The guide helps you understand the structure. When you are ready to create the actual invoice, move into the SensIn invoice generator so numbering, totals, and PDF-ready output are easier to manage.
Create the final invoice in SensInRelated pages