[AccessD] Payroll

Bob Heygood accesspro at gmail.com
Mon Apr 30 13:30:50 CDT 2018 

Rocky & Jim,
Yes I knew intuitively that I was breaking some normalization rules.
Just started to let the UI interface drive the schema.

For data entry the user insists on being able to "tab" through a whole pay
period (2 weeks) for each employee and job.

So, how do I use a table with only one record per day?
UNBOUND, I guess. And then via code stuff into a "proper" table........
I have done so before but a lot work.

Really don't need any other fields.

Thanks for responding,

Bob




-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Rocky Smolin
Sent: Sunday, April 29, 2018 4:36 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Payroll

Bob:

I think your timecard capture table should have one record for each day with
FK of Empl ID:

fldTimeCardID	Autonumber
fldEmplID	Number (FK)
fldDateWorked	Date
fldHours	Number(Double)
fldMultiplier	Number (for straight time(1), time and 1/2(1.5), double
time(2)

Obviously an Employee table.
And then a work period Start Date, End Date But for rate of pay since the
rate changes you should have a RateofPay
table:

fldRateOfPayID	Autonumber
EmplID			Number (FK)
fldRateStarDate	Date
fldRateEndDate	Date
fldBaseRate		Number (Double)

It's a little more complicated that way but that way you could reconstruct
their pay for any period in the past. 

But if all you want is hours without anything else then you don't need the
pay rate data.  But then why not just dump the timecards into a spreadsheet?
What is Access doing for you?

If you want to discuss, call me.  Or come over and in  short order we could
design the back end to just what you want.

R
760-683-5777


-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Bob
Heygood
Sent: Sunday, April 29, 2018 2:25 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Payroll

Thanks for the responses.
I should have been a bit more clear.
I am only tracking the hours worked per day per payperiod.
I will easily via a button dump into Excel for submission to the payroll
processer. Like ADT.

Bout settled on :
tblEmployees
tblJobs
tblTimeCard containing.. EmpID, JobID, Payperiod, Monday1Hours,
Tuesday1Hours.......... Monday1Hours15, Tuesday1Hours15,........
Monday1Hours2, Tuesday 1Hours2, .........
		then for the second week:  Monday2Hours, Tuesday2Hours......
Monday2Hours15, Tuesday2Hours15...... Monday2Hours2, Tuesday2Hours2

this allows for time, time and a half and double time.
Also, makes for easy and familiar entry.

tblEmployees contains pay rate info, so a little multiplication will give me
totals for the resulting sheet/query.

Tia

Bob


-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
James Button via AccessD
Sent: Friday, April 27, 2018 10:36 AM
To: 'Access Developers discussion and problem solving'
Cc: James Button
Subject: Re: [AccessD] Payroll

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

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

More information about the AccessD mailing list