Woke up this morning to find 3 out of 4 standing orders that were due to be paid had been declined (plenty of funds available).
Spoke to support who quickly worked out that they were due to go to RBS accounts which was undergoing scheduled maintenance until 1445 today .
Apparently with a legacy bank it would just keep retrying until it went through, but as Monzo give instant notifications this behaviour would result in lots of declined notifications which isn’t desirable.
I’m told they are working to suppress these notifications which will hopefully be implemented soon.
In the mean time, the only option is to process a manual faster payment which I have now done… A decline reason and “retry” button would have really helped here as it would save having to re-type reference numbers etc.
Thought I would share in case anyone else is having the same issue.
Definitely a weakness in the product which really needs fixed. A concern of mine changing Direct Debits over… hopefully it doesn’t come back to bite me. I’ll be watching every month the day they’re taken!
Ah interesting - I had one declined for a credit card payment to TSB. I figured I’d put in the account number wrong or something (I’d changed the amount so cancelled my old payment and set up a new one). I haven’t had a chance to check it but as I’d copied and pasted from a statement I’m hoping it was this same issue.
I don’t think it is a weakness. More that other banks are massively behind and need to catch up in terms of real time banking. Monzo do need to do something. However, I don’t think there can be a pretty solution.
Ah the old “expecting failure” vs “instant notifications” problem: legacy banks expect their systems and other banks to be unavailable and so automatically retry, however, new banks want to keep their customers informed to the second and so leave the retry choice up to the customer…
I wonder if the scheduled maintenance windows are “known and circulated in advance” so Monzo could just “soft fail” and go “Receiving bank undergoing maintenance - transaction will be reattempted in 6 hours time”. Unscheduled maintenance/remote failure - perhaps things like SOs have a “hidden soft failure” option and they are auto-retried automatically with just a “Pending” message.
Having given this some thought (it’s the second time this has happened to me) I’d really like Monzo to do something about this or at least give an update on what they are doing. It’s not a pleasant feeling waking up to a bunch of decline messages and it’s also not pleasant to have to manually re-enter all of the details to make the payment(s).
Longer term, suppressing the decline messages may be the answer, but in the short term can we have a “retry” option or at least allow support to retry them if requested by a customer (I did ask yesterday but was told computer says no). This is exacerbated by the longer than usual response times support are currently encountering.
I’d also like to know if Direct Debits are also affected by this issue?
Does anyone know what Starling/Revolut etc. do in this situation? Is it handled any better?
I have 22 scheduled payments from my account so this is important to me.
At the moment, Direct Debits are affected by this issue on Monzo. It is recommended that you don’t have them come out the same day that your salary (or other credit to cover them) comes in (don’t know if you remember, but you posted further up in this thread!):
And the issue was more recently confirmed, further down the thread:
Agree that this isn’t a good situation, hopefully sort it out before adding too many more current accounts. It’s the kind of little thing that could have big consequences for some people, especially with the charges and fees some payees have for missed direct debits.
And I agree that a simple ‘retry’ option for the failed standing orders would be great.
That isn’t necessarily the same issue though. That’s if you don’t have enough in your account to cover the Direct Debit. What if you do, but the receiving bank’s system is down? Will that fail, too? If so, it is quite concerning…
I am very disappointed by this issue. To my knowledge, the account is no longer in beta. Why were these issues not identified and resolved through the preview accounts? It makes me feel very uneasy about what else in the account isn’t really functioning correctly.
While I understand wanting to get everything rolled out as soon as possible, there’s only one chance to make a first impression. Testing things on users is all very well while you’re in beta, but many users have no interest in being a tester and want to use systems that have been well tested and “just work”.
Nothing is being “tested” here, this is just the way the account works at the moment. This did come up during the Beta, it’s somewhere on this forum along with the stated desire to improve this handling mechanism in due course…
Not being in Test is not the same as being finished - that won’t happen for years (hopefully) as I’m expecting new functionality to be added over numerous development iterations in the future.
I do agree that this one is less than ideal. I hope I never fall foul of it because it is a weakness at the moment. Hopefully it will get a makeover sooner rather than later.
I might be barking up the wrong transaction type here - but aren’t we merging multiple things?
— standing orders : which the sender sets up and controls
— direct debits : which the recipient sets up and controls amount and when
— available funds
— system down time / failure
From what I’ve read the problem initially was recipient system down time, and a Standing Order? If another system is down, agreed Monzo should reattempt - but for how long?
But we’ve also talked about all of the other items above.
Direct Debits I think it’s for recipient to reattempt - but if no funds that’s just down to account holder right? You then get into credit rating issues. If Monzo messes these up it’s a problem for sure. But not sure I’ve read anything about this - having a bunch of DDs go out same day as pay day isn’t a great idea using any bank.
Anywayyyyy, loving my current account and Monzo overall. That all said I’m only drip feeding SOs, DDs into my account and salary staying elsewhere for a little longer.
Oh, and this is my first community post so please at least try to be nice with your replies!
The impression I get with DDs is that the receiving bank requests but it’s up to the paying bank to make sure the money is transferred on the requested day.
If that’s true then it’s on ‘my’ bank to ensure the money gets through on the day in question. At that point, DDs are just the same as a Standing Order in the sense that it’s the responsibility of ‘my’ bank to ensure that ‘my’ outgoings are transferred correctly.
I’m clearly responsible to ensure funds are in the account…sadly
It’s the downtime that could be a grey area but, if other banks retry automatically, then custom and practice suggests that that’s the way it’s done even if I don’t know what rules govern the process.