Inter-Database Trading

aaaWhen parts of your organization trade with one another, especially across databases, the paperwork can be excessive and wasteful.

Abel’s inter-company and inter-database documents both minimize and automate your trading and financial transactions

Abel’s Inter-database trading means you can create a document in one database, and Abel automatically creates a corresponding document in another database, reducing manual work normally required and therefore reducing errors.

Abel’s inter-database trading can be used between any two organizations that trade with one another provided they both use Abel. They are most often used between different databases within the same Abel installation but can also be used to trade business to business with your customers or suppliers if they also run Abel.

As any multi-location business knows, separate locations or business units often have a very high degree of interdependence and share multiple inter-company transactions. These include buying goods for each other and also often locations transferring inventory, manufacturing goods, paying creditors, receiving debtor payments or paying for goods on behalf of each other.

All these transactions require specialized accounting processes. To simplify and unify this process, Abel provides inter-company documents that are automatically produced in the host location and subsequently transferred to the remote location. Each document performs the correct accounting necessary to balance the accounts on consolidation.

Branch Transfers

Abel’s Inter Branch documents can be used for both stock and non stock transactions. They use an intercompany accounting approach and can move stock or adjust anything between two databases e.g. Corporate Office can post a payroll total to a branch.

A Branch Invoice document can create a Branch Transfer document in another database. This can be used for stock transactions as stock is moved between branches. The Branch Invoice / Branch Transfer may be part of a larger document chain as shown in the below diagram. In this example, when the Branch Transfer is posted, it links back up with the original Supplier Purchase Order.

Cap387

Branch Invoice / Branch Transfer can also be used for non stock transactions – adjusting anything between two databases e.g. Corporate Office charging a payroll figure to a branch. While inter database documents for stock transactions are posted immediately, inter-database documents for non-stock financial adjustments can be kept open. Users or system processes can add lines for adjustments / transfers as they are needed. At the end of the month (or week or day) click Post then click Transfer to create the reciprocal document in the remote database. Staff in the remote database can review the Branch Transfer before posting it. You can optionally use a Branch Debtor and Branch Creditor for inter-branch settlement.

NewDiag

Abel’s Branch Transfer architecture can handle different currencies and different tax regimes.

Inter-Database Stock Processes

Abel’s inter-database client documents are used for inter-database stock processes and manufacture-for-stock processes between databases. They can be used to complete customer orders using stock from other branches or for other stock processes between branches. They can also be used between an installation and its customers or suppliers if they also run Abel.

The inter-database stock processes are an alternative to the Branch Invoice / Branch Transfer approach. They can accomplish similar results. The Inter-Database Stock Processes can be configured in two different ways:

  • With invoicing or
  • With inter-company accounting

With Invoicing

Inter-Database Stock with Invoicing uses a “sale and purchase” accounting approach and does not perform inter-company accounting. The inter-database documents used for this configuration are:

  • Supplier Order to Customer Order.
    A Supplier Order creates a Customer Order in another database.
  • Customer Despatch to Supplier Delivery.
    A Customer Despatch creates a Supplier Delivery in the other database.
  • Customer Invoice to Supplier Invoice.
    A Customer Invoice creates a Supplier Invoice in the other database.

Cap388

With Inter-Company Accounting

This option for managing inter-database stock uses an inter-company accounting approach. The inter-database documents used for this configuration are:

  • Supplier Order to Customer Order.
    A Supplier Order creates a Customer Order in another database.
  • Customer Despatch to Supplier Delivery.
    A Customer Despatch creates a Supplier Delivery in the other database.

Cap352 (1)

Inter-Database Customer Invoices

Abel’s inter-database Customer Invoice Transfer enables you to copy a customer invoice to another database where it will complete its life-cycle. It is most often used for managing large debtor accounts that are managed centrally or nationally.

Example:

  • A Branch raises an invoice and then transfers it to a central debtor where it will complete its life-cycle.
  • The transfer process settles the customer invoice in the branch and creates it in the central database.
    Staff in the central database send all invoices to the customer and the customer makes one payment.

The invoices are then settled in the Central database debtors.

Cap356