What is the RevOps playbook for commission disputes during outbound SDR on Salesforce when sales on Outreach in 2027?

The two ways to attribute the meeting

Every commission dispute in this motion collapses into one of two attribution models, and the playbook only works if RevOps picks one deliberately instead of letting it emerge by accident. The first model is first-touch attribution: whichever rep — SDR or account executive — generated the first logged, meaningful activity on the record gets credit for the resulting commission, regardless of who closed the deal. The second model is role-based attribution: the SDR is compensated for booking a qualified meeting (a fixed spiff or a percentage tied to meeting-held status), and the closer is compensated separately for the won revenue, so the two commissions never actually compete for the same dollar.

First-touch attribution is common in orgs where SDRs are still building pipeline coverage and leadership wants to reward prospecting hustle over meeting logistics. Its weakness is exactly what causes most disputes on this stack: Outreach logs sequence-level touches (opens, replies, bumps) that Salesforce never fully mirrors unless the sync is configured to write every activity type back as a Task. If a closer works a lead through a personal Outreach sequence that was never mapped to a Salesforce Campaign, RevOps has no clean way to prove who touched the record first, and the dispute becomes a screenshot war.

Role-based attribution avoids that fight entirely because it decouples "who gets the meeting credit" from "who gets the close credit." The SDR's commission is earned the moment a meeting is marked held on the Opportunity, sourced from a specific Outreach sequence recorded in a dedicated Salesforce field. The closer's commission is earned on Closed Won, full stop, with no dependency on who prospected the account. The trade-off is that role-based models require more upfront field architecture — you need SDR_Owner__c, Meeting_Source__c, and a validation rule that blocks Opportunity creation without them populated — but once built, the ambiguity that drives 80% of first-touch disputes disappears because the two commission pools never overlap.

Most mature RevOps teams land on a hybrid: role-based for the steady state, with a first-touch tiebreaker reserved for edge cases like a re-engaged cold lead where both an SDR and a closer independently worked the same contact within the same 30-day window. That hybrid needs to be written down in the commission policy document, not left as tribal knowledge, because the policy itself is what RevOps points to when a dispute escalates past the data audit.

How to decide between them

Choosing between first-touch and role-based attribution — or building the hybrid — comes down to answering three questions in sequence: is the SDR org still in pure pipeline-generation mode, does your Outreach-to-Salesforce sync reliably write sequence names back to the Opportunity, and how frequently do closers run their own outbound sequences outside SDR-sourced pipeline. If the sync is unreliable or closers freelance a lot of outbound, role-based attribution is the only model that survives contact with reality, because first-touch attribution depends entirely on data you cannot guarantee is complete.

Run this decision once per fiscal year, not per dispute — flip-flopping the underlying model mid-quarter is what actually erodes trust, more than any single disputed check. If the decision tree above points to first-touch, RevOps must also commit to the specific field comparison it will use every time: the Salesforce record's CreatedDate against the earliest Outreach ActivityDate on that prospect, with a documented tolerance window (commonly 24 hours) for sync lag. Document the tolerance in the commission policy itself so neither party can argue the threshold after the fact.

Concrete numbers behind each option

The operational cost difference between the two models is measurable, and RevOps should quantify it before recommending one to sales leadership. Teams running pure first-touch attribution without clean field architecture report that roughly 15-25% of monthly commission cycles generate at least one formal dispute, because the model depends on activity data that Outreach and Salesforce were never designed to reconcile automatically. Of those disputes, the majority — practitioners commonly cite figures in the 55-65% range — resolve within an hour once someone actually pulls the timestamp comparison, which tells you the disputes aren't really about the facts; they're about the facts not being visible to both parties in real time.

Role-based attribution, once the required fields (SDR_Owner__c, Meeting_Source__c, Commission_Status__c) are built and validation rules block incomplete records, typically drops the dispute rate into the low single digits — often under 5% of monthly cycles — because the two commission pools stop competing. The upfront engineering cost is real: budget 15-25 hours of Salesforce admin time to build the fields, validation rules, and a refreshing report, plus a comparable amount of Outreach-side sync configuration to make sure sequence names and enrollment dates write back correctly. That cost is paid once; the dispute-rate reduction compounds every commission cycle afterward.

On the escalation side, teams that commit to a hard 5-business-day resolution window report average actual resolution times of 2-3 days once the process has run for a full quarter, because most disputes resolve at the Day 2 data-audit step and never need manager or VP involvement. Teams without a time-boxed workflow — where disputes get handled ad hoc over Slack — routinely stretch resolution to 2-3 weeks, and unresolved disputes older than 30 days correlate strongly with SDR attrition, since reps interpret a stalled commission as the company not taking their comp seriously. A report refresh cadence of every 2 hours during business hours (5-6 refreshes across an 8 AM-6 PM day) is the commonly cited minimum to keep both sides looking at current data rather than a stale nightly snapshot; anything less frequent and disputes accumulate faster than RevOps can close them.

Implementation details and sequencing

Building this playbook is a four-phase rollout, and skipping phases is the single biggest reason these programs fail in production. Phase one — field architecture (week 1): create the custom fields on the Opportunity and Activity objects (SDR_Owner__c, Sales_Rep_Owner__c, Meeting_Source__c, First_SDR_Outreach_Date__c, First_Sales_Rep_Outreach_Date__c, Commission_Status__c as a formula field, and a RevOps-only-editable Dispute_Flag__c checkbox). Write-protect Meeting_Source__c from sales rep edits at the field-level security layer — this single control prevents the most common manipulation, where a closer overwrites the source field during meeting scheduling to claim SDR-sourced credit.

Phase two — sync validation (week 2): audit the Outreach-Salesforce integration mapping to confirm sequence names write back to Meeting_Source__c and that Campaign Member status updates fire before Opportunity creation, not after. This is where most teams find their stale-mapping bug: a sequence renamed in Outreach without updating the corresponding Salesforce Campaign mapping, which silently misattributes every meeting booked through it until someone notices the pattern in a dispute log.

Phase three — the single source of truth report (week 3): build the Salesforce report with row-level fields (Lead/Contact name, SDR name, sales rep name, sequence name, both first-activity dates, meeting source, commission status, dispute flag) plus an aggregation header showing total meetings per SDR, per sales rep, dispute count, and average hours between first SDR and first sales rep activity. Set access so SDRs and sales reps each see their own detail rows plus an anonymized team summary, while RevOps holds full edit rights and leadership gets read-only visibility into everything.

Phase four — the escalation workflow (week 4, then ongoing): stand up the 5-day process — Day 1 dispute submission via Salesforce Case with record ID, evidence, and proposed resolution; Day 2 RevOps data audit against the report; Day 3 manager-to-manager review for anything the data audit didn't resolve outright; Day 4 VP of Revenue Operations final ruling (with a rare 50/50 split reserved for genuinely inconclusive cases); Day 5 logging the root cause in a Commission Dispute Log so a pattern appearing three times in a quarter triggers a system fix rather than another one-off manual resolution.

Sequence these phases strictly — a report built on unvalidated sync data (skipping phase two) just gives both parties a more official-looking version of the same bad data, and an escalation workflow launched before the report exists (skipping phase three) has nothing to point to at the Day 2 audit step, guaranteeing every dispute drifts into the Day 3 manager review it was designed to avoid.

Related questions

Who should own commission dispute resolution in RevOps?

One named RevOps owner — typically a RevOps manager or operations analyst — should run the entire workflow end to end. Splitting ownership across sales managers and finance creates the same finger-pointing the playbook is designed to eliminate.

What happens when Outreach and Salesforce timestamps don't match?

Check for sync delays or missing field mappings first. If the mismatch persists after resync, apply a documented tolerance window (commonly 24 hours) and default to whichever system your commission policy names as authoritative.

Should commission disputes ever be split 50/50?

Only when the data audit and manager review are both genuinely inconclusive — this should apply to fewer than 10% of disputes. Defaulting to a split more often signals the underlying field architecture isn't capturing attribution cleanly.

How often should the commission report refresh?

Every 2 hours during business hours at minimum. Nightly refreshes let disputes sit unresolved for up to 24 hours, which is long enough for both parties to form entrenched, conflicting narratives before anyone looks at the data.

FAQ

What is the first step when an SDR disputes a commission from an outbound sequence in Outreach? Audit the data trail between Outreach and Salesforce before anything else. Pull the SDR's sequence enrollment timestamps and the Salesforce activity history to confirm whether the meeting traces back to a valid outbound touch — skipping this step means resolving the dispute on opinion instead of evidence.

Who owns the commission dispute resolution process in a RevOps playbook? A single RevOps owner runs the full workflow — reviewing evidence, updating the proof fields in Salesforce, and communicating the final decision to both the SDR and sales leadership. One owner prevents the process from splintering into parallel, conflicting conversations.

What Salesforce fields are critical for proving an SDR's commission claim? At minimum: a timestamped outbound-touch field synced from Outreach, an SDR source field set to the specific sequence used, and a write-protected meeting-source field populated at booking. Together these three let RevOps run a single report instead of reconstructing history from memory.

How do you handle disputes when Outreach activity data doesn't match Salesforce records? Check for sync lag or a broken field mapping first, since that explains most mismatches. If the gap persists, apply your documented tolerance window and default to the system your written commission policy names as authoritative — never decide case by case.

Can you automate commission dispute resolution for outbound SDRs? Partially. Automate the flagging — a validation rule that blocks Opportunity creation without required proof fields, and a dashboard surfacing pending disputes — but keep the actual ruling manual until you've piloted the process on one team and confirmed the criteria hold up.

What's the best way to report commission disputes to leadership? A weekly metric covering disputes opened, average resolution time against the 5-day target, and the split of outcomes between SDRs and closers. Trends here surface systemic issues — a broken sequence mapping or an ambiguous policy — faster than any single dispute does.

Sources

• https://help.salesforce.com/s/articleView?id=sf.compensation_planning.htm
• https://www.outreach.io/resources
• https://hbr.org/topic/subject/sales
• https://www.gartner.com/en/sales/topics/revenue-operations
• https://www.saastr.com/category/sales/
• https://www.forrester.com/blogs/category/revenue-operations/
• https://www.salesforce.com/resources/articles/sales-commission/
• https://www.g2.com/categories/sales-compensation

Related on PULSE

• What is the RevOps playbook for commission disputes during outbound SDR on Salesforce when parent-company rollup reporting?
• What is the RevOps playbook for commission disputes during outbound SDR on Salesforce when no dedicated RevOps hire yet?
• What is the RevOps playbook for commission disputes during marketplace listings on Salesforce when sales on Outreach?
• What is the RevOps playbook for commission disputes during outbound SDR on Salesforce when no dedicated RevOps hire yet?