Vendor Onboarding Checklist Before the First Payment

Start with one supplier identity and one owner

Search the vendor directory before creating another record. The same supplier might already appear under a trading name, an older company name, or a contact's name. Compare the available identifiers and ask the existing owner before merging or reusing a record. Similar names alone do not prove that two suppliers are the same organization.

Once the identity is clear, name an internal owner. This person coordinates missing information and changes; they do not automatically become the payment approver. Keep the supplier's usual contact, business address, and a short description of the relationship together so colleagues can understand why the record exists.

Collect information for a defined purpose. An operational contact record rarely needs a copy of every document the supplier can provide. Store sensitive payment or tax information in the restricted system that owns it, with a reference from the working checklist where necessary. Avoid putting full bank details in broadly visible notes.

Figena's vendor directory supports contact details, business context, and related records. A complete profile can help colleagues find the right supplier. It does not certify the supplier's identity or validate a bank account.

Check the purchase as well as the profile

Vendor setup and purchase approval answer different questions. A supplier can have a well maintained profile while a particular invoice still lacks an agreed order, delivery evidence, or an authorized decision.

Before the first payment, work through these checks. The evidence can live in your purchasing, document, or payment system; the checklist should point to it rather than create another uncontrolled copy.

The delivery check needs context. An advance payment may be legitimate under agreed terms; a delivery receipt is not the only acceptable basis. Record which condition applies and who accepted it. Do not mark an undelivered order as received merely to complete a checklist.

Keep the duplicate check in the system that contains the relevant payment history. Searching Figena's recorded expenses can support a review, but it cannot establish that an invoice was never paid in a separate banking or accounts payable system.

Verify new payment instructions through an independent route

A familiar email thread does not establish that payment instructions are trustworthy. The US National Credit Union Administration describes how compromised business email accounts can be used to redirect vendor payments and recommends confirming payment changes in person or through a known telephone number. NCUA guidance on business email compromise.

Apply your organization's verification procedure to new or changed instructions. Use a contact route established independently of the request being checked. Calling the number supplied in the same suspicious message provides little separation from that message.

Record who performed the check, when it happened, and where the protected verification evidence can be found. A note saying “looks fine” gives the next colleague no useful basis for a decision. Treat a later change of account or contact route as a fresh event requiring the relevant checks again.

Figena does not perform bank account ownership verification or send a vendor payment on the basis of a directory entry. Keep those actions in the approved payment workflow.

Give incomplete checks an explicit next step

Use a simple working status for each item: ready, blocked, or follow up. These are labels for your checklist, not a built-in vendor approval state.

Ready means the named check has the evidence required for its purpose. Blocked means the unresolved issue prevents the next consequential step. Follow up means somebody has an outstanding task that does not prevent the particular step being considered. Every blocked or follow-up item needs an owner, a due date, and a statement of what will resolve it.

Distinguish readiness for different steps. A supplier may be ready for a project kickoff while payment release remains blocked. A missing marketing brochure and an unverified payment change should not share the same consequence just because both appear on the checklist.

When an exception is allowed, record the decision and its scope under the team's authority rules. Do not turn an exception into a general “approved vendor” label that colleagues may reuse for unrelated purchases.

A hypothetical first purchase

Consider a small design studio purchasing prototype materials from a new supplier. The purchaser has an accepted order, and the delivery team has confirmed receipt. Finance receives an invoice that matches the order, but it includes account details different from those in the restricted supplier setup record.

The vendor profile is ready for operational use. The delivery check is complete. Payment release remains blocked while the payment operator verifies the changed instructions using an independently established contact route. The purchaser can continue planning the project without asking finance to treat the mismatch as resolved.

After verification and the required release decision, payment happens through the studio's payment system. Finance then records the actual expense with its source reference and the correct supplier and project links. A checklist status does not stand in for that payment result.

This separation also improves review. Profitable projects can still have a cash gap, so an agreed supplier cost, an expected outflow, and a recorded payment should remain distinguishable.

A reusable setup note

Keep this note beside the source records, with restricted references where needed:

• Supplier record and internal owner.
• Purchase purpose and related team or project.
• Agreed terms and source reference.
• Delivery or advance payment basis and reviewer.
• Invoice reference, amount, and currency.
• Duplicate check location and result.
• Payment verification reference, checker, and date.
• Authorized release decision and any limits.
• Outstanding item, owner, due date, and next check.
• Actual payment result or unresolved payment status.

Figena can connect a vendor to recorded expenses and related business context. Use that connection to make later review easier, while keeping the source invoice, sensitive payment details, and execution evidence in their appropriate systems. The weekly operating review can then surface material unresolved supplier items without reopening every document.

Review changes throughout the relationship

The first payment is a useful checkpoint, but supplier information changes. Revisit the relevant checks when contacts, payment instructions, purchasing terms, or internal ownership change. Add a reminder for a contract renewal when there is a real decision deadline, and assign someone to act on it.

Keep the original evidence and the later decision distinguishable. A directory edit should help colleagues find current information without making it appear that an earlier purchase was reviewed against terms that did not yet exist.

The practical result is a supplier record people can use and a payment decision they can explain. Start with one new vendor, establish the owners and evidence, and use the first complete checklist as the model for the next purchase.

Turning Meeting Decisions Into Actions the Team Can Complete

Separate decisions, actions, and open questions in meeting notes. Use a practical handoff template to confirm owners, define completion, manage dependencies, and review the result.