Know who you're selling to before you quote.
A stranger asks for a quote. KYB, screening, and credit run from first contact — the SAP or Infor record exists only after every gate clears.
Illustrative run — sample data, not a customer record.
Customer onboarding automation for SAP S/4HANA and Infor M3
Four gates, one flow: KYB, denied-party screening, credit, then the business-partner record in SAP or Infor. Every verdict is stamped into the ledger — a record of every decision: what changed, who approved it, when.
A stranger in. A customer out.
01The request lands
A new account writes to the shared inbox — or sends a first PO over EDI. Corin reads it where it lands; the request is the trigger, not a ticket someone files later.
02KYB / KYC
The business is verified — registry data, ownership, addresses — matched against the documents that came with the request.
03Export screening
Denied-party and end-use screening on the counterparty and the transaction, before anything is quoted.
04Credit
A credit report and a proposed limit, grounded in bureau data — written as policy for every decision that follows.
05ERP master creation
The cleared customer is created in SAP or Infor with its screening record attached. No swivel-chair keying, no skipped step.
Screening is not optional paperwork.
Export violations are priced in public — and the screening that prevents them is usually a manual step between the inbox and the ERP, exactly where it gets skipped. Corin screens at onboarding, at quote, and at order.
Named sources, policy-gated.
KYB, credit, screening, and trade-credit signals run against named providers — every call policy-gated, every result filed with its reason codes on the ledger row.
Provider lineup from Corin's MCP catalog, snapshot August 2026. Tiers and vendor status are badged on the integrations pages.
Every order screened. Every decision proven.
Screening is not a separate step — it runs inside every Corin loop, at quote and at order. A hit stops the transaction at a human gate with the match and the reasoning attached.
- At quote
- Denied-party and end-use screening before a price leaves the building — not after the order is already booked.
- At order
- The same screening at order entry — the last cheap moment to stop a bad transaction.
- Rescreening
- Lists change daily. The customer master is rescreened on every update, not once at onboarding and never again.
Three checks, one held line.
Every transaction runs the same screening set. A hold stops the line and shows you the match — and what to do about it.
Illustrative screening run — a sample check set, not a customer record.
11:20 — a stranger's RFQ. 11:26 — a cleared customer.
11:20
an email from a company nobody has heard of asks for a quote on 400 units.
11:21
KYB runs — registry data, ownership, addresses — matched against the documents that came with the email.
11:22
denied-party and end-use screening: the counterparty is clear; one part is dual-use and needs an end-use statement.
11:25
a D&B report and a proposed credit limit wait on a decision card. Ana approves with the limit she wants.
11:26
the customer master is created in the ERP with its screening record attached — and every quote and order after this one is screened as it happens.
An illustrative morning in onboarding — sample data, not a customer record.
Built for compliance and the ERP team.
- New accounts clear in minutes, not days — the quote doesn't wait.
- A screening hit stops the transaction with the match and the reasoning attached, not in a queue.
- One request starts the whole chain; nobody re-keys anything into the ERP.
- KYB, screening, and credit run as versioned Procedures with named owners.
- The customer master is created through released APIs with the screening record attached.
- Rescreening on every list change — every verdict lands on the ledger with its reason codes.