Projects:OpenBalances/Technical Documentation

Contents 1 Technical Documentation 1.1 Functional Description 1.2 Scope 1.3 Configuration 1.3.1 Record_ID2 Filling 1.4 Implementation 1.4.1 Table Structure

Technical Documentation

Functional Description

When browsing an open balance (for example for receivables account) in the ledger, we can see all entries related to that account and time range.

Having tons of entries some times makes it really difficult to understand where the outstanding amount (open balance) comes from.

Having an option to hide those entries which have already been debited and credited (are no longer open items) can really help to understand where an open balance comes from. User would like to map the open balance for receivables with the outstanding invoices that have not yet been paid.

Scope

This project revisits financial flow to link accounting entries one to another. Holding that info is required to exclude not open balances in the ledger.

This projects puts in place an infrastructure to be able to manage open balances per account, so that any other account can use it in future implementations.

Configuration

There is no particular configuration required to use this piece of functionality.

There is a new process which can be scheduled called:

Record_ID2 Filling

This process revisits accounting entries trying to populate required info. It sets both link and balancing date for historical records.

Implementation

There are two new fields in Fact_Acct table:

• Record_ID2: column which holds the key that links one entry to another

• DateBalanced: Date on which the set of entries was balanced.

Accounting processes needs to be revisited for:

• Populating info when posting:

• • DocInvoice: Adds Payment Schedule ID info to receivables and payables entries

• • DocFINPayment:

when booking against invoice:

• • • Adds Payment Schedule ID info to receivables and payables entries
    • Payment ID info to on receipt/paid account.

• • DocFINFinaccTransaction:

when booking against invoice:

• • • Adds Payment Schedule ID info to receivables and payables entries
    • Payment ID info to on receipt/paid account.

when booking against payment:

• • • Payment ID info to on receipt/paid account.
    • Transaction ID info to on deposited/withdrawal account.

when booking against transaction:

• • • Transaction ID info to on deposited/withdrawal account.
    • Empty info to on clearing account (As there is no further matching).

• • DocFINReconciliation:

when booking against invoice:

• • • Adds Payment Schedule ID info to receivables and payables entries
    • Empty info to on clearing account (As there is no further matching).

when booking against payment:

• • • Payment ID info to on receipt/paid account.
    • Empty info to on clearing account (As there is no further matching).

when booking against transaction:

• • • Transaction ID info to on deposited/withdrawal account.
    • Empty info to on clearing account (As there is no further matching).

• Clearing info when delete/unpost: It clears DateBalanced info

Table Structure

Fact_Acct table

Fact_Acct
Column Name	Type	Length	Comments
RECORD_ID2	VARCHAR	32	The ID WHICH LINKS ONE ENTRY TO ANOTHER.
DATEBALANCED	DATE		HOLDS THE DATE ON WHICH THE BALANCE WAS OFFSET