Skip to content

BILLING & PAYMENTS / RAKT

Hospital bills,
payments and refunds.

See which consultation, investigation, medicine, or admission produced a charge. RAKT keeps invoices, individual charges, payments, and refunds in the same system.

Explore the detail

ILLUSTRATIVE PATIENT LEDGER / INR

Change the payment.
See the balance.

Consultation
₹500
Investigation
₹800
Total charges
₹1,300
Outstanding₹600

Drag to change the payment. Fictional charges, not software pricing.

See where each charge came from

A consultation fee, an investigation, a medicine sale, and a bed charge begin in different workflows. The bill should show which service or event produced each charge.

RAKT’s shared invoice model links financial records to their source. Line items carry the charge detail, while payment records represent money received or refunded. In a demonstration, follow a single service from the originating department to its financial record instead of starting with an already completed invoice.

Track charges and payments separately

An invoice records charges. A payment records a financial movement against the invoice. Confusing them makes collection reports difficult to interpret, particularly when payment is partial or happens on a different date.

Use the illustrative ledger on this page to change a payment and see how the outstanding balance changes while the charges stay fixed. These sample amounts demonstrate arithmetic, not hospital tariffs or RAKT subscription prices. Your organisation’s charges, payment modes, and operational policies need their own setup.

Check refund permissions and repeated payments

RAKT checks whether a user is allowed to issue a refund and records the refund details. Payment requests can also include a unique reference, called an idempotency key, to help recognise a retry and avoid recording the same payment twice.

Ask the team to demonstrate a partial payment, an authorised refund, and an attempt by a user without the necessary permission. Review the resulting records and how the financial totals are interpreted. Tax and accounting treatment should be agreed with your finance team; a software demonstration cannot decide it for you.

Connect department work to the financial review

Review consultation and diagnostic charges with the people who create them, pharmacy billing with dispensing, and admission-related charges with the inpatient team. A finance-only demonstration can miss what happens before a charge reaches the cashier.

At the end of the exercise, inspect the invoice, payment history, and relevant management report together. Decide which dates, filters, and statuses your team will use for its daily review. Revenue, billed amount, collections, and outstanding balances describe different things.

Test the billing cases your team handles

Bring a de-identified bill format and a short list of real operational cases: one consultation, one investigation, one partial payment, one cancellation or correction, and one refund requiring authorisation. Ask for the resulting documents and records, not just a tour of the billing screen.

Record any required numbering conventions, payment modes, tax details, receipt formats, and access rules in the implementation scope. Confirm external accounting or payment-provider requirements separately; the existence of an API is not evidence that a particular integration is already configured.

COMMON QUESTIONS

Questions about this topic.

Does the example show RAKT pricing?

No. The ledger uses fictional patient charges to explain invoices, payments, and balances. Software budgeting is covered in the cost guide.

Can the same user always issue a refund?

Refund authority is checked by the application. Review the intended roles and permissions with your administrator.

Can billing be reviewed alongside department work?

Yes. The shared financial records support invoice and payment workflows associated with department activity. Confirm the specific charge sources and report views needed for your setup.

PLAN A DEMONSTRATION

See how RAKT handles
your team’s work.

Use fictional examples or blank formats. Keep patient information out of an initial enquiry.

Arrange a walkthrough