Billing in MindFlow is a unified financial layer covering OPD consultations, pharmacy purchases, in-patient charges, and store orders. Every financial change produces an audit record that cannot be altered, providing a tamper-evident history for governance and regulatory review.
A single invoice can combine OPD consultation fees, pharmacy items, in-patient ward charges, lab charges, and store items. Tax rates (CGST + SGST or IGST, as applicable) are configured per line item type. Invoices are generated automatically at the point of service.
Every change to an invoice, creation, item addition, amount change, payment received, refund, is appended to a permanent audit log with the acting staff member's identity, a timestamp, and a before/after snapshot. This log is append-only and cannot be modified retroactively.
Admins can close a completed month, preventing backdated edits to invoices in the closed period. This supports clean monthly P&L reconciliation and prevents accidental modifications to finalised accounts.
Front-desk staff open and close shifts with a physical cash count. All cash transactions in the shift period are totalled automatically and compared to the declared cash to produce a variance report.
Invoices can be exported as a CSV or as a Tally-compatible XML voucher file for the selected date range, allowing direct import into common Indian accounting software without manual data entry.
Handles card, UPI, net banking, and EMI payments for Indian patients. The patient is redirected to PayU's secure payment page and returned to the clinic application on completion. PayU sends asynchronous payment confirmation via webhook. All webhook events are validated against PayU's HMAC signature before processing.
For international card or PayPal wallet payments, for overseas patients or clinics with international clients. The PayPal redirect flow sends the patient to PayPal's secure checkout and returns them on completion.
Both payment gateways send signed webhook notifications. The system verifies the cryptographic signature of every inbound payment event before applying it. Events with invalid signatures are rejected and logged as security incidents.
Patients browse the store, add items to their cart, and check out via the patient portal. Physical orders that require dispensing from the pharmacy generate a dispense queue entry automatically, keeping store and pharmacy workflows in sync.
Patients can hold a credit balance that is applied at checkout. If a payment attempt fails after a wallet deduction, the deducted amount is automatically restored to the wallet balance, no manual refund intervention needed.
Discount codes are validated at checkout against their rules, percentage or fixed discount, minimum order value, per-patient usage limit, and expiry date. All constraints are enforced server-side, not just in the browser.
Products that require a valid prescription (scheduled medicines, certain supplements) can be linked to a prescription ID from the clinic record. The order is held until the pharmacist confirms the prescription before it is dispatched.
Physical orders requiring delivery are shipped via Shiprocket. A shipment is created through the Shiprocket API on order confirmation, an AWB number is assigned, and tracking updates arrive via webhook and are shown to the patient in their portal.
Each product page includes structured data (Schema.org Product markup) for search engine indexing. A product sitemap is generated automatically and included in the site sitemap.
The demo comes pre-loaded with real sample data, so you can click through actual appointments, patients and prescriptions.