Sales Teams & Commissions

A door-to-door sales force is a small company rebuilt every year. Reps are recruited over the winter, onboarded in a few weeks of spring, housed for the summer in markets far from home, organized into teams under leaders who are often reps themselves from last year, paid mostly on commission, and sent home in the fall. The software that runs it is part HR system, part payroll feed, part property manager and part org chart, and it's tightly coupled to sales data, because almost everything a rep earns depends on what happens to agreements after they sign them. This chapter covers the structure, the people pipeline and the money.

The Sales Organization#

The org chart is a tree, and it matters more than in most businesses because visibility and pay both follow it:

Level	Typically	Sees
Regional / divisional	Leaders over many markets	Everything below them
Senior team leader	Runs several teams	Their teams and recruits
Team leader	Runs one team, often still selling	Their team
Recruiter	Brings in reps (often a team leader too)	The recruits they brought
Rep	Sells	Themselves

Two attributes ride alongside the position. Rank (rookie, veteran, and leadership ranks) reflects experience and changes pay terms. Position on a team (leader, captain, a licensing coordinator who chases permits) is a role within one team for one season. Keep them separate from the position in the tree: a veteran rep can be a captain this summer and a team leader next summer, and the history of each needs to survive.

Downline visibility is the core access rule: a leader sees the people below them in the tree, and not their peers' people. Implement it as attribute-based access over the tree, layered on top of ordinary permissions (see Authorization). A request passes the route's permission check first, then any one of a small set of rules:

• Global admin: sales operations or onboarding staff, everything.
• Organization admin: an admin for a dealer (below), their organization.
• Downline manager: anyone above the subject in the tree.
• Self.

Store the tree as an adjacency list with a materialized path or closure table so "is A above B" is one indexed lookup, because it's evaluated on nearly every request.

Seasons and Rosters#

Teams exist per season. A team has a leader, a size, a color on the map, and a boundary on the map (see Door-to-Door Sales). A roster slot puts a rep on a team for a sub-season, so a rep can move from one team to another in July without rewriting where they were in June. Every slot change is recorded in an assignment history, because commissions, overrides and disputes all ask "who was this rep's leader on the day of this sale?"

Rosters also drive other systems: putting a rep on a team publishes an event carrying the jurisdictions that team's boundary intersects, which tells Licenses & Permits which permits that rep now needs.

Dealers and Partnerships#

Some companies sell through their own reps only. Many sell partly or entirely through dealers: independent sales organizations or partnerships that recruit, house and manage their own reps under the company's brand and contracts, in exchange for a share of each sale. The platform then has two kinds of tenant inside the sales organization:

• Dealer admins see and manage only their dealer's reps, teams and housing.
• Dealer reps sell the company's plans on the company's paper, with credit flowing to the dealer as well as the rep.
• Commissions split between the company's pay to the dealer and the dealer's pay to its reps, and the company may only compute the first.

Model the dealer as a scope on people, teams and money from the start (Multi-Tenancy covers the general pattern). Retrofitting it into an org chart that assumed one employer is painful.

Recruiting#

Recruiting runs from fall to spring and is its own funnel. A recruit record follows a person from first contact to the end of the season:

• Pipeline status: prospect, coming (committed for the season), arrived, knocking, finished; or not coming, quit, terminated. Returning reps carry over as prior-year reps and are re-recruited, often by their old leader.
• Recruiter and source: who recruited them (recruiting credit is often paid) and how they heard (campus, social media, referral, someone knocking on their door).
• Experience and rank: rookie, second-year, veteran.
• Logistics: expected arrival, the dates they plan to knock, whether they're bringing a car, housing needs.

Some companies recruit seasonal service technicians the same way, to cover the summer peak of service work. Same pipeline, different onboarding and different pay.

A recruit record collects some of the most sensitive data the business holds: Social Security numbers, driver's license and passport images, birth dates, bank details for direct deposit, and for some solicitor permits, physical descriptions and criminal history disclosures. Collect each field only for the purpose that needs it, encrypt it, restrict who can see it (a team leader needs a rep's phone number, not their SSN), and delete it on a schedule (see Data Retention). Uploaded documents go through an approval step (approved, or declined with a reason like "blurry" or "missing information") before they count.

Onboarding#

A recruit becomes a rep when onboarding is complete, and "complete" should be computed from requirements, not ticked by hand:

• Identity and work authorization. Employees complete Section 1 of Form I-9 no later than their first day of work for pay, and the employer completes Section 2 within three business days of that start, after examining the employee's documents. Employers enrolled in E-Verify then create a case from the I-9 no later than the third business day after the employee starts work for pay, and E-Verify participants may use a DHS-authorized alternative procedure to examine documents remotely. For a seasonal workforce arriving from all over the country, that remote option and an I-9 vendor integrated by webhook save weeks of chasing.
• Tax forms. A W-4 for employees, or a W-9 for contractors (see the next section for which).
• Background checks. Ordered through a consumer reporting agency, which brings the Fair Credit Reporting Act: a standalone written disclosure (not buried in an application), written authorization, a pre-adverse-action notice with a copy of the report and the FTC's summary of rights before rejecting someone on its basis, and an adverse-action notice after. Model those as steps with timestamps; they're what you produce if a rejected applicant complains.
• Agreements. The season's rep agreement, addenda and acknowledgments, signed electronically. Make them per season: a rep who hasn't signed this season's acknowledgment loses app permissions until they do, which is the simplest way to guarantee nobody sells on last year's terms.
• Profile. Emergency contact, mailing address, arrival date, knocking window, uniform size (yes, really: the uniforms are ordered in bulk before arrival).
• Permits. Solicitor permits and any sales licenses for the markets their team works, from Licenses & Permits.

Record completion per season, with the evidence behind each requirement, and push the result to whatever system pays the rep.

Employee or Contractor#

Door-to-door reps are paid mostly on commission, and many companies engage them as independent contractors rather than employees. That's a legal decision with tax, wage and benefit consequences, made by the business and its lawyers, not the engineering team. But the platform has to represent it, and the rules explain why the data looks the way it does:

• Federal tax. The IRS treats direct sellers as statutory nonemployees (self-employed for federal tax purposes) when substantially all of their pay is related to sales or other output rather than hours worked, and they work under a written contract stating they won't be treated as employees for federal tax purposes.
• Federal wage law. The Fair Labor Standards Act asks a different question: is the worker economically dependent on the business, or in business for themselves? The Department of Labor's guidance weighs six factors: opportunity for profit or loss depending on managerial skill, investments by the worker and the business, permanence of the relationship, the nature and degree of control, whether the work is integral to the business, and skill and initiative. The rule behind that test has changed repeatedly (a 2024 rule, a 2025 enforcement bulletin, a 2026 proposal), so check the current position.
• State law has its own tests, often stricter, and they differ by state.

What the system needs from all that:

• Worker type per person per season, because it decides the forms (W-9 and 1099 or W-4 and W-2), the payroll system (a contractor payment platform or the HR system), and whether hours and overtime are tracked.
• Pay terms in the written agreement that match how pay is actually computed. A contractor agreement that says pay is per sale, paired with a payroll feed that pays a daily minimum, is a classification problem the data created.
• No assumption baked into the schema that every seller is one or the other. Service technicians are almost always employees; seasonal reps may be either; dealers' reps aren't yours at all.

Housing#

A seasonal sales force has to live somewhere for the summer, and many companies arrange it: apartments, houses or extended-stay hotels leased per market, filled with reps by team. It's an operational system of its own:

• Units, with rooms, beds and couches, the complex and its lease, furniture and appliance delivery and pickup, and utilities.
• Assignments of reps to beds per season and sub-season, honoring requests (shared or single, same-gender housing, married couples, a requested roommate). Assignments end automatically when a lease's end date passes.
• A ledger of money: application fees and deposits, rent before, during and after the season, furniture and damage charges, utilities, and charges to reps for their share, deducted from pay where the agreement allows.

Treat housing money like any other money: an append-only ledger with payees, due dates and paid dates, reconciled to what was actually paid (see Payment States & Ledgers). Rent deductions from pay need to appear on the rep's statement as separate lines, and need the rep's written authorization. They're the most disputed lines on it.

Commissions#

A rep's pay is mostly commission, and commission depends on events that happen after the sale. The design has to answer three questions: what's commissionable, how much, and when it becomes final.

What's commissionable. The agreement records both the rep who sold it and the rep who gets credit (different when a set is closed by someone else, or a rep sells under a leader's code). Leaders often earn an override on their downline's sales, attributed by the roster on the sale date.

How much. Common bases, often mixed:

• A percentage of contract value or first-year value.
• A flat amount per sale, tiered by plan or by rank.
• Higher rates for higher ranks, sometimes with part of the commission paid as an up-front amount during the season against which later earnings are reconciled.
• Bonuses for volume, for average price above a target, for serviced sales.

When it's final. This is where most commission systems go wrong. An agreement can be rescinded inside the cancellation window, cancelled before the first service, or cancelled a few months in. A commission paid on signing and never revisited pays reps for sales that never became customers, and rewards exactly the pressure selling the business least wants. The usual controls:

• Earn on service, not on signature. A commission becomes payable when the first service is completed, not when the agreement is signed.
• Clawbacks for agreements cancelled within a defined period after service, deducted from future pay.
• Holdbacks: a share of each commission held until the end of the season (or later) to cover clawbacks after the rep goes home.

A Ledger, Not a Number

Represent commission as an append-only ledger per rep, not a computed field: entries for pending, earned, paid, held, released, voided and clawed back, each linked to the agreement and event that caused it, and each stamped with the version of the commission rules that produced it. A rep's statement is the ledger for a pay period. A dispute ("I sold twelve, you paid me for nine") is answered by listing the entries, and a rule change applies to new sales without silently recomputing old ones.

Compute from events, not from nightly snapshots. The completion of a first service, a cancellation and a rescission each arrive as events and each produce entries. A nightly recomputation from current state can't tell a cancellation before service from one after it if the agreement's history has been overwritten.

Bonuses Paid on Service

Upgrades and upsells sold by technicians or reps (see Pricing & Sales Rules) usually pay a flat bonus by the plans involved, and the same principle applies: pay when the customer has received a service on the new plan within a window after the upgrade, not when the upgrade was entered. Add the obvious conditions explicitly (the employee wasn't terminated before the qualifying service, the upgrade wasn't reversed), and keep the rule definitions versioned. When payroll asks why a bonus was paid, or a lawyer asks why it wasn't, the answer should be a query against the rules in force that day.

Attribution to the HR System

Commissions are paid through payroll or a contractor payment platform, which identifies people by its own worker IDs. Map sales identities to those IDs with effective dates (people are rehired, change employers between dealer and company, and get new IDs), send the ledger's payable entries per pay period, and reconcile what was actually paid back against the ledger. The reconciliation is what catches the bonus that was approved but never paid, and the rep paid twice because they had two IDs.

What This Means for the System You Build#

• An org tree with downline visibility as attribute-based access, plus rank and team position as separate, seasonal attributes.
• Seasons, sub-seasons and roster slots with full assignment history.
• Dealers as a scope on people, teams, housing and money.
• A recruit pipeline with sensitive fields minimized, encrypted, permissioned and deleted on schedule.
• Onboarding completion computed from requirements: I-9 and E-Verify deadlines, tax forms, FCRA steps, season agreements and permits, with evidence.
• Worker type per person per season, driving forms, pay systems and time tracking.
• Housing as units, beds, assignments and a ledger, with deductions itemized and authorized.
• Commission as an append-only ledger driven by sale, service, rescission and cancellation events, with holdbacks, clawbacks and versioned rules.
• Effective-dated mapping to HR and payroll IDs, and reconciliation of what was actually paid.

References#

Specifications

• USCIS: Completing Section 1, Employee Information and Attestation, Section 1 completed no later than the first day of employment
• USCIS: Completing Section 2, Employer Review and Attestation, Section 2 within three business days of hire, and the alternative remote procedure for E-Verify employers
• E-Verify: Create a Case, cases created after Form I-9 and no later than the third business day after the employee starts work for pay
• IRS: Statutory Nonemployees, direct sellers treated as self-employed when pay relates to sales and a written contract says so

Reference

• U.S. Department of Labor: Fact Sheet 13, Employee or Independent Contractor Classification Under the FLSA, the six economic reality factors and the status of the 2024 rule
• U.S. Department of Labor: Independent Contractor Rulemaking, the 2024 final rule and the February 2026 proposal
• FTC: Using Consumer Reports, What Employers Need to Know, standalone disclosure, authorization, and pre-adverse and adverse action notices