Oracle Fusion Payables: invoice on hold or stuck at Needs Revalidation
Oracle Fusion Payables invoice validation failed on hold needs revalidation
Also searched as
- Fusion AP invoice status needs revalidation
- how to release invoice hold Oracle Fusion Payables
- Fusion Payables matching required hold
- Validate Payables Invoices scheduled process invoice stays unvalidated
Short answer
An invoice in Fusion Payables is either Validated, Needs Revalidation, or Never Validated. Holds are placed by validation when a check fails, so the fix is to read the hold name on the Holds tab, correct the underlying data (match, price, tolerance, account, tax), and run Validate again. Manual release is possible but only for hold types your role may release.
Applies to: Oracle Fusion Cloud Applications Payables, current quarterly releases
Diagnose and clear the hold
- 1Open Payables > Invoices > Manage Invoices, search the invoice number and open Edit Invoice.
- 2Read the Validation Status, then open the Holds tab and note the Hold Name and Hold Reason, not just the count.
- 3If the status is Needs Revalidation, something changed after the last validation (a line edit, a distribution change, a PO change or a tax change). Choose Actions > Validate.
- 4For matching holds, open the matched PO or receipt in Procurement and confirm the quantity, price and UOM against the invoice line.
- 5For tolerance holds, check Manage Invoice Tolerances for the tolerance assigned to the business unit or supplier site.
- 6For account holds, fix the distribution combination or the segment value validity (inactive or end-dated).
- 7If the hold type allows manual release and the cause is accepted, select the hold and click Release with a Release Reason.
- 8To validate in bulk, run the Validate Payables Invoices scheduled process for the business unit and review the output log.
How validation and holds work
Payables validation runs a series of checks on each invoice: that the supplier and site are active, that header and line amounts agree, that distributions exist and are on valid account combinations, that tax is calculated, and, for matched lines, that the invoice agrees with the purchase order or receipt within tolerance. Each failed check places a named hold. The invoice cannot be paid or accounted while a hold that blocks those actions remains.
Needs Revalidation is not an error in itself. It means the invoice was previously validated and a later change invalidated the result. Any edit to amounts, distributions, terms or match references flips the status. Running Validate again either returns the invoice to Validated or places fresh holds.
Holds come in system-placed types (created by validation) and manual types (placed by a user). System holds are normally cleared by fixing the cause and revalidating, because the next validation run releases a hold whose condition no longer applies. Manual holds are cleared by Release.
Common hold families and what to check
Matching holds. Quantity, price and amount checks against the PO. A frequent cause is a PO that was revised after the invoice was entered, a receipt that has not been created yet for a three-way match, or a unit of measure difference between the PO line and the invoice. Check the match basis on the PO schedule (two, three or four way) before assuming the invoice is wrong.
Tolerance holds. Invoices that exceed price, quantity or amount tolerance are held even when the vendor is right. Tolerances are defined in the Invoice Tolerances setup and attached through Manage Invoice Options or the supplier site. Widening a tolerance is a policy change, so it belongs to the finance owner, not the person clearing the queue.
Distribution and account holds. A distribution on a segment value that was end-dated, a missing balancing segment, or a cross-validation rule failure leaves the invoice unaccountable. Fix the combination on the distribution line; do not override the chart of accounts rules.
Tax holds. Tax lines that cannot be derived, because the tax determinants (ship-to, bill-from, product classification) are incomplete, will hold the invoice until Manage Tax Rules or the invoice tax attributes are corrected.
Releasing holds and permissions
Release is controlled by hold-level setup and by privileges. Some holds can be released only by a role with the Release Invoice Holds privilege, and some hold types are configured so that they cannot be released manually at all. If the Release button is greyed out, that is by design, and you need to fix the cause.
Every release records the user, the date and the release reason, so a clean audit trail exists. Use specific reason codes rather than a generic one, because auditors sample these. Releasing a matching hold over an unreceived quantity turns a control into a suggestion, and the exposure shows up later as an overpayment.
Navigator > Payables > Invoices > Manage Invoices Edit Invoice > Holds tab > select hold > Release Scheduled Processes > Validate Payables Invoices Parameters: Business Unit, Ledger, Supplier (optional), Invoice Group (optional)
Finding stuck invoices in bulk
A queue of held invoices is best worked by hold name rather than invoice by invoice. Use the Invoice Workbench saved search filtered on Validation Status and Hold Name, or build an OTBI analysis against the Payables invoice holds subject area, so that you can see which hold type dominates. If one hold type accounts for most of the queue, the root cause is usually a single setup issue, such as a missing tolerance or an inactive account segment value.
If validation itself appears stuck, check the Scheduled Processes monitor for the Validate Payables Invoices run and confirm that it completed rather than sitting in Blocked or Running. A job stuck behind an incompatible process will leave invoices in their prior status.
Common pitfalls
- !Releasing a matching hold to clear a queue without checking the receipt, which pays for goods not yet received.
- !Widening a tolerance globally to fix one supplier instead of assigning a supplier-site tolerance.
- !Editing the invoice repeatedly in small steps, each of which resets the status to Needs Revalidation.
- !Assuming a greyed-out Release button is a bug; the hold type may be non-releasable by setup.
- !Fixing a distribution on one invoice but leaving the end-dated segment value that will break the next hundred.
How an ERP-grounded AI assistant handles this
A grounded assistant such as ERPray can read the invoice, its holds and the matched PO or receipt in one pass, then explain in plain language which check failed and what the data says (for example, invoiced quantity 120 against 100 received). It is read-only by default and shows the query it used. Any release or edit stays a human action with the normal approval, so the assistant narrows the queue by hold type and root cause, and the AP team makes the call.
Frequently asked questions
What does Needs Revalidation mean on a Fusion invoice?
It means the invoice was validated before but something changed afterward, such as an amount, a distribution, a term or a match reference. Run Validate from Actions on the invoice or run the Validate Payables Invoices scheduled process. It returns to Validated or gets new, specific holds.
Can I release any hold manually?
No. Releasability is set per hold type, and your role needs the release privilege. System holds are normally cleared by fixing the cause and revalidating. If the Release button is unavailable, the hold is either non-releasable by setup or your role lacks the privilege.
Why does the same invoice get held again after I release the hold?
Revalidation re-checks the condition. If the root cause, such as the price difference or the end-dated account, is still present, validation places the hold again. Release a hold only after deciding the variance is acceptable, and fix data issues at the source.
Where do I change tolerances?
Use the Manage Invoice Tolerances task in Payables setup, then assign the tolerance set through invoice options or the supplier site. Treat this as a controlled finance policy change, because it alters which invoices pass without review.
Related
Oracle Fusion Period Close: A Practical Checklist
Closing a Fusion GL period cleanly means closing every feeder subledger first (Payables, Receivables, Costing, Fixed Assets), running Create Accounting to post everything to GL, reconciling subledger-to-GL balances, and only then setting the GL period status to Closed - not Close Pending, which still allows adjustments. Close Monitor gives a single dashboard of every subledger's close status instead of checking each module separately.
Error fixFix The Oracle Fusion "You Don't Have Access To This Data" Error
This generic Oracle Fusion security message means the function privilege and the data security scope did not both line up for that user on that record - most often the job role is assigned but the matching data role, security profile, or business unit and ledger context in Manage Data Access for Users is missing. Fix it by checking data access setup for the user's role, not by re-granting the same job role again.
How-toFix Wrong Row Counts When Joining Across OTBI Subject Areas
Most subject areas in Oracle Fusion OTBI are self-contained and only support reliable analysis within their own folders; dragging a folder from a second subject area into the same analysis without a genuine shared join key silently produces duplicated or missing rows because OTBI has no way to correctly relate the two fact grains. Fix it by staying inside one subject area where possible, or by explicitly using a subject area that Oracle designed to cross domains, rather than combining arbitrary folders yourself.
Error fixClear An Oracle Fusion ESS Job Stuck In Blocked Status
A Blocked status on an Oracle Fusion Enterprise Scheduler (ESS) job almost always means an earlier instance of the exact same job is still running or stuck, and the job definition does not allow simultaneous requests. Find and finish, or cancel, the earlier request first; only then does the Blocked request move to Running.
Error fixFix FBDI Import Failures From Interface Table Validation Errors
When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load.
How-toOTBI vs BI Publisher: Which One Should You Use
Use OTBI when a business user needs ad hoc, self-service, real-time analysis with no fixed layout. Use BI Publisher when you need a pixel-perfect, scheduled, high-volume, or externally distributed document such as an invoice, check, or statutory report. Most Fusion implementations end up using both, not one instead of the other.
AI for ERPFusion Cloud ERP AI: OCI Generative AI Service vs. a Private LLM
Oracle's OCI Generative AI Service is a real option for Fusion Cloud ERP, but not the only one. Compare it honestly against a private LLM for sensitive data.
Stuck on Oracle Fusion Cloud ERP?
Talk to engineers who work inside Oracle Fusion Cloud ERP every week, and who build private AI that answers these questions from your own ERP data.