The short answer: separate the bill from the payment
A reliable clinic payment workflow connects four records without treating them as interchangeable:
- The service, consultation, procedure, or medicine supplied
- The invoice or bill raised for that work
- Each payment received against the invoice
- The bank, UPI, card, or cash record used to reconcile the collection
An invoice establishes what the patient was charged. A payment records what was collected. Reconciliation verifies that the money reached the clinic's cash balance or merchant account.
This distinction becomes important whenever there is a partial payment, split payment, failed transaction, refund, credit note, or outstanding balance.
Build the workflow around four linked records
The source transaction
The workflow should begin with the work already recorded in the clinic.
For a consultation bill, that may include the consultation, procedure, service, or investigation. For a pharmacy bill, it may include the medicines actually dispensed, quantities, batches, and applicable tax configuration.
Staff should not have to reconstruct the visit in a separate billing tool. CliniKite's connected prescription, pharmacy, and invoice guide explains why this handoff matters.
The invoice
The invoice should identify what was charged, the invoice date and number, the patient or customer context, applicable tax details, total value, and later corrections.
It should not change merely because the payment method changes. A ₹1,000 invoice remains a ₹1,000 invoice whether the patient pays in cash, UPI, card, two methods, or over several dates.
The payment entry
Each collection should have its own record:
- Amount received
- Payment method
- Date and time
- Receiving staff member
- Invoice or invoices settled
- External transaction reference where applicable
- Payment status
- Notes or correction reason where required
If the patient pays ₹600 by UPI and ₹400 in cash, the system should retain two payment entries against one invoice rather than converting the transaction into a vague "split" label with no traceable amounts.
The settlement or reconciliation record
The final step verifies the collection against evidence outside the invoice.
For cash, this may be the closing drawer or cash handover. For UPI, it may be the merchant transaction record and bank or acquirer status. For cards, it may be the terminal or payment-provider settlement report.
The clinic ledger and the external payment record should agree, or expose an exception that someone must investigate.
Use payment states that reflect reality
A single paid or unpaid switch is insufficient for a working clinic.
Useful payment states include:
- Unpaid
- Partially paid
- Paid
- Pending confirmation
- Failed
- Reversed
- Refunded
- Partially refunded
- Written off under an approved clinic policy
- Overpaid or refund due
These states should be derived from payment records, not selected casually.
For example, a ₹1,500 invoice with a confirmed ₹1,000 payment should show ₹500 outstanding. It should not appear as fully paid because the receptionist intends to collect the remainder later.
A pending digital payment should also remain separate from a confirmed collection. The clinic can continue the checkout according to its policy, but its financial report should not present uncertain money as settled.
Record each payment method properly
Cash
A cash entry should record the amount, receiving user, counter or shift where relevant, and the invoice it settled.
At closing, expected cash should be compared with the physical amount handed over. Differences should be recorded as exceptions, not hidden by editing yesterday's payments.
Software cannot prevent every counting error. It can make the expected balance, responsible user, and correction history visible.
UPI
NPCI describes UPI as an instant payment system supporting bank-to-bank and merchant payments around the clock. Its merchant FAQ also directs merchants to their acquiring bank for transaction status and grievances. NPCI's UPI overview and UPI FAQs provide the current operating context.
The clinic should record:
- Confirmed amount
- UPI or merchant transaction reference
- Payment time
- Success, pending, or failed status
- Receiving merchant account or counter
- Linked invoice
A patient's screenshot can help locate a transaction, but it should not be the clinic's only settlement evidence. Staff should verify the status through the merchant application, acquiring bank, or agreed payment process.
The clinic software should never ask a patient or employee to disclose a UPI PIN. NPCI states that the UPI PIN authorises transactions and should not be shared.
Cards
When a clinic records a card payment, it usually needs the amount, status, terminal or provider reference, and limited masked context, not the patient's full card credentials.
PCI DSS prohibits storing sensitive authentication data such as card verification codes and PIN data after authorisation, even when encrypted. PCI Security Standards Council guidance explains this boundary.
A clinic management system should not become a card vault merely to remember that a payment was made by card.
Split and partial payments
Split and partial payments solve different problems.
A split payment uses more than one method for the same collection, for example, ₹800 by UPI and ₹200 in cash.
A partial payment collects less than the invoice balance, for example, ₹500 received against a ₹1,000 invoice, leaving ₹500 outstanding.
The system should support both at the same time. It should also preserve the remaining balance automatically rather than requiring staff to maintain a second spreadsheet.
Advances
An advance should not be silently treated as payment for a completed service that has not yet occurred.
The system should identify:
- Who paid the advance
- Amount and method
- Purpose
- Date received
- Unadjusted balance
- Invoice against which it was later applied
- Refund or forfeiture outcome, if applicable
The GST document required for an advance can depend on the transaction and registration context. CBIC materials distinguish tax invoices, receipt vouchers, refund vouchers, and credit or debit notes. Clinics should configure these documents with qualified tax advice. CBIC invoice rules.
Run a daily collection close
A daily close should answer three questions:
- What did the clinic bill?
- What did it collect?
- Where is the collected money now?
A practical closing routine
- Confirm all completed visits that should have produced an invoice.
- Review unpaid and partially paid invoices.
- Total cash expected by counter or responsible user.
- Count and hand over physical cash.
- Match UPI and card transactions by amount, status, and reference.
- Review pending, failed, duplicate, and reversed transactions.
- Record refunds and approved corrections.
- Compare clinic and pharmacy collections separately where needed.
- Assign every unexplained difference to an owner.
- Lock or approve the completed day according to clinic policy.
Do not force the cashier to make the numbers agree by deleting or rewriting entries. A visible variance is better than a false balance.
Handle corrections, credit notes, and refunds without rewriting history
A financial correction should be an attributable event.
The clinic may need to:
- Correct a payment method entered incorrectly
- Void an invoice that should not have been issued
- Issue a credit note
- Refund a confirmed payment
- Reverse a duplicate payment
- Record a medicine return
- Write off an approved balance
These actions are not equivalent.
Changing a payment from cash to UPI corrects the collection record. Cancelling a charged service changes the invoice. Returning money changes the payment position. A medicine return may also affect stock.
The original transaction, correction, reason, user, date, and resulting balance should remain inspectable. The existing GST billing workflow guide covers invoice and tax configuration in more detail.
Turn outstanding dues into owned work
A receivables report is useful only when someone can act on it.
For every unpaid balance, the clinic should be able to see:
- Patient and invoice
- Original amount
- Amount collected
- Remaining balance
- Due date or agreed follow-up date
- Age of the balance
- Responsible staff member
- Last collection action
- Dispute, waiver, or hold status
A payment reminder should contain only the information needed for the collection purpose. It should not expose a diagnosis, treatment detail, or sensitive clinical context merely to explain that a balance remains.
Clinical decisions and financial follow-up must also remain separate. An outstanding balance should not silently alter a prescription, consultation record, or medical history.
Restrict payment corrections by responsibility
Not every staff member needs authority to perform every financial action.
A practical role model might allow:
- Front-desk staff to create invoices and record ordinary payments
- Pharmacists to collect against pharmacy bills
- Managers to correct payment methods with a reason
- Owners or authorised administrators to approve refunds, write-offs, or reopened days
- Account reviewers to inspect reports without changing clinical records
Important financial actions should be attributable to named users. Shared cashier logins make it difficult to investigate a discrepancy or train the right person.
See CliniKite's role-based access guide for a broader clinic responsibility model.
Keep the statutory and security boundaries visible
Software can structure transactions, but it cannot determine every clinic's tax or legal treatment.
Three boundaries deserve explicit review:
First, GST documents depend on the clinic's registration, supplies, pharmacy activity, and professional advice. Invoices, receipt vouchers, credit notes, and refunds should not be treated as interchangeable documents.
Second, the current Income-tax Act section 269ST restricts receiving ₹2 lakh or more through impermissible modes when the relevant daily, single-transaction, or event or occasion tests apply, subject to statutory exceptions. Clinics handling high-value cash collections should confirm the current application with their accountant or legal adviser. Income Tax Department: Section 269ST.
Third, recording "card" as a payment method does not justify storing card verification codes, PIN information, or unnecessary cardholder data. Use the clinic's authorised terminal or payment provider and retain only the reconciliation information the clinic legitimately needs.
A clinic payment software demonstration checklist
Ask the vendor to demonstrate these situations using synthetic patients and payments:
- Create a consultation invoice from a completed visit.
- Collect the exact amount in cash.
- Record a successful UPI payment with a reference.
- Leave a UPI payment pending without marking the invoice as settled.
- Fail the pending payment and collect through another method.
- Split one payment between cash and UPI.
- Take a partial payment and show the remaining balance.
- Apply an earlier advance to a new invoice.
- Correct a payment method with an audit reason.
- Issue a credit note and refund only part of a payment.
- Return a dispensed medicine and show the bill and stock effects.
- Close the cash counter and record a variance.
- Match daily UPI and card collections to external records.
- Open the outstanding-dues ageing report.
- Restrict refund approval to an authorised role.
- Export the day book and underlying payment references.
The demonstration should end with the owner opening the day's report without help from the operator. The owner should be able to trace every total back to invoices, payments, refunds, and exceptions.
Reports should explain collections, not decorate them
A useful clinic collection dashboard separates:
- Gross invoiced amount
- Credit notes or cancellations
- Net billed amount
- Amount collected
- Refunds
- Outstanding balance
- Cash, UPI, and card totals
- Partial-payment count
- Pending digital transactions
- Daily collection variance
- Receivables by age
- Clinic and pharmacy collections
Revenue, billing, and collections should not be displayed as though they mean the same thing.
Every dashboard total should link back to the transactions that produced it. A percentage without an inspectable ledger is difficult to trust.
Where CliniKite fits today
CliniKite's current public feature page describes consultation and service invoices, separate pharmacy bills, cash, UPI and card recording, split and partial payments, credit notes, day-book views, receivables, and financial reporting. CliniKite billing and reporting features provide the current public product scope.
CliniKite's public pages do not claim that the product is a bank, card processor, UPI acquiring application, or automatic substitute for accounting review. During a demonstration, clinics should confirm the exact payment references, reconciliation process, refund permissions, exports, and plan scope that apply today.
Conclusion
Clinic payment collection is a chain of evidence.
The invoice explains what was charged. Payment entries explain what was received. Settlement evidence confirms where the money went. Corrections and refunds explain why the final position changed.
When those records remain connected, the clinic can handle cash, UPI, cards, split payments, partial collections, and outstanding dues without relying on screenshots, memory, or a parallel spreadsheet.
The goal is not a perfect-looking daily total. It is a total the clinic can explain.
Questions clinics ask
Frequently asked questions
Is an invoice the same as a payment receipt?
No. An invoice records what was charged. A payment or receipt record shows what was collected. The documents may be produced together for an immediately settled bill, but the underlying events should remain distinct.
What should a clinic do when a UPI payment is pending?
Keep the payment pending and verify its status through the merchant application, acquiring bank, or agreed payment process. Do not mark the invoice fully paid until the clinic's policy considers the payment confirmed.
Can one clinic bill be paid partly by cash and partly by UPI?
Yes, if the software records separate payment lines, amounts, methods, and references against the same invoice.
How should outstanding patient dues be tracked?
Track the original invoice, payments received, remaining balance, age, responsible staff member, and collection outcome. Avoid using clinical notes as an informal debt register.
Should clinic software store card numbers or CVV details?
Ordinary clinic payment recording should not require sensitive authentication data. PCI DSS prohibits storing card verification codes and PIN data after authorisation.
Can a clinic accept a large payment in cash?
Section 269ST contains restrictions involving receipts of ₹2 lakh or more and specific aggregation tests, subject to exceptions. Obtain current professional advice before accepting a high-value cash payment.
Evidence used
Sources and claim notes
- NPCI: About UPI
Supports the description of UPI as an immediate, round-the-clock system supporting bank and merchant payments.
- NPCI: UPI FAQs
Supports UPI confirmation, pending or failed status, merchant receipt, acquiring-bank grievance, and UPI PIN guidance.
- CBIC: Tax Invoice, Credit and Debit Notes
Supports the distinction between invoices, receipt vouchers, refund vouchers, and credit or debit notes.
- Income Tax Department: Section 269ST
Supports the current statutory wording concerning receipts of ₹2 lakh or more, aggregation tests, permitted modes, and exceptions.
- PCI Security Standards Council FAQ 1533
Supports the prohibition on storing sensitive authentication data after card authorisation.
- PCI Security Standards Council FAQ 1318
Supports payment-card data minimisation, retention policy, protection, and secure disposal.
- CliniKite features
Supports current product statements about clinic and pharmacy invoices, cash, UPI and card payments, split and partial settlement, credit notes, day book, receivables, and reports.
- CliniKite security
Supports current product statements about role-based access and attributable activity.
A useful next step
Explore CliniKite billing and reporting
Bring the real clinic workflow, current plan and people who run the day. We will show the connected path and its limits clearly.
This article provides general operational guidance for evaluating clinic payment software. It is not tax, accounting, payment-security, or legal advice. Applicable requirements depend on the clinic's registration, services, pharmacy operations, payment providers, transaction structure, and current law. Obtain advice from appropriately qualified professionals.