*Gap samples / Gap 8 - Referrals (admins)*

# Referral and deal registration statuses: what each means, and what to do

A reference page. Look up the status a submission shows, read what it means, and do what the last column says. The second table starts from a symptom instead, for when something is missing and you do not know its status yet.

**Gap:** 8 of 13 · **Reader:** Admin working the approvals queue, support · **Type:** Reference

## Why this page needs to exist

The queue itself is documented: [Referral Approval](https://support.eulerapp.com/en/c/security-access/referral-management/referral-approval) covers accept and reject, and [Potential Duplicate](https://support.eulerapp.com/en/c/integrations/potential-duplicate) covers the three duplicate choices. What no page says is what each status means once it is set. The status values appear only in the API Reference and the MCP reference, so support cannot point a customer to them. One consequence goes unexplained: **Mark as Approved** sets the status to approved and creates nothing.

---

*Sample documentation starts here*

## Statuses

| Status | What it means | What to do |
| --- | --- | --- |
| `pending` | Submitted, waiting for a decision. Every channel lands here: portal, embedded form, email, Slack, PAM. Nothing approves on its own. | Accept or reject from **Referrals to Approve** ([Referral Approval](https://support.eulerapp.com/en/c/security-access/referral-management/referral-approval)). |
| `creating` | Accepted, and EULER is still writing it. API-created referrals show this until checks finish. For partner applications on CRM-only Salesforce forms, the CRM record was written and the partner arrives later through the sync. | Wait, then check again. Do not accept it a second time. |
| `approved` | Accepted. Either EULER created the CRM records, or someone chose **Mark as Approved**, which creates nothing. | If no CRM record exists, it was marked rather than created. Create the record in the CRM by hand. |
| `duplicate found` | The CRM already has a match, on email for contacts, and on name or website for companies. | Choose: **Proceed with Creation** (create or reuse the CRM records), **Mark as Approved** (the record already exists, create nothing) or **Reject**. |
| `error writing to crm` | Accepted, but the CRM refused the write. | Fix the cause, usually a form mapping or a CRM duplicate rule, then retry. See the symptom table below. |
| `rejected` | Declined. If the form has rejection reasons configured, one was required. | Nothing, unless the partner asks why. Send the reason when you reject, not later. |

**Drafts** are not submissions: they never appear in the queue or in counts.

**Referral or deal registration**

Both use these statuses. A deal registration also expires after the window you set, because it claims an opportunity the partner is working. A partner still working a deal near expiry should ask their Partner Manager before it lapses, because protection does not carry forward on its own.

## Accepting and rejecting well

- **Read the duplicate warning before you click.** EULER checks your CRM on the referred contact's email before you decide.
- **Associate the partner** when a submission from an external form came from an email address EULER does not recognize. Use **Associate Partner** before accepting, so attribution is right from the start.
- **Send a message on rejection.** You can notify the partner when you accept or reject. A reason they can act on keeps the next referral coming.
- **Outbound referrals reverse the roles.** For a referral you sent to a partner, the partner decides, and the form answers stay hidden from them until they accept.

## When something is missing

| Symptom | Most likely cause | Fix |
| --- | --- | --- |
| Partner says they submitted, you see nothing | Submitted to a different company's portal, or still a draft. Email submissions get no confirmation email. | Ask PAM or POPS for that partner's referrals in both directions. |
| Approved, nothing in the CRM | Marked as Approved rather than created. | Create the record in the CRM by hand, with the partner attached. |
| Approved, with an error | An API Value that matches no field. | Fix the mapping, run the form's Test, retry. |
| Salesforce: approval failed on a duplicate | A Lead has the same email. | Convert the Lead to a Contact, then accept. See [Salesforce setup checks](05-salesforce.md). |
| Flagged duplicate that isn't one | A typo in the email. | Correct the email, then decide. |
| Deal in the CRM, not credited to the partner | The partner link on the CRM deal is empty, or the affiliate link's tracking id was not captured. | Fill the partner link on the deal. For affiliate traffic, check the tracking script is installed on the page ([affiliate attribution](https://support.eulerapp.com/en/c/affiliate-links/how-to-use-affiliate-links-in-euler-for-partner-attribution)). |

## What wrong looks like

**WRONG - CLEARING THE QUEUE**

```
"Duplicate found" on 12 referrals
-> Mark as Approved on all 12, to clear the queue

Why it fails: Mark as Approved creates nothing. Any of the
12 that were not really in the CRM are now approved,
attributed nowhere, and invisible to sales. Mark as
Approved only the ones you have confirmed exist in the CRM.
```

## Confirm with engineering

1. The web app shows these statuses with the same wording as the API. Yes / no / correct me with the labels.
2. "duplicate found" is set before a decision, and "error writing to crm" after one. Yes / no / correct me.
3. A referral in "error writing to crm" can be retried from [location]. Correct me.
4. Rejection reasons are configured per form at [location]. Correct me.

### Related documentation

- [Referral Approval](https://support.eulerapp.com/en/c/security-access/referral-management/referral-approval)
- [Inbound Referral Management](https://support.eulerapp.com/en/c/security-access/referral-management/inbound-referral-management)
- [Potential Duplicate](https://support.eulerapp.com/en/c/integrations/potential-duplicate)
- [Tracking Your Referrals and Deals](https://support.eulerapp.com/en/c/partner-journey/referrals-and-deals/tracking-your-referrals-and-deals) and [Referrals Sent to You](https://support.eulerapp.com/en/c/partner-journey/referrals-and-deals/referrals-sent-to-you)
- [How to Use Affiliate Links for Partner Attribution](https://support.eulerapp.com/en/c/affiliate-links/how-to-use-affiliate-links-in-euler-for-partner-attribution)
- [Reviewing Referrals and Deal Registrations (MCP)](https://support.eulerapp.com/en/c/euler-mcp-customers/referrals)
- [GET /v1/referrals (API Reference)](https://api.eulerapp.com/docs#ep-list-referrals)

### Sources for this page

- API Reference: GET /v1/referrals status values, drafts excluded, conditional rejection reason, outbound answers hidden until accepted, POST /v1/referrals returns 202 and status "creating".
- MCP connector reference: partner application statuses, CRM-only "creating"; resolve\_referral (direction decides who resolves).
- Referral Approval (Referrals to Approve, Associate Partner, message to partner). Potential Duplicate (three choices, matching rules). Submitting a Referral (registration expiry, no confirmation email).

### Next

- Gap 2: [DealFlow AI](03-dealflow.md). Where many pending submissions come from.
- Gap 4: [Salesforce setup checks](05-salesforce.md). The causes behind most CRM errors.

---

*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.*