# Outstanding Invoices In AP And How Controllers Manage Them Outstanding invoices distort AP aging and slow the close when left untracked. Here's how controllers separate overdue invoices from routine ones. **URL Source:** https://www.brex.com/spend-trends/cash-flow-management/outstanding-invoice --- Outstanding invoices in AP: How controllers manage the backlog ### Key takeaways - In AP, the terms “outstanding,” “overdue,” and “past due” aren’t interchangeable. Treating them the same can make it hard to tell which invoices are normal and which are a problem. - An unmanaged backlog may distort your close, weaken your cash flow forecast, and potentially increase fraud risk, especially on lean teams. - A repeatable workflow can help prevent invoice backlogs from rebuilding. Ownership and structure upstream beat firefighting at close. ### Introduction Most controllers can pull up their AP aging report in a few clicks. Fewer can say, with confidence, which of those open invoices are simply moving through the normal approval queue and which ones have quietly stalled for three weeks because nobody claimed them. On a lean team, that gap tends to surface at the worst possible time, usually a day or two before close, when a vendor calls asking why a bill from last month is still unpaid. In accounts payable, the terms outstanding, overdue, and past due describe different points on the same timeline, but teams often use them interchangeably in conversation. That habit makes it hard to tell the CFO which invoices are on track and which ones need attention, and it's usually the first thing that breaks down once invoice volume outgrows a two- or three-person AP team. A term used loosely in a Slack message costs nothing, but the same looseness inside an aging report is what turns a routine backlog into a credibility problem at close. Systematic tracking fixes that. It gives the CFO a liability view they can trust, turns the close cycle into a structured sign-off instead of a scramble, and grounds the cash flow forecast in real due dates rather than guesswork. When the AP subledger doesn't tell the truth, every number that rolls up from it inherits the same uncertainty. Most advice on outstanding invoices is written for the other side of the desk, the vendor trying to get paid. Controllers face the receiver-side version, vendor bills that have arrived but haven't cleared the AP workflow yet. That's manageable with a large AP team and a clean system. It gets harder when two or three people are tracking invoice status by email while the business keeps adding vendors and volume. An outstanding invoice you owe is a liability that has to be scheduled and managed through the [accounts payable process](https://www.brex.com/spend-trends/cash-flow-management/accounts-payable-process). Controllers need clean intake, reason-coded ownership, due-date triage, and structural controls, along with [accounts payable metrics](https://www.brex.com/spend-trends/accounting/accounts-payable-metrics) that show whether the backlog is actually shrinking over time. That discipline supports cash flow management, because open bills only work as forecast inputs when their due dates and workflow status are reliable. ### What is an outstanding invoice in accounts payable? An outstanding invoice is a vendor bill that the company has received but has not yet processed and paid. It sits in the AP subledger, the detailed AP record that supports the general ledger, as an open obligation. Accounting teams classify the invoice as a current liability on the balance sheet until it clears the AP workflow through capture, coding, matching, approval, scheduling, and payment. Under the [expense recognition principle](https://www.brex.com/spend-trends/accounting/expense-recognition-principle), companies commonly record the obligation at the invoice date as a credit to the AP account. That entry happens before cash leaves the business, though specific treatment depends on the company's accounting policies and applicable standards. The same unpaid invoice is treated differently on the balance sheet depending on who holds it. From the vendor's perspective, it's an accounts receivable asset, money owed to them. From your perspective as the controller, it's an accounts payable liability, money the company owes. Same document, two mirror-image entries on two different balance sheets. An invoice can be outstanding at several stages of the AP workflow, and each stage presents distinct management challenges. Knowing the state of each open invoice determines who owns it. That status also indicates to AP which action clears the item. ### Outstanding invoice vs. overdue invoice vs. past due The three terms describe different points in an invoice's life, and conflating them hides how much of your AP aging is routine versus at risk. The labels also determine whether AP should schedule payment or escalate a bottleneck. A clean distinction here gives the CFO a clearer read on which open bills are expected and which need intervention. An outstanding invoice has been received and is open in AP, but hasn't passed its payment due date. The obligation exists, payment isn't late, and the invoice is still inside the normal approval or scheduling queue. An overdue invoice has passed its due date, and payment hasn't been made. What was outstanding has become late. Overdue invoices call for action to manage late fees and protect vendor relationships. Past due is often used interchangeably with overdue once Net 30, Net 45, or Net 60 terms expire. These items usually require escalation or a dispute review rather than routine scheduling, and the review should focus on why the payment hasn't cleared. Here’s how the three terms compare side by side: The distinction matters because outstanding and overdue states call for different responses. When the two live in the same bucket, you can't tell the CFO how much of the balance is on track versus stuck. The AP aging report typically surfaces this distinction by grouping open vendor bills into time buckets: - Current within terms - 1 to 30 days past due - 31 to 60 days past due - 61 to 90 days past due - More than 90 days past due An outstanding invoice that hasn't passed its due date sits in the current period. Once it passes the due date, it moves into the 1 to 30 bucket, and later ones if it continues to age. That makes [accounts payable reporting](https://www.brex.com/spend-trends/accounting/accounts-payable-reporting) a management tool, because different buckets should trigger different decisions. ### Why outstanding invoices pile up in AP and what it costs The root causes below end in consequences that land on your desk, from missed discount windows to a closed cycle that runs long. Each cause changes the action AP should take next. Treating them as one backlog makes the aging report harder to trust. Approval bottlenecks keep invoices stuck before they're approved for payment An approval bottleneck is any point where an invoice sits waiting on manager or budget-owner sign-off instead of moving through the AP workflow. Invoices entered but waiting on approval are outstanding and often unavailable for payment runs until someone approves them, because validated invoices move to payment while the AP workflow holds exceptions for review. Chronic slow approvers, unclear approval matrices, and email-based routing create backlogs. A backlog of this kind can leave a meaningful share of AP volume in a perpetual pending state. When this happens, AP teams can't schedule payment or forecast cash outflows confidently. You also risk missing discount windows or incurring late fees on invoices approved in principle weeks ago. Approval aging becomes a working-capital issue when the payment team can't tell which invoices are ready to move. Invoice matching exceptions create holds with no owner An invoice matching exception happens when a vendor bill doesn’t line up with its purchase order or goods receipt, and gets routed into a separate queue instead of moving through approval. [Invoice matching](https://www.brex.com/spend-trends/accounting/invoice-matching) failures against the [purchase order](https://www.brex.com/spend-trends/procurement/purchase-order) or goods receipt route invoices into an exception queue. Price variances, quantity mismatches, and missing documentation are common causes. Without a clear owner and a service-level agreement (SLA), they can age without visibility. An SLA defines a resolution timeline and keeps exception work from falling off anyone's priority list. Invoice exceptions are a major operational challenge for AP teams. According to [Ardent Partners’ State of ePayables 2025 report](https://d15fjz85703yz4.cloudfront.net/1517/5157/1685/Ardent_Partners_-_State_of_ePayables_2025_-_Bottomline_-_FINAL.pdf), 48% of AP professionals cite a high rate of exceptions as a top challenge, second only to slow approval times. Best-in-class AP teams average an 11.1% exception rate, nearly half that of their peers at 20.9%, which shows how much SLAs and clear ownership close that gap.. Unresolved exceptions distort your aging, delay accruals, and surface as last-minute firefighting during close. Invoices never enter the AP platform because intake is broken Whether invoices are emailed to department managers, mailed to a physical address, or submitted through a vendor portal, no one can monitor outstanding liabilities that the AP platform doesn't know exist. Manually entering invoice data is still the norm at many companies, which leaves room for invoices to slip through side channels unnoticed. Invoices that bypass the intake platform may surface at month-end close in AP or when a vendor calls to chase payment. This can result in an understated AP balance at month-end. Close teams then have to handle unexpected payables, and the risk of duplicate payments can rise when the same invoice arrives through a second channel. Closing the intake gap with [paperless accounts payable](https://www.brex.com/spend-trends/accounting/paperless-accounts-payable) can reduce a common source of invisible liabilities. Deliberate holds get mixed in with unmanaged delays AP teams sometimes hold invoices on purpose to manage cash timing. That might mean stretching terms with non-critical vendors or deferring a large payment pending contract resolution, which make these deliberate choices rather than processing failures. When intentional holds and unmanaged delays live in the same outstanding bucket, the AP aging report becomes unreadable. Close-time decisions then turn into guesswork. Because of this, you can't confidently tell the CFO how much of the outstanding balance is tactical and how much is due to process failure. Intentional holds can work, but only when they're visible, owned, and reviewed. Without that separation, the aging report stops working as a management tool. ### How outstanding invoices affect AP aging, close, and cash flow The operational effects of outstanding invoices reach far past AP. An invoice population with missing entries, unresolved exceptions, and untagged holds distorts the aging report, forces unscheduled close decisions, leaves cash forecasts reflecting only the invoices AP has already processed, and raises fraud and duplicate-payment exposure, especially on lean teams without full separation of duties. Each one becomes a problem that the controller has to explain to the CFO. Unmanaged outstanding invoices distort aging buckets and create subledger-to-GL variances The AP aging report reflects whatever is in it, including invoices that were never entered, miscoded items assigned to the wrong vendor or period, and stale holds that no one owns. Each distorts a different bucket. Missing invoices understate the liability. The miscoded invoices misroute it. Stale holds inflate the current or overdue buckets without a path to resolution. When the aging doesn't match the general ledger (GL) control account, you face a subledger-to-GL reconciliation problem at close. When variances arise, [invoice reconciliation](https://www.brex.com/spend-trends/cash-flow-management/invoice-reconciliation) serves as the bridge between the aging report and the GL. That bridge is harder to build when the underlying invoice population is incomplete. Outstanding invoices without reason codes turn the financial close process into reactive, unscheduled triage The [financial close process](https://www.brex.com/spend-trends/accounting/financial-close-process) requires the AP and accounting teams to evaluate every open invoice in accordance with company policy and applicable standards. Each invoice gets paid, accrued, disputed, or flagged for write-off review. When invoices arrive at close without owners or reason codes, that evaluation can't be scheduled in advance. Each open item becomes a decision to be made under time pressure by whoever is available, without the context of why the invoice remains open. Invoice error resolution times vary widely by team. Teams with clear ownership and SLAs can resolve exceptions in days, while those without them can take a week or more for the same. Goods received, or services incurred but not yet invoiced at month-end may require AP accruals, depending on the company's accounting policies and applicable standards. Close accuracy depends on AP decisions made before period-end, not during it. Untracked outstanding payables make the 30/60/90-day cash flow forecast unreliable Most outstanding invoices represent future cash outflows with known amounts and usually known due dates. When those due dates and workflow statuses aren't tracked, they can't feed the forecast. The CFO gets a cash position built on incomplete data, and the 30-, 60-, and 90-day forward view reflects only the invoices AP has fully processed. Invoices still moving through the workflow don't make it in. Static AP aging exports compound the problem because they show aging without workflow context. Accurate AP due-date visibility also supports days payable outstanding (DPO) optimization. DPO is the average number of days a company takes to pay suppliers. Extending payment terms to preserve working capital without damaging vendor relationships generally works best when the outstanding-invoice population is accurately tracked. Without that population, the DPO calculation reflects history rather than current obligation. Unmanaged backlogs raise fraud and duplicate-payment risk on lean teams When outstanding invoices don’t have a clear owner, no one is positioned to catch a duplicate payment or fake vendor before it clears. That risk grows as the backlog does, especially for lean teams where one or two people handle vendor setup, invoice entry, and payment release without a second set of eyes. Fraud and duplicate payments can slip through AP workflow controls when the same person is responsible for entering, approving, and paying the invoice. Avoid these mistakes by implementing a rule that no one person owns an invoice from start to finish. Without this separation, you won’t be able to tell your CFO the backlog is safe. ### How controllers manage outstanding invoices A reliable outstanding-invoice workflow moves from intake through classification, triage, payment, and automation. Each step is a control point that keeps the next one from breaking down, and skipping one tends to mean the backlog just resurfaces later, usually at close or on a vendor's overdue-payment call. None of these habits require new headcount on their own; most controllers layer them onto the team and tools already in place. Centralized intake keeps invoices from entering AP outside the platform A reliable outstanding-invoice workflow starts with where bills land. Controllers running a tight AP process typically route every vendor invoice through one channel, a dedicated AP email, a vendor portal, or a platform that captures bills the moment they arrive, rather than letting invoices land in department managers' personal inboxes or a paper tray. That single-channel habit works because it turns the AP platform into the actual source of truth for what the company owes, instead of a partial record AP has to reconstruct at month-end. Teams that track how quickly a received invoice reaches the platform, often through an internal service-level target, tend to catch backlogs while they are still small, rather than after a vendor calls about a missing payment. Reason-coded classification gives every open invoice an owner Once invoices are centralized, the strongest AP teams tag each tracked outstanding item with the reason it hasn't cleared, whether that's a pending approval, an invoice-matching exception, missing vendor data, a cash-flow hold, or a dispute. That single tag does a lot of work. It routes the item to the right owner, whether that's a department head approving spend, an AP or procurement staffer resolving a matching exception, or whoever manages vendor onboarding, and at a growing company one person often wears several of these hats. The reason code still matters even then, because it sets the resolution clock and surfaces patterns. When a large share of outstanding items keeps landing in the same awaiting-approval bucket, the workflow itself is usually the problem. No single invoice is really at fault. Teams that skip this tagging step tend to find that intentional holds and simple oversights end up looking identical on the aging report, which is exactly the ambiguity a reason code is meant to remove. A weekly AP triage catches invoices before they age into problems Many controllers build a short, recurring review into the calendar rather than relying on the aging report to flag problems on its own. That session usually prioritizes invoices approaching their due date, large or strategic vendor bills, anything sitting past a team-defined threshold without a logged reason, and items more than 30 days past due. The output tends to be a short action list with an owner and a resolution date attached to each line. Items that keep reappearing week after week without resolution are the ones controllers escalate to finance leadership, since a recurring miss usually points to a process gap rather than a one-off. This weekly cadence is what turns the AP aging report from a static export into something closer to an operating rhythm. Without it, the same handful of invoices tends to quietly resurface every month. Payment runs that follow the outstanding-invoice triage cycle Payment runs tend to work best when they draw directly from that triage cycle instead of running on a separate schedule. Invoices that have cleared approval and any matching exceptions move into the run, while invoices with an unresolved hold stay out, with the reason already logged so nothing ages invisibly past its due date. Controllers managing 2/10 net 30 terms or similar arrangements typically flag those invoices for priority routing, since the approval cycle has to close within the discount window for the discount to matter at all. Even after accounting for the coordination it takes, an early-payment discount captured across a meaningful share of AP spend is often worth pursuing, which is one reason treasury and AP teams increasingly plan payment timing together instead of separately. Whether a payment settles by ACH, [virtual card](https://www.brex.com/spend-trends/corporate-credit-cards/virtual-business-credit-card), or check, the method still needs to match the vendor's terms and the team's reconciliation setup, so the run supports both working capital and a clean close. Getting that alignment right once tends to save renegotiating it invoice by invoice later. AP automation that makes outstanding-invoice status visible in real time Instead of exporting the aging report and manually cross-referencing it against email threads, many AP teams now lean on automation to keep outstanding-invoice status current by default. Brex customers can capture vendor bills through email forwarding and route them through policy-based approval workflows using Brex bill pay, then sync bill pay data with QuickBooks, NetSuite, Xero, or Sage Intacct to see outstanding invoices by status, aging bucket, and due date in one place. The manual version of that workflow, toggling between a spreadsheet export and an email inbox, is exactly what this kind of automation replaces. Routing rules and escalation reminders help keep invoices from stalling in an inbox, which is what shifts bill pay from another export cycle into a status-driven workflow. That real-time view is also what makes the earlier habits, reason coding, weekly triage, and discount-window payment timing, sustainable instead of something a team does once and lets slip. A workflow that depends on someone remembering to check a report tends to work for a month and then quietly stop. ### How to prevent outstanding invoices from accumulating Clearing a backlog once doesn't make it stay clear. Each of the root causes described earlier tends to rebuild unless it gets a structural fix, and addressing them upstream is what keeps exceptions from compounding into close-week firefighting. The four habits below target intake, approval, vendor data, and cash-timing decisions specifically, since those are where most preventable backlogs actually start. POs on material spend categories make matching mechanical A lot of AP exceptions trace back to a missing purchase order or goods receipt rather than anything wrong with the invoice itself. In companies where procurement issues a PO and operations confirms receipt before the invoice arrives, matching becomes close to automatic instead of a manual investigation, and automated tools can compare each invoice against its open PO directly. Categories that skip PO issuance entirely, often smaller or recurring purchases, tend to be where these exceptions concentrate. Finance teams that want to know whether this is actually working tend to track two numbers. The straight-through processing rate is the share of clean invoices that move through AP without anyone touching them, and the [purchase order](https://www.brex.com/spend-trends/procurement/purchase-order) coverage rate is the share of invoices tied to a PO in the first place. A low PO coverage rate usually points to specific spend categories skipping the process entirely, which is a more useful thing to fix than trying to catch every resulting exception by hand. Approvals inside the AP platform replace email-based sign-off Email approvals are a common source of outstanding-invoice backlogs, mostly because nobody outside the thread can see where an invoice actually stands. When approvals live inside the AP or spend platform instead, every invoice has a visible owner from the moment it enters the workflow, and routing rules based on amount, department, or vendor replace the judgment call of who to email next. Automated reminders take on the chasing that would otherwise fall to an AP staffer's calendar. Controllers who have made this shift often find that a month of approval-latency data is more persuasive with department heads than a policy memo ever was, since it shows exactly where invoices stall and which approvers need a nudge. That keeps the conversation focused on process rather than becoming personal. A specific number tied to a specific approver is harder to wave off than a general complaint about slow sign-offs. Vendor onboarding completed before the first invoice arrives Invoices frequently get held not because anything is wrong with them but because the vendor record behind them is incomplete, missing a bank detail, an unfiled W-9, or a duplicate vendor entry. Companies that standardize onboarding with a short checklist, bank details, tax ID, preferred payment method, and payment terms, confirmed before the first PO goes out, tend to see far fewer of these holds later. A vendor record fixed once at onboarding avoids the same fix being repeated on every invoice that vendor sends afterward. Tracking vendor master file accuracy over time also catches drift before it becomes a compliance-related stall in the aging report. Clean vendor records at the front end are what keep an otherwise valid invoice from turning into a preventable exception, which matters more as vendor count grows faster than AP headcount. A vendor list that nobody audits tends to accumulate the same handful of errors that eventually stall a real payment. Intentional holds tracked separately from process failures Not every outstanding invoice on the books is a problem. A vendor dispute might genuinely need resolution first, or a payment might be deliberately deferred to manage cash around quarter-end. Controllers who separate these deliberate holds from unmanaged delays, tagging each with a reason code, an owner, and a review date, keep the aging report readable as a management tool rather than a mix of signal and noise. Reporting intentional holds separately in CFO and board AP summaries also means the backlog number itself tells a clearer story, since it no longer blends tactical decisions with genuine process failures. ### How ONEflight International clears its outstanding invoice queue in minutes instead of hours [ONEflight International's finance team](https://www.brex.com/resources/customer/oneflight-international) once spent two to three hours a day manually setting up each outstanding wire payment to aircraft operators, one at a time, before invoices could clear. Flight coordinators now email invoices directly to Brex, which captures the details through OCR and flags duplicate submissions automatically, catching cases where a coordinator sends both a quote and an invoice for the same charter. The controller reviews the populated bills in minutes, and the CFO clears the whole batch with a single bulk approval instead of opening each invoice individually. ### Turn outstanding invoice management into a competitive AP advantage Outstanding invoices are part of AP, and they become manageable when they have reason codes, owners, and aging visibility. With these structures, they become a more reliable input to cash flow forecasting. They also support working capital management and steadier vendor relationships, since vendors notice when payment is on time and predictable. The controller's job is to assign each open bill to an owner and log a reason before the due date passes. Start with intake discipline and a weekly triage cadence. Then use classification, service-level agreements, routing logic, and escalation reminders to keep approval bottlenecks from rebuilding. Tighten your end-to-end workflow with [accounts payable management](https://www.brex.com/spend-trends/accounting/accounts-payable-management) as the next step, and pair it with the [accounts payable best practices](https://www.brex.com/spend-trends/accounting/accounts-payable-best-practices) that keep the workflow itself audit-ready. Building this infrastructure from scratch takes resources a growing company often doesn't have to spare, which is where a platform like Brex tends to close the gap. Brex customers can capture invoices with AI-powered OCR, route them through policy-based approval workflows, and sync bill pay to QuickBooks, NetSuite, Xero, and Sage Intacct for enterprise resource planning coverage. Pairing that with a [Brex business account](https://www.brex.com/product/business-account) gives Brex customers a fast way to fund payments, since funds move without a separate bank connection in between. _Created with AI assistance and reviewed by Brex. This article reflects Brex's perspective at the time of publication and is intended for general informational purposes only. It is not intended as legal, tax, accounting, or financial advice. Laws, regulations, and guidance may vary based on your specific circumstances, and interpretations or outcomes may differ. Information may also change over time. Before making any decisions, you should consult your own qualified legal, tax, accounting, or financial advisors._ _The testimonials on this website are from actual Brex and Brex Treasury clients, and reflect their personal experiences and opinions. Please note:_ _- Testimonials may not represent the experiences of all clients, which can vary based on individual goals, market conditions, and services used._ _- They are not guarantees of future results. All investments carry risk, including potential loss._ _- Clients were not compensated for their statements._ _- Testimonials are presented as provided, without substantive edits._ _- Prospective clients should conduct their own due diligence, consider their financial circumstances, and consult a qualified professional before making investment decisions._ ## Frequently asked questions about outstanding invoices ### What is an outstanding invoice? An outstanding invoice is a vendor bill your company has received but has not yet paid, recognized as a current liability in the AP subledger until it clears the workflow. On the AP-receiver side, the outstanding invoice means money you owe and need to schedule. From the supplier's side, the same document is a receivable. ### What is the difference between an outstanding invoice and an overdue invoice? An outstanding invoice is open but still within payment terms, while an overdue invoice has passed its due date. Each status requires a different AP action. Outstanding invoices need a management workflow to approve, match, schedule, and pay, while overdue invoices need an escalation workflow to resolve the bottleneck and protect the vendor relationship. ### Is an outstanding invoice an asset or a liability? From the AP receiver's perspective, an outstanding invoice is a current liability recorded as accounts payable. From the vendor's perspective, the same invoice is a current asset recorded as accounts receivable. It's a single document with two different balance sheet treatments, depending on which side of the transaction you're on. ### How do I record an outstanding invoice in accounts payable? Under accrual accounting, companies commonly record a vendor invoice by debiting the relevant expense or asset account and crediting accounts payable at the invoice date. When payment clears, companies commonly debit AP and credit cash or the business account, then reconcile the subledger to the GL. Specific treatment depends on the company's accounting policies and applicable standards, so consult a qualified accounting professional for your situation. ### What is an AP aging report, and how does it relate to outstanding invoices? An AP aging report groups outstanding invoices by how long they've been open. Common buckets include current, 1-30 days, 31-60 days, 61-90 days, and more than 90 days. It's the primary tool controllers use to identify overdue items, prioritize payment runs, and report AP health to the CFO. ### How do I make sure a payment gets applied to the right outstanding invoice? Reconciling the payment method, whether ACH, wire, or card, against the invoice number logged in the AP platform before marking an invoice paid catches most misapplied payments before they surface as a false outstanding balance later. Misapplication happens most often when a vendor has several open invoices at once and no single system is tracking which payment matches which bill. Automated [accounts payable reconciliation](https://www.brex.com/spend-trends/accounting/accounts-payable-reconciliation) tools reduce this risk further by matching payments to invoices automatically instead of relying on manual lookups across separate systems. ### Can AP teams get automatic reminders before an outstanding invoice comes due? Many AP platforms can flag an invoice as its due date approaches instead of requiring someone to check the aging report by hand. Brex customers can rely on routing rules and escalation reminders in Brex bill pay to surface invoices before they stall past their due date, and see that status directly on the Bills page. The reminder still depends on accurate invoice data, so the invoice needs to be captured and coded before that reminder logic has anything to act on.