# IBSS Micro-Banking System Analysis

## 1. System Architecture & Core Concepts

The system is designed as a modular, integrated banking solution specifically tailored for Sharia compliance (BPRS/BMT). It uses a centralized database where all modules interact in real-time.

### Key System-Wide Logics

**Maker-Checker (Verification) System**
- A fundamental security feature where data entered (Status 0) is inactive until verified by a supervisor (Status 1)
- Applies to: Customer Data, Savings Accounts, Time , and Loans

**Integration**
- Front-end products (Savings, Loans) are mapped to back-end Accounting (GL) codes
- Transactions in Teller automatically journal into Accounting

**Login Security**
- Requires Server IP, Database path, and distinct User/Password credentials
- Managed by an Administrator

---

## 2. Module Breakdown

### I. Administrator Module

Acts as the "Control Panel" for the entire system, handling security, configuration, and product definitions.

#### User Management
- **Create/Edit Users**: Define User Name, Password, Full Name, and Unit/Branch
- **Access Rights**: Granular control over which menus a user can access
  - Supports duplicating permissions from existing users for faster setup

#### System Configuration
- **Menu Editing**: Renaming menu items to match institution terminology (e.g., changing "Interest" to "Profit Sharing")
- **Institution Identity**: Setting the Bank Name, Address, and Branch Codes

#### Product Parameter Settings
- **Savings/Time /Financing Settings**: Defining global rules for these products
- **Accounting Integration**: Mapping modules to the Chart of Accounts (COA) to ensure automatic journaling

#### Tools
- Backup Data
- Script Compiler (for updates)

---

### II. Customer Service (CS)

The front-line module for managing the CIF (Customer Information File).

#### Customer Database (Data Nasabah)
- **Registration**: Capturing bio-data (Name, ID/KTP, Address, Mother's Name, Spouse Data)
- **Biometrics**: Capturing Photos and Signatures via scanner or file upload (.jpg)
- **Search/Filter**: Searching customers by Name, ID, or partial text matches

#### Verification
- New customer data enters with Status=0
- A supervisor must verify it to Status=1 before accounts can be opened

#### Reporting
- Generating Customer Lists
- Customer Profiles (viewing all accounts—Savings, Deposito, Financing—linked to one Customer ID)

---

### III. Back Office Simpanan (Savings)

Manages daily savings accounts (Tabungan).

#### Master Data Management
- **Account Opening**: Linking a Product Type (e.g., Wadiah) to a Customer ID
- **Parameters**: Setting Profit Sharing Ratio (Nisbah), Tax (PPH), Minimum Balance, and AO (Account Officer)

#### Product Definition
- Defining distinct products (e.g., Hajj Savings, Student Savings)
- Setting calculation methods (Daily vs. Lowest Balance) and admin fees

#### Operations
- **Print Cover/Passbook**: Printing transaction history or account books
- **Blocking**: Freezing accounts (Blokir) and Unblocking
- **Profit Sharing Update**: Bulk updating of Nisbah (sharing ratio) per product
- **Adjustment**: Manual adjustment of balances if errors occur

---

### V. Back Office Pembiayaan (Financing/Loans)

The most complex module, handling loan origination, collateral, and scoring.

#### Loan Origination (Data Master)
- **Loan Details**: Principal, Margin/Mark-up, Term (Months), Installment Frequency (Monthly/Weekly)
- **Payment Type**: In Advance (pay at start) vs. In Arrears (pay next month)
- **Collateral (Agunan)**: Detailed recording of assets (Land Certificates, Vehicle BPKB, SK) used as security

#### Credit Analysis
- **Scoring/SID**: Recording BI standard data (Sector Economy, Usage Type) for reporting
- **Collectibility**: Automatic or manual setting of loan status (Current, Substandard, Doubtful, Loss) based on days past due

#### Operations
- **Schedule**: Generating the amortization/payment schedule
- **Restructuring**: Rescheduling loans (changing terms/installments) for troubled accounts
- **Write-off (Debius)**: Handling bad debt write-offs

---

### VI. Teller (Transactions)

The execution module for financial movement.

#### Savings Transactions
- Cash Deposit, Cash Withdrawal, and Overbooking
- Supports Bulk/Collective transactions (e.g., collecting from a school)

#### Time Deposit Transactions
- Deposit Principal (Account opening) and Withdrawal (Break/Maturity)
- Withdrawal of Profit Sharing (Basil)

#### Financing Transactions
- **Disbursement (Realisasi)**: Payout of the loan to the customer
- **Installment (Angsuran)**: Collection of principal and margin payments
- **Auto-Debit**: Processing installments directly from a Savings account

---

### VII. Akuntansi (Accounting)

The General Ledger (GL) module that captures all financial data.

#### COA Management
- Creating and editing the Chart of Accounts hierarchy (Assets, Liabilities, Equity, Revenue, Expenses)

#### Journal Entries
- **Automated**: Generated from Teller/BO modules based on integration settings
- **Manual**: General Journal, Cash In, Cash Out journals for non-system transactions

#### Closing
- **End of Year**: Process Closing Entry to zero out P&L accounts and move balance to Retained Earnings

#### Financial Reports
- Balance Sheet (Neraca)
- Income Statement (Laba Rugi)
- Trial Balance
- Profit Distribution Calculation

---

### VIII. Bank Indonesia (Regulatory Reporting)

Handles compliance reporting for the Central Bank.

#### SID (Credit Bureau)
- **DIN Management**: Requesting and Updating Debtor Identification Numbers
- **Export**: Sending credit history data (Form 1, Form 3) to the BI credit registry

---

## 3. Cloning Checklist (Technical Requirements)

Based on the manual's features, a clone must support:

### Database Design
- Relational tables for Customers, Savings, , Loans, and GL
- Foreign keys linking Customers to Accounts, and Accounts to Transactions

### State Management
- Implementing the Status=0 (Pending) vs Status=1 (Active/Verified) logic across all master data modules

### Accounting Engine
- A double-entry bookkeeping engine that listens to transaction events and creates Journal entries based on configurable GL mapping

### Reporting Engine
- Ability to generate PDFs for Passbooks, Bilyets, and Financial Statements
- Ability to export data to Excel/CSV for BI reporting

### Security Layer
- Role-Based Access Control (RBAC) to enforce menu-level permissions
- Audit trails for "Correction" events (modifying data after verification)