Disclaimer
All screenshots in the article were taken in the Dutch version of Yuki.
In this overview you can see all the scopes that have currently been created for the selected analytic view.
In a scope you determine which transactions should be analyzed within your analytic view. These form the input of your analytical accounting, as it were.
Only a user with the ‘Portal administrator’, ‘Portal back office’, ‘Management’, ‘Financial administration’ or ‘External accountant’ role can create or delete one or more scopes.
From this screen, a user can::
- create a scope
- change a scope
- delete a scope.
Click on the Financials icon in the navigation bar and then click on Analytical accounting.
In the now-opened screen, select the tab of the analytic view for which you want to view the scope(s) and click on the Go to dashboard button.
Then click on the Scopes tile in the now-opened screen.
The following screen is opened:
The scopes of the sample analytic view 'Revenue and costs by department' have already been created here:
- GL account type: Revenue
- GL account type: Costs.
Create scope
To create a new scope, click on the Create scope button.
The following screen is opened:
For a detailed description, see the article Create scope.
Change scope
Hover your mouse over the line of the relevant scope, click on the button with the three dots and then click on Edit in the dropdown menu.
The following screen is opened:
Change the relevant data and click on the Save button.
All transactions that meet the set input criteria of the changed scope for the selected period and fall under an existing allocation rule will be automatically assigned to the relevant value(s) by Yuki.
Delete scope
Hover your mouse over the line of the relevant scope, click on the button with the three dots and then click on Delete in the dropdown menu.
The following screen is opened:
Click on the Delete button to actually remove the scope from the analytic view.
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