Create a supplier with Alfie after checking company and payment identity

A trade name on a delivery note is not always the legal entity that should receive a purchase record. Creating a supplier too early can split invoices, hide duplicates and attach payment details to the wrong company.

Verify the source, identity and current state

The current Alfie product page positions Alfie as a governed execution layer where context, permissions and confirmations work together. Current application source registers create_supplier; it is classified as low risk but identity-sensitive. This page does not promise an external integration, autonomous outcome or availability beyond what the source supports.

Turn the request into one bounded decision

Search existing suppliers and resolve legal name, company number, VAT identity, address, contact and payment term. Treat bank details and entity changes as a separate heightened verification rather than trusting a message alone.

Keep evidence and separate the next actions

Keep the source document and duplicate check with the new record. Creating the supplier does not approve an invoice, select a preferred article supplier or accept changed payment details.

Test exceptions before daily use

Test a missing identifier, two records with the same name, insufficient permissions, stale source data and a temporarily unavailable system. Alfie should stop with a focused question or a proposal that has not executed. Keep the original request, selected record, relevant source fields, user, timestamp and confirmation without copying more personal or payment data than needed.

Repeat the check when the party, amount, scope, schedule, recipient or document version changes. An earlier result is context, not automatic permission. Define who can correct an error, who must be informed and when the exception is genuinely closed.

Make the result readable to a colleague who did not prepare the record. They should see which facts were established, what uncertainty remains and which action was executed or blocked. Free text can explain the evidence, but it does not replace identity, source or confirmation.

Before rollout, rehearse correction as well as success. Record how the team finds an incorrect selection, which dependent records need review and who may confirm the repair. This keeps one mistake bounded to its record instead of copying it into a schedule, quote, purchase decision or invoice.

Connect preparation to governed execution

Enfin connects the customer, supplier, quote, project, task, item, cost item and invoice in one construction record. Alfie can prepare information and propose an action within available permissions; an authorised user confirms consequential actions. Explore Enfin, compare pricing or discuss your workflow.