Page tree
Skip to end of metadata
Go to start of metadata


Highlights:

      • Event-driven financial accounting
      • Freely definable accounting logic and chart of accounts
      • "Map´n go" implementation of individual chart of accounts
      • Generated debit/credit entries are traceable to the underlying accounting transaction as well as the accounting rule which has been applied during the journalisation process


The blueprint Financial Accounting deals with requirements related to financial accounting, taking GAAP-specific requirements into account.

The Accounting Rules Engine (ARE) 

  • Identifies the applicable accounting event for accounting transactions related to financial instruments and non-financial instruments.
  • Organises subsequent, periodical measurement of assets and liablities  
  • Generates a set of debit/credit entries for each accounting event at individual transaction level for each configured GAAP in parallel and feeds these journal entries into data marts.
  • Considers a specific chart of accounts and accounting logic while generating debit/credit entries for each GAAP. Chart of accounts and accounting logic can be individually defined for each GAAP, nonetheless the Accounting Rules Engine comes with a standard chart of accounts and accounting logic which can be used out of the box.
  • Calculates general ledger account balances and feeds them into data marts specific for accounting in the result layer

The financial accounting provided is event-based: journal entries, which cover the entire life cycle of a financial or non-financial deal, are generated on the basis of business events and periodic accounting events.


It is possbile to run multiple GAAPs in parallel or use as an adjustment accounting for a master GAAP.

For this purpose, it uses a separately configurable accounting logic for each GAAP and transfers accounting transactions into debit/credit entries.


The generation of debit/credit entries is provided in two steps:

  • In a first steps, the set of entries and related individual debit/credit entries are identified for an accounting transaction.
  • In a second step, the general ledger account to which entries are to be posted is identified for each indiivdual debit/credit entry.

For both steps, the individual configuration of accounting logic and general ledger account assignment rules is supported. This enables an entity to consider the individual accounting policy and to use an individual chart of accounts.


Figure: Functional process steps of the accounting rules engine


Accounting transactions

Business events and periodical evaluation events are referred to as accounting transactions.

The Accounting Rules Engine expects the delivery of accounting transactions. Accounting transactions can be derived for specific types of events such as valuation, payment etc. through separate components. These separate components link other components such as Hedge, Impairment or Valuation with the Accounting Rules Engine.

An accounting transaction consists of parameters that describe the event, the link to the underlying financial or non-financial instrument, organisational characterictics, measures and ratios that help to calculate the amount to be posted and others.  

Accounting transactions can be

  • Imported from any third-party tool
  • Derived on the basis of information provided by the estimated cash flow plan, taking 
    • Delivered payments, 
    • Maturities of the estimated cash flow plan and 
    • Periodical valuation events as well as
    • Hedge information

 into account.

For details about supported types of accounting transactions, please read more in the manual: Accounting Transaction.


Accounting logic
The accounting logic links the accounting transaction with the set of entries.

A wide range of descriptive parameters can be used for the definition of the link between accounting transaction and set of entries as well as the link between general ledger account group and individual general ledger account. The following list of parameters provides examples only:

  • Product Type
  • Customer Type
  • Industry Type
  • Cost Center
  • Type of Hedge Relation
  • Impairment Stage


Set of entries

A set of entries consists of several individual debit and credit entries.

In the setup of the set of entries the individual entries are defined as follows:

  • Debit/credit sign depending on the sign of the value of the amount to be posted
  • Methodology of how the amount to be posted shall be calculated 
  • Group of general ledger accounts to which the account number belongs which ultimately is be posted

The number of debit/credit entries is not limited.


Chart of accounts

Individual debit and credit entries will be generated during the journalisation process, after the accounting transaction has been imported and the appropriate set of entries has been identified. In order to generate individual debit or credit entries, the Accounting Rules Engine makes use of a configurable chart of accounts. Specific account assignment rules can be defined for each general ledger account number.


Individual debit/credit entries

For each individual debit and individual credit entry, the

  • amount to be posted will be calculated on the basis of the method configured
  • debit/credit sign will be assigned on the basis of the configured relationship between debit/credit flag and the sign of the calculated amount to be posted
  • individual general ledger account to be posted will be assigned on the basis of the account number assignment process.

The account number assignment process selects all general ledger accounts for the configured group of general ledger accounts. Such a group can consist of one or more individual general ledger accounts. For the posting process, the general ledger account that fulfills the account assignment rule and has the highest number of hits will be selected.


FlexFinance provides special templates for the set of entries for every financial product, every event, every GAAP. These standard sets of entries can optionally be adapted individually to each customer requirement.

  • No labels