One Set of Books
A hospital is a business. Veona is a native, enterprise-grade ERP, so a patient invoice, a reagent draw, a purchase, a payroll run, and a depreciation all post into one general ledger, with statements computed live and no external accounting system to buy.
Every event in the hospital lands in the same ledger.
Most hospitals run a clinical system for care and a separate ERP for accounting, then spend the month reconciling one against the other. Veona removes that gap. The clinical and operational events that already happen in Veona, a bill issued, a consumable drawn, a supplier invoice submitted, a pay run approved, an asset depreciated, each post one balanced, idempotent voucher into a single general ledger. Trial balance, profit and loss, balance sheet, and cash flow are read live over that ledger. There is no export, no nightly sync, and no second system.
Subledgers that post into the ledger
Billing is the receivables subledger, stock is inventory, procurement is payables, HR is payroll, and assets are depreciation. Each posts through one seam that asserts debits equal credits, runs inside the same transaction as the subledger row so they commit together, and is idempotent on the event, so an invoice cannot be double-counted.
Dimensioned, period-guarded, and immutable
Every ledger line carries the cost center resolved from the originating department and an optional project, so profit and loss can be cut by service line. Postings into a closed or locked period are rejected, and ledger entries are never edited, corrections are reversing vouchers, so the books are tamper-evident.
Four ERP modules, one platform
On top of the ledger sit four native modules. Finance owns the chart of accounts and statements. Procurement runs buying, three-way match, and accounts payable. Assets keeps the fixed-asset register and depreciation. PRM manages the relationship pipeline. Each is a sellable module, and together they are the Veona Enterprise edition.
The events that hit one set of books.
Patient invoice
Issued: debit receivable, credit revenue, with VAT output.
Payment cleared
Debit cash, credit receivable, on the cleared transition.
Reagent draw
Consumed: debit cost of goods sold, credit stock at weighted average.
Goods receipt
Confirmed: debit stock-in-hand, credit goods received not invoiced.
Purchase invoice
Submitted: debit GRNI and tax, credit accounts payable.
Pay run
Approved: debit salary by department, credit statutory and net pay.
Depreciation
Monthly: debit depreciation expense, credit accumulated depreciation.
Deposit
Taken: debit cash, credit patient advances.
Statements
Recomputed live over every one of the above.
One seam, one ledger, live statements.
Event
Something billable, consumable, or financial happens in a Veona module.
Post
The module posts one balanced, idempotent voucher through a single seam.
Guard
Balance, period, and FX are checked before the entry is ever persisted.
Report
Trial balance, P&L, balance sheet, and cash flow recompute live.
The native ERP, module by module.
What buyers ask about the native ERP.
What does one set of books actually mean?
It means there is a single general ledger inside Veona, and the clinical and operational events that already happen in the system, a bill, a stock draw, a purchase, a pay run, a depreciation, post directly into it. There is no second accounting system and no reconciliation between them.
Do I still need a separate accounting package?
No. Veona is a native, enterprise-grade ERP. Finance, Procurement, Assets, and PRM are built in and post into the same ledger as the clinical modules, so there is no external system to license, integrate, or reconcile.
How do I buy it?
Finance, Procurement, Assets, and PRM are each sellable modules you can license individually, or take together in the Veona Enterprise edition, which bundles the full clinical stack with all four ERP modules.
Can I trust the numbers?
Every voucher is balanced before it is persisted, posted atomically with its source row, idempotent per event, period-guarded, and immutable, with corrections made by reversing vouchers, so the ledger is tamper-evident and the statements tie back to source.
See one set of books in action.
A walkthrough of how a clinical event becomes a financial statement, with no external ERP.