[ SAP S/4HANA / Master data ]

Supplier onboarding into SAP, without the re-keying

engini reads the documents a new supplier sends, checks SAP S/4HANA for an existing business partner, and prepares the new record for procurement to review on a board they already use. When they mark it ready, engini creates the business partner and its supplier role in SAP through SAP’s business partner service.

SAP S/4HANAOutlook or Gmailmonday.comSlack
Read the SAP S/4HANA guide →
A new supplier, start to SAP
  1. Documents arrivetax form and bank letter to vendors@
  2. AI extracts the detailslegal name, address, tax ID, bank
  3. SAP S/4HANA logo
    Duplicate check in SAPbusiness partners with this tax ID: none
  4. monday.com logo
    Ready for reviewprocurement board: new supplier item
  5. SAP S/4HANA logo
    Business partner createdafter the item is marked Ready
Illustration of the flow on this page, not a product screen.
What it does
Supplier documents read, duplicates checked, business partner prepared and created
Systems
SAP S/4HANA (OData), Outlook or Gmail, monday.com or Sheets, Slack or Teams
Built with
Two workflows: intake with an AI agent step, and create on Ready
Your control
Procurement marks each record ready; SAP authorizations apply
[ 01 / The problem ]

Every new supplier starts as a stack of PDFs

In SAP S/4HANA the business partner is the single entry point for supplier and customer master data, with roles, addresses, tax numbers and bank details. Getting a new supplier into it usually means a request form, a few emailed documents, and someone in procurement or master data typing it all in. The number of SAP partner add-ons for vendor forms, duplicate checks and onboarding workflows shows how much of this is still manual.

It is also where small mistakes are expensive: a duplicate supplier splits spend reporting, a mistyped bank account sends a payment to the wrong place, and a missing tax ID holds up the first invoice.

What slows onboarding

  • Reading tax forms and bank letters in different formats.
  • Searching SAP for an existing partner under a slightly different name.
  • Chasing the requester for the fields that were left blank.
  • Keying the partner, the supplier role and the bank details by hand.

Where the agent helps, and where people decide

An AI agent reads the documents, extracts the legal name, address, tax ID and bank details, and searches SAP for business partners with the same tax ID or a similar name. It prepares a clean record on your procurement board or sheet, with anything missing called out, and asks the requester for it.

A person in procurement reviews the record and marks it ready. That change starts a second workflow that creates the business partner, its supplier role and its bank details in SAP, each through the business partner service, on a connection whose SAP user is authorized for exactly that.

[ 02 / How it works ]

Read, check, review, create

01 / Intake

Documents arrive

A new email to the vendor inbox, or a form submission, starts the intake workflow. engini AI Tools extracts the supplier’s details from each document.

02 / Check

Look for duplicates

An AI agent step searches SAP S/4HANA business partners by tax ID and name, and flags close matches instead of creating a second partner.

03 / Review

Procurement decides

The prepared record lands as an item on a monday.com board or a row in a sheet, with gaps called out. Procurement reviews it and sets the status to Ready.

04 / Create

Business partner in SAP

The status change starts a second workflow that creates the business partner, its supplier role and bank details in SAP, and posts the new partner number back to the item.

[ 03 / What the agent reads and writes ]

What the agent reads and writes

SystemRecordsAccess
SAP S/4HANABusiness partners (duplicate search)Read
SAP S/4HANABusiness partner, supplier role, bank detailsCreate
Outlook or GmailSupplier documentsRead
monday.com or Google SheetsThe review item and the SAP partner numberCreateUpdate
Slack or TeamsRequests for missing detailsWrite
[ 04 / Build it with the engini skill ]

Describe it in plain words. The engini skill builds the workflow.

engini skills is engini’s plugin for Claude Code and Codex. Its workflow agent, Flo, turns a plain-language request into an engini workflow: it designs the steps, dry-runs them against your own engini account, shows you a proposal, and creates the workflow only after you approve it, always turned off. You check it in the engini designer and turn it on.

Blurred landscape photo with the SAP logo, the engini mark and a frosted tile joined by a thin line, labeled business partner: documents, duplicate check, ready

Editorial image: one supplier, one clean record.

Claude Code: install once
/plugin marketplace add engini/skills
/plugin install skills@engini
Then ask for this solution
Build a workflow in my engini account: when an email with supplier documents arrives in vendors@ in Outlook, extract the legal name, address, tax ID and bank details with engini AI Tools, search SAP S/4HANA business partners for the same tax ID, and create an item on my "New suppliers" monday.com board with the details and any possible duplicates. Do not create anything in SAP.
  1. You need an engini account, the engini CLI (npm i -g @engini/cli) and a workspace-scoped API key, ideally a dedicated least-privilege one.
  2. Connect the systems this flow uses in engini first. Flo never creates or changes a connection and never handles your key; it tells you which command to run.
  3. Flo checks your login and workspace, searches the tool catalog, compiles the plan and shows a proposal table with every step. It creates the workflow only when you approve that proposal, and it creates it turned off.
  4. Open it in the engini designer, fill anything it left for you, and turn it on.
engini skills for Claude Code and Codex →
What the skill will never do on its own →
[ 05 / Agent Policy ]

The agent does only what you allow. Every run is on the record.

Agent Policy is how you govern agents in engini: the tools each agent may call, the account each tool uses, and a record of every call.

Toolsets

Scope every call

Hand the agent a toolset: only the tools it needs, each on the connection you choose, for example read only. engini enforces it on the server for CLI, SDK and REST API calls; a call outside the toolset is refused. An MCP server exposes only the connections and tools chosen when you set it up.

Identity

Acts with the account you connect

engini acts with the permissions of the connected account. Connect a person’s own account and it acts as that person; use a shared integration account and it acts as that account. Every run is recorded under the user who triggered it.

Audit

History and audit log

Each tool call and workflow run is recorded in History and the audit log, which supports export and streaming to your SIEM. Your agent never needs your credentials: engini stores them and adds them when it runs each call.

SOC 2 Type IIISO 27001GDPRHIPAA compliant
[ 06 / Try it now ]

Build it on your own data today

Start free, connect SAP S/4HANA, and build this flow with the engini skill, in Workflow Studio, or from your own agent.

  • 01Workflow Studio. Build the flow on a visual canvas, with an AI agent step where judgment is needed. Start free →
  • 02Your own agent. Give Claude, ChatGPT or Cursor an engini MCP server with only these tools. MCP client setup →
  • 03The engini skill. Ask Flo in Claude Code or Codex and review its proposal. Install the skill →
[ 07 / Questions ]

Questions buyers ask before they start

Can new suppliers be created in SAP S/4HANA through an API?

Yes. SAP publishes a business partner OData service, and engini creates the business partner, its supplier role and its bank details through it, on a connection and SAP user your administrator sets up.

How are duplicates caught?

Before anything is prepared, the agent searches SAP business partners by tax ID and by similar name, and shows any matches on the review item so procurement can decide.

Who checks bank details before they are saved?

Procurement, on the review board. The create workflow runs only when someone sets the item to Ready. engini has no approval step of its own; the review is the status change on your board.

Can the same flow onboard customers?

Yes. The business partner service handles customers too; the second workflow creates the customer role instead of the supplier role.

Does this replace SAP Master Data Governance?

No. It automates the intake and keying around supplier creation. Teams that run SAP MDG keep it as their governance layer.