Projects:Bank Statement Reconciliation Process Review/Functional Specification
Contents |
Bank statement reconciliation process review - Functional Specifications
Overview
At present, Openbravo ERP allows users to generate bank files through remittances but there is no way of uploading files coming from bank to do an automatic conciliation.
Purpose
Uploading Bank files and doing automatic conciliations.
Scope
Actions performed:
- Bank file format definition.
- Bank file uploading.
- A proposal of payments matching. This action will be done taking into account this info:
- Payment amount.
- Due date.
- Business partner.
- DocumentNo (Invoice).
- Organization.
- A user friendly window to do manual matching will be provided for those payments that couldn't be matched automatically. If matching is not possible, in this window user will be able to flag the payment as not found so that the system can create one though a +/- settlement or through a manual settlement (C_GLItem required).
- Bank statements for each bank account will be generated automatically.
Design Considerations
Dependencies
There is no dependency for this project.
Functional Requirements
Business process definition
- Bank file format definition.
- Bank file header creation: here user selects a file format and uploads the file.
- Automatic matching.
- Manual matching if needed.
- Document processing: this step will generate bank statements.
User stories
Here we have a little example of a user story:
Carlos, who is in charge of registering bank movements in the application, receives a bank file from BBVA to be registered. Through Bank File window he is able to register the new file he has received and then run Creation lines process. This opens a form where all the movements are. Most all of them have been automatically matched by the system, so he only needs to find three more payments which do not exist in the ERP. He flags two of them as new, as he knows those charges are related to two invoices he has not received yet, and he also flags the third one as new but this time he selects a GL Item related to an expense and validates the process. Now he can check that everything is alright in lines tab. Once he has done that he can run process button so that the bank statement is created.
Functional requirements based on business processes
To achieve the desired functionalities the following elements need to be added.
Windows
Bank file format: Here user can define different bank file formats.
- Tabs:
- Bank file format (Header):
- Name
- Description
- Lines:
- Line type (Header, Body, Summary)
- Sequence
- Name
- Fields:
- Field Name
- Sequence
- Initial position
- End position
Bank file: Here user can upload bank files, do the matching and generate bank statements
- Tabs:
- Bank file:
- Name
- Description
- Date
- Bank file format
- Upload file button: This will create the lines and if any doesn't match a manual matching form will be shown.
- Process button: this will generate bank statements
- Bank file will be attached in this tab
- Lines:
- Business partner name
- Business partner
- Due date
- Amount
- Bank account name
- Bank account
- Invoice Number
- IsReceipt (flag)
- Description
- IsNew (flag)
- GL Item
- Matched payment
Form
Manual matching: In this form automatic matching will be shown with its details but also those payments which couldn't be matched automatically appears with no payment linked. User will be able to link them manually or just flag the line as “New”. If a line is flagged as new, user will be able to select a GL Item (optional). Once finished all new payments and settlements will be crated and lines info will be updated.