UBL (invoices)

Modified on Tue, 2 Jul at 11:51 AM


All screenshots in the article were taken in the Dutch version of Yuki.

UBL invoices can be submitted in Yuki in various ways. These can be sent to the administration(s) by the Yuki user or the suppliers who can submit UBL invoices. It is also possible to have UBL invoices automatically retrieved via InvoiceSharing or the Sales web service

All office staff can view the overview of submitted UBL invoices.

Only a user with a 'Back office' role in a domain can actually open the UBL invoices in that domain.

In the accountant portal, click on Management and then on UBL to view an overview of the UBL invoices in the (sub)portal.

The following screen is opened:

By clicking on the name of a UBL invoice, the relevant UBL invoice will be opened directly in the domain.

In this screen you will see the following columns, among others:

  • Type: the Intelligent Document Recognition (IDR) classifies the XML message as a purchase invoice or sales invoice type document.
  • All fields correct: all fields in the UBL invoice have or have not been correctly recognised by the IDR.
  • Autom. processed: the UBL invoice is or is not automatically processed by Yuki.
    A UBL invoice is not processed automatically if e.g:
    • the default values of a supplier or customer in a domain indicate that purchase or sales invoices should not be processed automatically
    • not all fields in the UBL invoice are correctly recognised by the IDR.
  • Job status: the status of the job (recognition and completion by IDR)
  • Error message: any error message if the job could not be completed.


The data in the All fields correct, Autom. processed, Job status and Error message columns can be viewed in more detail by clicking on IDR details at the top right of a processed UBL invoice.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article