This page is for the specialists who see these logs every week without owning them: fractional controllers, AP automation implementers, audit and advisory staff, and operators who run outsourced finance teams. You know where the exception queue lives and how good the notes are. The question you can usefully settle before an introduction is narrower: whose work is in it?
What a finance exception log holds, in plain terms
An exception is any transaction the normal rule could not clear on its own. Typical examples: an invoice that does not match its purchase order or goods receipt, a possible duplicate payment, a payment held for review, cash that cannot be applied to an open invoice, a bank reconciliation item that will not tie out, an expense outside policy, or a manual journal entry that overrides a control.
Each entry tends to carry the same parts: the trigger the system raised, a reviewer's note on what was wrong, a reason code, an approval, the correcting entry and some attached evidence. The parts that record judgment (why the reviewer decided as they did, who approved a departure from the rule and what fixed it) are why the exception-handling guide treats hard cases as useful evaluation material. They are also the parts most likely to be the company's own. The accounts payable side alone is described in more depth on the AP exception handling page.
Five kinds of author inside one exception record
The same entry can hold material from five kinds of author. The third column is a starting assumption to test, not a conclusion.
| Layer | Usually written or supplied by | Starting assumption about whose it is | The question that tests it |
|---|---|---|---|
| Flag or match result | Rules running in the ERP or an AP automation platform | The company's configuration, inside someone else's software | What do the platform terms say about generated data? |
| Reviewer note and reason code | Company staff, contractors or an outsourced provider's team | The company's, if its employees wrote it | Who typed it, and under which contract? |
| Approval and correcting entry | Company managers | The company's | Does the approval trail live in a company system? |
| Attached invoices, statements and remittances | Vendors, customers and banks | Other parties' documents, possibly under confidentiality terms | Which agreements govern them? |
| Expense receipts and card details | Employees and card issuers | Personal and payment data with its own limits | How much of it sits inside the log? |
A sixth source sits outside the company's systems entirely: the outside accountant's file. The AICPA's Records Requests interpretation separates client-provided records, which it describes as accounting or other records belonging to the client that the client gave the accountant, from the accountant's working papers. It lists audit programs, analytical review schedules and statistical sampling results among those working papers, and includes analyses and schedules the client prepared at the accountant's request. It says working papers "are the member's property". So an exceptions analysis the company's staff built for the auditors may sit in the auditor's file as the auditor's working paper. The company's own source system is the place to look; the auditor's file is not part of an introduction.
The finance-exception ownership question set
Twelve questions in four groups. Ask them through the person who runs the process, with the CEO's knowledge, and record each answer with a date and its source. None of them needs a file, a screenshot or a login.
| Group | Question | An answer that helps | An answer that pauses |
|---|---|---|---|
| Origin | 1. Who typed the resolution notes and reason codes: employees, contractors or a provider's staff? | Employees, in a company system | A provider's staff, under a contract nobody has read |
| Origin | 2. Which parts did software generate, and from whose rules? | Rules the company configured and can explain | Vendor scoring nobody at the company understands |
| Origin | 3. In which system, since when, and roughly how many exceptions a year? | Several years in one system | A few months, scattered across inboxes |
| Third parties | 4. What is attached: invoices, statements, contracts, remittances? | Notes that stand on their own | Attachments that carry all the substance |
| Third parties | 5. Do vendor or customer agreements limit how their documents are used? | Standard terms that counsel can check | Strict confidentiality on the largest accounts |
| Third parties | 6. Do bank, card or remittance details sit inside entries? | References only | Full account or card numbers throughout |
| People and money | 7. Do entries name employees or include expense receipts? | Business entries only | Personal expense detail in most entries |
| People and money | 8. Is it the company's own money, or client funds it administers? | The company's own payables and receivables | Client or trust funds |
| People and money | 9. Were any entries part of a dispute, investigation or claim? | Routine exceptions | An open dispute or a legal hold |
| Contracts and copies | 10. What does the AP or expense platform contract say about the company's data? | Counsel has read it and the company keeps its data | Nobody knows |
| Contracts and copies | 11. Does the best analysis live only in an outside accountant's file? | The company's own system is the source | Only the auditor's working papers have it |
| Contracts and copies | 12. Has any of it been licensed or shared for AI training before? | Never | Yes, which puts that material out |
Question 12 is a hard stop rather than a review item: SourceX's suppliers confirm their data has not been licensed for AI training before. Questions 5, 6, 7 and 8 map onto SourceX's own screening test, which asks whether the company can license the material "without breaching client confidentiality, employee privacy or third-party contracts."
Original work, mixed content and an open case (Illustrative)
Illustrative. Generic companies and invented facts; no outcome implied.
1. Original work. A 420-person industrial distributor runs its exception queue in its own ERP. Since 2016 its in-house AP team has logged price and quantity variances with a reason code, a reviewer note, an approver and the correcting entry, roughly 9,000 a year by the controller's estimate. Vendor invoices are attached. The notes, codes and approvals are the company's work; the invoices are described as a separate layer for rights review. The controller explains the process, and the CEO, who wants the conversation, is the person introduced.
2. Mixed third-party content. A 160-person property manager pays building owners' bills from client trust accounts. Its exception log is mostly owners' invoices, tenants' disputed charges and bank lines from client accounts. Most of the substance belongs to clients, and SourceX's screening page lists material that belongs to clients rather than the company as usually not a fit. The log does not carry an introduction. The firm's own procedures and internal approval records might; that is a different conversation with the CEO.
3. An uncertain ownership case. A 95-person freight company moved its accounts payable to an outsourced provider in 2021. Since then the provider's staff have written every exception note in the provider's platform, and the company has read-only access. Before 2021, its own clerks wrote the notes in its old ERP. The pre-2021 history is the clear part. The later notes wait until counsel reads the services contract's data and intellectual property clauses. The CEO decides whether a conversation about the clear part is worth having now.
Tracing the owner and the origin without opening a file
Three people answer three different questions. The person who runs the process (the controller, AP manager or outsourced team lead) knows the systems, the years and who writes what. Counsel reads the contracts behind questions 5, 10 and 11. The CEO decides whether the company discusses licensing at all and signs for it; a controller's enthusiasm is not authorization.
Origin matters to the eventual user as well as to SourceX. NIST's AI Risk Management Framework asks organizations to map the legal risks of an AI system's components, "including the use of third-party data or software," and to document "risks of infringement of a third party's intellectual property or other rights." A log where every layer has a known author is easier for anyone downstream to account for. A log where nobody knows who typed the notes is harder, whatever its quality.
Fit facts still come first: 50+ full-time employees at the company's peak, contractors excluded, documented operating history, the rights to license and an authorized CEO. 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.
A bounded note you can send
Keep the first written ask to metadata the company is willing to state. A note to the CEO, or to the controller for the CEO, can carry five lines:
- The system that holds the exception history, and the year it starts.
- A rough count of exceptions per year.
- Who writes the notes: employees, contractors or a provider.
- The kinds of documents attached, named by type, never sent.
- Whether the CEO would like a conversation with SourceX.
Ask for answers in a reply, not attachments. If someone offers an export "to show you what it looks like", decline it; partners never hold client records, and the company describes its own material. The cash application exceptions route shows who usually convenes such a conversation, and purchase order mismatch examples show one exception type in detail.
Limits of an ownership question set
- Answers are claims. Each answer is someone's account, dated. It can be wrong, and only SourceX's rights review and the company's counsel can test it.
- Contracts decide, and they vary. Platform terms, provider agreements and vendor confidentiality clauses differ; the question set finds them, it does not read them.
- Quality and demand are separate. A log can pass every ownership question and still not match a current program.
- Advisors carry duties. Accountants, consultants and outsourced providers have their own confidentiality obligations to the client; the accountants page covers the program from that side.
- No outcome data. SourceX has not published how often finance exception records lead to introductions or licenses. Log each question set you complete, its date and whether the CEO agreed to a conversation; those figures are not yet published.
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 questions show a log whose core layers the company's own staff wrote and a CEO who wants to talk, register as a partner, compare the company's facts with who qualifies and read the terms before you send the bounded note. For context on record types, see golden trajectories versus ordinary logs, keeping ownership while licensing and the finance stack redesign guide for fractional CFOs; more specialist guides are in the guides hub.