13.7 Offer and sanction

User stories

• As a borrower, I want to accept the offer with clear terms.
• As an analyst, I want to generate a sanction memo automatically from the decision.
• As a supervisor, I want to approve sanction within the matrix.

API requirements

• POST /offers, GET /offers/{id}, POST /offers/{id}/accept.
• POST /sanctions, GET /sanctions/{id}.

Data model

• offer, sanction.

UI screens

• Borrower: offer summary screen with accept / decline.
• Analyst / supervisor: sanction memo + approval.

Backend services

• Offer service.
• Sanction service.

External integrations

• KFS generation (downstream).

Test cases

• Offer expiry enforced.
• Acceptance triggers sanction.
• Sanction approval triggers documentation.

Edge cases

• Offer accepted after expiry — re-issue.
• Conditions not yet met — sanction held.
• Sanction approved by unauthorised user — block.

Acceptance criteria

• Offer → acceptance → sanction flow in single session for repeat borrowers.
• Sanction memo PDF generated and archived.