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.
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.
What the manager should do: Ask: which decision will change after this report? If no decision is supported, simplify or remove the 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.
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.
What the manager should do: A manager should separate what the data show from a causal explanation that has not yet been verified.
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.
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.
What the manager should do: For every KPI specify an owner, an authoritative source, a formula, a refresh cycle and an escalation channel.
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.
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.
What the manager should do: Match information granularity to decision authority: transaction-level details belong to authorised operations personnel, not every leadership dashboard.
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.
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.
What the manager should do: Use prioritisation rules and documented thresholds so teams focus on actionable exceptions rather than alert fatigue.
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.
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.
What the manager should do: Identify the output user and required assurance before selecting the system or treating figures as official.
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.
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.
What the manager should do: Use supporting indicators before intervention; do not reward speed if error rates worsen.
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.
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.
What the manager should do: Check that an improvement in one KPI has not shifted cost or risk into another unit.
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.
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.
What the manager should do: Compare branches only after adjusting for relevant business mix and reporting definitions.
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.
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.
What the manager should do: For interpreting a trend, distinguish closing balances from average daily balances and do not combine them in one ratio.
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.
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.
What the manager should do: Separate account count, loan outstanding amount and borrower-level aggregation when comparing risk metrics.
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.
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.
What the manager should do: Display pending-age buckets and serious cases even when headline resolution is high.
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.
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.
What the manager should do: Use drill-down to trace an exception to source records with audit logs, while limiting access to authorised roles.
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.
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.
What the manager should do: Treat business glossary approval as a product requirement, not as optional documentation.
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.
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.
What the manager should do: Document source-to-target mapping and handle duplicate, missing or late-arriving records explicitly.
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.
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.
What the manager should do: Store calculation timestamps and validation results alongside the published figures.
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.
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.
What the manager should do: Publish data-quality status and source snapshot time beside every significant dashboard.
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.
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.
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.
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.
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.
What the manager should do: Implement role-based and where needed attribute-based access, and test denial scenarios as rigorously as permitted access.
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.
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.
What the manager should do: Include historical restatement, rollback and audit-trail requirements in the initial design.
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.
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.
What the manager should do: Investigate business definitions before rewriting code or blaming one 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.
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.
What the manager should do: Assign each data-quality exception a named owner, root cause, remediation date and proof of testing.
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.
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.
What the manager should do: Use a narrative annotation that states the plausible issue, validation required, decision owner and follow-up date.
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.
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.
What the manager should do: Interpret the three categories together: growth and funding, asset quality, and customer service.
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.
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.
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.
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
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.
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 illustration

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 (%)
The denominator must include the relevant total deposits for the same date and reporting scope.Credit-deposit ratio (%)
This simplified management CD ratio is advances divided by deposits; use the bank-approved definition.Regional CD ratio: avoid averaging percentages
Calculate from total advances and deposits; the average of branch ratios is generally incorrect.Period-on-period growth (%)
Use comparable definitions and periods; changing the customer cohort may distort growth.Complaint cohort resolution (%)
Do not mix old-period closures with new-period complaints without a stated definition.Overdue-account incidence (%)
Management overdue incidence is not an RBI asset-classification or GNPA ratio.New-account activation (%)
Clearly define “activated” and the observation window.Source-MIS reconciliation
Any tolerance must come from an approved bank policy, not this example.Data completeness (%)
Completeness is separate from accuracy and uniqueness.Cost-to-income ratio (%)
This simplified branch indicator uses the inputs provided; real MIS requires approved accounting definitions.Average service turnaround time
An average is not a percentile and can conceal very slow cases.Fraud-alert precision (%)
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.
25 Original MCQs, instant answers and explanations
Q01. Which statement best describes a bank MIS?
Correct answer: B. MIS combines data, processes, controls, technology and users to support management decisions; a transactional ledger alone does not supply this complete function.
Q02. The most appropriate first question when designing a new MIS report is:
Correct answer: C. MIS design begins with a business decision and user need; visual styling, export options and access follow from that requirement.
Q03. A bank CBS primarily differs from MIS because the CBS:
Correct answer: A. CBS acts as a transaction-processing system of record. MIS extracts and validates information for operational, tactical and strategic management.
Q04. Which is an example of an exception report?
Correct answer: D. Exception MIS draws attention to items breaching predefined, business-approved limits, enabling prioritised follow-up.
Q05. A branch has CA ₹25 crore, SA ₹75 crore and total deposits ₹250 crore. CASA ratio is:
Correct answer: B. CASA = (25 + 75) ÷ 250 × 100 = 40%. Use comparable snapshots and definitions for each balance.
Q06. Branch A: advances ₹80 crore, deposits ₹100 crore. Branch B: advances ₹20 crore, deposits ₹50 crore. Combined CD ratio?
Correct answer: C. Combined advances = ₹100 crore and combined deposits = ₹150 crore. CD ratio = 100 ÷ 150 × 100 = 66.67%; avoid the unweighted mean of branch ratios.
Q07. A portfolio has 30 accounts with missed instalments among 1,000 active accounts. What is the simplified account-level overdue incidence?
Correct answer: A. Overdue-account incidence = 30 ÷ 1,000 × 100 = 3%. It must not be called an RBI GNPA ratio.
Q08. Which attribute most directly answers whether yesterday’s feed has been received on time?
Correct answer: D. Timeliness measures whether required records or reports are available within the agreed freshness window; accuracy and completeness test different aspects.
Q09. A metric dictionary should define:
Correct answer: B. Clear business definitions and ownership make KPI calculations reproducible and comparable across branches and time periods.
Q10. The main benefit of data lineage is that it:
Correct answer: C. Lineage connects the source, transformations and output, allowing users to investigate apparent mismatches and reproduce metrics.
Q11. A report shows source deposits of ₹250 crore versus MIS ₹248 crore. Absolute difference?
Correct answer: A. Absolute reconciliation difference = |250 − 248| = ₹2 crore; the bank’s approved materiality determines the required escalation.
Q12. The same difference as a percentage of source deposits is:
Correct answer: D. Difference percentage = 2 ÷ 250 × 100 = 0.8%. This is a worked example, not a prescribed RBI reporting tolerance.
Q13. Which MIS approach most respects customer confidentiality?
Correct answer: B. Role-based least-privilege access, masking and traceable access logs limit exposure of unnecessary personal data.
Q14. A regional MIS has 100 complaints received in a defined cohort, with 82 resolved from that cohort. Cohort resolution rate?
Correct answer: C. Using a consistent cohort denominator, 82 ÷ 100 × 100 = 82%. Old cases closed during the period must not be mixed without a clear definition.
Q15. Why is an average of branch percentages often misleading for a region?
Correct answer: A. An unweighted mean gives a small branch the same influence as a large branch. Aggregate the numerators and denominators, then recompute the regional ratio.
Q16. The best first action when CBS and MIS account counts differ is:
Correct answer: D. Cut-off time, unique-customer versus account counts and exclusions often explain apparent mismatches; verify those before making conclusions.
Q17. Which MIS is best suited to a branch operations team handling today’s reversals?
Correct answer: B. Operational MIS provides granular and timely exception information for frontline processing, such as pending reversals and failed items.
Q18. Which statement about a green compliance dashboard is correct?
Correct answer: C. A dashboard can summarise test results or exceptions, but underlying control evidence, scope and completeness require independent assurance.
Q19. A service team resolved 180 out of 240 cases in a consistent reporting cohort. What is the closure rate?
Correct answer: A. 180 ÷ 240 × 100 = 75%. The numerator and denominator must use the same cohort and closure definition.
Q20. The RBI IT Governance, Risk, Controls and Assurance Practices Directions, 2023 took effect on:
Correct answer: D. RBI issued the directions on 7 November 2023, with commencement specified as 1 April 2024. Applicability follows the directions.
Q21. Which option illustrates management by exception?
Correct answer: B. Management by exception concentrates attention on meaningful departures from agreed thresholds, supported by validation and escalation.
Q22. An MIS shows current deposits ₹30 crore, savings ₹45 crore and term ₹75 crore. CASA ratio?
Correct answer: C. Total deposits = 30 + 45 + 75 = ₹150 crore; CASA = 30 + 45 = ₹75 crore; ratio = 75 ÷ 150 × 100 = 50%.
Q23. A retail-loan journey begins with 500 applications and ends with 350 completed cases. Application completion rate?
Correct answer: A. Completion rate = 350 ÷ 500 × 100 = 70%; abandonment = 30%. Interpret alongside eligibility and customer experience.
Q24. Which design feature helps explain unexpected changes in a KPI?
Correct answer: D. Trends and governed drill-down show context and support root-cause analysis, while timestamps and annotations clarify data freshness and changes.
Q25. Which is an appropriate remedy for recurring differences between branch MIS and CBS?
Correct answer: B. A sustainable resolution addresses data definitions and source mappings, applies automated checks, assigns ownership and preserves traceable adjustments.
P4B11: Management Information Systems
JAIIB Paper 4 · Module B · Bank MIS explained through real-world workflows, data quality, banking KPIs, worked calculations and 25 original MCQs.
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.