Retail Products and Recovery

Management Information Systems

Read at your own pace. Use chapter practice to check your understanding.

Chapters and chapter contents
100%
Practise this chapter ↓

Last updated · By the Clerk2Officer editorial team · Report a correction

How to use this chapter

Understand why management needs MIS, trace figures back to source systems, identify misleading ratios, and practise choosing corrective actions. All case numbers are fictional; reported RBI dates are source-linked.

Official IIBF syllabus: Seven areas: main elements, organisational role, decision-making, banking uses, design, issues and remedial suggestions.

Important: Calculator activity and lesson checkboxes are demonstrations stored only on this page. The production site must connect syllabus progress to its authorised user database without overwriting historical results.
Lesson 01 · Main elements of MIS

MIS: meaning, scope and purpose

A Management Information System (MIS) is an organised arrangement of people, processes, controls, data and technology that turns operational records into information suitable for managerial action. A core banking system records transactions; an MIS selects, validates, groups, compares and presents those records for decisions. An attractive chart without a correct business definition, refresh time or accountable owner is not an effective MIS.

MIS: meaning, scope and purposeSTRATEGICTACTICALOPERATIONALInformation detail and user roles must match the decision
MIS: meaning, scope and purpose, visual summary and discussion prompt

What the manager should do: Ask: which decision will change after this report? If no decision is supported, simplify or remove the report.

Exam trap: A dashboard is one presentation layer of MIS, not a substitute for the complete information system.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 02 · Main elements of MIS

Data-information-insight-action ladder

Data are unprocessed observations such as account balances and transaction timestamps. Information adds meaning through definitions, aggregation and comparison. Insight explains patterns and plausible drivers; action assigns a decision, owner and deadline. Each stage requires validation. A percentage may be correctly calculated but misleading if the source uses a different date or scope.

From raw data to management actionDATAINFORMATIONINSIGHTACTIONExample: 40 complaints → ageing analysis → root cause → owner & deadline
Data-information-insight-action ladder: visual summary and discussion prompt

What the manager should do: A manager should separate what the data show from a causal explanation that has not yet been verified.

Exam trap: More raw data do not automatically mean better decisions.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 03 · Main elements of MIS

People, processes, data and technology

A reliable MIS has interdependent elements: data collectors and users; approved calculation rules; validated source data; supporting applications and infrastructure; and control mechanisms such as role-based access, audit trails and maker-checker approval. If the data are inaccurate, sophisticated analytics magnify the error. If people do not trust the reports, technically correct MIS may never influence decisions.

People, processes, data and technologyW1W2W3W4Illustrative trend only: always show unit and reporting period
People, processes, data and technology, visual summary and discussion prompt

What the manager should do: For every KPI specify an owner, an authoritative source, a formula, a refresh cycle and an escalation channel.

Exam trap: Software alone is not the whole MIS.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 04 · Role of Management Information Systems

Operational, tactical and strategic MIS

Operational MIS helps frontline staff handle daily exceptions, such as failed transactions and overdue follow-ups. Tactical MIS assists branch or regional managers with staffing, product conversion and periodic performance. Strategic MIS supports senior management in allocating capital, setting direction and reviewing long-term risk. The same banking activity can create all three views, but detail and frequency differ.

Three levels of banking MISSTRATEGICTACTICALOPERATIONAL
Operational, tactical and strategic MIS, visual summary and discussion prompt

What the manager should do: Match information granularity to decision authority: transaction-level details belong to authorised operations personnel, not every leadership dashboard.

Exam trap: A strategic dashboard is not merely a larger operational report.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 05 · Role of Management Information Systems

Routine, exception and on-demand reports

Routine reports follow an agreed schedule, such as daily service metrics or monthly branch reviews. Exception reports identify observations outside approved thresholds, such as unusually old unresolved complaints. On-demand reports answer authorised investigative questions. Trigger rules require context to avoid excessive false alarms; a sudden change can be caused by late batch arrival rather than genuine business stress.

Routine, exception and on-demand reportsSOURCEVALIDATEANALYSEACTTrace information from a trusted source to a decision
Routine, exception and on-demand reports, visual summary and discussion prompt

What the manager should do: Use prioritisation rules and documented thresholds so teams focus on actionable exceptions rather than alert fatigue.

Exam trap: An exception alert is a starting point for checking, not conclusive evidence of wrongdoing.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 06 · Role of Management Information Systems

MIS versus CBS, DSS, BI and regulatory returns

CBS is an operational system of record; MIS is the reporting and management-information layer. A Decision Support System (DSS) helps compare alternative actions or scenarios. Business Intelligence (BI) broadly covers data preparation and analytical visualisation. Regulatory returns are prescribed submissions governed by reporting instructions and controls. A single platform can support several functions, but their purposes and approval requirements are not interchangeable.

MIS versus CBS, DSS, BI and regulatory returnsSTRATEGICTACTICALOPERATIONALInformation detail and user roles must match the decision
MIS versus CBS, DSS, BI and regulatory returns, visual summary and discussion prompt

What the manager should do: Identify the output user and required assurance before selecting the system or treating figures as official.

Exam trap: MIS numbers must not be copied into regulatory returns without the prescribed reconciliation and validation.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 07 · Role of MIS in Improving decision making

MIS in decision-making: diagnosis to action

An effective management loop defines a problem, establishes a baseline, compares actual with target, explores drivers, evaluates alternatives, chooses an action and measures outcomes. Different choices may require different KPIs: customer acquisition uses conversion, service recovery uses complaint closure and branch efficiency may use cost-to-income. A KPI should have an explicit denominator, observation period and exclusion rules.

MIS in decision-making: diagnosis to actionMEASUREINTERPRETA calculated KPI requires a definition and business context
MIS in decision-making: diagnosis to action, visual summary and discussion prompt

What the manager should do: Use supporting indicators before intervention; do not reward speed if error rates worsen.

Exam trap: Correlation between two trends is not proof of causation.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 08 · Role of MIS in Improving decision making

Balanced scorecards for retail banking

A balanced banking scorecard combines business performance, risk, customer outcomes and operational controls. Deposits and loan growth alone can encourage unhealthy incentives. Adding asset-quality indicators, complaint outcomes, customer activation and audit exceptions reduces that risk. Weighting should be transparent and suited to the bank’s strategy rather than treated as a universal formula.

Balanced scorecards for retail bankingW1W2W3W4Illustrative trend only: always show unit and reporting period
Balanced scorecards for retail banking, visual summary and discussion prompt

What the manager should do: Check that an improvement in one KPI has not shifted cost or risk into another unit.

Exam trap: A weighted score can mask a critical control failure; risk limits must remain hard gates.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 09 · Role of MIS in Banking Industry

Branch and regional performance MIS

Branch MIS may include advances, deposits, CASA mix, overdue trends, cross-selling, service requests, digital usage and income/cost measures. Regional MIS rolls up branch records and allows peer comparisons. Aggregated ratios must be recomputed from totals, because an unweighted average of branch percentages can be wrong when branch sizes differ. A transparent reporting hierarchy is necessary for traceability.

Do not average bank ratios without weightsBRANCH A: 80 / 100 = 80%BRANCH B: 20 / 50 = 40%Correct regional ratio: (80 + 20) / (100 + 50)= 66.67%, not 60%
Branch and regional performance MIS, visual summary and discussion prompt

What the manager should do: Compare branches only after adjusting for relevant business mix and reporting definitions.

Exam trap: Ratios of totals and average of ratios are generally different.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 10 · Role of MIS in Banking Industry

Deposit and liability analytics

Deposit dashboards may show current, savings and term balances; inflows and outflows; active customer numbers; segment concentration and maturity profiles. A CASA ratio is (current + savings deposits) divided by total deposits, subject to the bank’s agreed balance definition and snapshot method. Deposit movement without pricing, tenure and behaviour may be of limited value for funding decisions.

CASA composition of deposit portfolioCA ₹20 crSA ₹60 crTerm ₹120 crCASA = (₹20 + ₹60) / ₹200 = 40%
Deposit and liability analytics: visual summary and discussion prompt

What the manager should do: For interpreting a trend, distinguish closing balances from average daily balances and do not combine them in one ratio.

Exam trap: A rise in CASA ratio can occur because term deposits fell; do not automatically label it organic growth.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 11 · Role of MIS in Banking Industry

Retail credit and asset-quality MIS

Credit MIS follows sanctioned and outstanding amounts, disbursement, repayment performance, overdue ageing, collateral review, collection actions and concentration. A management overdue-account ratio is not automatically the regulatory GNPA ratio. Regulations prescribe specific asset classification conditions; internal dashboard indicators should be labelled and reconciled accordingly.

Why overdue incidence is not GNPA24 / 800 loans = 3%NPA requires RBI normsOperational overdue monitoring ≠ regulatory asset classification
Retail credit and asset-quality MIS, visual summary and discussion prompt

What the manager should do: Separate account count, loan outstanding amount and borrower-level aggregation when comparing risk metrics.

Exam trap: Do not infer an account’s regulatory asset classification solely from a simplified dashboard ratio.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 12 · Role of MIS in Banking Industry

Customer service, complaints and digital-channel MIS

Service dashboards can show complaints received, resolved, outstanding, time-to-resolution, escalations, failed digital transactions and first-contact resolution. The numerator and denominator must cover the same scope and period. High closure percentages can conceal aged unresolved complaints, so trend, severity and ageing should be shown together. Digital adoption should be measured alongside outages and accessibility.

Complaint resolution needs ageingCLOSED 170OPEN 30CHECK AGEINGCohort closure: 170 / 200 = 85%; investigate old cases
Customer service, complaints and digital-channel MIS, visual summary and discussion prompt

What the manager should do: Display pending-age buckets and serious cases even when headline resolution is high.

Exam trap: Averages can hide extreme delays and should not replace ageing distributions.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 13 · Role of MIS in Banking Industry

Risk, compliance and audit MIS

Risk-oriented MIS highlights credit, operational, fraud and compliance exposures. Control-focused measures include unresolved audit observations, maker-checker overrides, access-review exceptions, repeated transaction failures and remediation age. Access should follow least privilege: business leaders can receive aggregate trends while sensitive individual details are restricted to designated officials. An MIS can support monitoring but cannot replace a mandated compliance or audit process.

Risk, compliance and audit MISW1W2W3W4Illustrative trend only: always show unit and reporting period
Risk, compliance and audit MIS, visual summary and discussion prompt

What the manager should do: Use drill-down to trace an exception to source records with audit logs, while limiting access to authorised roles.

Exam trap: A green dashboard does not demonstrate compliance if underlying control tests are incomplete.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 14 · Designing MIS for a Bank

Defining KPIs and a data dictionary

A KPI dictionary is a controlled catalogue of metric names, numerator, denominator, business exclusions, units, owner, source, update frequency and calculation version. It prevents branches from using similar labels for different numbers. When definitions change, management needs effective dates and restated comparison periods or clear break-in-series annotations.

KPI governance and definitionNUMERATORDENOMINATORPERIOD & SCOPEBusiness owner approves formula, source and reporting timestamp
Defining KPIs and a data dictionary, visual summary and discussion prompt

What the manager should do: Treat business glossary approval as a product requirement, not as optional documentation.

Exam trap: Without a common denominator definition, two accurate-looking percentages may be incomparable.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 15 · Designing MIS for a Bank

Source systems and data integration

Bank information may originate in CBS, loan origination, CRM, card switches, payment gateways, treasury systems and complaint platforms. Integration can use scheduled extracts or approved APIs; each feed needs an authoritative source, ingestion timestamp, unique keys, error handling and reconciliation. A source-system update can alter field names or business semantics, so versioned data contracts reduce downstream reporting errors.

Source systems and data integrationSOURCEVALIDATEANALYSEACTTrace information from a trusted source to a decision
Source systems and data integration, visual summary and discussion prompt

What the manager should do: Document source-to-target mapping and handle duplicate, missing or late-arriving records explicitly.

Exam trap: A joined dataset is not reliable merely because the SQL runs successfully.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 16 · Designing MIS for a Bank

Extract-transform-load and data lineage

ETL is the sequence of extracting data, transforming it according to defined rules, and loading it into a controlled reporting store. ELT loads before applying transformations. Data lineage documents how an output field was derived from upstream systems and rule versions. This allows a reviewer to trace a ratio back through calculations to underlying balances and identify where errors entered.

ETL and lineage in bankingSOURCE CBSVALIDATETRANSFORMPUBLISH MISLineage records the source, versioned rules and output
Extract-transform-load and data lineage: visual summary and discussion prompt

What the manager should do: Store calculation timestamps and validation results alongside the published figures.

Exam trap: A data warehouse is not a licence to ignore source-system reconciliations.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 17 · Designing MIS for a Bank

Quality dimensions and reconciliations

Data quality is multidimensional: completeness, accuracy, consistency, validity, timeliness and uniqueness all matter. A data set can be complete but inaccurate; a balanced aggregate can still hide duplicate records. Build automated tests on permissible values, mandatory identifiers, row counts, control totals and expected freshness. Exceptions should block or clearly label affected reports according to materiality.

Data lineage: reproduce the reported valueCBS BALANCESPRODUCT MAPMIS ₹650 CREvery aggregation should be traceable to source and exclusions
Quality dimensions and reconciliations: visual summary and discussion prompt

What the manager should do: Publish data-quality status and source snapshot time beside every significant dashboard.

Exam trap: Never silently substitute yesterday’s numbers into a report labelled “today”.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 18 · Designing MIS for a Bank

Dashboard design and visual communication

Effective dashboards answer specific questions quickly: show headline KPIs, a meaningful trend, peer comparison and high-priority exceptions with accessible drill-down. Axes, units and date ranges must be legible. Colour alone should not communicate status; also provide text, icons or patterns. Small-screen layouts should prioritise essential decisions over dense tables. Avoid decorative charts without analytical value.

Source reconciliation exceptionCBS ₹250 CROREMIS ₹248 CROREDifference: ₹2 crore = 0.8% of sourceInvestigate; 0.8% is not a prescribed tolerance
Dashboard design and visual communication, visual summary and discussion prompt

What the manager should do: Prefer a labelled line chart for a time trend, a ranked bar chart for branch comparison and a table for exact reconciliation values.

Exam trap: A 3D pie chart often makes modest differences harder to interpret.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 19 · Designing MIS for a Bank

Management hierarchy and access controls

MIS entitlements should align with operational responsibilities. A branch user may see authorised branch records; an area manager may see the region; specialised audit or risk staff may access approved controls data. Authentication, access reviews and audit logs reduce misuse. Masking customer identifiers and suppressing small cohorts can reduce unnecessary exposure of personal financial information.

Management hierarchy and access controlsDATAQUALITYACCURATETIMELYCOMPLETETRACEABLE
Management hierarchy and access controls, visual summary and discussion prompt

What the manager should do: Implement role-based and where needed attribute-based access, and test denial scenarios as rigorously as permitted access.

Exam trap: A valid login does not mean the user should be able to see every report.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 20 · Designing MIS for a Bank

MIS project life cycle and ownership

Design begins with a business decision and named report owner; proceeds through requirement workshops, approved KPI dictionary, source mapping, prototyping, data-quality checks, user acceptance, rollout and ongoing change management. A report without business ownership may become stale or misleading. Separate sign-off for business logic, IT implementation and information security provides accountability.

Least-privilege management MISBRANCH ROLEREGIONAL ROLERISK ROLEAccess differs by responsibility; mask customer-sensitive fields
MIS project life cycle and ownership, visual summary and discussion prompt

What the manager should do: Include historical restatement, rollback and audit-trail requirements in the initial design.

Exam trap: Successful software deployment is not equivalent to an approved management report.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 21 · Issues Related to Management Information System (MIS)

MIS pitfalls: silos, stale data and overload

Common failures include fragmented sources, inconsistent definitions, poor lineage, duplicate customer records, missing refresh alerts, delayed extracts, performance bottlenecks and too many metrics. Sometimes dashboards are technically available but unusable because business owners cannot explain them. A useful diagnosis separates source quality, transformation logic, report design, network performance and user training.

MIS pitfalls: silos, stale data and overloadSTRATEGICTACTICALOPERATIONALInformation detail and user roles must match the decision
MIS pitfalls: silos, stale data and overload, visual summary and discussion prompt

What the manager should do: Investigate business definitions before rewriting code or blaming one system.

Exam trap: A mismatch does not always indicate fraud or data corruption; it may be a scope difference.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 22 · Suggestions for Solution to MIS related Issues

Control remedies and data governance

Solutions include a bank-approved data dictionary, source ownership, automated reconciliation, maker-checker control for critical manual adjustments, scheduled refresh monitoring, data-quality scorecards, secure access reviews and periodic user feedback. Severe exceptions should be escalated and publication withheld or labelled where appropriate. Resolution effectiveness should be tested by recurrence rates, not simply by ticket closure.

Control remedies and data governanceMEASUREINTERPRETA calculated KPI requires a definition and business context
Control remedies and data governance, visual summary and discussion prompt

What the manager should do: Assign each data-quality exception a named owner, root cause, remediation date and proof of testing.

Exam trap: Fixing a report presentation cannot repair a broken upstream source.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 23 · Role of MIS in Improving decision making

Scenario lab: prioritise the right action

Decision-support simulations should encourage judgement, not automatic enforcement. Suppose a branch has high loan growth, worsening repayments and an older complaint backlog. The prudent next step is to validate data and assess credit and service causes, not simply celebrate disbursement volume. A dashboard should show trade-offs and allow managers to inspect related evidence before acting.

Problems → controls → evidenceSTALE DATAREFRESH ALERTAUDIT TRAILMonitor recurrence and prove the corrective action works
Scenario lab: prioritise the right action, visual summary and discussion prompt

What the manager should do: Use a narrative annotation that states the plausible issue, validation required, decision owner and follow-up date.

Exam trap: A dashboard should support human judgement, not claim a loan is fraudulent from a few KPIs.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Lesson 24 · Role of MIS in Banking Industry

Banking MIS case study: branch performance

Consider a branch with deposits of ₹250 crore, advances of ₹175 crore, CASA of ₹100 crore, 25 unresolved complaints and 700 active retail loan accounts. Its CD ratio is 70% and CASA mix is 40%. A dashboard that shows only these two ratios misses complaint age, credit performance and deposit-maturity concentration. A branch manager needs an integrated explanation and an action plan.

Banking MIS case study: branch performanceDATAQUALITYACCURATETIMELYCOMPLETETRACEABLE
Banking MIS case study: branch performance, visual summary and discussion prompt

What the manager should do: Interpret the three categories together: growth and funding, asset quality, and customer service.

Exam trap: Figures in this case are fictional teaching data, not a report about an actual bank.
Apply the control checkpoint

**Examination method:** First identify the relevant reporting population and period. Then identify the numerator, denominator, units and formula. Finally explain what decision the resulting information supports; do not infer statutory classification, compliance or causation from an illustrative operational ratio.

Lesson 25 · Issues Related to Management Information System (MIS)

Banking MIS case study: source mismatch

A region’s MIS reports 1,200 new retail accounts, while the source system shows 1,260. The apparent 60-account difference may stem from cut-off times, duplicate exclusion, rejected records, or mapping error. A disciplined investigation first checks periods and definitions, then reconciles individual records and documents the corrected figure and any restatement.

Banking MIS case study: source mismatchSOURCEVALIDATEANALYSEACTTrace information from a trusted source to a decision
Banking MIS case study: source mismatch, visual summary and discussion prompt

What the manager should do: Do not publish the 1,200 figure as final until the report owner applies an approved materiality and correction process.

Exam trap: Data accuracy, timeliness and reconciliation are separate control questions.
Apply the control checkpoint

**Control checkpoint:** Before a report is relied on, verify approved metric definitions, source timestamp, reconciliation position, access permission and the named reviewer. If the data are late or inconsistent, record the exception and escalate according to internal reporting policy.

Facts & Figures

7 November 2023: RBI issued IT Governance, Risk, Controls and Assurance Practices Directions, 2023; effective 1 April 2024 for specified entities. RBI
10 April 2023: RBI issued its Master Direction on Outsourcing of Information Technology Services. RBI
27 February 2024: RBI issued Master Direction on Filing of Supervisory Returns, distinguishing prescribed supervisory reporting from internal MIS. RBI

Worked figures (CASA, growth, complaints, CD ratios) elsewhere in this chapter are deliberately illustrative; none is a bank-level target or statutory tolerance.

Verified for this educational draft on 19 October 2026. Recheck the latest applicable RBI directions at publication.

Worked banking cases

Case 1: Regional credit-deposit ratio

Branch A has ₹80 crore advances and ₹100 crore deposits (80%); Branch B has ₹20 crore advances and ₹50 crore deposits (40%). Their simple mean is 60%, but combined CD is (80+20)/(100+50)×100 = 66.67%. Ratios must be recomputed from aggregated base figures.

Case 2: Report reconciliation

CBS deposits are ₹250 crore, but MIS is ₹248 crore for the agreed cutoff. Difference is ₹2 crore (0.8% of source). Check dates, product exclusions, duplication, mapping, and feed delays. No regulatory tolerance of 0.8% is implied.

CBS / CRMValidationReconciliationMIS publishMismatch → investigate sourcePublish only afterapproved checks
When validation fails, investigate rather than silently publish.

Case 3: Integrated branch scorecard

Deposits ₹250 crore, advances ₹175 crore, CASA ₹100 crore, 25 unresolved complaints, and 700 active retail loan accounts: CD is 70%, CASA is 40%. These two performance ratios alone cannot establish service quality or credit health. Evaluate overdue ageing and complaint severity too.

Animated MIS publishing lifecycle

Watch the six stages from extraction to governed publication. This is a conceptual sequence, not a representation of any particular bank's actual IT architecture.

Open animated teaching illustrationSix-step sequence: extract, validate, reconcile, resolve, approve and publish management information
Process animation; a text description is provided for accessibility.
Read the animation as text

1. Extract trusted source information. 2. Validate mandatory data and accepted values. 3. Reconcile source totals. 4. Resolve material mismatches. 5. Approve business definitions and access. 6. Publish with timestamp and audit evidence.

Interactive MIS Calculator Lab

Adjust figures and observe how denominator selection changes the management interpretation. Inputs and outputs are not connected to any bank.

CASA ratio (%)

CASA = 40%The denominator must include the relevant total deposits for the same date and reporting scope.

Credit-deposit ratio (%)

CD ratio = 70%This simplified management CD ratio is advances divided by deposits; use the bank-approved definition.

Regional CD ratio: avoid averaging percentages

Combined CD ratio = 66.67%; unweighted branch average = 60%Calculate from total advances and deposits; the average of branch ratios is generally incorrect.

Period-on-period growth (%)

Growth = 18%Use comparable definitions and periods; changing the customer cohort may distort growth.

Complaint cohort resolution (%)

Cohort resolution = 85%Do not mix old-period closures with new-period complaints without a stated definition.

Overdue-account incidence (%)

Overdue-account incidence = 3% (not GNPA)Management overdue incidence is not an RBI asset-classification or GNPA ratio.

New-account activation (%)

Activation = 70%Clearly define “activated” and the observation window.

Source-MIS reconciliation

Absolute difference = 2 crore; % of source = 0.8%Any tolerance must come from an approved bank policy, not this example.

Data completeness (%)

Data completeness = 95%Completeness is separate from accuracy and uniqueness.

Cost-to-income ratio (%)

Cost-to-income = 60%This simplified branch indicator uses the inputs provided; real MIS requires approved accounting definitions.

Average service turnaround time

Average turnaround time = 2.5 hours/caseAn average is not a percentile and can conceal very slow cases.

Fraud-alert precision (%)

Illustrative precision = 15%Illustrative alert precision is not a bank’s detection rate or a statement about confirmed criminal fraud.

MIS decision-path simulator

Choose a management situation to see the appropriate validation and escalation path.

First compare report timestamp, scope, product mapping and reconciliation. Assign data owner; hold or label an unreliable figure under policy. Do not quietly overwrite it.
LEARN THROUGH EXPLANATIONS

Chapter practice

This practice is separate from timed mock tests. Answers and explanations appear after you choose an option.

Your reading progress

Sign in to save your progress across devices.

Browse published timed tests for this paper