The Approval That Nobody Actually Had

Why this matters

An invoice that will not get paid rarely announces itself as a dispute. It just ages. Nobody is angry, nobody complains about the work, the manager keeps answering the phone and keeps saying it is in process, and three months later you are still holding it.

The cause underneath a large share of these on managed property is not slow payment and not a disagreement about quality. It is that the person who told you to proceed did not have the authority to tell you to proceed, and neither of you knew it at the time. This is one of those, followed from the first symptom to the confirmed cause, including the two hypotheses that ate three weeks before anybody looked in the right place.

One thing that does not wait for any of this. If the work removes an active hazard in a common area or an occupied unit, the hazard action happens immediately regardless of approval status: isolate the source, barricade the area with a rigid barrier rather than tape, or evacuate as the hazard requires, then notify the manager. Approval governs whether you perform the repair, never whether you leave a live hazard in place for a signature.

The symptom

A repair on a common element at an association-managed property. Terms were net 30. At the point the shop escalated internally, the invoice was 97 days old.

The surface facts, all of them unhelpful:

• The work was completed, verified, and closed out with photographs.
• No complaint, no callback, no warranty claim.
• The manager had acknowledged the invoice by email twice and both times said it was in process.
• Other invoices to the same account, issued after this one, had been paid.

That last point should have redirected the investigation on day one and did not. When newer invoices to the same payer clear while an older one sits, the problem is specific to that invoice, not to the account's cash or its process. The shop spent three weeks treating it as an account problem anyway.

Hypothesis one: the invoice never landed correctly

The cheapest thing to check, so it went first. Portfolio invoices get rejected silently all the time for missing a work-order number, going to a site address instead of an accounting address, or lacking a unit or property reference that their system requires to code the expense.

Checked: the invoice carried the work-order number, went to the accounts email the shop had used for a year, and had been acknowledged in writing. Two other invoices sent to the same address in the same month were paid.

Ruled out. Worth ten minutes and it eliminated the most common cause, which is why it goes first even though it was not the answer here.

Hypothesis two: this is just their payment cycle

The plausible one, and the one that cost the most time because it is partly true and therefore keeps producing reassuring explanations.

Association-managed properties commonly pay on a cycle rather than on receipt: invoices are batched, reviewed, and released against a check run that may be monthly and may be tied to a board meeting that is also monthly. A 45-day or 60-day actual against a 30-day term is normal on that structure and is not evidence of anything.

Checked: the check run was monthly. The invoice had been outstanding across three of them.

Not ruled out, but demoted. A cycle explains 45 days. It does not explain 97, and it cannot explain why later invoices cleared through the same runs this one sat through. The tell that should have collapsed this hypothesis on the first day: a cycle delay applies to the whole batch, and this invoice was not moving with its batch.

Hypothesis three: somebody is unhappy with the work

The one shops jump to emotionally and it is worth disproving properly rather than assuming.

Checked directly with a plain question to the manager: is there anything about the work itself that is holding this. The answer was no, and the closeout record with photographs was in their file. No callback had been logged, and the association's own maintenance log showed no follow-up on that element.

Ruled out. And ruling it out mattered, because it removed the temptation to offer a reduction to make the problem go away, which would have paid for a defect that did not exist.

What was actually true

The fourth question is the one that found it, and it is the question nobody asks because it sounds like an accusation: who approved this, and what is their limit?

The manager had a per-item spending authority set by the association's governing documents. Repairs below that figure they authorize alone. At or above it, the board approves, and the approval is recorded in the minutes of a meeting.

The sequence that produced the stuck invoice:

1. The work order was opened as a diagnostic, comfortably under the manager's limit. The manager authorized it, correctly and in writing.
2. Diagnosis found a larger repair. The shop provided an estimate. That estimate was above the manager's limit.
3. The manager, wanting it handled and reading it as an extension of an already-approved order, said proceed by phone.
4. The shop proceeded, holding a written authorization for the diagnostic and a verbal for the repair.
5. The treasurer, reviewing the batch, found an expenditure above the manager's authority with no board minute approving it, and pulled it out of the run pending ratification.

Nobody in that chain acted in bad faith. The manager believed they were approving a continuation. The treasurer was doing exactly their job. The shop had a written approval, just not for the thing that mattered. And because the invoice was pulled from the batch rather than rejected, no notification of any kind was generated. It simply stopped moving while everything around it kept moving.

How it was confirmed

Two requests, both polite, both specific:

"Can you send me the minute reference for the board approval on this one, for our file?" This is the diagnostic question: a routine documentation request, it accuses nobody, and it cannot be answered vaguely. The answer came back as a version of "let me check," which is itself the finding.

"What is your authority limit for a single repair item?" Asked once, plainly. Managers answer readily because it is not a secret and it makes their own life easier.

With those two answers the cause was confirmed in one afternoon, after three weeks of chasing an account that did not have a problem.

Getting this one paid

Ratification, not escalation. The expenditure was legitimate, the work was done and accepted, and the association had received the benefit of it. What was missing was a governance record, and boards create those at meetings.

The shop assembled one packet: the original diagnostic authorization, the estimate, the completion report with photographs, and a short cover note stating the work performed and the date. No argument, no demand, no interest claim at that stage. The manager put it on the agenda for the next monthly meeting, the board ratified it, and it cleared on the following check run. It was already 97 days old when the cause was found, and ratification plus the next run added most of another cycle.

The escalation the shop did not do is worth naming. Threatening a lien or a collections referral against an association over an approval defect the manager caused, while that manager is the person who has to put it on an agenda, converts a solvable clerical problem into an adversarial one and costs the account. Escalation is the right tool against a payer who will not pay. It is the wrong tool against a payer who cannot pay until a body meets.

The number that hid it

This account's invoice aging looked fine, which is why nobody caught the pattern earlier.

Across the year the shop issued 18 invoices to this payer. 15 of them were routine, under the manager's limit, and paid at a median of about 35 days against net 30 terms, which is healthy for a cycle-paying account.

3 of the 18 exceeded the manager's limit. Two of those had already happened before this one and had been paid at 74 and 102 days, a mean of 88 days, which is roughly three times the stated term. The third was the 97-day invoice under investigation.

So the account's median days-to-pay was about 35, and the median was true, and the median was useless. The three invoices that carried the problem are 3 of 18, about 17 percent of the invoice count, and they represented roughly 31 percent of the year's billed hours on the account, because over-limit items are by definition the larger ones. A median hides a minority; a minority holding a third of the work is not a rounding error.

The measurement that would have caught it: separate aging by whether the item was above or below the approver's authority limit. Two rows instead of one. Had that split existed, the pattern was visible after the second occurrence, a full year before anyone went looking.

What would have changed the conclusion

• A landlord-owned property with a single owner rather than an association. No governance limit exists, the manager's authority is whatever the owner delegated, and a stuck invoice at 97 days is far more likely to be a cash problem or a genuine dispute. The diagnostic question changes from "what is the minute reference" to "who else has to sign this."
• A documented emergency. Most association governing documents allow expenditure above a manager's limit to address an emergency without prior board approval, because a board cannot meet in an hour. A written emergency declaration from the manager at the time, naming the condition, would have given the treasurer a basis to release it without ratification. That declaration, at the moment of the decision, is worth more than any amount of chasing afterward.
• A purchase order system. Where the payer issues numbered purchase orders the ceiling is enforced mechanically, and the failure mode moves from an invisible approval defect to a visible PO overrun, which is a much easier problem.
• Work under a maintenance agreement with a pre-approved scope. Recurring scope inside an agreement the board approved once does not need per-item approval. This is one of the strongest arguments for putting routine portfolio work under an agreement rather than running it as a stream of individual orders.

The gate that prevents the next one

Stated so a technician or a coordinator can apply it without judgment:

Before starting work on a managed property, confirm in writing both (a) the approver's per-item authority limit and (b) that this item falls under it. Where the estimate is at or above the limit, do not start until you hold one of three things: a higher approval reference (a board minute number, a purchase order number, or a written approval from a regional or owner), or a written emergency declaration from the manager naming the condition. Unit of analysis is one work order. Where an estimate crosses the limit mid-job, stop at the limit and re-approve; do not continue on the reasoning that it is nearly finished.

Run the case through it. The diagnostic was under the limit and correctly authorized, so the gate passed at step one. At step two the estimate crossed the limit, which under the rule requires a stop and a minute number, a PO, or a written emergency declaration. The shop had a phone call from a person below the ceiling, which is none of the three, so the rule says do not proceed. It fired exactly where the failure happened.

Two supporting habits make the gate usable rather than theoretical. Record every approver's limit on the account record, not in someone's head, and refresh it when the manager changes, because it is set by the governing documents and not by the person. And when you get an approval by phone, send the confirming line yourself the same hour: what was approved, by whom, and under which reference. If the reply that comes back cannot name a reference above the limit, you have found the problem before you have done the work instead of ninety days after.

References

• See related: How to Get Approval Before You Do Extra Work
• See related: Verbal Approval vs Written Approval Decision Tree
• See related: The Payment Terms That Make or Break Commercial Cash Flow
• See related: The Property Manager as a Repeat Client
• Community association governing documents and board spending-authority provisions; the limit and the emergency-expenditure provision are property-specific and are the documents to confirm against