[AccessD] Payroll

[James Button]

Deadly assumption(s)

Workers will only work 1 shift in a calendar day
Workers shift will be entirely within a calendar day
Pay will be at the standard rate(s) for all hours in a shift
Bonuses will be subject to tax 
Benefits in kind - car, fuel, or taxi's, meals , healthcare - various categories
and provision processes 
Benefits in kind - non taxable such as hydration drinks, uniforms and safety
equipment  
Newly introduced local, or state taxes 

I would consider the input of hours being a daily thing with all employees (and
contractors?, and agents?, and professional persons?) hours being entered by
rote working down the employee list - 
That list being ordered by category, location and maybe grading so 1 person
deals with input for management at a site and 1 person (maybe the same one)
deals with the general pay-scale workers.

Allow for - paid or not, hours 
holiday 
Sick leave, compassionate/extraordinary
Education/courses
Legally required 
Contractual
Pay in lieu of hours
Hours owed/carried forward
Meetings required to attend - performance, disciplinary, associated with the
employment

All should be considered as entries for that person's 'employment' in a period -
day

The input should be appropriate for easy verification that there is no
fraudulent input and submission to courts if required /ordered
There maybe a legal decision that pay is (or is not) required for the time spent
in such activities.

Then - for the actual payment - as in assembly of time for which payment is due,

That becomes the weekly, or other timing process 
Not forgetting the possibility of changes to the qualification and 'cash'
related to any and all the above at any time in the payment period.
Your payroll period is unlikely to match the legislative periods.
 

Also maybe worth having an 'acceptable'  max for each person (or job
classification) for the payment period and for the quarter, and annually

There should also be a very well managed process for implementing changes on
specific dates (and times) with the effects being applied from specific dates &
times - Local or other 
Consider employees abroad on behalf of the organisation

Payroll is a real pain in the head (and elsewhere) and that is without getting
retrospective adjustments from insurers,  government departments, and the courts

As well as evaluations by inspectors who cannot do basic arithmetic, speak the
language properly. Or even punctuate letters so their orders and requirements
are clear.

So - no template - but asuggestion that you keep at least 7 separate structures
- the business, the employee their contractual usability, qualifications  and
benefits, the activities they do, the payments due, the payments made, the
payroll & benefits declarations to the government, and the associated business
costings.

OK - they will all link into 1 actual composite, but keeping them separate makes
their management - with modifications, general data input and reporting easier
to manage as an IT facility.

JimB 


-----Original Message-----
From: AccessD <accessd-bounces at databaseadvisors.com> On Behalf Of Bob Heygood
Sent: Friday, April 27, 2018 4:21 PM
To: 'Access Developers discussion and problem solving'
<accessd at databaseadvisors.com>
Subject: [AccessD] Payroll

Hello to the list,
I am beginning design of a db to track payroll. The clients biz is such that
even though I suggested a "canned" solution, they need a custom.
But in order not to recreate the wheel I am looking for a template or a table
relationship to jump start me.
They use a two week pay period. Ideally they would choose an employee (already
have a table), then a pay period (already have a table listing dates for two
years) and then enter hours in 14 text boxes or maybe a list box ???

Tia
Bob