Commission Report February 2026

This is the most important concept in the model. Every transaction has three components:

The source data provides realPrice, which is the total amount the customer actually pays. This includes fees but already reflects the discount:

Since commission should be on ticket revenue after the discount (what the customer pays for the actual seats):

Example 1: Payment Plan Customer

Payment plan: $1,660 over 7 installments. Monthly commissionable revenue:

Fees ($60) also split across installments but are not factored into commission. Each month’s commissionable amount is the same.

Example 2: One-Time Payment

No payment plan — the full $310 is counted if the transaction falls within the commission period.

Non-Payment-Plan Sales (315 of 382 transactions)

The full Commission Base is counted if the completedAt date falls within the selected period. If completedAt is missing, createdAt is used as a fallback.

Payment Plan Sales (65 customers, ~391 active installments)

The Commission Base (real price minus fees) is divided evenly across the number of payment plan months. Each month with a due date in the period gets that equal share:

Fees also split across installments but are not factored into commission calculations.

Canceled installments are excluded entirely.

Example: If a customer has a $1,600 commission base on a 7-month plan (Feb–Aug), each month gets $228.57 in commissionable revenue. If the period is February only, only $228.57 counts toward that month’s commission.

Payment plan total matches Real Price in 64 of 66 matchable cases. The 2 mismatches are customers with multiple season ticket transactions — the model uses the best-matching transaction.

Installment Timing Note

Not all plans start in February. 50 of 65 plans have their first installment due in February; the remaining 15 start in March. This is why the monthly installment chart shows February as the lowest month — peak payment plan cash flow is March through May.

Deposit + Season Ticket Overlap

3 payment plan customers also have separate deposit transactions. The deposit appears as its own line item with its own paid amount. The season ticket transaction shows a discount equal to the deposit. Both are included — no double-counting occurs because the season ticket’s Real Price already reflects the deposit credit.

Reps are identified from a name field in the source data. 231 of 382 transactions are assigned to one of four reps:

What’s in Unassigned?

54 — online direct purchases, deposit-only orders (no shop)

43 — CESA Tickets (community partner sales channel)

40 — generic “Season Ticket” shop (likely online self-service renewals)

14 — Stacey transactions (sponsorship accounts, separate from sales team)

Unassigned transactions appear in the data tabs for transparency but are excluded from rep commission totals.

New vs Renewal Classification

Determined by the STM Status field in the source data. Every transaction row has either “New” or “Renew.” This field is used as-is; no interpretation or guessing was applied.

Name Mismatches (4 customers)

Some customers have slightly different names across sheets (e.g., “Joey Hall” vs “Joseph Hall”). These are the same customers; linking is done by customer ID, not name.

Non-Standard Payment Statuses (13 transactions)

Some transactions show LOCAL-PENDING, LOCAL-RECEIVED, or POS-RECEIVED instead of RECEIVED. These are treated the same as completed sales.

Canceled Installments (14 excluded)

All belong to voided payment plans. Filtered out at build time and do not appear in the Payment Schedules tab.

Out-of-Period Transactions (160 rows)

160 rows have March dates. The date-filtering formulas correctly return $0 for these; they are in Raw Data for completeness but do not affect February commission calculations.

Primary source: February Report.xlsx (3 sheets)

Feb Buyers.xlsx and Feb Purchases.xlsx were reviewed but not used — they contain redundant data already captured in the February Report.

The Commission Model spreadsheet has 6 tabs. All values are formula-driven — nothing is hardcoded.