The agent drafts the memo; the underwriter owns it. At depth 1 the agent reads the file, spreads the financials, summarises the score and tests each policy rule. At depth 2 it drafts every section in your template with each figure cited. The underwriter rewrites what they disagree with and makes the decision; the agent never recommends approval.
What is a credit memo, and who owns it?
A credit memo is the document an underwriter or credit committee relies on to decide a lending request. It sets out who the borrower is, what they want and why, how they will repay, what security supports the loan, what could go wrong and which policy rules the request meets or breaks. A good memo lets someone who has never met the borrower make a sound decision.
The underwriter owns the memo once it reaches them. In many banks the relationship manager or a credit analyst prepares it first. Either way, the decision belongs to whoever holds the lending authority. The agent replaces the hours of gathering and formatting, not the judgement.
What are the steps?
- Agent, depth 1: reads the file. Application, financial statements, bank statements, valuations, the bureau report, prior memos for existing customers.
- Agent, depth 1: spreads the numbers. Income statement and balance sheet into the bank's template, with ratios. Each figure points to its page in the source.
- Agent, depth 1: reports the score. It states the score your credit scoring model produced and the main factors the model returns. It does not re-score or explain the score in its own terms.
- Agent, depth 1: tests policy. Each lending policy rule that applies is listed as met, not met or exception required, with the evidence.
- Agent, depth 2: drafts the memo. Borrower, purpose, repayment source, security, risks, policy position. The risks section is mandatory and comes before any mitigants.
- Person, underwriter: edits and decides. Approve, decline, approve with conditions, or refer.
- Agent, depth 2: drafts a referral note when the request sits outside the underwriter's mandate, using the bank's credit referral note template.
- Agent, depth 1: records the edits. What the underwriter changed, section by section.
| Step | The agent does | Depth | Stays with a person |
|---|---|---|---|
| Read file | Reads all documents | 1 | Requesting more |
| Spread | Enters figures with sources | 1 | Adjustments to figures |
| Score | Reports model output | 1 | Weighing the score |
| Policy | Tests each rule | 1 | Granting exceptions |
| Draft | Writes memo sections | 2 | Every conclusion |
| Decide | Nothing | None | Approve, decline, conditions |
| Referral | Drafts referral note | 2 | Sending it up |
Which controls apply, and what evidence do they leave?
Citation for every figure. No number appears in the memo without a source reference. The evidence is the memo itself: a reviewer can click through from any figure to the page it came from.
Provenance labels. Your own account data is sealed. Accounts and payslips supplied by the borrower are declared. Bureau data is external. The memo shows the class next to key figures, so an underwriter knows which numbers rest on the applicant's word.
No recommendation field. The template the agent fills has no "recommend approve" slot. The agent describes; the underwriter concludes. Any draft text that reads as a recommendation is caught at certification under the scope gate.
Edit log. Every change the underwriter makes is filed. This is how you learn where the agent is weak, and it is evidence that a person engaged with the memo rather than signing it unread.
Bureau access as a separate grant. Pulling the bureau report is its own capability, with recorded consent. Whether an agent can run a credit check is answered capability by capability, not by the memo grant.
What should you measure?
- Sections rewritten by underwriters. Track by section. Rewrites of the risks section matter most.
- Policy breaches the underwriter found that the agent missed. Each one is a certification case for the next run.
- Time from complete file to memo ready.
- Memos returned for missing evidence.
- Decisions reversed on later review where the memo was agent-drafted, compared with those that were not.
Where does it usually go wrong?
Advocacy creep. Memos drift into sales documents. "Strong management team with a proven track record" is a claim, not a fact. The agent should write only what the evidence shows, and leave character judgements to the RM and underwriter.
Invented mitigants. Asked to list mitigants, a model will find some. "Personal guarantee provides comfort" is only true if the guarantor has means. Each mitigant must cite evidence, or it is left out.
Spread errors that propagate. One misread figure changes every ratio. The agent should reconcile the spread back to the totals in the statements and flag any line it could not read with confidence.
Prior memo bias. For an existing customer, the agent reads the last memo and repeats its view. Mark what is carried forward, as you would in annual credit reviews.
Memo before file. A memo drafted from an incomplete file looks finished and hides the gap. The file should pass completeness checks first, which is the job of preparing applications in the origination system.
Where Pryme fits
In Pryme, memo drafting is certified through Attest on your own past files, scoring every section against your underwriters' final versions. The grounded gate checks that each claim traces to a source; the scope gate checks that the agent stops short of a recommendation. The broader limits are in AI agents in banking.
Questions people ask
Should underwriters see the agent's draft or a clean version?
They should see the draft, clearly marked as agent-prepared, with sources visible. Hiding where the text came from makes it harder to challenge.
Can the agent draft the decline reasons?
It can draft them from the underwriter's decision, using the policy rules and evidence on file. The underwriter confirms they are accurate, because decline reasons may have to be given to the applicant.
Does the agent need to know the bank's risk appetite?
Yes, as written policy it can test against. It should not infer appetite from past decisions, because that would turn habit into rule.