Billing and revenue cycle

Reconcile cash, UPI and card collections at day close

By Vikasraj YadavPublished 5 min read

For Billing / revenue-cycle manager · Plan implementation

TL;DR — what you’ll learn

  • Reconcile counter receipts, cash custody and bank settlements as separate events.
  • Explain timing, fees, refunds and unresolved differences in a visible bridge.
  • Match by supported references and amounts without inventing a balancing entry.
  • Keep adjustments and refund decisions under finance authority.

The hospital's receipt report shows ₹30,000. Only ₹9,800 appears in the day's bank settlement. A cashier is asked to explain the apparent ₹20,200 shortage, even though part of the collection is cash and another part settles tomorrow.

Hospital cash collection reconciliation should bridge the different records rather than compare two totals with different meanings. Begin with receipts by channel, then identify custody, settlement timing, fees and unresolved items.

Build the bridge using consistent scope

The following synthetic day has no refunds and excludes tax accounting. The fees and settlement timing are assumed values used solely to explain the reconciliation bridge; they are not claims about a payment provider’s charges or an accounting policy.

Scroll horizontally to see all columns.

Build the bridge using consistent scope
Receipt channelReceipted amountEnd-of-day evidence
Cash₹10,000Counted and signed into approved custody
UPI₹12,000₹10,000 gross settled today; ₹2,000 pending
Card₹8,000₹8,000 pending settlement
Total₹30,000Reconciles across custody and timing states

The ₹10,000 gross settlement produces ₹9,800 net bank credit and a separately evidenced ₹200 fee in this synthetic case. The bridge is ₹10,000 cash + ₹9,800 bank credit + ₹200 fee + ₹10,000 pending = ₹30,000. The fee is an assumed example, not a statement about UPI pricing or a recommended accounting entry.

Pending settlement is neither cash in the bank nor automatically a loss. Cash in approved custody is not a bank deposit until the deposit and bank acknowledgement occur.

Keep transaction identities intact

The pilot needs receipt ID, site, cashier shift, payment channel, provider transaction reference, amount, receipt time, settlement batch, bank value date, fee reference and any refund or reversal link. A single bank credit may cover many receipts, and a receipt may be affected by a later reversal.

Bahmni's billing documentation describes financial records and accounting functions. The payment provider's settlement export and bank statement remain separate evidence sources that must be mapped explicitly.

Use the original references wherever supported. A match based only on amount can confuse two equal-value payments. AI may suggest a candidate match from remittance text, but an ambiguous link should remain for finance review.

Assign each difference to the right owner

The cashier supervisor confirms receipts and cash handover. The payment-integration owner investigates missing provider events. Finance reviews settlements, fees and accounting adjustments. Do not ask the cashier to create an adjustment simply because a bank file is late.

Worked workflow

Original illustrative workflow. Follow the labelled transitions, including the exception paths.

  1. A · StepReceipts by channel and shift
  2. B · StepMatch cash handover or provider reference
  3. C · StepBridge gross settlement fees and timing
  4. D · DecisionAll differences explained
  5. E · StepFinance reviews day close
  6. F · StepOwned exception with source references
  7. G · StepEvidence-based correction or continued pending state

Scroll horizontally to see all columns.

Transitions and exceptions
FromConditionNext
A: Receipts by channel and shiftContinueB: Match cash handover or provider reference
B: Match cash handover or provider referenceContinueC: Bridge gross settlement fees and timing
C: Bridge gross settlement fees and timingContinueD: All differences explained
D: All differences explainedYesE: Finance reviews day close
D: All differences explainedNoF: Owned exception with source references
F: Owned exception with source referencesContinueG: Evidence-based correction or continued pending state

The reconciliation identifies unresolved money states; it does not decide who may close a shift, write off a difference or release a refund. Finance and the relevant governance owners must supply those decisions and permissions before any posting or closure automation.

Pilot reconciliation before automatic posting

Start with one counter, one settlement provider and a defined business-day cutoff. Use read-only exports first. Reconcile source row counts and totals before matching individual transactions; an incomplete file can otherwise look like many missing payments.

Use repeated files, partial refunds, missing batches, later chargebacks and corrected exports as demonstration cases. Ask each system owner to establish the supported identities, versions and recovery path. Passing the agreed synthetic set is evidence about those cases, not a guarantee of error-free live settlement.

If an export is unavailable, retain the close as pending or qualified under the approved process. Use an owned manual worksheet if necessary and reconcile its adjustments before restoring automated writes. Turning off an interface does not undo transactions already posted.

Measure unresolved value and age by reason, unmatched receipt count and correction effort. Separate genuine shortages established by investigation from timing differences and unsupported matches. A zero-difference dashboard achieved through unexplained balancing entries is a failed control.

Carry pending settlement into the next day

Keep the original receipt cohort when the pending ₹10,000 settles. In a further illustrative step, suppose the provider reports ₹10,000 gross, ₹30 separately evidenced fees and ₹9,970 net credit. The original cohort now reconciles as ₹10,000 cash + ₹19,770 total bank credits + ₹230 total fees = ₹30,000. The second fee is another synthetic assumption, not a general payment-channel charge.

This is an update to the settlement state of yesterday's receipts, not ₹9,970 of new counter collections today. A business-day receipt report and a bank-value-date report can therefore differ while both are correctly scoped. Retain the link between them.

Scroll horizontally to see all columns.

Carry pending settlement into the next day
Acceptance caseEvidence finance should inspect
Pending batch settles next dayOriginal receipts linked to the later gross/net settlement
The same bank file is imported againNo additional bank receipt or fee posting
A later reversal affects one receiptReferenced reversal and an owned adjustment decision
Cash is deposited after closeCustody handover and bank evidence, without counting both as new collection

Start by producing the bridge without posting adjustments. Finance should approve any later posting scope and inspect unresolved items before accepting the day-close result. This article stops at collection-to-custody/bank reconciliation; TPA allocation separately connects payer money to claims and deductions.

Next actions

  1. Define the day, channels and source reports included in the reconciliation.
  2. Build a bridge for one synthetic day with cash, pending settlement and a fee.
  3. Agree exception ownership and posting authority before extending the pilot.

Discuss this workflow

Discuss a day-close reconciliation pilot for one counter and settlement provider, with timing differences and unresolved amounts kept visible.

Describe the operation using business information only. Please leave out patient details.

Applying this guide

The scenarios and numbers are illustrative. Confirm these provider-specific inputs before implementation:

  • Finance controller and payment-provider owner: Current settlement agreements, fee statements and accounting review; ₹200 is synthetic and is not a UPI pricing assertion.
  • Finance controller, cashier supervisor and qualified adviser: Approved delegation, cash-handling, refund and exception-close procedures.
  • Payment integration and accounting system owners: Current export/API specifications and duplicate-file, refund, chargeback and missing-batch tests.

References

About the author

Vikasraj Yadav writes about software and operations at NextEdge Labs. This article is an editorial workflow guide; no clinical or regulatory specialist endorsement is asserted.

Browse all healthcare guides

Topics: hospital cash collection reconciliation · hospital cash reconciliation · clinic UPI settlement · daily collection hospital