Market Development Funds (MDF) and How Claims Get Paid

Avinash Gujje

CEO of ZUUZ. He scaled Cloud Box Technologies from 0 to $25M ARR in IT services and distribution before building ZUUZ. Connect on LinkedIn

Market development funds (MDF) are money an IT vendor sets aside to pay for marketing its channel partners run, such as webinars, events, email campaigns and digital ads. The partner gets the activity approved in writing, runs it, then claims reimbursement with proof of execution.

Picture an MSP three weeks after a co-funded security webinar, an illustration rather than a client story. The invoice is in finance's inbox, the approval in the channel manager's, and the attendees who wanted a call replied to a sales rep. The claim form wants all of it, plus the pipeline.

This guide covers market development funds end to end, for the reseller or MSP filing claims and the vendor reviewing them. The wider menu of partner rewards is in channel sales incentive programs.

What Are Market Development Funds?

Market development funds are a vendor budget that reimburses channel partners for approved marketing and sales activity promoting the vendor's products. The partner usually pays first and claims the money back with proof. DigiCert describes its MDF as cost sharing of approved activities, with funding set quarterly by partner engagement, projected return and fund availability.

In the IT channel, MDF sits beside margin and rebates in how vendors fund partners, as the channel sales guide shows. The vendor buys local reach; the partner gets marketing it might not fund alone.

Who qualifies for MDF?

Eligibility is set by the partner program, usually by tier. Ivanti's program is by invitation from the channel account manager, and Conga funds partners with a dedicated alliance manager or an approved joint business plan. Vertex ties eligibility to partner type and tier, and DigiCert requires good standing, a documented marketing plan and current training.

What MDF pays for, and what it does not

DigiCert's partner MDF guide covers sponsorships, customer events, email and direct mail, co-branded ads and sales training events. Microsoft's co-op list adds digital advertising, telemarketing and trade shows. DigiCert excludes product discounts, everyday equipment, funded employees and anything promoting competing products.

How Do Market Development Funds Work?

Market development funds move through six stages, from accrual to payout: funds accrue or are allocated, the partner gets a plan approved, runs the activity, assembles proof, files a claim and is reimbursed. Each stage has its own deadline, and missing one can forfeit the money even when the marketing worked.

1. Accrual or allocation. Microsoft splits eligible incentive earnings, giving 60% rebate and 40% co-op as an example, and accrues the co-op share over six months. Others allocate per request: Ivanti's 2022 MDF program guide describes a discretionary, proposal-based program, and Conga allocates funding per initiative.
2. Plan and pre-approval. Vertex's MDF terms want a request at least 60 days ahead, with expected outcomes and a budget, and say no verbal approval counts.
3. The activity. The partner runs what was approved, on the approved dates. DigiCert requires its logo on anything it funds.
4. Proof of execution. Microsoft's proof of execution steps require an execution date inside the campaign dates and a third-party invoice or Certification Service Report.
5. The claim. Ivanti gives partners 60 days from the activity to claim, after which the funds expire. Microsoft runs a set six-month claiming period.
6. Reimbursement. DigiCert pays within 60 days of the claim, and Microsoft completes its review by the end of the month after submission. Ivanti prohibits paying in advance.

How Is MDF Different From Co-op Funds?

The textbook answer is that co-op funds accrue as a share of a partner's past sales, while MDF is allocated forward against a plan the vendor approves. Vendors use the labels loosely, so the reliable test is how a program funds, approves and pays.

What most MDF guides get wrong

Most explainers say co-op is earned automatically and MDF must be approved. Microsoft's co-op is accrued, yet it still needs a pre-approval ID and per-activity proof, and it can pay for training and certifications, so the clean line breaks on a real program.

The bigger miss is the last column. Guides treat proof the activity happened as the whole claim, yet DigiCert asks for an ROI report and Ivanti asks partners to name a 30x pipeline return on the funds requested.

Why Do MDF Claims Get Denied?

MDF claims get denied for reasons written into the program terms, and nearly all are evidence problems: activity that drifted from the approval, the wrong invoice, dates outside the window or a missing results report. Weak marketing is rarely the stated reason.

• The activity changed. Vertex will not reimburse activity that materially differs from the approval, and Ivanti requires co-branded assets approved before launch.
• No written approval. A yes on a call is not approval under Vertex's terms, and Ivanti never funds activity retroactively.
• The wrong invoice. DigiCert says a partner-generated invoice alone is not enough; it wants the suppliers' invoices.
• Dates outside the window. Microsoft requires the execution date inside the campaign dates, and Ivanti accepts no invoices after its 60-day deadline.
• Missing results. DigiCert's required proof includes an ROI report, so a claim without one is incomplete.

The MDF Proof Chain, Applied

The MDF Proof Chain turns those denial reasons into a checklist. Breaks at links one to three get a claim denied. Breaks at links four and five get it paid with a thin results report and, where funding follows projected return, a smaller allocation next time.

Each link sits with a different person, from the channel manager's inbox to finance and the reps, so capture each on the day it happens.

Worked Example: One MSP Webinar Claim

An illustration: one webinar at a hypothetical MSP, using generic program rules.

1. Approval. The MSP requests funding with topic, audience, expected outcomes and budget, then files the approval ID and date the day it arrives.
2. Invitations. Marketing keeps the final email with its dated header, a proof Microsoft lists for email campaigns.
3. The event. The team exports attendee lists with contact details and files the platform's invoice.
4. Follow-up. Over three weeks, attendees reply to the rep. One asks about a backup review, so the rep opens an opportunity and files a deal registration, which DigiCert asks partners to tie to MDF campaigns.
5. The claim. The MSP files the approval ID, invoices, creative, attendee list and each opportunity with the date of its first reply.

Step four is where claims go thin: the reply that started the opportunity sits in a rep's inbox, and the opportunity rarely names the campaign.

What Vendors Should Check Before Paying

Vendors should compare each claim with its approval line by line, then ask for pipeline as opportunity or registration IDs with first-contact dates, because a bare count cannot be checked. When one customer appears in two partners' lists, or an IT distributor runs a campaign across several resellers, the rules in partner attribution should decide who counts it.

Claims sit in an incentives portal and opportunities in the CRM (see PRM vs CRM), so a portal-only review checks paperwork alone. A fairer yardstick than spend utilization is attributed pipeline divided by total campaign cost, counting both the vendor and partner shares.

What Operators Learn About MDF

From an operator's seat. In IT services and distribution sales, the expensive hour in MDF is the afternoon before the claim deadline: forwarding approval emails, chasing a supplier for a proper invoice and asking reps which attendees ever replied. The campaign itself finished weeks earlier.

The part teams do not plan for is that vendors read claims as a signal. Complete, on-time claims with results look like partner engagement, one input DigiCert names for setting funding. The fix is unglamorous: open the evidence folder the day the approval arrives.

MDF Evidence: How ZUUZ Writes It to the CRM

ZUUZ is revenue intelligence for the IT channel, an AI layer over the existing CRM. It reads the sales inbox, calendar and meeting tools, finds deal signals and updates Salesforce, HubSpot, Zoho, Attio or Pipedrive, and ConnectWise PSA, automatically, with full change history and one-click rollback.

That covers links four and five. When an attendee's reply turns into a deal, ZUUZ writes the contact and deal signals to the CRM, so the opportunity carries its dated first thread; campaign tagging stays with the CRM or the vendor's template. ZUUZ does not administer, approve, calculate or pay market development funds, file claims or replace a PRM.

RA Technologies, a US IT services company, ran ZUUZ on the HubSpot instance it had used for two years, with the same team, and ZUUZ surfaced $120K in pipeline within 72 hours that the CRM had never seen, captured from the sales mailbox (RA Technologies case study). At Cloud Box Technologies, inbound email turns into leads and renewals, and 10 to 12 renewals are tracked in minutes.

When an MDF Claim Is Not Worth Filing

Ivanti asks partners to match up to half the cost of some activities, so a small activity with little pipeline behind it can cost more than it recovers, and letting it go is rational. Under rules like DigiCert's, though, missing proof on a past activity blocks the next allocation, so close out what is already approved.

ZUUZ has limits too. A team that needs fund budgeting, claim workflows or a partner portal needs a PRM or MDF system, and ZUUZ is neither; teams that cannot connect a mailbox need another route.