Give Every Recurring Commission Review a Backup Owner
Recurring revenue should not stop being reviewable because one person is sick, traveling, overloaded, or gone.
The spreadsheet is rarely the whole dependency
Ask who reviews commission statements and most small advisory firms can name the person immediately. That sounds like ownership. Sometimes it is just dependency.
One person knows where each supplier posts statements, which files need to be downloaded, how account names map to clients, which expected payments deserve attention, who can explain an adjustment, and when an old variance has become an escalation. The process may look documented because a spreadsheet exists. Then that person takes a week off and nobody can run the review with confidence.
A backup owner is not a name in a policy. It is somebody who has the access, context, authority, and recent practice needed to complete the next review without rebuilding the process from inbox history.
Do not assign backup coverage to every administrative task. Start with the reviews that can hide lost revenue, delay advisor payments, distort a forecast, or weaken a supplier dispute.
Decide which reviews need backup coverage
List every recurring commission review by supplier, distributor, or payment source. For each one, record the review frequency, typical statement date, expected completion date, revenue covered, current owner, open exceptions, required systems, and next escalation point.
Then apply a simple loss test: if the primary owner disappeared before the next statement arrived, what would the firm fail to detect, explain, collect, pay, or report?
A review deserves backup coverage when a delay could affect meaningful recurring revenue, when the statement format or matching logic needs specialized knowledge, when access sits with one person, or when unresolved exceptions already require active follow-up. A small, stable statement with clean records may need lighter coverage. A large supplier with recurring adjustments and several open disputes needs more.
Use the risk to set the depth of coverage. Do not make every review equally heavy just to say the process is standardized.
Separate the primary owner, backup owner, and approver
The primary owner runs the normal review. The backup can run it when needed and should periodically prove that ability. The approver handles decisions outside normal authority, such as accepting a material write-off, changing a compensation treatment, or closing an unresolved variance.
Those roles should not quietly collapse into one person.
A backup does not need permission to see everything forever. Give the person the access required for the assigned review and preserve the approval boundaries that protect revenue decisions. NIST's current security and privacy control catalog separates account management, approved access, separation of duties, contingency planning, training, and testing. It is written for information systems, not advisor commission operations, but the operating lesson transfers: continuity and control have to be designed together.
If the backup can download a statement but cannot see the related deal, commission expectation, contract, or prior exception, the firm has created partial access rather than usable coverage. If the backup can also change payment rules and approve the result without review, the firm may have removed too many boundaries.
Build a continuation packet, not a giant manual
The backup needs the shortest set of current records that makes the next review possible. Keep the packet connected to the operating system rather than buried in a document nobody updates.
For each covered review, include:
- Supplier, statement source, normal arrival window, and review deadline
- Primary owner, backup owner, approver, and supplier escalation contacts
- Current access method and who administers that access
- Expected commission records, approved splits, and controlling commercial evidence
- Import, matching, and reconciliation steps
- Open variances, aging, next actions, due dates, and case numbers
- Materiality or approval rules that tell the backup when to stop
- Closure evidence and the report used to confirm the review is complete
Do not copy passwords into the packet. Record the approved access path and the person responsible for granting or restoring access.
Keep the continuation packet close to the existing commission reconciliation record. The mechanics of expected payment, statement data, variance type, evidence, owner, and resolution should remain one process. Continuity adds role coverage and takeover evidence. It should not create a second version of the numbers.
Test access before you test knowledge
Many backup plans fail at login.
Confirm that the backup can reach the supplier portal, shared mailbox, statement folder, CRM records, commission history, contract evidence, task queue, and reporting view needed for the review. Check whether multifactor authentication, device approval, licensing, or a supplier-specific administrator blocks access.
Do this while the primary owner is available. An access problem found during a planned test is annoying. The same problem found on statement day while the primary owner is unavailable can stop the review.
Also check that the backup can find the right records without using the primary owner's private bookmarks or saved local files. If the process works only from one laptop, it is not covered.
Require a real acceptance test
Sending the backup a process document does not prove readiness. Have the person run a controlled review.
Start with a shadow review. The backup independently locates the statement, matches a sample, identifies current exceptions, and explains which items can close and which require action. Compare the result with the primary owner's work.
Then schedule a takeover review. The backup runs the normal process for one statement period while the primary owner observes but does not lead. The test should prove that the backup can:
- Locate the complete statement and confirm the period
- Connect payments to the correct clients, deals, services, and expectations
- Classify unmatched or changed items without forcing a clean answer
- Create follow-up with an owner and date
- Escalate decisions outside assigned authority
- Produce the normal completion evidence and revenue report
NIST's contingency planning guide makes testing and training part of maintaining a workable plan. Your commission process does not need a federal continuity program. It does need more than an untested backup name.
Protect the open exceptions during a handoff
The monthly review is only half the work. Old variances, supplier cases, missing evidence, chargebacks, and payment corrections continue between statement dates.
When coverage changes, review every open exception with the primary and backup. Confirm the amount, issue type, latest supplier response, internal evidence, current owner, next action, due date, escalation threshold, and decision authority. The backup should accept the queue, not merely receive it.
Connect those items to the firm's follow-up system and bring stuck or material exceptions into the weekly operating review. A clean handoff should make the next action visible without requiring a separate meeting to explain every email.
Review continuity when the business changes
Backup coverage goes stale when suppliers change portals, statement formats, contacts, payment schedules, or program rules. It also breaks when your own team changes roles or adds new commission arrangements.
Review coverage after a staffing change, access change, new supplier relationship, major acquisition, compensation-policy update, or failed test. Recheck the highest-value reviews on a regular schedule even when nothing obvious changes.
Track a few honest measures: reviews without an accepted backup, failed access checks, overdue reviews, exceptions with no next action, and the date of the last successful takeover. Do not score the process by how many documents exist.
Start with one supplier this month
Choose the supplier statement that covers the most recurring revenue or creates the most investigation work. Name the primary, backup, and approver. Confirm access. Build the continuation packet from current records. Have the backup run the next review.
You will find the real gaps quickly. Maybe the expected commissions are incomplete. Maybe supplier access belongs to one email address. Maybe open disputes live in the primary owner's inbox. Fix those problems in the working process before expanding coverage.
Advisor OS CRM connects deals, suppliers, commission tracking, revenue attribution, activity, tasks, and reporting. Use the free Advisor OS agency scorecard if recurring revenue still depends on private spreadsheets and one person's memory.