Shireburn Indigo staff cost reporting, Malta

The short answerCan we see Shireburn Indigo payroll costs beside revenue and operations?

Yes. After each pay run, payroll figures by cost centre, department or location reach a warehouse in your own cloud account, by a route the audit confirms with your Indigo administrator, next to revenue, sales and jobs from your other systems. Leadership then sees people costs against what each site or team brings in. Reports show totals wherever totals answer the question, and any pay-level detail stays under access by role. We do not run payroll, and we are not part of Shireburn.

01The problem

Why people costs sit apart from the rest of the numbers

Indigo is built for the people who run payroll, leave and attendance, and it reports well for them. Its payroll report comes as totals, gross totals or in full detail, and the Payroll Totals report can be grouped by company, department, location, cost centre and more. Shireburn's People Insights adds dashboards built on Microsoft Power BI for the people data itself.

Leadership's questions reach further. What does each outlet spend in wages for the sales it brings in? Did last month's overtime come with more orders, covers or jobs? Which contracts carry more staff cost than their margin allows? Each one needs Indigo and something Indigo does not hold: the tills, the accounts, the booking system or the job records.

So the answer is usually a payroll export, a sales export and a spreadsheet joining them by department name. Because that export carries everyone's pay, it is often kept by one person, and the question waits for them.

02What we do

What Indigo already holds that the warehouse can use

From Shireburn's own help centre. The audit confirms which of these your Indigo setup uses.

Cost centres, departments and locations

Set up in Indigo's HR employee setup, with departments divided into sections and sections into units. They are the bridge between payroll and the rest of the business.

Reallocation profiles

Indigo can split one employee's cost across cost centres, by a percentage held on the employee or by the cost centre on each basic hour, pay item or overtime entry.

Attendance and rosters

Where Indigo Attendance is in use, rosters and clockings are kept there, attendance allocations are sent to the payroll period, and a costs report shows rostered costs by cost centre.

Roles and record filters

Indigo decides who sees what through permission sets, user roles and record filters. Its Payroll User role does not see salaries unless that permission is granted.

How payroll figures reach the warehouse, and who sees them

The first decision is what to keep. Most leadership questions need cost, hours and headcount by cost centre, department or location, not anyone's salary. Wherever totals answer the question, the warehouse keeps totals, once each pay run is complete; the audit confirms whether your route delivers totals or detail that has to be summed first.

The route is confirmed in the audit with whoever administers Indigo. Shireburn publishes a RESTful Indigo API through its developer portal for employee and company data, including employee profiles, payroll run information and leave; access is set up with a developer account, a product subscription and a dedicated Indigo user that creates the key. Indigo's own detailed payroll report can also be produced as Excel data. Which of the two carries the figures your reports need is checked against your setup before anything is quoted.

After each run, AI checks the figures before they reach a report: an employee with no cost centre, a leaver still in a run, a location that matches no site code, a run whose totals move further from the last one than the threshold finance set. Each is listed for payroll to correct in Indigo, and the totals then appear beside revenue in the 110 Command Centre.

Where individual rows are genuinely needed, for example to cost a contract from the hours booked to it, they sit under access rules agreed with you. Who can see pay-level rows in the warehouse, our own team included, is agreed before the first load. Then the definitions: staff cost might mean gross pay, or gross pay plus employer costs and benefits; headcount might count people or full-time equivalents. Finance chooses, the choice is written down, and every report uses it.

Questions payroll data cannot answer alone

Each one sets people costs beside something recorded in another system.

Wage cost against sales, by site

Payroll totals for each outlet or branch, next to that site's sales from the tills or the accounts.

Overtime against activity

Overtime hours and cost for each pay period, set beside orders shipped, covers served or jobs completed in the same weeks.

Staff cost inside contract margin

Hours booked to each job, costed from payroll, joined to what that contract invoiced.

Headcount and cost against budget

Actual headcount and staff cost by month, against the budget finance keeps.

Seasonal staffing against demand

Last season's hires and hours laid beside last season's bookings or sales, month by month, before this season is planned.

03In practice

A facilities services company pricing contracts without knowing their staff cost

Illustrative example. A fictional business, not a client.

A Maltese facilities services company employs cleaning and maintenance staff across many customer sites. Shireburn Indigo runs its payroll and attendance, with staff clocking in on the mobile app, and each site has its own cost centre. Contracts are invoiced from the accounting system, and the contracted hours per site sit in a contracts list.

Before

Wage cost per contract is worked out once a quarter, from a payroll export and the invoice list joined in a spreadsheet.
Overtime spikes are noticed in the pay run, weeks after the work that caused them.
Contracts are renewed at the same rate without anyone seeing what they cost to staff.
The payroll export stays on one laptop, because it carries everyone's pay.

After

Payroll totals by cost centre load after each pay run into a warehouse in the company's own cloud account, beside invoices by contract.
Each contract shows staff cost against what it invoiced, pay run by pay run, using the cost centre each site already has in Indigo.
Overtime by site sits beside the contracted hours, so the cause is visible before the next run closes.
No payroll file circulates by email. Only totals by cost centre are loaded, so individual pay stays in Indigo.

Payroll ran as before, in Indigo, by the same team with the same support from Shireburn. The directors now price renewals knowing what each contract costs to staff.

04How it works

Matching rules to agree before payroll meets the ledger

Cost centre to the accounts

Indigo's cost centres mapped to the cost centres or departments in the accounting system, so staff cost lands on the same lines as revenue.

Location to the site

Each Indigo location matched to the outlet, branch or site code the tills or the booking system use.

Pay run to month

Which month each pay run counts in, and how a run that spans two months is treated.

Reallocated cost

Where Indigo already splits a person's cost across cost centres, the warehouse follows that split rather than inventing another.

People who map nowhere

A new starter without a cost centre, or a leaver still in a run, is listed for payroll to correct rather than hidden in a total.

What we do not do

We do not sell, license, implement or support Shireburn Indigo, and we are not part of Shireburn.
We do not run payroll, calculate pay or change anything in Indigo.
We give no HR, pay or employment advice.
Payroll figures are copied into a warehouse in your own cloud account.

How it works

A strategy callThirty minutes with Glen, free, with no pitch deck. Bring the systems you run and the question none of them answers on its own. You leave knowing whether joining them is worth doing, and where to start.
The data auditAbout three hours with your team, mapping where each figure comes from, which system holds it and which steps are done by hand. The audit confirms how each system can be read, and it ends with a quote.
The buildThree to four weeks from an accepted quote to a live dashboard. Implementation is the first month. Your team agrees the definitions with us; we do the building.
The fractional teamAn ongoing senior team keeps the loads running, follows changes made to your systems and connects the next source when the business needs it.

Glen SultanaFounder · 110 Analytics

Who you will work with

Glen Sultana founded 110 Analytics after a career built where the numbers move daily. Our people have run analytics for tier-one companies, S&P 500 firms and high-growth technology businesses. Glen is the person on the first call, and he runs every data audit himself.

Built in your environment, under your account
Every connection approved by you first
Based in Malta

Open the demo ecosystem, built on invented data

05Questions and terms

Straight answers

Does Shireburn Indigo stay as it is?

Yes. Indigo keeps running your payroll, leave and attendance, and your payroll team works in it as before. We read agreed figures from it into your warehouse, so people costs can be reported beside the rest of the business.

Will this affect our Shireburn Indigo licence or support?

No. Your subscription and support stay with Shireburn. If the route agreed in the audit needs an API subscription or a dedicated Indigo user, your Indigo administrator sets it up, and you hear about it before any quote.

How do you connect to Shireburn Indigo?

By the route the audit confirms with your Indigo administrator: Shireburn's Indigo API, through its developer portal, or the payroll reports Indigo produces as Excel data after each run. Only the agreed fields are kept, as totals wherever totals will do.

Do you process payroll?

No. Pay is calculated and approved in Indigo by your team, exactly as today. We report on payroll figures once each run is complete and never touch the run itself.

Who will be able to see salaries?

Only the roles you approve before the first load. That applies to our own team too. Most reports are built on totals by site, department or contract, and any row-level data sits under access rules set by role.

How is employee personal data handled?

Payroll records identify people, so what is read, why, and who sees it is agreed with you and whoever leads data protection in your company before anything is loaded. Wherever totals answer the question, the warehouse keeps totals instead of individual rows, which keeps the personal data involved to a minimum.

Indigo has People Insights dashboards. Why add a warehouse?

People Insights shows Indigo's own people data in Power BI dashboards inside Indigo, and it stays useful for that. The warehouse is for the questions that need Indigo beside sales, invoices or jobs held in other systems.

I am an employee looking for my payslip. Can you help?

No. 110 Analytics is not part of Shireburn and cannot see or reset anyone's Indigo sign-in. Payslips issued through Indigo are in your employer's Indigo Employee Portal and the Indigo mobile app, and your HR or payroll team can help you sign in.

Payroll terms, as reporting uses them

Cost centre: A label that says where a cost belongs, such as a site or a department. Kept in Indigo and in the accounts, it is the usual bridge between the two.
Reallocation: Indigo's split of one employee's cost across several cost centres, by percentage or by the cost centre on each entry.
Full-time equivalent: Headcount adjusted for hours worked, so two people on half time count as one.
Pay run: One payroll calculated and completed in Indigo for a period. Its figures reach the warehouse once it is complete.

Where the product facts come from

Every product fact on this page comes from the vendor's own documentation, read on 22 October 2026. Vendors change their products, so the audit checks the version you run.

Payroll lives in Shireburn Indigo. What does each site cost to staff?