PartnerStack partner support and integration documentation reviewed 11 November 2026. This is a documentation-based operational guide.
Does a closed-won deal automatically mean a PartnerStack commission is payable?
No universal rule applies. In PartnerStack, a partner can register a deal, obtain program approval, move it through configured stages and mark it closed-won. The company may then need to approve the closed-won deal. Whether commission is awarded at that stage or on later customer transactions depends on the company’s commission offer. Treat deal registration, deal approval, closed-won approval and commission payment as distinct checkpoints.
This guide focuses on the post-registration path. For the earlier lead-versus-deal distinction, see PartnerStack leads vs deals. For ownership disputes and expiry policies, use our B2B partner deal registration rules.
Four different checkpoints in the partner pipeline
PartnerStack’s partner help article says that deal registration is available only if the company enabled it. The company reviews the submission, and a partner can update approved deals through program-defined stages. When the partner marks a deal closed-won, the company is notified to approve it. The help article explicitly states that some programs commission on closed-won deals while others commission on subsequent transactions.
| Checkpoint | What it means | What to verify before payout |
|---|---|---|
| Deal submitted | Partner claims an opportunity | Customer identity, duplicates, eligibility |
| Registration approved | Partner may progress deal in pipeline | Ownership and protection terms |
| Closed-won recorded | Partner reports sale won | Company approval, CRM stage consistency |
| Commission offer triggered | Configured milestone or qualifying transaction | Offer conditions, amount, hold, reversals |
A sales representative changing a CRM stage to Closed Won does not prove the PartnerStack commission offer has triggered. Similarly, a partner changing the PartnerStack stage does not prove the invoice has been collected. Define one source of truth for each stage and reconcile them rather than relying on matching labels.
Two legitimate commission models
Model A: a closed-won bounty
A program might pay a fixed $500 after an approved deal is closed-won, subject to contract execution and a defined cancellation period. In this model, the partner’s earning trigger is the approved milestone, not a billing webhook. Finance must still decide what happens if the customer never pays, cancels during onboarding or signs a smaller contract than expected.
Model B: commission on paid customer revenue
Another program may pay 10% of the first qualifying annual subscription invoice. Suppose a deal is marked closed-won for $12,000 annual contract value, but the first invoice is $10,000 of eligible subscription services and $2,000 of excluded implementation work. The candidate commission is $1,000 after the qualifying invoice is paid, not $1,200 at CRM close. The amount and timing are illustrative contractual choices, not PartnerStack defaults.
For longer recurring programs, define whether future invoices, expansions, renewals or customer transfers count. The annual subscription commission policy provides a separate billing perspective.
How to keep PartnerStack and the CRM aligned
PartnerStack’s deal registration integration guide recommends testing the creation of a CRM deal from a partner submission, duplicate detection and stage updates in both systems. Its default example stages are Working, Closed Lost and Closed Won, although a merchant may configure additional stages. The guide also calls for verifying the customer referral record when a deal closes and checking company approval where configured.
- Capture the claim: store partner ID, registered deal ID, account/domain, CRM opportunity ID, contact and timestamp.
- Resolve duplicates: check whether another partner or direct sales already owns the opportunity before approving it.
- Map stages: define which CRM stages correspond to PartnerStack stages and which direction each update flows.
- Record approval: distinguish approval of the original registration from approval of a closed-won outcome.
- Trigger commission: use the configured offer milestone or qualifying transaction, not an assumed generic closed-won event.
- Audit reversals: record cancellation, duplicate attribution, refund, unpaid invoice and clawback decisions with evidence.
For a sales-led SaaS program, a deal can stay open for months. A stable opportunity ID is more reliable than an affiliate cookie alone. Our PartnerStack Salesforce sync guide covers a CRM-specific mapping example.
Avoid double commission on partner and direct-sales claims
Two partners may register the same account using different contact names, or a direct salesperson may already be negotiating with the buyer. Establish an approval queue that compares company domain, legal entity, CRM opportunity, registered product and sales region. Do not automatically reject every shared domain, because subsidiaries and distinct business units may represent separate opportunities. Escalate ambiguous cases and document the final owner.
After approval, retain the registered owner even if a new marketing click occurs later, unless the written deal-protection policy allows reassignment. Where multiple partner contributions are recognized, distinguish partner-sourced revenue from partner-influenced revenue rather than paying two full sourced bounties by accident. See our partner-sourced vs partner-influenced guide.
Deal registration and payout QA checklist
| Test case | Expected result |
|---|---|
| Partner lacks deal submission permission | No unsupported registration workflow shown |
| New approved deal | CRM record created with matching partner and deal IDs |
| Duplicate account registration | Ownership conflict reviewed, not silently paid twice |
| Working to Closed Lost | CRM stage sync correct; no closed-won bounty |
| Working to Closed Won | Company approval and offer conditions checked |
| Closed-won with unpaid invoice | Cash-based offer stays pending |
| Closed-won event replay | One commission per eligible milestone or transaction |
| Customer refund or contract cancellation | Reversal policy and evidence recorded |
Frequently asked questions
Can a partner register any deal in PartnerStack?
Only if the company has enabled deal submissions and the partner’s program allows them. Registration fields and stages vary by program.
Can the partner edit a closed-won deal?
PartnerStack’s help article says a partner cannot update a deal after moving it to closed-won. The company may still have approval and commission review steps.
Is the commission always paid on a closed-won stage?
No. PartnerStack documents different offer structures: some reward the closed-won milestone, while others reward later customer transactions. Read the actual program offer.
Official sources reviewed
Editorial disclosure: This independent guide is based on PartnerStack’s public documentation reviewed 11 November 2026. Commission rates and amounts are illustrative merchant choices. We have not tested a specific PartnerStack account or represented its offer terms as universal.