What is Invoice exception?

An invoice exception is a supplier invoice, or a single line on one, that does not match what the hotel ordered, received, or agreed to pay, and therefore needs a human decision before payment. It is a question raised against a bill — not a verdict, and not an accusation that anyone did something wrong.

The exceptions a hotel actually sees.

• A unit price higher than the purchase order or higher than the last time the same item was bought
• Fewer units delivered than were billed — a short delivery or substitution
• A second copy of an invoice already paid, or the same invoice under a slightly different number
• Fees and surcharges that move independently of the goods: delivery, fuel, bottle deposits, environmental charges
• A pack size or unit of measure that changed while the case price stayed the same
• A rate billed above a supplier pricing agreement the hotel already negotiated

A worked example from a live property.

At a Niagara Falls hotel running Atrium across eight suppliers, the exception queue surfaced 10 spend anomalies, two of them critical. Two of the clearest were not product prices at all. A CRV bottle fee moved from $2.00 to $6.00. A fuel surcharge moved from $7.00 to $12.00.

That is a 200% increase and a 71.4% increase, sitting on lines almost nobody reads, on invoices whose totals looked entirely normal. A reviewer scanning for a big number would never find them — the numbers are small. They only become visible when something compares this week’s line to the same line last month.

Why exceptions are usually found too late.

Most hotels meet their exceptions at month-end, inside a reconciliation, when the payment has already gone out. At that point the conversation with the supplier is a refund request rather than a hold, and refund requests lose to the next week’s delivery schedule almost every time.

The other reason is volume. That same property forwarded 1,214 invoice lines across eight months — well over a hundred a month to compare by hand, and the person doing it is usually also running the front desk or the kitchen.

An exception is a question, not a judgment.

A good exception carries its own evidence: the line, the expected value, the billed value, and the variance. Some resolve immediately — the price rose because the contract allowed it, or the substitution was approved at the door. Those are supposed to close quickly. The point is that they close on purpose.

This matters because a review layer that cries wolf gets ignored within a month. An exception queue is only useful if the person opening it trusts that most items on it are worth the thirty seconds.

How an exception actually gets resolved.

• Approve it, because the difference is explained and acceptable
• Hold the invoice and ask the supplier for a corrected copy or a credit memo
• Pay the undisputed portion and keep the contested line open
• Update the agreed price, because the increase was negotiated and the baseline is simply out of date
• Escalate it to whoever owns the supplier relationship, with the evidence attached

Every one of those is a human decision. Software can assemble the evidence and put it in front of the right person on the right day. It should not be the one choosing.

What Atrium does about it.

Atrium reads every line of every forwarded invoice and raises exceptions into a live queue before payment. It never moves money and never disputes anything on its own. Your team holds, requests a credit, or approves — the decision is always yours. See pre-payment exception review for how the queue works in practice.

Two adjacent terms are worth reading next: 3-way matching is the check that generates most exceptions, and spend leakage is what happens when they go unanswered.