External Accounting: Fueltorque connection to external accounting system



Fuel is able to be connected to external accounting systems. Supported accounting systems are:

  • Xero
  • Desktop General Ledgers Sync'd via Fueltorque API

An external accounting system may be fully integrated with Fueltorque, for instance XERO, or it may be a standalone or desktop system that synchronises with Fueltorque using a broker application that connects to Fueltorque via the API.

Fully Integrated External Accounting Systems

When connected to a fully integrated external accounting system, the Fueltorque host operation is different from non connected sites. In particular:

  • Customers and Suppliers are managed in the accounting system rather than Fueltorque. These are configured and maintained in the accounting system and then synchronised through to Fueltorque
  • Payments to customer accounts are allocated to the invoice in the accounting system and then synchronised through to Fueltorque. As a Received on Account (RoA) payment in Fueltorque is not able to be automatically allocated to a particular invoice this feature becomes disabled within Fueltorque
  • Supplier purchase orders are posted through to the accounting system when they are created in Fueltorque. Payment processing is then managed within the accounting system while inventory tracking is managed within Fueltorque.

Standalone or Desktop External Accounting Systems

When synchronised with an external desktop accounting system, it is expected that the Fueltorque system is the master repository for local debtors, creditors, departments and payment methods. That is, the desktop GL probably does not have a real time bank feed and so does not make local debtor received on account payments at the GL which then have to be synchronised with Fueltorque.

To aid in the posting to an external desktop GL, GL Codes are able to be manually entered to:

  • Local Debtors
  • Suppliers
  • Payments
  • Departments

The external GL connects to Fueltorque via the API, downloading sales transactions, purchase orders and stock receipts since the last download date and time.

Note: it is the responsibility of the external GL to remember the time and date of the last transactions downloaded, and on subsequent downloads only request those transactions posted since then.