Use casesApprovals and back office
Vendor onboarding
Collect supplier documents, review them properly, and approve new vendors with a record.
- Invited
- Documents received
- Under reviewApproval
- ApprovedDone
- SuspendedSide exit
The problem
What goes wrong today
New suppliers are set up from an email thread and a folder of attachments. Certificates expire without anyone noticing, and when an auditor asks who approved a vendor, the answer takes a week to find.
How It Works
How this use case runs, step by step
Amber steps wait for a person's decision; everything else moves on its own.
- Procurement adds a vendorAt a food manufacturer, a buyer adds a new packaging supplier and marks it as high risk because it handles food-contact materials.
- Documents arriveThe supplier emails its certificates. The buyer attaches them to the vendor record and moves it to review.
- Parallel review All reviewers approveFinance checks the bank details while procurement checks the certificates. Both approve on the same afternoon.
- Compliance signs off Approve or rejectBecause the vendor is high risk, the compliance lead is next. She approves with a note on the next audit date.
- Ten months laterThe scheduled check flags a certificate expiring next month, and the buyer asks the supplier for a new one before it lapses.
Product Capabilities
What you configure in this app
Mostly configuration. Rules that configuration cannot express are written in C#.
Records 4
- Vendor5 fields + history, files, comments
- Vendor document5 fields + history, files, comments
- Bank details4 fields + history, files, comments
- Vendor review4 fields + history, files, comments
Stages 5
- Invited
- Documents received
- Under reviewdecides
- Approved
- Suspended
Automatic 3
- WorkflowA secure share link with an expiry date and a click limit sends the vendor the documents they need to sign
- ScheduleA monthly scheduled workflow finds documents expiring in the next 30 days and notifies the vendor’s account owner
- WorkflowOn approval, a workflow sends the vendor to your finance system over HTTP
Screens and reports 5
- Vendor record with documents in the file manager
- Data grid of vendors by stage and category
- Review screen for approvers with the documents alongside
- Approved vendor list with review dates, as a PDF for audit
- Expiring documents by owner, in Excel, emailed monthly
Who approves, in detail
Procurement and finance review in parallel and both must approve (All quorum). Vendors in a high-risk category add a compliance level, routed to the compliance role. Each level has a five-day limit with a reminder and escalation to the head of procurement.
When the rules change
See TechAppForce on your own use case
Bring your own version of “Vendor onboarding” and we will model its records, stages and approvals with you. A change a few months in is a reviewed release, not a rebuild.
Release: Entity: vendor
- Developmentmake the change
- QAreview the diff, test it
- Productionpromote the release