Configuring Tungsten AP Essentials for use with Microsoft Dynamics AX 2012

The integration configuration proposes a default approver that is used for invoice registration and approval; however, you can override this value using a custom field. This way, you can modify the approver during verification.

To utilize this feature, add a custom field to the document type and use these settings in the Add header field view:

When Accept empty value is selected and the field is empty (during verification), the integration uses the value specified in the Default approver setting.

The integration configuration proposes a default sales-tax group that is used for invoice registration; however, you can override this value using a custom field. This way, you can modify the sales-tax group during verification.

To utilize this feature, add a custom field to the document type and use these settings in the Add header field view:

When Accept empty value is selected and the field is empty (during verification), the integration uses the value specified in the Default sales tax group setting.

The integration configuration proposes a default sales-tax group that is used for invoice registration; however, you can override this value using a custom field. This way, you can modify the sales-tax group during verification.

To utilize this feature, add a custom field to the document type and use these settings in the Add header field view:

When Accept empty value is selected and the field is empty (during verification), the integration uses the value specified in the Default item sales tax group setting.

By default, the Dynamics AX integration uses the Dynamics AX system date as the posting date; however, you can override this value using a custom field. If you leave the custom field empty, or if you do not create the custom field, the Dynamics AX system date is used as the posting date.

To utilize this feature, add a custom field to the document type and use these settings in the Add header field view:

When Accept empty value is selected and the field is empty (during verification), the integration uses the value specified by the Posting date custom field. If the Posting date field is missing or not set, the current system date is used.

The Dynamics AX integration configuration specifies a default voucher description template; however, you can override this value using a custom field. This way, you can modify the voucher description during verification.

To utilize this feature, add a custom field to the document type and use these settings in the Add header field view:

When Accept empty value is selected and the field is empty (during verification), the integration uses the value specified in the Journal description template setting.

The Dynamics AX integration supports invoice coding for these types of invoices:

• General Ledger - for invoices that require account coding.
• General Ledger with projects - for invoices that require account and project coding.

You must specify an Account type for each invoice type you want to process. You do not need to specify an account types that you do not use.

Use this account type for coding general-ledger invoices. Users who code general-ledger invoices specify the account number and the other information such as the sales tax group, item sales tax group, dimensions etc.

When you add and account type for general-ledger invoices, use these settings in the Account type view:

Use this account type for coding general-ledger invoices with projects. Users who code general-ledger invoices specify the project number and the other information such as the sales tax group, item sales tax group, dimensions etc.

When you add and account type for general-ledger invoices, use these settings in the Account type view:

The Workflow service settings described in this section deal with coding fields. Do not confuse these fields with invoice fields.

The Dynamics AX integration supports coding fields such as:

• Sales Tax Group
• Items Sales Tax Group
• Coding dimensions
• Text

The Dynamics AX integration configuration proposes default sales-tax groups. The default value can be overridden for approval on a specific coding row using a coding field. This way, you can modify the sales-tax group for a specific coding row during approval.

This coding field can be used for general-ledger coding and general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

The Dynamics AX integration configuration proposes default item sales-tax groups. The default value can be overridden for approval on a specific coding row using a coding field. This way, you can modify the item sales-tax group for a specific coding row during approval.

This coding field can be used for general-ledger coding and general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

A standard Dynamics AX integration supports three dimensions: Department, Center and Purpose. If you require additional dimensions that correspond to other dimensions in Dynamics AX, you can add a coding field for each dimension that you require using the settings in the Coding field dialog described below.

This coding field can be used for general-ledger coding and general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

The Dynamics AX integration configuration specifies a default voucher description template that is used during invoice registration; however, you can override this value on a specific coding row using a coding field. This way, you can modify the voucher description on a certain coding row for approval during coding.

This coding field can be used for general-ledger coding and general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

When Accept empty value is selected and the field is empty (during approval), the integration uses the invoice registration value that is created from the configuration template.

The Dynamics AX integration can set the project category for a specific row. In Tungsten AP Essentials, the value can be defined on a specific coding row using a coding field. This way, you can specify the project category for a specific coding row during approval.

This coding field can only be used for general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

The Dynamics AX integration can set the project employee for a specific row. In Tungsten AP Essentials, the value can be defined on a specific coding row using a coding field. This way, you can specify the project employee for a specific coding row during approval.

This coding field can only be used for general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

The Dynamics AX integration can set the project line property for a specific row. In Tungsten AP Essentials, the value can be defined on a specific coding row using a coding field. This way, you can specify the project line property for a specific coding row during approval.

This coding field can only be used for general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

The Dynamics AX integration can set the project sales currency for a specific row. In Tungsten AP Essentials, the value can be defined on a specific coding row using a coding field. This way, you can specify the project sales currency for a specific coding row during approval. If you do not specify a value for the project sales currency during approval, the default value from the currency field is used.

This coding field can only be used for general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

The Dynamics AX integration can set the project sales price for a specific row. In Tungsten AP Essentials, the value can be defined on a specific coding row using a coding field. This way, you can specify the project sales price for a specific coding row during approval. If you do not specify a value for the project sales price during approval, the default value from the amount field is used.

When coding, the value must be formatted using a period as the decimal separator. For example: 0.00

This coding field can only be used for general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

The Dynamics AX integration can set the project sales tax group for a specific row. In Tungsten AP Essentials, the value can be defined on a specific coding row using a coding field. This way, you can specify the project sales tax group for a specific coding row during approval. If you do not specify a value for the project sales tax group during approval, the default value from the sales tax group field is used.

This coding field can only be used for general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

The Dynamics AX integration can set the project item sales tax group for a specific row. In Tungsten AP Essentials, the value can be defined on a specific coding row using a coding field. This way, you can specify the project item sales tax group for a specific coding row during approval. If you do not specify a value for the project item sales tax group during approval, the default value from the item sales tax group field is used.

This coding field can only be used for general-ledger coding with projects.

To use this feature, add a coding field and use these settings in the Coding field view:

Coding lines are required must be selected to make sure the user codes at least one row.

Allow balancing against total amount must be selected to enforce coding amount validation and enable amount-split assistance.

The balancing amount field depends on the Approval journal configuration in Dynamics AX. The approval journal setting, Amount includes sales tax, in the Sales tax section of your coding, determines whether you balance against the net or gross amount:

• If Amount includes sales tax is not selected (recommended), you balance against the net amount.
• If Amount includes sales tax is selected, you balance against the gross amount.