Tuning IDR, Duplicate Control, and Mobile Approval in AP
AP Shared Services processes 1,200 supplier invoices per month from 300 suppliers. About 60% are non-PO, 25% are in EUR or GBP, and 10% are duplicates. The team has deployed Oracle Intelligent Document Recognition for PDF invoices. The confidence threshold is set to 95%, so 45% of invoices route to manual review. Keyers still enter duplicate invoice numbers because the duplicate check is based only on invoice number, not supplier and amount. Suppliers email PDFs to AP; the supplier portal is available but unused. Month-end requires four FTEs and takes three days. The IDR supplier model has not been trained on the top 20 suppliers. The AP director wants to cut manual review to 20% and stop duplicate payments without adding staff. Mobile approvers also complain they cannot approve invoices from their phones.
1. How would you tune IDR and review routing to reach the 20% manual review target without increasing error rates?
Read the worked answer
I would not simply lower the global confidence threshold from 95% to a lower number. That would reduce review volume but push errors into invoice validation and payment. Instead, I would segment the population:
- Train supplier-specific IDR models for the top 20 suppliers, which account for a large share of volume.
- Use field-level confidence. A clean header with a low-confidence tax line should route only the tax field to review, not the whole invoice.
- Set a lower threshold for suppliers with a proven extraction accuracy record, and keep a higher threshold for new or poor-quality suppliers.
- Enable straight-through processing for invoices that pass IDR confidence, duplicate checks, validation, and tolerance rules.
I would measure straight-through rate, extraction error rate, and duplicate leakage weekly. The target is 20% manual review with no increase in duplicate payments or validation exceptions. That requires selective automation, not a blanket threshold cut.
2. What duplicate-prevention configuration and process changes do you recommend?
Read the worked answer
The duplicate check is too narrow. Invoice number alone will collide across suppliers and will miss rekeyed invoices with the same supplier and amount. I would configure duplicate identification on a composite of supplier, invoice number, invoice date, and amount, and enable duplicate checking during invoice entry and IDR import. When a potential duplicate is found, the invoice should be held or blocked for review, not silently created.
Process changes matter as much as configuration. Suppliers should submit through the supplier portal so the invoice is validated at the source and visible to AP. AP should use the IDR duplicate indicator and a daily duplicate exception report. Keyers should not override a duplicate warning without a documented reason. I would also reconcile the duplicate report to the payment register before each payment run. This reduces both duplicate entry and duplicate payment risk.
3. How can mobile approval and supplier portal adoption reduce the three-day cycle?
Read the worked answer
The three-day cycle is partly waiting time, not processing time. Mobile approval lets approvers act on invoice exceptions and non-PO invoices from a phone instead of waiting for a desk session. I would enable mobile-friendly approval notifications, show the key invoice details and hold reason, and allow approve, reject, or request information. The approval should still enforce the same authorization limits and audit trail as the desktop process.
Supplier portal adoption reduces inbound email and keying. Suppliers can submit invoices with structured data, see status, and correct rejected invoices. That shortens the correction loop and reduces duplicate email submissions. I would onboard the top 20 suppliers first, measure portal submission rate, and track cycle time by channel. Mobile approval and portal adoption are complementary: the portal improves input quality, and mobile approval removes bottlenecks after validation.