Cooper Software Keeps Invoice Checks in Place for Manual Approvals
An invoice can be captured correctly and still remain unresolved because the receiving record is missing, a price differs from the purchase order or nobody owns the next decision. Cooper Software says its approach to supplier document processing separates those conditions before a transaction enters IFS. The distinction matters because faster document capture can coexist with slow approvals and growing exception queues. Comments from Cooper and an operational analysis submitted by SetupFlow Enterprise identify a shared problem: completing an individual task does not establish that work has progressed across departmental boundaries.
Capture Is Only the First Check
David Kidd, Managing Director of Cooper Software, said the company’s TRAX system checks proposed invoice information against the customer’s own IFS records. According to his written response to The Supply Chainer, automatic filing requires confidence in the captured information and successful validation of the transaction. Checks cover the supplier, purchase order, quantities, prices, goods receipt, totals, duplicates and changes to bank details. If a required check cannot run, Kidd said the invoice is held. These are the company’s descriptions of its controls, rather than independently measured performance results.
Kidd emphasized that a person handling an exception should not be able to bypass the same controls applied to automatic processing. “If a check can't run, the invoice is held rather than waved through. A person clicking ‘file’ faces the same checks, so a stop can't be skipped, only cleared with a recorded reason.” That distinction separates an authorized resolution from an undocumented override. It also makes the explanation for releasing a transaction part of the operating record.
Waiting Should Not Always Become Manual Work
Cooper’s response distinguishes a genuine discrepancy from a transaction that is simply waiting for another event. Kidd said an invoice arriving before the goods can remain pending and be checked again when the receipt appears in IFS. Small price differences can pass if they fall within the customer’s defined tolerance. Cases reaching a reviewer should therefore contain a specific unresolved question and the supporting evidence. According to Kidd, aging queues also generate alerts, although his response did not specify how responsibility is assigned across departments.
That ownership issue extends beyond accounts payable. In an analysis submitted to The Supply Chainer, Sajeev Benny Sukumaran, Founder of SetupFlow Enterprise, described how warehouse, dispatch, planning and finance teams can each meet their own targets while an order remains stalled between them. “Communication certainly matters, but it cannot compensate for an operating model that leaves important transitions undefined.” His argument concerns organizational design rather than the performance of Cooper’s software. It explains why identifying an exception and assigning someone accountable for resolving it are separate requirements.
Measure Resolution, Not Processing Activity
Kidd said TRAX reports the share of invoices filed without human intervention, the reasons transactions are held, price variance against purchase orders and approval duration. Those measures can help distinguish a useful control from a queue that merely accumulates work. They can also reveal whether recurring problems originate in supplier documents, purchasing records or receiving activity. Cooper did not provide customer results quantifying reductions in errors or approval time. The evidence supplied therefore describes how improvement would be assessed, rather than establishing its magnitude.
The operational test is whether a held transaction reaches an authorized decision with less avoidable delay. A high automatic-processing rate would be incomplete evidence if unresolved exceptions continued to age elsewhere. Equally, a high hold rate could reflect missing receipts rather than defective invoices. Connecting each hold to its cause, responsible function and resolution time makes those differences visible. The value of automation depends on the work it helps finish across the process, as well as the documents it reads.
