469,622 Members | 2,155 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,622 developers. It's quick & easy.

Payroll DB

Hi all,
New to Access......
Trying to create a payroll database for employees
who are paid on the 1st and the 15th of the month.
This is quite different than every 2 week pay periods.

Employees work all hours of the day, any day of the
week, depending on their assignment, and this can change
from day to day. But employees must remain under
40 hours per week. The 1st and 15th pay periods,
of course, lead to carryover hours from one week
to the next. This needs to be tracked to avoid overtime.

As an added twist, some employees work in multiple
categories at differing rates of pay during any given week.

Any pointers, ideas or clues?

Thanks!

Mark
Nov 13 '05 #1
4 1757
Per Mark T.:
As an added twist, some employees work in multiple
categories at differing rates of pay during any given week.

Any pointers, ideas or clues?


My first reaction is that payroll sounds like such a bread-and-butter
application that there must be hundreds - if not thousands - of off-the-shelf
applications that can do it cheaper, faster, and better than one person can.

The one payroll app that I've done was extremely complicated (state/local taxes,
various withholdings, special payments, medical coverage, direct deposit....the
list goes on).

Something like that can eat you alive - and often for no good reason bc there's
a canned solution that will do 90% of what the users want for 5% of the cost of
rolling your own.
--
PeteCresswell
Nov 13 '05 #2
Hi Pete,
Thanks for the info. I'm pretty sure that Peachtree
or something else could do it. We don't internally
process the taxes, etc. We sub that out to a payroll
company. All we do is compile hours
in various categories at different rates of pay for
multiple employees, from time sheets they fill out
in the field and fax over. We do this internally so that
we can audit the managers who sign off on the timesheets
and ensure accuracy / validity.
Example:
Sam worked 5 hours at B House on Tues. the 3rd
and 7 hours on Friday the 6th @ $12.00 / hr.
Sam also worked 2 hours at C House on Tues. the3rd.
at $11.25 / hr.
He also worked 2 hours at D House on Tues. the
3rd @ $13.75 per hour.
This happens with about 100 employees working
on various assignments.

Thanks again,
Mark
Nov 13 '05 #3
Per Mark T.:
employees
who are paid on the 1st and the 15th of the month.
This is quite different than every 2 week pay periods.

Employees work all hours of the day, any day of the
week, depending on their assignment, and this can change
from day to day. But employees must remain under
40 hours per week. The 1st and 15th pay periods,
of course, lead to carryover hours from one week
to the next. This needs to be tracked to avoid overtime.


In the couple of apps I've done like that, it's been:

tblEmployee
tblTimeSheet
tblHours
tblPayPeriod

With supporting tables like:
tblDepartment
tlkpCostCenter
tlkpHoursType
tlkpJobCode
tlkpHoursTypeDifferentialFactors

Employees have TimeSheets: one for each pay period.

A TimeSheet has PayPeriodID, plus other ingredients added to the user's taste
like ApprovedBySupervisor, ApprovedByPaymaster, PaymentMade, CheckNumber,
DirectDepositControl#, and so-forth.

PayPeriods have a PayPeriodID (PK), PayPeriodNumber, and PayPeriodDate.

An hours record has HoursType, DateWorked, NumberOfHours, HourlyRate, and a
bunch of other stuff, depending on what is desired.... like WorkLocation,
StartTime, and so-forth.

Seems to me that as long as you have the date for every hour worked, you can do
40-hour/week validation, even on a rolling basis...
--
PeteCresswell
Nov 13 '05 #4
Per (PeteCresswell):
An hours record has HoursType, DateWorked, NumberOfHours, HourlyRate, and a
bunch of other stuff, depending on what is desired.... like WorkLocation,
StartTime, and so-forth.


The one 'gotcha' is a pivot-table presentation of hours. Generally, the
timekeeper or other user wants a pay period's hours presented in a seven-column
grid where columns are Monday, Tuesday, Wednesday, and so-forth. In the
two-week period that would expand to 14 columns - more or less depending on
end/beginning year periods.
--
PeteCresswell
Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Randi | last post: by
reply views Thread by zexx | last post: by
1 post views Thread by kgatchell2001 | last post: by
8 posts views Thread by John Sitka | last post: by
reply views Thread by sajithamol | last post: by
4 posts views Thread by jnce | last post: by
reply views Thread by devrayhaan | last post: by
reply views Thread by gheharukoh7 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.