What is deal registration, and how is it different from a referral?

Deal registration, defined

Deal registration is the process in which a channel partner, such as a reseller, managed service provider or ERP implementation partner, submits a specific sales opportunity to a vendor and receives approval that protects the opportunity for a set period. The approved partner usually gets better pricing or extra margin on the registered deal, and other partners who later spot the same opportunity are turned away.

Vendors run it for two reasons: to reward partners who find new business rather than simply fulfil orders, and to settle channel conflict before two partners, or a partner and the vendor's own sales team, discount against each other for the same customer.

A referral program works on a different principle. In the SourceX partner program there is no approval step that reserves a company for you. Credit goes to the first valid referrer whose introduction leads to a verified company application within the attribution window.

How deal registration works in a vendor program

The mechanics differ by vendor, but most programs follow the same sequence inside a partner relationship management (PRM) portal.

1. Qualify: the partner confirms a named end customer, a need, a budget owner and an expected close date.
2. Submit: the partner enters the customer, products, estimated value and timeline in the vendor's portal.
3. Conflict check: a channel manager checks whether the account is already registered, already in a direct sales cycle or an existing customer.
4. Approve or reject: approval starts the protection period defined in the program guide; a rejection usually comes with a reason.
5. Work the deal: the partner sells, scopes and often implements, and may need to show progress to keep or extend the registration.
6. Close or expire: if the deal closes in time, the registered pricing applies; if not, the registration lapses and the opportunity is open again.

Illustrative: a fictional 40-person MSP registers a firewall and backup refresh for a 210-person regional distributor it already supports. The vendor approves, and the MSP buys at the registered price and resells. Months later, during a Microsoft 365 tenant review, the MSP's vCIO notices that the distributor still holds 14 years of order history, customer service tickets and warehouse procedures across a dozen systems. There is nothing to register for that observation. The MSP sends the distributor's CFO a referral link, the CFO applies, and the MSP's credit depends on that application being verified.

Deal registration vs a referral introduction

Three deal registration habits that do not carry over

Partners who live in vendor portals tend to bring three habits to referral programs, and each one causes problems here.

1. Staking accounts in bulk. Registering every client to hold a place can make sense in some vendor programs. In a referral program a name on a list is not an introduction, and only an introduction that leads to a verified application earns credit.
2. Owning the opportunity. In deal registration you carry the deal to close. Here you introduce and step back. You never export, upload or describe a client's confidential records; the company decides what to share, under redaction rules agreed before any work starts.
3. Expecting margin at invoice. No reward is guaranteed, and nothing is payable when a meeting happens or an agreement is signed. Payment follows the buyer's payment to SourceX.

One habit does carry over: qualify before you submit. A good candidate is a US company with 50+ full-time employees at peak (contractors excluded), several years of documented operations, the rights to the records it would license, and an owner, CEO, CFO or other authorized representative ready to sponsor the conversation. The who qualifies page sets out the full baseline, and the company fit checker gives a preliminary, non-binding read without asking for contact details.

Why the difference matters for MSPs and ERP partners

MSPs and implementation partners see what most advisers never do: how many systems a client runs, how far back the archives go and whether anyone can still export them. That visibility makes you a strong source of introductions, as the page on referral opportunities for managed service providers explains. It also means clients trust you with access, so the introduction should rest on what the owner chooses to share, not on what you can see in their tenant.

Two practical points follow. Tell the client plainly that you may receive a referral reward if a license closes. And if you promote the program publicly, for example in a client newsletter or on LinkedIn, FTC staff guidance on endorsements says a material connection such as referral compensation should be disclosed clearly and close to the recommendation (FTC Endorsement Guides FAQ). This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

Related terms

• Customer referral program vs partner program: how programs for existing customers differ from programs built for professional partners.
• Success fee: pay that exists only when a defined outcome happens, the model a referral reward follows.
• Post-merger integration: the phase in which many MSPs consolidate tenants and retire systems, and where record histories are most at risk.
• Attribution window: the period within which an introduction must lead to a verified company application to earn credit.

Next step

If a client you support already fits the baseline, register as a partner and send the introduction through the referral form or your referral link. There is no opportunity to file in advance; the company's verified application is what counts.