Integration Methods

From AutoCount Resource Center
Revision as of 02:50, 23 August 2023 by DanielY (talk | contribs) (→‎Bridging and Interface with API)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Introduction

.Net Framework

AutoCount Accounting is developed on Microsoft .Net Framework that the assemblies of AutoCount Accounting can be added as reference into the project of which the project is built on the same framework as AutoCount Accounting.

.NET Framework includes the Common Language Runtime (CLR). It serves as the execution engine of .NET Framework and offers many services such as memory management, type safety, exception handling, garbage collection, security and thread management. All programs written for .NET Framework are executed by the CLR.
Programs written for .NET Framework are compiled into Common Intermediate Language code (CIL), as opposed to being directly compiled into machine code. During execution, an architecture-specific just-in-time compiler (JIT) turns the CIL code into machine code.
https://en.wikipedia.org/wiki/.NET_Framework

Planning for Integration

When two systems to be integrated are on different platforms, external data media or application interface is developed to execute data transfer and conversion between two systems.
Whether the data transfer is executed on local network or via internet, data format is crucial to how data is carried from one system to another system.

Commonly known data format are csv, excel, xml and JSON.


Deciding which is the best solution for the integration of two applications can be challenging when the integration points were undetermined or the business flow for the integration is not clear.

The decision can be factored into:-

  1. Business Flow and Integration points
  2. Programming language that is used
  3. The size of data
  4. Data transfer frequency
  5. Connection Stability
  6. Hardware requirements and infrastructure
  7. Maintenance
  8. Time needed for development
  9. Cost of development


Common Integration with AutoCount Accounting

Plug-In (API)

Plug-In is a program that run as an attach process to the parent application, which the parent application is AutoCount Accounting.
Write a plug-in for AutoCount Accounting that will perform batch update of transaction or data into account book. Though this method of integration requires user interaction, it allows user to verify the data before insert/update to the account book.
This reads data from the source, and write data to AutoCount Accounting by using AutoCount Accounting API.

AutoCount Accounting assemblies can be found in the application folder.
The default path to AutoCount Accounting assemblies is "C:\Program Files\AutoCount\Accounting\".


If the plugin that attached to current account book (Account Book A) has to write transactions or data to another account book (Account Book B), “API Module” license is required.
Download Plug-In Training sample
for AutoCount Accounting 1.8.27

Features in training sample:

  1. Load data from Excel file directly
    • Support specific columns structure only
  2. User Interface that implement AutoCount Skin Style
  3. Write to Sales Invoice and create AR Payment with knockoff invoice
  4. Create missing Debtor or Item in Sales Invoice
  5. Check for Modules that is supported in this account book (eg. Project, Scripting)
  6. Access Rights control
    • Control user rights
  7. Add custom table
    • Create your own table in the database by executing embedded resources.

Download Training Sample

Direct Access to AutoCount Accounting API (.Net Framework)

With .Net Framework, programmer is able to include and make reference to AutoCount Accounting assemblies (dll). The source data is loaded by an executing application, it directly write transaction to AutoCount Accounting using AutoCount Accounting API. Same as the “Integrate Program”, “API Module” license is required. For web application, Developer License Key is not supported.

Bridging and Interface with API

Develop a standalone application to act as an interface to transfer data between two systems.
By using this method, the target account book of AutoCount Accounting requires "API Module" for the 3rd party to integrate with the API.

Integrate via AOTG Gateway

Integration via AOTG cloud server allows web developers to call AOTG API to transfer or share data between AutoCount Accounting and your system.

Please see Introduction to AOTG API,
and Begin AutoCount Accounting Integration via AOTG API


Integrate via Common Data Format

Import 3rd Party XML File

This method is to extract data from your system and write the source to XML Data file. The XML structure must be according to the structure defined by AutoCount Accounting system.

XML Schema specification, guideline and samples can be downloaded.
Download XML Samples & basic XML Schema


Customer is required to enquire “Import 3rd Party XML” module, in order to load & import the xml data.

Developer may test the import with “Unregistered Account Book”, as long as the database has not reach 500 transactions.

Import from Excel (Sales & Purchase, Stock, A/R & A/P) with AutoCount Excel Import

This method allows user to import data into AutoCount Accounting via Excel data file.
It supports “columns mapping” for Excel Columns and AutoCount Accounting Data Fields.
Furthermore, it supports “Code Conversion” of debtor, creditor and item.

Go to menu

Go to top
Resources For AutoCount Software Developers