Supplier Portals in New Zealand

Answer the supplier's question first

Your suppliers have no obligation to log into anything. They will use a portal if it is faster than emailing you, and they will ignore it if it is not — and then you are running both systems, which is worse than where you started.

So before anything is designed, answer this: what does the supplier get?

Things that genuinely appeal to a supplier:

• Knowing when they will be paid, without ringing your accounts team.
• Seeing that an invoice was received and approved.
• Submitting an invoice against an order without formatting it to your requirements.
• Having their insurance and compliance documents in one place, with a reminder before they expire.
• Seeing all open orders in one list rather than searching an inbox.

Ask each developer what the supplier gets from their design. A firm that answers only in terms of your internal savings has designed half a system.

Design for your smallest supplier

Your top twenty suppliers have accounts teams and will cope with anything. The long tail is a sole trader with a phone in a ute, and they are frequently the ones causing the most administrative work.

Design deliberately for them:

• Email-first flows — a purchase order that can be confirmed by clicking a link in the email, without logging in at all.
• Magic links rather than passwords. Nobody remembers a password for a site they use monthly.
• Mobile-first screens. Assume a phone, not a desk.
• Photograph an invoice rather than upload a PDF.
• Someone at your end can act on their behalf, because some of them will never use it.

A portal that assumes every supplier has an accounts department covers your top twenty and misses the ones generating the phone calls.

Build the thing that generates the most email

Before committing to a platform, count. Go through a fortnight of correspondence with suppliers and tally what it is actually about.

In most New Zealand businesses it comes down to two questions: when is this arriving? and when am I being paid?

Whichever of those dominates is your first build. Get it working, run it for two months, and let the suppliers who like it pull the others along. A platform covering six functions nobody has tested is six guesses.

Check your ERP first

Several mid-market ERPs used in New Zealand have a supplier portal module. If it is close to what you need, it will be cheaper, better integrated and somebody else's problem to maintain.

Building is right when no module exists, when it is priced per supplier in a way that becomes painful at your numbers, or when your process is genuinely unusual.

Ask your ERP partner before commissioning anything, and expect any competent developer to have asked as well.

Onboarding is the unglamorous half

Getting suppliers into the portal is a project in its own right and rarely appears in a brief.

Work through:

• How does a supplier get an account — invited, or self-registered and approved?
• Who verifies they are who they say they are? An NZBN lookup is free and worth building in.
• What happens when their staff change, which they do constantly?
• Can one supplier have several users with different permissions?
• What happens to their access when the relationship ends?

The bank account question deserves particular attention. Invoice fraud generally arrives as a convincing request to change payment details, and a portal that lets a supplier change their own bank account without verification is a liability. Ask how that specific change is handled — it should involve a person and a phone call to a number you already hold.

Compliance documents need expiry, not just upload

If you are collecting insurance certificates, health and safety documentation or trade qualifications, the value is not in storing them. It is in knowing which have expired.

What that requires:

• An expiry date captured with each document.
• Automatic reminders to the supplier before it lapses, and again afterwards.
• A view of who is currently non-compliant.
• A rule about what happens when they are — blocked from new orders, or flagged?

That last one is a business decision and it should be made before the build, because it changes how the portal behaves.

Connect it, or you have built a second system

A portal that does not talk to your purchasing and accounting systems means someone at your end retyping — which is the problem you were solving.

Settle in the quote: how do orders reach the portal, how do confirmations get back, how do invoices reach accounting, and how does payment status flow out to the supplier. Then ask how failures are handled and where you would see them.

Comparing five quotes

Read for:

• Who asked what the supplier gains?
• Who designed for suppliers without an office?
• Who checked whether your ERP already has this?
• Who raised bank account changes and verification?
• Who included onboarding rather than only the portal?

Describe how many suppliers you have, what your correspondence with them is mostly about, what systems hold the orders and the invoices, and how small your smallest supplier is. Developers who have built one will ask about the long tail before they ask about the screens.