Difference between revisions of "GL reconciliation"

From ADempiere
Jump to: navigation, search
This Wiki is read-only for reference purposes to avoid broken links.
(Status)
(Overview)
Line 4: Line 4:
 
== Contributors  ==
 
== Contributors  ==
 
== Overview  ==
 
== Overview  ==
 +
Provide a means to automatically reconcile GL accounts including those used as clearing accounts in ADempiere such as bank-in-transit, unallocated AP and AR payments, Goods Received but not invoiced, Goods invoiced by not received and AP and AR control accounts.
 +
 +
The functionality works as follows (using AR Control Account as example) 
 +
Every invoice debited to AR control Account obviously has a C_Invoice_ID.
 +
Every Payment allocation that impacts the AR Control Account has a C_AllocationLine which links to a C_Invoice_ID.
 +
The system has a process which finds those items which sum to zero and sets a flag to indicate that they are matched.
 +
 +
The system also has a manual matching window so that an invoice can be cleared buy a journal entry (say) even though the system can not detect any relationship between the two items.
 +
A new report allows you to select a GL account for a nominated data range and includes all transactions which do not sum to zero within the nominated date range.  This function can be used for maintaining reconciliations of any Balance Sheet accounts within the application
 +
 +
The functionality makes use of a new table with the same IDs as the FactAcct table.  There are no dependencies or changes to existing Adempiere
 +
 
== Purpose  ==
 
== Purpose  ==
 
== References  ==
 
== References  ==

Revision as of 00:53, 7 June 2013

Status

In production use

Contributors

Overview

Provide a means to automatically reconcile GL accounts including those used as clearing accounts in ADempiere such as bank-in-transit, unallocated AP and AR payments, Goods Received but not invoiced, Goods invoiced by not received and AP and AR control accounts.

The functionality works as follows (using AR Control Account as example) Every invoice debited to AR control Account obviously has a C_Invoice_ID. Every Payment allocation that impacts the AR Control Account has a C_AllocationLine which links to a C_Invoice_ID. The system has a process which finds those items which sum to zero and sets a flag to indicate that they are matched.

The system also has a manual matching window so that an invoice can be cleared buy a journal entry (say) even though the system can not detect any relationship between the two items. A new report allows you to select a GL account for a nominated data range and includes all transactions which do not sum to zero within the nominated date range. This function can be used for maintaining reconciliations of any Balance Sheet accounts within the application

The functionality makes use of a new table with the same IDs as the FactAcct table. There are no dependencies or changes to existing Adempiere

Purpose

References

Design Considerations

Assumptions

Dependencies

Constraints

Glossary

Functional Requirements

User roles & profiles

Business process definition

User stories

Functional requirements based on business processes

User Interface Mockups

Acceptance criteria

QA and test cases

Development infrastructure

Technical Requirements

Data Requirements

Non-Functional Requirements

Open Discussion Items

Closed Discussion Items