Money in Veridien is exact, by design

Every hotel system stores money. Few of them store it exactly. Veridien treats every amount as a decimal in its own currency, never a floating-point number, and never a total added up across currencies. This post explains the three rules behind that and why they matter more in a small hotel than in a big one.

Rule one: a number is a decimal, in one currency

A folio line for a room night in US dollars and a bar charge in Maldivian rufiyaa are two different things. Veridien keeps them apart. Each line carries its own currency and, frozen at the moment it was posted, its value in the property's base currency at that day's rate. Nothing is ever recalculated later. A report you run next year adds up the same numbers you saw on the day.

Rule two: a folio is settled per currency

A folio with a dollar balance of zero and a rufiyaa balance of minus fifty is not settled, even if a naive conversion would net it to nothing. Veridien only marks a folio as settled when every currency on it nets to zero on its own. Where a conversion does appear, for example a guest paying a dollar charge in euros, the receipt shows the amount and the rate plainly, with no approximation marks.

Rule three: the past does not change

Charges, fees and commissions are recognised once, when they are posted. Editing a charge later never rewrites past revenue. Payment methods you define yourself, such as a card terminal with a processing fee, freeze that fee on each payment at the moment it is taken, so changing the fee next month changes next month, not last month.

Why this matters more for a small property

A large chain has a finance team that reconciles the system against the bank every week and catches what the software got wrong. A twelve-room guesthouse has one owner and a spreadsheet. If the software rounds, or converts silently, or lets an edit ripple backwards, nobody notices until the accountant does. So the software has to be right the first time. That is the standard Veridien is built to, and it is why the accounting side of the product stays deliberately simple: exact records in, honest totals out, and nothing clever in between.