Skip to content
IND-02 · Banking, SACCOs, insurance and capital markets

EDMS for banks and SACCOs: files that are complete when the regulator asks

An examiner pulls a sample of files and checks three things: whether the file is complete, who has been inside it, and how long it has been kept. EDMS by Sibasi stops an incomplete file progressing at onboarding, restricts what each role can open, and holds the access history an inspection will ask for.

REF / RECORDS

What you hold

The file plan is built around these. Each record class gets its own metadata, permissions and retention position.

  • KYC and customer due diligence files
  • Loan applications, appraisals and security documents
  • Account opening and mandate forms
  • Insurance policy files and claims documentation
  • Member records and share registers
  • Board, ALCO and credit committee papers
  • Regulatory returns and correspondence
  • Internal audit and risk documentation

REF / OBLIGATIONS

What you are judged against

These are the rules the deployment is configured to satisfy — mapped onto retention schedules, access models and audit reporting during design, not asserted afterwards.

Compliance

Anti-money laundering and CDD requirements

Customer due diligence records must be complete, current and retrievable, and retained for the statutory period after the relationship ends.

Compliance

Prudential and market conduct examination

Supervisors sample files during inspection. A file that cannot be produced is treated as a file that does not exist.

Compliance

Data Protection Act, 2019

Customer financial data carries some of the strictest handling expectations in the Act, including access control and demonstrable retention limits.

Compliance

External audit and IFRS evidence

Impairment, provisioning and revenue recognition all rest on underlying documents that auditors must be able to trace.

Compliance is a property of your organisation rather than of software. What the platform provides is the technical control and the evidence — see security and compliance for how each control is implemented.

REF / BEFORE

What tends to be true today

  • Incomplete files discovered during inspection

    A missing identity document or an expired mandate found by an examiner rather than by the institution, months after onboarding.

  • Credit files spread across branches

    Security documents in one branch, appraisal in another, correspondence in a shared mailbox. Nobody holds the whole picture.

  • Turnaround measured in customer complaints

    Loan and claim approvals stall in queues nobody can see, and the first signal of a delay is the customer calling.

  • Retention that is either indefinite or accidental

    Records kept forever because nobody is willing to authorise destruction, or destroyed early because nobody applied a schedule.

REF / AFTER

What the deployment changes

  • Files that cannot be incomplete

    Mandatory document checklists per product. A file cannot progress to approval while a required item is missing or expired.

  • Expiry monitored automatically

    Identity documents, mandates, valuations and insurance certificates carry expiry dates the system tracks and escalates before they lapse.

  • Turnaround you can manage

    Every approval stage timed, every overdue item visible, and a Power BI dashboard that shows where the queue actually is.

  • Examination without a fire drill

    Requested files, access histories and retention evidence produced from standing reports rather than an all-night search.

REF / NEXT STEP

See EDMS by Sibasi configured for financial services

Bring one of your own record types and one process that currently takes too long. We will show you both running in under an hour.