Professional Documents
Culture Documents
OI Central Staff Cost Repository Simver
OI Central Staff Cost Repository Simver
OI Central Staff Cost Repository Simver
______________________________________________________________________________
Last update on 7 Jan 2010
-1-
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
1 Background
Starting from March 2010, Otto International (OI) will adopt a single finance system
(Navision) for all OI offices. The system will reflect the latest OI hierarchy and
dimensions like entity, business unit (BU) and functions, in order to provide the
management the right pieces of information.
One of the key sets of data, the staff cost, needs to be allocated to the right dimensions
and fed into Navision as well. Because of the complexity, using manual way to perform
the new staff cost calculation and allocation will be a challenge. An automatic,
computer driven approach is necessary to ensure accuracy and efficiency and in order to
meet the tight accounting schedule every month.
To build different interfaces between Navision and the local payroll systems in individual
offices is another challenge. These interfaces will hardly be completed within such short
time frame (However, interfaces from the payroll system (IPL) used by the HK and
China offices have been implemented before and will be modified to suit the current
purpose). That is why this proposal comes up, to implement a single secured system
with simple user interface to collect data from all offices, to do the allocation and to post
data to Navision. This document provided a high level system design on this proposed
solution, the implementation details, costs involved and a rough time schedule.
______________________________________________________________________________
Last update on 7 Jan 2010
-2-
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
2 Requirements
The below requirements are collected from our colleagues in HR, Accounts and IT
departments in HK.
Covered
in the
Type Requirements proposal Reference
Prerequisite
Up-to-date staff cost allocation rates have to be maintained Yes HR need to
in the existing staff bank database. It should cover all the communicate the
staffs in OI dead line for
update
The existing local payroll process and local requirements Yes
should not be changed
Full payroll details of new joined staff and leaving staff must Yes HK HR confirmed
be entered into IPL and post to the centralized repository that this can be
(HK and China offices) achieved
Some staff costs need to be approved and realized in the Yes To be handled by
middle of a month are entered into Navision currently before a new
the payroll process start. A mechanism needs to be in place reimbursement
to ensure they are allocated to the new dimensions system
correctly.
Basic
features
A centralized database storing the monthly staff payroll and Yes
expenses details. It should cover all OI staff as well
The payroll details should be broken down into the sub- Yes 3.4
accounts of the five different staff cost categories, namely
salary, bonus, benefit, rental and utility, social security
The payroll details should include the relevant bank or cash Yes 3.4
accounts or third party accounts, payment date, relevant
posting month, currency, expatriate or local terms, full or
partial payment (for terminated staff), etc
A program to calculate and allocate the staff cost into the Yes Appendix –
new OI dimensions Calculation Logic
______________________________________________________________________________
Last update on 7 Jan 2010
-3-
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
Covered
in the
Type Requirements proposal Reference
Security
This centralized repository must be independent from the Yes 3.3
existing IT environment that only HR staffs have
administrative access, not even the IT administrators
The user maintenance of this repository should be managed Yes 3.3
by HR only
The system implementation is preferably outsourced to an Yes 3.3
external company, for security reason
Users of each office can only access data of their own Yes 3.1
offices. Every month after posting they will no longer see
and print old data from the repository
Navision
interface
The entity input from the offices will be adopted, instead of
using the entity from staff bank.
An interface to send the allocated data in lump sum, but Yes 3.6
broken down by right chart of account (COA) and
dimensions, to Navision. No individual staff name will be
sent outside the centralized payroll repository
Accrual records for profit sharing bonus, the 13th and 14th
month salaries to be generate automatically (HK offices)
______________________________________________________________________________
Last update on 7 Jan 2010
-4-
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
Covered
in the
Type Requirements proposal Reference
late entries of staff costs should refer to the allocation rates Should be
of the corresponding month OK
Interfaces
to other
systems
An automated system interface to post monthly payroll data Yes 3.1
from IPL HR system to the centralized repository, with all Data mapping will
required details, and a closing mechanism to make sure the be handled by
posted data is final CSR via SP in
Navision
The bank payment record will be generated by CSR. The
bank account is defined according to the auto-pay flag and
currency
Staff headcount statistics will be derived from the monthly Should be
copy of staff allocations and will pass over to the budget and OK
reporting system (Clarity)
Process /
Control
The payroll is not limited to monthly basis. Weekly payroll Yes 3.1
should also be possible. However, the closing will be done
every month to align with the accounting process.
A copy of the staff allocation rates to be saved every month Yes 3.1
for allocation and calculation of that month and for future
reference and reporting
A set of comprehensive reports for data verification after the Yes Appendix –
calculation and allocation Validation Reports
The offices need to make sure the staff costs entered into Yes 3.1
the centralized repository match with the actual payroll Finance teams
need to work out
some controlling
procedures
Others
Ways to allocate benefit that cannot be separated by staff to Finance teams to
all BU in an entity provide details
______________________________________________________________________________
Last update on 7 Jan 2010
-5-
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
3 Propositions
3.1 The Process
1. Managers of business unit (MBU) and Entity managers need to keep the staff
allocation details in Staff Bank up-to-date (but not the allocation for future).
2. An image of these allocation rules will be captured in the beginning of each month
and saved in CSR
3. All offices continue to prepare staff payroll in their existing systems, like HK and
China offices using the IPL HR system. The payroll is not limited to monthly basis.
Offices can perform weekly payroll or ad hoc payroll for staff that leaving in the
middle of a month.
4. Staff costs that need to be paid or reimburse in the middle of a month will be
entered into a new reimbursement system where the costs will be allocated
according to the image of current month allocation rules and then post to Navision
5. Final Payroll data in IPL will be posted to the Central Staff Cost Repository (CSR)
during a month-end process
6. Offices that are not using IPL will need to feed their final staff payroll details to the
CSR through a secured web front program (see 3.5 below).
7. The CSR will calculate the offices payroll data according to the allocation details and
generate lump sum figures per entity per business unit and function. The calculated
data will further be transformed to accounting requested format/breakdown and
upload to vouchers in Navision (see calculation logic in appendix).
8. The accounting teams will validate the uploaded payroll data against the information
sent from offices, before posting the vouchers into Navision. Once the posting is
done, the payroll data of that month in the CSR will be locked.
Non-IPL offices
MBU and Entity managers IPL offices (HK + China)
Prepare payroll in local
Update staff allocation in staff bank Prepare payroll in IPL
system or Excel
Individual
Non-IPL offices
Calculated staff staff
Input payroll data to
cost in Lump Sum Central payroll centralized repository
Payroll details
Navision
Repository
______________________________________________________________________________
Last update on 7 Jan 2010
-6-
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
3.2 Security
Database and server: A single dedicated database will be setup solely for this
purpose. It will be resided in a server in the HK data centre, next to the Navision
server. The server, however, will be hosted independent from the OI domain
User access: Both the database and the server can only be accessed by authorized
users. HK HR department will be the only party to manage the user access, not the
IT administrators.
Connection: The connection from user workstations to the system will be encrypted
by SSL technology plus login control to ensure no data leak during data transmission.
Each user is limited to see his/her own data only.
Web front
input form
Hamburg
SSL Encrypted
Italy
Central Hong Kong
Payroll Repository Data Center
Turkey
China
Hong Navision
Kong
OI Domain
Development team: The development and implementation of the CSR, the Web
Front Input Interface, the posting interfaces and user maintenance will all be
outsourced to external developers.
______________________________________________________________________________
Last update on 7 Jan 2010
-7-
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
We propose to use an MS Excel like interface for the input screen. It requires less
training and is more flexible for data editing and copying.
______________________________________________________________________________
Last update on 7 Jan 2010
-8-
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
4 Implementation
______________________________________________________________________________
Last update on 7 Jan 2010
-9-
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
business bu function
entity staff id unit name allocation % function name allocation %
OI HK Test4.Sun 3Suisses 50 Sourcing 100
OI HK Test4.Sun Bon Prix 50 Sourcing 100
HKD bank
Test4.Sun No 25/Nov/10 HKD 1,200 4011001 Salary 1502501 account 10/Nov/10
HKD bank
Test4.Sun No 25/Nov/10 HKD 600 4011201 Bonus 1502501 account 10/Nov/10
HKD bank
Test4.Sun 25/Nov/10 OI HK Bon Prix Sourcing HKD 600 4011001 Salary 1502501 account
HKD bank
Test4.Sun 25/Nov/10 OI HK Bon Prix Sourcing HKD 300 4011201 Bonus 1502501 account
HKD bank
Test4.Sun 25/Nov/10 OI HK 3Suisses Sourcing HKD 600 4011001 Salary 1502501 account
HKD bank
Test4.Sun 25/Nov/10 OI HK 3Suisses Sourcing HKD 300 4011201 Bonus 1502501 account
______________________________________________________________________________
Last update on 7 Jan 2010
- 10 -
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
Case 2 – a staff works with 2 internal functions and left the company in
the middle of a month
______________________________________________________________________________
Last update on 7 Jan 2010
- 11 -
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
Case 3 - an expatriate staff with rental arrangement
business bu function
entity staff id unit name allocation % function name allocation %
OI HK Test2.Wong Bon Prix 100 Sourcing 100
Test2.Wong Yes 25/Nov/10 USD 2,000 4011002 Salary 1502502 USD bank account can be generated by IPL
Test2.Wong Yes 25/Nov/10 USD 1,000 4011202 Bonus 1502502 USD bank account can be generated by IPL
Offset to rent prepayment, can be
Test2.Wong Yes 25/Nov/10 USD 500 4011302 Rental 1703200 Prepaid account generated by IPL
Test2.Wong Yes 25/Nov/10 USD 100 4011452 Benefits 1502502 USD bank account can be generated by IPL
Credit COA
Pay- Debit COA Description of Bank /
Payment Business Curr- ment of of Payment other Description of Bank /
Staff ID Date Book Unit Function ency Amount Payment COA accounts other accounts
Test2.Wong 5/Nov/10 OI HK Bon Prix Sourcing USD 500 1703200 Prepaid 1502502 USD bank account
Accrual
account for
Test2.Wong 25/Nov/10 OI HK Bon Prix Sourcing USD 2,000 2302200 expat staff 1502502 USD bank account
Test2.Wong 25/Nov/10 OI HK Bon Prix Sourcing USD 2,000 4011002 Salary 1502502 USD bank account
Test2.Wong 25/Nov/10 OI HK Bon Prix Sourcing USD 1,000 4011202 Bonus 1502502 USD bank account
Test2.Wong 25/Nov/10 OI HK Bon Prix Sourcing USD 500 4011302 Rental 1703200 Prepaid account
Test2.Wong 25/Nov/10 OI HK Bon Prix Sourcing USD 100 4011452 Benefits 1502502 USD bank account
Social
Test2.Wong 25/Nov/10 OI HK Bon Prix Sourcing USD 100 4011602 Security 2302500 other short term liability
______________________________________________________________________________
Last update on 7 Jan 2010
- 12 -
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
OI HK Test1.Chan OI HK OI DG
Credit COA
Pay- Debit of Bank /
Payment Business Curr- ment COA of Description of other Description of Bank / other
Staff ID Date Book Unit Function ency Amount Payment Payment COA accounts accounts
C/A account of
Test1.Chan 25/Nov/10 OI HK Bon Prix Sourcing HKD 2,600 262000 OI DG 1502501 HKD bank account
Accrual
account for
Test1.Chan 25/Nov/10 OI DG Bon Prix Sourcing HKD 1,000 2302300 local staff 242016 C/A account of OI HK
Test1.Chan 25/Nov/10 OI DG Bon Prix Sourcing HKD 1,000 4011001 Salary 242016 C/A account of OI HK
Test1.Chan 25/Nov/10 OI DG Bon Prix Sourcing HKD 500 4011201 Bonus 242016 C/A account of OI HK
Test1.Chan 25/Nov/10 OI DG Bon Prix Sourcing HKD 100 4011601 Social Security 242016 C/A account of OI HK
______________________________________________________________________________
Last update on 7 Jan 2010
- 13 -
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
The allocated staff costs of all the above cases will be transformed to a
Navision Voucher in this structure:
______________________________________________________________________________
Last update on 7 Jan 2010
- 14 -
Central Staff Cost Repository – Reviews and Proposals
_________________________________________________________________________________
Reports
Payroll detail list per Entity
Payroll summary per Entity
Allocated staff cost detail per Entity
Allocated staff cost summary
Allocated staff cost with detail COA mapping
Allocated staff cost summary by COA
______________________________________________________________________________
Last update on 7 Jan 2010
- 15 -