The Challenge
New vendor requests at an Enterprise organisation arrived through every channel except a structured one — email with PDF attachments, WhatsApp photos of PAN cards, chat messages with half a GST number, and ad-hoc Google Forms that nobody validated. Finance re-keyed the same details into ERP: legal name, GST, PAN, bank account, contact person, payment terms. When a document was missing, the vendor sat in limbo. Nobody could see whether the blocker was procurement, finance, or the vendor themselves.
Payments stalled at month-end because vendor masters were incomplete — missing cancelled cheques, unsigned agreements, or mismatched GST and PAN. Duplicate vendors existed under slightly different names, causing split spend reporting and reconciliation headaches. Requesters asked "where is my vendor?" daily because there was no status view, only a chain of forwarded emails.
The business needed faster onboarding without hiding bad data in the ERP. Speed and accuracy had to move together — which meant validation upfront and exceptions with owners, not silent failures.
The Approach
We mapped the procure-to-pay handoff: who initiates, who validates tax documents, who creates the ERP master, and what triggers a payment hold. Then we built intake around that sequence instead of around a generic form.
- Single intake — One structured form with required fields by vendor type: goods, services, contractor. Different types, different document checklists.
- Validation rules — GST format, PAN match, bank account pattern, and duplicate vendor checks before ERP creation — fail fast, not fail at payment time.
- Exception routing — Invalid or incomplete records went to a named queue with category and age — not a silent rejection the requester never saw.
- Stage visibility — Requesters saw status: submitted, finance review, ERP created, blocked — without emailing finance for an update.
- Document checklist — Standard attachments enforced upfront: agreement, tax certificates, bank proof — so payment holds did not surface two weeks later.
How It Worked
A requester submitted one form with all fields and documents for their vendor type. Validation ran immediately — GST checksum, PAN format, duplicate name match against existing masters. Clean submissions routed to finance review; failures landed in the exception queue with a clear reason the requester could fix and resubmit.
Finance worked from a single queue sorted by age and priority. Approved vendors were created in ERP with a linked intake record — audit trail from request to master. Requesters tracked status in the portal. Month-end payment runs hit fewer surprise blocks because documents were enforced at intake, not discovered during batch processing.
Results
Clean vendor records reached ERP with leaner setup cycles — less manual chasing for missing PAN copies, less re-keying from unstructured emails. Finance spent less time answering "any update?" and more time reviewing exceptions that actually needed judgment. Exception lists became a daily habit instead of surprise blockers at month-end.
Duplicate vendors decreased because matching ran before creation. Payment holds from missing documents dropped because the checklist was enforced upfront. The improved process gave procurement, finance, and requesters a shared view of where every vendor stood.
Procurement could plan around realistic setup timelines instead of assuming "finance will handle it." Vendors experienced fewer back-and-forth requests for documents they had already submitted in the wrong format. The intake form became the contract for what "ready for ERP" actually meant — and that clarity alone cut a surprising amount of rework. Finance reported fewer payment holds triggered by incomplete master data at month-end.
Takeaway
Onboarding automation works when you automate validation and visibility — not just data entry. Exceptions need a home and an owner from day one. Fail fast at intake so ERP stays clean and payments do not stall later.