Field Service ERP for a Fire-Safety Inspection Contractor: Paper Books to a 42,000-File Digital Archive

Where the paper archive lived

The client ran a fire-protection inspection and servicing business out of a 3-4 person office. Filing cabinets held years of finished work orders, invoices and quotes. One client’s full history sat scattered across a paper folder, a scanned photo on a shared drive, an Excel row and a Word document, and pulling all of it together took an afternoon of digging rather than a click.

There wasn’t a shared filing standard, either. One document type lived under the customer name, another under the job number, a third under whoever saved it last and however they happened to spell the street that day. The office knew where things were because the same two or three people had always known where to look. Anyone new to the job started from zero.

The receivables spreadsheet nobody could fully trust

Accounts receivable lived in two Excel workbooks kept up by hand. An independent audit re-derived every figure from the raw files, five separate times, before anyone trusted the totals. What it found:

• Outstanding invoices came to north of $1.7 million across roughly 490 rows, once two confirmed duplicate rows were pulled out.
• The invoice number was no kind of key. The same number turned up on two separate invoices inside one year’s sheet, and two historical sheets shared over a hundred numbers with almost none of them pointing at the same document. Working out which invoice an old row meant took the number, the site and the amount together.
• Tens of thousands of dollars of the book sat hidden in the spreadsheet. Those rows counted toward every total while showing up nowhere on screen, because the sheet’s autofilter range had gone stale against its own data.
• Two dozen invoices showed up as outstanding and paid at the same time, some of them with records that fought each other. One carried a partial-payment note for one amount while the payments sheet recorded two separate cheques against it totalling something larger. Staff had flagged that one “get back to this,” and nobody ever did.
• Roughly two-thirds of the rows had no reliable bill-to entity on them, only a job-site address, and the site address isn’t always who pays the bill.
• A meaningful share of the outstanding book was more than 90 days overdue, and one client relationship accounted for a lopsided slice of the whole total.

This is what “just use a spreadsheet” turns into after enough years. Nobody sat down to build an unreliable ledger. It piled up a row at a time until the row count and the recycled invoice numbers made the thing impossible to read at a glance.

One platform to hold the whole history

We built the client a field-service operations system on an open-source ERP platform. Its job is to hold every document the business has ever produced, in one place, filed the way the office already talks about its own paperwork. Open a client and you can read their history without a second search.

The three-role permission model

Three roles, with the boundaries enforced down at the permission layer where nobody can click around them:

• Admin sees the lot, money included.
• Coordinator/office runs intake, scheduling and quotes, and cannot reach an invoice or a payment. The block sits at the API layer, so no menu setting can undo it.
• Technician works on a phone, sees his own assigned jobs and nothing else, and loses the job’s data the moment it’s invoiced.

Partway through the project, the business owner named a specific fear. A staff member could walk out with the company’s data, the way anyone could once copy an entire shared folder off the old file storage in a single click. He wanted a system where nobody could download the app or pull information out of it in bulk.

We didn’t promise him an unbreakable system, because that promise would have been a lie. The new system already makes you drill into one document at a time, a structural difference from the old shared-drive setup. On top of that we offered something concrete: cap how many documents any one staff member can open in an hour, and fire an automatic alert when someone goes past the cap. No system, custom or off the shelf, stops a person photographing their own screen, and we said so out loud rather than glossing over it.

A follow-up audit checked the “by design” permission claim against the actual configuration instead of assuming it held. Two real gaps turned up between what had been claimed and what the system enforced. Both got fixed. We’d rather tell you that than say the system is secure and leave it there.

The 42,000-file archive and the legacy AR import

Two migrations ran next to the new system, because “start fresh and forget the old records” is not an answer you give a business with years of client history behind it.

The per-client document archive brought roughly 42,000 legacy files over from the client’s old file storage: invoices, quotes, reports, certificates, correspondence. They’re filed by client, by document type and by year, under the words the office already uses for them.

The legacy accounts-receivable import moved the historical invoices and payments out of the two Excel workbooks into the new system as real ledger documents that affect the books. Every defect the audit turned up, the duplicate rows, the recycled invoice numbers, the hidden rows, the invoices marked paid and outstanding at once, went to the business owner for a decision. Nothing was quietly guessed at. That rule, ambiguity becomes a question for a human, held for the whole import.

Nightly on-host backups run alongside a separate off-host disaster-recovery copy. We ran a restore from both before go-live, so the client knows the archive comes back if something goes wrong.

Why this wasn’t an off-the-shelf archive

A 3-4 person fire-inspection office is exactly the size of shop generic field-service software is built for, and plenty of shops that size should buy it. This one went custom for reasons you can point at. Their own filing language became the system’s data model, so the business didn’t have to bend itself into somebody else’s folder structure. Most off-the-shelf tools don’t offer a coordinator structurally blocked from ever seeing money, a 42,000-file legacy archive organized in the client’s own filing terms, or a receivables import that treats years of messy history as something to reconcile rather than discard.

None of that makes custom the right answer for every shop this size. It worked here because the business carried enough operational history, and enough specific quirks in how it filed things, that squeezing it into someone else’s software would have cost the owner detail he cared about.