Khajna payment status and GRN search on Banglarbhumi

What a GRN is, and why it matters more than the receipt

GRN stands for Government Reference Number. It is generated by the state's treasury payment system — GRIPS — when a payment against a government service is initiated, and it is the identifier the treasury, the department and your bank all share.

This is the crucial point: your bank's transaction reference and the portal's application number are *different numbers in different systems*. When a payment goes through but the record doesn't update, the GRN is what lets anyone reconcile the two. It is the one thing worth screenshotting before you close the tab.

So the working rule is simple. At the moment of payment, record three things — the GRN, the application number the portal issued, and your bank reference — and note the date and amount. With all three, almost any payment problem is solvable. With none of them, you are reconstructing history from a bank statement.

Three status screens, and which one to use

The portal spreads payment information across menus in a way that makes people conclude it isn't there. It is — it's just in three places, each answering a different question. All three sit under Citizen Services and all three require you to be signed in.

• GRN Search — under Citizen Services. Answers: *did the treasury receive this payment?* Use it when you have the GRN and want to confirm the money landed on the government side. This is the authoritative check. Note that GRN Search is available only for about a month from the date of application, so check it early rather than months later.
• Payment Status of Land Revenue (Khajna) — under Online Service Status. Answers: *has the department credited this payment against my Khatian?* Use it to confirm your land revenue is actually recorded as paid.
• Application No. Recovery ( Khajna ) — under Online Service Status. Answers: *what was my application number?* Use it when you have lost the number and can't look anything up.

Money left the account but the status says unpaid

This is the common emergency, and it splits cleanly into two cases depending on what GRN Search reports.

Case one: GRN Search shows the payment as received. The treasury has your money and the failure is a sync between systems — the department's record hasn't picked up the successful payment. Payments do not always reflect instantly, so the first move is to wait and re-check rather than pay again. If it persists, raise it through the portal's Grievance Application with the GRN, application number and date, and check progress under Grievance Status/Description.

Case two: GRN Search finds nothing, or shows the payment as failed. The money has left your account but has not reached the treasury — it is sitting in the payment gateway's settlement. This is a banking matter, not a land-records matter. Contact your bank with the transaction reference and raise a failed-transaction dispute. Gateway-side reversals are routine and your bank handles them.

You have lost the application number

The portal anticipated this, which tells you how often it happens. Application No. Recovery ( Khajna ), under Citizen Services → Online Service Status, exists specifically to recover a Khajna application number you no longer have.

You will generally need the identifiers the application was filed against — district, block, mouza and Khatian number — plus the mobile number registered on the account. If your registered mobile has changed since, recovery will fail for the same reason login does, and that needs fixing first — through Mobile Number update Against Khatian if you can still sign in, or at your BL&LRO office if you cannot.

If you have the GRN but not the application number, start from GRN Search instead — the payment record is the thread that leads back to the application.

How the Khajna payment actually flows

Understanding the sequence makes the failure modes obvious. A land revenue payment moves through four stages, and a problem at each looks different:

• Application — Land Revenue(Khajna) Application under Online Application, filed against your Khatian. Produces an application number.
• Challan — eChallan Generation produces the challan, and the GRN is issued at that point, *before* you pay. It identifies the challan, not the payment. Note it down then.
• Payment — your bank or card debits the amount. Your bank reference is created here, and this is the only stage your bank knows about.
• Reconciliation — the treasury confirms receipt (visible in GRN Search) and the department credits it against your Khatian (visible in Payment Status of Land Revenue (Khajna)). Most reported failures are a stall between these two.

Receipts, reprints, and no-due certificates

Once a payment is settled, Application/Report Reprint under Citizen Services will regenerate the receipt or report. There is no need to preserve the original download forever — but you do need the identifiers to find it again, which is the argument for recording the GRN and application number at the time.

Related to this, No Due Certificate under Service Delivery certifies that no land revenue is outstanding against a holding. It is a separate request with its own requirements and fee, and it is usually what a bank or buyer actually wants — a payment receipt shows one payment, whereas a no-due certificate speaks to the whole position.

As with every service on this page, a fee applies where the portal says one does, and the portal's Online Fees Calculator is the only figure worth trusting. Amounts are deliberately absent here — the portal's calculator is the only source that stays current.

On apps, ours included: our own app, Bhumir Tathya, covers only the portal's record lookups — Khatian, plot details, mutation status — and it reaches those by signing in with your own banglarbhumi.gov.in account, not by getting round the sign-in. Khajna payment and payment status are not among them, and no app can make them so. No third-party app can bypass the government's sign-in, its payment gateway, or its fees, and you should never enter Banglarbhumi credentials anywhere except the portal's own sign-in.