Guide
How to Handle Incomplete Vendor Packets
By Keelstar Team · Updated July 11, 2026
The short answer
When a packet is incomplete, identify missing or rejected items specifically — not a generic 'incomplete' flag vendors cannot act on. Send targeted portal tasks with deadline and consequence. Do not partially activate vendors in ERP without a written exception policy: which missing items block PO vs payment vs both. Standard path: no first payment until tax and banking validate; COI may follow for low on-site risk with documented acceptance. Escalate to the business sponsor when vendors miss second deadline. Track incomplete rate by document type to fix systemic gaps — often unclear COI requirements or W-9 entity confusion.
Diagnose the gap precisely
Break incomplete into: not requested, vendor pending, submitted wrong, internal review backlog, or rejected pending vendor fix. Each has a different owner and fix.
Vendor-facing clarity
Portal should list outstanding items with examples and contacts. Vendors abandon packets when requirements read like internal jargon.
Internal review bottlenecks
Sometimes the vendor is done and AP or legal has not reviewed in ten days. Track internal SLA separately from vendor SLA.
Exception documentation
When leadership approves go-live with gaps, record approver, missing items, remediation deadline, and payment limits. Auditors will ask.
Root cause reviews
Monthly tally of rejection reasons: TIN mismatch, wrong entity on W-9, COI limits, missing additional insured. Feed into checklist and template improvements.
Frequently asked questions
- Can we pay a vendor with a missing COI?
- Only under a documented exception with risk acceptance for low physical exposure — never as default. Construction and on-site vendors should never pay without valid COI.
- What if the vendor submitted the wrong document?
- Reject with specific correction instructions in the portal. 'Wrong COI limits' beats 'please resubmit' — vendors fix faster with precise feedback.
- How long before we cancel onboarding?
- Typical policy: 30–45 days inactive with two reminders, then suspend request. Tier-one strategic vendors get phone escalation before cancellation.
- Should incomplete vendors stay in ERP?
- Prefer pending or blocked vendor status — not active — until minimum packet complete. Active status invites PO creation bypass.
Related guides
Put this into a monitored workflow
Vendor Packet handles this continuously — with reminders and an audit trail.