Module comparison and ownership

Requirements review v0.2 • 14 October 2026. All new Banking modules are proposed; no implementation or permission is approved by this map. A module is a business responsibility. An application is where a person uses it. An offering is the institution-specific bundle of permitted products, modules and channels. Start here explains those three layers with one bank and one NBFC example.

Module responsibilities and handoffs

Topic	Responsible module	Related module responsibilities
Branch structure and staff assignments	B01 records the branch; B02 assigns staff.	B34 checks transaction-specific authority, approvals and limits.
Customer verification, account opening and digital access	B04 verifies the party.	B06 opens a legal account; B35 verifies digital access.
Customer relationships and operating mandates	B05 presents the relationship.	B06 owns account holder/operating authority; B11 owns payment mandates.
Loan application and credit decision	B12 gathers and prepares the application/contract.	B13 records the credit decision; confirmed disbursement is recorded separately.
Loan servicing and collections	B14 calculates dues and applies verified receipts.	B16 manages overdue work; balance changes require verified servicing events.
Card issuance, funding and transaction processing	B17 owns the credential and activation.	Funding/credit eligibility comes from B18/B19/B20; B21 handles the transaction messages.
Ledger, settlement and reconciliation	B07 records the financial effect.	B21 records card clearing/settlement facts; B24 proves cross-source agreement.
Service cases, disputes and financial corrections	B27 records and resolves the service case.	B22 investigates transaction disputes; financial correction needs its own authority and confirmed posting.
Business-day processing and reporting	B31 coordinates dated jobs.	The product module calculates, B07 posts, and B29 prepares a governed report/filing.

Debit, prepaid and credit: the same card action, different money

The following are simplified fictional arithmetic examples with no fees, taxes, currency conversion, other holds or other transactions. They do not adopt actual limits or pricing.

Type	Source of spending capacity	Before an INR 1,000.00 authorisation	After reservation	After matching clearing
Debit B18	Linked deposit account	Ledger INR 5,000.00; available INR 5,000.00	Ledger stays INR 5,000.00; hold INR 1,000.00; available INR 4,000.00	Debit posts once: ledger INR 4,000.00; original hold resolves.
Prepaid B19	Confirmed loaded stored value	Value INR 3,000.00; available INR 3,000.00	Value stays INR 3,000.00; hold INR 1,000.00; available INR 2,000.00	Spend posts once: value INR 2,000.00; original hold resolves.
Credit B20	Approved revolving credit	Limit INR 50,000.00; used INR 0.00; available INR 50,000.00	Reserved INR 1,000.00; available INR 49,000.00	Used receivable INR 1,000.00; original hold resolves; available INR 49,000.00. Actual bill/due depends on adopted cycle and terms.

For all three, B17 supplies the card identity and B21 co-ordinates the network event. A failed/unknown authorisation does not justify a second debit. A matched reversal must resolve the original event under adopted rules.

Lending handoffs

The diagram shows responsibility handoffs. The execution sequence supports multiple B13 assessments requested by B12 before final accepted terms. Institution-approved state transitions and source ownership are required implementation inputs.

Module-by-module ownership directory

Organisation, customer and core records

Module	Own record	Result to inspect
B01 Institution and branch administration	Institution, region, branch and service-location records.	A versioned organisation structure with contacts, status and service routing.
B02 Staff identity and access	Staff identity, duty assignment, enrolment and staff session.	An active or revoked staff access record with effective scope and review history.
B03 Product and programme configuration	Product definition, programme and effective policy version.	An approved version that eligible operating modules can reference, or a blocked publication with reasons.
B04 Customer onboarding and KYC	Customer application, identity evidence and KYC review.	A verified, rejected or pending customer record with evidence and decision reasons.
B05 Customer relationships and servicing view	Party-to-product relationship and its source/freshness information.	A scoped view of linked products, roles and permitted servicing entry points.
B06 Account lifecycle and mandates	Account, holders, operating mandate, status and restriction.	A confirmed account state with attributable authority and retained history.
B07 Ledger and financial accounting	Journal, posting lines, balance reservation and accounting period.	A balanced, uniquely referenced financial effect or a pending/rejected posting.
B08 Savings current and overdraft servicing	Deposit servicing facts, accruals, charges and overdraft utilisation.	A traceable statement and correctly referenced account-service postings.
B09 Term and recurring deposits	Deposit contract, funding schedule, accrual and maturity instruction.	A confirmed deposit advice or maturity/closure result linked to its financial postings.
B10 Teller cash and vault	Till/shift, denominations, custody transfer and cash transaction.	Confirmed physical custody and financial entries that agree, or an owned discrepancy.
B11 Payments beneficiaries and mandates	Beneficiary, payment mandate, instruction and provider status.	A confirmed payment/return with original references, posting and reconciliation evidence.
B33 Cheque operations and clearing	Cheque range, instrument, stop instruction, clearing item and return.	A confirmed instrument disposition linked to its clearing/posting/settlement evidence.
B35 Customer digital identity and security	Customer digital identity, verified product link, factor/device and session/proof.	A scoped customer session or action proof, with attributable revocation and recovery history.

Lending

Module	Own record	Result to inspect
B12 Loan origination	Application, documents, offer, agreement and disbursement-readiness checklist.	An accepted, ready application handed to servicing, or a pending/rejected application with reasons.
B13 Credit underwriting and decisioning	Assessment inputs, policy version, decision, conditions and exception reasons.	A reproducible approved/declined/conditional credit decision.
B14 Loan servicing and repayment	Loan book, schedule, accrual, receipt allocation and servicing change.	Updated exact balances and statement, with linked payment/posting and correction evidence.
B15 Collateral and securities	Secured asset, evidence, valuation, encumbrance and release authority.	A traceable security position linked to the correct facilities and controlled release status.
B16 Collections and recoveries	Arrears queue, contact task, promise/dispute and recovery decision.	An attributable case outcome linked to confirmed servicing receipts or adjustments.

Cards and ATM

Module	Own record	Result to inspect
B17 Card programmes issuance and inventory	Card programme, tokenised card record, issuance order and inventory/delivery status.	A confirmed usable, blocked or replaced card credential linked to the correct funding product.
B18 Debit card operations	Debit-card account link, use controls and balance/hold relationship.	An eligible debit instruction against current available funds with linked hold/posting status.
B19 Prepaid cards wallets and PPI operations	Prepaid balance account, KYC/programme restrictions, load and redemption.	A confirmed stored-value change linked to funding, safeguarding and settlement evidence.
B20 Credit card accounts billing and servicing	Revolving credit account, limit, receivable, statement and allocation.	Current exposure, available credit and customer dues linked to accepted terms and postings.
B21 Card authorisation clearing and settlement	Network transaction, reservation reference/status, clearing match and settlement position. Monetary reservation remains in B07 or the selected funding book.	One traceable economic effect per accepted event, or an explicit unresolved exception.
B22 Disputes chargebacks and remediation	Dispute, evidence packet, network deadlines and adjustment decision.	An evidenced case outcome and any separately confirmed financial correction.
B23 ATM application and terminal operations	Terminal trust/health, session, dispense journal and cassette custody.	Confirmed dispense/debit evidence or an owned partial/unknown-dispense exception.

Cross-module controls

Module	Own record	Result to inspect
B24 Reconciliation and exception management	Source batch, match, exception, corrective evidence and sign-off.	A proven match or a named unresolved exception with an authorised resolution.
B25 Treasury liquidity and settlement positions	Liquidity position, counterparty/deal, maturity cash flow and funding instruction.	An approved institution funding position with confirmed settlement or explicit shortfall.
B26 Risk fraud AML and compliance	Signal, screening result, investigation case and authorised disposition.	A recorded case decision and any separately confirmed protective action or filing.
B27 Service requests and complaints	Case, assignment, correspondence, status and closure evidence.	A customer-visible response and traceable completion of the requested service or referral.
B28 Communications documents and consent	Template version, document, delivery attempt, preference and acceptance evidence.	The correct recipient can access the exact approved content and its delivery/acceptance status.
B29 Management and regulatory reporting	Report definition, source snapshot, run, export and submission evidence.	Reproducible scoped figures with completeness/lineage and controlled submission status.
B30 Banking APIs integration and data health	API contract, integration scope, source receipt, callback and correction lineage.	Validated scoped data or instruction acknowledgement with reliable status/finality semantics.
B31 Business date EOD and scheduled operations	Business calendar, cycle/run, dependency checkpoint and sign-off.	A verified completed business-date cycle or a blocked run with recoverable checkpoints.
B32 Security audit deployment and resilience	Security control evidence, audit event, incident, recovery exercise and release packet.	Verified protective controls and accountable accepted or blocked release/recovery decisions.
B34 Approvals limits and operational controls	Bound action intent, approval decision, consumed limit and exception authority.	An executable or rejected/expired intent with attributable independent decisions.

Implementation and documentation status

State	Meaning here
Documentation available	Definitions, examples, diagrams, features, journeys and required implementation inputs are documented.
Legacy reuse candidate	Existing banking_app capabilities require implementation review before reuse; new-module acceptance remains separate.
Proposed / implementation not started	Every B01–B35 module needs an agreed execution packet before new-project coding.
Locally tested / bank accepted / released	Separate evidence milestones, not statuses conferred by a published documentation page.

Each module’s Current implementation and reuse section records legacy evidence. Required implementation inputs records the institution policies and contracts needed for implementation. The delivery gates define acceptance.

Reference and design ownership

M2P publicly groups origination, servicing, collateral and collections within its lending suite. That is a reference for explaining modular responsibilities, not an adopted architecture or provider contract. The ownership boundaries above are this project’s proposed design. M2P core lending suite and reference basis.

Understand the modules

Core and operations modules

Lending modules

Cards and ATM modules

Control and delivery modules

Module comparison and ownership

Module responsibilities and handoffs

Debit, prepaid and credit: the same card action, different money

Lending handoffs

Module-by-module ownership directory

Organisation, customer and core records

Lending

Cards and ATM

Cross-module controls

Implementation and documentation status

Reference and design ownership

​Module responsibilities and handoffs

​Debit, prepaid and credit: the same card action, different money

​Lending handoffs

​Module-by-module ownership directory

​Organisation, customer and core records

​Lending

​Cards and ATM

​Cross-module controls

​Implementation and documentation status

​Reference and design ownership

Module responsibilities and handoffs

Debit, prepaid and credit: the same card action, different money

Lending handoffs

Module-by-module ownership directory

Organisation, customer and core records

Lending

Cards and ATM

Cross-module controls

Implementation and documentation status

Reference and design ownership