Map Ledger Codes between InforLN and Xero.
Ledger codes used in InforLN and Xero are normally different, meaning they follow different naming convention logic, resulting in a probable confusion of the financial accounts. To solve this problem, the End User has the possibility to define standard Ledger Codes to use for Sales and Purchases and additionally to map specific Ledger Codes between InforLN and Xero.
- Default Sales Account Code
- For InforLN: default Ledger code used when generating sales invoices from Xero into InforLN. Note that functionality is not present in the current version of the connector but the property is reported here for completeness.
- For Xero: default Account Code used when generating sales invoices from InforLN into Xero.
- Default Purchase Account Code
- For InforLN: default Ledger code used when generating purchase invoices from Xero into InforLN.
- For Xero: default Account Code used when generating purchase invoices from InforLN into Xero.
- Sales Ledger Codes Map
- Allows to define zero or more relations between a sales Ledger Code in InforLN and a sales Account Code in Xero.
- Purchase Ledger Codes Map
- Allows to define zero or more relations between a purchase Ledger Code in InforLN and a purchase Account Code in Xero.
Notes
Similarly to the other screens, one of the Tax Rates mapping can be defined as a Default, meaning that if during the synchronisation no mapping is found, this Default will be used instead.
If, for any reason, the default assigned entity is removed from InforLN or Xero and not changed in the Connector Settings, then the synchronisation process will fail for the records that need a default value, generating Audit table Exceptions.
Ledger codes are not strictly bound to a Client/Supplier.
How many and what ledger codes to use will subject for an internal meeting within the Linea Light group.