Programmer Notice

From AutoCount Resource Center

Programmer Notice

AutoCount Accounting 2.1

AutoCount Accounting 2.1 API - Updated: 6/1/2023
  • Added important knowledge regarding TaxCode and TaxRate for 2.1
  • Added note to "Assemblies Filename Changed"

AutoCount Accounting 2.0

AutoCount Accounting API Update - 13/4/2022
  1. Runtime error when use "MultiPricing" column in the object of documents, such as Invoice.
    The new column name is "MultiPrice".
  2. Credit Limit Control and Overdue Limit Control will not invoke credit control events, if the document does not violate the limit.
    Credit Control Event from this release can be used only when programmer wishes to override system rules if the document has hit limit control.
    View topic on how to override limit control.
  3. CEF components (version 99.2.14)
    Plug-in project that has implemented CEF components and for Singapore users,
    suggest to use CEF version 99.2.14 to prevent version conflict which this version is used in Seamless Filing and IRAS GST F5 Returns.
    Furthermore, plug-in builder does not have to include the CEF components in the plug-in package,
    as this API can check for the CEF component and download the component if it is not installed.
   //Requires AutoCount Accounting or higher to implement "LoadCefComponent()"
   if (!AutoCount.Components.Components.LoadCefComponent())
       //Exit or throw exception if load/download CEF component failed.
       return false;

AutoCount Accounting API Updated in - 14/4/2020

7 new dll have been added to better manage system resources.

These assemblies are required when your project has reference to AutoCount Accounting 2.0 UI object.

AutoCount Plug-In Builder is available for download - 31/12/2020
Click here to download page
AutoCount Accounting - 30/12/2020
Plug-In is required to specify the Developer's Company email at the constructor of the Plug-In.
This is to allow the developer to be informed of the exception that was thrown from the plug-in.
Exception: Method not found: 'Void AutoCount.PlugIn.BasePlugIn..ctor(System.Guid, System.String, System.String)'.)
Solution: at the constructor of the plug-in, add email to the new parameter.
   public PluginInitialize() : base(new Guid("<<Put your product Guid here>>"), "My First Plugin", "<<Plugin Version>>", "<<Company/Developer email>>")

Requires DevExpress 19.2.10
Add this line in the constructor
Plug-In Builder is released for AutoCount Accounting and higher
Version plug-in builder can be used to build earlier version of AutoCount Accounting 2.0 plug-in.
Separate installed folder is not required.
Click here to go to download page
AutoCount Accounting Plug-In update
Plug-In is required to specify the DevExpress version for this plug-in at the constructor of the Plug-In.
AutoCount Accounting
This release requires DevExpress 19.2.7, which you may find the installer on Download page.
AutoCount Accounting has major API update in GL/AR/AP.

DLL added:
DLL removed:

Remove of AutoCount.CommonAccounting.dll does not implicate that classes that were in AutoCount.CommonAccounting.dll are removed.
To better organize the naming, UI and logic, system engineer and analyst have rearranged and split them into two libraries.

AutoCount Accounting is released to compliant with GST 0% SR
There is no major changes in API compatibility for project uses API
But, do rebuild with assemblies to confirm the compatibility.

AutoCount Accounting 1.9

Upgrade from AutoCount Accounting 1.8 to 1.9 requires a special license key.

However, if create a new account book in AutoCount Accounting 1.9.6 and higher version,
you will be able to use the account book for development & testing without requirement of License Key.

AutoCount Accounting 1.9 is compatible with AutoCount Accounting 1.8.

Some coding may require minor update, due to earlier version of 1.8 has some differences in method call.
Such as SubProjectStartup parameter has been updated since version 1.8.30.
Click here to see the changed in SubProjectStartup method.


This document does not allow to save, because it contains accrual and payment basis tax code
When you see the message prompted similar to the title,
this is to accommodate the new SST calculation of Sale Tax and Service Tax,
which Sale Tax is on "Accrual Basis", while Service Tax is on "Payment Basis".

  • Accrual Basis is defined as, Sales Tax is payable when the invoice is created.
  • Whereas, Payment Basis is after payment is received from customers for Service Tax.
    However, if the payment is not received after 12 months,
    it becomes payable regardless of whether the payment is received.

The difference between the two methods is the timing to recognize Payment Basis as Tax is deffered until
payment is received, or 12 months period.

Therefore for AutoCount Accounting to recognize these two occurrence whether it is payable tax,
separating them to two documents can clearly differentiate them in the finance and tax report.

Posted on 6 Sep 2018

Go to menu

Go to top
Resources For AutoCount Software Developers