The Obligation That Lives in the Warehouse
Almost every compliance obligation belongs to finance and is performed at a desk. This one belongs to the buyer and is discharged on a loading bay — by somebody who has never been told they are part of a control.
Think about where compliance work physically happens in your organisation. Somebody at a desk, with a screen, on a cycle — monthly, quarterly, whenever the date falls. It is finance's work, it is done indoors, and the people who move goods around are not part of it.
That model is so consistent that it is invisible. Which is why the Colombian arrangement catches competent organisations out: the obligation is the buyer's, and what it wants acknowledged is a delivery. Not a payment, not a return, not a reconciliation. A delivery — an event that happens on a loading bay, at a moment nobody in finance witnesses.
So the person who can discharge it is a receiving clerk. And nobody has told them.
Two things, said before the argument starts
First: we do not send the acknowledgement. We are not connected to it, we transmit nothing, and if that is what your decision turns on then a provider who already does it is the right purchase. Second: the regulatory detail behind this — which instrument, which resolution, what the timing is — is set out and sourced on our Colombia market page, and it is not repeated here. A blog post citing a regulation it did not read is worse than a post that points at one which did.
Why this fails silently, which is the whole problem
Most compliance failures announce themselves. A return is late and something arrives. A figure does not reconcile and somebody investigates. There is a mechanism for finding out.
Here the failure mode is a deduction lost with no error appearing anywhere. Nothing was rejected. No document bounced. The goods arrived, they were put away, they were sold, and the operation worked perfectly — while a thing that needed to happen at receipt did not happen, and no system anywhere in your building produced a symptom.
| Ordinary compliance failure | This one |
|---|---|
| Finance discovers it | Nobody discovers it |
| A deadline passes visibly | A receipt is completed normally |
| There is an error to investigate | There is no error |
| The cost is a penalty | The cost is a deduction that quietly was not available |
| You find out in weeks | You find out when somebody reconciles a year, if ever |
An obligation with no failure signal is not really an obligation on the organisation. It is an obligation on one person remembering, which is a different and much weaker thing.
What actually has to change, and most of it is not software
Three things, and the order matters because the first is free and the third is the one everybody starts with.
-
Tell the receiving team they are part of a control
Costs nothing and is skipped almost universally. A clerk who knows that completing a receipt properly protects a deduction behaves differently from one who thinks they are updating stock. This is the single highest-return action available and it is a conversation, not a project.
-
Make the receipt event exist as a record, with a time and a person
Not a stock adjustment at the end of the day. An acknowledged receipt, attributable to whoever accepted the goods, against the order it belonged to. Without that, there is nothing to point at afterwards — and afterwards is when somebody asks.
-
Connect it to whatever transmits
This is the integration, it is the part vendors talk about first, and it is worth the least on its own. A transmission fed by a receipt nobody recorded properly sends a confident message about an event that was never captured.
Where we sit in that list
Squarely in the middle item, and nowhere near the third. Which is a narrow claim, and it happens to be the item the middle of the list says matters more.
Receiving against the order, with tolerances
Goods received against order lines with your own quantity and price tolerances, so a short delivery or a moved price surfaces as an exception at the door rather than settling silently.
The receipt as an attributable event
Who accepted what, when, against which order — a record with a person and a time on it rather than a quantity that changed overnight.
Approvals that block before the commitment
Because an obligation attaching at receipt is much easier to meet on a purchase somebody authorised deliberately than on one that appeared.
Documents held against the transaction
So when a question arrives about one delivery in one period, answering it is a retrieval. In a market where the failure leaves no trace, the retrievable record is the only defence.
Sending the acknowledgement
Not built and not connected. This is the third item in the list above and it is genuinely somebody else's product today. Commissionable as an integration against a published specification, with a written specification, a timeline and a price — and if it is your binding constraint, buy from whoever already ships it.
Telling you whether a particular deduction is available
Not ours. That is your adviser's judgement about your circumstances, and this post deliberately contains no regulatory detail for exactly that reason.
The general lesson, and it is an organisational one
When a compliance obligation is discharged by an operational act, the control has moved out of the department that owns compliance and into the department that owns the act. Nobody usually notices the transfer. Finance still believes it is accountable; the warehouse has no idea it is.
It is worth asking, in any market: is there anything we are required to do that is performed by somebody who does not know it is a requirement? Colombia makes the question concrete, but the shape appears wherever a certificate has to be checked at a gate, a condition recorded before a job starts, or a document collected at a handover.
What is built here, what is not, and what we would decline is on the Colombia market page, including the sourced regulatory detail this post deliberately leaves to it. The market next door, where the document is signed by the state before your customer sees it, is Mexico.
