Ask a finance team which invoices cause the most trouble, and they will point at the ones stuck in a queue. But that is only part of the picture. The invoices costing you just as much are the ones that already cleared: paid a few days late, paid past the discount window, or in some cases paid twice. Nothing flags them, because on paper everything closed.
QAD holds a reliable record of what you owe and to whom. The problem is never the record. It is the manual work wrapped around it; the keying, the routing, the chasing, that lets money slip out before QAD ever sees a clean number.
The Discount You Paid Right Past
Many suppliers offer better terms for paying early. When accounts payable (AP) is manual and running behind, invoices get paid whenever they finally surface rather than when the terms are best, and every missed early-payment discount is margin you already earned and gave back.
This is the most invisible leak on the list, because a missed discount never shows up as a cost. It just fails to show up as a saving. Nothing in your aging report says this is the fourth month in a row we paid Supplier X on day 34 instead of day 10. You have to go looking for it, and most teams running manually do not have the hours to go looking.
The Approval that Quietly Ages
An invoice arrives, needs a sign-off, and lands with someone who is traveling, in a plant, or buried in their own work. It sits. Days pass. By the time it clears, the discount window has closed and the supplier has already called to ask where their payment is.
Manual routing is where cycle time disappears, and it is rarely anyone’s fault. Nobody decided to sit on that invoice. It just never surfaced above the rest of their inbox. Automated, rules-based routing sends each invoice to the right approver by amount, site, cost center, or entity the moment it is ready, with reminders and escalation when it stalls. The invoice you never had to chase is the cheapest one you will ever process.
The Receipt That Has Not Posted Yet
This one is specific to how manufacturers actually run, and it is one of the most common exceptions we see. The invoice arrives before the receipt is in QAD. The goods are on a boat, or they landed on the dock and receiving has not caught up. There is nothing to match against yet, so the invoice goes into a pile to be looked at later.
Later is where the cost lives. Someone has to remember to go back into QAD and check whether the receipt has posted, then check again, then check again. Across a few hundred invoices a month, that is hours a week spent looking for something that has not happened yet.
There is a better way to handle it. The invoice waits, and the software does the checking. It looks in QAD for the receipt, for as long as you tell it to. If the receipt lands and everything matches, the invoice posts on its own. If nothing shows up by the end of the week, it goes to a person, and by then there is a real reason to look.
The Mismatches That Grow
Manual entry is how the same invoice gets paid twice, matched to the wrong receiver, or keyed at the wrong amount. Duplicates are recoverable, but recovery is its own project: someone has to find it, prove it, and get the supplier to issue the credit, often months later.
The subtler cost is what mismatches do to your books. Every invoice that does not cleanly tie to its PO and receipt is another loose end, and anyone who has run a QAD shop for long knows how those pile up when they are left to drift. The longer a receipt and its invoice sit unmatched, the more room there is for the two to fall out of step, and the more that piles up into a reconciliation exercise at close.
The Process Only Two People Understand
Ask most AP teams to document how an invoice actually moves and you get a version that is roughly right, plus a set of judgment calls that live in one or two people’s heads. Which exceptions go to sourcing and which go to operations. How long to give each before chasing. Which suppliers never tie cleanly, and what to do about it.
That works until the person holding it leaves. It also makes audits harder than they need to be, because there is no consistent trail to point at. A standard workflow that applies across your domains, sites, and entities turns tribal knowledge into something the team can hand off, and gives you a documented history of who approved what and when.
What It Looked Like for One Manufacturer
One long-time QAD user had four people in AP on overtime and burning out, with roughly 1,300 invoices sitting unchecked in the inbox. That is a real liability. Depending on the supplier, unchecked invoices become late payments, and late payments become production problems.
After automating, one of those four people handles what the team used to handle, spending 15 to 20 minutes a day on exceptions. The rest of the team moved onto onboarding the businesses being acquired. And using reporting to prioritize suppliers offering discounted credit terms, they documented over $400,000 in savings in less than a year.
Most of This Is a Timing Problem
A duplicate check is only as strong as what it compares against. DocLib checks QAD itself, so it catches an invoice already vouchered there and one still sitting in an approver’s queue. Matching works the same way, against the PO and the receipt as they stand in QAD right now.
When everything lines up, the voucher is created in QAD as part of that same run. So the invoice that cleared this morning is in QAD this morning, and month-end close is less of a scramble because the record kept up as you went.
What This Means for Whoever Owns the QAD Environment
Finance feels this first, but IT owns the consequences, so a few things are worth knowing up front.
Version coverage is broad. DocLib connects to QAD releases from old versions through the current.
And most of what finance will ask you to change later is configuration, not development. Approval routing runs off a matrix your team maintains, with approvers, amounts, sites, and cost centers. Variance tolerances and the coding behind them are set to match how you already handle them in QAD. Approvers set their own out-of-office delegation. New approver, new site, new threshold, none of that should land in your queue as a change request.
Suppliers are the Other Half of This
Everything above is about what happens once the invoice reaches you. A lot of the same mess lives one step earlier, on the purchasing side. POs get confirmed over email, date changes happen on the phone, and suppliers call AP for status because there is nowhere else to look.
A QAD-integrated supplier portal puts that in one place. Suppliers confirm POs, request a date change or a split line, submit invoices, and see where each one stands. Requests route to the buyer for approval, and approved changes are written into QAD. If a supplier does not confirm, the portal chases them, and only escalates when it needs a person.
AP also gets one thing out of this directly: suppliers can see invoice and payment status themselves instead of calling to ask.
Find Your Own Number
You cannot recover money you never measured. If you want to see what your own process is costing, in missed discounts, aged approvals, receipt exceptions, and manual hours, run your numbers through the AP automation ROI calculator and put a figure on it.
The backlog in your queue is the problem you can see, and it is worth fixing. But some of this money already walked out the door, and more of it is walking out right now, quietly, on invoices that will close clean and never flag anything. That is the part worth finding.
