Finance and Bookkeeping

Accounts Receivable for roofing contractors

Very few unpaid invoices are refusals. Most are waiting on something specific that nobody on either side has said out loud.

The three things you get back

An ageing you can act on, meaning invoices dated from the work rather than from whenever somebody typed them in, credits applied, and part-billed jobs visible as one position rather than as fragments.

Against each slow invoice, a named reason. Not a status like awaiting payment, which restates the problem — an actual answer: waiting on a signed change order, waiting on their funding draw, sent to somebody who left, missing the reference their system requires.

And a contact trail with dates, so that whoever picks the account up next can continue rather than restart. The trail is what stops the same conversation happening three times with three different people, which is how a customer learns to ignore the follow-up.

Silence is not a position

The instinct with a slow invoice is to send it again. That treats non-payment as forgetfulness, and forgetfulness is the least common cause of an invoice sitting still. Far more often the payer is entirely willing and something is in the way — something the roofing company has no visibility of and the payer has not thought to mention because, from their side, it is obvious.

Roofing has a particular version of this because so much of the work arrives through intermediaries. A general contractor may be waiting on their own draw. A property manager may need an approval from an owner who is travelling. An insurance-funded job may be waiting on a document that nobody told the roofer was part of the file. In every case the invoice looks identical from the outside: sent, unpaid, quiet.

The work, then, is diagnostic rather than persistent. Sending the same reminder more often does not surface a missing purchase order number. One specific question to the person who actually processes payments does, and it usually does so immediately, because the answer costs them nothing to give.

That is why the deliverable is a named reason per invoice. Once the reason exists, the account is either a task somebody can complete or a genuine disagreement — and knowing which is nearly the whole of the problem.

What receivables produces, and what holds each piece up A horizontal spine carries three labelled artifacts produced by receivables: an accurate ageing, a named blocker per invoice, and a dated follow-up trail. Beneath each artifact a vertical line drops to a second tier naming what holds it up — respectively invoices dated from the work, not from the entry, somebody asked the customer what it is waiting on, and every contact recorded where the next person can see it. Across the foot of the diagram a separate band states the judgement this function does not make, which is whether to write an account off or press it further. The diagram shows structure only and contains no figures. What this desk produces An accurate ageing A named blocker perinvoice A dated follow-uptrail invoices dated from thework, not from the entry somebody asked thecustomer what it iswaiting on every contact recordedwhere the next person cansee it Every item above sits on the one below it. Outside this desk Whether to write an account off or press it further
Each artifact on the spine has something underneath holding it up. That is the whole design: receivables is not an argument, it is a set of items that can each be traced to how they were arrived at, so that a slow invoice is a question with an answer rather than a mood. The band across the bottom is the part that stays outside the work.

Sometimes payment is an exchange, not a transfer

One blocker recurs often enough in construction to be worth naming specifically: payment conditioned on a document going the other way. In that arrangement the money is not withheld — it is waiting for an exchange that nobody has set up.

California legislates the shape of that exchange, and its treatment is useful as a worked example of the class rather than as a statement of national law. California Civil Code section 8132 — Conditional waiver on progress payment provides that where a claimant is required to execute a waiver and release in exchange for a progress payment and is not in fact paid, the waiver “shall be null, void, and unenforceable unless it is in substantially the following form” — and then prints the form. The statute also carves out rights based on work done under a written change order that has not been fully executed.

Two practical things follow, and both are documentation rather than legal questions. A payment expected in exchange for a document is blocked until the document is prepared correctly, so preparing it early removes the block. And a change order that was agreed verbally sits outside whatever was released, which is a very common reason a roofing company is owed money it cannot point to. Other states handle this differently.

This describes one state’s statute to illustrate a pattern. It is not legal advice, it makes no determination about your contracts, your rights or any account, and the rules differ materially by state. Those questions belong with your own counsel; the department page below sets out where this work stops.

The desks either side of this one

Receivables sits inside Finance and Bookkeeping, which carries the boundary for the department as a whole.

What owners ask about money owed

Most of our slow payers are not refusing. What is going on?

Something is missing and nobody has said what. That is the ordinary case rather than the exception — a purchase order number the invoice does not carry, a document the payer needs before releasing funds, a change order signed by somebody without authority to sign it, an invoice sitting in an inbox belonging to a person who left. None of those look like a dispute from either side. They look like silence.

How do you find the blocker?

By asking a specific question of a specific person, which is a different act from sending a reminder. A reminder restates a number the payer already has. The useful question is what has to happen for this to be released, addressed to whoever actually processes it, and it usually gets a direct answer because it is easy to answer.

Will you chase our customers? Some are relationships we protect.

The contact is factual and unembarrassing, and that is deliberate — most of what makes chasing awkward is that it implies an accusation. Asking what a payment is waiting on implies nothing. Where an account genuinely needs the owner rather than a desk, it gets flagged for you instead, and which accounts those are is a rule you set at the start.

Our ageing report is not trustworthy. Does that matter?

It is the first thing to fix, because everything downstream is triage and triage against wrong dates prioritises the wrong accounts. The usual causes are invoices dated when they were entered rather than when the work finished, credits never applied, and jobs invoiced in parts with no single view. That cleanup has an end, and after it the report is a tool rather than a document.

Do you decide when to escalate?

No. We surface what is stuck, what it is stuck on, and what has been tried, and the decision about what to do with an account stays with you. Where an account has moved beyond a documentation question, the sibling desk on notices and collections is the one that carries it.

Commercial and residential behave differently. Do you handle both?

Yes, and they need different questions. A homeowner who has not paid usually has a reason they will state plainly if asked. A general contractor who has not paid is often waiting on their own funding, or on a document the roofing company did not know was required. Treating those two with the same follow-up produces a polite reminder that helps neither.

The statute quoted above

Pick your oldest invoice and ask why

If nobody in the company can name what it is waiting on, that is the finding — and it is usually true of more than one account.