MK
Martinus K

1 reviews | Active since Jun 2015

14 Jan 2018, 08:55

Cannot create Ugu account number as an ABSA beneficiary

I received an e-mail from Ugu district municipality on 5 December 2017 advising me “I have opened your water account no. ********** 0, you need to make a payment of R550.00 the deposit. Here are the bank details of Ugu district municipality: ABSA bank ********** 647 branch code 632005. Please forward proof of payment.” On the same day I also received a SMS to that effect.

The next day I wanted to create UGU as a beneficiary via ABSA internet banking but was advised that the account number was not valid. Ugu District Municipality is an ABSA listed beneficiary and Ugu has two accounts with them with different Institution Codes ( ********** and ********** ) – I tried both. I also tried to make a physical deposit at the ABSA but encountered the same problem with the account number.

On the morning of 8 December 2017 I went to the Ugu office and advised them that there was a problem with the account number they provided. However on their system it showed that the account number was correct, I was advised to pay the deposit and then the number would be valid for beneficiary purposes. I paid the required deposit at the office and was advised that the problem should be addressed the same afternoon. It was not.

Since then I was advised, physically and on the phone, that they are working on the problem and that my account number problem would be addressed. I’ve also attempted a few times to create Ugu as a beneficiary with the same results – the account number is not valid.

On 5 January 2018 I attempted again but still with the same results. I’ve sent an e-mail to Ugu district municipality on 5 January 2018 explaining that I still cannot created the account number as a beneficiary. I did not receive a reply and on 8 January 2018 I sent another e-mail referring to my query. Till today (14 January) no reply.

0
Replies (1)
MK
Martinus K's update24 Jan 2018, 15:15
Reviewer Update
I received a reply from Ugu today (24 January 2018) via e-mail with a solution. I'm glad to report that it worked and my problem is solved.