We use cookies to ensure you get the best experience on our website - Find out more

Hi, what can we help you with?

  • If after mapping the “Employee” data in Solo Expenses with the “Supplier/Vendor” data in Sage 50, the user removes the “Supplier/Vendor” data from Sage 50 and then tries to export the transaction data from Solo Expenses. Solo Expenses will show an error message, because the “Supplier/Vendor” data was removed (in Sage 50).
  • This will result in the export to fail.
  • In this case, the user must again add the “Supplier/Vendor” data in Sage 50 first, and then map it with “Employee” data in Solo Expenses.
  • If the user exports the transaction data now, the Solo Expenses transactions will be exported successfully.
  • If after mapping the “Tax code” in Solo Expenses with the “Tax Code” in Sage 50, the user removes the “Tax Code” from Sage 50 and then tries to export transaction data from Solo Expenses. Solo Expenses will show an error message, because the “Tax Code” was removed (in Sage 50).
  • This will result in the export to fail.
  • In this case, the user must again add the “Tax Code” in Sage 50 first and then map it with the “Tax code” in Solo Expenses.
  • If the user exports the transaction data now, the Solo Expenses transactions will be exported successfully.
  • If after mapping the “Expense categories” in Solo Expenses with the “Nominal Code” in Sage 50, the user removes the “Nominal Code” from Sage 50 and then tries to export transaction data from Solo Expenses. Solo Expenses will show an error message, because the “Nominal Code” data was removed (in Sage 50).
  • This will result in the export to fail.
  • In this case, the user must again add the “Nominal Code” in Sage 50 first and then map it with “Expense categories” in Solo Expenses
  • If the user exports the transaction data now, the Solo Expenses transactions will be exported successfully.

TROUBLESHOOTING AND FAQs