From supplier form to clean record

NgageFlow checks each new supplier, then creates it in IFS or SAP.

Before and after

The same piece of work, as it waits today and once NgageFlow has run it.

Before The supplier form travels from inbox to inbox.
Outlook Procurement inbox 4 unread

Fw: Fw: New supplier, Example Fasteners AB

From
Finance, via procurement
Attached
Supplier form.xlsx, bank letter.pdf
Asks
Is this the same as Example Fastening?

Waiting Bank details unchecked, not yet in IFS

NgageFlow Agents run it

Supplier flow

  1. 1Read the form and the bank letterOutlook
  2. 2Look for duplicatesIFS
  3. 3Check the VAT numberHTTP
  4. 4Ask finance, then create itIFS
After Checked, approved and created in IFS, once.
Teams #procurement 1 new

Example Fasteners AB is created in IFS as supplier 30418.

Duplicates
None, 1 near name checked
VAT number
Valid in the registry
Bank details
Approved by finance

Created Checked, approved and created by NgageFlow

Illustrative, on a test landscape. Names, numbers and amounts are samples.

What runs between form and IFS

Every new supplier starts a run like this.

NgageFlow 4 steps

New supplier form from Example Fasteners AB

  1. 1 Read the form and the bank letterExample Fasteners AB, 1 bank account Outlook
  2. 2 Look for duplicatesNo match, 1 near name checked IFS
  3. 3 Check the VAT numberValid in the registry HTTP
  4. 4 Ask finance, then create itApproved in Teams, created as 30418 IFS
An illustrative run on a test landscape.
  1. 1

    Read the form and the bank letter

    Outlook, the procurement inbox

    The agent gathers name, tax number and bank details into one record.

  2. 2

    Look for duplicates

    IFS, suppliers

    It compares the new supplier with existing ones, near spellings included.

  3. 3

    Check the VAT number

    An HTTP step

    It calls the registry or screening service your compliance team uses.

  4. 4

    Ask finance, then create it

    Teams, then IFS

    Finance approves the bank details in Teams. Then the supplier is created.

Runs on IFS and SAP

New suppliers land in either, checked the same way.

SystemWhat it holdsWhat NgageFlow does
IFS Suppliers and payment details Checks for duplicates, creates the supplier
SAP Business partners and bank details The same, on SAP
HTTP Registries and screening services Checks VAT numbers and sanctions lists
Outlook or a web form The supplier’s documents Starts a run for each new supplier

IBM Maximo, IFS and SAP are ready today. For any other application, including a homegrown one, we teach Ngage how it works in weeks.

You choose what waits

The checks run alone. The decisions wait for a person.

  • Read the documentsRuns alone
  • Check duplicates and the registryRuns alone
  • Create a new supplierWaits for procurement
  • New or changed bank detailsWaits for finance

Questions about supplier onboarding

How does it catch duplicate suppliers?

The flow reads your existing suppliers, and the agent compares names, tax numbers and addresses, near spellings included. A likely match goes to a person with both records side by side.

Who approves a new supplier?

Whoever your policy names. Procurement approves the supplier, finance the bank details, and every decision goes on the audit trail.

Can compliance checks run automatically?

The routine ones can. HTTP steps call the registry and screening services you already use, and people review what they flag.

Describe your supplier process

Write it the way you would brief a new buyer.

Or write to hello@ngagesuite.com

Try one

It runs on

We run it with you, live, in a safe test setup.