Manufacturing
Your input costs rose. Did the price on the invoice?
Manufacturing sells on supply agreements that assume prices move: an annual review, an index, a surcharge when raw material or energy costs rise. All of it is negotiated once, then depends on somebody applying it to the billing schedule, per customer, every time. Against a high-volume trade ledger, the ones that never got applied are invisible.
Price reviews that never reached the invoice
What LeakIQ detects
- Customers invoiced an unchanged amount through one or more anniversaries
- The annualised value of each static account
- How many anniversaries have passed without a change
- The invoice history behind the flag
The problem
A supply agreement anticipates change, whether an annual review, an index-linked increase or a surcharge mechanism. Applying it means someone raising it with the customer, on the date, per account. Raw material, energy and labour costs move regardless, so a price that never moved does not read as a loss, it reads as a normal invoice while your margin quietly erodes.
How LeakIQ surfaces it
LeakIQ groups each customer's invoice history and flags the accounts whose value has never changed, with the annualised figure and the anniversary dates. It cannot see your supply agreements, so it hands your team the review list rather than claiming an under-bill.
Trade accounts ageing across a high-volume ledger
What LeakIQ detects
- Invoices past their due date and still unpaid
- How many days past terms each balance is
- Exposure per customer rather than per invoice
- Balances settled elsewhere, resolved automatically
The problem
Manufacturing runs on trade credit and a large volume of invoices, so there is always outstanding debt and most of it is normal. What is hard to see is which accounts have moved from slow to stuck, because the ledger shows a balance but not a trajectory, and nobody in particular owns the chase.
How LeakIQ surfaces it
Your aged debt surfaces at customer level, each overdue balance with its age and value and ranked by exposure, so the team chases the largest real gaps by account first, each with an owner and the source record attached.
The same order, billed twice
What LeakIQ detects
- The same customer charged the same amount twice in a short window
- The gap between the two charges
- The excess beyond a single charge
- Both underlying records for confirmation
The problem
Orders get amended, split across deliveries and re-raised, and at volume the same order can be invoiced twice without anything looking wrong. Customers with procurement teams reconcile their own spend and find these, and a duplicate found by the customer costs goodwill on top of the credit.
How LeakIQ surfaces it
Identical charges to the same customer inside a short window, where both settled, are raised for confirmation rather than asserted as duplicates, so your team can verify before crediting.
The same delivery, invoiced twice
What LeakIQ detects
- The same customer invoiced the same amount twice inside a short window
- The gap between the two invoices
- The amount over-billed if both are paid on terms
- Both invoices attached to confirm against
The problem
On trade credit most revenue moves as invoices, not card charges, and the same order can reach the ledger twice: a delivery is invoiced, the order is amended and re-raised, or a proof of delivery triggers a second bill. The amount is not taken twice, it is billed twice, and it sits on the account inflating what the customer is chased for. Procurement teams reconcile line by line, so a double invoice found by the customer costs goodwill on top of the credit.
How LeakIQ surfaces it
LeakIQ flags the same amount invoiced twice to one customer inside a short window, raised as possible rather than asserted because a legitimate repeat order looks identical. Your team confirms against both records and credits the duplicate before it reaches a payment run.
Credit notes left sitting on the account
What LeakIQ detects
- Customers holding a credit note while they still have open invoices
- The value of the credit left unapplied
- The open balances that credit could have cleared
- The records behind both sides
The problem
Returns, rejected batches, short deliveries and post-invoice price adjustments all raise credit notes, and on a busy trade ledger they are easy to issue and then lose track of. A credit sits unapplied on one account while the same customer carries open invoices it could have settled, so working capital is tied up on both sides at once. It tends to stay there until the customer notices and asks for it back.
How LeakIQ surfaces it
LeakIQ flags customers who hold a credit note while open invoices sit against the same account, with both sides shown together. Your team decides whether to apply it against the open balances or refund it, rather than letting it sit until the customer raises it.
Want to see an example of the free report you'd receive?
The headline figures, then every finding with its amount, the customers affected and the source records behind it.
More sectors
Where revenue leaks in other industries.
Revenue recovery for saas and subscriptions
Failed renewals, silent churn, disputes and price drift.
Read more→Revenue recovery for ecommerce and dtc
Failed payments, duplicate charges, chargebacks and ageing balances.
Read more→Revenue recovery for plant and tool hire
Rate cards that stopped moving, failed collections, ageing trade accounts.
Read more→Free revenue leakage report
See what it finds in your own numbers.
Connect your billing and accounting systems and LeakIQ will show you the prices that never moved, the trade accounts quietly ageing, any duplicate billing and credit notes left unapplied, with the source record attached to every one.
Read-only. LeakIQ never writes back to your systems and never moves money.