How to Map GL Accounts in SwiftPOS BO

Modified on Fri, 14 Jan 2022 at 10:16 AM

Configure GL settings in SwiftPOS BO to map media, sales and purchases to accounts in the general ledger (MYOB and XERO only).


Quick Guide


1.  Navigate in SwiftPOS BO to Data Changes/Export > Data Portal > GL Mapping > Settings

2.  Select Tab where GL account is required to be mapped to the relevant Assignments.

3.  Scroll down list until you find the relevant line item

4.  Highlight the line

5.  Select the GL account from the GL Account Code drop menu

6.  Select Apply

7.  Select Save


If a GL account is not available for selection in SwiftPOS BO:

Import this using the MiGL Integrator app. Open the app and navigate to Account Codes;

  • A list of your Chart of Accounts will appear; tick the check box next to each of the account codes you require and select the Post button.
  • Return to SwiftPOS BO (close and open the GL settings screen to refresh. The new accounts will now be available to select from the drop menu in Step 5).



Step by Step Guide


1.  Navigate in SwiftPOS BO to Data Changes/Export > Data Portal > GL Mapping > Settings



2.  Select Tab where GL account is required to be mapped to the relevant Media/Account (Payment types), Group/Account (Sales/Revenue) or Purchase Expense (Supplier Invoices) Assignments.


3.  Scroll down the list until you find the relevant media, account or purchase line item 

4.  Highlight the line (click the empty cell next to the location)

  • Tip: If you have more than one location, click on table header to sort list by description or location. You can highlight multiple lines to apply the same account code to the same POS item.

5.  Select the relevant GL account from the GL Account Code drop menu

  • Leave the Apply To default setting as 'Selected Rows'

6.  Select Apply


7.  Select Save (botton located bottom of screen)



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article