Vendor onboarding that would survive an audit
Onboarding a vendor is a compliance exercise wearing a form’s clothes: documents that must be present, approvals that must be earned, and a history someone will one day ask for. On Faldaro the vendor fills a public link, the documents attach to the record, approval is gated on what was actually answered, and the whole trail is append-only.
-
One request instead of an email checklist
Company details, tax status, banking, certificates — one form with conditional sections, so a sole trader and a corporation answer different questions and nothing arrives as “see attached”.
-
Review as a workflow, not a spreadsheet
Submitted, In review, Approved, Rejected — with moves permissioned, conditions gating approval on the answers, and deadlines escalating a vendor nobody has looked at.
-
Vendor numbers that behave
A reference number is allocated once, when the record commits, and never changes — edits never renumber a vendor, and two simultaneous registrations can never draw the same number.
-
A file that would survive an audit
The exact form version answered, every document uploaded, every state change and who made it, the signed agreement and its evidence — kept in an append-only log, not a shared drive.
Built from the same parts as everything else: the builder, workflows and e-signatures for the agreement itself.
Questions
Onboarding on Faldaro, plainly
Do vendors need an account on our system?
No. The vendor gets a public link — an unguessable token you can rotate — and sees only the form: never your review states, risk fields or internal notes. Tax forms, certificates and bank letters upload without a sign-in and arrive attached to the record.
Can approval require the documents to actually be there?
Yes. A transition can require fields to be filled before it is offered, and a condition can gate on any answer — so “Approve” is simply not available while the insurance certificate is missing or the risk rating says review. Moving a vendor and editing a vendor are separate, permissioned acts.
Where do the signed agreements happen?
In the same record, on the Team plan and above: a workflow move requests the signature, the vendor signs on their own tokenised link, the document is frozen and fingerprinted first, and the evidence is kept in rows the application role cannot delete. A later transition can gate on the signature having happened.
What does procurement get out of this beyond a tidy queue?
A defensible history. Every submission keeps the exact form version it was filled against, every move records who took it and when, and the audit log is append-only because the database refuses updates and deletes on it — the answer to “who approved this vendor, on what information?” is always producible.
Put procurement on rails
A registration form, four states and a required-documents gate make a working onboarding — start free, no card.
No card required.