When defining an Account Code format it is possible to specify additional Option Attributes against 1 or many of the account code parts in a format. The flexible Attributes allow the community to store additional values against the account code Part. When a user selects account codes in the checkout the system also records the associated Attribute value(s) against an account code part for use within reporting or the customer ERP (see examples).
Note: End users cannot view or select attributes. It is only additional data captured when they code accounting on requisitions.
Example
This example Account Code has the Parts: Cost Centre and Account.
Cost Centres have different tax classifications so the community creates an Option Attribute of Tax_Class (see below). An additional column will appear in the Account Code upload template and the community then uploads the different tax classifications against each Cost Centre in the Tax_Class column.
When the Cost Centre '2' (Charitable Trust) is selected, the Tax_Class of 'FREE' is also recorded. This can then be used in the customer ERP to determine how they apply tax against this Cost Centre.
Other examples
Option Attributes can be used for anything, however a common use is to identify CAPEX versus OPEX expenditure. To do this an Attribute of CAPEX could be added to the appropriate account code part and the community would upload their account codes with a CAPEX Y/N flag to easily record if spend was classified as CAPEX. This removes the need for end users to have knowledge of CAPEX/OPEX items.
Defining Option Attributes
Add an Option Attribute in the Account Code Part definition and give it a Name. There can be many for an Account Code Part.
Upload the Option Attribute values as part of the Account Code upload.
Part | Parent | Value | Description | Tax_Class |
Cost Centre | 1 | Business | FULL | |
Cost Centre | 2 | Charitable Trust | FREE | |
Account | A | Products | ||
Account | B | Services |