Introduction About Site Map

RSS 2 Feed RSS 2 Feed

Main Page | Blog Index

Tuesday, December 6th, 2022, 5:43 pm

Pension Blunders at Sirius ‘Open Source’

Too busy to do pensions and send payslips

Summary: Today we turn our attention to pension blunders at Sirius ‘Open Source’; in recent years even something basic like pension contributions wasn’t smooth sailing

WE’VE just posted a meme that demonstrates the immunity (de facto impunity) for bosses who make serious mistakes that upset not only staff but also clients. There are many examples of this, but today we share one. We’ll also show some evidence tomorrow as it serves to show the depth of these scandals.

This text, which can be found below, is part of a report left when we resigned; we may come back to that later as it shows a pattern of cover-up and lame excuses after utter failure to do the job properly at the very top of the company.

Regarding greenwashing the cessation of physical payslips, and not to forget repeated failure to send electronic payslips, this subject may also be revisited later. We’ve been noticing similar experiences in other companies, not just banks and utility billing; the bogus excuse that sending E-mail (or using a Web site, “apps” etc.) is “green” overlooks the massive carbon footprint associated with manufacturing (power and waste) and operating (electricity) computers, even some of the more modern “phones” that need to be charged every day.

Here is the relevant part of the report:

Pension Not Now!

There’s no more in-house accounting, the person who set up the pension scheme also left, and all workers’ pensions got outsourced to some other company (so the pension scheme is now fragmented for long-serving staff).

Years ago several colleagues, including Roy and Rianne, were cautioned by the pension provider that the pension was not being paid; it wasn’t an isolated incident as this happened for several consecutive months and on numerous occasions over the years. The simplest and plausible explanation is that the company (Sirius) had financial difficulties, but the “official” explanation was that the portal had technical issues in it. There are several inconsistencies in the latter explanation, for reasons beyond the scope of this document. Later difficulties cemented the belief that under the surface there was a crisis of another nature. It may be possible that there were technical issues coming back every now and then (for almost a year). If so, staff should have been notified and fully informed, sparing the need to go through the hassle communicating with barely-accessible pension companies, sometimes behind the managers’ backs (this is bashful both for workers and for the pension providers). This seems like a managerial failure. Speaking of failure to pay, it’s crystal clear that the company (Sirius) failed to pay providers of services or clients’ providers of services. It’s like not paying the webhost for a very long time. These chronic issues of either neglect or miscommunication should be brought up; but in Sirius it’s seriously unwelcomed.

It may seem appropriate to note that one administrator has been on maternity leave and as a result staff has received no payslips for months already (it’s a strict legal requirement by the way). As a matter of fact, prior to that everyone received physical copies by post. Then members of staff were assured electronic versions would replace them. Then… they stopped coming. And then, only upon polite prodding they started coming again, sometimes in bursts several months apart (not every month). Nowadays staff may receive nothing at all as evidence of pay. There are many gaps in the sending of such payslips, even electronically. Who has been given the responsibility and where is the accountability? Staff should not have to repeatedly ask for payslips; it ought to happen automatically without the feeling that it requires perceived ‘nagging’. Roy and Rianne were chasing this many times as payslips had stopped coming. This even needed to be escalated upwards (to the CEO) before things got belatedly done, at least temporarily.

Inconsistent operations or ‘compliance in intervals’ had already become routine. Communication had been diluted into subtle hints and sporadic innuendo. Engagement with clients had descended to storytelling, with very rare admissions of guilt or apologies. Some clients demanded a refund (all their money back) for Sirius failing to fulfil its side (contractual obligations) of the deliverables or service levels.

Technical Notes About Comments

Comments may include corrections, additions, citations, expressions of consent or even disagreements. They should preferably remain on topic.

Moderation: All genuine comments will be added. If your comment does not appear immediately (a rarity), it awaits moderation as it contained a sensitive word or a URI.

Trackbacks: The URI to TrackBack this entry is:

Syndication: RSS feed for comments on this post RSS 2

    See also: What are feeds?, Local Feeds

Comments format: Line and paragraph breaks are automatic, E-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Back to top

Retrieval statistics: 21 queries taking a total of 0.149 seconds • Please report low bandwidth using the feedback form
Original styles created by Ian Main (all acknowledgements) • PHP scripts and styles later modified by Roy Schestowitz • Help yourself to a GPL'd copy
|— Proudly powered by W o r d P r e s s — based on a heavily-hacked version 1.2.1 (Mingus) installation —|