Sales Commission After Termination: Renewals, Reorders, and Account Credit

A founder hiring a wholesale representative discovered that the agreement promised commission on every account the representative developed for as long as that account kept ordering. That framing—renewals, reorders, and line extensions after the representative leaves—is the practical sales commission after termination question that turns up when the next invoice arrives. The example comes from a public founder discussion, not a rule for other businesses. Read the source discussion.

There is no universal answer. The agreement and applicable law determine whether an obligation survives termination. But the decision should not wait until a former representative asks to be paid: define the qualifying accounts and revenue, record the evidence, and make the operating configuration match the adopted rule.

Not legal advice: This guide is operational guidance, not legal advice. Commission obligations depend on the agreement and applicable law; have qualified counsel review the rule you adopt.

Start by classifying the revenue

A departure date is one fact in a commission decision, not the decision itself. The first question is what kind of revenue is in front of you. A commission that was already earned before termination may be unpaid because the normal payment cycle has not run. A deal that was only being pursued may be pending. A transaction may close after termination because of work completed beforehand. Or an established customer may place a later renewal, reorder, or line-extension order. Those states can carry different contractual outcomes.

Revenue state	Decision to make	Record that supports it
Earned but unpaid	Did the earning event occur before termination?	Transaction, earning rule, calculation
Pending at termination	What event changes it from pending to earned or payable?	Source activity, stage history, agreement
Closed after termination	Does qualifying pre-termination work receive credit at a later close?	Origination record, close record, account rule
Later renewal, reorder, or line extension	Does continuing developed-account credit cover this order?	Account attribution, eligibility dates, agreement version

This distinction prevents two common errors. First, do not call an earned-but-unpaid amount a tail claim merely because payment occurs later. If the agreement says commission is earned at close and the sale closed before termination, calculate it under the normal earned-commission rule. Second, do not assume that a pending opportunity or a later reorder has the same treatment. A policy may grant credit for one, both, or neither.

For example, suppose a representative closes a $12,000 order on June 20 and their contract ends June 30. The agreement says commission is earned at close and paid the following month at an operator-chosen 10% rate. The commission is $1,200: $12,000 × 10%. It is earned but unpaid, so the later payment date does not convert it into a post-termination renewal obligation.

A later-close rule needs its own trigger. One business may define a protected opportunity as a named account with documented pre-termination work and a close within a stated period; another may require a signed order before any commission is earned. Put the trigger in the agreement. A sales stage label alone is usually too vague to resolve an argument.

Define the developed account before the duration

The hardest question is often not how long credit lasts, but which customer earned it. A developed account should be a defined status created by a stated qualifying event and supported by evidence. Depending on the program, that event might be an accepted introduction, a written named-account assignment, a first order, or another specifically documented milestone. The definition should name the evidence that proves it: an assignment record, accepted lead, meeting record, opportunity history, first transaction, or a combination.

Set defaults for the cases that otherwise become manager-by-manager exceptions. An account already in the pipeline before the representative’s qualifying event should default to a house account unless a written assignment expressly grants credit. The reason is simple: a pipeline record demonstrates that the business was already pursuing the relationship, so later participation should not silently create account-origin credit.

If another seller expands a developed account, treat the expansion as a line extension by default when it is for the same legal customer or buying group and falls within the agreement’s product or account scope. That preserves a clear continuing-credit rule for revenue from the relationship the representative developed. Treat it as a new opportunity only when the agreement identifies a materially separate customer, buying entity, product line, or opportunity that was independently originated. The point is not to reward every future sale; it is to avoid relitigating the account boundary after each expansion.

Reassignment should change who works the account, not erase its history. The default is to preserve the former representative’s developed-account status and eligibility window, while recording the effective date and scope of the new assignment. The new seller receives credit only under the rule for new opportunities or shared credit; the former representative’s approved tail, if any, continues only to its stated end. For wholesale or channel relationships, the Channel Partner Program recipe is a separate configuration pattern; this guide addresses the policy decision that comes first.

Make the clause usable on an invoice

If an operator cannot fill in the fields below for a specific invoice, the clause is not yet administrable. Each field answers a different dispute question.

Qualifying event and developed-account definition. State the event that creates credit and the account boundary. A workable value is: “Credit begins when a named prospect accepts the representative’s introduction and the company records the account assignment.” That is more usable than “accounts developed by the representative,” because it identifies both the action and the record.

Attribution evidence and duration. Name the proof and the start and end of eligibility. For example, retain the accepted introduction and assignment date, then state whether eligibility ends at termination, at a stated date, or under an account-specific schedule. Duration is an agreement choice, not a market norm.

Rate and commission base. A rate is incomplete without the amount to which it applies. “8% of net collected revenue” is workable only if the agreement defines net collected revenue—for example, whether it excludes taxes, shipping, refunds, credits, or uncollected invoices. “8% of sales” invites different calculations from finance and sales.

Exclusions and adjustments. Say what happens after an otherwise eligible order changes. A workable adjustment rule identifies the events that reduce or reverse commission, such as returns, refunds, credit notes, cancellations, or nonpayment, and states whether the change reduces a future payment, creates a clawback, or requires case-by-case approval. Do not leave a broad “subject to adjustment” phrase without a mechanism.

Effective date, approval, disputes, and agreement version. Record when the rule began, who approves exceptions, how a representative raises a dispute, and which signed agreement or amendment governs the account. Agreement version matters because an account may have been developed under an earlier rule. Attach or link that version to the account record rather than asking a later reviewer to infer the answer from email and memory.

Choose a tail shape deliberately

A tail commission is continuing eligibility for commission after a representative’s contract ends. It is a policy term, not a universal right, recommended duration, or legal conclusion. The agreement and applicable law determine whether a tail exists and what it covers.

One model provides no continuing credit: eligibility ends at the defined earning event or termination date. It is easiest to administer, but it may not fit a business that wants to reward a representative for opening accounts with long buying cycles. A fixed-term tail applies the stated rate to qualifying developed-account revenue until a visible end date. This model works only when the account definition and start date are recorded.

A declining-rate tail changes the commission rate at defined points while retaining the same account boundary. For example, if an operator chooses a 10% rate for an eligible renewal of $20,000, the commission is $2,000. If the agreement instead specifies a 5% rate after a stated milestone, the same $20,000 renewal produces $1,000. Those figures are worked examples, not suggested rates. Different first-sale and renewal structures can also be expressed in a program; see Running a Subscription Affiliate Program.

Account-specific eligibility is a fourth option. It can suit strategic accounts, negotiated exceptions, or acquisitions, but it requires a named account list, effective dates, and an owner who keeps the list current. Without those controls, an exception becomes an unbounded claim.

A wholesale reorder illustrates why the model must be explicit. Assume a representative qualified a retailer under the agreement, the account remains eligible, and the retailer submits a $15,000 reorder after termination. At an operator-chosen 7% rate on the defined commission base, the calculation is $1,050: $15,000 × 7%. If the agreement excludes that reorder because the eligibility window ended, the calculation is $0. The invoice amount does not decide the result; the account classification, agreement version, window, rate, and base do.

Keep the system aligned with the rule

The operating record should connect the account to the source event, governing agreement version, calculation, approval, adjustment, and payout. That chain gives sales, finance, and the former representative the same place to test a claim. It also distinguishes a disputed policy decision from a simple arithmetic or data-entry error.

Siren can support the administration after the business sets the rule. When a partner is bound directly to a customer account under a revenue-share program, every order from that customer—including renewals—can produce commission without a tracking link or coupon. The Business Partner Revenue Share recipe owns the configuration for that account-bound model.

Siren can calculate a commission as a set percentage of a referred sale’s transaction value and record it as a draft obligation. That draft state creates a review point before payout, which is useful when the operator must compare a post-termination transaction with the governing agreement and account evidence. The attribution pipeline explains how renewal activity traces through the original relationship and downstream records.

Stopping future accrual is an operator action, not an automatic consequence of a contract ending. Review the running commission configuration and account attribution against the agreement’s end rule, then make the appropriate operational change. This guide does not prescribe a specific status change or UI step, because the correct action depends on the adopted policy and the account’s recorded eligibility.

Prevent overlapping credit

Duplicate credit usually appears when ownership changes: a house account is later claimed as developed, a new seller inherits an account that still has continuing eligibility, or an internal seller and a partner both appear connected to the same revenue. Use one source of truth for account eligibility, effective dates, approved exceptions, and the agreement version. Preserve old attribution and its end decision instead of overwriting it at reassignment.

Before approving an obligation, compare the order against every active or surviving claim to the account. If two claims overlap, route the decision to a named owner before payout. The owner should record whether the revenue is excluded, shared under a stated formula, or assigned to one claimant under the agreement. For the broader framework of qualifying events and duplicate-payment controls, read How to Structure Multi-Tier Partner Commissions.

Review accounts before the next order

Use this review when a representative leaves or when an account’s treatment changes:

• Identify the qualifying event, evidence, and developed-account classification.
• Attach the governing agreement version and record the eligibility start and end.
• State how pending deals, later closes, renewals, reorders, and line extensions are treated.
• Confirm the commission base, rate, exclusions, adjustment or clawback method, and approval owner.
• Preserve reassignment history and resolve overlapping claims before an obligation is approved.
• Give the representative a defined dispute route and retain the decision with the payout record.

The result should be more than a clause: it should be a record that produces the same answer when reviewed by sales, finance, and the former representative. To see an account-bound ongoing-commission configuration, read the Business Partner Revenue Share recipe. You can also explore Best Partner Commission Payout Software for adjacent payout-tool evaluation.