Activity Stream

2 days ago
new user registration
Parasuraman Vaidyanathan joined our community! Welcome!

More than a week ago
new download
Kandasamy Nagappan downloaded Aging 4 buckets


new user registration
Kandasamy Nagappan joined our community! Welcome!

new user registration
Zakeer Shaik joined our community! Welcome!

More than 2 weeks ago
new user registration
Narasinga Chennuri joined our community! Welcome!

new download
Marek Skulski downloaded Aging 4 buckets

Financials Accounting Hub - An incremental implementation approach
( 1 Vote )
Financials for R12 - Subledger Accounting & FAH
Written by Sven van Leemput   
Monday, 10 January 2011 14:33

This is a high level example of a FAH implementation. I already described this briefly in this post, but never got around sharing my illustrations, which better showcase the approach. We start with the following architecture:

Starting situation

 The purple boxes represent source systems (e.g. billing, mortgages, investments, claims etc.).

Originally both Lines of Business (LOB1 & LOB2) had their own General Ledger solution. At some point in time both Lines of Business migrated to a single General Ledger solution.
As the source systems are connected to the legacy General Ledgers through various point-to-point interfaces, it would have taken too much time and effort to redesign all those solutions at once and point them to the new corporate General Ledger. Therefore the interfaces from the source systems towards the legacy General Ledgers were preserved, and a custom transformation framework was put in place which translates the accounting from the legacy General Ledgers onto the new corporate accounting structure.

Phase 1: introduce FAH in a Journal Pass-through mode:

Pass-through

First FAH is introduced in the architecture by replacing the custom transformation framework. At this stage FAH is only used in a Journal Pass-through mode: the events presented to FAH already contain an accounting key, and FAH simply maps the accounting from the legacy format onto the new chart of accounts.

Phase 2: move towards an event-based accounting architecture. Now that FAH is part of the application landscape, any newly introduced source system can be connected directly to FAH:

New source
Such a direct connection leverages the true powers of FAH, as you can use the raw transaction information from the source system to have FAH create the accounting entries. In addition FAH will also maintain the audit trail between source events and the General Ledger journals.
Then select one of the existing source systems to connect it directly to FAH:
Connect existing
Over time the non-strategic source systems will become obsolete. The remaining source systems (and new ones) can be connected directly to FAH.
Connect more
This leads to a situation where the legacy interface and General Ledger can be switched off and removed:
Remove legacy interface
And the same holds true for the other Line of Business, eventually leading to the following end-state:
End state
So you can use such incremental approach to position FAH within the architecture at low risk and with low effort, while still having all accounting flow through FAH from day 1. Then you can gradually move to an event-based accounting approach, doing so at your own pace, because all variations of journal pass-through and event-based accounting are possible.

In the end-state all accounting rules and logic are stored centrally within FAH's user updatable rules repository, the legacy interfaces and systems can be switched off, and FAH preserves a complete bi-directional audit trail between business events and General Ledger journals.

Comments

avatar dilipk
0
 
 
Hi, how can tax be handled in FAH? If recoverable / non-recoverable taxes are coming from source system, what all does FAH offer? Can it calculate taxes by % etc.?
avatar mohit
0
 
 
I ahve a question regarding FAH applicability for a particular business scneario.
In banking industry the fees and expenses on accoutns are treated differently.
Subledger Accounting queries:

Can FAH generate the ammortization accounting given below (I'm assuming using multi accountg period):

Scenario:

A Loan is added in an external system on Jan-15th-2012 ,during Addition of Loan a sperate line item "Acquisition Fees " is paid by cusomter in that external system,

Now business requirement is Acquisiton Fees of 3600 $ is collected for a 36 months loan.Recognition of this income should be
during the tenure of loan

On Jan-15th

Cash AC-3600$ DR
Acquisition fees(Advance)-3600$- CR

On Jan 15th
Acquisition fees(Advance)-100$ DR
Acquisition Feess income-100$ CR


On Feb 15th
Acquisition fees(Advance)-100$ DR
Acquisition Feess income-100$ CR

Amortize the income for 36 moths
............


Now this split of 3600$ can be into 36*100$ or could be based on some different rule.Is FAH allows to have different rules for recognizing this income differently each month

Assuming External system can send all the required information in the required format eg., Entity Class,Event,Type,Amount ,Date

Also if due to some business event ,e.g., Loan closure in say month 22nd the remaining amortization needs to be stopped and another GL entry needs to be posted .Can this be done through FAH.

Also if Daily Accruals possible (based on different interest rates ,different
Please login to post comments or replies.