Tax Transaction Change Management
A major improvement is implemented in this version of AutoCount Accounting. Previously, when the GST Processor has processed the GST Return for a period, the period lock mechanism is employed to lock the related documents to prevent from accidental modification that may cause issues with the correctness of the document. As such if the user is required to modify some parts of a document that is locked, they are required to manage the period lock exception. While this in itself is easy to apply, an issue may arise in that with the period lock exception being open, any other modification could occur on other documents, and these changes might be accidental. To prevent such issue from ever occurring as well as giving users more flexibility, a new mechanism is now implemented to help with this situation.This mechanism is known as the Tax Transaction Change Management. The Tax Transaction Change Management works as a safeguard mechanism to protect the tax transaction that has been processed by the GST Processor. This mechanism works by comparing the changes being done to the document containing the tax transaction with its original version and assigning a severity level on each of the changes done. The highest severity level of all the changes done will then be the severity level assigned to the changed document. If the user making the changes have the correct access right level to save the changes, he or she will be allowed to save the changes done to the document. If the user does not have the access right level to do so, the changes will not be saved and the document will revert to its original condition. The level of severity that is assigned to changes are as follows; Low, Medium and High.
The following series of images shows how the system will prompt the user when the user has modified a document that contains a severity level. Note: if the user did not received any prompt when saving a modified document with tax transaction, this means that the modification done does not impact the tax transaction itself and is safe. As such the Tax Transaction Change Management mechanism will not trigger any prompts to the user and the save operation will continue without any other input from the user.
The following table illustrate the type of action as well as its severity level.
Action on document with tax transaction | Condition | Severity | ||
---|---|---|---|---|
Low | Medium | High | ||
Insert or Delete | Tax Code is ‘OP’ or ‘OS’. | True | ||
All other Tax Code | True | |||
Modification | Change on the following fields:
| True | ||
Change between tax code ‘OP’/’OS’ to empty tax code and vice versa. | True | |||
Change on the following fields:
| True |
To help users manage and track the changes done under this mechanism, a new report is also introduced. This report is named as Tax Transaction Change Tracking Report and it will display the changes done, the severity of the changes as well as who did the change.
Added Tax Code and Transaction ID fields in Ledger Report.
Two new fields is added into the Ledger Report. The two fields added are Tax Code and Transaction ID.New Fields in Sales, Purchase, ARAP and GL.
A few new fields are added into the documents in the Sales, Purchase, ARAP and GL module. These columns are localtaxableamt, taxcurrencytax and taxcurrencytaxableamt which is used to store some of the previously calculated values into the database. The Local Taxable Amt field is also added into the Tax Transaction Audit Trail report.GST Detail in Cash Book and Journal Entry
In an effort to make it easier for user to enter the GST information in both Cash Book and Journal Entry as well as reducing the number of columns for the information, a new button is introduced under the column GST Detail. The user can just click this button to enter the following GST information on a separate dialog;- Business Name
- Business Registration Number
- GST Registration Number
- GST Permit Number
- GST Export Country
- GST Reference Number
- Bill Date for GST
No comments:
Post a Comment