Collect placement fees in India without a rekeyed invoice

The build covers GST invoice fields on placement billing: the supplier and recipient GSTIN, the place of supply, the applicable SAC code for recruitment services, and the CGST, SGST or IGST split that follows from whether the client is in your own state or another one. Whether a given invoice is correct remains a matter for your chartered accountant; what the product does is hold and carry the fields.

That distinction is the honest one. We are not claiming that Surhires makes your invoicing compliant, because compliance depends on your registration, your treatment and your filings. The capability statement is that the fields exist, they are configured per client entity, and what is sent is what you set.

A client in India commonly deducts tax at source before paying a recruitment invoice. The money that arrives is less than the money that was billed, and that gap is not a shortfall, a dispute or a write-off. A CRM built only for US and UK billing treats it as an underpayment and leaves every Indian placement showing a balance that will never be collected.

Recording the deduction against the placement means the receivable reflects what will actually arrive, and the deducted amount is tracked as something to be reconciled against a tax credit rather than chased as a debt. It is a small piece of modelling that decides whether the aged debtor report is usable at all on an Indian desk.

The same applies to clients who settle a single fee in instalments. What matters is that the placement shows the gross fee, the deductions, the amounts received and the balance that is genuinely outstanding. An owner reading the pipeline should be able to tell the difference between a client who is late and a client who has already paid everything they were ever going to pay directly.

Razorpay is the sensible target because it covers the methods Indian clients pay by: UPI, net banking, cards and NEFT or RTGS references. A payment link that only accepts cards would be close to useless for a mid-sized Indian client, where a UPI collect request or a bank transfer against an invoice reference is the normal path.

The Wave 1 scope is the same as elsewhere. A payment link raised against a specific placement invoice, and the resulting payment reconciled back to that invoice and the placement. Payouts, vendor payments and contractor disbursement are not in scope, and they are not what recruitment software should be doing.

Raise the placement record and its billing detail in Surhires, then raise the tax invoice in your accounting package where your numbering series and your GST configuration already live. Create the collection link in your own Razorpay dashboard and send it with the invoice. Then record the invoice number, the payment date and any TDS deducted back on the placement.

That last step takes under a minute and it is what makes the placement record tell the truth. Without it, the CRM shows a fee that was billed and never shows whether it landed, and the only person who knows is whoever opens the bank statement.

Candidate and client data on an Indian desk sits under the DPDP Act, and the product supports notice and consent records against candidate profiles and portability export. Billing data is client data rather than candidate data, but the same principle applies: what is held is visible, what is exported is exportable, and the responsibility for lawful processing sits with you as the entity holding it.

Primary data residency is on AWS us-east-1 with encrypted backups. That is a fact worth stating plainly to an Indian buyer rather than leaving to be discovered, because for some enterprise clients the answer determines whether a procurement process proceeds at all.