UPI Payment Pending at a Clinic: A Reception and Reconciliation Workflow
Handle pending UPI payments with merchant verification, a named follow-up owner, safe fallback payment and duplicate-credit reconciliation.
Reconcile clinic gateway payments in stages: match each verified payment to the correct bill or advance, match provider transactions and deductions to a settlement, then match that settlement to the bank credit. Keep cash receipts separate. A successful webhook can update a payment record, but it is not by itself a bank-settlement reconciliation or proof that a patient still owes the deducted fees.
Indian clinic owners, accounts teams and developers connecting Razorpay or another payment gateway to booking, billing and daily collection reports.
A clinic needs to answer different questions at different moments. Was a payment initiated for the right amount? Did the provider confirm it? Did the clinic issue or recover the receipt? Which settlement contains the money? Did that settlement reach the bank account? A single paid/unpaid field cannot explain all five.
Use stable references for the bill or advance, the collection intention, the provider transaction, the internal receipt and the settlement or bank entry. The relationships may not be one-to-one: a bill can have instalments, a settlement can contain many payments and a refund can affect a later settlement.
Razorpay describes settlement as the transfer of received customer funds to the merchant bank after applicable deductions, with capture and account conditions relevant to the process. Its cycle can vary. Read the actual account schedule rather than assuming every clinic receives funds on one universal timetable.
A patient’s verified ₹600 payment can fully settle a ₹600 bill even when the later bank credit attributable to it is lower because of a provider deduction. The clinic’s processing cost belongs in reconciliation; it does not automatically recreate patient dues.
A webhook is a server notification from the provider. Validate its signature using the provider’s documented method before allowing it to affect financial records. For Razorpay, the documentation specifies validating the raw request body, identifying duplicate events and accommodating events that arrive out of order.
After validation, match the event to the intended clinic account, amount, currency and payment reference. Apply its effect once. An older event arriving later should not downgrade a payment already known to have reached a later state. Preserve the event evidence and the result of processing without exposing secrets or unnecessary patient data.
If a notification cannot be matched, put it in an exception queue. Do not invent a cash receipt just to balance the daily report. A successful external payment without an internal receipt is an integration or allocation problem; a receipt without corresponding payment evidence is a different problem.
Keep a recovery path for missing notifications. Reconciliation should be able to discover a provider transaction through trusted reporting or retrieval, then link it without duplicating a receipt already created by another route.
First reconcile internal collections to the provider’s payment-level records for the defined period. Next reconcile the provider’s settlement composition, including the relevant payments, refunds and deductions. Finally match settlement references and amounts to the bank statement. Each stage has its own unmatched queue.
Razorpay’s settlement reconciliation API exposes fields such as transaction type, fees, tax, settlement ID and bank-transfer reference. Those fields support a traceable match; their existence does not mean an exported report is complete. Check the requested date range, pagination and the account or environment used.
Use dates deliberately. The consultation date, payment creation or capture time, settlement date and bank posting date can differ. A report filtered by consultation date should not be expected to equal bank credits on the same calendar date.
On a narrow screen, scroll the table horizontally to read all columns.
| Layer | Match these records | Investigate |
|---|---|---|
| Patient collection | Bill allocation, internal receipt and provider payment | Missing receipt, wrong amount or wrong patient |
| Provider settlement | Eligible transactions, refunds and deductions | Held item, fee difference or missing report rows |
| Bank credit | Settlement reference, amount and bank posting | Missing credit, timing difference or wrong account |
| Cash collection | Cash receipt and physical drawer movement | Duplicate receipt or cash classification error |
| Refund | Original payment, outgoing refund and status | Duplicate instruction or patient non-receipt |
In a fictional settlement, included patient payments total ₹10,000. The provider statement lists ₹200 in fees, ₹36 in tax on those fees and ₹1,000 in refunds deducted in that batch. Expected bank credit is ₹10,000 − ₹200 − ₹36 − ₹1,000 = ₹8,764. The fee and tax amounts are invented statement inputs, not asserted statutory rates or provider pricing.
If the bank shows ₹8,764 with the matching settlement reference, that settlement is reconciled. The ₹1,236 difference from gross collections is explained by the three separate deductions. Do not reduce patient receipts to ₹8,764 or record ₹1,236 as unpaid consultation fees.
Now suppose the clinic collected another ₹600 after the settlement cutoff. Total collections for the clinic’s reporting day are ₹10,600, but the matched settlement still contains only ₹10,000 gross. The ₹600 belongs in the unsettled collection list, not in an unexplained-fee bucket. It should be matched when its own settlement arrives.
Beware of subtracting a fee or refund twice. Some exports show gross amount and separate deductions; others provide net credit and debit fields. Understand which fields are already net before constructing the bridge. Reconcile using one documented convention and test it on a small known set of transactions.
Save the period, report generation time and source account with the reconciliation. A fresh export can contain late updates absent from yesterday’s file. Without a cutoff and version, two correct reports can appear to contradict each other.
Use an exception reason that describes the missing link: provider success without receipt, receipt without verified payment, unsettled payment, unmatched bank credit or pending refund. Assign an owner and next check. A catch-all “gateway mismatch” category makes prioritisation difficult.
Restrict report access and remove unnecessary clinical information from exports. Payment IDs and internal references are usually enough to trace the financial event. A reconciliation spreadsheet should not become a second patient database.
Use a sandbox to simulate a successful payment whose browser response is lost, a duplicate webhook, a delayed event and a refund in a later period. Then use fictional reports to test a settlement containing several payments and deductions. A successful checkout alone does not prove the full accounting trail.
Check that a direct cash collection remains outside the gateway webhook path. If reception manually records a verified gateway payment during an outage, the later notification should recover or match that record, not create another receipt. The manual action needs its own authority and evidence.
Ask how failed bank settlements, held transactions and unavailable reports appear to accounts. The system should retain a truthful unresolved state. Marking every captured payment as bank-settled simply to clear a dashboard hides the very work reconciliation is meant to identify.
Agree on the division of responsibility between reception, accounts and the software vendor. Reception can identify a patient payment query; accounts can trace settlement composition; the vendor may need to diagnose an integration gap. Each needs a reference and a specific next action rather than a screenshot of an unexplained total.
A patient’s verified ₹600 gateway payment is allocated to a ₹600 consultation and the receipt is issued. The payment falls after the current settlement cutoff. Reception correctly shows no patient dues, while accounts lists ₹600 awaiting settlement. When the next settlement and bank entry are matched, accounts clears that item. The clinic does not ask the patient to pay again just because the money reached its bank later.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
No. It describes a provider event that must be validated and interpreted. Match the payment to its settlement and then to the bank credit separately. Payment confirmation and merchant bank settlement can occur at different times.
A verified payment should be allocated according to the amount the patient actually paid against the valid charge. Provider deductions are a separate clinic reconciliation issue. They do not automatically create new patient dues.
Providers may retry notifications, and Razorpay documents duplicate delivery as expected behaviour. Process a recognised event once and preserve its reference. Also handle events that arrive out of order so an older notification does not corrupt the current state.
No. That would misclassify the payment and distort the cash drawer. Verify the provider transaction and use an authorised recovery or manual matching process that preserves the actual payment method.
Possible reasons include settlement timing, provider deductions, refunds, holds and report-scope differences. Build a transaction-level bridge and list unsettled items. Do not force equality by changing receipts or treating every difference as a fee.
Updated on . Technical and operational guidance checked 25 October 2026. Razorpay references are provider-specific; all rupee examples are fictional. Confirm current integration support and accounting treatment for the clinic. No independent clinical or legal review is claimed.
Provider documentation distinguishes capture and settlement and describes account-dependent cycles. No generic cycle is promised for the clinic.
Provider documentation on signature validation, duplicate event IDs and unordered delivery. Applies to that integration, not every payment system.
Provider reference includes payment/refund entries, fees, tax, settlement IDs and bank-transfer references. Sample amounts are not a price list.
Handle pending UPI payments with merchant verification, a named follow-up owner, safe fallback payment and duplicate-credit reconciliation.
Understand idempotency, unknown payment results and safe retries through clinic examples, concurrent desk tests and receipt reconciliation.
Close an Indian clinic cash drawer with an opening float, receipts, refunds, paid-outs, deposits and a worked variance investigation.
Trace a fictional payment through receipt, settlement and bank matching, then introduce a duplicate event and a payment after cutoff. Ask for the unresolved-item report.
Request a clinic demo