A business running on multiple disconnected operational platforms

A business had grown to the point where its operations couldn't keep up with it. Scheduling, accounting, job tracking, document management, and payment processing all lived in separate tools. None of them talked to each other.

The result: staff spent most of their working day copying information from one system into another. A job completed had to be manually closed in the scheduling tool, entered into the accounting system, matched against the payment record, and filed in the document store. Every step was a person doing work that a connected system would do automatically.

The business wasn't inefficient because of its people. It was inefficient because its systems weren't built to work together.

The platforms were connected through a central automation layer built on n8n, software that watches for events across connected systems and triggers the right action in response, without anyone having to do it manually.

When a job is completed, the relevant record updates automatically in scheduling. The invoice generates in Xero (the accounting platform). The payment gets matched when it clears through FNB. The document goes to the right folder in Microsoft 365. Nothing waits for a person to move it.

The system also connects to the custom operations application the business uses internally, so all of this runs through their existing workflows rather than replacing them.

The largest part of the work sits around the ledger. Every supplier bill, credit note and purchase order now passes through an approval workflow in ApprovalMax before it settles in Xero, instead of being captured and paid on trust.

Approvals route on three things at once: which division the spend belongs to, how much it is for, and who raised it. A reviewer checks the coding, the divisional manager approves the spend, an operational approver follows, and anything over that division's threshold goes to the managing director. Approvers see budget against actual for the division while they are deciding, so the question is not only whether the invoice is correct but whether the division can carry it.

Bills are matched against their purchase order automatically and the variance is put in front of the approver rather than left to be noticed, with a separate check raising an alert when a bill falls outside tolerance against its order.

Segregation of duties is built into the structure rather than asked for in a policy. Whoever submits a bill cannot approve it, and the routing holds even for the person who raises most of them. At the bank, the people who load a payment cannot be the person who releases it.

A control is only worth what the evidence says, so the system audits itself. A weekly job compares what was authorised in Xero against what actually came through the approval workflow, and reports anything that reached the ledger another way. Amounts, accounts and tracking changed after approval are flagged to the administrators.

The last stretch connects approved bills to the bank. Suppliers are checked against a verified bank register and against account verification at FNB, so a supplier whose details have not been confirmed is held automatically rather than paid. Payment instructions are then prepared for FNB's Integration Channel one bill at a time. Releasing them stays a human action inside the bank, deliberately. The system prepares, verifies and confirms. It does not pay on its own, and it was built so that it cannot.

The coordination work is gone. Staff who spent most of their day moving information between systems now have that time back. The business runs the same volume of work with less operational overhead, and the data across every platform stays accurate without anyone maintaining it manually.

On the finance side the gain is a different one. Spend that reaches the ledger without passing the approval chain used to be invisible, and a bill edited after it was approved left no trace anyone would see. Both now surface on their own, in a report nobody has to remember to run.