What Is Procure-to-Pay?
Procure-to-pay (P2P) is the complete cycle that begins when someone in your organization identifies a need for goods or services and ends when the vendor receives payment. Every purchase your facility makes — medical supplies, food service items, maintenance contracts, therapy equipment, office supplies — follows this cycle, whether you've formalized it or not.
The difference between facilities that manage procurement well and those that don't usually isn't intelligence or intention. It's whether the P2P cycle is a structured, automated process or an informal series of habits and workarounds. One produces predictable costs, clean audit trails, and efficient operations. The other produces invoices in department head inboxes, unauthorized purchases on personal credit cards, and month-end budget surprises.
This guide walks through every stage of the P2P cycle, explains what goes wrong at each step in long-term care environments, and describes what a properly automated P2P process looks like in practice.
The Six Stages of the P2P Cycle
Stage 1: Requisition
What it is: A purchase requisition is the formal request to buy something. It's the starting point of every purchase — the moment a need is identified and a request is created.
What usually goes wrong in LTC: In most long-term care facilities, requisitions don't exist in any formal sense. A department head needs wound care supplies, so they call a vendor. A dietary manager is running low on supplement products, so they order directly from the sales rep. These are unauthorized purchases made outside any formal process — they don't exist in the system until an invoice arrives.
Without a requisition step, there's no point in the process where someone with budget authority confirms that a purchase is appropriate before it's made. Budget control becomes reactive (reviewing what was spent) rather than proactive (approving what will be spent).
What good looks like: Department heads submit purchase requests through the procurement system. Each request specifies what's needed, the quantity, the preferred vendor, and the cost center. The system checks the request against the department's remaining PPD budget and flags any request that would push the department over target. A manager reviews and approves or modifies the request before any order is placed.
This adds maybe 2–3 minutes to the purchasing process for a department head. In exchange, the facility gains advance control over spending and eliminates the "invoice surprise" dynamic.
Stage 2: Purchase Order
What it is: Once a requisition is approved, it becomes a purchase order (PO) — the formal document sent to the vendor authorizing the purchase at a specified price, quantity, and delivery date.
What usually goes wrong in LTC: Many long-term care facilities operate with minimal PO discipline, especially for routine supplies. Orders are called in, emailed directly, or placed on vendor websites without generating a PO in the accounting system. When the invoice arrives, there's no PO to match it against — which means manual research, delayed payment, and higher risk of billing errors going undetected.
PO coverage rates (the percentage of invoices that have a matching PO) at facilities without formal procurement processes often run at 30–50%. Best-in-class operations run at 90%+.
What good looks like: Every approved requisition automatically generates a PO. The PO is sent to the vendor (by email, EDI, or through a vendor portal) and simultaneously creates a record in the system that AP will use for matching when the invoice arrives. The PO includes the agreed price per the vendor contract — so any invoice with a different price is automatically flagged as a discrepancy.
The discipline of PO-based purchasing is the single change that most dramatically improves the rest of the P2P cycle. Without it, every downstream step is harder.
Stage 3: Receiving
What it is: When goods arrive or services are completed, someone in the facility needs to confirm receipt — verifying that what was ordered is what was delivered, in the right quantity and condition.
What usually goes wrong in LTC: Receiving is the most commonly skipped step in long-term care procurement. Goods arrive, the nurse's aide or stock room person puts them away, and no one creates a receiving record. This creates two problems:
First, it enables billing discrepancies to go unchallenged. If a vendor ships 8 cases of gloves but invoices for 10, and there's no receiving record, AP has no basis for disputing the invoice. Second, it undermines the 3-way matching process — without a receiving record, automated matching can't work, and the efficiency gains of PO-based procurement are significantly reduced.
What good looks like: Receiving is completed by the person who physically accepts the delivery — using a simple mobile interface, they confirm receipt against the PO, note any discrepancies (wrong quantity, damaged goods, substitutions), and submit the receiving record. This takes 2–3 minutes for most deliveries and creates the third leg of the 3-way match.
The receiving confirmation doesn't require any accounting knowledge. It's a simple "did you get what was ordered?" question with a digital record attached.
Stage 4: Invoice Capture
What it is: When a vendor sends an invoice, the AP team needs to capture all of the invoice data — vendor, invoice number, date, line items, amounts — into the accounting system.
What usually goes wrong in LTC: Manual invoice data entry is the biggest AP time drain in skilled nursing and assisted living facilities. The average invoice takes 10–15 minutes to key manually. At 400–600 invoices per month for a 100-bed facility, that's 66–150 hours of manual labor every month — before any matching, approvals, or payments happen.
Manual entry also introduces errors. Transposed digits, wrong vendor codes, incorrect GL account assignments — small errors that create reconciliation problems downstream.
What good looks like: AI-powered invoice capture reads any invoice format — PDF attachments, scanned paper, emailed images — and extracts all data automatically using optical character recognition (OCR) and machine learning. The system recognizes vendor-specific invoice formats and improves accuracy over time. Most modern systems achieve 95–99% accuracy, meaning human review is only needed for a small percentage of exceptions.
Invoice capture should be connected to a centralized inbox or portal — a single destination for all invoices from all vendors, regardless of how they're submitted.
Stage 5: Three-Way Matching
What it is: Three-way matching compares three documents: (1) the purchase order, (2) the receiving confirmation, and (3) the vendor invoice. If all three agree within your configured tolerances, the invoice is approved for payment. If there's a discrepancy, it's flagged for human review.
What usually goes wrong in LTC: Without POs and receiving records, 3-way matching is impossible. Many facilities skip matching entirely — every invoice is reviewed manually, which is both time-consuming and less accurate than automated comparison. Others do 2-way matching only (invoice vs. PO, no receiving check), which misses quantity and delivery discrepancies.
When matching is skipped, common problems get through: invoices for goods not received, quantities billed higher than ordered, prices higher than contracted, and duplicate invoices for the same shipment.
What good looks like: Automated 3-way matching runs as soon as an invoice is captured. The system retrieves the matching PO and receiving record and compares all three line by line. Matches pass automatically and are queued for payment. Discrepancies are flagged with the specific variance highlighted — wrong price, wrong quantity, no receiving record — and routed to the right person for resolution.
In a facility with good PO discipline and consistent receiving records, 70–85% of invoices will pass 3-way match automatically without human review. AP staff focus on exceptions, not routine processing.
Stage 6: Approval and Payment
What it is: After matching, invoices that require review go through a structured approval workflow before payment is scheduled.
What usually goes wrong in LTC: Manual approval chains are where invoices go to die. An invoice lands in a manager's email inbox. They're in a care planning meeting. It sits for two days. Then it gets forwarded with a one-word "approved." By the time it gets back to AP, the early payment discount window has closed — and if the same invoice was accidentally forwarded to two people, AP might approve it twice.
Paper-based or email-based approvals also create compliance problems: there's no reliable audit trail, no escalation mechanism for invoices that don't get approved, and no consistent record of who approved what.
What good looks like: Digital approval workflows route invoices automatically to the right approver based on rules you configure: department, amount, vendor, cost center. Approvers receive a mobile notification, review the invoice in the system, and approve with a tap. If an approver doesn't act within a configured window (24 or 48 hours is typical), the system automatically escalates or sends a reminder.
Payment scheduling is equally important. Once approved, invoices should be queued for payment according to terms — capturing early payment discounts when available, paying at net terms when not. The system should alert the AP team to invoices where early payment discounts are expiring.
How LTC Workflows Make P2P Uniquely Complex
Long-term care facilities have P2P requirements that generic procurement software doesn't always handle well. Understanding these differences is important when evaluating a platform:
Census-Based Budgeting
In most industries, budgets are fixed: the materials budget for a manufacturing plant doesn't change because production volume fluctuated last Tuesday. In long-term care, PPD budgets mean your spending authority is directly tied to daily census. A P2P platform built for LTC should integrate with your EHR — PointClickCare, MatrixCare — and recalculate department spending limits in real time as census changes.
A generic procurement tool won't do this. It manages fixed budgets. For LTC, that's fundamentally the wrong model.
Acuity and Resident-Specific Purchasing
Some purchases in a skilled nursing facility are resident-specific — a particular wound care protocol, a specialized nutrition product, an adaptive device. These purchases need to be tracked not just against a department budget but against the specific resident's care plan, and in some cases are billable to payers.
A robust LTC procurement platform should support resident-level purchase tracking and flag purchases that may qualify for separate billing.
Multi-Vendor, Multi-Category Complexity
A typical SNF purchases from 50–150 active vendors across a dozen categories: medical supplies, dietary, pharmacy, maintenance, equipment, therapy supplies, staffing services, technology, professional services. Managing these through a unified P2P platform — with consistent catalog management, PO generation, and invoice matching across all categories — requires a vendor management system that handles the complexity of healthcare supply categories without requiring separate workflows per category.
Regulatory Documentation Requirements
Long-term care facilities operate under significant regulatory scrutiny. CMS surveys, state health department audits, and financial audits all may require documentation of procurement decisions. The P2P system needs to maintain a complete, retrievable audit trail: who requested, who approved, what was received, what was paid, and when.
This isn't just a compliance checkbox — it's operational discipline that protects the facility and its administration.
Evaluating a P2P Platform for Your Facility
When you're reviewing procurement software for a long-term care environment, these are the questions that separate platforms built for your environment from generic tools that technically work but create friction:
Does it integrate with your EHR? PointClickCare and MatrixCare integrations for live census are table stakes for LTC-specific procurement.
How does it handle PO discipline? Does it require POs before orders are placed? Can you configure thresholds (no PO required under $X)? What happens when someone tries to pay an invoice without a matching PO?
How does invoice capture work? Is OCR included? Does it handle multiple invoice formats? What's the workflow for exceptions?
What does 3-way matching look like? Can you configure tolerances? How are discrepancies routed? What's the approval workflow for flagged invoices?
Does it support PPD budgeting? Not just fixed budgets — dynamic PPD limits that update with census.
What are the reporting capabilities? Spend by department, vendor, category. PPD trend over time. Early payment discount capture rate. Duplicate payment detection.
How long does implementation take? For a single SNF, 3–4 weeks is achievable with a platform designed for fast deployment. Longer timelines suggest a platform that requires heavy configuration or consulting.
The ROI of a Well-Implemented P2P System
The return on investment from a properly implemented P2P system in long-term care comes from multiple sources that compound:
| Source | Typical Impact |
|---|
|---|---|
| AP labor reduction (80%) | $17,000–$40,000/year per facility |
|---|---|
| Maverick spending reduction | $50,000–$150,000/year per facility |
| Early payment discount capture | $18,000–$24,000/year per facility |
| Duplicate payment elimination | $1,500–$7,500/year per facility |
| Vendor contract compliance | 8–12% of non-contracted spend |
| Total | $86,000–$221,000+/year per facility |
Most facilities see full ROI within 2–4 months of going live — not because P2P automation is magic, but because it removes friction that's been silently costing money for years.
Getting Started
You don't need to implement the full P2P cycle at once. The most effective starting point is usually:
- Centralize your vendor catalog — build a single, approved vendor list with contracted pricing
- Enforce POs on higher-dollar purchases — start with a threshold (e.g., all purchases over $250)
- Implement AI invoice capture — eliminate manual data entry immediately
- Add digital approval workflows — replace email chains with structured, trackable approvals
From there, you build out receiving workflows, 3-way matching, and more sophisticated budget controls as your team adapts.
Adelpo is built specifically for this progression in long-term care environments. Most facilities are fully live within 3–4 weeks. If you want to see what the full P2P cycle looks like in a platform designed for skilled nursing and assisted living, book a 15-minute demo with our team.