This decision tree is part of the cash application exceptions guide. It answers one question for treasury systems advisors: who inside a company can say yes to a conversation about its cash application exception history?
Who touches the records, and why that is not authority
Cash application history is spread across finance. The treasury manager sees the bank side: booked credits, often received as ISO 20022 camt.053 statements reporting booked entries and balances. The AR team sees remittances, which may arrive as X12 820 transactions (a format that can serve as a payment order, a remittance advice or both), PDFs, portal downloads or emails. The ERP administrator sees settlements and credit memos. A treasury systems advisor may have worked with all of them on a bank connectivity or cash application project.
Each of those people can describe a part of the chain. None of them, alone, can decide that the company may license it. That decision involves customer contracts, the company's own confidentiality obligations and its appetite for a data licensing conversation, which sit with the CEO, advised by the CFO and counsel.
The tree: five questions in order
Read the graphic from the bottom up: system owners first, the convener in the middle, the signer at the top. The same path in words:
- Who do you know? If it is the treasury manager or ERP administrator, ask who owns the cash application process end to end. The answer is usually the AR director or a shared services lead.
- Will the AR director convene? Ask whether they would sponsor an internal conversation about the company's exception history. If yes, they are the working contact. If no, stop; nobody else will carry it.
- Is cash application outsourced? If a shared service center or business process outsourcer applies cash and works deductions, find out who holds the case notes and under which contract. The company may need the outsourcer's cooperation, and the contract decides access.
- Do customer contracts restrict reuse? Remittances and deduction correspondence name customers and may fall under confidentiality terms. General counsel reviews this; the partner only notes that it is a question.
- Who approves? The CEO, with the CFO preparing the case and general counsel advising. Add a parent company or sponsor with consent rights where one exists.
Roles side by side
| Question | AR director | Treasury manager | Controller | CFO | General counsel |
|---|---|---|---|---|---|
| Where are remittances and cases stored? | Knows | Partly | Partly | Rarely | No |
| Which years and volumes exist? | Knows | Bank side | Ledger side | No | No |
| When does the cash application vendor contract end? | Often | Sometimes | Often | Yes | Sometimes |
| Do customer contracts restrict reuse? | No | No | Partly | Partly | Knows |
| Can convene the discussion? | Yes | No | Sometimes | Yes | No |
| Can approve a licensing discussion? | No | No | No | No; prepares the case | No; advises |
The approval itself sits with the CEO.
Side branches that need review
Customer remittances and correspondence. The company received them in its own business, but customers wrote them. Where EU law applies, the GDPR defines personal data as any information about an identified or identifiable person, including by reference to a name or identification number; a contact name on a remittance or a sole trader's payment qualifies. More often the issue is commercial confidentiality in the customer agreement.
Outsourced case work. If an outsourcer holds the case notes, check whose records they are under the services agreement. The business process outsourcing page covers that pattern.
Records under dispute. Deductions in active litigation or collections are left alone.
None of these ends the discussion. They shape scope, and SourceX wants to know about them early.
Two finance teams, two routes (Illustrative)
Fictional companies, invented for this page; not real cases.
| Step | 450-person manufacturer, in-house AR | 1,100-person distributor, outsourced cash application |
|---|---|---|
| First contact | Treasury manager from a bank connectivity project | ERP administrator from a system upgrade |
| Convener | AR director | Shared services lead, with the AR director |
| Case notes held by | Company's ERP case module | Outsourcer's ticket queue |
| Side branch | Confidentiality clauses in key customer agreements | Outsourcing contract on data access, plus customer agreements |
| Approver | CEO, with the CFO and general counsel | CEO, with the CFO and general counsel; outsourcer cooperation needed |
The manufacturer's route has one convener and one approver. The distributor's route adds an outsourcing contract check, which changes timing and possibly scope, not eligibility. In both cases the convener can describe years, volumes and systems from reports without opening a remittance. The system map gives them the vocabulary.
What waits for SourceX's rights review
Which records and years can be licensed after contract and privacy checks; whether remittances, settlements, cases and credits are all in scope and in what de-identified form; whether any buyer wants cash application exception histories; and whether an offer follows. Applying is not the same as a deal; see whether a company application leads to a licensing deal (it does not, by itself) and what happens after a company applies.
The introduced company needs 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. 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. Partners sign the Channel Partner Agreement before submitting; the first valid introduction within the 90-day window is credited when the company submits a verified application, and one partner is credited per company. Why data rights matter explains the review order, the referral brief template puts the answers on one page, and the ERP consultants page covers how systems advisors refer.
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 agreed to convene and the CEO is named as approver, register as a partner, confirm the company on who qualifies and read the program terms before you make the introduction.