Cash Is Leaking Between Your Systems — Here’s Where to Look

Most owners can tell you what last month's revenue was. Far fewer can tell you what it should have been. The difference rarely comes from one dramatic failure. It sits in small amounts spread across job cards, parts counters, warranty portals and payment links. Each is too minor to chase on the day, and together they are too large to ignore over a year.

That money doesn't leak inside your systems. It leaks between them. The DMS knows a job was opened. The ERP knows what was invoiced. The CRM knows what the customer was promised. The payment gateway knows what was actually paid. Each system is right about its own piece, but nobody owns the gaps. So a person, usually a tired one, carries information across by hand. This is a RevOps problem as much as a finance one, because revenue operations only works when the path from promise to cash is visible from end to end.

This article looks at four places where cash typically goes missing: unbilled work, missed parts charges, expired warranties and uncollected deposits. We show how each happens in a realistic multi-location operation, then explain how to close the gaps without replacing the software you already pay for.

The systems you run, and the gaps between them

If you run a dealer group, a distributor or any technical, service-led business, you probably have some version of these four layers:

• DMS (dealer management system): the operational record of vehicles, job cards, workshop scheduling, parts issue, vehicle sales and stock. Aftersales lives here, and it is where most of the day-to-day work is captured.
• ERP or accounting platform: the financial record covering the ledger, receivables, purchasing, inventory valuation, VAT or sales tax and, where mandated, e-invoicing such as Peppol-based schemes. It is where money is formally recognised.
• CRM: the customer record covering leads, quotes, follow-ups, service reminders and, increasingly, the messaging conversations on apps like WhatsApp where customers actually make decisions.
• Payments: card terminals, payment links, bank transfers, cheques and online gateways. This is where money physically arrives.

Each of these works well on its own. The trouble starts at the handoffs: job card to invoice, parts issue to ledger, quote to deposit, warranty-eligible repair to claim. Where those handoffs depend on someone re-keying, remembering or forwarding a screenshot, errors become routine.

In a multi-location group the problem multiplies. A group with sites in three countries may find that each site has slightly different habits, different price lists, different tax rules and different ways of recording the same event. Head office sees the totals but not the seams. A central command center view, one place where leadership can see the status of each handoff across every site, is what makes those seams visible in the first place.

Unbilled work: the job that finished but never became an invoice

Consider a dealer group's service department in the busy weeks before a peak season. A customer brings in a vehicle for a routine service. During the inspection the technician finds worn brake pads, and the advisor messages the customer on WhatsApp, in the customer's preferred language, with a photo and a quote. The customer replies "okay, go ahead" within minutes.

The advisor tells the technician verbally and the work is done. But the approval lives in a personal chat thread, and the job card still shows only the original scope. When the invoice is generated from the job card, the brake work isn't on it. The customer pays and drives away happy, and the business has done the work for free.

A second version of the same leak is technical. The job closes in the DMS, but the invoice transfer to the ERP fails overnight because of a missing customer tax number or a mismatched account code. The record lands in an exception list that someone is supposed to review. In peak season, with the team stretched, nobody does, and a week later the job is "complete" in one system and nonexistent in the other.

This isn't limited to workshops. A real estate brokerage can complete a milestone that triggers a fee without anyone raising the invoice. An agency can deliver out-of-scope work on a retainer because the account manager agreed to it on a call and the finance system never heard about it.

The common thread is that work is recorded where it happens and billed where it is remembered, and the two aren't connected.

Missed parts charges: the part that left the shelf but not the invoice

Parts are the most tangible leak because they physically leave the building. In a typical workshop, parts get issued against a job card at the counter. In practice, technicians also take items in the moment: a clip, a sensor, a bottle of fluid, a set of gaskets. Some get scanned, some get written on a slip, and some are meant to be added later.

Three patterns are common:

• Issued but not billed. The part leaves stock against the job but isn't carried onto the final invoice, often because the job was edited late or the invoice was produced from an earlier version.
• Inter-branch transfers. A branch borrows a part from another to avoid delaying a customer. The transfer is agreed by phone, and the stock moves, but the cost and the customer charge never reconcile.
• Stale pricing. A supplier or distributor price change lands in the ERP, but the DMS price list is updated days later, or only at some locations. Parts are sold at yesterday's margin.

Where regional e-invoicing mandates apply, such as Peppol-based schemes, there is a further reason to catch errors early. Once an invoice has been issued and cleared, corrections generally go through credit and debit notes rather than simple edits. A missed charge found after the fact is no longer a quick fix. It becomes a customer conversation and an accounting adjustment, so most teams quietly let small amounts go. That is how a hundred small amounts turn into a real number.

Expired warranties: money you were owed and cover you could have sold

Warranty leakage runs in two directions.

Claims you never filed. Manufacturers and suppliers set rules for warranty recovery, including documentation requirements and submission windows. A claim needs the VIN, mileage, labour operations, parts used, technician notes and often photographs. When a warranty-eligible repair is done, that information is scattered across the DMS, the technician's notes and a messaging thread. The claim sits in "to do" while the team handles the next day's cars. By the time someone assembles it, the window may have closed, and the business has absorbed a cost it was entitled to recover. Distributors face the same problem with supplier warranties on parts that fail early.

Cover you never renewed. Dealers sell extended warranties and service contracts, but the expiry date usually sits in the DMS or a spreadsheet while the CRM, where follow-ups are actually triggered, knows nothing about it. No reminder goes out. The customer's cover lapses, and they discover it only when a repair bill arrives. That bill is a trust problem as well as a missed renewal. Reputation travels quickly through word of mouth, reviews and group chats, and an avoidable surprise can cost more than the contract's value.

Both leaks come from the same cause. The event that matters, whether a repair or an expiry date, is recorded in one system, and the team that should act on it works in another.

Uncollected deposits: money promised but not tracked

Deposits are where sales, finance and customer communication collide. Think of vehicle booking deposits, advance payments on special-order parts, reservation fees on a property unit, or advance payments on an agency project.

Here is a typical sequence. A customer agrees to reserve a vehicle and sends a bank transfer screenshot on WhatsApp. The salesperson tells the finance team. Finance checks the bank statement, which may take a day or two across a weekend, then matches the payment manually. In the meantime the vehicle has been marked as allocated in the DMS, though the CRM still shows the deal in "negotiation". If the payment was made through a link, it may have reached the gateway but never been tied back to the right order.

This sequence can fail in several ways:

• The deposit is never requested because the CRM stage advanced without a payment step.
• The deposit arrives but isn't linked to the deal, so stock is held without confirmed money, or released while the customer believes it is reserved.
• The deposit is received but not applied to the final invoice, so the customer is asked to pay the full amount again, or a refund is owed and nobody notices.

During peak seasons, with stretched teams and customer activity outside normal office hours, these delays grow because handoffs depend on people being at their desks at the same time. A customer who has paid and gets a chaser message remembers it for a long time.

How The Ninjaz Group approaches it

None of these leaks is solved by buying another system. The DMS, ERP, CRM and payment tools you have are usually capable. What is missing is the operating layer that makes them behave as one. That is what The Ninjaz Group builds and runs.

We work in three phases, and you can stop after any of them.

Blueprint. We map the operation end to end, from the job card to the invoice, the part to the ledger, the quote to the deposit. The aim is to find every point where work is done twice, data goes stale or money leaks. You keep the map whether or not you continue with us, and many teams find it valuable on its own because it shows what is actually happening rather than what the process document says.

Build & Link. We build what is missing and wire your existing systems into one backbone. This is the Managed Link layer: the operating connection between DMS, CRM, finance, service, website and messaging, built, owned and maintained by us. There is no rip-and-replace, and software you have already paid for stays. In practice, depending on what the Blueprint finds, this could mean:

• A check at job close that every approved line, labour and part, reaches the invoice, with messaging approvals attached to the job card rather than left in a chat.
• Invoice transfers between DMS and ERP that surface failures immediately instead of leaving them in an unreviewed queue.
• Price and parts data kept consistent across locations.
• Warranty-eligible work flagged at job close, with claim documents assembled while the details are fresh, and expiry dates passed to the CRM so renewals are prompted.
• Payment confirmations updating the CRM and the DMS automatically, so a deposit is either confirmed or visibly outstanding.
• A command center view for leadership that shows unbilled jobs, failed transfers, outstanding deposits and unfiled claims across every site, so RevOps and finance work from the same picture.

Operate. After go-live, we stay on with support, monitoring and continuous improvement. This is the Managed Business Operations layer, effectively your operations and IT team without the headcount. Integrations need looking after: systems get updated, tax and e-invoicing requirements change, and locations add new habits. Someone has to watch for the failed sync before it becomes a month-end surprise.

Delivery is split deliberately. Strategy and account leadership stay close to your business, while engineering, AI development and support run from our dedicated delivery operation in India, working across your business hours. If you only need the change itself, our Managed Transformation Services layer covers strategy, design and development, and you can take that work to your own team to run.

If you suspect cash is slipping through the gaps in your own operation, the Blueprint is a practical place to start. Book a consultation and we will walk through where to look first.