5. Supplier onboarding: from approval to transaction

The purpose of onboarding

During onboarding, Fluenta One creates a live, transaction-capable partner from the approved supplier. Until this process is complete, no order can be placed and no payment can be initiated.

Manual onboarding—PDFs via email, hand-collected signatures—can take weeks. In contrast, Fluenta One significantly shortens this lead time with automated workflows and real-time validation, especially for low-risk suppliers.

Supplier self-service portal and modular data collection

The process starts on the Fluenta One supplier portal: the buyer organization sends an invitation email, and the supplier provides their data on a structured interface.

Behind the portal operates a modular questionnaire library—not a single monolithic form, but modules automatically assembled according to the risk level, category, and regulatory area established during qualification:

Module
Content
For whom?
Basic module
Company information, financial data, basic compliance
All suppliers
Quality module
Quality management system, certifications, defect rates
Manufacturers
Cybersecurity module
SOC 2, ISO 27001, data handling
IT suppliers
ESG module
Carbon footprint, labor practices, diversity
Strategic suppliers
Regulatory module
GMP, AS9100, DORA/AML
Industry-specific
Financial health module
Audited statements, credit reports
High-risk suppliers

For example, a domestic office supply vendor sees the basic module and a simplified financial section; an international IT service provider gets expanded cybersecurity and regulatory modules.

Real-time validation and duplication check

During completion, Fluenta One performs real-time validation:

  • Tax number verification with government registries
  • Bank account number reconciliation with bank databases
  • Business license verification in regulatory registries
  • Company name comparison with sanctions lists

Errors surface immediately—not weeks later during a stuck payment.

The system also runs automatic duplication checks:

  • On exact match (tax number), onboarding stops and returns the already existing supplier
  • On similarity match (name), the case is routed to human review
  • If there's no match, creation continues

Approval process

During onboarding and qualification, Fluenta One applies a multi-step approval workflow:

  • Parallel and sequential approval branches
  • Conditional logic (e.g., different approvers by risk level)
  • Document attachment and versioning
  • Automatic forwarding and escalation mechanism

Status tracking is fully transparent—all stakeholders see where the process stands and what the next step is.

Due diligence execution and escalation

The due diligence level established during qualification (I–III) determines the scope and depth of checks executed during onboarding.

If a suspicious result emerges during checks—problematic bank account validation, negative media hit—the workflow automatically escalates the problem. Pre-approved escalation routes determine who investigates the signal and what the decision deadline is.

ERP activation and two-way integration

The final step of onboarding is ERP record activation, during which Fluenta One automatically performs:

  • Purchasing organization assignment
  • Payment terms and methods configuration
  • General ledger accounts and tax codes setup
  • Catalog content loading
  • Order channel activation
  • Status change to active

The system applies two-way, real-time integration toward the ERP via REST API or SAP RFC connection: data validated during onboarding (legal identifiers, tax data, bank data, payment terms, category codes, compliance status) synchronizes automatically without manual copying.

After sending data, Fluenta One waits for confirmation with the final master data identifier. This eliminates the "zombie record" problem: when the onboarding system marks the supplier as approved, but no active record is created in the ERP.

From this moment, the supplier profile is transaction-capable—orders can be placed and payments sent. Supplier master data, orders, goods receipt documents, invoices, and payment data continuously flow between the two systems.