Skip to main content
Review draft • 14 October 2026 • New Banking project • Proposed, not built.

​
Definition and responsibility

Cheque operations manage physical cheque instruments and their clearing/return lifecycle. Issuing a cheque book does not debit an account. A stop-payment request and a cheque already presented for clearing need separate confirmed states. Read the module comparison map for the whole platform and the glossary for shared terms. Planned operating duties: Customer; cheque operations; branch officer; clearing finance. The institution owns rules and authority; this specification grants none.

​
Worked Indian example

Use the four stages below to distinguish the initial facts, the action to test, confirmed completion and the alternate result. This example exercises this module’s responsibility; related modules still own the handoffs listed above. Fictional illustration, not seeded data or approved policy. CHQ-001 / ACC-001 / INR 5,000.00.

​
Module flow diagrams

Read top to bottom: rectangles describe actions/outcomes; diamonds describe decisions. Follow denial and unknown-result routes as well as success. Each diagram matches its numbered journey below; a request acknowledgement does not prove final completion.

​
Flow 1: Request book to reconcile statement

​
Flow 2: Report lost cheque to notify

​
Required features

Planned functionality is listed below. Implementation requires confirmed field definitions, permissions, state transitions and product economics for the selected offering.

​
Required configuration

Instrument numbering; permitted accounts; positive-pay/proof rules; cutoff; returns; stop authority; fees. Use approved, effective-dated versions; bind each sensitive intent to its original terms and approval. Missing required evidence or policy blocks the dependent action.

​
End-to-end journey 1

Request book → verify account/mandate → issue and deliver → capture permitted instrument details → present to clearing → confirm paid or returned → reconcile statement.

​
End-to-end journey 2

Report lost cheque → verify instrument/account authority → submit stop → confirm effective status → handle any already-paid/clearing conflict → notify. A request acknowledgement is not a final financial/security result. Reconcile the original reference rather than blindly retrying after an uncertain response. Corrections preserve original history.

​
Interfaces and data dependencies

Account/mandate; clearing/image/status contracts; instrument identity; stop finality; return and settlement files. Confirm stable institution/resource IDs, freshness, completeness, status/finality, correction ordering and exact money representation. Web/mobile/ATM must not duplicate policy calculations or widen authority.

​
Current implementation and reuse

New Banking project: not built. No operational cheque book, stop-payment or clearing implementation exists. Reviewed legacy feature boundary: No operational module found.

​
Acceptance criteria and exception scenarios

Stop races with clearing; duplicated presentment; signature mismatch; already paid instrument; wrong cheque range. Verify permitted success, foreign institution/branch/customer denial, current revoked authority, stale state, concurrent/repeated actions, outages/unknown outcomes and redacted audit. Test exact book/counter effects where applicable and safe list → detail → action → result → return navigation. Apply shared journeys and the scenario matrix.

​
Required implementation inputs

Status: Pending institution confirmation. Cheque services, clearing contracts, action proof and effective stop-payment rules. Module register · Decision register