A Pellucid guide

Why Is This B2B Invoice Still Unpaid?

How to diagnose an overdue B2B invoice before you send another reminder

When a business-to-business (B2B) invoice stays unpaid after follow-up, something specific is usually in the way. The customer may never have accepted it. It may be missing a purchase order (PO) number. Someone on their side may still need to approve it. Part of it may be disputed, a payment may have failed, or the money may have arrived and not been matched to the invoice yet. A useful follow-up depends on what is holding the invoice up.

This guide covers the most common situations to investigate, where to find the evidence for each, who usually owns the next step, and what to do. It ends with a short exercise for your own open invoices, and a look at why this work gets harder as invoice volume grows.

Quick reference

SituationFirst place to checkLikely ownerNext action
Not yet due on the agreed termsContract or orderAccounts receivable (AR)Confirm terms and record the expected payment date
Not received, accepted or set upDelivery record, supplier portalARComplete onboarding, resubmit, confirm acceptance
Missing PO or referenceCustomer email, PO recordBillingCorrect and resubmit through your billing process
Waiting on customer approvalEmail thread, timesheet or sign-offAccount manager or project leadAsk the approver for a decision date
Disputed or billed incorrectlyContract, delivery proof, creditsWhoever can decidePause reminders with a review date, resolve, correct
Scheduled or promisedAccount notesARRecord the date and amount, check on that date
Payment attempted but failedPayment processorARCheck the failure reason, retry or ask the customer to act
Customer says they paidBank deposits, processor, remittance emailsAR or cash applicationConfirm payment status, then apply it
Short-paid or deductedRemittance adviceAR, with approver for creditsApply the payment, track the difference in a linked case
Possible cash constraintsPayment history, conversationsFinance leadInvestigate, then escalate to someone with authority
Reason not yet establishedAll of the aboveARRecord what you checked and set a review date

Invoices can have more than one blocker at a time. Record each one.

Eleven situations to investigate

1. The customer says it isn't due yet

What it looks like: Your system shows the invoice as overdue. The customer says it's on time.

Where to check: The signed contract or order. Look at what starts the payment clock. Your system may count Net 30 from the invoice date, while the customer's accounts payable (AP) team counts from the date they received or approved the invoice. Some customers also pay only on set days of the month.

What to do: Check the agreed terms first. If your due date is wrong, correct it. If the customer is asking for a change, get it authorized and documented. Record their expected payment date separately from the due date.

What to avoid: Overwriting the agreed due date to match the customer's payment schedule. It hides real lateness and makes your aging report less accurate over time.

2. The invoice was never received, accepted or set up

What it looks like: Silence, or a reply saying they can't find the invoice.

Where to check: Your delivery record. Did the invoice go to the AP team or to the person who signed the contract? If the customer uses a supplier portal, check whether it was submitted and whether it was accepted, rejected or is still pending. Also check vendor onboarding. Larger customers often need supplier registration, tax documentation (in the US, often a W-9) and verified bank details before they can pay you.

What to do: Finish any onboarding steps, confirm the correct AP contact or portal, resubmit, and get confirmation that the invoice has been entered. If the customer asks you to confirm or change bank details, verify the request through a contact you already know.

What to avoid: Assuming a delivered email means the invoice is in their system. Portal-based customers may need successful submission and acceptance before processing can start, so an invoice can sit in a rejected queue for weeks while you send reminders to an inbox.

3. It's missing a PO number or reference

What it looks like: A portal rejection, or a request to add a PO number, cost center or project code.

Where to check: The customer's email, the original order or contract, and the PO itself. Check whether the PO has enough remaining value to cover this invoice.

What to do: Correct the invoice and resubmit it through your normal billing process, following your accounting policy for revisions. If the PO has run out, ask the customer to raise a new one or increase the existing one first.

What to avoid: Creating a second invoice for the same work. A duplicate receivable inflates your balances and confuses the customer about what they owe.

4. It's waiting on the customer's internal approval

What it looks like: "It's with the project lead." In staffing, the timesheet hasn't been approved. In professional services, the client hasn't signed off on the milestone.

Where to check: The email thread, the timesheet or sign-off record, and your own delivery team, who may already know the approval is stuck.

What to do: Ask AP who the approver is and when they expect a decision. Ask your account manager or project lead to contact the approver directly, since they usually have the relationship.

What to avoid: Chasing AP. They can't pay until the approver acts, so reminders to them use up goodwill without moving the invoice.

5. It's disputed or billed incorrectly

What it looks like: Pushback on a rate, hours, quantity, scope or delivery. Or a genuine error on your side: a canceled service still billed, a duplicate invoice, or an agreed credit that hasn't been issued.

Where to check: The contract, change orders, delivery proof or timesheets, credit memos, and the full email history.

What to do: Pause automated payment reminders on the invoice and set an owner and a review date. Route the question to whoever can decide it, often someone outside finance. If only one line is in question, ask the customer to pay the undisputed portion. If the error is yours, correct it and issue any credit promptly.

What to avoid: Letting the undisputed amount wait along with the disputed one, or leaving a pause open with no review date. Both let a small question hold up the whole balance.

6. Payment is scheduled or promised

What it looks like: "It's in next week's payment run." "We'll pay on the 15th."

Where to check: Your account notes and the customer's usual payment pattern. Many AP teams pay on a fixed weekly or twice-monthly cycle.

What to do: Record the promised date and amount against the invoice. On that date, check for the payment before reaching out.

What to avoid: Recording the promise without a date to check it. A promise nobody tracks quietly becomes another overdue invoice.

7. A payment was attempted but failed

What it looks like: A declined card, a returned bank debit, or a customer who says they paid when your processor shows a failure.

Where to check: Your payment processor's status and failure reason. Insufficient funds, an expired card, a closed account and a revoked authorization each need a different response.

What to do: For a temporary failure, retry within your processor's rules. For anything else, tell the customer what happened and ask them to update their payment method or authorization.

What to avoid: Retrying repeatedly without reading the reason. Some failures won't succeed on retry, and repeated attempts can create fees or frustrate the customer.

8. The customer says they paid, but the invoice is still open

What it looks like: The customer insists it's paid. Your system shows it as open.

Where to check: Bank deposits, your payment processor and remittance emails. Look for payments made under a parent company's name, combined payments covering several invoices, or money that went to a different account or entity. Separate four states: initiated (the customer sent it), pending (it's in transit, which can take a few business days for bank transfers), received (it's in your account) and applied (it's matched to the invoice).

What to do: Confirm the payment status with your bank or processor, match the payment to the invoices it covers, and record it following your accounting policy for funds in transit and allocation. Then let the customer know it's closed.

What to avoid: Closing the invoice on the customer's word alone, or sending a reminder before you've checked for unmatched cash. The first can misstate your receivables and payment records. The second tells their AP team your records are behind.

9. It was short-paid or deducted

What it looks like: A payment that's less than the invoice.

Where to check: The remittance advice, which often explains the gap. Common causes are an early-payment discount taken after the discount window, bank or card fees deducted by the payer, deductions for damaged or missing goods, pricing differences, or a credit the customer believes they're owed.

What to do: Apply the payment to the invoice so the remaining balance stays visible. Track the difference in a linked case or task, decide whether the deduction is valid, and either issue an approved credit or respond with your evidence.

What to avoid: Writing off the difference without approval, or leaving the payment unapplied while you investigate. Small unapproved write-offs add up, and unapplied payments make your aging report wrong.

10. There may be a cash constraint

What it looks like: Repeated missed promises, slower payments across all invoices, or a customer who stops responding.

Where to check: Payment history over recent months, past conversations and your account manager's view of the relationship. These signals can also mean the contact left, a dispute is brewing or an administrative problem is unresolved, so rule those out first.

What to do: If the evidence points to a cash problem, escalate to whoever can approve a payment plan, a hold on new work or other next steps. Document every conversation and commitment.

What to avoid: Offering concessions without authority. Payment plans, holds and write-offs need someone who can see the full commercial picture.

11. You don't know yet

What it looks like: Nothing in your records explains the delay.

What to do: Record what you checked, name an owner and set a review date. "Reason not yet established" is a legitimate status. Forcing an invoice into a category before you have evidence leads to the wrong next step.

An illustrative example

This is an example for illustrative purposes and doesn't reflect or describe a real customer.

A consulting firm's aging report shows a $9,200 invoice for Client A at 47 days past due. Two reminders have gone out with no reply.

Before sending a third, the AR specialist checks the bank deposits and finds a $17,600 payment from Client A's parent company two weeks ago. The remittance email, sent to a project manager rather than the AR inbox, says the payment covers this invoice and a second one for $8,800. It also deducts $400 from this invoice for a travel expense the client says wasn't approved.

So the invoice had two blockers: a payment received but not applied, and a small dispute. The specialist applies the payment, which leaves $400 open on the first invoice and tracks it in a linked case. The account manager owns the expense question, with a review date one week out. The case closes when the account manager confirms whether the expense was approved and either a credit is issued or the client pays the remaining balance.

A third reminder for the full $9,200 would have ignored the payment already received and the specific expense still in dispute.

The ten-oldest-invoices exercise

Give yourself a one-hour first pass. Stop when the time is up and note what's left unresolved.

  1. Pull your aging report and pick your ten oldest open invoices. Swap in a few very large balances if they matter more.
  2. For each invoice, record:
    • Outstanding amount and current payment status
    • The blocker, marked as confirmed or suspected, with the record that shows it
    • The accountable owner on your side, and anyone you're waiting on outside it
    • The next action and a review date
    • Whether the same issue has happened before with this customer
  3. Afterward, record the resolution for each invoice.

Then ask yourself:

  • How many of these would another reminder have moved forward?
  • How many needed someone outside finance to act?
  • Were any already paid?
  • How many places did you have to look, and how long did gathering the information take?

The oldest invoices surface the hardest cases, so treat the results as a view of your trickiest problems rather than a picture of your whole receivables.

Fix the causes that repeat

Some blockers show up again and again with the same customers. Those are worth fixing at the source:

  • Missing POs: Capture the PO and required references when the contract or order is signed, and check for them before each invoice goes out.
  • Wrong recipient or incomplete setup: Record AP contacts, portal requirements and onboarding documents when you set up a new customer.
  • Approval delays: Name the approver for each engagement and send them the supporting detail with the invoice.
  • Unmatched payments: Ask customers to include invoice numbers with payments, and tell them where to send remittance details.
  • Term mismatches: State in the contract what starts the payment clock, and make sure your system uses the same rule.

For each resolved case, note what fixed it and whether it came back. That record is what lets the next invoice to the same customer go out right the first time.

Why diagnosis gets harder as volume grows

As invoice volume and customer requirements grow, keeping track of every blocker from memory becomes harder. Teams start triaging: the largest and oldest balances get investigated, and everything else gets a standard reminder or waits.

That's when the backlog starts to compound.

  • Every billing cycle adds new invoices while the unresolved ones carry over.
  • Blockers can get harder to clear with age. Contacts change, POs close, approvers move on, and the records needed to resolve the issue become harder to find.
  • Unmatched payments and deductions pile up, which makes the aging report less reliable and prioritizing harder.
  • More of the team's time goes to finding information and less to resolving anything.

Signs in your AR metrics

MetricWhat it tells youWarning sign
Days sales outstanding (DSO)How long, on average, it takes to collectWell above your standard payment terms, or rising for several months
Average days delinquent (ADD)An estimate of how much of DSO comes from customers paying after their due datesGrowing
Balances more than 60 or 90 days past dueHow much of your receivables has aged well beyond termsA growing share of total receivables
Collection effectiveness index (CEI)How much of what was collectible in a period you collectedFalling
Unapplied cashPayments received but not matched to invoicesA growing balance, or items that sit for weeks
Open disputes and deductionsHow much is held up waiting on a decisionMore cases, or cases taking longer to close
Overdue invoices with no recorded reasonHow much of the backlog nobody has diagnosedA rising share of overdue invoices

DSO also moves with sales swings, seasonality and the mix of payment terms, so read it alongside the other measures. Compare it first with your own payment terms and its trend over time. Industry benchmarks vary widely by sector and customer mix, so use them as context.

How automation and AI can help

The diagnosis in this guide depends on two things that are hard to do by hand at volume: checking every open invoice regularly, and pulling evidence from several systems for each one. That's where automation and AI can make the biggest difference.

  • Regular checks across your invoices. Software can regularly review invoices available through connected systems and flag any without a recorded reason or next step. Earlier detection gives teams more time to resolve blockers before invoices age further.
  • Evidence gathered in one place. AI can read customer emails and remittance attachments, recognize a PO request, a promise date, a dispute or a payment reference, and connect it to the right invoice. A suggested explanation should show the records behind it and flag anything missing or conflicting, so your team can confirm it before acting.
  • Payment matching with review for the hard cases. Software can match incoming payments, including combined and partial ones, when the available records support a reliable allocation, and route ambiguous cases to a person. Fewer payments sit unapplied, and fewer reminders reach customers who have already paid.
  • Follow-up that fits the blocker. A missing PO calls for a corrected invoice, a pending approval goes to the account manager, and a routine reminder goes out on schedule. The aim is to improve collection outcomes by addressing the specific blocker on each invoice.
  • Attention where it matters. Ranking invoices by amount, age, payment history and open issues helps your team spend its time on disputes and cash conversations that need judgment.
  • Repeat causes made visible. When resolutions are recorded consistently, patterns can surface: the customer who always needs a PO reference, or the approver who's always late. Fixing them can reduce repeat disputes and late payments.

People stay in charge of disputes, credits, payment terms, write-offs and sensitive customer conversations. Automation takes on the routine volume so those decisions can get made sooner.

Measure the change honestly

Before changing your process or tools, record a baseline for the metrics above. Compare similar invoices before and after, and account for changes in payment terms, customer mix or collection policy. Track cash outcomes, such as days to collect and cash collected, separately from activity, such as reminders sent. Faster activity on its own doesn't prove you're collecting more or sooner.

Where Pellucid fits

Pellucid is an AI-Native accounts receivable platform for B2B finance teams.

It works alongside your accounting system. Pellucid is designed to bring together what your accounting system, AR inbox and payment records each know about an invoice, suggest the likely blocker with the records behind it, and prepare the next step for the right person. Our approach is to automate routine steps within agreed controls and involve people where judgment or customer relationships matter. Disputes, payment terms, credits and write-offs stay with your team. See how the Pellucid platform connects these records and how it handles invoice questions and disputes.

We're building Pellucid to help B2B finance teams get paid sooner, collect more of the cash they're owed, remove repetitive manual work and get time back for the decisions that need judgment.

Want to talk through what's holding up your invoices? Talk to us