Reviewers
Sales datasales@yourco.com
Credit limitcredit@yourco.com
Taxtax@yourco.com
Master datamdm@yourco.com
Assigned reviewers
Decisions go to named owners or authorized teams, with reminders, and every email links back to the case.
SAP AI Agent · Business partner · Customer master Demo available
Automate SAP customer onboarding with governed AI agents.
Turn credit applications, ship-to lists and tax exemption certificates into complete SAP customers. The agent reads each document, checks for existing customers, sets up sold-to, ship-to and bill-to partners with sales area data, and creates the customer once sales, credit and tax have approved their parts.
- Human-approved
- ECC & S/4HANA
- SOC 2 Type II
- ISO 27001
New customer NC-0412 · Sales org 1000agent active
- 01Documents readCredit application, 3 ship-tos, tax certificateExtracted
- 02Duplicate checkSimilar name found · different tax IDClear
- 03Partners set upSold-to, bill-to and 3 ship-tosProposed
- 04ApprovalsSales ✓ · Tax ✓ · Credit pending2 of 3
- 05Create customerWaits for the credit limit decisionOn hold
Illustrative example · not a production transaction
Triggered by
New customer request
Reads
Credit applications, ship-to lists, tax certificates
Validates against
Existing customers and your rules
Writes to SAP
Customer business partner
Approved by
Sales, credit, tax
Runs on
SAP ECC · SAP S/4HANA
Why it matters
Slow customer setup delays the first order.
Sales waits days for a customer number while credit, tax and master data pass forms around, and mistakes show up later as blocked orders and tax errors.
- Slow setup
Days to the first order
Every new customer waits for several teams to fill in their part, one after another.Late first order → Frustrated sales → Lost deals - Duplicates
The same customer twice
A new spelling or address creates a second customer, splitting credit exposure and history.Split exposure → Credit risk → Messy reporting - Tax and address errors
Wrong tax status, wrong ship-to
Exemption certificates and addresses are retyped, so invoices go out with the wrong tax or to the wrong dock.Tax errors → Credit notes → Disputes
How it works
Read. Validate. Decide. Act.
The same four steps as every Artificio agent. The agent does the research and the paperwork; your teams make the decisions.
- 01 · Read
Read the documents
Credit applications, ship-to lists, tax exemption certificates and setup forms.
- Legal name, addresses, contacts and tax status extracted
- Ship-to lists from Excel or PDF read in one go
- 02 · Validate
Check against SAP
Checks for existing customers and validates addresses and tax data.
- Duplicate check on name, address and tax ID
- Exemption certificates checked for state and expiry
- 03 · Decide
Set up partners and route
Proposes sold-to, ship-to and bill-to partners with sales area data.
- Values proposed from your rules and similar customers
- Sales, credit and tax approve their own fields
- 04 · Act
Create the customer
Creates the business partner with all partner functions once approved.
- Sales area and partner functions created together
- Field-level change log for later changes
Worked example
A new customer with three ship-tos, from documents to approval.
Sales sends a signed credit application, a list of three ship-to addresses and a resale certificate. Here is what the agent sets up before anyone opens SAP.
New customer NC-0412 · Harbor Equipment Co.Extracted
- Legal name
- Harbor Equipment Co.credit app
- Bill-to
- 55 Pier St, Portland ORcredit app
- Ship-tos
- 3 addresses in OR, WA and IDExcel
- Tax status
- Resale exemption, WA, valid to 2028certificate
- Credit requested
- USD 150,000credit app
- Trade references
- 3 providedcredit app
No duplicate customer1 similar name
Harbor Equip. Inc. exists in sales org 2000 but has a different tax ID and address, so it is shown for information only.
Proposed customer setupProposed
| Field | Proposed | Why |
|---|---|---|
| Partners | SP, BP, 3 × SH | Sold-to and bill-to at Portland; one ship-to per address |
| Sales area | 1000 / 10 / 00 | Requested by sales org 1000 |
| Customer group | 02 · Distributors | From the credit application |
| Payment terms | N030 | Your default for new distributors |
| Tax classification | Exempt for WA ship-to only | The certificate covers Washington only |
| Credit limit | USD 100,000 | Your new-customer cap; USD 150,000 requested |
- Sales dataSales repApproved
- TaxTax teamApproved
- Credit limitCredit managerWaiting
The customer is created only after credit decides the limit. Each approval is tied to the values the approver saw.
Illustrative example · names and values are fictional and depend on your SAP configuration
Inside the platform
Every case is traceable from start to finish.
The case shows who it is waiting for, what happens next, what the agent checked and exactly what each person is approving.
NC-0412 · Harbor Equipment Co. · Sales org 1000
Requested by Sales · started Mon 2 Nov, 13:15 · agent version v2
Waiting for creditDocumentsAuditRe-assess
RequestChecksApprovalsCreate in SAP
Now
Waiting for D. Brooks (Credit manager) to set the credit limit, asked Mon 2 Nov at 13:31.
Next
A reminder goes out tomorrow at 13:31. Sales wants to book the first order on Thursday.
| Section | Approver | Status |
|---|---|---|
| Sales and partners | J. Ruiz · Sales | Approved |
| Tax classification | K. Lee · Tax | Approved |
| Credit limit | D. Brooks · Credit | Waiting |
| Create customer | Agent | On hold |
Question for D. Brooks
Approve a credit limit of USD 100,000, your new-customer cap? The customer requested USD 150,000.
Approve 100,000Change the limitAnswer as authorized delegate
- If a certificate is missing or expired
Taxable until it's valid
The ship-to is set up as taxable and tax is asked to follow up, instead of guessing an exemption. - If the customer already exists
Extend, don't duplicate
The agent proposes extending the existing customer to the new sales area instead of creating another. - If SAP rejects the posting
The case stays open
SAP's message is recorded on the case so the data can be corrected and the posting retried.
Recreation of the Artificio case screen · names and values are fictional
Capabilities
Customer onboarding with governance built in.
Every new customer goes through the same checks before the first order.
- Capture
Setup documents
Credit applications, ship-to lists and tax certificates from email or a form. - Prevent
Duplicate detection
Matches on name, address and tax ID across sales areas. - Partners
Partner functions
Sold-to, bill-to, payer and ship-to partners set up together. - Tax
Exemption checks
Certificates checked for state and expiry before a ship-to is marked exempt. - Credit
Credit at the door
Credit limit decided by credit before the first order. - Audit
Field-level change log
Every value at creation and every later change, with who and when.
Ownership
Each part of the customer goes to the team that owns it.
You name an approver for each part of the customer record. Whoever answers first decides, and anything without an owner goes to the master data team.
- Sales
Sales area data
Sales org, customer group and pricing. - Credit
Credit limit
Credit limit and risk category. - Tax
Tax status
Exemptions and tax classification. - Finance
Payment terms
Terms and reconciliation account. - Logistics
Ship-tos
Delivery addresses and shipping conditions. - Requester
Business need
Why the customer is needed. - Customer
Missing documents
Forms and certificates that are missing. - Master data
Exceptions
Duplicates, rejected postings and a weekly summary.
Owners, rules and tolerances are configured to your organization and agreed for each deployment.
Controlled autonomy
Start with human oversight. Automate only when ready.
The agent proves itself on your real work before it writes anything to SAP. The platform measures how often your people agree with it, so you decide when to give it more room, case type by case type.
- Step 1Where every agent starts
Shadow mode
The agent proposes every action but writes nothing to SAP. Your people decide, and each answer counts toward the agreement rate.
- Step 2
Approve, then act
The required owners approve. The agent acts in SAP only when the last approval lands.
- Step 3
Act by approved rule
For case types you explicitly configure and approve, such as adding a new ship-to address for an existing customer, the agent acts on its own and reports back.
Agreement with the agent · by case typeIllustrative
New ship-tos for existing customers97%
Domestic customers84%
Customers with tax exemptions71%
- Approval rules are enforced by the platform, whatever the agent's instructions say
- No customer is created while a duplicate or credit question is open
- SAP credentials never reach the agent or its instructions
- Every value carries its source; approved values are locked
Governed agent runtime
Shared platform controls across every Artificio agent.
What makes this agent different is its configuration: its instructions, the tools it may use and the policies it works under. Reviewers, approvals, versions and audit work the same way for every agent you add.
Tools
Check for duplicate customersRead
Check exemption certificateRead
Record an approvalRead
Create customer in SAPAction
Read tools and Action tools
Gathering data is kept separate from changing SAP. Action tools are controlled and can require human approval before they run.
Instruction versions
v3ActiveTolerances updated
v2New plant added
v1Created from blueprint
Versioned instructions
Versions can't be edited, and each case keeps the version it started with, so a change never alters work in progress.
Recreations of Artificio platform screens
What we measure
Results you can see in your own numbers.
Every pilot tracks the same four measures from day one, so the business case comes from your data, not ours.
Time to first order
From request to customer ready for orders.Duplicates prevented
Requests matched to existing customers instead.First-pass completeness
Customers created with all partners and data approved.Tax setup accuracy
Ship-tos whose tax status is backed by a valid certificate.
For SAP teams
Integrates with SAP ECC and S/4HANA through standard interfaces.
The agent reads and writes data through supported SAP interfaces, without modifying standard SAP objects and without replacing your existing governance.
Reads from SAP
| Customers | Existing business partners for duplicate checks |
|---|---|
| Configuration | Sales areas, customer groups, payment terms |
| Credit | Credit segments and existing exposure |
| Tax | Tax classifications and jurisdictions |
Writes to SAP
| S/4HANA | API_BUSINESS_PARTNER (OData) |
|---|---|
| ECC | Customer master through a supported interface |
| Documents | Setup documents linked where configured |
| Responses | Every SAP response recorded on the case for resolution or retry |
ScopeThe exact interfaces, objects and fields in scope are confirmed for your SAP release and deployment during technical discovery. S/4HANA Cloud Public Edition is reviewed case by case, and some landscapes may need additional configuration.
Pilot approach
Start with one sales org and a measurable scope.
A focused pilot in your QA or sandbox system proves the agent on your own data before anything reaches production.
- Phase 1
Connect
Review SAP edition, interfaces, authorizations and representative data.
- Phase 2
Configure
Agree one sales org, the customer types, rules and approvers.
- Phase 3
Pilot
Run real requests in shadow mode, including duplicates and tax exemptions.
- Phase 4
Expand
Review the four measures, then add sales orgs, customer types and autonomy.
Frequently asked questions
Questions SAP teams ask.
Which documents can it read?
Credit applications, ship-to lists in Excel or PDF, tax exemption and resale certificates, and setup forms, from email or a web form.
Can it set up several ship-to addresses at once?
Yes. A ship-to list is read in one go, and each address becomes a ship-to partner, checked against existing addresses.
How are tax exemptions handled?
Each certificate is checked for state and expiry. Only ship-tos covered by a valid certificate are marked exempt, and tax approves before the customer is created.
Who sets the credit limit?
Your credit team. The agent proposes a limit from your rules and the application, and the credit manager approves or changes it.
What if the customer already exists?
The agent shows the existing customer and proposes extending it to the new sales area instead of creating a duplicate.
Does the Customer Onboarding Agent write to SAP without approval?
Not by default. Every agent starts in shadow mode, where nothing is written to SAP. After that, the required owners approve before the agent acts. Automatic action is only possible for cases you explicitly configure and approve.
Which SAP versions are supported?
SAP ECC and SAP S/4HANA. The exact interfaces and scope are confirmed for your release and deployment during technical discovery; S/4HANA Cloud Public Edition is reviewed case by case.
Security & compliance
Enterprise security across every agent
ISO 27001:2013 certified, SOC 2 Type 2 compliant, GDPR and HIPAA ready. Every agent action is logged and auditable, and SAP credentials stay in the platform's integration accounts.
- ISO 27001:2013
- SOC 2 Type II
- GDPR ready
- HIPAA ready
See it working
Two ways to get started.
Request demo
See a new customer go from credit application and ship-to list to an approved customer with partner functions, using sample data.
Request demoDiscuss an SAP pilot
Scope a pilot on one sales org and a defined set of customer types in your SAP QA or sandbox system, with the four measures agreed up front.
Discuss an SAP pilot