AP Aging 60+ Days, Sage

AP Aging 60+ Days shows the share of your accounts payable balance aged 60 or more days past invoice date, the early signal of strained supplier relationships, missed early-pay discounts, or a developing cash crunch. How to read it, why it matters, and how to act on it.

Metrics type: Supporting Metrics • Category: Ecommerce Platform

Share of accounts payable balance aged 60+ days. High share signals strained supplier relationships, missed early-pay discounts, or a cash crunch.

At a glance

The percentage of your total open accounts payable balance that has aged 60 or more days past invoice date. This is the supplier-side mirror of AR aging: a high and rising share means you are paying suppliers late, which quietly erodes goodwill, forfeits early-payment discounts, and can flip a Net-30 vendor onto stop-supply or cash-on-delivery terms right when you need stock. The card reads the AP sub-ledger by aging bucket and surfaces the 60+ slice as a single governable number, dimension-tagged in Sage Intacct so finance can pivot the late cohort by Vendor, Department, Location, or Entity and route each conversation to the right owner.

What it counts	The 60+ day aged portion of open AP, expressed as a percentage of total open AP. The card reads the AP sub-ledger (open Bills, Bill Lines, and applied payments) and ages each open balance against its invoice or due date per the aging policy, then divides the 60+ bucket by the total open AP balance.
Aging basis	Invoice date by default. Configurable per workspace to age from due date instead, which is the more forgiving view because it credits the agreed payment term (Net-30, Net-60) before counting a Bill as late.
Bucket definition	60+ means the 61-90, 91-120, and 120+ buckets combined. The card respects the bucket boundaries set in the Intacct AP aging configuration.
Credits and debit memos	Vendor credit memos and debit memos net against the open balance in their respective buckets, so a large unappplied credit can pull the percentage down without any cash actually moving.
Currency	Multi-Entity Console: each entity’s AP aged in base currency, the percentage computed per entity and at the consolidated level in reporting currency at the configured FX cadence.
Entity scope	Card respects the dashboard entity filter.
Dimensional cut	Each aged dollar carries Intacct dimensions through. Pivot by Vendor to see which suppliers you are slow-paying, by Location to see which site’s AP team is behind, by Department to see which cost centre is sitting on unapproved invoices.
Time window	30D vs prior
Alert trigger	>30% of AP in the 60+ bucket, sentiment ap_aging. Configurable per workspace. A healthy mid-market operation typically runs single digits to low teens; sustained readings above 30% usually mean a cash problem, an approval bottleneck, or both.
Roles	owner, finance

Calculation

Calculated automatically from your Sage data. The card divides the AP sub-ledger balance in the 60+ aging buckets by the total open AP balance and expresses it as a percentage. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.

Worked example

A UK-based homewares brand on Sage Intacct, single entity, GBP base currency, roughly 12M GBP annual revenue selling through Shopify Plus DTC and a BigCommerce B2B wholesale channel. Most inbound stock is bought on Net-30 and Net-60 terms from a mix of UK and EU suppliers. Snapshot 14 Apr 26. Aging basis set to invoice date. Total open AP on the day is 1,840,000 GBP.

Aging bucket	Open AP (GBP)	Share of total AP
0-30 days	1,012,000	55%
31-60 days	386,000	21%
61-90 days	258,000	14%
91-120 days	110,000	6%
120+ days	74,000	4%
AP Aging 60+ Days (this card)	442,000	24%

Five things to notice:

1. 24% sits below the 30% alert line but the direction is what matters, not the absolute level on the day. The card reads 30D vs prior, and on this account the 60+ share moved from 16% a month ago to 24% now, an 8-point jump that is the real signal. A static 24% on a business that always runs 24% is a stable (if slightly uncomfortable) baseline; an 8-point climb in a single month is a developing cash or approval problem that has not yet tripped the alert but will if it continues. The value of the card is that finance sees the trend a month before it becomes a stop-supply phone call from a key vendor.
2. The 91-120 and 120+ buckets (184,000 GBP combined) are where supplier relationships actually break. A Bill that has slipped past 90 days is no longer a timing artefact, it is a Bill someone forgot, disputed and never resolved, or deliberately stretched because cash was tight. Pivot the 60+ cohort by Vendor and the 120+ slice almost always concentrates in two or three suppliers. On this account it was a single EU packaging supplier (62,000 GBP across four Bills) where an early dispute over a damaged pallet was never closed, so AP held every subsequent Bill. The Vendor dimension cut surfaced it in one click; without the card it would have surfaced as a stop-supply notice.
3. Aging basis materially changes the headline. This account ages from invoice date, which is the strict view. Switching to due-date aging would credit the Net-30 and Net-60 terms first and pull the 60+ share down by roughly a third on this mix, because a Net-60 Bill is not actually late until 60 days after invoice. Neither is wrong, but finance and the auditor need to agree which lens the board pack uses. The card respects whichever is set in the field map; the worked number here is on the strict invoice-date basis.
4. A rising 60+ share is the leading indicator of forfeited early-pay discounts. Many of this brand’s suppliers offer 2/10 Net-30 (2% off if paid within 10 days). Every Bill that drifts into the 60+ bucket is, by definition, a discount already forfeited. At 442,000 GBP of late AP, even a modest blended 1.5% discount opportunity is roughly 6,600 GBP of margin left on the table per cycle if those Bills could have been paid on time. Pair this card with Vendor Payment On-Time Rate to quantify the discount leakage directly.
5. Cross-reference cash before assuming it is an approval bottleneck. A high 60+ AP share has two very different root causes: you do not have the cash, or you have the cash but invoices are stuck in approval. Read this card next to Days Since Last Bank Reconciliation and your live cash position. On this account the bank balance was healthy, which pointed the diagnosis squarely at approval workflow: 70% of the 60+ Bills were sitting unapproved in a single Department whose budget holder had been on leave. That is a process fix (delegate approval authority), not a financing problem, and the card made the distinction visible.

Sibling cards merchants should reference together

Card	Why pair it with AP Aging 60+ Days
Vendor Payment On-Time Rate	The behavioural twin: aging shows the backlog, on-time rate shows whether you are still falling behind.
Active Vendors	The denominator context. Concentration of late AP in a few of many active vendors is a relationship risk.
Days Since Last Bank Reconciliation	Separates a cash problem from an approval problem when AP aging spikes.
AR Balance (live)	The other side of working capital. Late AP plus high AR means cash is trapped in receivables.
AR Aging 60+ Days	The receivables mirror. Stretched AR often forces stretched AP.
Open & Pending Transactions	Unposted Bills inflate or deflate the aged population until they clear.
Sage Health Score	The roll-up. AP aging is one of the working-capital inputs to the composite.

Reconciling against Sage

Where to look in Sage:

The native Sage Intacct views to run side by side with this card:

Reports → Accounts Payable → AP Aging Report (the canonical aged-payables breakdown by bucket, run as of the snapshot date) Reports → Accounts Payable → AP Aging Detail (line-level Bills behind each bucket, for chasing the specific late invoices) Reports → Accounts Payable → Vendor Aging (the same aging pivoted by Vendor, which is the cohort this card lets you drill into) Reports → Accounts Payable → AP Ledger (the underlying open-Bill and applied-payment detail) Interactive Custom Report (ICR) built on the AP data source, aging open Bills into buckets and computing the 60+ slice as a percentage of total open AP, pivoted by Vendor and Department dimensions

The AP Aging Report defaults to aging from invoice date in most Intacct configurations; confirm whether your board pack uses invoice-date or due-date aging, because the two produce materially different 60+ percentages on a portfolio with long terms. For Multi-Entity Console accounts, run Reports → Accounts Payable → AP Aging by Entity at the same scope as the dashboard filter so FX does not shift the GBP value of EU-entity payables between report runs.

Common reconciliation pitfalls:

• Aging “as of” date. The AP Aging Report ages as of the date you run it. If you run it at month-end and compare to the card snapshotted at 14 Apr, the populations will differ purely on the date. Match the as-of date first.
• Unapproved or unposted Bills. Bills entered but not yet posted may or may not appear in the aging depending on the report’s posted-status filter. The card’s behaviour is set in the field map; align the report filter to match.
• Applied vs unapplied payments. A payment entered but not yet applied to a specific Bill reduces the vendor balance but may leave the Bill showing open in detail views. This can make the card and a detail report disagree until application completes.

Why our number may legitimately differ from a Sage Intacct AP Aging Report:

Reason	Direction	Why
Aging basis	Either	Invoice-date vs due-date aging. Card defaults to invoice date (strict); due-date aging credits Net-30 and Net-60 terms first and reads lower.
As-of date	Either	Card snapshots at the dashboard date; a report run at month-end ages a different population.
Posted-status filter	Either	Whether draft and unposted Bills are included. Card setting lives in the field map.
Credit memo netting	Card may understate	Unapplied vendor credits net against the open balance, pulling the 60+ percentage down without any cash movement.
Disputed Bills on hold	Card may overstate	A Bill flagged on-hold pending dispute still ages; some board packs exclude disputed Bills from the late count.
Recurring Bill schedules	Either	Future-dated recurring Bills generated early can appear in the 0-30 bucket and shift the denominator.
FX cadence per entity	Small	Multi-Entity Console: card uses current-day FX, Intacct reports may use period-end. Differences usually under 2%.
Prepayments and deposits	Card may understate	Vendor prepayments sitting as debit balances can net the total AP down depending on configuration.

Cross-connector reconciliation:

Card	Expected relationship	What the comparison reveals
Vendor Payment On-Time Rate	Inverse correlation	A falling on-time rate precedes a rising 60+ aging share by roughly one payment cycle. Watch them together.
AR Balance (live)	Working-capital pair	High AP aging alongside high AR means cash is trapped downstream; the fix is collections, not just AP scheduling.
Days Since Last Bank Reconciliation	Diagnostic	An unreconciled bank means you may not actually know your cash position, which makes any AP-stretch decision blind.
Sage Health Score	Component	AP aging feeds the working-capital component of the composite health score.
Active Vendors	Concentration	Late AP concentrated in a small share of active vendors is a sharper relationship risk than the same total spread thin.

The cross-connector value is that commerce platforms see none of this. Shopify and BigCommerce know what you sold, not what you owe your suppliers. Sage Intacct is the only system that can tell you a key packaging vendor is three Bills and 90 days from putting you on stop-supply, and the dimensional carry-through means the Vendor owning the late cohort is one click away. This is the early-warning conversation that keeps stock flowing.

Known limitations / merchant FAQs

Should I age from invoice date or due date? Both are valid and the choice changes the headline materially. Invoice-date aging is the strict, conservative view and is what auditors and lenders usually expect. Due-date aging is the operational view because it credits the agreed term: a Net-60 Bill is not genuinely late until 60 days after invoice. Pick one, set it in the field map, and make sure the board pack and the bank covenant calculations use the same basis. Mixing the two between documents is the single most common cause of “the numbers do not match” arguments.

What is a healthy 60+ AP share? There is no universal number, but a well-run mid-market operation typically keeps the 60+ bucket in the single digits to low teens as a percentage of total AP. Sustained readings above 30% almost always mean one of three things: a real cash shortage, an approval bottleneck, or a vendor dispute that is being managed by simply not paying. The card does not tell you which; pair it with your cash position and the Vendor dimension cut to diagnose.

Does a high AP aging share actually hurt me? Yes, in three measurable ways. You forfeit early-payment discounts (often 1-2% of invoice value), you risk suppliers tightening terms from Net-30 to cash-on-delivery or stop-supply just when you need stock, and you signal financial stress to any vendor who runs a credit check on you. The relationship damage is the part that does not show up in the numbers until a key supplier declines your next purchase order.

Sage Intacct vs Sage 50 / 100 / 200 / X3? This connector targets Sage Intacct. The AP aging concept exists in all Sage products, but the sub-ledger structure, aging configuration, and reconciliation paths differ. Sage 50 and 200 are UK SMB products with their own AP aging reports; Sage X3 is a different mid-market ERP. The arithmetic is conceptually identical but the field map and API differ. If you run one of those, reach out about connector availability.

How do vendor credit memos affect the number? Unapplied vendor credits net against the open AP balance in their bucket. A large credit (a returned shipment, a negotiated rebate) can pull the 60+ percentage down without any cash actually moving, which can mask a real aging problem. If you want the gross view, the field map can exclude credit memos from the netting so you see the true late-Bill exposure separately.

Why did the percentage jump when total AP barely changed? Because the card is a ratio. If a large 0-30 Bill is paid (shrinking the denominator) while the older Bills sit untouched, the 60+ share rises even though your absolute late exposure did not. Always read the percentage alongside the absolute 60+ value, which the card also exposes, so you can tell a denominator effect from a genuine aging deterioration.

Does this card include unapproved invoices stuck in workflow? It depends on the posted-status setting in your field map. Many approval bottlenecks live in unposted Bills that have not hit the AP ledger yet, so a card configured to count only posted Bills can understate the true backlog. If your aging problem is suspected to be an approval problem, set the card to include unposted Bills and pivot by Department to find where they are stuck.

Multi-currency: does FX move this card? The percentage is fairly FX-stable because both numerator and denominator move together, but the consolidated absolute values shift with daily FX on Multi-Entity Console accounts. A GBP-EUR move changes the reporting-currency value of EU-entity payables but rarely changes the 60+ percentage by more than a point or two. Read the per-entity cut if a consolidated swing looks alarming.

How fresh is the data? The card refreshes on the standard data cadence, typically within 5 to 15 minutes of the most recent posted AP activity in Intacct. Payment runs (Bacs files) that have been generated but not yet posted will not reduce the aged balance until they post, so the card can briefly read high on the morning of a large payment run.

How does this relate to a Bacs payment run? A Bacs run is how UK businesses settle the late Bills this card surfaces. The practical workflow is: read the 60+ cohort, pivot by Vendor, select the Bills that protect supply or capture remaining discounts, and include them in the next Bacs file. After the run posts, the card should step down. If it does not, the run did not actually clear the aged Bills, which usually means a payment-application gap worth investigating.

---

Tracked live in Vortex IQ Nerve Centre

AP Aging 60+ Days is one of hundreds of KPI pulses Vortex IQ tracks across Sage and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.