*Gap samples / Gap 6 - Rewards (admins)* # Set up MDF and CIF funds, and decide on fund requests You finish this page with one fund your partners can request against, an approver assigned, and a first request taken from submission to a decision. MDF is a Market Development Fund: money a partner spends on marketing for you. CIF is a Co-op Investment Fund. Both run on the same request flow. **Gap:** 6 of 13 · **Reader:** Admin, partner marketing, finance · **Result:** A live fund and one decided request ## Why this page needs to exist Funds appear in the help center only inside AI articles: [PAM: Incentives, Funds (MDF/CIF) & Service Projects](https://support.eulerapp.com/en/c/ai-agents/pam-incentives-funds-mdf-cif-service-projects) and the MCP prompt guides for requesting and deciding. Forms 2.0 lists a Fund Request form type. Nothing tells an admin how to set up a fund, who approves, or what each step of a request means. --- *Sample documentation starts here* ## How a request moves A fund has a budget, a status, period dates and a request form. A partner's request moves through ordered steps. Each step is either the partner's to act on or yours. 01RequestPartner fills the fund's form02ApproveYour approver decides03ExecutePartner runs the activity04ProofPartner uploads evidence05ReimburseYou pay out06CIF onlyAssign the resulting deal Which steps a fund uses depends on how it is configured. **[VALIDATE STEP ORDER]** ## Before you start - A connected CRM. A Fund Request form is a Form, and Forms need one. - A budget figure and a period for the fund. - A named approver. Only a user configured as an approver for the step can decide it. ## What can go wrong - No approver assigned: requests wait on a step nobody is allowed to complete. - Paying before proof of performance turns co-marketing into a subsidy you cannot defend to finance. - Some steps can be finished only in the EULER web app, not through PAM or POPS: customer upload, reimbursement, and assigning a deal to a CIF. ## Steps 1. **Build the request form** In **Settings > Forms**, create a form of type **Fund Request** (see [Forms 2.0](https://support.eulerapp.com/en/c/core-euler-features/customization-content/forms-2-0)). Ask for what you need to approve: the activity, the expected result, the amount and the dates. **Check:** the form's Test passes. 2. **Create the fund** Create an MDF or CIF fund with its budget, period dates and the form from step 1, and set which partners are eligible and for how much. **[VALIDATE MENU PATH]** **Check:** the fund is active, and an eligible partner can see it in their portal or by asking PAM which funds are available. 3. **Assign approvers to each approval step** Name at least one approver per approval step. You **should** set an amount below which requests clear on their own, so small requests do not wait on a manager. **[VALIDATE THRESHOLD SETTING]** **Check:** every approval step shows a named approver. 4. **Decide the first request** A submitted request appears as pending against its fund. Read the partner's answers, then: - **Approve** completes the approval step and the request moves on. - **Reject** ends the request. - **Request info** asks the partner for documents or notes. It is not a decision: the request stays on the same step and waits on the partner, and you can still approve or reject after. **Check:** the request shows the next step, or shows waiting on the partner. 5. **Gate payment on proof** Payment **shall** wait until the partner's proof of performance is approved. Then complete reimbursement in the web app. **Check:** the fund's paid amount rose by the request amount, and its remaining budget fell by the same. **Budget words** **Committed** is approved but not yet paid. **Paid** has gone out. **Remaining** is budget minus committed minus paid. **[VALIDATE FORMULA]** ## What wrong looks like **WRONG - APPROVER NOTE** ``` Approved. Pay once the webinar is done. Why it fails: "done" is not evidence, and the note is private to your team. Use Request info on the proof step and list what counts as proof: the recording link, the registrant count, the attendee list. ``` ## Confirm with engineering 1. Funds are created at [menu path]. Correct me. 2. The auto-approve threshold is set per [fund / step]. Correct me. 3. Remaining = budget - committed - paid. Yes / no / correct me. 4. The step order is configurable per fund. Yes / no / correct me. 5. "Assign deal to CIF" links the request to the deal the co-investment produced. Yes / no / correct me. ### Related documentation - [PAM: Incentives, Funds (MDF/CIF) & Service Projects](https://support.eulerapp.com/en/c/ai-agents/pam-incentives-funds-mdf-cif-service-projects) - [Reviewing and Deciding on MDF and CIF Fund Requests (MCP)](https://support.eulerapp.com/en/c/euler-mcp-customers/fund-requests) - [Applying for MDF and CIF Funds (MCP, partner side)](https://support.eulerapp.com/en/c/euler-mcp-partners/funds-request) - [Forms 2.0: the Fund Request form type](https://support.eulerapp.com/en/c/core-euler-features/customization-content/forms-2-0) - [Agency programs on eulerhq.com](https://eulerhq.com/solutions/agencies) (MDF and proof of performance) ### Sources for this page - MCP connector reference: customer\_fund\_requests and customer\_fund\_requests\_manage (fund budget, status, period, form; step types; approver rule; request\_info; web-app-only steps); fund\_requests (partner side). - Forms 2.0: Fund Request form type. eulerhq.com agency FAQ: eligibility, threshold auto-approval, proof of performance, total/committed/paid/remaining. ### Next - Gap 5: [Incentives and commissions](06-incentives.md). How commissions are calculated. - Gap 12: [Style guide](13-styleguide.md). MDF is expanded two ways today. --- *Independent writing sample by Bachtiar Widyantoro (bachwidy.site), November 2026. Not published or endorsed by EULER. Free to reuse and edit. Customer names in examples are fictional. Anything marked [VALIDATE ...] or [CONFIRM ...] is not settled by a public source and needs checking before publishing.*