Re: Payroll

Tech-Archive recommends: Fix windows errors by optimizing your registry

There are several challenges here, both on learning the key info and that
this will be a project rather than just one post/question. But here's and
idea on structure.

It sounds like payheadmaster has one record per employee or may actually be
an employee table. I'll call that the "Employee" table.

It souds like your pay and pay records are a once-per month summary.

So, one "Employee" table which has all of the "once per employee"
information. Plus a PrimaryKey "EmployeeNumber"

Next a "Pay" table which has a record for each instance of a monthly entry
for an employee. It will have an "EmployeeNumber" field (NOT a PK), and
link it to the Employee table (EmployeeNumber to EmployeeNumber). It will
have a PayDate field It will have fields for all of the data that changes
pay-period to pay-period. Any calculations where the "equation" never
changes will run at the instant that you are providing the data (via a report
etc.).

Just a start, but hopefully on a foundation of a good underlying structure.







"SHETTY" wrote:

Payment is on monthly attendance basis,
full day or half day attendance absence can be marked
Casula leave -6, Sick Leave-6 & Paid Leave -30 will be provided
leave taken in exess of above will be dedcuted from salary (loss of pay)

Leave under each of above head will be credited to respective A/c only at
the end of calender year ie 31st December. Employee can carry forward PL up
to 180 days , Sick leave up to 15 days, Casual leave cannot be caarried
forward.

Payheadmaster table stores pay details as per appoitnment order
Structure
ID (PK), EmployeeCode (FK), Basic, Da, & other pay heads including
profession tax and other deductions

at present one LOP (loss of pay days) field is provided in above table and
no of days leave to be deducted updated in that field and pay head under
each head is worked.

There will be defferent profession tax applicable for defferecent states.
Profession tax slab is pre defined and can be called for each branch or
employee wise also

There will be 3-4 grades in basic salary and modification in salary master
will happen April month of every year

Apart from monthly salary following will be paid occationally
Paid leave encashment,Leave Travel allowance, Medical expenses
reimburshment(non taxable), statutory bonus, performacne incentives, all of
above must be added total yearly salary . Our financila year is April to
March

Hope I have provided all the required information

Please guide me

Ramesh

"Fred" <Fred@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F58B28A0-A098-456A-B489-7EFEC9188B74@xxxxxxxxxxxxxxxx
A core question is: what level of detail is going into the DB? For
example:

- punch-in and punch-out times from time clocks. (e.g. Access is doing
the
hours calculations)
- total hours, holidays, sick days etc.
- just pay for the pay period.

Also could yu clarify what your payheadmaster table is?


"SHETTY" wrote:

Dear Friends

I am planning to design a database for maintaing payroll information. At
present i am using database where in I am unable to maintain historic
data
like details of previous months. I have payheadmaster and employee master
table. Reports and payslips are generated through querries from master
table itself. data changes will be made in master table itself

Can anyone guide me how to create a database where in I can
maintain/store a
data for elapsed previous months also. Report for any given period. There
will not be major changes in the payhead and employee data month after
month
, changes may be to the extent of 2%
So I think it may not be good design if a store salary releated
information
for everymonth and every employee. Is there any other way where I can
list
only the changes in pay head data

thanks

Ramesh






.

Relevant Pages

  • Re: Payroll
    ... Employee can carry forward PL up ... Payheadmaster table stores pay details as per appoitnment order ... There will be 3-4 grades in basic salary and modification in salary master ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Multiple keys and transition constraints
    ... EMPPOS ... EMPLOYEE ... $1/hr pay cut. ... there are two candidate keys: ...
    (comp.databases.theory)
  • Re: Payroll
    ... would be to do it without using any database implementation terminology. ... The update to pay table will be based on the attendance leave status etc. ... It sounds like payheadmaster has one record per employee or may actually ...
    (microsoft.public.access.tablesdbdesign)
  • Re: My take on the flawed "Fair Tax" (repost)
    ... Because we have PITAX we work to pay ot. ... > real cost to employers, however, the real compensation to the employee is the ... All the employer does is fulfill a tax collection obligation. ...
    (misc.taxes)
  • Re: Watching Barrett-Jackson
    ... Buffett included this in his 40% figure I think, and if the money is being taken out of your gross pay and sent to the government, I would call it a tax, rather than a benefit, although I think they call it a "contribution". ... show me an employee that I am guaranteed to come out ahead on and I'll hire them on the spot. ... I'm not even guaranteed to make a profit on me, and I'm one of my better employees. ... I believe Mr Buffet was comparing the small percentage that the govt takes on dividends and capital gains from money he gets to the larger percentage that the govt takes of her wages. ...
    (rec.motorcycles.harley)