IAS 16 (Property, Plant & Equipment)¶
IAS 16 Property, Plant and Equipment is the IFRS standard governing how tangible long-term assets are recognised, measured, depreciated, and disclosed in financial statements. In Thailand, the corresponding local standard is TFRS 16 (which carries the IAS 16 substance with local adaptations for the Thai accounting framework).
Hospitals own significant tangible assets — medical equipment is often the second-largest balance-sheet line after buildings — so IAS 16 compliance matters both for external audit and for management reporting.
HEMMS supports parts of the IAS 16 lifecycle and explicitly leaves other parts to Odoo Accounting. This page sets out the boundary honestly.
HEMMS is an equipment system, not an accounting system
HEMMS does not post journal entries. It captures the operational data (cost, in-service date, condition, disposal) that an accounting system needs to depreciate and disclose the asset under IAS 16. Hospitals that need depreciation postings should pair HEMMS with Odoo Accounting and the Thai localization — see the roadmap section.
IAS 16 lifecycle and HEMMS coverage¶
| IAS 16 stage | What the standard requires | HEMMS coverage |
|---|---|---|
| Recognition | Probable future economic benefits + cost can be reliably measured | ✅ maintenance.equipment captures purchase cost, in-service date, location |
| Initial measurement | At cost, including purchase price + directly attributable costs + dismantling provision | ⚠️ Single cost field on equipment; multi-component breakdown not modelled |
| Componentisation | Significant parts depreciated separately | ⚠️ Spare-parts module distinguishes parts; no componentised depreciation lifecycle |
| Subsequent costs | Capitalise replacement parts if recognition criteria met; expense routine maintenance | ✅ Q2 Spare Parts + Q3 Service Contracts cleanly separate the two |
| Depreciation | Systematic allocation over useful life; review at year-end | ❌ Not shipped — roadmap, integrate with Odoo Accounting account.asset |
| Impairment | Test when indicators arise (damage, obsolescence) | ⚠️ Asset Inspection captures Damaged / Lost / Disposed; no posting |
| Derecognition | Remove from books on disposal or no future benefits | ✅ Asset Inspection lost / unused flags feed into derecognition decisions |
| Disclosure | Reconciliation of carrying amount + depreciation method + useful life by class | ⚠️ Equipment data available; report assembly belongs in Accounting |
Recognition: when an item enters HEMMS¶
A piece of medical equipment is recognised in HEMMS when it is created in maintenance.equipment. The form captures:
- Name + serial number + ref. no. (
reffrom OCAmaintenance_equipment_ref= รหัสครุภัณฑ์) - Category (hierarchical via
maintenance_equipment_category_hierarchy) - Purchase cost — field present on Odoo's
maintenance.equipmentby default (cost) - In-service date —
effective_dateon the same model - Location (department + location field)
- Brand and model — added by
roots_hemms_asset_master(Layer 3)
For IAS 16 recognition the auditor cares about (a) that the asset exists, (b) the cost is captured, and © the in-service date is correct. The Mass Import module (Q6) lets a finance team load these fields in bulk from the procurement system at year-end, with full provenance (which spreadsheet, which user, when).
Day-one capture example
A hospital purchases a CT scanner for THB 18,000,000 with installation, calibration, and removal-of-old-CT-scanner costs of THB 1,200,000. Under IAS 16, the recognised cost is THB 19,200,000 (cost + directly attributable costs).
In HEMMS: the BME admin creates the maintenance.equipment record and sets cost = 19,200,000 and effective_date = installation date. The breakdown lives in the procurement system / Odoo Accounting; HEMMS holds the operational view.
Subsequent costs: parts vs repairs¶
IAS 16 distinguishes:
- Replacement of a significant component (e.g., a high-voltage tube in a CT scanner) → capitalise; derecognise the carrying amount of the old component if separately tracked.
- Day-to-day servicing (calibration, cleaning, consumables) → expense through profit or loss.
HEMMS supports this split structurally:
| HEMMS action | Accounting treatment |
|---|---|
Q2 Spare Parts consumption tied to a maintenance.request of type "Repair" with a significant part | Likely capitalise (component replacement) |
Q2 Spare Parts consumption on routine PM (maintenance_type = preventive) | Likely expense |
| Q3 Service Contract spend — recurring vendor service fee | Expense |
| Q3 Service Contract spend — major retrofit covered under contract | Discuss with auditor |
HEMMS does not auto-classify the journal treatment — the spare-parts consumption goes to stock and is posted through Odoo Inventory in the standard way. The hospital's Finance team determines the IAS 16 treatment per material item. HEMMS provides the operational evidence (which part, which equipment, which date, which technician, signed by whom).
Componentisation¶
IAS 16 requires that components with different useful lives be depreciated separately if their cost is significant relative to total cost. For a CT scanner, the body of the machine, the X-ray tube, and the software licence might have lives of 15 / 5 / 3 years respectively.
HEMMS today models each piece of equipment as a single maintenance.equipment record. Componentisation would require either:
- Creating child equipment records for each significant component (workable but not natively supported in the IAS 16 sense), or
- A future
hemms.asset.componentmodel that ties multiple components to one parent equipment for depreciation purposes.
⚠️ This is on the roadmap and is part of the broader depreciation roadmap.
Depreciation roadmap¶
Depreciation posting is not shipped in HEMMS today. The recommended path for hospitals that need IAS 16 / TFRS 16 depreciation:
| Component | Module | Status |
|---|---|---|
| Asset register (data) | maintenance.equipment + roots_hemms_asset_master | ✅ Shipped |
| Depreciation postings | Odoo Accounting account.asset | Available in Odoo Enterprise / OCA equivalents — integration not yet built |
Bridge: equipment → account.asset | Future roots_hemms_ias16 module | 📋 Roadmap |
| Componentised depreciation | hemms.asset.component | 📋 Roadmap (later) |
For an interim solution today, hospitals manually mirror equipment master data into account.asset records in the accounting module and run depreciation there. Mass Import (Q6) can speed the mirroring up.
Impairment¶
IAS 16 (and IAS 36 for the impairment test itself) requires impairment review when indicators arise — physical damage, obsolescence, drop in market value, restructuring.
HEMMS's roots_hemms_asset_inspection module captures condition during the annual ปจป. inspection on a 5-state selection:
| Condition | IAS 16 / IAS 36 indicator |
|---|---|
in_use (ใช้อยู่) | No indicator |
broken (ชำรุด) | Possible impairment indicator — depends on whether repair is economic |
deteriorated (เสื่อมสภาพ) | Possible impairment indicator — review useful life |
lost (สูญไป) | Derecognition trigger |
unused (ไม่จำเป็นต้องใช้) | Derecognition trigger (held-for-sale) or impairment |
This data feeds the impairment conversation between BME and Finance at year-end. HEMMS does not perform the impairment test or post any write-down — that is the accounting team's call, with the auditor.
Derecognition¶
IAS 16 requires derecognition on disposal or when no future economic benefits are expected. HEMMS supports this operationally:
- Annual Asset Inspection flags the equipment
lostorunused. - The BME team raises a final disposal
maintenance.request(e.g., for pickup by an e-waste vendor). - The equipment record's
current_conditionis updated; the audit log captures the change inhemms.stage.transition.log. - Finance reads the ปจป. signed report and posts the derecognition entry in Odoo Accounting.
The signed ปจป. report (under Q4 sign_oca) is the load-bearing evidence the external auditor reads to support the derecognition.
Disclosure¶
IAS 16 requires per-class disclosure of:
- Measurement basis (cost vs revaluation)
- Depreciation method and useful lives
- Reconciliation of opening + additions + disposals + depreciation + impairment + closing
HEMMS provides the additions and disposals data (via the equipment register + ปจป. inspection). The remaining lines (measurement basis, method, life, closing carrying amount) come from Odoo Accounting once the roadmap depreciation integration is in place.
Summary¶
| If you need... | HEMMS today | HEMMS roadmap |
|---|---|---|
| Operational asset register | ✅ | — |
| Cost at recognition | ✅ (single field) | Multi-component breakdown |
| Subsequent cost categorisation evidence | ✅ (Q2 / Q3) | — |
| Depreciation postings | ❌ — use Odoo Accounting | roots_hemms_ias16 bridge |
| Componentised depreciation | ❌ | Future hemms.asset.component |
| Impairment indicators | ✅ (ปจป. inspection conditions) | — |
| Derecognition evidence | ✅ (signed ปจป. report) | — |
| IAS 16 disclosure note | ❌ — assembled in Odoo Accounting | Future export helper |
Related pages¶
- Compliance Overview — coverage matrix across all regimes
- Asset Inspection module — the condition-evidence source for impairment & derecognition
- Spare Parts module — the parts-vs-repair distinction
- Service Contracts module — recurring vendor spend
- For CFO / Finance Director — user-guide companion page