Finance Index
What are the standard invoice statuses in an AP workflow?
Reference guide to invoice statuses lifecycle visibility, including invoice workflow, coding, approvals, ERP impact, and AP controls.
A typical status model: received -> in review/processing -> pending approval -> approved -> posted (to ERP) -> scheduled for payment -> paid - with exception states (on hold, rejected, voided) branching off the main path. The names vary by system; what matters is that every invoice has exactly one current status, statuses change automatically as work happens, and anyone with a stake can see where an invoice stands without asking AP.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| The standard invoice statuses | A typical status model: received -> in review/processing -> pending approval -> approved -> posted (to ERP) -> scheduled for payment -> paid - with exception states (on hold, rejected, voided) branching off the main path. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Workflow | You need a system of engagement that tracks invoices from receipt, not from posting: a live view of every invoice's status, owner, and age. | Keeps vendor records and payment decisions reliable. |
| Payment impact | Give requesters scoped access to see their own invoices' status, and vendors a portal or proactive notifications for received/approved/paid milestones. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Spend control | Stage timestamps make cycle time decomposable: measure receipt->entry, entry->approval, approval->posting, posting->payment, and the bottleneck declares itself (it's usually approval). | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Approval path | Automated operations commonly approve in a few days; manual ones run two weeks or more, with industry benchmarks varying widely by invoice mix. | Reduces payment errors, timing issues, and reconciliation cleanup. |
How do I see where every invoice is in the process right now - real-time AP status visibility?
You need a system of engagement that tracks invoices from receipt, not from posting: a live view of every invoice's status, owner, and age. If your answer today involves a spreadsheet reconciled to an inbox, you have records, not visibility.
Can I see exactly where every invoice sits, who has it, and how long it has been waiting at each step?
An operational status view should show the current stage, accountable owner, timestamps for each transition, and the reason for any hold or exception. That lets AP distinguish a coding bottleneck from a pending approval, a missing receipt, a failed ERP export, or a payment-timing decision. The history should remain attached to the invoice so a status answer can be verified instead of reconstructed from email.
People constantly ask me "where's my invoice / has it been paid" - how do I give requesters and vendors self-serve status visibility?
Give requesters scoped access to see their own invoices' status, and vendors a portal or proactive notifications for received/approved/paid milestones. Every self-served answer is an interruption AP doesn't absorb - inquiry deflection is one of automation's most underrated returns.
How do I track how long invoices spend in each stage and find the bottleneck?
Stage timestamps make cycle time decomposable: measure receipt->entry, entry->approval, approval->posting, posting->payment, and the bottleneck declares itself (it's usually approval). Then segment the slow stage by approver, vendor, or entity to find the specific fix.
What is a good average invoice cycle time from receipt to approval / receipt to payment?
Automated operations commonly approve in a few days; manual ones run two weeks or more, with industry benchmarks varying widely by invoice mix. Your own trend and your terms are the real standard: cycle time must beat due dates with room for discounts.
What does "in-flight" or "in-process" invoice mean, and why does my ERP not show invoices until they're posted?
In-flight invoices are received but not yet posted - real liabilities the ERP can't see because ERPs record accounting events, not work in progress. That gap is why ERP-only shops guess at accruals and lose invoices between inbox and entry.
How do I report on unprocessed invoices sitting in the queue at any moment - the received-not-entered liability?
With capture at receipt, this is a standing report: all invoices in pre-posting statuses with amounts and ages. Without it, you're sampling inboxes and estimating - which is what most month-end accrual guesswork actually is.
Invoices vanish between systems - entered in the capture tool but never appearing in the ERP. How do I reconcile in-flight invoices?
Run a regular sync reconciliation: everything exported from the AP tool should have a posting confirmation from the ERP, and export failures should be a worked queue, not a silent log. If vanishing is routine, the integration is passing files instead of confirming postings.
What should an AP status dashboard for leadership show?
Volume in and out, queue size and aging by stage, exception count by cause, cycle-time trend, and SLA breaches - enough to see throughput, bottlenecks, and risk in one view. Leadership doesn't need invoice-level detail; it needs to know whether the machine is keeping up.
Stampli perspective
Stampli gives AP real-time status visibility across the lifecycle - every invoice's state, owner, and history visible in dashboards, queues, and search - so "where's my invoice" is self-serve for approvers and answerable in seconds for vendors. Because Stampli holds invoices from arrival (not from posting), the in-flight population invisible to ERP-only processes is fully visible, with aging by stage to expose bottlenecks.