Does Your Hospital Have an SLA for Vendor Inquiry Response? Here's Why It Should

Your hospital has a service level agreement (SLA) for almost everything that matters operationally.

Clinical: Code response within 2 minutes. Rapid response team activation within 5 minutes. Lab result turnaround for STAT orders within 60 minutes.

IT Help Desk: Tier 1 issues acknowledged within 1 hour, resolved within 4 hours. Tier 2 within 4 hours acknowledged, 24 hours resolved. System-down priority within 15 minutes.

Procurement: Purchase order processing within 2 business days. Contract amendment review within 5 business days.

Vendor inquiry response from AP? No SLA. No tracking. No accountability. No defined escalation path.

A McKesson AR rep emails asking about an outstanding invoice. Your organization has no formal commitment to when that gets answered. It might be answered in two hours. It might be answered in three days. It might not be answered until the AR rep follows up, calls, or emails the procurement director.

This isn't a minor administrative gap. As we've explored throughout this series, delayed vendor inquiry response has real costs: credit holds that disrupt clinical supply chains, early-pay discounts that expire, vendor relationships that erode under repeated poor experiences. An SLA doesn't solve those problems by itself, but it creates the organizational structure that makes solving them possible.

Why AP Doesn't Have SLAs (Yet)#

The absence of vendor inquiry SLAs in healthcare AP isn't oversight. It reflects how the function has historically been understood. AP is a transaction processing function. It processes invoices. The performance metrics that exist (cost per invoice, DPO, exception rate) are process efficiency metrics, not service delivery metrics.

When AP's identity is "invoice processor," vendor inquiry handling is an informal service activity that sits alongside the "real" work. There's no accountability framework because there's no frame that would prompt someone to build one.

But as this series has argued from the beginning, vendor inquiry handling is a service delivery function. It operates at significant volume, carries real financial stakes, and has direct implications for supply chain reliability. The natural organizational response to a service delivery function is to define service levels.

Debra Richardson, in her work on vendor onboarding policy design, emphasizes that setting clear SLA timelines for vendor-facing processes, even simple ones like vendor setup requests, creates accountability, sets vendor expectations, and gives the AP team a defensible standard to work toward. The same logic applies directly to inquiry response.

A Tiered SLA Framework for Healthcare AP#

The following framework proposes three service tiers based on inquiry urgency and business impact. It's designed to be realistic for a healthcare AP team of 3-8 reps, not aspirational for a fully automated operation.

Tier 1: Routine Status Inquiries#

Tier 1 covers invoice status, payment date, remittance request, and simple statement confirmations. These are standard inquiries where the vendor needs information and there is no immediate urgency or credit risk.

The SLA target is initial acknowledgment the same business day (within 4 hours if received before 2:00 PM) and full resolution the same business day or the next business day.

This tier is achievable because the majority of vendor inquiries fall into it, roughly 75% based on typical inquiry type distributions in healthcare AP. Routing and prioritization discipline, not staffing increases, is what makes the target hit reliably for most teams.

Tier 2: Discrepancies and Missing Invoices#

Tier 2 covers invoice amount disputes, GPO pricing discrepancies, missing invoices (a vendor sent an invoice with no ERP record), and statement reconciliation requests. Statement reconciliation automation in healthcare is particularly relevant here. A 40-line vendor statement is technically one Tier 2 inquiry but represents 40 individual ERP lookups when handled manually.

These inquiries require investigation, involve potential amount differences, or require cross-referencing between the vendor's records and the ERP. They cannot always be resolved from data immediately at hand.

The SLA target is initial acknowledgment and triage the same business day (within 4 hours), a resolution or status update with an expected resolution date within 48 hours, and full resolution within 5 business days.

Tier 2 inquiries can't always be resolved immediately because they often require input from receiving departments, procurement, or ERP administrators. The SLA commitment is to acknowledge quickly, communicate a timeline, and follow through. Not acknowledging because you can't immediately resolve is the failure mode this tier is designed to prevent.

Tier 3: Credit Hold Threats and Escalations#

Tier 3 covers formal credit hold notices or warnings, direct escalations from vendor management or procurement contacts, and any inquiry where the vendor has indicated supply disruption is imminent. These are high-urgency situations. Delay in response has direct operational and potentially clinical consequences.

The SLA target is an initial response within 1 hour, resolution or escalation to leadership within 24 hours, and immediate notification to procurement and AP leadership upon receipt.

Credit holds in healthcare carry clinical supply chain implications. The 1-hour response target is aggressive but appropriate. It reflects the operational stakes and ensures the escalation cascade described in earlier posts in this series stops before it reaches supply disruption.

Making the SLA Real#

An SLA that exists in a document nobody reads is not an SLA. The following steps are what make a vendor inquiry SLA operational:

Define and document the tiers. Write the framework down (tier definitions, response targets, escalation paths) in a format that can be shared with the AP team and with leadership. The act of writing it forces you to make decisions about what's actually achievable.

Classify inquiry types on receipt. The SLA only functions if inquiries are routed to the right tier at the point they arrive. This can be done manually (a quick read-and-tag when email arrives) or more systematically. The key is that the classification happens immediately, not when someone gets around to it.

Track performance against the SLA. The KPI framework from earlier in this series provides the measurement infrastructure: average response time by inquiry type, backlog age, escalation rate. Add SLA compliance rate (percentage of each tier's inquiries resolved within the target time) as a separate metric.

Communicate the SLA to vendors. Not as a formal commitment that creates legal liability, but as a statement of intent: "Our policy is to respond to routine vendor inquiries within 4 hours of receipt during business hours, and within 1 hour to any inquiry indicating a credit hold risk. If you don't hear from us within those timeframes, please re-flag the inquiry as urgent." This communication sets vendor expectations and reduces the pre-emptive follow-up emails that contribute to backlog.

Review SLA performance monthly. It goes on the AP director's monthly report alongside invoice processing metrics. When SLA performance is visible to leadership, it creates the accountability structure to sustain the discipline. For Tier 2 in particular, statement reconciliation automation in healthcare has the highest impact on SLA compliance. Batch ERP lookups replace the manual line-item-by-line-item process, compressing a 2-hour reconciliation into a 10-minute review. See how statement reconciliation at scale plays out in a healthcare AP team managing high vendor volume.

What to Do This Week#

If the idea of formalizing a vendor inquiry SLA resonates but the implementation feels distant, here is a realistic "week one" plan:

Day 1-2: Pull one week of AP inbox data. Sort by received date and response date. Calculate average response time by inquiry type (status, payment date, dispute, statement). This is your current baseline.

Day 3: Write the tier framework above, adjusted for your specific context. Adjust the time targets based on your baseline. If your current average is 18 hours, a same-day target may be realistic. If it's 4 days, start with a 48-hour target and tighten over time.

Day 4: Share the framework with the AP team. Get their input on whether the targets are achievable with current resources. The conversation this generates is as valuable as the framework itself. The team will tell you where the workflow breaks down.

Day 5: Share the draft framework with the AP director or VP of Finance. Frame it as: "here's what we currently deliver, here's the standard I'm proposing, and here's what I need to hit it reliably." That conversation is the one that creates organizational alignment and, where needed, resource justification.

An SLA for vendor inquiry response is not bureaucracy. It's the operational discipline that moves inquiry management from a reactive, variable-quality service to a consistent, accountable function. Healthcare organizations apply SLA thinking everywhere the stakes demand consistency. The vendor inquiry function has earned the same treatment.

The SLA framework above sets the standard. Statement reconciliation automation in healthcare and vendor inquiry automation are what make hitting that standard achievable without burning out your team. The features page outlines how Auxtri automates the ERP lookup cycle that makes same-day Tier 1 response feasible at volume, and reduces Tier 2 statement reconciliation from hours to minutes.