What Statuses to Track Across Procurement and AP So Work Does Not Disappear

1. Track requests: submitted, approved, rejected, and ordered. 2. Track POs: issued, open, partially received, and closed. 3. Track service tickets: requested, fulfilled, and invoiced. 4. Track card outcomes: authorized, settled, and reconciled. 5. Track invoices: received, coded, approved, scheduled, and paid. 6. Track ERP exports: exported, failed, and corrected. 7. Watch the handoffs: the transitions where items get lost.

The early statuses cover requests, POs, and service tickets. A purchase request needs a status, submitted, approved, or rejected, and crucially whether an approved request actually became a PO, because an approved request that is never ordered is a common disappearance. A PO needs status through its life, issued, open, partially received, closed, so POs do not sit open forever or get lost.

Service tickets need tracking too, since service spend often lacks a physical receipt. Knowing whether a requested service was fulfilled and then invoiced keeps service work from falling through, because a service delivered but never billed or matched is easy to lose. Tracking these front-of-lifecycle statuses is what keeps committed spend visible before it becomes an invoice.

Card outcomes are a frequent disappearance point. A card purchase moves through authorized, settled, and reconciled, and the gap is usually reconciliation, a card transaction that settled but was never reconciled to a receipt or coded correctly. Tracking card outcomes through to reconciliation is what keeps card spend from becoming an untracked hole.

Invoice statuses are the core of AP visibility. An invoice moves through received, coded, approved, scheduled, and paid, and an item can stall at any of these, an invoice received but never coded, approved but never scheduled. Tracking the invoice through each stage is what surfaces where it is stuck, so nothing sits in limbo unnoticed between receipt and payment.

The last and often most overlooked status is the ERP export. When an approved, paid invoice is exported to the ERP, the export can fail, and a silent export failure is a classic disappearance, the work looks done in the AP system but never landed in the ERP. Tracking export status, exported, failed, corrected, is what catches these before they become reconciliation problems at close.

This final handoff matters because it is the seam between the AP system and the system of record. An item can be fully handled everywhere upstream and still not reach the ERP, so explicitly tracking the export, and surfacing failures for correction, closes the last gap where work disappears. Without it, the financial record can be missing transactions that everyone believed were complete.

Stampli provides real-time visibility across the procure-to-pay process, so the status of requests, POs, invoices, and payments is visible in one place rather than scattered across stages and systems. Because the invoice is the workspace, its status through received, coded, approved, scheduled, and paid is always current without manual tracking.

Stampli's procurement intake carries requests and POs into the same platform, so the front of the lifecycle connects to AP, and Stampli Card brings card spend into the same environment so card outcomes can be reconciled rather than lost. Validation against the ERP before posting, and one-to-one reconciliation, help surface export and reconciliation issues rather than letting them pass silently.

Because the ERP stays the system of record and every action is captured in an immutable audit trail, the handoffs between stages and to the ERP are traceable. Keeping the spend lifecycle on one platform is what lets Stampli show status end to end, so items do not disappear at the seams between procurement, AP, card, and the ERP.