06-06-2018 06:57 AM
We have recently moved our billing platform to the UCRM. We love it! However, when we put in a recurring payment credit card with a payment date, the payment comes out the day before (i.e. the day the invoice is generated). We are using Authorize.net as our credit card portal. We assumed it was the credit card folks. But, when we called them, they said we (our UCRM) is giving them the day prior as the payment date. Has anyone else had this problem? If so, is there a solution? Thank you.
06-07-2018 03:58 AM
glad you like UCRM
Note that it is up to you or the client to set the day of the recurring payment while creating the subscription. By default, it's set to "today", but you can modify it.
However, even when the payment is created before the invoice is issued, there should be no problem. When a payment is received by UCRM while there is no related invoice yet, the payment is converted into client's credit. Then, the invoice will use the credit resulting in a "paid invoice status". Just make sure you didn't turn off the option "Use credit automatically" in the client's service settings.
06-08-2018 08:49 AM
For example recent transactions were set up for the first of the month and authorize.net took the payment on the 30th so these group of clients credit card was charged twice in one month. Payments set up for today were taken yesterday.
06-11-2018 12:21 AM - edited 06-11-2018 04:27 AM
@Syndemus please, check the subscriptions:
- is there more than 1 subscription set for the client?
- what is the subscription day?
What is your timezone set in UCRM (System > Settings > Localization)?
06-13-2018 01:46 PM
This is happening to all of our clients. Most have only one subscription. We take payment on the day of installation, so we bill some, but not all customers each day. We are in Minnesota and time zone is set to (UTC-06:00) Central Time (US and Canada). We use: Billing cycle - Real days count. Billing period type - Forward. And, Billing period start day - today. It seems when we put in, for example, the 13th for the period start date, the cycle ends on the 12th of the following month. And from then on, Authorize.net wants payments on the 12th at 5pm. We have been adjusting by simply setting the start date to one day in the future, but there is no clear answer as to why this is occurring and if it is the UCRM that is even the issue.
2 weeks ago
Turns Out it was the Authorize.net side that had the time zone set improperly. It has been working for us since we figured that part out. However, this month it happened again. It took out payments for the 1st of August on the 31st of July. Is there another known issue, or is this an anomoly?
2 weeks ago
we have investigated this issue thoroughly and we introduced some improvements for this in v2.11.3. However, we found out that it may not work in all cases and all timezones due the way of payment processing by Authorize.Net. Unfortunately, they process the payments once per day at specific hour in MST which may cause the 1 day difference if you are in another time zone and there is no way to tell Authorize.Net to process the payments at another hour..
The only workaround possible at the moment is to set your subscriptions to 2nd day of the month if you want them to be on 1st or set the MST in your UCRM (but this may cause some inconvenience in other features, like scheduling - depends on what you use in UCRM)