Invoice vs Receipt: The Difference, Timing and Why Both Matter

If you export services from India, you need both ends of this pair, and one of them is special.

You send an invoice to request payment, and you need proof once it arrives, but your proof is not an ordinary receipt. It is the FIRA, the document that shows your export earnings were realised.

Here is the short answer. An invoice is a request for payment you send before you are paid. A receipt is proof of payment you issue after the money arrives. Invoice comes first and asks for the money, receipt comes last and confirms it.

They are two ends of the same transaction, not alternatives. For a cross-border sale, the request is an export invoice, and the proof of an inward payment is a specific compliance document, not a shop-style receipt.

That timing, before payment versus after, is the whole distinction, and it decides which document you need at any moment. It is a different split from invoice vs bill, where the two words describe the same pre-payment document from two sides.

The table below sets the two documents side by side, with the detail underneath.

An invoice is the document a seller sends to ask for payment. It comes before the money changes hands, and it sets out what was delivered, how much is owed, and the terms for paying, such as the due date.

It is both a request and the seller's formal record that a sale took place, carrying a unique invoice number. Because it is issued upfront, an invoice is forward-looking: here is what you owe, and here is how and when to pay it.

An unpaid invoice stays an open item on the books until it is settled. For services exporters, that document is usually an export invoice, built for a cross-border sale and often marked as an export of services under GST, zero-rated.

A receipt is the document that confirms payment has been made. It comes after the money arrives, and it serves as proof for both sides that the amount was paid and the obligation is cleared.

A shop receipt is the everyday example, handed over the moment you pay. A receipt is backward-looking: it records a completed event, this much was paid, on this date, by this method.

Where an invoice asks, a receipt confirms. For a buyer it is proof of purchase; for a seller it closes the transaction. It never carries a due date, because there is nothing left to pay.

The cleanest way to hold the two apart is the transaction timeline.

• The invoice is the before: issued when work is delivered, requesting payment, carrying terms and a due date.
• The receipt is the after: issued once payment lands, confirming it, with no due date because the money is in.
• An invoice can go unpaid, which is why it needs terms. A receipt only exists because payment already happened.
• Together they document the full arc of a sale, the request and the settlement, which is why business records usually keep both.

The contents follow the purpose, so each carries different fields.

An invoice should carry:

• A unique invoice number and the invoice date.
• Seller and buyer details, and for exports, the client’s country and currency.
• An itemised list of goods or services, with the amount due including any tax.
• The payment terms and due date. Under GST, a tax invoice must also show the tax charged so the buyer can claim ITC in GST.

A receipt should carry:

• The amount actually paid and the date of payment.
• The payment method used.
• A reference to the invoice it settles, so the two can be matched on your remittance advice.

Not for most business purposes, because they prove different things. An invoice proves an amount is owed and supports terms, tax and, under GST, input tax credit. A receipt only proves an amount was paid.

For a simple over-the-counter sale, a single document can sometimes serve both roles, requesting and confirming payment at once. But in B2B and export work, where payment follows delivery on terms, you generally need both.

Relying on a receipt alone leaves gaps in your records and your GST trail. The invoice establishes the tax position; the payment proof closes it.

For an Indian exporter, an ordinary receipt is not enough on the payment side, which quietly complicates international payments for IT ITeS. When money comes in from abroad, the compliance system wants proof of that specific inward foreign remittance, not just an acknowledgement that a client paid.

• That proof is the Foreign Inward Remittance Advice (FIRA), or the related certificate, issued against the payment.
• It is what your bank and the RBI’s systems use to confirm the realisation and repatriation of export proceeds.
• It is also what supports a FIRC for GST refund on a zero-rated export.

So the exporter’s version of a receipt is a specific document, and getting it reliably matters. The FIRC vs FIRA distinction explains which is which.

Example: A Chennai firm invoices a US client $5,000 and receives it a month later. A PayPal-style “payment received” note is not enough for compliance.

The firm needs the FIRA showing that $5,000 came in as an export receipt, so its books, its EDPMS entry and its GST refund all line up.

This is where Xflow closes the loop. You can raise and send invoices to overseas clients, and when they pay, funds settle into receiving accounts linked to your Indian bank account, typically the next business day, at the live mid-market rate.

The eFIRA and payment advice are auto-issued as your proof of the inward remittance, and Xflow holds final RBI PA-CB authorisation for exports and imports, as of February 2026.

Invoice and receipt are two stages of one transaction, split by timing.

• Invoice comes first: it requests payment and states what is owed, with terms and, under GST, the tax charged.
• Receipt comes last: it confirms payment was made, with the amount, date and method.

You usually need both to keep clean records. As an exporter, remember that your payment proof is a specific document, the FIRA, not just an ordinary receipt.