General Ledger

XERO

3rd Party Integration with swiftpos Back Office

 


Subjects      

 


About     

 

Available In?      

  • SwiftPOS V10+

What Is It?     

The swiftpos XERO GL Interface is used to export swiftpos Sale, Stock Movement, Supplier Invoice and Terminal Cash Off Variance related data to XERO via the XERO API.

Data (specifically Sales data) is exported in a consolidated form (summarised) specific to a Trading Date. This is to avoid the rapid expansion of XERO. If every individual transaction was posted into XERO from SwiftPOS, XERO would quickly expand. Especially for sites that have many POS terminals and are doing 1,000s of transactions per day.

 

What Is Required?     

It is highly recommended that the setup and configuration of swiftpos XERO export interface is done in Test environments initially. That is, test environments for both swiftpos and XERO (Refer to How To Signup For A 30 day Free Trial In XERO for more information).

  • In XERO
    • For Venues that are contemplating using XERO for the first time and are wanting to make use of swiftpos XERO Interface, ensure the following is addressed:
      • XERO Registration - Venues will need to be registered to use the XERO Accounting platform. That is they will need to have a XERO Account. There is also the option available to Login/Sign up for a 30 day free trial. This option is very useful when it comes to testing the swiftpos XERO interface using a copy of the Venue's swiftpos database in a test environment. Refer to How To Signup For A 30 day Free Trial In XERO for more information.
      • XERO API - Venues will need to ensure they have configured an APP in XERO in order to be able to establish a connection to XERO's API. Refer to How To Create A XERO App For An API Connection for more information.
      • Chart of Accounts (COA) - Venues may need to enlist the assistance/expertise of an accountant to ensure that in XERO, all Accounts are correct and appropriately configured for the Venue. Refer to XERO Articles on the Chart Of Accounts for more information.
        • Once the COA has been configured, an export of it will need to be obtained, in order to import into the XERO Test environment. Refer to How To Export The Chart Of Accounts for more information.
  • In SwiftPOS
    • SwiftPOS Registration - Venues will need to be registered for the swiftpos XERO GL interface for access to this feature. Email registrations@swiftpos.com.au to obtain the appropriate registration.
    • For Venues using XERO for the first time and for Venues already using XERO, and wanting to now make use of the swiftpos XERO interface, ensure the following is configured:
      • Ensure that the Post Financial Data option is selected for those Locations for which General Journal, Supplier Invoice and/or Terminal Cash Off related data is to be exported.

 

Notes ...


This does NOT apply to Inventory/Stock transfers between Locations. These will always be exported regardless of the whether this option is selected or not.

 

 

What Is Supported?     

The swiftpos XERO export feature supports the export of the following:

  • General Journals - All data associated with the following:
    • Sales - All Sales, Refunds, Account Charges/Payments, etc.
    • Stock Movements - All Stock Adjustments, Damages, Receipts, Returns, Transfers, Wastage and Stocktake variances.

 

Notes ...


With regards to Account Charges/Payments, Journals will be posted in XERO to a single Debtors Account rather than to individual Debtor Accounts.

  • Supplier Invoices - All completed Supplier Invoices.

 

Notes ...


The XERO API will automatically create Suppliers in XERO (when exporting Supplier Invoices) that do NOT already exist in XERO.

  • Terminal Cash Offs - All Cash Off Variances that have been saved/committed in the Back Office.

 

Notes ...


Cash Offs that balance will NOT be exported.

 

What To Consider?     

  • The XERO GL interface exports by default to the Accrual Accounting method. Cash Accounting is NOT currently supported.
  • The XERO GL Interface does NOT support multiple XERO Organisations and each having their own Charts of Accounts (COAs). Venues requiring this will need to request a registration for the XERO Pro GL interface.
  • The XERO GL Interface NOW SUPPORTS multiple XERO Organisations. However, it DOES NOT SUPPORT multiple Chart of Accounts (COAs). Refer to Single vs Multiple XERO Organisations for more information.

 

Notes ...


A XERO App (XERO API credentials, namely Client ID, Customer Secret and Redirect URL) configured in XERO, can be used by more than one swiftpos Location Group (Venue) when establishing a connection to XERO.

  • It is recommended that prior to implementation, implementers familiarise them selves with the limitations of XERO, as outlined in their XERO API documentation.
  • It is recommended that all rows, in each of the Account Assignment/Mapping Tabs, be assigned/mapped to an Account or to the Exclude from Export Account.
  • Use the Exclude from Export Account (listed as the first entry in the Account drop down lists in the Account Assignment/Mapping Tabs) to ensure specific Location/Media, Location/Master Group and Location entries are excluded from being exported.

 

Notes ...


Caution must be taken when using the Exclude from Export Account, as it can potentially result in unbalanced Journals being generated and these will NOT successfully import into XERO.

  • For Location Groups (Venues) that have the Track Individual Location Costs option selected, transfers between Locations will be exported, with the value of the transfer calculated based on the cost of the Products in the From Location (at the time of the Transfer).
  • DO NOT enter Credit Notes into swiftpos as negative Supplier Invoices. These DO NOT export to XERO successfully. Instead raise a Credit Note using the Credit Note Type option available when entering Supplier Invoices.
  • Any errors encountered when exporting data into XERO, can be viewed in the Event Logs > swiftpos Applications > swiftpos SQL Application.
  • Products in Non-GST Categories will be exported into XERO with an EXEMPTOUTPUT XERO Tax Type. This will ensure that both GST and GST Free sales can be posted to the same XERO Account.
  • All stock movement type transactions, for example : Stocktake, Adjustments, Receipts, Returns, Damages, etc, will be exported to XERO with the following Tax Types:
    • BASEXCLUDED for Australian sites.
    • NONE for non-Australian sites.

 

Notes ...


This will ensure no GST is applied regardless of the XERO Account's Tax Type.

  • It is recommended that the export to XERO of all types of Transactions is tested. It maybe necessary to enlist the assistance/expertise of an accountant to ensure that in XERO, all Account mappings (outlined in the Setup below) are correct and that the Journals that are posted are correct.

 

When Is It Used?     

Any swiftpos Venue that wants to ability to export financial transactional data to XERO.

 


How To?     


How To Get Started?     

Do as follows:

 

When Going Live     

 

Notes ...


The first time the XERO Export runs successfully as part of the End of Day process, all Transactions that are NOT flagged as Exported, will be exported and uploaded into XERO. This will mean that immediately after the EOD has processed, there should not be any Trading Dates available for export, when viewed in the Export screen, for each of the Location Groups (Venues) that have the XERO Export option selected in the End of Day Options screen.

 

When Testing     

 


Screens     

 

Export Screen     

 

 

To access select the Export option in either the XERO or XERO Pro menu in Data PortalProvides a Venue with the ability to export General Journal, Supplier Invoice and Terminal Cash Off related data from swiftpos and import them directly into XERO using XERO's API. General Journal data includes both Sales and Stock Movement transaction data. Supplier Invoice data refers to completed Supplier Invoices. Terminal Cash Offs refers to committed Terminal Cash Offs that have recorded a variance.

 

Sections     

 

General Journals Section      

 

Used to export Sales and Stock Movement transaction data to XERO

  • Location Group - Select from the drop down list the Location Group for which data will be exported.
  • Location - Select from the drop down list the Location for which data will be exported.
  • Trading Date - Select from the drop down list of dates the date for which data will be exported and uploaded into XERO using XERO's API.

 

Notes ...


Once exported, the data will be flagged as exported and the date will be removed from the Trading Date drop down list. This will ensure that the same data is NOT exported multiple times. It is important to note that even though the export for a specific Trading Date may NOT be completely successful, the Trading Date will still be removed from the drop down list. It is therefore VERY IMPORTANT to always review the Event Logs to ensure that any ERRORS are investigated and resolved in an appropriate manner.

  • Export - Select to invoke the export. Once completed a prompt will be displayed confirming completion. All exported Journals can be viewed in the Event Logs.

 

Notes ...


If no prompt is displayed and the Export appears to have completed without the selected Trading Date being removed from the list of available dates, this may point to a failure of being able to connect to Xero. Check the Event Logs > swiftpos Applications > swiftpos SQL Application for any logging that may have occurred. Refer to Troubleshooting for more information.

  • Reset - Select a Trading Date to ensure that General Journal related transactions for that date are flagged as NOT Exported, so that they can be exported again. Select to display the following prompt:

 

  • Continued ...
    • Location Group - Select from the drop down list the Location Group for which data will be reset.
    • Location - Select from the drop down list the Location for which data will be reset.
    • Trading Date - Select from the drop down list the Trading Date for which General Journal related transactions will be reset.
    • OK - Select to Reset.
    • Cancel - Select to exit without Resetting.

 

Notes ...


When resetting and exporting again, be sure that they DO NOT result in duplicates when imported into XERO.

  • Mark ALL as Exported - Select to display the following prompt and thereby ensure ALL General Journal related data in the selected Location is flagged as exported.

 

  • Continued ...
    • Location Group - Select from the drop down list the Location Group for which data will be flagged as exported.
    • Location - Select from the drop down list the Location for which data will be flagged as exported.
    • OK - Select to flagged as exported.
    • Cancel - Select to exit without marking as exported.

 

Notes ...


This is usually recommended when initially configuring swiftpos to Export to XERO for the first time and also, when there is a requirement that all existing General Journal related transactions for a selected Location need to be flagged as exported.



Supplier Invoices Section     

 

Used to export completed Supplier Invoice data to XERO

 

Notes ...


Invoices completed and having the same Posting Date as that of the selected Trading Date, will be selected for Export. Also, DO NOT enter Credit Notes into swiftpos as negative Supplier Invoices. These DO NOT export to Xero successfully. Instead raise a Credit Note using the Credit Note Type option available when entering Supplier Invoices.

  • Location Group - Select from the drop down list the Location Group for which data will be exported.
  • Location - Select from the drop down list the Location for which data will be exported.
  • Trading Date - Select from the drop down list of dates the date for which data will be exported and uploaded into XERO using XERO's API.

 

Notes...


Once exported, the data will be flagged as exported and the date will be removed from the Trading Date drop down list. This will ensure that the same data is NOT exported multiple times. It is important to note that even though the export for a specific Trading Date may NOT be completely successful, the Trading Date will still be removed from the drop down list. It is therefore VERY IMPORTANT to always review the Event Logs to ensure that any ERRORS are investigated and resolved in an appropriate manner.

  • Export - Select to invoke the export. Once completed a prompt will be displayed confirming completion. All exported Invoices can be viewed in the Event Logs.

 

Notes ...


If no prompt is displayed and the Export appears to have completed without the selected Trading Date being removed from the list of available dates, this may point to a failure of being able to connect to Xero. Check the Event Logs > swiftpos Applications > swiftpos SQL Application for any logging that may have occurred. Refer to Troubleshooting for more information.

  • Reset - Select a Trading Date to ensure that Supplier Invoice related transactions for that date are flagged as NOT Exported, so that they can be exported again. Select to display the following prompt:

 

  • Continued ...
    • Location Group - Select from the drop down list the Location Group for which data will be reset.
    • Location - Select from the drop down list the Location for which data will be reset.
    • OK - Select to Reset.
    • Cancel - Select to exit without Resetting.

 

Notes ...


When resetting and exporting again, be sure that they DO NOT result in duplicates when imported into XERO.

  • Mark ALL as Exported - Select to display the following prompt and thereby ensure ALL Supplier Invoice related data in the selected Location is flagged as exported.

 

  • Continued ...
    • Location Group - Select from the drop down list the Location Group for which data will be flagged as exported.
    • Location - Select from the drop down list the Location for which data will be flagged as exported.
    • OK - Select to flagged as exported.
    • Cancel - Select to exit without marking as exported.

 

Notes ...


This is usually recommended when initially configuring swiftpos to Export to XERO for the first time and also, when there is a requirement that all existing Supplier Invoice related transactions for a selected Location need to be flagged as exported.

 

Terminal Cash Offs Section     

 

Used to export committed Terminal Cash Off data to XERO

 

Notes...


Terminal Cash Offs that have not recorded a variance will NOT be available for export.

  • Location Group - Select from the drop down list the Location Group for which data will be exported.
  • Location - Select from the drop down list the Location for which data will be exported.
  • Trading Date - Select from the drop down list of dates the date for which data will be exported and uploaded into XERO using XERO's API.

 

Notes...


Once exported, the data will be flagged as exported and the date will be removed from the Trading Date drop down list. This will ensure that the same data is NOT exported multiple times. It is important to note that even though the export for a specific Trading Date may NOT be completely successful, the Trading Date will still be removed from the drop down list. It is therefore VERY IMPORTANT to always review the Event Logs to ensure that any ERRORS are investigated and resolved in an appropriate manner.

  • Export - Select to invoke the export. Once completed a prompt will be displayed confirming completion. All exported Invoices can be viewed in the Event Logs.

 

Notes...


If no prompt is displayed and the Export appears to have completed without the selected Trading Date being removed from the list of available dates, this may point to a failure of being able to connect to Xero. Check the Event Logs > swiftpos Applications > swiftpos SQL Application for any logging that may have occurred. Refer to Troubleshooting for more information.

  • Reset - Select a Trading Date to ensure that Terminal Cash Off related transactions for that date are flagged as NOT Exported, so that they can be exported again. Select to display the following prompt:

 

  • Continued ...
    • Location Group - Select from the drop down list the Location Group for which data will be reset.
    • Location - Select from the drop down list the Location for which data will be reset.
    • OK - Select to Reset.
    • Cancel - Select to exit without Resetting.

 

Notes...


When resetting and exporting again, be sure that they DO NOT result in duplicates when imported into XERO.

  • Mark ALL as Exported - Select to display the following prompt and thereby ensure ALL Terminal Cash Off related data in the selected Location is flagged as exported.

 

  • Continued ...
    • Location Group - Select from the drop down list the Location Group for which data will be flagged as exported.
    • Location - Select from the drop down list the Location for which data will be flagged as exported.
    • OK - Select to flagged as exported.
    • Cancel - Select to exit without marking as exported.

 

Notes...


This is usually recommended when initially configuring swiftpos to Export to XERO for the first time and also, when there is a requirement that all existing Terminal Cash Off related transactions for a selected Location need to be flagged as exported.

 

Settings Screen     

 

To access select the Settings option in the Xero menu in Data Portal. Provides a Venue with the ability to configure the settings required to establish a connection to XERO, as well as import the Chart of Accounts from XERO, and assign/map these to swiftpos Location/Media combinations, Location/Master Group combinations and Locations.

 

Tabs      

 

Account Assignment / Mapping Tabs     

 

Notes ...


It is recommended that all rows, in each of the tabs, be assigned/mapped to an Account or to the Exclude from Export Account. Use the Exclude from Export Account (listed as the first entry in the Account drop down lists in the assigning/mapping tabs) to ensure specific Location/Media, Location/Master Group and Location entries are excluded from being exported. Caution must be taken when using the Exclude from Export Account, as it can potentially result in unbalanced Journals being generated and these will NOT successfully import into XERO.

 

Location / Media Clearing Accounts Tab      

 

Example of Account assignments/mappings for one Location

Used to assign/map XERO Accounts to SwiftPOS Location/Media combinations.

 

Header Section

  • Filters
    • Clearing Account - Select from the drop down list the XERO Account that will be used to assign/map to the SwiftPOS Location/Media combination.
    • Apply To - Use to assign/map the selected XERO Account to the rows in the grid by using one of the following options:
      • Selected Rows - Select to assign/map to all rows that are currently selected in the grid.
      • Unassigned Rows - Select to assign/map to all rows that are currently DO NOT have an Account assigned/mapped in the grid.
      • Selected Location - Select to assign/map to all rows in the grid that are associated with a selected Location.
      • Copy Location - Select to copy the assignments/mappings of a selected Location to another.

 

Grid Section 

Displays a list of Location/Media combinations that are required to be assigned/mapped to a XERO Account.

 

Location / Master Group Sales Accounts Tab        

 

Example of Account assignments/mappings for one Location

Used to assign/map XERO Sales Accounts to SwiftPOS Location/Master Group combinations and used when exporting General Journals.

The Accounts assigned/mapped in the Cost of Sales Account column above, will be used when exporting General Journals. Cost of Sales Accounts are normally referred to as Direct Cost accounts in XERO and are used to post the Cost of Goods sold.

The Accounts assigned/mapped in the Sales Account column above, will be used when exporting General Journals. Sales Accounts are normally referred to as Revenue accounts in XERO and are used to post the value of revenue for goods sold.

 

Notes ...


If the Exclude from Export Account is used to assign/map a Location/Master Group combination, then it MUST be selected in both columns for the same entry. That is, select in both the Cost of Sales and Sales Account columns.

 

Header Section

  • Filters - Refer HERE for more information.
  • Apply To - Refer HERE for more information.

 

Grid Section

Displays a list of Location/Master Group combinations that are required to be assigned/mapped to a XERO Sales Account.

An example of the setup of a Cost of Sales Account in XERO can be seen below:

 

 

Location / Master Group Inventory Accounts Tab        

 

Example of Account assignments/mappings for one Location

Used to assign/map XERO Inventory Accounts to SwiftPOS Location/Master Group combinations and used when exporting General Journals and Supplier Invoices.

Header Section

  • Filters - Refer HERE for more information.
  • Apply To - Refer HERE for more information.

 

Grid Section

Displays a list of Location/Master Group combinations that are required to be assigned/mapped to a XERO Inventory Account.

An example of the setup of a Inventory Account in XERO can be seen below:

 

 

Location / Master Group Freight Accounts Tab        

 

Example of Account assignments/mappings for one Location

Used to assign/map XERO Freight Accounts to SwiftPOS Location/Master Group combinations and used when exporting Supplier Invoices.

Header Section

  • Filters - Refer HERE for more information.
  • Apply To - Refer HERE for more information.

 

Grid Section

Displays a list of Location/Master Group combinations that are required to be assigned/mapped to a XERO Freight Account.

 

Location / Master Group Rounding / Misc Charge Accounts Tab        

 

Example of Account assignments/mappings for one Location

Used to assign/map XERO Rounding/Miscellaneous Charge Accounts to SwiftPOS Locations and used when exporting Supplier Invoices.

Header Section

  • Filters - Refer HERE for more information.
  • Apply To - Refer HERE for more information.

 

Grid Section 

Displays a list of Locations that are required to be assigned/mapped to a XERO Rounding/Miscellaneous Charge Account.

  • Location - Displays the SwiftPOS Location.
  • Rounding/Miscellaneous Charge Account - Displays/Select the XERO Rounding/Miscellaneous Charge Account from the drop down list that is to be assigned/mapped to the SwiftPOS Location.

 

Accounts Tab     

 

Example of the Accounts tab after importing the Chart of Accounts from XERO.

 

Grid Section 

Displays a list of XERO Accounts and their attributes as imported from XERO, an which can then be selected when assigning/mapping Accounts in the Account Assignment/Mapping tabs to the right. The grid displays the following columns:

  • Xero Account
  • Description
  • Xero Account Type
  • Status

 

Notes ...


The values of the Account attributes listed above are as they were when last imported from XERO. To view the most up to date values, re-import the Chart of Accounts.

Location Group Settings Tab        

 

 

Grid Section

Displays a list of Location Groups that are currently available to be selected when exporting to XERO. These are listed along with their:

  • Organisation - Displays the XERO Organisation the Location Group is associated with.
  • Venue ID - Displays Location Group's ID.
  • Client ID - Displays the Client ID that is being used to establish a connection to the XERO Organisation.
  • Client Secret - Displays the Client Secret that is being used to establish a connection to the XERO Organisation.
  • Redirect URL - Displays the Redirect URL that is being used to establish a connection to the XERO Organisation.
  • Test - Select to initiate a test of the connection credentials entered above.

 

Footer Section

  • Add Row - Select to add row in the grid.
  • Delete Row - Select to delete the currently selected row in the grid.
  • Import Chart of Accounts - Refer to How To Import The Chart Of Accounts for more information.

 

Notes ...


The swiftpos XERO GL Interface does NOT support multiple XERO Organisations and each having their own Charts of Accounts (COAs). Venues requiring this will need to request a registration for the XERO Pro GL interface.
In the XERO GL Interface, it is the expectation that the same COA is applicable for all Location Groups (Venues) listed in the grid above.

 


What Else?     

 

Examples      

Examples of exported XERO data for:

 

General Journals      

Sale/Refund of Food & Drink items, paid/refunded in Cash and exported:

Sale

 

Refund

 

Sale/Refund of Food & Drink items, charged/refunded to a Member's Account and exported:

Sale

 

Refund

 

Transfer of Drink items from Location Bottle Shop to Bar and exported:

 

+/- Adjustment of Drink items for Location Bottle Shop and exported:

+ Adjustment

 

- Adjustment

 

Damaged Goods/Wastage of Drink items for Location Bottle Shop and exported:

Damaged Goods

 

Wastage

 

Returns of Drink items for Location Bottle Shop and exported:

 

Promotions of Drink items for Location Bottle Shop and exported:

 

Stocktake +/- Variance of Drink items for Location Bottle Shop and exported:

+ Stocktake Variance

 

- Stocktake Variance

 

Supplier Invoices     

Invoice/Credit Note of Drink items and exported:

Invoice

 

Credit Note

 

Invoice of Drink items with Freight and exported:

 

Invoice of Drink items with Surcharges and exported:

 

Invoice of Drink items with Discounts and exported:

 

Invoice of Drink items with Rounding/Misc Charge and exported:

 

Invoice of Drink items with Freight, Discounts and Rounding/Misc Charge and exported:

 

Invoice of Drink items with Freight Averaging across items and exported:

 

 

Terminal Cash Offs     

+/- Cash Off Variances and exported:

+ Variance

 

- Variance

 

 

Single vs Multiple XERO Organisations     

Provides an explanation for Venues either hosting single or multiple XERO Organisations in their use of XERO, and that in relation to the swiftpos XERO and XERO Pro GL Interfaces.

  1. What Is A Single XERO Organisation?
  2. What Is A Multiple XERO Organisation?
  3. What Is Not Supported?
  4. What Is Supported?

 

What Is A Single XERO Organisation?      

These are Venues that export to only one XERO Organisation, that is, all swiftpos Location Groups (Venues) are configured to connect to the same XERO Organisation.

 

What Is A Multiple XERO Organisation?      

These are Venues that export to more than one XERO Organisation, that is, all swiftpos Location Groups (Venues) are configured, and in some cases, connect to different XERO Organisations.

 

What Is Not Supported?      

The swiftpos XERO Pro GL Interface supports both single and multiple XERO Organisations, as well as multiple Charts of Accounts (COA). That is, each XERO Organisation in XERO has it's own unique COA.

 

What Is Supported?      

The swiftpos XERO GL Interface supports both single and multiple XERO Organisations, However, when it comes to multiple XERO Organisations, it DOES NOT SUPPORT multiple Charts of Accounts (COA). That is, each XERO Organisation in XERO has it's own unique COA.

It is recommended that Venues wanting to make use of multiple COAs, request a registration for the XERO Pro GL interface.

XERO And Multiple XERO Organisations

If however, Venues choose to remain using the swiftpos XERO GL Interface and want to make use of multiple COAs, the they will need to ensure the following:

  • Each XERO Organisation configured in XERO and to which they will be exporting, has a COA that is a complete list of ALL Accounts. That is, every Account for all the XERO Organisations is setup in all of the COAs of each XERO Organisation. In short, the COA must be a complete list of all Accounts across all XERO Organisations.
    • It is recommended to use archived Accounts in XERO to distinguish Accounts from one XERO Organisation from another. Accounts listed in the COA for a particular XERO Organisation (Organisation A) and relating to other XERO Organisations (Organisation B,C and D), would then be archived, to ensure they cannot be assigned/mapped when imported into swiftpos for the same XERO Organisation (Organisation A). Hence, Accounts maybe archived in one Organisation, but are active in another. The Accounts listed in the Accounts tab can have one of the following statuses:
      • Active - Indicates the Account is currently active in the COA of the Location Group (Venue) that was last imported. These Accounts CAN be used in the Account assignment/mapping tabs.
      • Archived - Indicates the Account is currently archived in the COA of the Location Group (Venue) that was last imported. These accounts CANNOT be used when exporting from the same Location Group (Venue). However, these Accounts CAN be used in the Account assignment/mapping tabs, as they may be Active in the COAs of other Location Groups (Venues) that are configured in other XERO Organisations. Refer to the warning prompt for more information.

 

Notes ...


When the SAME XERO Account is configured in different XERO Organisations, it must have the same properties in each Organisation (for example: TaxType) otherwise this may generate errors. Great care and consideration should be taken when setting up XERO in swiftpos Back Office to support multiple XERO Organisations. We highly recommend that the setup is thoroughly tested prior to implementation. Also, with regards to the EOD process and multiple XERO Organisations, the XERO Export will cycle through each of the Location Groups (Venues) configured and establish a connection to their preferred XERO Organisation and then commence the export of the required journals.

 

  • Once the COA has been imported, then it will be incumbent on Venues to ensure that the Account assignment/mapping of the XERO Accounts is carefully undertaken to ensure that the correct Accounts are mapped to the correct Location Groups (Venues).

Each time a change is made to anyone of the COAs in any one of the XERO Organisations, this will need to be duplicated to the other XERO Organisations and the importing and assigning/mapping activities (outlined above) will need to be done again.

As can be seen the above is somewhat of an onerous task and can be prone to the exports failing to complete correctly. Again, It is recommended that Venues wanting to make use of multiple COAs, request a registration for the XERO Pro GL interface.

 

End of article