The NABH FPM digital health standard — Finance and Procurement Management (FPM) — covers 3 standards and 17 Objective Elements. Three of those 17 are Core — tied with AAC for second-highest of any chapter, behind only DOM’s 6. NABH finance procurement digital requirements here cover supply chain and procurement, vendor and customer payments, and patient billing — and none of the three Core elements are satisfied by generic bookkeeping software alone.

Recommended starting point: This piece is from a series on the NABH Digital Health Standard for Hospitals and assumes familiarity with many fundamental terms such as Chapters, Standards, Objective Elements, the four bands, and tier requirements. If these terms are new to you, it may make more sense to start from the beginning.

Important to note that NABH is exacting about hospital billing automation — it isn’t satisfied by a hospital simply owning accounting software like Tally. A generic bookkeeping setup handles ledgers and invoices; it doesn’t necessarily give patients a digital way to pay with pre-defined charges, or track quality issues against specific purchased items.

Read the standard yourself. NABH’s Digital Health Standard for Hospitals is available in full, free, at nabh.co/digital-health-standards — creating a free NABH account is required to access it. Nothing in this piece substitutes for the source document itself.

A note on FPM.1’s lettering: NABH’s source document labels two distinct Objective Elements in FPM.1 with the same letter, “d” — one Commitment-band (digital receipt notes) and one Core-band (digital quality-concern tracking). This appears to be a labeling oversight in the source. Both are genuinely distinct requirements, so both are distinguished here as FPM.1.d (i) and FPM.1.d (ii) for clarity.

FPM.1 — Digital System to Manage Supply Chain

FPM.1 requires the hospital to use a digital system to manage its supply chain, across 5 Objective Elements.

Core

• FPM.1.d (ii). A digital system to record quality concerns of purchased hospital assets — item expiry, volume, SKU, and similar issues flagged and tracked against ordered items, supporting recall of defective assets.

Commitment

• FPM.1.a. Digital inventory management, based on the stock movement of all hospital items — supply and equipment levels tracked in real time, with automatic reorder flags, so a stockout surfaces as a system alert rather than a delay in patient care. This isn’t simply a broader version of MOM.1.a — MOM.1.a requires two things FPM.1.a doesn’t ask for at all: digital tracking of medicine/consumable disposal, and hazard-based categorization (high-risk medicines, sound-alike drugs, differing concentrations of the same drug, emergency medicines). A hospital could satisfy FPM.1.a’s stock-movement tracking across every item it owns and still fail MOM.1.a on either of those two points.
• FPM.1.b. Digital creation and management of indents for any hospital item — staff requesting and tracking supplies through the procurement pipeline digitally, rather than on a paper requisition slip that’s easy to lose or forget to follow up on.
• FPM.1.c. Digital creation of purchase orders — orders created, tracked, and managed electronically, cutting the paperwork and saving time. Especially useful for hospitals with high daily volume of supply orders.
• FPM.1.d (i). Digital creation of receipt notes for orders received in the store — goods received acknowledged, quantified, and quality-checked digitally at the point of receipt, rather than on a paper slip reconciled manually later.

Achievement

None under FPM.1.

Excellence

None under FPM.1.

FPM.2 — Digital System to Manage Vendor and Customer Payments

FPM.2 requires the hospital to use a digital system to manage vendor and customer payments, across 4 Objective Elements.

Core

None under FPM.2.

Commitment

• FPM.2.a. A digital payment channel to make vendor payments — EFT, UPI, wire transfer, or card payment rather than a cheque, giving vendor payments faster settlement and a built-in, auditable record instead of a paper trail.
• FPM.2.b. A digital system to maintain records of all payables and receivables — every transaction with suppliers and customers held in one electronic ledger, so financial reporting and discrepancy checks don’t depend on reassembling paper invoices.
• FPM.2.d. A digital system to create a debit/credit note — the documents requesting payment for services rendered, or refunding an overcharge, generated and calculated digitally rather than drafted by hand and prone to arithmetic error.

Achievement

• FPM.2.c. A periodic payment cycle, with the digital system reflecting payments to be made or received in upcoming cycles — visibility into what’s coming, not just what’s already happened.

Excellence

None under FPM.2.

FPM.3 — Digital System to Perform Patient Billing Functions

FPM.3 requires the hospital to use a digital system to perform patient billing functions, across 8 Objective Elements — the largest standard in the chapter, and where hospital billing automation NABH scores most directly shows up.

Core

• FPM.3.a. A digital system for patients to pay for any hospital service — payment via online portal, UPI, or card, rather than cash or cheque being the only way to settle a hospital bill.
• FPM.3.b. A digital system that includes pre-defined charges for all key services and items — rates set in the system in advance, not negotiated or keyed in ad hoc at the billing counter.

Commitment

• FPM.3.d. A digital mechanism to periodically update the patient on their billing records — automated alerts via patient portal, SMS, or WhatsApp whenever billing information changes, rather than a patient discovering a revised charge only at discharge.
• FPM.3.f. A digital system to manage insurance claims — claims processed, tracked, and reconciled through a system built for it, rather than assembled manually across paperwork exchanged with insurers and TPAs.

Achievement

None under FPM.3.

Excellence

• FPM.3.c. A digital portal for the patient and/or family member to view provisional or final bills — patients checking their own bills online, rather than every billing question requiring a phone call or a trip to the billing counter.
• FPM.3.e. A digital, standardised billing template — every patient’s charges captured in the same structured digital format from consultation to discharge, rather than each department’s bill assembled differently and reconciled by hand at the end.
• FPM.3.g. A digital mechanism to notify and update the patient and/or family member about TPA, insurance, or empaneled-agency processes — claim-status updates sent by message, e-mail, or app alert, rather than the patient having to call to find out where things stand.
• FPM.3.h. A digital system to route claims through the Health Claims Exchange (HCE) — a specific ABDM-linked interoperability requirement for claims processing.

FPM at a Glance — Every Standard, By the Numbers

Standard	TL;DR	Core	Commitment	Achievement	Excellence	Total
FPM.1	Supply chain — inventory, indents, purchase orders, quality tracking	1	4	0	0	5
FPM.2	Vendor/customer payments — payables, receivables, payment cycles	0	3	1	0	4
FPM.3	Patient billing — payment system, pre-defined charges, claims, HCE routing	2	2	0	4	8
FPM total	3 standards, 17 Objective Elements	3	9	1	4	17

The Self-Check

Before assuming existing accounting or billing software already covers FPM, check it against these questions with finance and procurement teams directly:

1. Can a patient actually pay digitally for any hospital service through the system (FPM.3.a, Core), or does “digital billing” just mean an itemised printout handed over at the counter?
2. Are charges for key services and items pre-defined in the system (FPM.3.b, Core), or negotiated and keyed in manually at billing each time?
3. Does the procurement system track quality concerns on purchased assets — expiry, defects, recalls (FPM.1.d, Core) — or does that information live only in a vendor’s paper delivery note?
4. Can finance actually see upcoming payables and receivables reflected in the system (FPM.2.c), or is the payment cycle still assembled manually from a folder of invoices?
5. If asked to route a claim through the Health Claims Exchange (FPM.3.h), can the hospital’s system do it directly, or would that require a manual workaround with the insurer?

A generic Tally-style accounting setup can usually answer “yes” to basic bookkeeping questions — but not reliably to these five, which is exactly the gap between generic bookkeeping and hospital billing automation NABH scores in FPM.

Why FPM Is a Gating Chapter, Not a Nice-to-Have

FPM carries 3 Core Objective Elements — tied with AAC for second-highest of any chapter, behind only DOM’s 6. Two of the three sit in FPM.3, patient billing: a digital system for patients to actually pay for hospital services, and pre-defined charges for all key services and items. The third sits in FPM.1, procurement: digital tracking of quality concerns on purchased hospital assets.

None of these three are satisfied by a hospital simply owning accounting software. A generic ERP or Tally-style setup handles ledgers, invoices, and basic bookkeeping — it doesn’t necessarily give patients a digital way to pay with pre-defined charges, or track quality issues against specific purchased items. “Finance already has software” is a different claim from “finance’s software satisfies FPM’s Core elements,” and the gap between those two claims is exactly where a hospital gets caught out late in a GAP analysis.

This is also why FPM is worth checking early, before committing spend elsewhere in a digital health roadmap. A hospital that invests heavily in clinical digitisation — COP or MOM, for instance — while its billing desk still runs on a spreadsheet and a printed rate card has left a Core gap sitting exactly where every patient touches the hospital on their way out.

This is the same reason operational excellence for Indian hospitals depends on checking foundational, revenue-facing systems early — the same instinct behind understanding why a system works at a structural level rather than just clearing the nearest bar.

FAQ

How many Objective Elements does the FPM chapter have in NABH’s Digital Health Standard for Hospitals?

17 — across 3 standards, out of 182 total across the standard.

What are FPM’s Core (mandatory) Objective Elements?

Three: a digital system for patients to pay for hospital services (FPM.3.a) and pre-defined charges for all key services and items (FPM.3.b), both in patient billing; and digital tracking of quality concerns on purchased hospital assets (FPM.1.d), in procurement.

Does generic accounting software like Tally satisfy FPM?

Not by default. FPM’s specific Objective Elements — a patient-facing digital payment system, pre-defined service charges, quality-concern tracking on purchases, and claims routing through the Health Claims Exchange — go beyond what off-the-shelf bookkeeping software provides out of the box.

Why does FPM.1 have two Objective Elements labeled “d”?

NABH’s own source document repeats the letter “d” for two distinct elements in FPM.1 — one Commitment-band (digital receipt notes) and one Core-band (digital quality-concern tracking). This piece labels them FPM.1.d (i) and FPM.1.d (ii) for clarity; the requirement content is what NABH scores, not the letter.

The Decision

The question FPM actually asks isn’t whether finance has software — it already does. It’s whether that software specifically lets a patient pay digitally with pre-defined charges, lets procurement track quality concerns against purchased items, and can route an insurance claim through the Health Claims Exchange without a manual workaround. A hospital that checks this chapter early, before committing budget to more visible clinical digitisation, avoids discovering a Core gap sitting at the one desk every patient walks past on their way out.