Summer sales back end pay is the largest single bill most D2D programs pay all year, and it lands after the doors stop. Reps sell from May to August. The back end check goes out in the fall or early winter. By then the knocking has stopped, new revenue has slowed, and the money that came in over the summer has often been spent on housing, payroll and next year's recruiting.
The companies that get hurt by it aren't usually short on sales. They're short on a system that tracks what's owed, account by account, from the day each one sells.
What summer sales back end pay is
Most summer programs split a rep's pay in two. A smaller amount pays out during the season. The rest is held and paid later, once the accounts have had time to prove they'll stick. The Deseret News described the pattern in a 2021 look at Utah summer sales: a payment at the close, typically around $50, and "backend checks" in the late fall or early winter. If customers cancel before those checks go out, that part of the pay never comes.
The structure makes sense. It ties pay to accounts that last, and it keeps reps through the final week. But it creates two problems an owner has to solve:
- A liability that grows every day of summer and comes due all at once.
- A promise reps are counting on, with the details often living in someone's head or a spreadsheet.
Reps know it, too. Snow College's career office tells students to ask recruiters, before they sign, whether they'll still get a back end check if they leave mid-summer. If your answer isn't written down, it isn't an answer.
Reserve it like a tax
PestPac's recap of a door-to-door webinar says reserving 20 to 25% of summer revenue for fall payouts can blindside operators who don't plan for it. That's a vendor figure from a panel, not a benchmark, and your number depends on your comp plan. The advice that comes with it is the part to copy: treat the reserve like a tax, set it aside right away, keep it in a separate account, and don't touch it until reps are paid.
We'd go one step further and stop estimating. Your back end isn't a percentage of revenue. It's a sum of specific accounts, each with a known amount owed. So build it that way.
An example reserve model
Every number below is an example, not a benchmark. Swap in your own.
| Line | Example |
|---|---|
| Accounts sold this summer | 1,000 |
| Back end per account still active at payout | $90 |
| Gross back end if every account sticks | $90,000 |
| Accounts cancelled or charged back so far | 140 |
| Back end owed today | 860 x $90 = $77,400 |
| Overrides owed to managers on those accounts | 860 x $15 = $12,900 |
| Reserve the account should hold today | $90,300 |
The point isn't the formula. It's that the last line is knowable every Friday from May to payout, and the transfer into the reserve account happens that day. When an account cancels, its back end comes off the liability and can come out of the reserve. When the payout date arrives, the money is already there.
Decide what releases the hold, in April
The back end is held until something happens. Decide what that something is before the first rep sells under it, because everything downstream depends on it. Common triggers:
- First service completed or install finished.
- A number of days active after signing.
- A number of payments collected from the customer.
- The rep finishing the season through a set date.
Rework's summer program guide puts the chargeback window on the list of rules to settle in April, along with a season-completion bonus reps are reminded of near the end. We agree, and we'd add: every trigger has to be something your system can see. "Account in good standing" is a feeling. "Second payment received" is a field.
There are two ways to run it. You can hold pay until the trigger fires, or pay early and claw it back when an account fails. Commission software vendor CaptivateIQ describes hold and release as releasing commission as the customer pays, which avoids clawing it back later, at the cost of reps waiting longer for cash. Most summer programs use a mix: a small payment up front, the rest held. Whatever you choose, write it down and make the system enforce it.
Chargebacks without the fall fight
Chargebacks are where back end pay turns into arguments. A rep remembers 120 accounts. The office says 96 qualify. Nobody can show the list.
The fix is the same one we wrote about in Pre-service cancellations in D2D pest control: put commission status on every account in the CRM, next to the account.
- One status per account: pending, earned, held, paid, charged back.
- The trigger flips it. A completed first service or a posted payment moves the status, not a person editing a sheet.
- A reason on every chargeback, picked from a short fixed list.
- A weekly statement for every rep, account by account, from June on.
A rep who has seen a statement every week since June doesn't get surprised in November. And an owner who can open any account and show why it paid or didn't has ended most disputes before they start.
Pay it through the system, not a spreadsheet
If your reps are W-2 employees, the back end check is wages. It runs through payroll, with withholding. The IRS rate on supplemental wages remains 22% for 2026, so a rep expecting the full gross amount on a lump-sum check can be surprised by what lands. Ask your payroll provider how the check will be withheld, and tell reps before payout day. A check that goes out in January also falls in the next tax year, for you and for them.
More D2D reps are moving onto payroll. In Utah, residential solar retailers now have to employ their sales reps, setters included, as W-2 employees, which we covered in Utah's solar retailer law. Some states also regulate the plan itself. California, for example, requires that commission agreements for work in the state be in writing and state how commissions are computed and paid, with a signed copy to the employee.
State law can also decide when pay is due after a rep leaves, and what you can hold back or deduct. We're operators, not lawyers. Have counsel review your comp plan, your holdback terms and your chargeback rules in every state you sell in, before reps sign.
Where this sits in the five systems
Back end pay touches three of the five systems we build. Sell owns the comp plan and the record of every account. Deliver owns the event that releases the hold: the first service or the install. Measure owns the weekly liability, the reserve transfer and the rep statements. When they're connected, the fall payout is a report. When they aren't, it's a project. That connective work is most of what we do in the build phase.
Fund it every Friday
The fall payout doesn't have to be the hardest month of the year. Write the triggers in April. Put a commission status on every account. Move the reserve every Friday. Send every rep a statement every week. Do that, and November becomes the month you pay your best reps what they earned, on time, with cash that was waiting for them, and sign them for next summer before anyone else can.