AP Cycle Time

In one sentence: AP cycle time is the number of days between when a vendor invoice is received and when payment is issued, measuring the end-to-end efficiency of the accounts payable process.

What Is AP Cycle Time?

AP cycle time tracks how long an invoice takes to travel through the entire payable workflow: receipt, data entry, validation, matching, approval, and payment execution. It is measured in calendar days and is one of the core performance metrics for any AP function.

A shorter cycle time means vendors get paid faster, discounts are captured, and the finance team has better control over cash flow timing. A longer cycle time signals bottlenecks that are costing the company money and damaging vendor relationships.

Why It Matters

AP cycle time has direct financial and operational consequences:

• Early payment discounts: Many vendors offer 1-2% discounts for payment within 10 days (Net 10). If your cycle time is 25+ days, you never capture these discounts.
• Late payment fees: Exceeding vendor payment terms triggers late fees and damages your reputation as a reliable customer.
• Vendor relationship quality: Vendors who get paid predictably offer better terms, prioritize your orders, and are more flexible during disputes.
• Cash flow predictability: Knowing your average cycle time allows treasury to forecast cash outflows accurately.
• Team performance visibility: Cycle time reveals where the process is stuck, whether it's data entry, approval delays, or payment batching.

How It Works

AP cycle time is calculated as:

Cycle time = Payment date - Invoice receipt date

Most teams track cycle time as an average across all invoices, then break it down by segment:

• By vendor: Which suppliers experience the longest payment delays?
• By amount: Do high-value invoices take longer due to additional approval layers?
• By exception status: How much longer do exception invoices take compared to touchless invoices?
• By department: Which cost centers create approval bottlenecks?

The breakdown reveals where to focus improvement efforts.

Common Problems

• Approval delays dominate cycle time. In most organizations, the invoice sits waiting for approval longer than any other stage. Approvers are busy, emails get buried, and there's no urgency mechanism.
• Batch payment schedules add padding. Companies that run payment batches weekly or biweekly add up to 14 days of unnecessary delay to every invoice.
• No visibility into where invoices are stuck. Without real-time status tracking, the AP team discovers bottlenecks only when a vendor calls to ask where their payment is.
• Exception handling is unmeasured. Teams track total cycle time but don't separate exception resolution time from normal processing time. This hides the true cost of exceptions.

FAQ

What is a good AP cycle time?

Industry benchmarks for mid-market companies range from 10-15 days for automated environments and 25-35 days for manual processes. Best-in-class AP functions achieve under 7 days on average. The target depends on your vendor payment terms: if most vendors are Net 30, a 10-day cycle time gives you 20 days of float.

How does AP automation affect cycle time?

Automation reduces cycle time by compressing or eliminating the slowest stages: data entry (from hours to seconds), matching (from manual review to automatic), and approval routing (from email chains to mobile push notifications). Companies implementing AP automation typically see cycle time drop by 40-60%.

Should cycle time be measured for all invoices or just touchless ones?

Both. Tracking overall cycle time shows the aggregate performance. Tracking touchless vs. exception cycle time separately reveals how much exceptions are dragging down the average and where to focus improvement. If touchless invoices process in 3 days but exception invoices take 18 days, the priority is clear.