For my customers the payroll would be the same as your's. Its an off the
shelf package.
For the main billing system I do for one customer. Fortunately, a year
ago I completed the first major rewrite. Y2K was a move from the
inherited RPG II (S/36) to RPG/400, DDS, date field types and only minor
logic changes. Besides moving everything to ILE I had seen more than one
sales tax in their industry (water and sewer) in the state and designed
the system in normalized database fashion so they effectively (but not
practically) have unlimited number of taxes.
I have also seen some retailers handle local option sales taxes as a
separate line item so they should be just a configuration away from ready.
Roger Vicker, CCP
On 3/21/2008 9:15 AM, Chris Durbin arranged the binary bits such that:
This is not a "for or against" discussion, but rather a "cause and
effect" discussion.
There is a move to get the "Fair Tax Act HR25" passed, eliminating the
federal tax and replacing it with a national sales tax. How much cost
and changes would we (the RPGLE programming world) have to effect if
this change if enacted? Would it be like Y2K, or just some minor
changes.
In our case, the payroll system and our sales system would have to
change. Our payroll system is a bought product, so no changes there for
us, only our vendor. Our sales system is home grown, and would have to
incorporate a new tax field in all programs that deal with sales
calculations. Also some way to summarize and send the tax through the
GL would be required, but nothing huge to overcome at first blush.
