Skip to main content

Order of Precedence of Analysis Codes

Order of Precedence of Analysis Codes

Dimensions Only - This feature is not available in Dimensions Lite

The Analysis capabilities within Access Dimensions are very comprehensive and you can analyse at many levels within the system.

This flexibility can sometimes make it difficult to get the set up that you want, as one setting may take precedence over another. For this reason, it is sensible to start using the defaults and from there set up and test other Analyses that you require.

Similarly if everyone can make changes and set Analysis requirements, the results you expect may be altered by something that someone else has done - for this reason we suggest that ONE person only controls all Analysis settings, in this way, one change at a time can be made and recorded, and the results carefully checked to ensure that they are correct, and not overruled by another setting elsewhere.

Analysis Codes can be set in:

The Customer or Supplier VAT window Analysis Code (referred to as the Customer/Supplier default analysis code).

Each Address in the Customer or Supplier record has an Analysis Code.

Each Address entered via the Company Details window has an Analysis Code.

Each Trading Currency has a default Sales and Purchase Analysis Code.

Each Currency Rate has a default Sales and Purchase Analysis Code.

Each Price Line in the Buying and Selling Prices for each Stock record has a default Sales or Purchase Analysis Code.

Each Sub Analysis record has a default Sales and Purchase Analysis Code.

Each Price Item record in SOP and POP has a default Sales or Purchase Analysis Code.

Default Analysis Selection

The Analysis facilities help you to analyse your Purchases, Sales and other transactions quickly and easily. The logic is based on a set of hierarchical rules in which the first fitting rule (uppermost in the list below) is applied as the default.

The Currency of the transaction has to match the Analysis code in order for the rule to apply. If it does not match, then the logic of the next rule is applied.

If the Analysis Matrix is enabled, a concatenated Analysis Code must exist. If it does not, then the logic of the next non-matrix rule is applied.

e.g. if no Matrix code from Sub Analysis exists: the Matrix code from Stock Record will not be applied; the logic of the Customer Delivery Address rule will be applied.

These rules are applied separately to each Transaction Detail line.

Sales Ledger and Sales Order Processing

Rule

1

Matrix code from Sub Analysis

SOP transactions where Sales Ledger Matrix is enabled

2

Matrix code from Stock Record

SOP transactions where Sales Ledger Matrix is enabled

3

Analysis code from the Delivery Address

SOP transactions

4

Customer Invoice Address

SOP transactions

5

** Customer default analysis code

Sales Ledger and SOP Transactions

6

Analysis code from Sub Analysis

SOP transactions for Sub Analysis Stock

7

Stock/Price record analysis code

SOP transactions for Stock or Price records

8

** Sales Analysis Default

Sales Ledger and SOP Transactions

Purchase Ledger and Purchase Order Processing

Rule

1

Matrix code from Sub Analysis

POP transactions where Purchase Ledger Matrix is enabled

2

Matrix code from Stock Record

POP transactions where Purchase Ledger Matrix is enabled

3

Analysis code from the Delivery Address

POP transactions

4

** Supplier default analysis code

Purchase Ledger and POP transactions

5

Analysis code from Sub Analysis

POP transactions for Sub Analysis Stock

6

Stock/Price record analysis code

POP transactions for Stock or Price records

7

** Purchase Analysis Default

Purchase Ledger and POP transactions

** Order of precedence for Sales and Purchase Ledger transactions. These ignore multiple addresses, stock and price records.

Transaction Entry

At the point of Transaction entry you are able to manually enter an alternative Analysis if required.

If you are using the Advanced Nominal Ledger to create your own chart of accounts using segmented or cost centre coding and a category is chosen on the Header of a ledger transaction, then this takes precedence over either:

  • the default Analysis set on the customer/supplier record, or

  • the default Sales/Purchase Analysis set on the ledgers.

Further information / Tips

Transaction Keys, Costing Projects and Project Cost Centres have no default settings.

Nominal Ledger Profiles allows for automated ‘post-entry’ re-analysis.

Invoicing from Costing allows Analysis settings to be brought through from the Project Record.

Defaulting to a ‘do not use’ Analysis record forces the Users to select a specific analysis for a Detail line, effectively clearing the defaults presented.

Did this answer your question?