nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

We want to hear from you: please tell us about your experience of the online community.

UC Statement was always ready on 6th, but it's not here this morning. Anyone else?

james19o6

Good morning guys

I am getting paid on the 12th every month and my statement was always ready on the 6th of the month despite stating it will be ready on the 8th of the month. However, i just checked my statement is not there this morning? Did you guys have the same problem?

Find more posts tagged with

Comments

janer1967

Hi there

Mine is same date but my statement is there

Try again as it may update once they refresh their system

james19o6

@janer1967

Okay thank you for your response. I logged in from 6am but still no changes. Do you reckon I shall contact my case manager?

janer1967

The system usually updates round about 9 I think when they start work

See what happens if mot there by tomorrow give them call

Has there been any changed to your claim

james19o6

Nothing changed atm.

calcotti

If it states it will normally be ready on 8th there doesn’t seem much point in chasing until the 8th.

james19o6

@janer1967

My case manager just replied with this: any idea what happend there or just a error

Hi,
I see that the system has asked me to pay you directly. I will be doing so today and your statement will show up soon on your claim. I'm actioning it right now.
Kind Regards

janer1967

I have heard of this happening before to others

For some reason they have to do a manual payment

At least it is getting sorted

cazza6565

No really an issue if it's meant to be the 8th.

james19o6

cazza6565 said:

No really an issue if it's meant to be the 8th.

Well it is an issue as it usually comes at the 6th for the last 2 years. Plus there was a error and issue for that reason my case manager rectified the problem. So it is an issue @cazza6565