Wednesday, August 12, 2015

Download Final Release for Accounting (1.8.16.124)

The following is the download links to download AutoCount Accounting ver 1.8.16.124.

AutoCount Accounting 32-bit: http://autocount.blob.core.windows.net/accounting/AutoCount%20Acc%20Setup-1.8.016.124.exe
AutoCount Accounting 64-bit: http://autocount.blob.core.windows.net/accounting/AutoCount%20Acc%20×64%20Setup-1.8.016.124.exe
AutoCount Express 32-bit: http://autocount.blob.core.windows.net/accounting/AutoCount%20Express%20Setup-1.8.016.124.exe
AutoCount Express 64-bit: http://autocount.blob.core.windows.net/accounting/AutoCount%20Express%20×64%20Setup-1.8.016.124.exe
The following is the download links to download AutoCount POS ver 3.0.12.87. (This version supports season code license.)
The following download links are provided for convenient.
AutoCount USB Key Server (version 1.5): https://onedrive.live.com/download?resid=7C414A0BD12F8388%215440
AutoCount Backup Server (version 1.8.11.3): https://onedrive.live.com/download?resid=7C414A0BD12F8388%215441

Introduction

This version of AutoCount Accounting is a maintenance release for version 1.8. Some of the improvements implemented in this version are:
  1. Enhancement in the previous rounding method.
  2. Addition of Inclusive field in Cash Book and Journal Entry detail.
  3. 30 Days Advanced Payment Warning.

Improvements Introduced

Enhancement in the previous rounding method

In an effort to produce a more accurate and consistent figures, the rounding methods available in AutoCount Accounting has been updated. The update has upgraded the Whole Document Rounding Method to version 3 and the Line by Line Rounding Method to version 2. The reason for this enhancement is due to the fact that there is some inaccuracy and inconsistency in figures generated for inclusive tax documents. For example:
The following image is shows the inconsistency found between the document and the transaction detail screen when comparing the values generated by the Whole Document Rounding version 2.
There is a difference of 1 cent in the figures generated in the document when compared to the figures in the transaction details
There is a difference of 1 cent in the figures generated in the document when compared to the figures in the transaction details
In the following image, the previous inconsistency is no longer observed when using the Whole Document Rounding version 3. With the new update, both the figure in the document and the transaction detail screen is now consistent and is no longer inaccurate.
The difference is no longer observable  after using the Whole Document Rounding Method version 3
The difference is no longer observable after using the Whole Document Rounding Method version 3

Addition of Inclusive field in Cash Book and Journal Entry detail

A new field is added into both the Cash Book Detail and Journal Entry Detail entry. This field, Inclusive Tax, is added to allow users the capability to simultaneously enter multiple bills of exclusive and inclusive tax type together in one Cash Book or Journal Entry document. To access this field in the respective document entry, the user must drag out the Inclusive Tax column via the Column Chooser menu (accessible by doing a right click on the column header inside the document entry window).
The Inclusive Tax column in the Column Chooser
The Inclusive Tax column in the Column Chooser
The Inclusive Tax column in action inside a Journal Entry document
The Inclusive Tax column in action inside a Journal Entry document
This field is by default controlled by the Master document Inclusive Tax option. As such, if the user changes the master Inclusive Tax option, all detail Inclusive Tax will follow the changes done to the master option. This is also observable when a new detail is added as the new detail will also follow the master inclusive tax option when created. It must be noted that while the master inclusive tax option controls the detail options, the calculation is still based by the detail as if the user changes the detail inclusive tax to be different from that of the master option, the calculation will be change to reflect that change.

30 Days Advanced Payment Warning

A new feature has been added into this version of AutoCount Accounting. This feature, 30 Days Advanced Payment Warning, will cause a warning to be prompt when users try to save an A/R Receive Payment document that is used to knock-off an Invoice that has its document date or knock-off date greater than 30 days of the A/R Receive Payment document date. To access this option, just navigate to the Tools -> Options -> Goods and Services Tax.
The 30 Days Advanced Payment Warning option
The 30 Days Advanced Payment Warning option
The warning message that will be prompt when user try to save the document that violates the 30 days rule
The warning message that will be prompt when user try to save the document that violates the 30 days rule

Bugs Fixed and Minor Enhancement

Among the newer bugs fixed and minor enhancement introduced in AutoCount Accounting version 1.8 are:
  1. Enhancement: Add GST Bank Recon reminder message.
  2. Enhancement: Add Imported Goods record in Tax Transaction Audit Trail report.
  3. Fix Bug: Fix wording issue in Confirm Change Tax Trans form.
  4. Enhancement: Change Ctrl+Alt+G shortcut key for GST Instant Infor to Ctrl+Alt+5.
  5. Enhancement: Add ToTaxCurrencyRate to all ARAP and GL Import from Excel template.
  6. Fix Bug: Fix UDF memo type can’t display during view transaction.
  7. Enhancement: Replace TaxableAmt to LocalTaxableAmt for Tax Transaction Audit Trail Report.
  8. Enhancement: Add drill down control for Bank Reconciliation report.
  9. Fix Bug: Fix Stock Detail Listing report Filter Option display error.
  10. Enhancement: Add declaration date for GST Processor.
  11. Fix Bug: Fix bug in write upgrade exception to error log.
  12. Enhancement: Modify Tax Bill Date validation by comparing with Tax Date.
  13. Enhancement: Add write error message to error log file when upgrade account book.
  14. Enhancement: Add can change GST Date access right.
  15. Fix Bug: Correct Median wording to Medium for Tax Transaction Changed Tracking Report.
  16. Enhancement: Add drill down on Tax Transaction Listing Report.
  17. Enhancement: Modify calculate local tax adjustment for APDN.
  18. Enhancement: Extend command time out for upgrade DB.
  19. Enhancement: Use Doc Date to increase next number instead of today’s date for import excel.
  20. Enhancement: Add Self Billed Approval Number for debtor.
  21. Enhancement: Extend Self Billed Approval Number length for PI, CP, Debtor and Creditor table.
  22. Enhancement: Request to have Audit Trail for GST Processor.(ACC-2848)
  23. Enhancement: Enable summary style in submitted Journal Entry when create new account book.
  24. Enhancement: Add Tax Date filter to Tax Transaction Audit Trail report.
  25. Enhancement: Allow Tax Transaction Change Tracking form to be closed by pressing the escape key.
  26. Fix Bug: Fix unable to filter Stock Write Off when export data.
  27. Enhancement: Display tax date info when it is different with the doc date in document entry form.
  28. Enhancement: Prompt tax date form when create new document with tax code in GST Processor period.
  29. Fix Bug: Fix date filtering issue in Tax Transaction Audit Trail form.
  30. Enhancement: Support new Area Code size, from 12 to 50.
  31. Fix Bug: Fix NullReferenceException in Stock Assembly Order entry form.
  32. Enhancement: Add new whole document rounding method 3 and line by line rounding method 2.
  33. Fix Bug: Fix total of taxable amount for line by line rounding method.
  34. Fix Bug: Fix scan barcode with item batch no when merge.
  35. Fix Bug: Fix in Copy from other cash book where Source Type is not null transactions should not appear in the search list.
  36. Fix Bug: Fix sum tax transaction listing report amount grid view display.
  37. Fix Bug: Fix extra discount amount does not calculate according to Indent Group Discount.
  38. Fix Bug: Fix object is null in journal entry when processing currency rate control.
  39. Fix Bug: Fix copy to new document exclude GST Journal Entry dockey.
  40. Enhancement: Show Tax Permit No for Tax Transaction Audit Trail Report.
  41. Fix Bug: Fix issue in GST Detail window where mru items does not work properly in Cash Book Entry and Journal Entry.
  42. Enhancement: Add To / From column, this column maps to debtor / creditor name in A/R and A/P documents, or maps to Cash Book Entry’s Pay To / Receive From column, or maps to Journal Entry’s Description.
  43. Enhancement: Add negative sign to A/R CN, A/P CN, and Supply record in Journal Entry’s detail.
  44. Enhancement: Support Include Empty Tax Code option.
  45. Enhancement: Add 5 cent rounding adjustment for Quotation and Purchase Order.
  46. Enhancement: Modify C/N and D/N list finding invoice filter by Debtor or Creditor code in GST Processor.
  47. Enhancement: Add Is Inclusive Tax field in CBDTL and JEDTL.
  48. Enhancement: Add C/N Reason at A/R and A/P Payment discount.
  49. Enhancement: Add Advanced Payment 30 days rule warning for A/R Payment.
  50. Enhancement: Modify Item Package Inquiry interface to show Item Package Description.
  51. Enhancement: Add amountextax and amountwithtax column in CBDTL.
  52. Enhancement: Add Audit Trail on delete transaction for Stock Assembly Order and Stock Assembly.
  53. Enhancement: Add Bad Debt Credit Sales AccNo for posting Journal Entry.
  54. Fix Bug: Fix divide by zero exception when inquiry Item Profit Margin report.
  55. Enhancement: Enhance return cheque by posting to Tax Trans table.
  56. Enhancement: Support boolean in UDF in Import Stock.
  57. Fix Bug: Fix chkedtAccChqNo control does not bind into database.

Autocount GST Workshop Training ( 22th August 2015 )


Saturday, August 8, 2015

Improvements Introduced Version 1.8 ( Revision 123)

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 access right to allow user to save according to the severity of the changes
The access right to allow user to save according to the severity of the changes
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.
When saving a low severity change
When saving a low severity change
When saving a medium severity change
When saving a medium severity change
When saving a high severity change
When saving a high severity change
Trying to save a high severity change without access right
Trying to save a high severity change without access right
The following table illustrate the type of action as well as its severity level.
Action on document with tax transactionConditionSeverity
LowMediumHigh
Insert or DeleteTax Code is ‘OP’ or ‘OS’.True
All other Tax CodeTrue
ModificationChange on the following fields:
  1. TaxDate (in the same GST Processed Period)
  2. DocNo
  3. DocDate
  4. ProjNo
  5. DeptNo
  6. TaxableAccNo
  7. TaxableName
  8. Seq
  9. TaxAccNo
  10. Business Register No
  11. Bill of No for GST
  12. Tax Permit No
  13. Tax Export Country
  14. Detail Description
True
Change between tax code ‘OP’/’OS’ to empty tax code and vice versa.True
Change on the following fields:
  1. TaxDate (not in the same period or out of GST processed period)
  2. TaxCode
  3. Currency code
  4. Currency rate
  5. Taxable amount
  6. Local Taxable amount
  7. Tax
  8. Local Tax
True
With the addition of this mechanism, the previous period lock mechanism is no longer applied and as such when updating to this version of AutoCount Accounting, the period locks applied previously will be removed.
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.
The Tax Transaction Change Tracking Report that shows the changes done the tax transaction document by which user
The Tax Transaction Change Tracking Report that shows the changes done the tax transaction document by which user

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.
The Tax Code column in the Ledger Report window
The Tax Code column in the Ledger Report window

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;
  1. Business Name
  2. Business Registration Number
  3. GST Registration Number
  4. GST Permit Number
  5. GST Export Country
  6. GST Reference Number
  7. Bill Date for GST
Click on the button under the GST Detail column, and the dialog window to fill the information will prompt up
Click on the button under the GST Detail column, and the dialog window to fill the information will prompt up

Lampiran 2 export to excel function

Lampiran 2 export to excel function

A new function is added into the GST Return window. The function allows users to create the Lampiran 2 report which the Customs may request when the user is requesting tax refunds from them. To access this function, just open the GST Refund window and click the ‘Export Lampiran 2 in Excel’ button. The function will then generate the Lampiran 2 in excel format.
Click the button highlighted to generate the report
Click the button highlighted to generate the report
An example of the report generated
An example of the report generated

An explanation on AutoCount GST rounding algorithm

Hi, if you have seen two lines with same amount, but GST amount may be different by 1 cent in AutoCount Accounting. Don’t worry, this is correct as it is caused by the adaptive rounding algorithm used by AutoCount Accounting. Let me explain in detail how this algorithm works in the following paragraph.
Let see the following example:
Line NoQtyUnit PriceTax %GST (Unrounded)GST (Rounded)
1113.116%0.78660.79
2113.116%0.78660.79
3113.116%0.78660.79
410.006%0.00000.00
Total339.332.37

If you calculate the GST line by line and do the rounding to 2 decimal, then the total GST of the above Invoice is 2.37, however, if you use 39.33 x 6% = 2.3598 ~= 2.36, which has 1 cent different. Since most of the time, users would use total amount x 6% to calculate their GST, so we have to resolve this potential 1 cent different issue.
In order to resolve this issue, you can apply this 1 cent to the last row of the invoice, then it will become the below example:
Line NoQtyUnit PriceTax %GST (Unrounded)GST (Rounded)
1113.116%0.78660.79
2113.116%0.78660.79
3113.116%0.78660.79
410.006%0.0000-0.01
Total339.332.36

Then the weird thing is user might ask why the last line (Line No. 4), the unit price is 0.00, but why GST is -0.01.
Then in order to resolve this 1 cent issue, we have derived a rounding algorithm called Adaptive Rounding Algorithm.
The algorithm works from top to bottom.
Line NoQtyUnit PriceTax %GST (Unrounded)Prev Unrounded TotalPrev Rounded TotalGST (Rounded)
1113.116%0.78660.78660.790.79
2113.116%0.78661.57321.570.78
3113.116%0.78662.35982.360.79
410.006%0.00002.35982.360.00
Total339.332.36

The GST of line 1 is just the rounded value of 0.7866, which is 0.79.
The GST of line 2 is Round(0.7866 + 0.7866) – [line 1 GST] = Round(1.5732) – 0.79 = 1.57 – 0.79 = 0.78.
The GST of line 3 is Round(0.7866 + 0.7866 + 0.7866) – [line 1 GST + line 2 GST] = Round(2.3598) – 1.57 = 2.36 – 1.57 = 0.79.
The GST of line 4 is Round(0.7866 + 0.7866 + 0.7866 + 0.0000) – [line 1 GST + line 2 GST + line 3 GST] = Round(2.3598) – 2.36 = 2.36 – 2.36 = 0.00.
The formula is:
Round(Sum of unrounded GST from line 1 to line n) – Sum(GST from line 1 to line n-1)
By using this rounding algorithm, line 4 will not have any GST because the unit price is 0.00, however, it may make the intermediate line has weird GST value such as line 2, which has GST value of 0.78, different from 0.79 of line 1 and line 3.
But because in the end, people tends to check GST of the whole invoice instead of individual item, so we have applied this algorithm in our calculation. In other words, as long as the total GST is correct, then users don’t worry too much about the individual GST amount.
Note: This algorithm has been accepted by Singapore Iras for many years.

Saturday, August 1, 2015

Fuel prices down by 10 sen

PETALING JAYA: Retail prices of RON95, RON97 and diesel will be reduced by 10 sen a litre from midnight. Petroleum Dealers Association of Malaysia deputy president Datuk Zulkifli Mokti confirmed the drop in fuel prices. "Yes that is what is happening," he told The Star Online on Friday when asked about the 10 sen drop across the board. The new prices will see RON95 retailed at RM2.05, RON97 at RM2.45 and diesel at RM1.95 per litre. In June, prices saw a 10 sen hike across the board with RON95 selling at RM2.05, RON97 at RM2.35 and diesel at RM2.05. This was followed by another hike in July - 10 sen for RON 95 and 20 sen for RON97 with diesel remaining unchanged.

MSME Digital Grant MADANI - 1st April 2024

1st April 2024 Enquiry Email : admin@hjysolutions.com Contact No : 012-260 1655   Are You Eligible? Malaysian-Owned: MSMEs/Cooperatives must...