Verified local facts
The commitment observatory uses a household obligation ledger and a separate personal-data request ledger, preventing MCIB participation from becoming an invented individual record.
Evidence reviewed
Help a Mauritius household list debts and credit checks using attributable evidence and a stop condition.
Decision checklist
The commitment observatory uses a household obligation ledger and a separate personal-data request ledger, preventing MCIB participation from becoming an invented individual record; review marker 115 applies this device only to “list debts and credit checks Mauritius” and the evidence boundaries named on this page.
Open household Ledger A
List every current obligation known to the household with legal owner, account reference, dated balance source, payment amount and due date. Include informal promises when they genuinely affect cash, but label their evidence. Do not omit an account because it may not appear elsewhere. The purpose is an honest capacity register, not a guess about provider visibility.
Map payment timing and exposure
Add remaining term, rate basis if documented, security, guarantor and event-triggered obligations. Place payments on the household calendar. A balance alone cannot show the pressure of due dates or the consequence of a promise. Unknown settlement or security information remains open. This map feeds affordability and application answers without merging them.
Separate disputed entries
Mark a disputed balance, payment or status with its source, reason and competent contact. Do not delete it from the budget while unresolved, and do not present the household's view as an official correction. Preserve receipts and correspondence. A complaint or data request follows its own process and does not automatically suspend an obligation.
Open personal-data Ledger B
Identify the organisation believed responsible, exact information sought, reason, authenticated route and current procedure. Do not send a general request to every MCIB participant. Data access, correction and application review are distinct actions. Ledger B records requests and receipts without declaring what information actually exists before the responsible organisation answers.
Interpret MCIB participation narrowly
The official participant list can confirm that named organisations participate in MCIB. It cannot establish that a particular person has a file, which entries appear, whether a score is used or how an application will be decided. Keep those prohibited inferences on the observatory wall. Questions about a personal record require a competent individual process.
Reconcile without forcing agreement
Compare household records with any personal-data response only after ownership, period and identifiers align. A difference becomes a dated discrepancy, not proof that either side is automatically wrong. Ask the responsible organisation through its current process. Do not change Ledger A's cash-flow treatment until the contractual or payment evidence supports a change.
Answer applications truthfully
Use the exact question and product owner to decide what commitments must be disclosed, then answer from current evidence. MCB and MauBank criteria are not interchangeable. Do not hide an obligation because a data response is pending or volunteer unrelated private information. Record the question, answer, supporting item and recipient for accountability. Build the household ledger from payment evidence outward, not from recollection inward. Begin with every observed outgoing amount that may represent a commitment, identify its payee and date, and then connect it to the agreement or statement that explains balance, term and status. If no competent record resolves the item, keep an uncertainty row and a conservative capacity treatment; do not silently delete it. Contingent duties, guarantees, disputed amounts and payments made for another person receive distinct labels because they raise different questions. The personal-data ledger follows a different clock. It records the organisation addressed, identity-verification method requested, scope of the access question, date sent and response received. It never copies a household estimate into a supposed institutional file. When a response arrives, reconcile exact fields rather than announcing that the record is clean or wrong as a whole. One observer reads the received information; another compares only the bounded field with contractual or payment evidence. A mismatch produces a dated question to the competent owner. During that process, ordinary payment duties and household planning continue according to reliable evidence; an unresolved query is not permission to ignore an amount. The final observatory report therefore has two endings. The household view lists commitments used for capacity decisions and every uncertainty reserve. The information-rights view lists requests, responses and unresolved fields. Neither ending assigns a score, states what an MCIB participant holds before evidence arrives, or forecasts how MCB, MauBank or another institution will assess an application.
Close two ledgers, never one score
Summarise household payments, disputed entries, data requests, responses and unresolved differences. The observatory does not calculate a credit score or approval probability. A provider owns its decision, while the household separately owns affordability. Set review triggers for new statements, corrected data or changed terms and keep both ledgers traceable. Add a discrepancy telescope for any difference between contractual records, household evidence and a received personal-data response. It logs the exact field, owner, period, source and correction route without broadcasting the entire file. Magnification means narrowing the question, not increasing certainty. A second observer must locate the same difference from the cited records. Keep the payment in the capacity calendar until competent evidence supports another treatment. The telescope's output is a bounded request and review trigger; it never becomes a score, allegation or forecast of the application result.