Bank Statement & Reconciliation Application For Elit'Avia
<h1>1. Application Overview</h1><p>The <strong>Elitavia Bank Statement & Reconciliation Application</strong> is designed to provide a centralized process for handling bank statement data and supporting reconciliation activities across <strong>Credit Card Expenses</strong> and <strong>Travel</strong> records.</p><p>The solution uses a unified Bank Statements dataset as the central source for uploaded and parsed bank transactions. The same bank transaction information is then used by separate reconciliation modules, with relevant records filtered according to Credit Card Expense or Travel requirements.</p><p>The overall solution is structured around three main modules: <strong>Bank Statement Upload & Parsing, Credit Card Reconciliation, and Travel Reconciliation</strong>.</p><h2>2. Bank Statement Upload and Parsing</h2><p>The <strong>Upload & Parsing Module</strong> handles bank statement information and writes the parsed transaction data into the unified Bank Statements list.</p><p>This provides a common source of bank transaction information that can subsequently be used by the different reconciliation processes.</p><h2>3. Centralized Bank Transaction Records</h2><p>Bank statement transactions are maintained within a unified Bank Statements list.</p><p>The transaction information includes:</p><ul><li><p>Bank Name</p></li><li><p>Sheet Name</p></li><li><p>Transaction Date</p></li><li><p>Cardholder / Employee</p></li><li><p>Amount</p></li><li><p>Description</p></li><li><p>Vendor Code</p></li><li><p>Item Number</p></li><li><p>Amount in EUR</p></li></ul><p>This provides the core transaction information required for subsequent Credit Card and Travel reconciliation activities.</p><h2>4. Credit Card Reconciliation</h2><p>The <strong>Credit Card Reconciliation Module</strong> uses the centralized Bank Statements data for reconciliation with Credit Card Expense information.</p><p>The module reads from the same unified Bank Statements dataset and filters the records according to criteria relevant to <strong>CreditCardExpenses</strong>.</p><p>The Amount EUR field is specifically identified as information used for Credit Card reconciliation.</p><h2>5. Travel Reconciliation</h2><p>The <strong>Travel Reconciliation Module</strong> also uses the centralized Bank Statements dataset.</p><p>Instead of maintaining a separate bank transaction source, the module uses the same transaction information and filters it for <strong>Travel-related records</strong>.</p><p>This allows Credit Card and Travel reconciliation processes to work from a common bank transaction source while using the records relevant to their respective processes.</p><h2>6. Shared Data Across Reconciliation Modules</h2><p>The application uses a centralized approach in which bank statement information is maintained once and then shared across the relevant reconciliation processes.</p><p>The <strong>Credit Card Expense</strong> and <strong>Travel</strong> areas maintain their respective information, while the unified Bank Statements list provides the common transaction dataset required by both reconciliation modules.</p><p>This structure avoids the need for separate copies of the same bank transaction information for each reconciliation process.</p><h2>Overall Application Workflow</h2><p>The process begins with bank statement information being uploaded and parsed through the Bank Statement Upload & Parsing Module. The resulting transaction information is stored in the unified Bank Statements dataset.</p><p>The Credit Card Reconciliation Module then reads from this centralized dataset and filters the relevant transactions for Credit Card Expense reconciliation. Similarly, the Travel Reconciliation Module uses the same bank transaction information but filters the records required for Travel reconciliation.</p><p>This provides a common transaction source that supports multiple reconciliation processes while keeping Credit Card Expense and Travel activities connected to their respective records.</p><p><strong>Upload Bank Statement → Parse Transaction Data → Store in Unified Bank Statements List → Filter Relevant Transactions → Credit Card Expense Reconciliation / Travel Reconciliation</strong></p>
Project Summary
<h1>1. Application Overview</h1><p>The <strong>Elitavia Bank Statement & Reconciliation Application</strong> is designed to provide a centralized process for handling bank statement data and supporting reconciliation activities across <strong>Credit Card Expenses</strong> and <strong>Travel</strong> records.</p><p>The solution uses a unified Bank Statements dataset as the central source for uploaded and parsed bank transactions. The same bank transaction information is then used by separate reconciliation modules, with relevant records filtered according to Credit Card Expense or Travel requirements.</p><p>The overall solution is structured around three main modules: <strong>Bank Statement Upload & Parsing, Credit Card Reconciliation, and Travel Reconciliation</strong>.</p><h2>2. Bank Statement Upload and Parsing</h2><p>The <strong>Upload & Parsing Module</strong> handles bank statement information and writes the parsed transaction data into the unified Bank Statements list.</p><p>This provides a common source of bank transaction information that can subsequently be used by the different reconciliation processes.</p><h2>3. Centralized Bank Transaction Records</h2><p>Bank statement transactions are maintained within a unified Bank Statements list.</p><p>The transaction information includes:</p><ul><li><p>Bank Name</p></li><li><p>Sheet Name</p></li><li><p>Transaction Date</p></li><li><p>Cardholder / Employee</p></li><li><p>Amount</p></li><li><p>Description</p></li><li><p>Vendor Code</p></li><li><p>Item Number</p></li><li><p>Amount in EUR</p></li></ul><p>This provides the core transaction information required for subsequent Credit Card and Travel reconciliation activities.</p><h2>4. Credit Card Reconciliation</h2><p>The <strong>Credit Card Reconciliation Module</strong> uses the centralized Bank Statements data for reconciliation with Credit Card Expense information.</p><p>The module reads from the same unified Bank Statements dataset and filters the records according to criteria relevant to <strong>CreditCardExpenses</strong>.</p><p>The Amount EUR field is specifically identified as information used for Credit Card reconciliation.</p><h2>5. Travel Reconciliation</h2><p>The <strong>Travel Reconciliation Module</strong> also uses the centralized Bank Statements dataset.</p><p>Instead of maintaining a separate bank transaction source, the module uses the same transaction information and filters it for <strong>Travel-related records</strong>.</p><p>This allows Credit Card and Travel reconciliation processes to work from a common bank transaction source while using the records relevant to their respective processes.</p><h2>6. Shared Data Across Reconciliation Modules</h2><p>The application uses a centralized approach in which bank statement information is maintained once and then shared across the relevant reconciliation processes.</p><p>The <strong>Credit Card Expense</strong> and <strong>Travel</strong> areas maintain their respective information, while the unified Bank Statements list provides the common transaction dataset required by both reconciliation modules.</p><p>This structure avoids the need for separate copies of the same bank transaction information for each reconciliation process.</p><h2>Overall Application Workflow</h2><p>The process begins with bank statement information being uploaded and parsed through the Bank Statement Upload & Parsing Module. The resulting transaction information is stored in the unified Bank Statements dataset.</p><p>The Credit Card Reconciliation Module then reads from this centralized dataset and filters the relevant transactions for Credit Card Expense reconciliation. Similarly, the Travel Reconciliation Module uses the same bank transaction information but filters the records required for Travel reconciliation.</p><p>This provides a common transaction source that supports multiple reconciliation processes while keeping Credit Card Expense and Travel activities connected to their respective records.</p><p><strong>Upload Bank Statement → Parse Transaction Data → Store in Unified Bank Statements List → Filter Relevant Transactions → Credit Card Expense Reconciliation / Travel Reconciliation</strong></p>
Location: Birkirkara, Malta
Industry: Business Aviation / Private Aviation / Aircraft Management & Charter Services
Challenge and Requirements
<h1>1.
Solution Delivered
CodeScale delivered a powerapps solution using PowerApps, PowerAutomate, SharePoint for Business Aviation / Private Aviation / Aircraft Management & Charter Services.
Technology Used
- PowerApps
- PowerAutomate
- SharePoint
Business Outcome and Impact
<h1>1. Application Overview</h1><p>The <strong>Elitavia Bank Statement & Reconciliation Application</strong> is designed to provide a centralized process for handling bank statement data and supporting reconciliation activities across <strong>Credit Card Expenses</strong> and <strong>Travel</strong> records.</p><p>The solution uses a unified Bank Statements dataset as the central source for uploaded and parsed bank transactions. The same bank transaction information is then used by separate reconciliation modules, with relevant records filtered according to Credit Card Expense or Travel requirements.</p><p>The overall solution is structured around three main modules: <strong>Bank Statement Upload & Parsing, Credit Card Reconciliation, and Travel Reconciliation</strong>.</p><h2>2. Bank Statement Upload and Parsing</h2><p>The <strong>Upload & Parsing Module</strong> handles bank statement information and writes the parsed transaction data into the unified Bank Statements list.</p><p>This provides a common source of bank transaction information that can subsequently be used by the different reconciliation processes.</p><h2>3. Centralized Bank Transaction Records</h2><p>Bank statement transactions are maintained within a unified Bank Statements list.</p><p>The transaction information includes:</p><ul><li><p>Bank Name</p></li><li><p>Sheet Name</p></li><li><p>Transaction Date</p></li><li><p>Cardholder / Employee</p></li><li><p>Amount</p></li><li><p>Description</p></li><li><p>Vendor Code</p></li><li><p>Item Number</p></li><li><p>Amount in EUR</p></li></ul><p>This provides the core transaction information required for subsequent Credit Card and Travel reconciliation activities.</p><h2>4. Credit Card Reconciliation</h2><p>The <strong>Credit Card Reconciliation Module</strong> uses the centralized Bank Statements data for reconciliation with Credit Card Expense information.</p><p>The module reads from the same unified Bank Statements dataset and filters the records according to criteria relevant to <strong>CreditCardExpenses</strong>.</p><p>The Amount EUR field is specifically identified as information used for Credit Card reconciliation.</p><h2>5. Travel Reconciliation</h2><p>The <strong>Travel Reconciliation Module</strong> also uses the centralized Bank Statements dataset.</p><p>Instead of maintaining a separate bank transaction source, the module uses the same transaction information and filters it for <strong>Travel-related records</strong>.</p><p>This allows Credit Card and Travel reconciliation processes to work from a common bank transaction source while using the records relevant to their respective processes.</p><h2>6. Shared Data Across Reconciliation Modules</h2><p>The application uses a centralized approach in which bank statement information is maintained once and then shared across the relevant reconciliation processes.</p><p>The <strong>Credit Card Expense</strong> and <strong>Travel</strong> areas maintain their respective information, while the unified Bank Statements list provides the common transaction dataset required by both reconciliation modules.</p><p>This structure avoids the need for separate copies of the same bank transaction information for each reconciliation process.</p><h2>Overall Application Workflow</h2><p>The process begins with bank statement information being uploaded and parsed through the Bank Statement Upload & Parsing Module. The resulting transaction information is stored in the unified Bank Statements dataset.</p><p>The Credit Card Reconciliation Module then reads from this centralized dataset and filters the relevant transactions for Credit Card Expense reconciliation. Similarly, the Travel Reconciliation Module uses the same bank transaction information but filters the records required for Travel reconciliation.</p><p>This provides a common transaction source that supports multiple reconciliation processes while keeping Credit Card Expense and Travel activities connected to their respective records.</p><p><strong>Upload Bank Statement → Parse Transaction Data → Store in Unified Bank Statements List → Filter Relevant Transactions → Credit Card Expense Reconciliation / Travel Reconciliation</strong></p>
Project Screenshots
