|
This section describes how to enable the integration between Polygon and Xero, and how GL accounts should be created and mapped in Polygon Back Office to ensure correct posting of GST figures for BAS reporting.
The initial setup, authorisation and ledger mapping will be provided as part of Redcat’s installation process in consultation with the client. The following information is provided for your review and future reference.
The integration between Redcat Polygon and Xero creates a mapping between the Chart Of Accounts in each program, including instruction on which GST types are relevant to each account.
This integration passes the information contained within the sales reset from the POS to Xero when the reset is processed in Polygon POS Management in the form of a Draft Manual Journal – for users running perpetual stock this will include the Asset | Cost journal relevant to stock decrementation.
These draft manual journals may then be reviewed in Xero and posted as desired.

|
To correctly deal with GST when mapping revenue to feed into Xero, the setup of Revenue Accounts and PLUs in Polygon POS Management must follow these rules:
1.PLUs that are set up with GST Type: GST Free, must be mapped to a separate Revenue Account to items set up as GST Type: GST Inc
2.To assist with mapping, include ‘GST Inc’ or ‘GST Free’ in at least one of the Revenue Account names in Chart of Accounts File:
EXAMPLE PLUs:
| Coke (GST Inc) | Bottled Water (GST Free) |

|
If there are Paid Out transactions included in your POS resets the integration may also need to pass expenses or costs to Xero. To correctly deal with GST when mapping expenses\costs to feed into Xero the setup of Expense Accounts and Paid Out keypad buttons in Polygon POS Management must follow these rules:
1.Clients utilising multiple Paid Out buttons that are set up deal with specific GST Types, must be mapped to a separate Expense Accounts for GST Inc or GST Free.
2.To assist with external account mapping, include ‘GST Inc’ or ‘GST Free’ in the Expense Account names in Chart of Accounts File
Please note: this does NOT mean that the revenue and/or expense accounts must also be separated in Xero, ie. you can map both the Beverage and Beverage GST Free revenue accounts in Polygon to the same revenue ledger account in Xero.
|
The progression to successful integration will be much smoother if you understand all the elements involved before you start the mapping process.
Collect the list of accounts.
The progression to successful integration will be much smoother if you understand all the elements involved before you start the mapping process. It is recommended that you run the following reports to help you determine which ledger accounts will need to be mapped, and if you need to make any changes within Polygon POS regarding the considerations in the sections above.
•PLU List by PLU Class (this will show both the revenue account assigned and the GST Type of each PLU, check that any GST Free PLUs are assigned to revenue accounts separate your GST Inc items)
•POS Media Log (to determine which media types need to be mapped)
•Sales by Revenue Account (to determine which revenue accounts need to be included in the mapping)
•Paid Out Report (to determine if expense/cost accounts need to be included in the mapping.
•Stock items List (if you are using Polygon Inventory you will need to know which asset and cost accounts are attached to stock items)
Asset Accounts
|
These will be your media types. Think about if you want a direct ‘like for like’ mapping (cash to cash, eftpos to eftpos, amex to amex etc) or if you want to map all media to a clearing account, or a combination of the two.
Are you running Polygon Inventory? If so, you need to know which asset accounts are attached to stock items.
If you process Client Account charges at POS these affect Accounts Receivable ledger account in Polygon (see note below for recommendation).
|
Liability Accounts
|
Do you have Polygon Loyalty with hybrid cards or gift cards? If so, you will need to map the Unexpired Gift Cards liability account.
|
Revenue Accounts
|
Check your Sales by Revenue Account report to ensure that you map all the relevant revenue accounts. POS Discounts, POS Surcharges and Cash Over/Under are system revenue accounts and will also need to be mapped.
|
Expense Accounts
|
Check your Paid Out report to find out which expense accounts (if any) will need to be mapped. If you use generic paid outs like Petty Cash (GST Inc) and Petty Cash (GST free) ensure that these are assigned to separate expense accounts in Polygon.
|
Cost Accounts
|
Are you running Polygon Inventory? If so, you need to know which cost accounts are assigned to stock items.
|
Note: Polygon users who process Client Account charges at POS are advised to map the Polygon ‘Accounts Receivable’ Asset account to a generic clearing account in Xero. For example: ‘POS Client Charges’, ‘POS Client Clearing Account’ or something similar. This is because the integration will send account charges as a journal and client invoices will not be created in Xero. You would then enter the relevant client invoice in Xero as required, against this clearing account.
Determine the GST Implications.
When each ledger account is mapped, the GST type that will be assigned to transactions sent from that account must also be assigned.
The default GST types accepted by Xero are:
•GST on Income,
•GST Free Income,
•GST on Expenses,
•GST Free Expenses
•BAS Excluded
Generally:
Asset and Liability accounts have no GST implication (BAS Excluded).
While Revenue, Expense and Cost accounts are affected by GST (GST on Income, GST Free Income, GST on Expenses, GST Free Expenses).
Please note: If you are running Polygon Inventory a perpetual stock decrementation will be processed as part of the reset. This movement between asset and cost has NO GST implication so BAS Excluded should be chosen for the asset and cost accounts that are assigned to stock items.
This table can be used as a guide.
Ledger Type
|
Description
|
GST Type
|
Asset
|
Asset accounts listed in the external mapping will be:
Media Types (cash, eftpos, amex etc)
Accounts Receivable (if you allow client account charges at POS)
Accounts attached to stock items (if you are using Polygon Inventory)
|
BAS Excluded
|
Liability
|
Liability accounts could be:
Unexpired Gift Cards (if you have Polygon Loyalty with hybrid or gift cards)
Accounts for recording donations (if you are using the Round Up For Charity functionality).
|
BAS Excluded
|
Revenue
|
Revenue accounts listed will be:
Accounts attached to PLUs sold at POS.
System accounts used by POS -
POS Discounts,
POS Surcharges, and
Cash Over/Under
|
GST on Income
or
GST Free Income
|
Expense
|
Expense accounts listed could be:
Accounts assigned to Paid Out buttons (if used at POS)
|
GST on Expenses
or
GST Free Expenses
|
Cost
|
Cost accounts could be:
Accounts attached to stock items (if you are using Polygon Inventory).
|
BAS Excluded
|
|
|
Redcat Operations or Support staff will facilitate the setup of the correct modules and walk you through the process to authorise the authentication between Redcat Polygon and Xero.
Polygon POS Management setup:
1.In POS Management, go to Application Settings, tick ‘Enable the Polygon Central Framework’
2.Go to Web Reporting > Polygon Central and ensure Polygon Central server address is configured

3.Go to Xero Interface > General. Tick ‘Enable the Xero interface module’

4.In the Xero tax codes field, enter the account tax codes required for mapping, followed by pipe separators
EXAMPLE:
BAS Excluded|GST Free Expenses|GST Free Income|GST on Expenses|GST on Income
The External Tax Code pick list will then consist of these free text entries as options
5.Interface API root URL:
/api/v1/interfaces/xero
6.GL posting URL:
/api/v1/interfaces/xero/sync
7.Press the select icon next to Polygon/Xero GL account assignment.
8.Press the select icon in the left column, this will display a list of Xero accounts for this client, which are retrieved via API.
[NOTE: if an access error is displayed at this point, then Redcat Polygon Central could not connect to Xero. Please contact the HelpDesk on 1300 4 73322 for assistance in resolving this error.]
9.Select the relevant Xero account, set the correct tax code for this account, then select from the right-side list to apply the corresponding Redcat GL account
10.Continue until all relevant accounts are mapped, press OK to save.
Recommendations from the Redcat Support Manager:
Redcat users who process Client Account changes at POS are advised to map the Redcat ‘Accounts Receivable’ Asset account to a generic clearing account in Xero. For example: ‘POS Client Charges’, ‘POS Client Clearing Account’ or something similar. This is because the Redcat interface will send account charges as a journal and client invoices will not be created in Xero. Users would then enter the relevant client invoice in Xero as required, against this clearing account.
The GST Type assigned to each ledger account must be confirmed by the client as ultimate responsibility rests with them to ensure this is correct. As a GENERAL rule: Asset, Liability and Equity accounts have no GST implication (N-T / BAS Excluded). While Revenue, Expense and Cost accounts are affected by GST (GST, FRE / GST on Income, GST Free Income, GST on Expenses, GST Free Expenses).
If a perpetual stock decrementation will be processed as part of the reset, please be aware that this movement between asset and cost has NO GST implication.
|
Processing Resets
With the module correctly enabled, posting from Redcat to Xero will occur automatically when sales resets are processed in the Revenue Download screen or via the auto-download and processing service.
If a Redcat account is detected in the GL Reference of a sales reset, which has not been mapped to an external Xero account as per section above, the following errors will be displayed specifying the offending account(s):


The reset will not be processed in Polygon POS Management until this is rectified. Follow steps above to map the account correctly. Then return to Revenue Download to attempt the process again.
NOTE: The following System PLU will be automatically added to a database that is licensed for Xero Interface:

This may be used in certain circumstances to handle GST rounding during reset processing, to ensure the reset data can be mapped correctly to Xero.
Reset Corrections or Reprocessing of Sales Resets
If for any reason you desire to amend/reprocess a reset in Redcat Polygon, you will need to ensure that the relevant posting in Xero is also removed prior to the resend so as to safeguard against overstating of revenue figures.
1.Identify the relevant draft journals (or journals if they have already been posted) created by this sales reset in Xero
2.Delete the relevant draft journals (or journals) from Xero
3.Contact Redcat Support to perform the reset correction in Polygon POS Management (if required)
4.Re-process the corrected reset
5.Verify the correct result in Xero
See Also:
Getting Started with POS Management
Polygon Back Office Introduction
|