This template belongs to the cash application exceptions guide. Fill it in after a first conversation with the AR director or controller, using only facts someone at the company will stand behind.
The blank brief, field by field
Copy the left column and answer in one or two lines each. "Unknown" is an acceptable answer.
| Field | Fill in | Where the answer usually comes from |
|---|---|---|
| Company | Sector, country, full-time headcount at peak | The owner or CFO |
| Exception types | Short payments, overpayments, unreferenced receipts, multi-invoice payments with deductions | The AR director |
| Record classes | Bank statement files, remittance advices, match logs, deduction cases, credit memos, rebills | The AR director |
| Systems | Bank feed or portal, cash application tool, ERP, shared remittance mailbox, deduction tracker | The AR director with IT |
| Coverage | Years each system holds, and any gap from an earlier migration | IT or the controller |
| Volume | Payments a month, exceptions a month, open deductions, as estimates with their source | The AR director |
| Deadline | Any documented end of access: tool contract end, read-only period, archive date | The controller or procurement |
| Open question | The one thing nobody yet knows about how complete the records are | The AR director |
| Owner and sponsor | Who owns the records day to day; who sponsors the discussion | The AR director |
| Authorized contact | The CEO, who can approve a licensing discussion | The CEO's office |
Write field values the way the company says them. If the AR director says "our remittances come in three ways", the brief says that, not your reinterpretation.
Writing each field so it survives review
A brief is read by someone who has never met the company. Each entry should let them picture the records without seeing any.
- Record formats, not contents. "Remittances arrive as EDI 820 files from large customers and emailed PDFs from the rest" is useful. The X12 820 transaction set can serve as a payment order, a remittance advice or both, so naming it tells a reviewer the data is structured. A sample file is never needed.
- Bank side in one line. "Daily bank statement files" or "camt.053 statements from two banks" is enough. camt.053 is the ISO 20022 bank-to-customer statement message reporting booked entries and balances.
- Matching method. Say whether appliers mark invoices by hand or rely on automatic settlement. In Dynamics 365 Finance, without a settlement priority, automatic settlement picks transactions by due date, and manual marks take precedence; whether people override that default is part of what makes the history instructive.
- Volumes with a source. "Several hundred exceptions a month, per the AR director, not verified" beats a precise number from nowhere.
- One open question only. If you have five, the brief is premature. Pick the one that most affects whether the records join up.
Completed example (Illustrative)
Illustrative. A fictional 410-person building products manufacturer in the U.S. The AR director reviewed and approved every line.
| Field | Entry |
|---|---|
| Company | Building products manufacturer, United States, about 410 full-time employees at peak |
| Exception types | Mainly multi-invoice payments with a deduction on one invoice; some unreferenced receipts |
| Record classes | Bank statement files, remittance advices (EDI and emailed PDFs), match logs, deduction cases with notes, credit memos and rebills |
| Systems | Bank portal, a cash application tool due for replacement next year, the ERP, a shared remittance mailbox |
| Coverage | About eight years in the ERP; the cash application tool since its rollout six years ago |
| Volume | Several hundred exception cases a month, per the AR director; not verified |
| Deadline | The cash application tool contract ends next year; read-only period still being confirmed by procurement |
| Open question | Whether the outgoing tool exports deduction case notes with the remittance images attached |
| Owner and sponsor | AR director owns the records and will sponsor |
| Authorized contact | CEO, with the CFO preparing the case and counsel reviewing customer contracts |
Nothing is attached. The brief does not include a remittance, a statement extract, a customer list or a screenshot of the tool.
What the reviewer reads first
SourceX reads a brief for three things before anything else, so put care into these fields.
- Authorized contact. An AR director is the right first conversation, but the person who can say yes is the CEO. If the brief names only the sponsor, the next step stalls.
- Deadline. A real documented date, such as a tool contract end, changes priority. A guessed date does not; mark it unconfirmed.
- Open question. It tells the reviewer what to ask first. For cash application, it is usually whether case notes and remittance images stay linked when exported.
For the deadline field in particular, the retention timeline shows which record classes fade first in a tool switch. To check the authorized contact, the who can license answer maps the finance roles.
Before you send it
Check the basics against the program rules:
- Size: 50+ full-time employees at peak, contractors excluded.
- Geography: 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.
- History and rights: the company has a documented operating history and the brief flags customer confidentiality as an open rights question, without answering it.
- Agreement: you have signed the Channel Partner Agreement before submitting. The first valid introduction within the 90-day window is credited when the company submits a verified application.
For the covering note to the owner, adapt the warm introduction brief or draft one with the client opportunity brief generator. If the CFO sits in a holding company, the holding company CFO page explains that role. For why this kind of decision history matters to AI developers, see why AI agents need work data.
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.
Once the AR director has approved every field or marked it unknown, register as a partner, confirm the company on who qualifies, and read the program terms before you send the brief.