This is more of a brainstorming question, then an actual technical question. Currently my organization has a program that was created on an IBM iSeries for dues billing. The billing is based on the number of weeks that a person works in a month. Parts of this program aren't working correctly so I've been asked to re-write it in an Access database format, which is great. I've completed the first phase of the project which is to determine how much I need to bill for each week and then I sum that by month. I have two outstanding issues that I don't know how to handle...
1. I don't know how to handle a retro billing instance. For example, if we receive a date hire 2 months later and dues should have come out for one month already, how do I create a separate procedure for that billing?
2. I also don't know how to handle retro termination arrears removal. For example, if I billed out for the month of March, but they only worked for 3 weeks in March, how can I capture that change correctly.
I'm really just looking for some ideas on how to tackle this, not the in-depth technical part on creating it...