Currently, Yuki does not yet allow you to use actual cost centers and cost carriers.
However, you do have the option of using projects and/or Yuki Analytical accounting in Yuki.
Projects
Costs and revenue, both documents and financial transactions, can be assigned to different projects.
From each project, you can view financial reports and request the P&L account.
Projects are only available when a user with the role 'Management' role has selected the Medium, Large or Unlimited bundle through the Yuki Store in the domain.
Project and Nmbrs® link
If you use the Nmbrs® link and projects in Yuki, you can set up that all costs of a cost center in a payroll journal entry imported from Nmbrs® will automatically be assigned to a project you create in Yuki. This project must have the same name as the cost centre in Nmbrs®.
For each project, access can be determined so that, for example, part of the financial administration can be released to one or more users without these users having access to the entire financial administration.
For a detailed description of the Nmbrs® connection, see article Nmbrs® link with Yuki.
Yuki Analytical accounting
In Yuki, you have the option of analytical posting. Analytical entries are processed off-balance sheet, which means that they are not actually posted to GL accounts in your administration. These cost and revenue entries are assigned to certain dimensions, such as cost centers and cost carriers, according to an analytic plan (view).
Yuki Analytical accounting is available only when a user with the 'Management' role has selected the Large or Unlimited bundle through the Yuki Store in the domain.
Permissions and roles
The 'Analytical accounting' feature is available only to a user with the 'Portal administrator', 'Portal back office', 'Management', 'Financial administration' or 'External accountant' role.
For a detailed description, see article Yuki Analytical accounting.
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