ERP Modernization · October 30, 2026 · 6 min read
Invoices are stuck in approval: how to trace a Munis/EERP bottleneck
Follow one invoice from entry to payment, find the step that's waiting, and give AP, the department or the ERP administrator a specific correction to make.
By Altioras Civic
Key takeaways
- Check the invoice's current status and history before asking someone to approve it again.
- Match the waiting step to the municipality's approved authority and the employee's actual access.
- After the correction, confirm what happened to the invoice; approval alone doesn't mean it was posted or paid.
Start with one invoice and its last completed step
A vendor calls about an overdue invoice. The department says it approved the purchase, AP says the invoice is still waiting, and the manager can't find anything to approve. Bring those staff together around the same invoice before changing the routing or entering another copy.
Record the vendor number, invoice number, amount, purchase order reference where applicable, batch reference and current status. Use the available transaction history to find the last completed action, its date and who performed it. Save any rejection message exactly as shown. A purchase approval, receipt confirmation and invoice approval may be separate actions in your municipality's process.
Tyler describes Enterprise ERP as powered by Munis. This guide uses Munis/EERP for that product. The checks below are a suggested investigation sequence. Confirm the available history, status meanings, routing rules and reassignment options for your release and configuration with your ERP administrator; these aren't instructions for a particular screen.
Trace the invoice before changing anything
- Step 1Find the recordMatch vendor, invoice, amount and PO.
- Step 2Read the historyFind the last completed action.
- Step 3Find who's nextCheck the required approval and access.
- Step 4Correct and retestAssign the cause and check the result.
- Step 5Confirm payment statusCheck posting, holds and the payment run.
Sources: Tyler Technologies — Enterprise ERP, powered by Munis
Check that the invoice reached approval
Ask AP or the employee who entered the invoice to confirm that entry is complete and that it was submitted through the agency's normal process. If it remains in an entry or validation stage, an approver reminder won't resolve it. Read the actual message and assign the missing step.
Compare the invoice with the purchase order, receiving record and account coding, where those records are required. Ask the receiving department to confirm what was delivered, including partial deliveries. For a non-PO invoice, use the municipality's separate approval procedure.
Sacramento County's published AP procedure lists incomplete invoice information, missing or unposted receipt records and quantity differences among reasons payment may be delayed. It concerns the County's COMPASS environment, not Munis instructions. Use your own policies to determine which documents and checks apply.
Find the approval that's actually waiting
Have the ERP administrator and AP lead compare the current waiting step with the approved routing rules. Check the department, account coding, amount and invoice type used to select the route. Record who should approve this invoice and why.
If useful, compare it with an invoice that completed the same route. Choose one with comparable coding and approval requirements. An invoice from another fund or above a different approval threshold may take a different path.
Ask the assigned approver to check their actual queue. If the invoice is there, find out whether they're waiting for a receipt, a corrected charge or another department's answer. If it isn't there, have the administrator investigate the assignment and authorized access. An email notification by itself doesn't establish the transaction's status.
Correct the cause without bypassing approval
If an approver has left or is absent, the Finance owner should confirm who has authority to act. The ERP administrator can then check whether the installed configuration supports an approved substitute, delegation or reassignment. Record the authorization and its duration. Don't share credentials or add broad approval rights to clear the queue.
For incorrect coding or missing documents, name the employee who must correct them and tell AP when to check again. Confirm whether a correction requires resubmission or renewed approval in your configuration. Retain the original history rather than deleting and re-entering the invoice to make the delay disappear.
GFOA recommends written financial procedures that identify employees' responsibilities and transaction authority. Use those approved assignments when resolving a routing problem. Changing a software role doesn't grant someone authority under the municipality's policy.
Use a short worksheet during the review
Add the actual invoice reference, finding, assigned employee and follow-up date to your internal copy. Keep vendor banking and other restricted details in approved agency storage.
| What to check | What staff compare | Who reviews the result |
|---|---|---|
| The right invoice | Match vendor number, invoice number and amount to the original document; check for another entry before adding one. | AP |
| Entry and submission | Read the current status, validation messages and last completed action. | AP and the employee who entered it |
| Receipt and coding | Compare the invoice with the PO, receipt and approved account coding, where required. | Receiving department and AP |
| Required approval | Compare the waiting step with the approved route for this amount, department and invoice type. | Finance owner and ERP administrator |
| Approver access | Check the assigned employee's queue and authorized role; verify any substitute's approval authority. | ERP administrator and Finance owner |
| Rejected or corrected invoice | Read the reason, confirm the correction and check whether resubmission or approval is required. | Employee making the correction and AP |
| After approval | Check the batch/posting result, any hold and the scheduled or completed payment record. | AP and the payment-run reviewer |
Confirm the result and keep the next payment run in view
After the correction, AP should reopen the same invoice and confirm its next status and history. If approval is complete, check whether posting completed and whether a hold or payment-run selection still prevents payment. Tell the department what remains outstanding before promising the vendor a payment date.
If support is needed, send the product release, module, invoice and batch references, expected route, actual history, exact message and the last date the process worked. State whether one invoice, one department or several routes are affected. Use the approved support channel for restricted records.
Finish the review with a named person and next check: who corrects the record, who verifies the invoice has moved, and who confirms payment. Update the staff procedure if the resolution changes how future invoices should be handled. Altioras Civic's ERP Implementation & Remediation service can help Finance and IT investigate recurring routing problems and test an agreed correction.