Our direct accounting connection plugins explained
The accounting connecting extensions and the additional platform plugin are explained in this post.
Why do we develop these accounting connect plugins?
Developing a direct, secure, and reliable accounting connect plugin for Magento 2 had been on our to-do list for some time. Many Magento webshop owners spend too much time keeping their accounts. How nice would it be if this all happens automatically and all your orders are processed immediately in your accounting package?
With that in mind, we started developing an extension. We wanted to do this differently than other accounting links that often use an external API or platform. Due to the sensitivity of the data, we did not consider this desirable. That's why we decided to make a direct connection.
We developed a basic accounting extension with sub-extensions underneath that connect directly to the API of various accounting systems like E-Boekhouden and Snelstart.
A unique, direct, and reliable link between your webshop and your accounting package. This gives you worry-free accounting and saves you a lot of time and frustration.
Direct link. On the API of the accounting package.
Updates. Always up to date due to the layered approach.
Specific. Written for the relevant accounting package.
The following parts are collected from Magento so that they can be used later in the accounting connection plugin:
- Sales : Orders
- Sales : Invoices
- Sales : Credit Invoices
- Sales : Transactions
- TAX configuration
We can then collect this data to pass on to the basic accounting module.
Module: Accounting - Base
The basic accounting module collects all available data from Magento and stores it in the appropriate tables.
Module: Accounting - Accounting Package
The module for the accounting package uses all data from the Accounting base extension so that it can then be specified according to the API standards of the relevant accounting package. Moreover, this data is directly linked to the correct ledger/cost center/general ledger account.
In the example below a short example of a possible link from the Accountingbase to the API specific of a specific accounting package;
- InvoiceID Mutation_id
- CustomerID Relation_id
- ProductID Article_id
- TaxClass btwType
When the data has been received with the relevant accounting package, this is fed back through various statuses that immediately return to the link. Any error codes are therefore immediately recognizable from the synchronization grids within the Magento link.
An example of possible error codes are;
Invoice number already exists
Invalid VAT code
Cost center on line X does not exist