Disclaimer
All screenshots in the article were taken in the Dutch version of Yuki.
Statistics are kept such as the number of transactions processed per day, document type, domain, etc.
A user with the 'Portal administrator' role can view these statistics for all domains in the portal.
A user with the 'Portal back office' role can view these statistics only for the domains they have access to.
In the accountant portal, click on Management and then click on Reports.
In the now-opened screen, click on Productivity to view an overview of the number of transactions processed in the domains of the portal.
The following screen is always opened in the Transactions per user view:
To view an overview of all invoices or bank transactions automatically processed in the (sub)portal in a given period, select the following filters in the Transactions per document type view:
- Transaction type: automatically processed via match rules
- Period: indicate, if possible, from which period you want to view the data.
- Portal: the portal or just the subportal containing the domains whose processed transactions you want to view.
To view an overview of all invoices or bank transactions processed automatically by domain, select the following filters in the Transactions per domain view:
- Transaction type: automatically processed via match rules
- Document type: please select one of the document types shown below:
Standard, Electronic bank statement, Purchase invoice, Sales invoice (Yuki invoicing), Bank statement, Cash statement, VAT return, Financial import file, Pay slip, SEPA, General journal, Opening balance sheet, Payroll tax assessment, Unpaid invoice reminder, Sales invoice (uploaded) or Expense claim. - Period: indicate, if possible, from which period you want to view the data.
- Portal: the portal or just the subportal containing the domains whose processed transactions you want to view.
The filters underlined above refine each other and work as an AND rather than an OR.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article