Card Payments for Roofers: Processing Percentages, Deposits, and Who Absorbs the Fee

Of all the usage fees that sit outside a roofing CRM subscription, payment processing is the one that grows with success: it is a percentage of money collected, so your best collections month is automatically your most expensive one. Our roofing CRM add-on audit raises it as three audit questions — what the real rate is, whether the CRM forces its own payment rail, and what your written policy on the fee is — but a policy is not a paragraph in an audit. It is a set of decisions about deposits, progress payments, and the final balance that belong in your estimate terms, settled before the first invoice goes out. This post works through those decisions: the math of the percentage on roofing-sized tickets, a deposit structure worth stating in writing, and the absorb-vs-state-it choice, made once, on paper, instead of argued about at the kitchen table when the final balance comes due.

The percentage math on roofing-sized tickets

Processing is normally quoted as a percentage of each transaction plus a small per-transaction charge. On small retail tickets the per-transaction part matters; on roofing tickets it is rounding. What decides your cost is the percentage applied to a deposit, a progress payment, and a final balance that are each larger than most businesses' weekly sales. The rate itself varies — by processor, by how the payment is taken, and by card type — so pull your effective rate off your own statements: total processing fees for the month divided by total card volume for the month. That single number, not the advertised starting rate, is the one to plan with. The examples below use a round, clearly illustrative 3% — the same illustrative rate our add-on audit uses — purely to make the arithmetic visible:

• A $1,000 deposit paid by card: an illustrative $30 in processing
• A $15,000 roof collected in full by card across deposit and final balance: an illustrative $450
• A $30,000 month of card collections: an illustrative $900 skimmed before the money reaches your account
• The same month at storm volume — $60,000 collected by card: an illustrative $1,800

Two properties of that math shape every decision after it. First, the fee never arrives as a bill you can review — it is deducted from money arriving, so a company can run a strong collections year and never once see its largest usage fee as a line it approved. Second, it scales with the share of customers who pay by card, not just with revenue: if taking cards gets easier and more homeowners choose them — for the points, for the float, because the invoice link made it one tap — the percentage quietly applies to a bigger slice of every job. Neither property makes cards a bad deal. Deposits that land the same day instead of after a check clears are worth real money to a company scheduling crews and ordering materials. It makes the fee a price to set deliberately, per payment point, rather than a surprise averaged over the year.

Structure the payments before the first invoice: deposit, progress, final

The fee decision cannot be separated from the payment structure, because the structure decides how many times money moves, in what amounts, and against what evidence of progress. Whatever structure you choose, it belongs in the estimate terms the homeowner signs — the document our roofing estimate template treats as the job's contract with itself — not in a habit each salesperson describes differently. A workable structure names three things:

• The deposit: how much, when it is due, and what it secures — commonly collected at signing or before materials are ordered, so the job enters the schedule with money behind it rather than as a promise
• Any progress payment: the trigger that earns it, stated as an event the homeowner can verify — materials delivered, tear-off complete, roof dried in — never as a date alone, so the payment follows visible progress
• The final balance: due on completion, tied to the finished work being walkable and the paperwork — invoice, warranty, completion photos — being in the homeowner's hands, so paying in full never feels like paying on faith

Insurance work bends the same structure around a different payer rhythm: proceeds may arrive in stages, a supplement can change the total mid-job, and the homeowner's own portion is only part of the balance. The discipline does not change — every expected payment, from whichever source, is written against the job with its trigger and its amount, so the office can see at a glance what has actually arrived, what is still owed, and by whom. That visibility is the difference between a balance that is being collected and a balance that is being remembered. Jobs sit in the Invoiced stage until they are paid in full and only then move to Closed, which means a partial payment is a state the whole team can see, not a note in one person's head.

Who absorbs the fee: the three policies, chosen once

Every roofing company has a policy on the processing fee, including the ones that have never discussed it — theirs is "absorb it and find out at year end." The three real options:

• Absorb it: the fee is a cost of getting paid fast, recovered across your pricing generally the way fuel and disposal are. The homeowner sees one price and pays it however they like. Simplest to explain, easiest to run, and the cost is real money on every card-paid job — so absorb it knowingly, with your effective rate in the pricing conversation, not by default.
• State it in the terms: the estimate says, before anyone signs, how card payments are handled — for example that the quoted price assumes payment by check or bank transfer and a card payment carries the processing cost. Stated in advance, it is a term of the deal; raised for the first time on the final invoice, it is an argument. Passing processing costs on is governed by rules that vary — card-network and processor terms and, in some places, state law — so confirm what your processor and your jurisdiction allow before this policy goes in writing.
• Split it by payment point: cards welcome where speed matters most — the deposit that books the job — with the larger final balance steered to check or bank transfer in the terms. This is the structure many companies land on once they see the math: the percentage on a $1,000 deposit is a modest price for a signed, funded job, while the same percentage on a five-figure final balance is where the fee actually bites.

Whichever policy you choose, two failure modes are worse than any of the three. The first is deciding per customer — quoting one homeowner an absorbed fee and surcharging the next because the job felt tight — which is how a company ends up with an unfairness complaint it cannot answer from its own paperwork. The second is hiding the policy until the final balance: a homeowner who learns about a card charge when the roof is already on has no choice left, and knows it. The estimate terms are the one moment the homeowner can still choose — a different payment method, or a different roofer — which is exactly why an honest term stated there protects both sides, and why our guide to "good, better, best" roofing estimates insists every tier of an estimate carry the same payment terms rather than burying differences between options.

What the fee buys, weighed honestly

The case for taking cards at all is cash flow, and it is a strong one. A deposit paid by card at the kitchen table starts the job today; a promised check competes with everything else in the homeowner's week. A final balance paid by card on completion day does not age into the overdue pile, and overdue balances are where small roofing companies quietly finance their customers for free. Weighed against that, the percentage is the price of speed and certainty — worth paying at the payment points where speed changes behaviour, and worth questioning at the points where it does not. That weighing is also why the processing line belongs in the same budget conversation as the rest of the stack: divided by the jobs you actually closed, it is part of what a roofing CRM-era operation costs per signed job, and at the whole-company level it belongs in the totals our roofing software stack audit builds.

A five-step card-payment policy, set in one sitting

• Pull your effective rate from your own processor statements — total fees divided by total card volume for a recent busy month — and write that number, not the advertised rate, into the policy
• Choose the payment structure: deposit amount and trigger, any progress payment and its verifiable event, and the final balance tied to completion and paperwork — and put all three in your standard estimate terms
• Choose the fee policy once — absorb, state it in the terms after confirming what your processor and jurisdiction allow, or split by payment point — and apply it to every customer the same way
• Make sure every payment, partial or full, from homeowner or insurer, is recorded on the job record as it arrives, so owed, paid, and overdue are visible to the whole office and the job only closes when it is paid in full
• Re-run the math at renewal and after any storm season: card share and card volume both move, and a policy set at one volume can be the wrong policy at twice it

GableFlow's place in this is the record, not the rail. Invoices and payment tracking are part of the included product: you create the invoice from the job, record payments as they come in, and see what is owed, paid, and overdue on the record, inside the same six-stage pipeline (Lead → Prospect → Approved → Completed → Invoiced → Closed) as the estimate and the photo report. GableFlow adds no processing percentage of its own — if you take a card payment through a separate processor, that processor's percentage is the processor's, and it would apply with any CRM; what GableFlow does not do is force its own payment rail at its own rate as the price of using its invoicing. The rest of the price is the published one: $40/month flat, every feature included, unlimited seats, no per-seat fees, with a 7-day free trial — and the gaps stated on the same page (no QuickBooks sync, no e-signatures, no text messages, no measurement-taking). See how GableFlow's invoicing and payment features keep the money on the job record, check the flat $40/month pricing, or run the subscription side of the comparison on our roofing CRM cost calculator.