AMAC warns taxpayers against fake revenue collectors in Abuja
The Abuja Municipal Area Council (AMAC) has cautioned Abuja residents to pay their taxes and levies to designated AMAC accounts to avoid falling victim to fake revenue collectors.
The Chairman of the Council, Mr Christopher Maikalangu, gave the warning while addressing newsmen in Abuja on Tuesday
He frowned at a situation where tax payers in Abuja preferred to pay cash to fake agents and get reductions instead of paying to the council’s bank account for accountability.
Maikalangu emphasised that only taxpayers who presented bank tellers of their payment into the council’s account would be accepted.
“The general public is hereby advised not to pay cash to any technical partner or their representatives to avoid falling victim to fake revenue collectors operating illegally within the Council.
“Except for daily ticketing and mobile advertising, remember that when you pay cash, it is assumed that you have not paid at all and you will pay twice,” he said.
According to him, the collection of revenue is not as easy as many people imagined, and that informed the setting up of a taskforce when he assumed office.
“In fact, we recorded good results in 2023; that’s why I am relying on the taskforce to help in arresting revenue leakages abetted by fake revenue agents,” he said.
He urged residents to call their mobile telephone numbers, 07055550346 and 07055550246, to confirm the authenticity and proper designated bank details before making any payment.
“After payment, your evidence of payment will be verified by the AMAC Taskforce,” he added.
Maikalangu acknowledged that one of the major challenges he inherited upon assumption of office was fake revenue consultants.
He commended the AMAC Revenue Task Force for its efforts in apprehending and prosecuting the perpetrators.
Maikalangu warned that any partner caught producing its own receipts and documents risks licence revocation and criminal prosecution.
He added that measures were being implemented to collect revenues without resorting to force and to eliminate revenue leakages.
On his part, the Chairman of the AMAC Revenue and Security Taskforce, Mr. Yunusa Yusuf, disclosed that the taskforce had arrested and prosecuted 68 illegal revenue agents.
According to him, steps were also underway to digitise revenue payments in the Federal Capital Territory (FCT).
“The chairman has engaged ICT consultants to digitise our activities.
“Very soon, you will sit down and get a demand notice, and we will be monitoring those who have paid and those who have not paid,” he said.(NAN)
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager