Work with Reconciliation Views

A reconciliation view is used to setup customer specific parameters for building and analysing of the Inventory valuation and reconciliation of sub ledgers with the general ledger. In the window Reconciliation View you can define the template with which the reconciliation between the sub administration and the general ledger can be analysed. The reconciliation view is comparable with the standard Dynamics NAV Analysis View functionality.

Follow the setps below top create a Reconciliation View:

1. Open the window Reconciliation View by selecting Departments - Compliance - Control - Reconciliation - Inventory Reconciliation - Reconciliation View.
2. Press Ctrl+N to create a new reconciliation view.
3. Fill the fields on the FastTabs:

FastTab General

• Code: Enter a suitable short name for the reconciliation view. Preferably base the name on the setup handled further this instruction.A possible code to use is RECONCILIATION (Dutch: AANSLUITING).
• Type: Select the type Inventory Reconciliation.
• Name: Enter a clear description for your reconciliation view.
• Select the smallest period to which the inventory data should be reconciled in the field Date Compression. You can choose Day, Week, Month, Quarter, Year or Period. The entries will be compressed with the selected level. Mostly the inventory will be reconciliated by month or accounting period.
• Starting Date and Ending Data: These fields are only applicable for type Inventory Analysis.
• Determine Used Accounts: Check this field if you want to perform the reconciliation based on historical postings (how is really posted). Do not check this field if you only want to analyse the reconciliation based on the current setup.
• Blocked: Check this field if a reconciliation view should not be updated anymore.

FastTab Update

• Show Progress: Check this box if you want to see the progress during the update. * Attention: this can decrease performance.
• Automatic Calc Analysis: If this box is checked, Dynamics NAV automatically calculates the data with the last set filters after updating the reconciliation view.
• Process with Job Scheduler: With this option it is possible to automatically update the reconciliation view with the job scheduler with Codeunit 11111990.

FastTab Dimensions

Define (optional) up to 4 dimensions that you want to use for the set reconciliation posts.

FastTab Attributes

These attributes are used for report purposes. Define on this FastTab customer, supplier and item attributes. The attributes set in this FastTab are only available in the Value Reconciliation Entries.

To analyse the reconciliation between the sub administration and the general ledger, the reconciliation view has to be built completely the first time you want to analyse. After this you can update the reconciliation with the latest entries to be able to analyse the most actual data.

Note!

• Depending on the size of your database, the initial update of a reconciliation view can take a long time.
• There is a timing difference in updating: the G/L Entry is updated first and the Value Entry second. Posting documents during building the reconciliation yields values in the sub administration which are not present in the G/L. This cannot be solved in environments with continuously posting. Best practice is to analyse only for already closed periods (..P-1).

1. Open the window Reconciliation View.

2. Select Related Information, Update and select All. The reconciliation view is build. If you checked the option Show Progress you can see the progress during the calculation. When the updating is finished, you can analyse the reconciliation in the windows Analysis Inventory Accounts and Analysis Applied Accounts.

3. The reconciliation view contains an amount of (non-editable) information field.

• Last Date Updated VREand Last Date Updated GRE: the date of the latest update of the reconciliation view.
• Last Value Entry No.and Last G/L Entry No.: the numbers of the last updated entries respectively.
• No. of Skipped Value Entriesand No. of Skipped G/L Entries: shows how many entries are skipped respectively. These entries could not be processed by module Inventory Reconciliation, because they were not created according to the standard logic of Dynamics NAV.

Follow the steps below to update the reconciliation view:

1. Open the window Reconciliation View.

2. Select Related Information, Update and select From Last Entry. The reconciliation view will be updated from the last updated entry. If you checked the option ‘Show Progress’ you can view the progress during the calculation. When the updating is finished, you can analyse the reconciliation in the windows Analysis Inventory Accounts and Analysis Applied Accounts.

3. The function Update has the following options:

• From Last Entry: Updates the reconciliation view from the last updated entry. With the first update, the reconciliation view will be updated from the first entry.
• All: Updates all entries in the reconciliation view. Attention! If reconciliation views are already updated once, the existing entries will be deleted and all entries will be updated again.
• Attributes: Updates all entries with the currently set up properties on the FastTab Attributes.
• Setup Accounts: Updates all entries with the current posting setup (only applicable if posting setup has changed).
• Analyses: Updates the analyses for the windows Analysis Inventory Accounts and Analysis Applied Accounts, based on the added filters.

Note! Depending on the size of your database, the initial update of a reconciliation view can take a long time.

4. The reconciliation view contains an amount of non-editable fields:

• Last Date Updated VREand Last Date Updated GRE: are filled with the date of the latest update of the reconciliation view.
• Last Value Entry No.and Last G/L Entry No.: are filled with the numbers of the last updated entries respectively.
• No. of Skipped Value Entriesand No. of Skipped G/L Entries: shows how many entries are skipped respectively. These entries could not be processed by module Inventory Reconciliation, because they were not created according to the standard logic of Dynamics NAV.