Every supplier. Verified, scored, managed.

Yes - both bank-account validity (Pay.UK modulus check) and account-holder name (Confirmation of Payee, the same name-check banks use before processing faster payments). Together with Companies House and HMRC VAT, that's the four-layer verification pass - runs in under five seconds, audit-trailed, fraud-tagged. The full breakdown is on the supplier verification page.

Each failure is captured as structured JSON with a specific reason - for example: "Company Number not found in Companies House", "Postcode does not match", "VAT Number not found at HMRC". The supplier remains in verification_failed state, exposing the failures to admins. Approval is blocked unless an admin uses the skip_checks override (audited) for genuine edge cases - overseas suppliers, sole traders not VAT-registered, etc.

Existing suppliers are classified the first time an invoice from them is processed - the line items, vendor name and trading patterns are used to infer the category from your tree. Each classification has a confidence score and a source tag (ai, manual, imported). The active category is computed as: highest confidence wins and any manual classification beats AI regardless of confidence. So if you correct one supplier's category once, that becomes the persistent answer.

Yes - that's what the multi-site supplier account model is for. One legal supplier (e.g. FS Foodservice) can have multiple accounts, one per site or business unit, each with its own account number, contact, payment terms, minimum order value and preferred delivery day. Pricing flows through individual purchase orders against each account. Site-level pricing variance is one of the things the spend analysis surfaces - same product, two sites, different supplier-side pricing.

It's a weighted composite from your live data: 30% delivery reliability (variance % from GRN data), 25% credit quality (credit-to-spend ratio), 25% invoice accuracy (% of invoices matching PO amounts), 20% credit recovery (expected vs received credits). The result is a 0–100 score with five bands: Excellent (90+), Good (75–89), Acceptable (60–74), Poor (40–59), Critical (<40). Calculated on demand, not stored stale - when you open a supplier's scorecard, it reflects yesterday's invoices.

No - the onboarding flow is invite-only and one-shot. The supplier gets a 48-hour token-based link to fill in their profile and once submitted, that link is closed. There is no persistent supplier login portal. Ongoing supplier communication happens via email and the OmniPATH messaging surface (which can include external suppliers via SES). A persistent supplier-side portal for ongoing access is a separate consideration on the longer-term roadmap.

CSV import deduplicates by company number first, then by email - both scoped within your organisation. If a row matches an existing supplier on either, it's skipped with a "duplicate" note in the import report. Validation errors (missing required fields, invalid formats) are surfaced row-by-row before commit, so you can fix and re-upload. A typical 50-row import takes about 4 seconds.