View source | View content page | Page history | Printable version   

Projects:MatchStatement Unmatch Multiple Records/FunctionalSpecs


Unmatch Transaction Engine Refactor - Functional Specifications


This project intends to deliver a new and extensible unmatch engine for core's Openbravo ERP.


Current unmatch engine only covers the single transaction unmatch method. This project will deliver a new unmatch engine that will facilitate to unmatch different transaction in the same time.


This project will deliver a new API to manage unmatch multiple transactions. All core functionality based on old unmatch will be updated to support the new one.

Design Considerations



Functional Requirements

Business process definition

  1. Match Statement screen.
    1. Unmatch Multiple Records in the same time.
    2. Unmatch Multiple Records does not change previous unmatch single record.

Functional requirements descriptions

In this section are described all the functional requirements to fulfill this development.

The aim of the new engine is to unmatch Multiple Records. Each record will have its Imported Bank Statement without any match.

Technical Requirements

Non-Functional Requirements

Discussion Items

Open and comment discussion items on project's Open discussion forum

Retrieved from ""

This page has been accessed 1,634 times. This page was last modified on 9 September 2015, at 14:38. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.