July 6, 2009 at 1:31 pm
Hi All,
I need to design a Payroll database for my Mid Size Company. Our Employees are all salary based and get monthly payed. Any suggestion or Sample database ?
thanks in Advance
July 6, 2009 at 1:57 pm
Any reason to not use something off-the-shelf? There are plenty of payroll applications that you could buy much more easily than you can build one. Plus, they have the advantage of often having legal compliance taken care of in them, instead of having to design and build all of that.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 6, 2009 at 2:07 pm
Our Boss wants something unique not one off the Shelf. Plus the Application will be simple just keeping monthly payroll and reports
July 6, 2009 at 2:29 pm
Then the key thing will be to get your boss to articulate exact needs on the thing. What kind of reporting will it need to do? How about history? What about legal and other regulations? Security issues (who gets to see what in the database)? Will it have anything to do with performance reviews? Will it store Social Security Numbers, and if it does, how will they be secured? What about database encryption? What kind of front-end will it have, and what features are expected in it? And so on.
Once you have all the use cases and all that worked out, then you'll need to move on to logical design. Till you have all the use cases and feature requirements and so on, there's no point in trying to get code samples and all that.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 6, 2009 at 2:41 pm
A payroll system (in the U.S.A.) would normally contain columns for an array of payroll deductions. For example
1. Number of dependents declared
2. Filing jointly or as a single individual.
3. Amount deducted for Social Security tax.
4. Amount deducted Federal Income tax.
5. Amount deducted for State Income tax.
6. In many locations:
a. Amount deducted for school district taxes.
b. Amount deducted for fire district taxes.
c, So called right to work tax deduction (Thinking of PA.)
d. Workmen's compensation
Other items to be recorded and tracked.
1. Monthly salary per individual.
2. Rates, generally a percentage of gross wages, for each deduction.
3. Maximum sum to be withheld for each deduction.
Capability of summing all these withholdings and submitting the payment and documentation to the various taxing authorities in accordance with applicable legal requirements. Not to mention the time period required to maintain these records ....
So do you really want a payroll system or ? ? ? ? ?
July 6, 2009 at 3:17 pm
This Payroll System will not be apply to USA System. This will be in Europe. That's why we need a Unique System since the most of Software system are based on USA System
July 6, 2009 at 3:19 pm
vblllove (7/6/2009)
This Payroll System will not be apply to USA System. This will be in Europe. That's why we need a Unique System since the most of Software system are based on USA System
Are you saying that there are no COTS Payroll Systems in Europe??
July 6, 2009 at 5:01 pm
vblllove (7/6/2009)
This Payroll System will not be apply to USA System. This will be in Europe. That's why we need a Unique System since the most of Software system are based on USA System
What country are you located in?
"Europe" is still wide spread in terms of payroll systems (among many other things)...
I'm not sure what you want to cover but as soon as it gets into legal subjects (like taxes, social security fund, health insurance a.s.o.) you'd have to make sure your application meets legal requirements...
As much as I like to program applications, the phrase "legal requirement" usually stop me from thinking about any in-house development...
As far as I can see there is no requirement for a thing like "Unique Payroll System" - even in Europe.
I strongly recommend that you'll try to convince your boss to go with some "of-the-shelf"-software, since that stuff usually meets legal requirements.
[SET humor ON]
If you'd like to get something unique, you might want to enter the amount available per month and divide it evenly as some sort of predefined tax-optimized company shares.
[SET humor OFF]
July 7, 2009 at 12:16 am
Albania, I dont know if you heard about that..
July 7, 2009 at 2:16 am
Since Albania submitted an apply for admission to the EU, you'd be faced with European (minimum) standards in terms of taxes a.s.o. sooner or later.
If you'd do your payroll system as an inhouse development now, you'll most probably need to get "off-the-shelf"-software by then.
I'm not sure if it's worth the effort...
Btw: I'm located in Germany so I've heard about Albania before. 😉
July 7, 2009 at 7:08 am
Yes, I've heard of Albania. I have no idea what your legal requirements are going to be, but that will be the first thing you need to nail down in terms of designing the software. Tell your boss you'll need to consult with a lawyer (or whatever would be appropriate in that role). There are almost certainly employment legal professionals who can tell you what you need to incorporate.
It will include taxes, it might include things like benefits (in the US, there are different rules for different types of health insurance deduction, you probably have something similar on some subjects, but possibly not health insurance).
You might need to be able to create ad hoc deductions. In the US, the courts can take a piece of your salary/wages for things like child support or back taxes, or paying off federally funded student loans. It's called "garnishing wages". You'll need to find out if that kind of thing is possible, and, if so, you'll need to set it up.
Consult with a good lawyer on the subject. They'll have more accurate and complete lists of advice than we will here. Once you know exactly what the system will need to do, we can help with the technical aspects, but (so far as I know) none of us are qualified to offer legal advice for your situation.
What you might also do is check with other local businesses. Even if you walk down the street your office is on and just go into other offices. See what they've done. People are often willing to help out on that kind of thing. I wouldn't recommend asking a competitor for help, but anyone else will probably be willing to give you some advice on the thing. (And, if you find that nobody has a good solution, and you work out how to produce one, that might be a market for you!)
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
July 7, 2009 at 8:12 am
I've known many bosses who want what they want.. But ROI and costs often cause them to rethink it. Payroll in the EU or even Albania cannot be an uncommon thing.. Everybody has to pay, I am almost 100% sure that you could acquire a MORE than adequate system to do payroll for your area and the EU for considerably less than you could build one.
If you were dead set on building one GSquared I think was on the right track with determining use cases, you should understand exactly how it will be used before writing code. I used to want to jump right in myself, but over time I realised that is I did as much planning upfront as possible I would write less and better code later because it hadn't gone through all the iterations of changing how things worked, I had figured out most things before the code was written..
CEWII
July 7, 2009 at 9:14 am
Actually, in most cases, I'm a believer in "find something you can build that will help the end user and build that, then evolve it into something better step by step". I like frequent releases that incrementally and evolutionarily improve things for the users. The best software I've seen has been built that way.
BUT, payroll is usually so sensitive to legal issues that it requires more of a waterfall method. If you build anything at all, it better not create legal liabilities that can result in the company being forcibly shut down and in people being prosecuted on criminal issues. Kind of hard to guarantee that without serious planning and consultation before-hand.
Most systems don't require that, but anything HR-related generally does. I'd do the same for anything that was going to be involved in medical decisions, or anything related to nuclear power plant management, and so on.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply