Buyer requests a pro forma invoice: check the order scope before sending

A buyer has discussed products in chat and now asks for a pro forma invoice. One colleague sees a ready-to-pay order; another copies an old document and changes the customer name. Both can miss the unresolved details that determine what the business is actually offering.

Before sending the document, reconcile it with the current conversation. Confirm the intended buyer, the exact order scope and the terms your business has approved. A request for an invoice is useful progress, but it is not evidence that payment has arrived.

Understand the document request

The U.S. International Trade Administration describes a pro forma invoice as a quotation in invoice format. Its guidance explains that buyers may need it for steps such as an import license or arranging a letter of credit. A document request can therefore serve a purchasing or administrative step without proving that every buying decision is complete.

Ask what information the buyer needs to proceed when the purpose is unclear. Avoid requesting unnecessary personal information through chat. Use your authorized document process for the buyer details required by the transaction, and involve the responsible commercial or logistics person when the requested terms are uncertain.

Reconcile six fields against the current offer

1. Parties and reference: verify the intended buyer and seller details and the correct inquiry or quotation reference.
2. Product scope: confirm product references, variants, relevant specifications and quantities. An image alone may not identify a final selection.
3. Price basis: check the approved unit amounts, totals, currency and what the quoted amounts include.
4. Commercial terms: verify the approved payment and delivery terms, including the named delivery point where applicable.
5. Dates and open checks: distinguish a quotation validity date and an estimated shipping date from a confirmed operational commitment.
6. Version and approval: identify the current document version and the person authorized to issue it.

These six review areas are our workflow recommendation. The ITA guidance lists quotation details including parties, items, prices, terms and dates; it does not make this checklist a universal legal or customs requirement. Apply the requirements relevant to the actual transaction with appropriate professional support.

Use the same order scope throughout the handoff

Consider a hypothetical buyer who discussed 40 jackets, then requested custom labels before asking for the document. Reusing the original standard-product amount would omit the unresolved labeling requirement. The useful response is to confirm whether the invoice should cover the standard selection or the custom version, then obtain the applicable approved terms.

In the same inquiry, an internal draft can show that the labeling check remains pending. It should not silently become a final offer. If the business cannot issue an accurate document yet, tell the buyer which decision is missing and who will resolve it. Continue the known part of the request without inventing a completion date.

Control revisions after the invoice is sent

Record which version was actually sent, when it was issued and the scope it covers. When a buyer changes quantity, destination or a product specification, return the changed fields for review. Explain the revision so the buyer can identify the current offer. An old attachment remaining in the chat should not become the authority for a changed transaction.

Keep document issued, buyer response, order accepted under your process and verified payment as separate states. A payment screenshot or a message saying payment was arranged needs checking through the business's authorized financial source. Do not promise production release or dispatch based only on conversational evidence.

Give the AI a document-ready handoff

HireSalesAI can clarify purchasing requirements and retain context for a human handoff. Configure which approved commercial information it may explain, and provide the owner of document issuance. This guide does not establish automatic accounting, payment verification or invoice generation integrations.

Use a sales handoff summary containing the selected scope, approved terms and unresolved decisions. When evaluating the process, compare documents returned for corrections separately from documents accepted and verified payments. With no readable financial outcomes, do not claim that issuing more invoices increased revenue.