The Threshold That Is Not Money
Some legal limits are not amounts of money. They are multiples of a unit the state revalues — once a year in Colombia, once a day in Chile — which means a system that stores the limit as currency is not wrong yet, it is wrong on a schedule.
Here is a sentence from Colombian tax law that looks unremarkable and is not: a point-of-sale till receipt may not be issued for more than five UVT. Not five thousand pesos, not any number of pesos. Five of a unit — and the unit is revalued every year.
This is a device that a great deal of software has no shape for, and it is common enough across Latin America to be worth understanding before you configure anything. The statute names a quantity. A separate instrument, published on its own cadence, says what that quantity is worth. The law does not change; the amount it imposes changes constantly.
Two speeds of the same idea
Colombia and Chile both do this, and they sit at opposite ends of how often it moves — which is useful, because it shows that the problem is not "an annual update to remember".
| Colombia — the UVT | Chile — the UF | |
|---|---|---|
| What it is | A tax value unit that statutory figures are expressed in | A unit of account the authority publishes a value for |
| Who sets it | The tax authority, by resolution | Published by the authority as a dated series |
| How often it moves | Once a year | Every day |
| When you find out | Before 1 January, for the year ahead | Daily, in a published table |
Colombia's is set out in article 868 of the Estatuto Tributario: the value is adjusted annually by the change in the consumer price index for middle incomes, and the tax authority must publish the figure for the coming year before 1 January. The article also fixes the base — twenty thousand pesos, at 2006. Everything since is indexation.
Chile's moves on a different order entirely. The Servicio de Impuestos Internos publishes a table of daily values: on 1 September 2026 it was published as 40.875,09 and on the 2nd as 40.876,41. Those two figures are facts about a table on two named days, which is the only honest way to state them — and it is why you will notice we have not printed a "current" value for either unit anywhere on this page.
A page that told you today's value would be committing the exact error it is describing. That is not caution; it is the argument.
Why software gets this wrong, and gets it wrong silently
Almost every system that holds a limit holds it as an amount of money, because almost every limit anybody has ever needed to store is one. A credit limit, an approval ceiling, a reorder value — all amounts, all stable until somebody deliberately changes them. That assumption is so well founded it is rarely written down, which is exactly why it is not noticed when it stops being true.
Store an index-denominated limit as currency and you have not made an error. You have made a correct entry with an expiry date nobody recorded. It is right on the day it is entered, it stays right for a while, and it goes wrong without any event occurring in your system at all. Nothing was edited. Nothing failed. The number simply stopped agreeing with the law while sitting perfectly still.
And in Colombia the ceiling is only half of it
The five-UVT rule is worth finishing, because the consequence attached to it is sharper than the limit. Under the same paragraph of article 616-1, a point-of-sale till receipt gives the buyer no input VAT and no deduction at all. Where the buyer is entitled to claim, they can require a proper sales invoice instead.
So a retail system in Colombia is deciding two things at once when it issues a document: whether it is over a ceiling denominated in a unit that moved in December, and whether the person at the counter needed a document of a different kind entirely. Neither is a presentation choice and neither is visible on the receipt.
What ours does, since we are the ones raising it
Our limits are amounts of money. There is nothing in the product that holds a value expressed as a multiple of an external unit, nothing that fetches such a unit, and nothing that would notice one had been revalued. Our point-of-sale also has no concept of a document type that forfeits the buyer's credit, and no ceiling above which it must become a full invoice — it produces a sale with a customer, a tax amount and a receipt. Both gaps are stated on our Colombia page in the same words. Worth separating from a different question we have written about: whether a stored limit is consumed by anything at all is a governance problem about our own controls, and this is a modelling problem about somebody else's law.
What a buyer can actually check
Three questions, and none of them takes long
Can a limit in your system be expressed as a multiple of something rather than as an amount?
What you will hear
Usually no, and usually said quickly.
How to read it
No is a perfectly acceptable answer and it is ours. What matters is whether it is followed by a plan or by a change of subject. A vendor who has met this market will already know the question.
If the unit is revalued in December, what happens in January?
What you will hear
A description of somebody updating a setting.
How to read it
That is a real answer for an annual unit and it is not a real answer for a daily one. Ask which cadence they are describing, because the two look identical in a demonstration.
What reads the limit — does anything actually refuse?
What you will hear
Sometimes a warning, sometimes nothing.
How to read it
A limit that is stored, correctly, in the right unit, and consulted by nothing is a decorative field. This is the cheapest question on the list and it disqualifies more systems than the other two.
What AWRA OpsHub does today
- A tax rate stored on every sales invoice line, so a document stays true to what was charged and no later change rewrites it.
- Multi-currency documents and reporting, with a fixed base currency so a reported figure always has an unambiguous unit behind it.
What it does not do
- We cannot express a limit as a multiple of an external unit. Our thresholds are amounts of money. Nothing fetches an index value and nothing would notice one had changed.
- Our point-of-sale has no concept of a document that forfeits the buyer's credit, and no ceiling above which it must become a full invoice.
What is not built for your market today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do in your market. Kenya's eTIMS integration and its maintained payroll engine exist because Kenyan clients needed them and commissioned them; neither appeared by itself. The same door is open here. If the seam to a clearance provider, a supplier invoice that can be read, a limit that is not an amount, a bank or mobile money feed, a statutory return format, a rule your own operation needs that the standard one does not have, or a link to a system you already run is what stands between you and a decision, tell us and we will scope it as a build — written spec, timeline and price — before you commit to anything.
Which end of the document you stand at, and what the limit is written in
Three builds cover most of what this region exposes, and the first is a seam rather than a system. Document exchange with the authority runs through a role somebody is accredited for, so what we build is the two-way join to the provider you pick — our document handed over in the shape they expect, and the reference, status and any acknowledgement written straight back onto our record, which is what turns "which of ours are not yet cleared" into a report rather than a reconstruction. Second, reading a supplier's electronic invoice into lines that carry tax, so the purchase side holds a rate and not only an amount. Third, a limit expressed as a multiple of an index unit rather than as a sum of money, with something that actually reads the unit when it is revalued. All three are data-model changes rather than settings, and we would quote them as such.
Local payment rails, and obligations that fall on the buyer
Statement feeds and local payment rails wired into the Payments Register, alongside the buyer-side obligations this region is unusual for — an acknowledgement generated from a receiving event and transmitted, and a report of purchases received but not yet acknowledged. Receiving against the order already runs; the outbound half is the buildable part on top of it.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
Payroll and statutory returns
A local payroll engine with income tax tables and social security contributions computed on live employee records, producing returns in the layout your authority expects rather than rebuilt each month.
Systems you already run
The accounting package, CRM, online store or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. No roadmap slide, and no pretending in a demo that something exists when it does not.
Tell us what you need integratedThe short version
If any limit that binds your business is written in law as a quantity of something rather than as an amount of currency, the question to ask about any system is not whether it can store the number. It can. The question is what happens on the day the number stops meaning what it meant, because that day arrives without an event, without an error and without anybody touching the record. In Colombia it arrives every January. In Chile it arrives tomorrow.
