1. Home
  2. UK Finance Discussions
  3. On-line banking
  4. Page 2

On-line banking

The detailed answer I have had is:

When you set up a payment, and then make the payment, the system keeps a record for next time. However if you don't make a payment for a considerable time ( they say it could be as short as a year ) the system deletes the record. (seems reasonable).

I find it convenient to instruct the system to pay several bills at the one sitting. As they have different due dates I tell the system to pay on future dates. This is a normal part of the system

I am told that the system does not recognise instructions to pay in the future as "use". So if you make only future payments the system thinks you are not using it and deletes the payees record. The odd thing is that I have been using the system for several years and have had nothing deleted before.

Reply to
bluenep27
Loading thread data ...

I'd say that a bug, caused by an inept specification :-)

Reply to
Tumbleweed

You are right and they seem to prefer that the customer has the inconvenience of re-entering the payee details rather than they remove the bug.

That's banks!!

Reply to
bluenep27

I'm sure they'll fix it in a couple of years!

Reply to
Tumbleweed

wrote

Does that mean that, in the intervening period between giving instruction to pay and the actual (future) payment date, the payee record may be deleted - and so the future payment request won't know where to go to? :-( Excellent system! (not)

Reply to
Tim

I suspect what it means is the instructions given are stored up and will be executed properly, and all that happens is that the drop-down box for creating new instructions starts to forget payee details which have not been used recently for creating further instructions.

I guess the need for this timing out stems from there not being any option in the UI whereby such details can be explicitly expunged.

It would be much better if there were, and if the timing-out function were removed altogether.

Reply to
Ronald Raygun

There didnt used to be, but there has been for some time.

I think its simpler than that, the code that looks to see if any payees have not been accessed for a period of time, doesnt also look at the future payee details, presumably because,as you say, they are stored with the future payment details, so it would be not straightforward to check them and see if they are the same as the list of payees. This also leads to numerous other complications I can think of, for example if you makea payment for a future date, then change the payee details, its likely that you'll still have the original payee details (possibly no longer valid) in the future instruction. OTOH if they changed it to correspond automagically, that might not be what you'd want to happen either.

Reply to
Tumbleweed

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.