Hi all!
My development team has brought this to my attention a few times now so I'm wondering if this happens elsewhere and if there's a way I can fix it.
Sometimes when they are setting up a monthly pledge, they select their billing schedule and instead of the amount being broken evenly over X number of months it is broken out into a weird number (1 cent short of what it should be) and the final amount has the differences added to it.
For example, if the patron should be paying $10 per month for 12 months the billing schedule wants to charge them $9.99 for the first 11 months and then $10.12 for the last month.
The amounts can be changed manually so it isn't a huge deal. Just fairly irksome. It also appears to be happening randomly. 95% of the time the schedule works as it should... just that 5% of the time it goes wonky.
Any thoughts?
Thanks in advance for any advice!
I have a similar problem, but with ours, it's the dates. If I have a pledge that I want paid/due on the 15th of each month and split it into 12 payments over the year, the default dates that pop up are random (2/7, 3/18, 4/27, 5/3, etc.) and I have to manually edit them to be the same date each month. Any tips for solving that problem? Thank you!
Alaina Smith, Development Coordinator, Broadway Rose Theatre Co.
Again I would look at TR_BILLING_SCHEDULE, check the Bill Dates column. Here's some information from the system table documentation
http://www.tessituranetwork.com/network/Learning/Documentation/System%20Administration/System%20Tables.aspx
Bill Dates – The dates to use for the payments in the schedule. Values should be entered as a comma-delimited list of fixed dates, dates relative to the start or end date of the billing schedule, or dates relative to a month in the billing schedule. Relative dates use the following formats:
· FM – The first day of the schedule start month. Placing a number after FM represents the number of months after the start month. For example if the start month is January, FM0 represents Jan 1 and FM3 represents April 1.
· EM – The last day of the schedule start month. Placing a number after EM represents that number of months after the start month. For example if the start month is January, EM0 represents Jan 31 and EM3 represents April 30.
· S – The schedule start date.
· E – The schedule end date.
The relative date options are modified with + or – a number of days. For example, if the start month is January, FM3 +14 represents April 15.
Thank you! I've got some investigating to do now. :)
I had a thought that also seemed plausible. Perhaps this is a rounding issue? For example, if the total pledge amount breaks down to a weird number (ex. $20.82134 per month) it will round down instead of up. Meaning the last month of the schedule has to pick up the slack.