A Department That Is Only a Word
A requisition carries its department as free text. A purchase order carries it as a foreign key. The bridge between them is a lookup by exact name — and when it fails, the order is raised, approved, received and paid with no department on it at all, and no budget ever hears about it.
The finding, immediately
Where a department reaches a purchase order only via the requisition, it does so by matching the requisition's free-text department name against your department list by exact name. A trailing space, a plural, an abbreviation or a different capitalisation produces no match, no department on the order, and therefore no budget consumption. Nothing warns. Fix it by never typing a department name and always choosing from the list — which means agreeing the list first.
Two records in this product hold the same idea in two different ways, and the join between them is the weakest thing in the procurement chain.
A requisition — the request that starts everything — holds its department as a string. A purchase order holds its department as a reference to your department list. Somewhere between the two, a string has to become a reference.
How the conversion happens
When a purchase order is created from an approved quotation, the code looks for a department in a specific order. First it takes one supplied directly. Failing that, it takes the one on the request for quotation, if that carries one. And failing that, it reaches back to the original requisition, takes the department name written there, and searches your department list for a department with exactly that name.
If it finds one, the order gets the department. If it does not, the order gets nothing, and the process carries on.
No error, no warning, no exception queue. An order with no department is a perfectly valid order.
What breaks the lookup
| Department list | Typed on the requisition | Match? |
|---|---|---|
| Operations | Operations | Yes |
| Operations | operations | No — the lookup is by exact name |
| Operations | Operations | No — a trailing space is a different name |
| Facilities Management | Facilities | No |
| IT | I.T. | No |
| Finance | Finance Department | No |
Compare this with the budget category match, which lowercases both sides before comparing and therefore forgives the second row here. Two string matches in the same chain, written at different times, with different levels of defensiveness. The department one is the stricter and the more consequential.
What actually happens downstream
Everything works. That is the problem.
-
The order is raised
With a supplier, a value, lines, a delivery destination and an approval. Nothing about it is wrong.
-
The approval runs
Requisition approval is genuinely enforced — an order cannot be raised against a request that has not been approved. That control is unaffected.
-
The goods arrive and are matched
Ordered against received, with tolerances, and the payment gate holds until it reconciles. Also unaffected.
-
The budget is not consumed
Budgets are held per department and category. An order with no department cannot consume a departmental budget, so the department reads as underspent by exactly the amount of the orders that failed to match.
-
Nobody notices, because underspend is good news
A department over budget generates a conversation within days. A department under budget generates a compliment at the quarterly review.
Why a Portuguese operation is likely to hit it
Two ordinary characteristics, neither of them unusual, that happen to combine badly with an exact-name lookup.
The first is bilingual working. Where the interface is in English and the organisation talks in Portuguese, department names get written both ways by different people on different days, and "Manutenção" and "Maintenance" are not the same string. A department list in one language and requisitions typed in another is a guaranteed miss.
The second is multi-site structure. A business with an operation in Lisbon and another in Porto tends to name departments with a qualifier — and whether the qualifier is in the name or implied is exactly the kind of thing two people decide differently.
Four questions that find this class of defect in any product
Is the department on a requisition a reference or a name?
A good answer sounds like
A reference, chosen from a list.
What it actually means
Ours is a name on the requisition and a reference on the order, which is where the conversion — and the failure — lives.
What happens when the conversion fails?
A good answer sounds like
A refusal, a warning, or an exception queue.
What it actually means
Ours does nothing. Silence on a failed join is the pattern to hunt for; it is far more common than a broken join that shouts.
Show me spend with no department against it.
A good answer sounds like
A filter and a total.
What it actually means
If that figure cannot be produced, you cannot audit the join at all. It is the single most useful number on this page.
Is the match case-sensitive?
A good answer sounds like
A precise answer, and a demonstration.
What it actually means
Ours is, on the department, and is not, on the budget category. Two joins in one chain behaving differently is normal and worth checking in any system.
The right fix is upstream, not a fuzzier match
A more forgiving comparison would hide the problem rather than solve it — the day somebody adds a genuinely new department, a fuzzy match sends its spend to the wrong budget instead of to none. The work worth doing removes the string.
A department reference on the requisition
The department list exists and the order already holds a reference. Making the requisition hold one too removes the conversion entirely, and it is the cleanest fix available.
A warning when the join fails
Cheaper, smaller, and useful even after the first fix: an order created with no department, where a name was supplied and did not resolve, is an exception somebody should see.
An unattributed-spend figure
Total value of orders with no department, per period. This is the number that would have found the problem, and it is a report rather than a feature.
We do not publish dates. If departmental budget control is a governance requirement for you rather than a management preference, say so and we will come back with a written scope, timeline and cost.
Scope the department joinWhat AWRA OpsHub does today
- Requisition approval genuinely enforced — an order cannot be raised against a request that is not approved.
- Departments as a maintained list, referenced by purchase orders, and budgets held per department and category.
- Approved purchase orders counted as commitment against a budget, not only paid ones.
- A department taken from the request for quotation where one is set, before any name lookup is attempted.
- Workflow rules that gate on an order's total value.
- A two-way match on receipt with per-organisation quantity and price tolerances, and a payment gate that holds a discrepant order.
What it does not do
- A department reference on a requisition. It is free text, and the conversion to a reference is an exact-name lookup.
- Any warning, refusal or exception when that lookup fails. The order proceeds with no department.
- A report of spend with no department attached.
- Case-insensitive or whitespace-tolerant matching on the department name, unlike the budget category match, which does lowercase both sides.
- Budget dimensions beyond department and category — no project, no branch, no cost owner.
Not ours, by choice
- Where the department is set on the request for quotation, the name lookup never runs and none of this applies. The exposure is specific to the path where the department exists only on the requisition.
- The rest of the procure-to-pay chain is unaffected by a failed match. This is a reporting and control gap, not a transactional one.
- Nothing here is Portuguese. It is what an exact-name join does when two people type; bilingual working simply makes it certain rather than likely.
Audit your department names this afternoon
Export your requisitions, take the distinct department values, and compare them to your department list. Anything on the first list that is not on the second is spend with no budget behind it. Send us both lists and we will do the comparison with you.
Run the comparisonFrequently asked questions
Can I fix this by renaming my departments?
Partly, and it is the right first move: make the department list match exactly what people are already typing, rather than the other way round. The residual risk stays, because the requisition field is free text and the next new person will type something new.
Does the order still count against the budget if I set the department later?
Budget consumption is computed from orders carrying the department, so attaching one later brings the order into the figures. The difficulty is finding the orders that need it, which is why the unattributed-spend list matters more than the fix itself.
Is the category match on budgets the same problem?
The same shape, one degree less severe, and it is worth reading alongside this one — see [A Budget That Matches on a Word](/blog/a-budget-that-matches-on-a-word). That comparison lowercases both sides, so it forgives capitalisation and nothing else. Two strings on two records, both feeding the same budget, with different tolerances.
