April 28, 2014 at 5:11 am
Hi guys i want to make database for payroll only but i don't know how to make structure for this
suppose i want to calculate payroll every month for employees as following
basic salary
bonus
overtime
absence
deduction
meaning
salary = basic salary +bonus+overtime-absence-deduction
How i make database (ERD)Diagram for this
Meaning tables i need and relations
April 28, 2014 at 5:20 am
i googled for "payroll database examples"
and went for images related to the search;
this is the first one tha it saw that appealed to me, but it's really up to you to find an example you are comfortable with:
the image comes from some opensource software at http://epayroll.sourceforge.net, so you might want to consider not reinventing the wheel, when there are so many exisitng options out there.
Lowell
April 28, 2014 at 5:56 am
April 28, 2014 at 8:40 am
ahmed_elbarbary.2010 (4/28/2014)
Hi guys i want to make database for payroll only but i don't know how to make structure for thissuppose i want to calculate payroll every month for employees as following
basic salary
bonus
overtime
absence
deduction
meaning
salary = basic salary +bonus+overtime-absence-deduction
How i make database (ERD)Diagram for this
Meaning tables i need and relations
My recommendation is that you shouldn't actually spend any time doing this because you're going to miss a whole lot of stuff.
For example...
I see nothing in here to handle 1099 employees.
I see nothing in here to handle taxes right down to the city level.
And if you do write one, the testing will take a whole lot longer than you could ever imagine.
My bottom line recommendation is to use some form of 3rd party software that is well established and very well proven. If you want control over the software, the buy "Quick Books", will also allow for imports and exports if needed. If you don't care about absolute control, the sign up for a Web Service that will do it.
Payroll is one of the most difficult things there is to get right. Considering that you're asking how to design the database, I'll suggest that you're not going to get it right. Buy a 3rd party solution.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 28, 2014 at 9:57 am
Jeff Moden (4/28/2014)
ahmed_elbarbary.2010 (4/28/2014)
Hi guys i want to make database for payroll only but i don't know how to make structure for thissuppose i want to calculate payroll every month for employees as following
basic salary
bonus
overtime
absence
deduction
meaning
salary = basic salary +bonus+overtime-absence-deduction
How i make database (ERD)Diagram for this
Meaning tables i need and relations
My recommendation is that you shouldn't actually spend any time doing this because you're going to miss a whole lot of stuff.
For example...
I see nothing in here to handle 1099 employees.
I see nothing in here to handle taxes right down to the city level.
And if you do write one, the testing will take a whole lot longer than you could ever imagine.
My bottom line recommendation is to use some form of 3rd party software that is well established and very well proven. If you want control over the software, the buy "Quick Books", will also allow for imports and exports if needed. If you don't care about absolute control, the sign up for a Web Service that will do it.
Payroll is one of the most difficult things there is to get right. Considering that you're asking how to design the database, I'll suggest that you're not going to get it right. Buy a 3rd party solution.
I agree with everything Jeff says, and I would recommend that you find a hosted solution, especially if it is for a fairly small organization.
Even if you buy third-party software, the number of changes to laws will give you a full time job applying changes to the software, so let that be someone else's problem.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply