Christina Florinet Business and System Analyst

The Excel Add-In for Free text invoice (Free Text Invoice Entity template) does not have the field Reason code available for insert to the template.

The implication is that Free Text Invoice Excel Add-In cannot be used for Fixed asset sale, for companies having mandatory reason code configuration.

This idea is for adding the Reason code in the standard Excel Add-In template - or making the Reason code available for users to add to the template using the Desig mode.

The following reports can be used for general ledger and sales tax analysis, by selecting sales tax specification when generating the reports.

Tax - Inquiries and reports > Sales tax reports > Sales tax specification by ledger transaction and

General ledger > Inquiries and reports > Ledger reports > Transaction list by date > select option "Sales tax specification"

These reports are designed to display transactions that are directly related to posted sales tax. Consequently, when the sales tax specification option is selected, only general ledger transactions associated with tax transactions are included in the report. Essentially, this means that the report will only display a portion of the voucher.

Here’s an example of a typical business scenario not covered by the current report design:

When a discount (percentage or amount) is applied to a sales order line, the main account used for posting the discount is not included in the report because the discount transaction type does not have an association with tax transactions. As a result, the reports do not accurately reflect the sales tax base.

Suggested improvement is to remove the filter that limits the data to tax-related transactions and include all transactions, even if the sales tax amount is not directly shown on the transaction itself.

When creating an automation process for ledger settlements, users can define criteria to automatically match general ledger debit and credit transactions. The main account and posting layer options are required matching criteria. Additionally, financial dimensions and financial tags can be included as optional matching criteria.

However, there is currently no option to exclude transactions that lack values in Financial dimensions or Financial tags. As a result, transactions with empty values are being incorrectly matched and settled.

This proposal suggests adding the ability to exclude blank values in Financial dimensions and Financial tags from the matching process.