Vis artikel på:
Follow

Implementation proces

1) Start 2) Integration of data 3) Implementation proces
Power of attorney> To Acubiz > From Acubiz > Progress > Test > Go-Live >

implementation Process

As a rule, the implementation process will be so.

  1. Implementation meeting, including integration, configuration and setup:
  2. Customer test period (POC)
  3. Continuous follow-up and preparation for Go-Live
  4. Internal communication to users around the new system
  5. Go-Live

implementation Meeting

At the implementation meeting, a dialogue is held on the accounting principles, flow and processes, as well as setting up and configuring Acubiz EMS to handle the company's wishes and needs.

The goal for this day is that a (reasonable) clear Acubiz EMS solution is provided. There may be areas that are not fully configured and created, but it is possible to conduct a thorough test of Acubiz before the second implementation meeting. The topics being discussed are specifically:

  • Approves flow
    Who is the user's approver? Is it a direct boss or is there possibly project or department approval? Has the user a procurement limit for what is required for approval. Does the approver have a procurement limit on how much the individual must approve for? The flow in Acubiz is:
    EMPLOYEES => APPROVES => FINANCE
    This is the flow in Acubiz before the transactions comes to bookkeeping.
  • Dimension setup (posting string)
    To get the correct posting string, talk about what dimensions are used in the company. Ex. Department, cost center, project etc. Are there dependencies between the dimensions and which must be visible to the user. Here you have to think a lot about "What can the user decide on". Not all users are account and VAT experts.
  • Chart of accounts / cost types
    In Acubiz, a chart of accounts must be created for users to post their costs. It is important that these are created with the end-user in mind. It must be easy and clear. The name of the cost type must be indicative of the receipt by the user. VAT codes (which the user does not have to see) etc. must be considered. company policies for respectively users and accounts.
    See if any. Acubiz proposal for cost types: ExpenseTypes(Account template).xlsx
  • Acubiz posting principles
    There must be talk of how the thoughts from Acubiz's side are about the posting principles. How to be posted in the different situations and at what times. Link to the posting principles>
  • Payroll data
    Should employee claims / outstanding claims be registered in a payroll system. In which case which payroll system is concerned and which payrolls must be registered.
  • Email setup
    Which emails should Acubiz send to users and at what times. What should be in these emails.

Customer test period (POC)

After the first configuration meeting, one (or more) usable Acubiz EMS solution (s) is provided. Here, the customer will be able to test for a period based on real data and review the setup that is made from the first implementation meeting.

Nothing is chiseled in granite so changes can be made continuously before Go-Live.

Continuous follow-up and preparation for Go-Live

Details of the daily use of Acubiz, including the ADMIN and FINANS roles. The implementation meeting may have covered the areas, but it is expected that Acubiz has been set up and configured to focus on use and flow and Go-Live.

Internal communication to users

The new Acubiz system must of course be introduced to all relevant employees in the company. There are several methods for this and these can be used in different combinations, for example:

  1. Welcome email

 - Template to fast track users

 - Template to Expense reports

     2. Internal joint meetings with introduction
     3. Workshops

As a starting point, it is the company itself that is responsible for these initiatives via the super users who are trained via another implementation meeting.

After that, Acubiz is ready for Go-Live.

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk