View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

Projects/Reconciliation Screens Refactor/Functional Specifications

Contents

Overview

This document contains the functional specifications for the refactoring of the “Match Statement” process in Financial Account window.

The intention of this project is to improve the “Match Statement” window that currently exists in Openbravo using parameter windows technology.

Purpose

The purpose of this project is to refactor reconciliation process to enhance it and move it to 3.0 technology. This will provide:

Scope

The 1st phase of this project is the refactor reconciliation process, this phase only cover the development of the functionality that now exists in Match Statement button.

The 2nd phase of this project is improve the match statement functionality and add a new grid in which the result will not be a single record or match but a list of candidates.

Design Considerations

Dependencies

This project needs the new functionality created for selectors Process for Adding Records available since 3.0PR14Q4 release. This new functionality allows to open a process definition from a selector.

Functional Requirements

"Match Statement" process can be launched from Financial Account window by clicking in match statement button.

User roles & profiles

Financial staff (Peter): Peter is an employee part of the financial staff. He is in charge of review all transactions and do reconciliations.

Business process definition

F&B International Group is an enterprise from USA making business with several Business Partners: Vendors, Suppliers, Customers, etc. Every Business Partner can have by default Payment Methods such as Check and Wire transfer; and by default Payment Terms such as Immediate, 30 days or 60 days. Peter a member of financial staff review the transactions which have been introduced into the system and do reconciliations.

User Stories

Story 1: Match Automatically a Transaction and a Bank Statement Line

Peter is reviewing sales transactions, he should reconcile a transaction type BP Deposit, amount: 10000 and transaction date 09-09-2014.

Peter creates a new bank statement line with this data: transaction Date: 09-09-2014, reference No.: 123456, business Partner: Customer A, amount In: 10000

Peter reconcile this transaction by clicking match statement and click OK in using the standard algorithm.


Story 2: Match Manually a Transaction and a Bank Statement Line.

Peter is reviewing sales transactions, he should reconcile a transaction type BP Deposit, amount: 2500 and transaction date 10-09-2014.

Peter creates a new bank statement line with this data: transaction Date: 10-09-2014, reference No.: 123458, business Partner: Customer A, amount In: 100

Peter click cancel in using the standard algorithm.

Peter click on Magnifying glass button in the line and select the previously created transaction and click Done.

Functional requirements based on business processes

All the information displayed in that main grid is related to bank statement line info. There all not yet matched transactions will appear together with the lines matched in the ongoing reconciliation.

There will be a default filtering criteria to just see open oitems (not yet matched bank statement lines) which could be cleared to have a full picture of the reconciliation lines (both open and matched for the selected reconciliation).

Mach column has three icons through which the user is able to

Another icon showing level of affinity for the match will be as well displayed.

User Interface Mokups

Match Statement grid

MatchStatement3.png

Match Statement Selector

MatchStatementSelector.png

Retrieved from "http://wiki.openbravo.com/wiki/Projects/Reconciliation_Screens_Refactor/Functional_Specifications"

This page has been accessed 282 times. This page was last modified on 23 September 2014, at 10:14. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.