On 02/23/2012 04:20 PM, Chris Travers wrote:|
I think we'll be able to plug in appropriate rules if there's a model we can use to get started.
Main things I'm thinking about needing here:
- tracking employer, employee contributions to each of the various taxes we need to pay, with variable rates for each. e.g. unemployment insurance varies quarter by quarter and employer by employer.
- tracking accumulation of PTO (Paid time off) which in our case accumulates per hour worked for hourly employees, and per pay period for salaried -- probably need to support a variety of rules based on company policy
- tracking usage of PTO
- we do PTO instead of splitting out sick leave, vacation, etc but a payroll system needs to accommodate these things
- calculate overtime per week
- schedule tax payments, post to correct accounts
- quick bulk entry of hours per pay period -- we don't use the LSMB timecard feature, we have another system for this.
At this point, I still don't have that much time to contribute. If there's a framework in place for this, I'd probably be able to do some fleshing out of individual resources.
I think the first step is getting a framework in place that defines the endpoints, the formatting of the data, etc. Something that converts a web service payload into some sort of Perl object that can be populated based on LSMB data.
Then it's a matter of doing that mapping between the web service and the LSMB data structures. I would think there's some low hanging fruit here:
* account list, to populate GL transactions
* vendor/customer lists
* part lookups
* menu lookup
Without getting into any financial transactions at all at first, just providing simple access to JSON-formatted data for those items would facilitate making the user interface much nicer. Even if it's read-only to start...