'Transactions' report

Modified on Thu, 25 Jul at 9:53 AM

Disclaimer

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


In the Yuki accountant portal, from the 'Transactions' report, two views are available regarding the history of transactions processed in a given period in each domain:

  • Transactions per domain
  • Transactions per administration.


Only a user with the 'Portal administrator' role can view this report.


A user with the 'Portal back office' role does not have access to the 'Transactions' report.


Statistics are kept of, for example, the total number of transactions processed per month or the percentage of automatically processed transactions. 


In the accountant portal, click on Management and then on Reports

In the now-opened screen, click on Transactions to view an report of transactions processed by back office employees as well as automatically by Yuki in the portal's domains.


The following screen is always opened in the Transactions per domain view:



Views

You can also indicate in this screen that the Transactions per administration view should be shown:



Filters

In both views, you can filter the shown data by Document type

  • 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)
  • Expense claim.


In addition, you can use an extended filter by clicking on the filter button in the upper right corner of the search/filter bar:



Allows you to filter the displayed data by back office role in a domain:

  • Responsible
  • Backup
  • Controller
  • Account manager.


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