# Duplicate payment referral brief template | SourceX

Canonical: https://refer.sourcex.si/resources/duplicate-payment-recovery-referral-brief-template
Last updated: 2026-11-04

A company introduction about duplicate payment recovery needs nine facts, each confirmed by the AP director: company size and location, the business task, the record classes and their years, the systems, rough case volumes, the open question, any access deadline, who owns the records and who can authorize a discussion. Nothing confidential goes in it: no invoices, emails, exports, supplier names or recovered amounts. The template below captures those facts, and a completed Illustrative brief shows what a finished one looks like.

This template is part of the [duplicate payment recovery guide](/guides/workflow-duplicate-payment-recovery), which explains what a useful recovery history contains. The brief turns one planning conversation with the AP director into a page they can forward to the CEO.

## The nine fields, with prompts

Each field has a prompt to ask the AP director and a note on how to record the answer. Leave nothing blank: write "unknown" where the answer is not yet confirmed.

1. **Company.** Prompt: "How many full-time staff at peak, not counting contractors? Where is the company based, and how long has it operated?" Record: sector, headcount, country, years.
2. **Business task.** Prompt: "In one sentence, how does the team find and recover duplicate payments?" Record: the task as the AP director describes it, including whether an outside audit firm helps.
3. **Record classes and years.** Prompt: "Which of these exist, and from which year: invoice images and versions, approval history, payment runs, match results, supplier emails, credit memos, close notes?" Record: each class with its first year.
4. **Systems.** Prompt: "Which tools hold each of those, and which are being replaced?" Record: tool names as plain text, and which stays or goes.
5. **Volumes.** Prompt: "Roughly how many invoices a year, and how many duplicate cases found and recovered in total?" Record: ranges, marked estimate or report-based.
6. **Open question.** Prompt: "What can nobody confirm yet about this history?" Record: one question, worded neutrally.
7. **Access deadline.** Prompt: "Is any system contract ending, or any data due for deletion, and when?" Record: the date from the contract, or "none known".
8. **Owners and decision-maker.** Prompt: "Who owns each record class, and who can authorize a discussion about licensing company data?" Record: roles, not personal details beyond the authorized contact's name.
9. **Not shared.** Record: a line confirming what you did not see or receive.

The [client opportunity brief generator](/tools/client-opportunity-brief-generator) gives a general first draft; these prompts add what a recovery history needs.

## A completed brief (Illustrative)

Written by a partner after a planning call with the AP director of a fictional company. Every value is invented.

| Field | Entry |
|---|---|
| Company | Industrial parts distributor, 260 full-time staff at peak, U.S., operating 14 years |
| Business task | Finding and recovering duplicate supplier payments, including resubmissions with altered references; quarterly internal review, no outside audit firm |
| Record classes and years | Invoice images and approval history since 2017; payment runs and credit memos since 2012; quarterly match results since 2019; AP mailbox threads since 2018; close notes since 2019 |
| Systems | AP capture platform being replaced in the first quarter; ERP, which stays; shared AP mailbox |
| Volumes | About 60,000 invoices a year; the AP director estimates a few hundred recovered duplicates in total; not verified |
| Open question | Whether the old platform's rejected and resubmitted versions export with their images |
| Access deadline | Capture platform contract ends March 31 |
| Owners and decision-maker | AP director (capture platform, mailbox), controller (ERP payables and credits); CEO can authorize, with the AP director as sponsor |
| Not shared | No invoice, email, export, screenshot or supplier name |

Two entries carry most of the weight. The open question shows the CEO exactly what is uncertain. The access deadline is the only urgency that counts; the [retention timeline for recovery records](/guides/preserve-duplicate-payment-recovery-records) shows what disappears first when that date passes.

## Notes behind the example

Why the brief lists record classes by year rather than one span: each class has its own life. Images, rejected versions and match results often live only in the capture tool, while posted documents stay in the ERP, so a single "history since 2012" line would overstate what survives a platform change. The [retention timeline](/guides/preserve-duplicate-payment-recovery-records) explains the order in which they tend to go.

Why the access deadline names a contract, not a feeling of urgency: deadlines have documented mechanics. If the AP mailbox sits in a Microsoft 365 tenant that is being retired, for example, Microsoft describes Expired, Disabled and Deleted stages, with data reachable only by admins while Disabled and no recovery once deleted. A date taken from the contract tells the CEO exactly how long the owners have to decide.

Why the open question is about exports and versions: whether the old platform can produce rejected versions with images is unknown until its administrator checks, and guessing would set false expectations. A related question is worth asking in the same call: does the company record why an invoice was stopped? Oracle Payables, for instance, uses predefined hold and release types, including a matching hold reason and a matching release reason, and invoices cannot be paid until holds are released. Where reasons like these were captured, the brief can say the history records decisions, not just payments. The [AP exception handling page](/data-types/accounts-payable-exception-handling-process) covers the wider queue this sits in.

## Common mistakes in duplicate payment introductions

| Mistake | Why it hurts | Instead |
|---|---|---|
| Quoting total dollars recovered | Shares financial data without authority and implies a value | Give case counts, marked estimate |
| Naming suppliers who paid back | Confidential, and often restricted by contract | Describe supplier types only |
| Attaching a sample of the recovery log | Partners never handle raw records | Describe the log's columns and years |
| Naming the AP admin as the contact | Technical access is not authority | Name the CEO, who has the authority |
| Guessing at an export capability | Creates an expectation nobody has checked | Write the open question |
| Suggesting what the company might earn | Unknown until SourceX reviews the opportunity | Leave value out entirely |

The [decision tree on who can license recovery records](/questions/who-can-license-duplicate-payment-recovery-records) explains how the record owners, the sponsor and the CEO fit together. Distributors are a common fit for this kind of history; see [specialty distribution private equity](/industries/specialty-distribution-private-equity), and the [industries hub](/industries) for other sectors.

## Before it leaves your outbox

- [ ] The AP director has corrected every line, and the authorized contact expects the brief.
- [ ] Headcount is 50 or more full-time staff at peak, contractors excluded, and the company has a documented operating history.
- [ ] As far as the sponsor knows, the company has rights to license the records; whether it actually does is decided in SourceX's rights review.
- [ ] Location is covered. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.
- [ ] You have signed the Channel Partner Agreement.
- [ ] You know what you will need later to be paid; see [what you need to receive a referral payment](/resources/what-do-i-need-to-receive-a-referral-payment).

SourceX licenses approved business data directly from companies for AI training and evaluation and manages the agreement, rights review, data preparation, delivery and payout. Unknown until SourceX reviews the opportunity: dataset demand, the rights result, the company's offer and any reward. The first valid introduction within the 90-day window is credited when the company submits a verified application.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

When the AP director has confirmed the brief and the decision-maker is expecting it, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you submit the introduction.

## Sources

- https://refer.sourcex.si/terms
- https://learn.microsoft.com/en-us/microsoft-365/commerce/subscriptions/what-if-my-subscription-expires?view=o365-worldwide
- https://docs.oracle.com/en/cloud/saas/financials/25b/fappp/invoice-holds-and-releases.html
