← Back to Work
Process file · Finance
Finance
What’s inside: company memory · audit trail
A new vendor, waiting on AP, compliance and treasury
The question this file answersDo we really need AP, compliance and treasury each rebuilding the same supplier file before the first invoice can be paid?
Fits: banks, payment firms and fintechs where compliance files are still assembled by hand.
Typical day
What the desk looks like today
Not a measured desk — the finance playbook gives no volume for vendor onboarding, and KYC’s is not borrowed. A new supplier’s tax form, bank letter and questionnaire arrive by e-mail. AP builds a file, sends it to compliance, then treasury; the first invoice arrives before anyone has approved the vendor.
Typical, from the industry playbook — not a client's day.
What changes
What Monday looks like after
When the approver opens the queue, each new vendor is one file — documents, extracted details, the list-check result and a note on anything missing — rather than a chain of forwarded e-mails. Their decision takes the time a decision takes; the collecting and retyping no longer sit on their desk.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
How this file is built
No published benchmark covers vendor onboarding at AP. The McKinsey KYC study (2023) range is about client KYC and is left on the parent file; suppliers are not clients, and the number is not moved. Not an approval-time claim.
What we install
What we put in front of the systems you already run
Your ERP vendor master and screening tools stay — SAP, Dynamics, World-Check or the ones you run. Our KYC onboarding build, aimed at suppliers rather than clients:
- the documents are collected from the mailbox or a supplier form, and each one is classified and checked for completeness
- legal name, tax ID and bank details are pulled out and screened against sanctions lists and your existing vendor master for duplicates
- a complete file with every check logged goes to the approver, and nothing is written to the vendor master until they say so.
What stays human — and what this will not do
Sanctions hits. Odd banking arrangements. Related-party questions. The approval decision.
Not an approval-time claim.
What can go wrong — and what we do about it
A bank letter that is a forgery looks like a bank letter — the build checks completeness and lists, not authenticity, which is why the call-back to the bank stays a person’s job. If your vendor master is full of duplicates, the duplicate check will flag most new vendors until it is cleaned.
What it costs to get there
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
This is about you if…
- Do new-vendor documents arrive piecemeal by e-mail and get assembled by AP?
- Is approval a named person in compliance or treasury, and do they screen against a list?
What does this mean in euros?
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Finance.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.
All process files