web
You’re offline. This is a read only version of the page.
close
  • Add back ability to easily view accounting currency next to company ID

    In earlier versions you could easily amend your user options status bar for additional elements to appear on your status bar. Particularly useful was the ability to add currency, the accounting currency then displayed next to the company id.

    You could also use this option to convert the currency which changed all forms and reports to the selected currency, this was a neat function but in reality not used that frequently in my experience.

    However the ease for a user transacting in a large volume of companies, all in different currencies to determine the accounting currency was a really useful visual aid.

    The best option for a workaround without development would be to add the currency symbol to the default workspace by changing the name in legal entities table, however this is not practical as this is usually the source company name for external documents.

     

  • Vendor collaboration bank account details to include account number and routing number

    In Supplier information workspace add bank account number and routing number to the the Pending Bank account creation dialogue and the form.

    For payments in the UK the mandatory required fields are Account number and Sort code (routing number). If these fields are not added then the vendor cannot self service and update bank information.

  • Allow bridged transactions using centralised payments across multiple companies without need for vendor in payment company

    If you use centralised payments across company for vendor payment and use a method of payment which uses a bridging account you can only settle the bridged transactions if you create the vendor account in the payment company.


    A dimension attribute error is return unless the vendor is also in the payment company.

    Unable to return DimensionAttributeValue record for dimension SystemGeneratedAttributeVendor with value SP000005, in legal entity w093, because a record doesn't exist in table VendTable through view DimAttributeVendTable.


    The vendors are not used for any other purpose in the payment company except to make the payment and therefore this adds considerable data migration effort (especially when 50+ companies and many thousands of vendors). Ongoing maintenance is also required for new vendors and process wise always have to ensure created in invoice company and repeated in payment company.


    It contradicts the purpose of centralised payments and intercompany account that you have to duplicate the party id just to settle a bridged transaction.