A Windows desktop application built for Tripura Forest Development & Plantation Corporation Ltd. to digitise and centralise bank account management - replacing paper registers with structured account tracking, FD maturity alerts and a full transaction audit trail.
TFDPC Ltd., a Government of Tripura public sector undertaking, managed its banking operations entirely through paper registers. The organisation held funds distributed across fixed deposits, current accounts and savings accounts - often across multiple banks. Tracking maturity dates for fixed deposits required manually cross-referencing old records and there was no consolidated view of the company's financial position at any given point.
Core ask: Build a system that alerts the accountant ahead of FD maturity dates, tracks all transactions with an audit trail and provides a current status view of all accounts - eliminating the paper-based process entirely.
This was our MCA first-year summer internship project at ICFAI University, Tripura, completed in July 2012. The client was TFDPC Ltd., guided by Mr. Ranjit Singh (company guide) and Mr. Ashish Chowdhury (academic project guide).
The application was built as a Windows Forms MDI (Multiple Document Interface) application using VB.NET, with Microsoft Access as the backend database connected via OLEDB. The choice was driven by the client's existing IT environment - Windows XP machines with Office installed - and the team's familiarity with the Microsoft stack from coursework.
Three-tier alert system surfacing fixed deposits maturing within 7, 30 and 90 days - visible on the home screen immediately after login.
Full CRUD for Fixed Deposits, Current Accounts and Savings Accounts - including deposit/withdrawal transactions and automatic balance updates.
Every financial event - account creation, fund transfers, debits, credits, FD maturation - is logged to a transaction table with timestamps.
Consolidated view of all accounts across banks, filterable by account type and bank name, with a print-ready report output.
Search accounts by bank name, account number, date of opening, date of maturity, or date of transaction - across all account types.
Administrator authentication with credential management and a one-click database backup to any local path - protecting against data loss.
The maturity alert was the primary business requirement. On every login and whenever the home form regains focus, the application queries the Accounts table for fixed deposits maturing within three time windows. The colour-coded counters (red for 0–7 days, orange for 8–30, yellow for 31–90) are visible at a glance in the top-right of the home screen.
Matured FDs are automatically moved to the MT (Mature Table) and removed from active accounts - keeping the dataset clean without manual intervention. The corresponding transaction record is written to the TT table with a "ACCOUNT MATURED" remark.
The project followed an iterative waterfall model - feasibility study, requirements specification, design, coding and testing, with feedback loops between phases. The design artefacts included Data Flow Diagrams at three levels, an Entity-Relationship diagram and a Use Case diagram covering nine administrator-facing functions.
Four tables in MS Access covered the full data model:
| Field | Type | Description |
|---|---|---|
| acno | Number (Double) | Account number |
| acctype | Text | FIXED DEPOSIT / CURRENT ACCOUNT / SAVINGS ACCOUNT |
| bankname | Text | Bank name |
| bname | Text | Branch name |
| opendate | Date/Time | Date of opening |
| maturedate | Date/Time | FD maturity date |
| balance | Number (Double) | Current balance |
| intrate | Number (Single) | Interest rate |
| matureamt | Number (Double) | Maturity value (pre-TDS) |
| Field | Description |
|---|---|
| idno | Auto-incrementing transaction ID |
| dot | Date of transaction |
| from | Source account or CASH |
| to | Destination account |
| amt | Amount |
| remark | ACCOUNT CREATED / MODIFIED / DELETED / MATURED / DEPOSIT / WITHDRAWL |
MT (matured FD archive) and ADMINISTRATOR (login credentials) complete the schema. Fund transfers between accounts update balances atomically - debit from source, credit to FD - with a single transaction record capturing both sides.
The system was delivered to TFDPC Ltd. as a functional desktop application at the end of the summer internship. Future enhancements identified at the time included multi-user network support and online database hosting - problems that would look very different solved with today's stack.
The full source code - VB.NET forms, database and project files - is available on GitHub.