New features in this update 

• Within the preference module it was possible to set a preference to automatically approve invoices within a certain predefined price margin. We have decided to remove this preference as uniforming our processes resulted in this logic now only being implementable via our workflow solution. Note: This preference was only applicable for clients performing invoice approval in Cevinio, without using workflow. – Invoice Processing
   
• We have added a setting to our system, allowing configuration that makes the invoice date mandatory or not when sending an invoice to the accounting robot. This used to be mandatory in all cases. The advantage is that clients can determine if they want the automation stopped when the invoice date is populated or not, before sending the invoice to the robot. This can have certain validation advantages, dividing the validation work between agent types. – Invoice Processing
   
• We have added a setting to our system, allowing configuration that makes the creditor invoice number mandatory or not when sending an invoice to the accounting robot. This used to be mandatory in all cases. The advantage is that clients can determine if they want the automation stopped when the creditor invoice number is populated or not, before sending the invoice to the robot. This can have certain validation advantages, dividing the validation work between agent types. – Invoice Processing
   
• When no invoice location is recognized and the last used invoice location is filled on the invoice, the default VAT codes that are filled in were not based on the last used invoice location. This release resolves that issue and makes sure the VAT codes selectable and used for recognition purposes are the ones related to the last used invoice location. – Invoice Processing
   
• When trying to determine the default value for the creditor bank account, any linked PO’s are taken into account as well in order to determine the currency. However, if the ‘universal dummy PO’ is linked to the invoice, the currency on the PO is irrelevant and should be ignored, which is achieved via this development. – Invoice Processing
   
• We have created an extensive feature that allows our clients to fully automate all the processing steps in the system themselves. This was already available to a large extent, but the management of the automation has now been placed into the hand of the client itself. It allows our clients to manage per processing step in the system if automation is desired on a per vendor, per invoice type, basis. – Invoice Processing
   
• The PO interface to Cevinio has been updated in order to have an additional elements used for product uniqueness validations. The elements product discription and currency of the product have been added to allow additional uniqueness checks over these characteristics. This gives the added benefit of allowing the same product to exist with a different currency and a different description. – Invoice Processing
   
• In the warehousemanagement solution within our purchase module, currently the expiry date was not available in the cyclecount lists. This prevented proper cyclecount routines for our clients. This has been fixed. – Purchase
   
• We had a check on dutch bankaccountnumbers to validate them with the so called “elfproef”. This is no longer needed, so the validation has been removed out of the system. – Purchase
   
• If the same product is ordered in two separate order requests and grouped on a single PO invoice line, you end up with two OR lines and a single PO invoice line for that product. In step 4, this will be shown as two PO invoice lines, because although we call them PO invoice lines, they are actually OR invoice lines. Now let’s say that on one of the OR lines 3 PCE were ordered and on the other 5 PCE, making 8 PCE in total. The supplier will then receive a PO line for 8 PCE and will probably invoice it like that. For the end user who is processing the invoice, it may be confusing that there are 2 matching PO invoice lines for a single invoice line on the scanned invoice. This functionality makes sure that the invoicelines are represented below each other in the sorting, helping the end user to quickly see what should be matched by the invoice. – Invoice Processing
   
• For the Internal Order interface we have been adding logic that allows us to easily manage and maintain potential duplication that arises from clients sending duplicate input coming out of multiple SAP instances. The addition of this feature puts the prevention of duplicates caused by clients with multiple ERP’s at Cevinio’s solution. – Cevinio API’s
   
• For the General Leder Account Interface we have been adding logic that allows us to easily manage and maintain potential duplication that arises from clients sending duplicate input coming out of multiple SAP instances. The addition of this feature puts the prevention of duplicates caused by clients with multiple ERP’s at Cevinio’s solution. – Cevinio API’s
   
• For the Vendor Master Data (VMD) Interface we have been adding logic that allows us to easily manage and maintain potential duplication that arise from clients sending duplicate input coming out of multiple SAP instances. The addition of this feature puts the prevention of duplicates caused by clients with multiple ERP’s at Cevinio’s solution. – Cevinio API’s
   
• We have extended our PO interface to be able to work with the SAP AUFNR, or Process Order, field. This particular extension allows us to store this number besides the PO number and functionally the systems OCR engine also picks up this number in the recognition of this value on the invoice. – Cevinio API’s
   
• For our clients using the warehousemanagement module in purchase, we have extended the downstream reporting capabilities by adding the expiry date, lot number and the serial number into the data flow. This should allow our clients to create BI reports containing relevant information with regard to this data. – Purchase
   
• We have extended the automated processing by allowing clients to activate a creditor setting on the “Creditor settings details” page on automatically creating credit invoices from system step 3. – Invoice Processing
   
• We have further standardized our implementation of OAuth for the incoming masterdata interfaces. – Cevinio API’s
   
• For the free text order inbox we have extended the purchasing departments ability to add additional lines to the reference order that originates from the original free text order line. Previously it was only possible to create one reference order line out of the original free text order line. Now its possible to add multiple lines to the reference order, making the free text order process easier. – Purchase
   
• For our connection with Coupa on the outgoing AR invoices, we have updated the logic on the odering for the service line detail items. This improves the integration capabilities of our solution. – InvoiceSharing
   
• The imported file history page has be extended with an additional overview showing the Mail History. This allows our client to not only look at the history of the submitted files, but it also allows them to investigate the submitted emails. This is important, as certain emails might not contain any files, or files that are not suitable for further processing. This feature improves the transparency of the status of submitted emails. – InvoiceSharing
   
• For electronic invoices there was no Unique Reference Number (URN) generated and stored during processing. We have now also extended the addition of URN to e-invoices, allowing improved traceability throughout our system. – InvoiceSharing

Bug fixes in this update

• For electronic invoices we had a bug which was not properly storing the balance type of an invoice. This has now been resolved. – Invoice Processing
   
• Within our spend tool a minor bug with regard to filtering on the time frame in a certain dashboard has been resolved. – Spend tool
   
• In the “Show History” page of InvoiceSharing – the page which shows all the invoices that were sent to the system – has a feature “Search bar” but when you tried to input an invoice number in the search bar – an error appeared -. This has now been resolved. – InvoiceSharing
  
• We fixed a bug in the BI dataflow, allowing for inconsitency on the creditor number. – BI reporting
  
• We fixed a bug in the BI dataflow, allowing for inconsitency on the Cevinio Internal Invoice number. – BI reporting
  
• Our functionality to re-export invoices in bulk to an external system was working incorrectly. This issue has been resolved and is back in working order. – InvoiceSharing