Keep estimates, deposits and final bills separate
For Billing / revenue-cycle manager · Understand the problem
TL;DR — what you’ll learn
- An estimate describes a proposed scope and assumptions; a final bill records authorised charges.
- A deposit is a payment record with an allocation, not a reduction in the agreed price.
- Create a new estimate version when authorised scope or pricing changes.
- Explain the bridge from estimate to final bill using documented changes and adjustments.
A hospital gives a synthetic ₹40,000 estimate and receives a ₹10,000 deposit. After an authorised scope change, the estimate becomes ₹46,000. The front desk edits the original estimate to ₹36,000 by subtracting the deposit, so nobody can see either the revised scope or the original proposal.
Estimate version control keeps the commercial proposal separate from payments and final charges. Preserve the ₹40,000 version, create the authorised ₹46,000 revision, and retain the ₹10,000 deposit under its payment reference. Show the estimated remaining amount separately, with the assumptions and current version clearly identified.
Explain what each record can establish
Use an estimate record to show the proposed scope, tariff/package reference, inclusions, exclusions, assumptions and validity supplied by the authorised commercial owner. Keep its approval and communication history. The example treats the amount as a proposal; only the actual agreement can establish a guaranteed price. The software must not create such a commitment from the presence of an estimate total.
The deposit records money received and its current allocation. The bill records authorised charges and adjustments. A refund, credit or transfer is another referenced event; it should not be concealed by rewriting the original receipt.
Bahmni describes quotations, payments and accounting functions. Request a demonstration that the proposed version retains separate estimate, receipt and bill identities through scope changes and corrected allocation. Inspect prior versions and permissions in the export. A displayed net balance alone is insufficient evidence that the required history is preserved.
Follow the ₹40,000 example through a revision
Assume estimate E1 is ₹40,000. An authorised scope change adds ₹6,000 and creates E2 for ₹46,000. Payment P1 is ₹10,000. If P1 is allocated to this episode and no other events exist, the estimated remaining amount is ₹36,000. The revised price is still ₹46,000.
Later, suppose the authorised final bill is ₹44,000 because the documented final services differ from the estimate. With the same ₹10,000 allocation and no other adjustments, the remaining billed balance is ₹34,000. The ₹2,000 difference between E2 and the final bill needs an explanation in the service/charge bridge; it is not automatically a refund.
Scroll horizontally to see all columns.
| Record | Amount | Interpretation |
|---|---|---|
| Estimate E1 | ₹40,000 | Original proposal |
| Estimate E2 | ₹46,000 | Revised proposal after authorised change |
| Deposit P1 | ₹10,000 | Receipt with episode allocation |
| Final bill B1 | ₹44,000 | Authorised final charges in this example |
| B1 less allocated P1 | ₹34,000 | Outstanding billed balance under these assumptions |
The ₹36,000 and ₹34,000 figures use the stated single-payment assumptions and exclude tax, payer splits, credits and other adjustments. They are balance calculations only. Obtain actual charge, allocation, acknowledgement and refund decisions from finance and the commercial owner before posting; the ₹2,000 estimate-to-bill difference supplies no refund authority.
Keep the patient-facing summary understandable
The summary should identify the current estimate version, the material scope change, the received payment and the remaining estimate or billed balance under the right label. It should also explain whom to contact for a question. A record that someone received a summary is not interchangeable with consent to clinical care or agreement to every commercial term.
Internal evidence may include approval references, tariff mappings and detailed change reasons. Avoid placing unnecessary clinical detail in a commercial notification. The provider must determine its approved acknowledgement and communication procedure.
Worked workflow
Original illustrative workflow. Follow the labelled transitions, including the exception paths.
- A · StepCreate estimate with scope and assumptions
- B · StepAuthorised commercial review
- C · StepRecord approved communication and acknowledgement
- D · DecisionAuthorised scope or price change
- E · StepCreate linked estimate revision
- F · StepReconcile actual authorised charges
- G · StepAllocate payments by reference
- H · StepExplain final bill and outstanding balance
Scroll horizontally to see all columns.
| From | Condition | Next |
|---|---|---|
| A: Create estimate with scope and assumptions | Continue | B: Authorised commercial review |
| B: Authorised commercial review | Continue | C: Record approved communication and acknowledgement |
| C: Record approved communication and acknowledgement | Continue | D: Authorised scope or price change |
| D: Authorised scope or price change | Yes | E: Create linked estimate revision |
| E: Create linked estimate revision | Continue | B: Authorised commercial review |
| D: Authorised scope or price change | No | F: Reconcile actual authorised charges |
| F: Reconcile actual authorised charges | Continue | G: Allocate payments by reference |
| G: Allocate payments by reference | Continue | H: Explain final bill and outstanding balance |
Test changes that a simple total cannot explain
Ask the demonstrator to revise an estimate after payment, cancel one proposed service, correct an incorrectly allocated receipt and produce both the original and current summaries. Check whether permissions stop an operator from editing an approved historical amount in place.
For an estimate that crosses a payer or tariff change, the pricing basis needs explicit review. A date field alone cannot determine the right contract rule. For an episode cancellation, the approved adjustment and refund decision should be linked to the original payment rather than created from an estimate subtraction.
A reliable estimate process lets people understand why an amount changed. Versioned scope, visible assumptions and separate payment records make that explanation possible before a disputed balance becomes a collection problem.
Next actions
- Define the required estimate fields and authority for commercial revisions and communication.
- Reconcile E1, E2, P1 and B1 without treating the deposit as a discount.
- Continue with the billing evaluation guide to test changes, allocation errors and historical versions.
Continue your evaluation
Continue with the hospital billing evaluation to test whether estimate versions, receipts and final charges remain separately reconstructable.
Evaluate hospital billing software using corrections and handoversApplying this guide
The scenarios and numbers are illustrative. Confirm these provider-specific inputs before implementation:
- Commercial lead, patient-services lead and legal reviewer: Approved estimate terms, communication/access procedure and distinction from clinical consent.
- Finance controller and relevant tax/commercial adviser: Applicable accounting/tax policies and authorised episode allocation/adjustment rules.
- Billing system owner and finance implementation lead: Tests for post-payment revision, receipt reallocation, cancellation and immutable historical summaries.
References
- Bahmni billing and accounting — Odoo subsystem and billing/accounting boundaries; not authority for tax, refunds or consignment treatment.
Topics: hospital estimate management · hospital cost estimate workflow · patient deposit reconciliation · hospital package estimate