How to Handle a Disputed Charge on a Portfolio Account

Why this matters

On a single-family customer, a disputed charge is one bill. On a portfolio, it is a policy. The same manager will see forty more invoices from you this year, and whatever you do with this one becomes the expectation for all of them. Credit it to keep the peace and you have just repriced every similar charge for the life of the account. Fight it on principle and you can spend a relationship over a couple of labor hours.

There is a second cost specific to portfolios. A dispute on one line frequently freezes the whole batch, because accounts payable holds vendor payments while anything from that vendor is open. One queried line can hold six clean invoices, so the first move is administrative, not persuasive.

First: unfreeze everything the dispute does not touch

Before you argue anything, ask the manager in writing to release the invoices that are not in question, and name them by number. Most will, because holding clean invoices is a habit rather than a policy, and nobody has ever asked them to stop.

If the disputed line sits inside a multi-line invoice, void that invoice and re-issue it as two: one carrying every undisputed line, one carrying the disputed line alone. You have not conceded anything by doing this. You have removed the disputed amount's ability to hold the rest hostage, and you have made the open item small enough that the manager can escalate it without embarrassment.

Do this within one business day. The longer the batch sits, the more likely it is to cross a payment cycle, at which point you are chasing aging rather than a dispute.

The gate, stated once

Every dispute over a charge resolves on one question, and it is not whether the work was needed or well done. It is whether you can trace the charge to an authorization.

Per disputed line, not per invoice, you must be able to produce all four of these from your own records: a named person, a timestamp, a scope that covers the work performed, and an authorization ceiling that covers the amount charged. All four, not three. If all four are present, hold the charge and escalate one level. If any one is missing, credit that line within one payment cycle without argument.

The one partial case: when the only missing element is the ceiling and the other three hold, credit down to the ceiling rather than to zero. The work was authorized in scope by the right person, just beyond what that person could approve alone, and crediting the whole line teaches your own office that authorization traces do not matter.

Note what the gate deliberately excludes. It says nothing about whether the repair was correct, whether the price was fair, or whether the tenant was happy. Those are real questions and they belong in other conversations. Mixing them into a billing dispute is how a two-hour argument becomes a three-month one.

Case A: the after-hours callout that holds

Unit 118, no heat, called in at night. Tech on site 3.4 hours including the return trip for a part. A new manager, four weeks into the account, disputes the whole charge as "not authorized, should have waited for morning."

Run the gate:

• Named person. The answering service log shows the on-call maintenance supervisor by name.
• Timestamp. 22:41, and the tech's arrival stamp is 23:20.
• Scope. The log records "no heat, unit 118, tenant reports occupied," which covers the work performed.
• Ceiling. The agreement gives the on-call supervisor a standing after-hours authorization of up to 4.0 labor hours per event without further approval. The charge is 3.4 hours, which is inside it.

All four elements are present, so the charge holds. The move is to send the four elements as a single short message to the manager, copy nobody, and offer to walk it through by phone. If the manager still refuses, escalate one level with the same four elements attached and nothing else. No history, no tone, no reference to the six other invoices.

The new manager is not wrong to ask. They inherited an account and have no idea what the previous manager agreed to. What resolves this is not argument, it is the trace, and the trace exists because somebody in your office wrote down four fields at 22:41.

Case B: the common-area charge that gets credited

Same portfolio, same month. A tech at the property for a scheduled item is asked by the on-site maintenance technician to "take care of" a common-area problem while he is there. He does, 5.0 hours across two visits. The manager disputes it: no work order, and nobody told her.

Run the same gate:

• Named person. Yes, the maintenance technician, by text.
• Timestamp. Yes, on the text.
• Scope. "Take care of it while you're there" does not describe a scope, and the work grew across two visits from the thing that was pointed at.
• Ceiling. Under the agreement, only the supervisor and above carry an authorization ceiling. The maintenance technician carries none.

Two elements fail, so the line gets credited in full within the cycle, and the credit goes out without a paragraph of explanation attached. A credit issued with an argument stapled to it reads as resentment and buys you nothing.

Why the same portfolio produced opposite answers

Both charges were for real work that somebody at the property genuinely wanted done. Both were requested verbally by a person the tech reasonably trusted. The outcomes are opposite because the gate does not test good faith, it tests traceability, and traceability is something your own office controls entirely.

That is the useful lesson: the shop decided the outcome of both disputes months earlier, at intake, by what it recorded and from whom it accepted work. Case A was winnable because of four fields captured at night by a dispatcher. Case B was lost the moment a tech accepted a verbal from someone with no ceiling and nobody in the office caught it before the invoice went out.

Concessions set a rate, not a price

On a portfolio, never concede an amount without changing a rule at the same time. A credit on its own teaches the account that disputing works. A credit paired with a written rule change teaches it that the process changed.

In Case B the pairing is: credit the 5.0 hours, and in the same message propose that any request from on-site staff be converted to a work order before the tech starts, with a named fallback for after-hours. You have given up hours once and closed the route that produced them. If you credit and change nothing, expect the same charge and the same dispute next quarter, and expect the credit to be assumed rather than requested.

The reverse also holds. If you hold a charge, do not also hold a grudge on the next borderline call. Holding correctly on a traceable charge and being generous on a genuinely ambiguous one is a coherent position a manager can work with.

The three disputes that are not about authorization

Not everything is an authorization problem. Sort a dispute into one of three types before you run the gate, because two of them route elsewhere:

• Authorization. "Nobody approved this." Runs the gate above.
• Price. "This costs more than it should." Does not run the gate. This is a rate conversation for the agreement, and it belongs at renewal or in a scheduled review, not in an accounts payable thread. Hold the invoice, agree to review the rate separately.
• Quality. "It did not fix the problem." Does not run the gate either. This is a warranty question. Send a tech before you send a paragraph, and issue the return visit as a zero-charge document so the record shows the shop absorbed it.

Shops lose the most time by answering a quality complaint with an authorization trace. It is the correct answer to a question nobody asked, and it reads as evasion.

Close every dispute in writing, in one paragraph

However a dispute resolves, send a short written close: what was disputed, what was decided, and what changes going forward. One paragraph, no history, no tone.

That note is doing two jobs. It is the precedent document, so the next manager on the account inherits a decision rather than an argument, and property manager turnover means there will be a next manager sooner than you think. It is also the only version of the story that survives; without it, the account remembers that there was a problem with your invoicing and not what the problem was or that it was fixed.

Store the close against the account, not against the invoice. Invoices get archived by period and become effectively unfindable; the account file is where somebody actually looks when the same question comes up two years later.

How to verify you got this right

Measure per account, per quarter, on disputed lines rather than disputed invoices:

• Count disputed lines raised.
• Count how many you could trace on all four elements.
• Count how many were still open after two payment cycles.

The gate for the account: if fewer than 8 of every 10 disputed lines are traceable on all four elements, the defect is in your intake, not in the manager. Fix the missing element with the highest count first, one at a time, and re-measure the next quarter rather than the next month, because dispute volume is too low to read reliably over four weeks.

Second check: no disputed line should still be open after two payment cycles. Anything older has stopped being a dispute and become aging, and it needs a decision to write off or to escalate above the manager, not another follow-up message.

Run the two cases above through the account gate. Two disputes, one traceable on all four elements, one failing on two of them, is a 50 percent trace rate on that pair. If the quarter's full count sat at that ratio it would clear the trigger badly, and the missing element with the highest count is scope, which points directly at the intake rule proposed in Case B.

References

• See related: How to Set Approval Limits With a Property Manager
• See related: The Multi-Property Work Order SOP
• See related: What Makes an Invoice Easy to Approve
• See related: The Three-Party Problem in Property Management Work