The invoice is in. The work is done. Then Accounts Payable sends it back with a short note: vendor paperwork is not current.
Now the scavenger hunt starts.
Is a document actually expired? Did the vendor already send the replacement to somebody else? Is it sitting in a shared inbox? Did a third-party vendor system request it but never receive it? Does this customer need something different from the standard vendor file? Did the new document arrive and simply never make it through the internal review step?
This is one of those administrative problems that looks simple from the outside. “Get the missing paperwork” sounds like a five-minute job. Sometimes it is. Other times the vendor administrator spends half the morning reconstructing what happened across email, a spreadsheet, a customer portal, the accounting system, and a folder containing three versions of the same PDF.
The useful response is not to immediately send the vendor another generic request. First, figure out what is actually holding up the record.
Start with the reason the invoice stopped
When somebody says a vendor is “not current,” that description is too broad to work from.
A vendor record may contain a dozen pieces of information, and eleven of them may be perfectly fine. Reopening the entire onboarding packet wastes time and creates another problem: asking the vendor for documents they already supplied.
Start at the downstream failure and work backward. Get the invoice number or transaction reference, the customer or project if one is involved, and the specific item AP believes is unresolved.
A useful working note can be very plain:
Vendor: Summit Mechanical
Invoice: 18427
Reported problem: vendor record not current
Open item: replacement certificate not reflected in customer record
Last known action: renewal requested Aug. 19
Next step: check shared inbox and vendor-management portal
That is enough to give the administrator a starting point. It also connects the payment problem to the document problem without trying to turn your document tracker into an accounting system.
If AP cannot tell you which item is holding things up, finding that out is the first task. “Paperwork issue” is not a workable status.
Before you chase the vendor, make sure the vendor still owes you something
This is the part worth doing even when everyone is impatient.
Check the original request thread. Search the shared inbox. Look at the vendor or customer portal if one is part of the process. Check the internal record for recently received documents. If a broker was involved, search for that contact too.
A surprising amount of duplicate chasing starts after the outside party has already done its part.
Maybe the broker replied Friday afternoon and the attachment is still unread. Maybe the vendor sent the renewal to the employee who handled onboarding six months ago. Maybe the portal says the replacement was received and is waiting for review. Maybe somebody saved the PDF to the shared drive but never updated the spreadsheet.
Those are not versions of “vendor did not respond.” They are internal handoff problems.
That distinction matters. If the file arrived, change the operating state from Waiting on vendor to whatever is actually true now: Received — needs review, Waiting on customer, Needs internal update, or another state your team understands.
Otherwise the vendor gets a second request for work they already completed, and your own tracker becomes less trustworthy at the same time.
Follow the current requirement, not the filename
Renewals are especially good at creating false confidence because the folder looks busy.
You may have COI.pdf, COI-new.pdf, COI-2026.pdf, and the immortal COI-FINAL.pdf. The newest file may be obvious to the person who saved it. It will be considerably less obvious to somebody covering the desk next Thursday.
The requirement record should tell the current story:
| Requirement | Current state | Latest meaningful activity | Next action |
|---|---|---|---|
| Customer certificate | Received — needs review | Replacement received Aug. 28 | Review and update record |
| Vendor tax form | Current | Confirmed during onboarding | None |
| Customer portal profile | Waiting | Renewal uploaded Aug. 29 | Recheck Sept. 2 |
The folder still matters. It is where the files live. It just should not have to explain the workflow by itself.
This is where document storage and administrative coordination part company. Storage can tell you that four PDFs exist. The operating record needs to tell you which one matters, what happened to it, and whether anybody still has work to do.
Keep customer-specific problems separate from the master vendor record
A common source of confusion is the phrase vendor record itself.
Suppose Summit Mechanical works for three customers. Its general company information is current. Customer A has everything it needs. Customer B is waiting on a project-specific form. Customer C has a portal submission under review.
Is Summit “current”?
That single label is not very helpful anymore.
Keep the general vendor record separate from customer-specific work:
Summit Mechanical — master vendor record
Company information and reusable documentsRed Mesa — customer requirements
Project form still openNorth Valley — customer requirements
Portal submission waiting on review
Now an invoice problem can be traced to the right context instead of turning the entire vendor red.
Customer requirements vary. One customer may ask for something another customer never needs, and a reusable company document can be current while the work surrounding it is still unfinished. A single source of truth is valuable precisely because it can preserve those differences without making the administrator reconstruct them from old email.
Treat portal reminders as evidence, not the whole story
Outside vendor-management and customer systems add another wrinkle. They may send automated reminders, show their own status, and maintain their own review queue.
Useful? Absolutely. Complete picture of your internal work? Usually not.
A portal may show Pending Review while your spreadsheet still says Submitted. An automated system may have emailed the vendor three times while the vendor replied directly to your office. A customer may request a correction in its portal while the person who owns the internal tracker has not seen it yet.
You do not need to reproduce every portal field internally. You do need enough context to understand what the outside status means for your team.
For example:
Portal observation: Pending Review, checked Aug. 29
Internal state: Waiting on customer
Next review: Sept. 2
That is much more useful than copying Pending Review into another spreadsheet and hoping everyone remembers what to do with it.
Give the blocker a next move
Once you find the actual issue, the remaining workflow should become boring.
If the vendor still owes the replacement, record that and set the next follow-up date. If your team received the file but has not processed it, assign the internal action. If a portal is reviewing the upload, record when it was submitted and when someone should check again. If AP needs an update after your part is complete, make that handoff visible too.
Avoid leaving this behind:
Invoice on hold — paperwork issue.
Three days from now, that sentence will tell you almost nothing.
This is better:
Replacement received Aug. 28. Maya reviewing the Red Mesa requirement today. AP update is next. Recheck Sept. 1 if invoice 18427 still shows blocked.
Now the work can survive a weekend, a sick day, or somebody else taking over the desk.
It also answers the three questions that matter during a handoff: What happened? Who has the ball? When should we care again?
After the invoice moves, spend two minutes on why it got that far
Once the immediate fire is out, it is tempting to close everything and get back to the rest of the pile. Before you do, look at why an invoice was the thing that exposed the problem.
Maybe the expiration date was never updated. Maybe the renewal arrived in the wrong inbox. Maybe the portal and spreadsheet disagreed for two weeks. Maybe nobody owned received-document review. Maybe a customer-specific requirement was hiding behind a cheerful green Complete on the master vendor row.
You do not need a committee meeting. You need enough of a postmortem to prevent the same failure from becoming next month’s scavenger hunt.
If the issue was an inbox handoff, decide where received items become visible. If it was an ambiguous status, add the waiting party and next review date. If customer-specific work was buried in the master record, separate it. If the team only discovered an expiration because AP complained, make sure renewal work surfaces earlier next time.
Sidecar can help with that operating layer by keeping customer requirements, requests, replies, waiting states, follow-ups, and activity connected while accounting systems and customer portals continue doing their own jobs. A disciplined spreadsheet can use the same principles. The software matters less than having one dependable place where the administrative story is current.
Because when an invoice gets stuck, the useful question is not “Do we have a folder for this vendor?”
It is:
What am I missing, who has the ball, and what happens next?
That answer should take a minute to find.
Not an afternoon.