A merchant underwriting decision is easier to explain, audit and revisit when its underlying facts and outstanding conditions are recorded together. A brief verdict without supporting context can leave the next reviewer wondering whether a document was received, a risk factor was accepted, or an approval was conditional.
Separate evidence from the decision
Start by listing the information that was actually available at the time of review. This could include the submitted application, ownership information, processing history when relevant, business model, product or service details, and requested processing parameters. Identify the source and date of material evidence. Mark unavailable information as pending rather than assuming it was reviewed.
Record the rationale in plain language
For each material observation, write what was found, why it matters under the organization’s documented criteria, and what follow-up (if any) is needed. Avoid vague labels such as “looks risky” without citing a specific fact. Internal risk classification and final decisions should follow your applicable policy, not a general-purpose template.
Observation: Requested processing volume differs from the amount supported in submitted records. Evidence: Application dated October 1 and supplied processing statements. Action: Request clarification and any supporting documentation. Status: Pending reviewer follow-up.
Make conditions actionable
If an application is approved subject to conditions, do more than attach a note saying “conditional.” Record the specific condition, its owner, due date or review point where applicable, evidence required to resolve it, and the person or role authorized to confirm completion. Distinguish pre-activation requirements from items monitored after activation.
A practical decision-log structure
- Application reference: a stable record identifier and review date.
- Evidence reviewed: source, receipt date, and key gaps or inconsistencies.
- Decision and rationale: outcome as determined under the applicable underwriting policy, plus material reasons.
- Conditions and follow-ups: requirement, owner, target timing and status.
- Approvals and changes: the appropriate decision authority and any subsequent amendments.
- Closure: when each condition was verified, with reference to supporting evidence.
Review the record before handoff
Confirm that a new reviewer could tell which information was known on the decision date, which questions remained open, and whether the outstanding requirements are measurable. Keep an amendment history instead of overwriting earlier rationale; this makes later periodic reviews and quality assurance more useful.
Need an editable starting point?
MintedTools has a published Underwriting Decision & Approval Conditions Tracker ↗ on Flevy. The Flevy workbooks section also links to periodic review, portfolio monitoring and underwriting QA templates. These are workflow aids, not substitutes for your organization’s underwriting standards, legal review or internal controls.