3. Financials

Accounting Structures

This document details the Accounting Structures of ADempiere including the Accounting Schema, Elements, Accounts and Costing & Tax Rules.

Financial Reports & Report Cube

This How To guide investigates creating financial reports in ADempiere as well as detailling the ‘Report Cube’ functionality that allows for the creation of highly summarised data using user-selected dimensions. The Report Cube can be used as a source of data for the Financial Report Writer module or the data can be exported using the Cube Viewer.

Creating Summary Reports

This document explains ADempiere’s architecture that automatically provides a reporting function on all tables of information that are accessible to a User in the system. This Report capability is referred to as the List Report Writer. The List Report Writer produces reports which display one line per row/record in the table being reported on. Sometimes it is desirable to suppress some of the detail by “rolling up” a series of items into a single report line. This can be done quite easily by adding a view to the database which pre-summarises the data as required. This view can then be reported on using the standard ADempiere

List Report Writer.The following guide is produced to show the steps required to set up summary reporting on the general ledger transactions stored in the FactAcct table. The guide includes screen shots of each window visited to make the necessary changes.

Drill Down & Across Reporting

This guide details how ADempiere’s architecture automatically provides a reporting function on all tables of information in the system that is accessible to a User. The Reporting functionality in turn provides the functionality to enable export of information to a variety of formats including spreadsheet formats.

In ADempiere this reporting capability is referred to as “Drill-Down” and Drill-Across” functionality. Knowledge of this functionality is fundamental to the effective use of ADempiere.

Manual Bank Reconciliation

The purpose of this document is to explain the process of manual bank reconciliation in the ADempiere ERP system. By manual bank reconciliation we mean either where the Payments have already been entered into the system by manual posting, Payment Selection for paying vendors in bulk or importing from a CSV or similar downloaded from your bank. It is also possible to create payments by code by creating your on bank statement import class. This case is not considered in this document.

Reconciliation Module

This guide explains how Adempiere uses a series of clearing accounts in the processing of documents. Examples of these clearing accounts are:

  • Bank-in-Transit
  • Payment Selection / Unallocated Customer Receipts
  • Goods Received but not invoiced
  • Goods invoiced but not received
  • AP and AR control accounts.

The characteristic of these accounts is that a debit will be created in the suspense account and at a later date/time a matching credit will be created clearing the balance back to zero. In some case the credit is created and followed by a debit. The balance of the account at any time will consist of those transactions for which the offsetting transaction had not been posted at the selected date, or both are posted and there was a mismatch in the values. In clearing accounts with many transactions it can be quite complex to determine which transactions form the balance of the account. This module is designed to simplify these reconciliation tasks.

Non-Vendor Payments

This HowTo guide describes the way in which Adempiere ERP & CRM can be used to process non-inventory related payments. Many expenses and some revenues will appear in the company’s accounts that do not relate to inventory purchases. These exepnses (and some revenues) will typically affect accounts unrelated to inventory. Examples of such transactions are Payroll transactions, Dividends, BAS and Income Tax Payments, Transfers between bank accounts, Loans from parent companies and utility bills. Payments which are not inventory purchases will typically be allocated to a Charge.

Credit Card Transactions

This how-to document suggests a number of ways of managing the processing of credit card transactions in ADempiere. Credit Card transactions can occur due to employee expenses, paying vendors by credit card and receiving customer payments by credit card. Each of these processes is explored. Credit Card transactions raise a series of issues by employers which can be addressed in a number of ways. The most common issue is a need to pay the credit card company before an employee has provided all the details of the amounts spent. Companies adopt a number of methods to deal with this issue.

Foreign Currency Payments

This document explains the process used in ADempiere to enter and pay foreign currency Invoices ($USD in this example) from a bank account that is denominated in the system accounting currency ($AUD in this example).

Housekeeping and Month End Processes

The purpose of this document is to details the specific tasks that typically have to be completed for month-end close of an accounting system. All systems require a degree of administrative effort to ensure that they are running properly. The task typically falls to accounting staff since they will be the ultimate users of information that is generated by the actions and inactions of users of the ADempiere system. This document outlines some of the tasks that need to be undertaken to ensure that the system is running properly and that the accounting information is up to date.

Payment Selection

The purpose of this HowTo guide is provide instruction on the concept of ‘Payment Selection’ which allows for Adempiere to pay a batch of invoices due via automated processes determined by business rules such as payment terms, dispute status or manually.

Reporting and Listing Improvement

Adaxa has extended ADempiere reporting in the Financial report writer and List Report Writer.

Adaxa Revenue Recognition – Statement of Capabilities

Adaxa has implemented Revenue Recognition for both Time and Event based recognition requirements.