News

• MediusGo now supports receiving multiple payment accounts for its registered vendors.
  The interface has been updated to handle multiple payment accounts available to the linked vendor
  
  
• The system can now communicate information to users directly on the login page.
  
  
• Values in the coding information are now highlighted directly when moving between cells on the coding rows to facilitate management.
  
  
• Search has been updated so that ERP transaction no. numbers can be retrieved between an interval
  
  
• Optimizations around receipt readings have been made in the system.  

PO matching

• Dynamic text based on configuration when matching invoices.
  Left to allocate / left to post is displayed depending on the configuration to more easily guide the customer what actions may need to be taken.
  
  
• The system now more clearly shows the remaining amount left to post based on configuration
  
  
• Extended control for the system to automatically forward approved order invoices

Bugs

• When canceling and restarting an invoice, the canceled invoice did not get a correct unique External ID in the system
  
  
• The system could flag coding rows as not fully approved even though it was.
  
  
• The system reported that the user does not have approval rights for x amount, even though the user has had this as a replacer.
  
  
• Replacers had the option to forward an invoice for payment even though it was not fully approved.
  
  
• The system did not always suggest the right user in the hierarchy if only a few rows were approved.
  
  
• In the search and work queue, the date fields due date, invoice date and posting date were time zone converted.
  
  
• In the old application, the sorting order of the history could be incorrect.
  
  
• Company control added when applying coding suggestions based on reference
  
  
• Child rows were not automatically applied when importing in combination with real estate VAT
  
  
• Misleading information in the system when we showed the heading Supplier No. in the work queue and Supplier ID inside the invoice, now called Supplier ID globally.
  
  
• Templates set up with the value % were not applied by the system
  These rows will now be created correctly where column with invalid value is blank.

PO matching

• Problems with being able to forward order invoices in the system  
  
  
• The system did not take into account the AllocateVATAmount parameter when displaying the amount left to allocate
  
  
• Incorrect value was sent to the system during supplier matching which caused the vendor to be incorrectly linked and the invoice stuck.
  
  
• Unapproved/completed item lines could be updated when posting.