Common Prerequisites

Access Prerequisites

• You must have a valid login account and role assignment.
• Your role must include permission for the target action.
• Your branch assignment must be correct (for manager and staff users).

Data Prerequisites

Before transaction and payment workflows, ensure:

• Customer exists with unique Civil ID.
• Civil ID front and back images: upload whenever your branch policy requires them (the system stores secure URLs; onboarding is strongest when both sides are on file).
• Daily gold price is available for the working date (needed for valuation, risk, and many releases).
• Branch is active.

Operational Prerequisites

• Use the correct payment, release, or closure date. The system rejects future-dated payments and dates before interest has started accruing for that loan.
• Confirm whether the transaction belongs to your branch before you expect to fully close it from your terminal—cross-branch collection is fine, but closure must be recorded at the owning branch.
• For every posted payment, prepare a reference number (receipt / bank ref / internal ticket). It is required, must be non-empty, and cannot be reused for the same loan (protects against double posting).
• For any discount, prepare a mandatory reason (required when discount amount is greater than zero).
• For AUCTION transactions: do not attempt a normal payment—the system blocks it. Use the status and branch policy for what happens next.

Financial Prerequisites

• Understand that payment allocation is interest first (including any carried unpaid interest), then principal.
• Know that first-month full closure uses special minimum interest rules (15-day and 30-day windows as applicable).
• Confirm transaction status is ACTIVE before payments and releases (CLOSED and AUCTION are not payable in the normal flow).

Security and Audit Notes

• Every financial action is logged permanently.
• Payment deletion is not allowed.
• Correction should be done through adjustment entries, not record removal.