The client paid. You saw the confirmation. Then an email arrives from the payment gateway: your settlement is on hold, please share an invoice or proof of the service provided.
You do not have an invoice. You have a WhatsApp chat, a delivered file and a client who said "done, paid". Until this email, nobody had ever asked for anything more.
For some freelancers this is how the first invoice happens. It is not planned. A payment gateway holding money and asking for an invoice, or a client's accounts department refusing to release a payment without one, forces it.
The quick answer
They want to see what the payment was for. Reply once, with everything: a real invoice for the work you did, something from the client confirming the work, and proof that you delivered it.
Make the invoice honestly. Date it the day you actually make it, state the delivery date and payment date as separate lines, and never backdate it or invent details. Whether the documents are enough is the gateway's or bank's decision. No invoice tool decides that for them, mine included.
What is usually being asked for, and why
The wording changes, but the request is nearly always the same: show us what this payment was for.
A gateway sits between your client and your bank account. It collects the money, holds it briefly, then settles it to you. While it holds the money, it has its own checks to run. If a payment looks unusual for your account, such as a larger amount than usual, a new kind of customer or a new account with little history, it can pause the settlement and ask for documents.
A client's accounts department asks for a different reason and ends up in the same place. They cannot record a payment in the company's books without a document that says who was paid, how much, and for what. No invoice, no payment.
In both cases the person asking is not accusing you of anything. They need paper, and the usual story is real work, a real client, and nothing on paper to show for it.
Reply once, with everything
Do not send a one-line reply and wait, and do not send five replies either: put it all in one message on the same ticket or email thread.
Hi, replying to your request on ticket [number] regarding the payment of ₹18,000 received on 28 September 2026.
I am a freelance [designer / developer / writer] working as an individual. This payment was for [one line describing the work] delivered to [client name].
Attached:
- Invoice [number] for this work
- Written confirmation from the client that the work was ordered and received
- Proof of delivery: [link / screenshot / email]
Please let me know if you need anything further to complete the review.
Keep the tone flat and factual. If they ask for KYC documents as well, complete what they ask, honestly. I am not going to suggest ways around a verification step, and you should be wary of anyone who does.
What a real invoice needs to show
If you have never made one, an invoice is a short document that answers six questions. Use this as a checklist.
1. Who is billing Your name (as on your PAN and bank account)
Your PAN, or your GST number if you have one
2. Who is billed Client's name or company name
3. What for A plain description of what you delivered
4. When Invoice date, plus the date the work was delivered
5. How much The amount, in rupees
6. Which invoice An invoice number you have not used before
A few notes on each.
Your name. Use the same name that is on your PAN and your bank account.
PAN or GST number. Add your GST number only if you are registered. If you are not, do not charge GST and do not write a number that is not yours. Check with a CA if you are unsure whether you need to register. If you are GST registered, a tax invoice needs more than this list: the tax split into CGST and SGST (or IGST), a service code (SAC), and your client's GSTIN if they have one. Ask your CA to check your format.
What was delivered. "Design work" is weak. "Logo and brand guide for Sneha's bakery, 3 concepts, final files delivered" is a description a stranger can follow.
Amount. It should match what was actually paid. If the client paid ₹18,000, the invoice says ₹18,000.
Invoice number. Start a simple sequence and stick to it. INV26-001 is fine.
How to make it honestly for work already done
This is the part people get wrong under pressure.
The work was finished two weeks ago. The payment came a few days ago. You are making the invoice today. The temptation is to date the invoice two weeks back so it "looks right".
Do not. Date the invoice the day you actually make it. Then state the real timeline on the invoice itself:
Invoice date: 3 October 2026
Work delivered: 19 September 2026
Payment received: ₹18,000 on 28 September 2026
That is a truthful document. It says what happened, in order, and it lines up with the payment date and your chat history.
A backdated invoice says something untrue about when it was created. If its dates clash with your chats, your file timestamps or the client's records, a routine document request becomes a real problem. It can also cause trouble later in the client's books and your own tax records. I have written about a related situation in a client asked me to backdate an invoice.
If you are GST registered, there are extra rules. A tax invoice for a service is normally due within 30 days of delivering it, and the GST can fall due from the date you were paid, or from the date of delivery if the invoice is late. A backdated date does not fix a late invoice. Ask your CA how to report it.
The same goes for the content. Do not inflate the description, split one payment into several invoices, or add a client address you are guessing at. If you do not know something, ask the client. Every line should be something you could back up if asked.
What else they may ask for
An invoice is something you wrote yourself. A reviewer will often want something from the other side as well.
Confirmation from the client. An agreement, a quote the client accepted, an email, or a chat where they ordered the work and agreed the price. If none of that is tidy, ask the client for a short written reply now:
Hi Sneha, the payment gateway is reviewing the ₹18,000 payment and has asked for proof of the work. Could you reply to this message confirming that you hired me for the logo and brand guide, that it was delivered on 19 September, and that you paid ₹18,000 on 28 September? A two-line reply is enough. Thank you.
Their reply, dated today, confirms what happened.
Proof of delivery. The email or message where you sent the final files, a shared-folder link, a live website URL, a screenshot of the published post.
Send screenshots with dates visible. Do not edit or crop out anything that changes the meaning.
What to do while you wait
- Keep one thread. Reply on the same ticket. Opening new tickets for the same hold usually slows things down.
- Note the ticket number and the date of every reply. If you have to follow up, quote them.
- Tell the client plainly. They paid in good faith. A short "the gateway is reviewing it, nothing needed from you beyond that one confirmation" keeps them calm.
- Do not plan around a date. How long a review takes, and whether the documents are accepted, is up to the gateway or bank.
- Follow up once, politely, if you hear nothing after the timeline they gave you.
How to avoid this next time
Two habits remove most of the risk.
Invoice before the payment, not after. If the invoice exists before the money moves, every payment you receive already has a document behind it. When anyone asks, you forward a PDF.
Let clients pay your own UPI ID directly. For a domestic client paying in rupees, a UPI payment goes from their bank to yours. Nobody sits in the middle holding it. I have compared the two routes in UPI payment link vs payment gateway, including when a gateway is the right call. If asking feels awkward, there are scripts in how to ask a client to pay by UPI.
Direct UPI is not a free pass. Your bank can still ask questions about any account. That is one more reason to have an invoice behind every payment.
This is where Riffit fits, and since I built it I will keep the claims small. You can create an invoice from a short form in WhatsApp in under two minutes, or on the web dashboard. Riffit dates every invoice the day you make it, and each line has a details field where you can note when the work was delivered. The invoice carries a UPI link and QR that pay straight to the UPI ID saved in your profile. Riffit never touches the money. It also does not detect payments, so you mark the invoice paid yourself. Free covers 5 invoices/month.
To be clear about the limit: I cannot tell you a Riffit invoice will satisfy a gateway's or a bank's review. That decision is theirs. What an invoice does is state truthfully who did what for whom and for how much.
Make the invoice before the payment next time. Under two minutes from WhatsApp, with a UPI link and QR that pay straight to your own UPI ID.Try Riffit freeIf it is the client's accounts department, not a gateway
The steps are the same, with one difference: ask what they need on the invoice before you make it.
Hi, I am preparing the invoice for the ₹18,000 payment. Could you tell me the exact company name and address to bill, and anything else your accounts department needs on it, such as a PO number or my PAN?
One message saves you from making the invoice twice.
FAQ
The gateway wants to see what the payment was for. It holds money between your client and your bank account and runs its own checks before settling. Reply once with an invoice for the work, a confirmation from the client, and proof of delivery. Whether that is enough is the decision of the gateway.
Yes, as long as it is truthful. Date the invoice the day you actually make it, and state the delivery date and the payment date as separate lines. Do not backdate it and do not invent details.
Six things: your name and PAN, or your GST number if you have one; the name of the client; a plain description of what you delivered; the invoice date and delivery date; the amount; and an invoice number. Add a GST number only if you are registered. If you are, a tax invoice also needs the CGST and SGST (or IGST) split, a SAC code and the GSTIN of the client if they have one.
The date you actually make it. Write the delivery date and the payment date on the invoice as separate lines. Do not backdate it: a backdated invoice states something untrue about when it was created, and it can clash with your chats and the records of the client.
Send the invoice before the client pays, so every payment has a document behind it. For clients in India paying in rupees, ask them to pay your own UPI ID directly so nobody holds the money in between. Your bank can still ask questions about any account, so keep the invoice either way.
I cannot promise that. Whether any document satisfies a review is the decision of the gateway or bank. Riffit lets you create an invoice from WhatsApp in under two minutes, with a UPI link and QR that pay straight to your own UPI ID. Riffit never touches the money.