Invoice vs Quote: What Is the Difference?

A client asks you to send them a quote. You send an invoice by mistake. Or you send a quote when the client was ready to pay and waiting for an invoice. Neither mistake feels catastrophic in the moment, but both create confusion and delay. Understanding the difference, and knowing which document to send at which stage, is one of the more useful basics of running a freelance business.

The short version

A quote comes before the work. An invoice comes after. A quote says "here is what I will do and what it will cost." An invoice says "I have done this, please pay me now."

They sit at opposite ends of the same transaction. A project often moves from quote to invoice in a predictable sequence: you discuss the scope, you send a quote, the client accepts, you do the work, you send an invoice. Both documents can refer to the same project and the same numbers. But they are issued at different moments and serve different legal purposes.

What a quote is and what it commits you to

A quote is a formal offer. When you send a quote, you are saying: I will do this specific scope of work for this specific price. That price is the one the client can hold you to if they accept the quote.

The key word is if. Until the client accepts, nothing has been agreed. You can withdraw or amend a quote at any time before acceptance. Most quotes include an expiry date, typically two to four weeks, after which the price is no longer guaranteed.

Once a client accepts your quote, either in writing or by asking you to proceed with the work, you have an agreement. The price in the quote is the price you are expected to charge. If the scope changes after acceptance, that is a separate conversation, and any change in price should be confirmed in writing before you do the extra work.

Whether a quote is legally binding after acceptance depends on the jurisdiction and the specifics of the situation. In most countries, an accepted quote constitutes a contract even without a separate signed document. The key elements are offer (your quote), acceptance (their agreement), and consideration (the agreed payment). If all three are present, you generally have an enforceable agreement.

What an invoice is and what it commits the client to

An invoice is a demand for payment. It refers to work that has already been agreed and usually already been done, or to a milestone that has been reached. When you send an invoice, you are not proposing anything. You are stating what is owed.

An invoice creates a legal obligation for the client to pay, provided the work was done as agreed. It has a due date. It is a financial document that both sides keep in their accounts. It can be used as evidence in a dispute or a legal claim.

You should only send an invoice when you are entitled to payment: after completing the work, after reaching an agreed milestone, or at the start of a project if you agreed to a deposit upfront.

When people get confused between the two

The most common mistake is sending a quote when the client is ready to pay. This happens when a freelancer creates a quote document, realizes the client has already accepted verbally, and sends that document anyway thinking it functions as an invoice. It does not. A quote tells the client the price. An invoice tells the client the price is now due.

A client who receives a quote when they are expecting an invoice will often wait, assuming the invoice is coming separately. The result is a confusing exchange: "did you receive my invoice?" "I only received a quote."

The reverse also happens. A freelancer who has not yet confirmed the scope sends an invoice before the client has agreed to the price or the work. That creates conflict immediately, because the client is receiving a demand for payment for something they did not formally sign off on.

How they work together in practice

A typical project looks like this. You have a call with a client who runs a small video production agency. You discuss a two-day shoot and editing package. You send a quote within 24 hours, listing what is included, the price, and a validity date.

The client replies: "This looks good, let us go ahead." You confirm the start date and send an invoice for the deposit, typically 25% to 50% of the total. You do the work. You deliver the files. You send the final invoice for the balance.

The quote and the invoices all reference the same project. The numbers match. The scope description matches. The quote is what created the agreement; the invoices are what collected the money.

You can use the quote generator to create the proposal and the invoice tool to collect payment once the work is done. Keeping these as separate documents from the beginning avoids any confusion about what is a proposal and what is a bill.

If you ever genuinely need to combine the two functions, which can happen for very small or very quick jobs, the safest approach is to note on the document that it is a quote which becomes a valid invoice upon acceptance, with the accepted amount due by a specified date. This is not standard, and many clients find it confusing. Two separate documents is almost always cleaner.

---

Related articles

• What Is a Purchase Order and When Do You Actually Need One?
• How to Write a Quote That Clients Actually Accept