Twenty invoices, one wrong account: why coding errors in property management only surface in autumn

In October, a property manager sits down with the annual statement for a forty-unit building and finds a line that doesn’t add up: heating costs are running about eight hundred euros over what the budget had planned for the year. Not a dramatic sum, but enough that someone on the advisory board will ask about it at the next meeting. So she pages back: which invoices were booked under that cost category, when, from whom. After the better part of half an hour, she finds it - an invoice from the heat cost allocator, dated March, that actually belonged to a different building on the same street, but sat only three lines away from it on the collective invoice and got booked to the wrong one.

That, or something close to it, is how a good share of the autumn queries start. The actual mistake happened months earlier, on an ordinary morning when twenty to thirty incoming invoices had to be worked through and this one simply slipped past among the rest.

What actually has to be decided before an invoice gets paid

Before an incoming invoice can be approved, three separate calls have to be made correctly, and none of the three sits as plainly on the invoice itself as you’d like.

Which building. An invoice from a contractor who looks after several buildings in the same neighborhood often names only the job (“heating system repair, as discussed”) and an address that could match more than one similarly named property. A collective invoice from a heat cost allocator is even less clear-cut: a single PDF page listing twelve or fifteen properties and one combined total that has to be split before any single building is even affected.

Which cost category. Does the item run as ongoing operating costs, which get passed on to tenants through the utility bill - or as maintenance, which isn’t recoverable and comes out of the owners’ reserve fund instead? For a routine service contract that’s usually clear; for a repair that grew out of that same service call, it often isn’t anymore. That exact line is the one that shifts most often - and it matters, because it decides whose account ends up carrying the cost.

Which budget year. Every building has its own annual budget with its own line items for the current year. An invoice that arrives in January for work done in December has to be booked to the right fiscal year, or the comparison between planned and actual costs shifts by an amount that, in that form, never really existed.

Photo: sharonmccutcheon / Unsplash

Why the sticky-note fix breaks down at twenty invoices a day

The traditional fix is a note scrawled on the invoice: building number in the corner in pen, then into the folder or straight into the accounting software. At five invoices a day that works, because each one still gets real attention. At twenty to thirty, the assignment turns into routine - and routine is exactly the state in which a similar street name or an over-long collective invoice is most likely to slip through.

The tricky part: the accounting software doesn’t push back. It checks whether an account exists, not whether it’s the right one for the content. An invoice that lands on the wrong building by mistake gets booked without complaint, quietly changing that account’s balance - and is just as quietly missing from the building it actually belonged to. None of this is visible on the day it happens. It only becomes visible once someone eventually lines the two numbers up next to each other.

Why the mistake shows up specifically in autumn

This is the point where this problem differs from most other bookkeeping errors: it doesn’t show up right away. It surfaces later, and at one particular point in the year - the annual statement.

As long as bookings just keep happening, every account looks plausible on its own. One contractor invoice more or less doesn’t stand out in day-to-day bookkeeping; there’s no threshold that trips an alarm. Only once the year-end budget - what was planned - gets set against what was actually booked does a discrepancy become a number anyone questions. And even then, only if it’s large enough to notice. A single invoice for a hundred and fifty euros, booked to the wrong account, may never surface at all inside a budget running into six figures - it just quietly skews the numbers by a small amount, indefinitely.

When the advisory board reviews the statement in autumn, or an owner questions a line item, that’s when the real work starts - not the correction itself, but the tracing: which of the three or four hundred bookings made that year was it. That costs a multiple of the few seconds the correct assignment would have taken back in February, and often enough a figure already communicated to owners, or even a utility bill already sent to tenants, has to be corrected after the fact.

Photo: jakubzerdzicki / Unsplash

What can be sorted reliably in advance - and what can’t

This is exactly where an automated first check earns its keep - not at year-end, but on the day the invoice arrives.

Most cases are genuinely straightforward once it’s on record which supplier belongs to which building: the lift maintenance contract for building A, the buildings insurer for B and C, the caretaker service for D. A document-reading system can pull the sender, amount and service period and check them against that mapping. That’s not a particularly hard task for AI - it’s mostly a well-maintained table, applied consistently, which alone makes a difference in the rush of daily business.

Two cases remain, and they should. A collective invoice covering several buildings can have its split proposed and calculated by a system, but the split itself should be confirmed by someone who knows the contracts. And the line between recoverable and non-recoverable costs is a financial, and partly legal, judgment call, not a formality - a system may flag it (“this looks like maintenance, not a routine service”) but shouldn’t decide it alone. Automate that particular call quietly, and all that shifts is who makes the mistake, not whether one still happens.

If the assignment in your portfolio slips more often than it should

What this kind of first check looks like in practice depends on your operation: which software you use, how many suppliers serve several buildings at once, how often collective invoices come in, and where the maintenance line actually gets drawn in your day-to-day work. An off-the-shelf tool rarely fits assignments and exceptions that have grown organically over years - I build this tailored to your buildings and your existing software, as one person who designs and understands the solution, rather than forcing you into a rigid system.

If you want to know where the errors in your invoice processing actually originate, and what can be caught before the advisory board asks about it in autumn: I’m Eric Menge of EMIT Solution, reachable at info@emit-solution.com and via emit-solution.com. A first conversation costs nothing and looks at where the time in your invoice processing is actually lost.