Keep the approved scope
If the client accepted the quote, keep the same work description so the invoice matches the agreement they already saw.
A quote becomes an invoice when approval is done and the document needs to request real payment. Keep the parts that already worked, such as the client details and approved line items, then replace the quote language with invoice details like number, date, due date, and payment terms.
If the client accepted the quote, keep the same work description so the invoice matches the agreement they already saw.
The invoice should carry the same pricing logic unless something specific changed and was confirmed separately.
Use the same client name, project reference, and any job number that helps the invoice map cleanly back to the approved quote.
Replace quote-style wording with an invoice number, issue date, due date, and clear payment terms so the document is ready to collect payment.
Words that belong to the quote stage, such as validity or approval framing, should not fight the invoice's billing purpose.
If the quote is approved but the workflow still needs a deposit or pre-final payment request, proforma may belong before the final invoice.
Keep the approved client details, scope, line items, and pricing so the invoice still matches the quote the client accepted.
Swap approval wording for payment wording, add the invoice number and due date, and make the document behave like a real billing record.
Use proforma when the quote is approved but the workflow still needs a structured prepayment or pre-final billing document before the final invoice should exist.
Yes. Reusing the same line items is usually the cleanest path as long as the final invoice still reflects the approved scope and totals.
Keep the approved scope, add the invoice details, and only pause for proforma if the workflow still needs a middle payment step.