Reconciliation 

Use

Item-generating external and internal systems (such as payment transactions, settlement, and payment orders) supply posting items that are then processed in Account Management (AM) in the following two steps:

·        The item is posted on the account in AM.

·        The item is transferred to the general ledger if the General Ledger Transfer component is active, (usually cumulated with other items).

Note the following special constellations:

·        As a result of material posting problems, an item is not posted directly on the account, but set to status In Postprocessing. At this time this item can be irrelevant (ordering-side postings) or relevant (recipient-side postings) for the general ledger.

·        An item from postprocessing is posted or finally rejected.

Additionally, postings are triggered on the general ledger from AM that do not result in a balance change in AM (non-balance-changing postings, accrual/deferral postings, general ledger group changes, individual value adjustments and so on).

Integration

Archiving

You can specify whether reconciliation data is archived or deleted physically (deletion object RECONC) from the database once a certain period of time has expired.

You can display archived reconciliation data by choosing Account Management ® Archiving ® Data Deletion ® Reconciliation Data (Archiving object RECONC) from the SAP Easy Access screen.

For more information on archiving, see Data Archiving in Account Management (FS-AM).

Requirements

You need to provide a statement of the following operations on each posting day to adhere to the regulations of orderly accounting:

·        All items transferred to Account Management have either been posted or placed in postprocessing, provided that they have not been explicitly rejected. AM does not log postings that were rejected during the posting attempt. This is the responsibility of the supplying systems (such as feeders).

·        All posted items have changed the balance of an account in AM. (Items in postprocessing do not change an AM account)

·        For every changed balance in AM, a corresponding posting on the G/L account has been triggered on the general ledger.

·        For every posting to a balance sheet account, a corresponding offsetting posting has been triggered on the general ledger.

·        All non-balance changing postings have been accepted by the delivering internal systems.

·        All postings triggered for the general ledger have been duly and properly transferred.

Prerequisites

Reconciliation can only take place to the extent that the feeder systems and the general ledger supply or process the required data.

Scope of Functions

The statement proving the completeness of end-of-day processing is provided on the basis of various logs (see Arrival and Processing in Account Management).

Reconciliation between the logs is based on sub-totals and overall totals. The overall total is substantiated by the subtotals, and the subtotals are substantiated by the single items.

The balance follow-up check is a check routine at single account level; errors are logged.

Structure of the reconciliation of the daily turnovers

 

The data is initially reconciled in these blocks based on the overall totals of the posting day, and separated by currency and the debit/credit indicator. If there is a difference, you can then drilldown in the hierarchy to the level of the individual components within the reconciliation units.

A journal is also available.

 

The following options are available for the reconciliation of general ledger and subledger (balance calculation):

·        Inventory

For the inventory, the system determines the balances of the AM accounts (positions) on a key date and, if applicable, compares them with the values posted on the general ledger. For more information, see Determination of Balances by Inventory in the SAP Library.

·        Legacy data transfer

For legacy data transfer, the system determines the account balances (positions) existing on a go-live date of contracts and transfers them to the general ledger. For more information, see Determination of Balances for the Legacy Data Transfer in the SAP Library.

In both cases, the system calculates the balances separately according to currency and business area. To improve performance for the calculation and evaluation of the balances, even if large datasets are involved, the process is divided into data collection and data evaluation. Due to the large data quantities, you need to run the data collection. You can evaluate the calculated balances by using an online evaluation report.