Understanding Status Issue Priority on Jobs
Last updated: March 30, 2026
When OpenEnvoy processes an invoice, it runs a series of validations to check for completeness and accuracy. If exceptions are found, they appear as status issues in the Status Report on the job. A single job may display multiple status issues at once — this guide explains how to interpret and prioritize them.
Why do multiple status issues appear?
OpenEnvoy validates invoices across several categories simultaneously: purchase order data, receipt data, GL codes, tax information, and more. Because these checks run in parallel, a single root cause (such as a missing purchase order) can trigger multiple related status issues.
For example, if a PO-based invoice (match job) cannot locate its purchase order, you may see:
Provide purchase order — the PO itself was not found
Confirm missing GL code — for match jobs, the GL account is derived from the purchase order, so a missing PO means the GL code cannot be populated either
Receipt not found in ERP — receipt matching could not proceed without PO reference
In this case, the root cause is the missing PO. Since the PO provides both the GL account and the receipt reference for match jobs, resolving the PO issue first will likely clear the other two automatically upon rematch.
Recommended priority for resolving status issues
While status issues do not currently display in a fixed priority order, we recommend addressing them in this sequence for the most efficient resolution:
1. Purchase order issues (resolve first)
These are the most foundational — many other validations depend on PO data being present and correct.
Status issue | What it means | What to do |
Provide purchase order | PO data not found in the system | Verify the PO number on the invoice and update it in Details → Purchase Order Number |
Provide missing PO data for pending lines | PO exists but line items could not be matched | Check if the PO is approved, matches the vendor/site, and has unconsumed lines |
Purchase order not approved in ERP | PO exists but is not yet approved | Confirm PO approval status in your ERP system |
2. Receipt and delivery issues
These depend on PO data being resolved first.
Status issue | What it means | What to do |
Receipt not found in ERP | No matching receipt data available | Verify receipt exists in your ERP for the relevant PO lines |
Missing fuel delivery ticket data | FDT data cannot match invoice lines | Check that fuel delivery ticket is attached and data is complete |
3. Amount, quantity, and rate conflicts
These are comparison-based checks that require review.
Status issue | What it means | What to do |
Review conflict with PO total amount | Invoice total differs from PO total | Compare invoice and PO totals; check if amounts were consumed by other jobs |
Review conflict with PO amount | Unit price mismatch between invoice and PO | Verify unit pricing on both the invoice and the purchase order |
Review conflict with PO quantity | Quantity billed differs from PO quantity | Confirm quantities on invoice vs. PO and check for partial consumption |
4. GL code and tax issues
These are typically configuration-related and can be resolved after the above.
Status issue | What it means | What to do |
Confirm missing GL code | GL code is missing or incomplete on line items | Add or correct the GL code on the affected lines |
Review conflict with PO tax | Tax rate/amount mismatch between invoice and PO | Review tax configuration on the PO vs. the invoice |
5. Other validation issues
These are less common and typically company-specific.
Status issue | What it means | What to do |
Confirm service invoice | Invoice is against a service-type PO | Review and confirm the service was rendered |
Review invoice from freight vendor | Vendor classification needs verification | Confirm vendor is classified as a freight provider |
Tips for efficient resolution
Start from the top of the priority list. Resolving foundational issues (like missing PO data) often clears dependent issues automatically.
Click Rematch after making changes. This refreshes the job and updates the Status Report with any resolved or new issues.
Use the Job List Filter to find all jobs with a specific status issue across your workspace.
Action Required issues have a clear fix — click the action button and follow the steps. Review issues require your judgment to determine the right course of action.
Summary
The general priority order is:
Purchase order issues
Receipt and delivery issues
Amount, quantity, and rate conflicts
GL code and tax issues
Company-specific validations
Always resolve the most foundational issue first, then rematch to see which remaining issues clear automatically.