Routty can use business partners imported from your ERP or created automatically from document data. Both can exist in the same tenant. Imported masterdata is checked first; automatic generation is a fallback when no imported partner matches.
Imported and generated business partners
-
Imported masterdata contains customer and supplier records supplied through CSV imports or the masterdata API. Use it when the ERP controls partner numbers, identifiers, and other reference data.
-
Generated business partners are created from document content when generation is enabled and no matching partner is available. They are separate from imported masterdata.
Company masterdata is still required to identify your own companies. Enabling customer or supplier generation does not create your tenant's companies.
How Routty selects a business partner
-
Extract identifiers from the document and look for an enabled imported business partner in the correct tenant, company group, partner type, and Test or Production environment.
-
If an imported partner matches, use it. This takes precedence even when generation is enabled.
-
If no imported partner matches, check whether generation is enabled for the relevant customer/supplier type and environment.
-
When generation is enabled, reuse a matching enabled generated partner. If none matches, create a partner from the document data, subject to the configured extraction and validation rules.
-
When generation is disabled, stop with a business-partner determination error if no imported partner matches. Existing generated partners are not used as a fallback in that case.
|
Imported partner matches |
Generation enabled |
Result |
|---|---|---|
|
Yes |
Either setting |
Use the imported partner. |
|
No |
Yes |
Reuse a matching generated partner, or generate a new one if the document contains valid data. |
|
No |
No |
Business partner not found; correct the masterdata or generation settings. |
Customer, supplier, and environment settings
Automatic generation is controlled independently for customers and suppliers, and separately for Test and Production. The partner type associated with the document type determines which setting applies.
|
Partner type |
Test |
Production |
|---|---|---|
|
Customers |
Generate Unknown Customers — Test |
Generate Unknown Customers — Production |
|
Suppliers |
Generate Unknown Suppliers — Test |
Generate Unknown Suppliers — Production |
Ask your implementation partner to review these features on the tenant's Features tab. The former tenant-level Partner masterdata switch is no longer used.
Disabling generation prevents generated partners of that type and environment from being selected or newly created. It can also hide those generated records from relevant lists; it does not delete them. Imported masterdata remains available.
When an output connector requires masterdata
An output connector configuration can have Require masterdata enabled. If the selected partner is generated rather than imported, the route cannot proceed through that configuration. Enabling generation alone does not satisfy this requirement.
Keep this requirement enabled for integrations that need ERP-controlled partner records. Import the missing partner into the correct company group, type, and environment before reprocessing. Only relax the requirement when the receiving integration is designed to accept generated partners.
Example: imported customers and generated suppliers
-
Import your companies and customer masterdata from the ERP.
-
Keep customer generation disabled if every customer must exist in the ERP.
-
Enable supplier generation in Test. A known imported supplier is still selected first; an unknown supplier can be generated from a valid document.
-
Check the generated identifiers, names, addresses, routing, and the output configuration's Require masterdata setting.
-
After validating the integration, enable supplier generation in Production if required. Production has its own setting; enabling Test does not enable Production.
Resolving matching problems
-
Check the tenant, company group, customer/supplier type, Test/Production environment, identifiers, and whether the partner is enabled.
-
For BusinessPartnerNotFound, import or correct the partner, or review the relevant generation feature with your implementation partner.
-
If generation fails, inspect the document audit logs and extracted document data. Enabling the feature cannot compensate for missing or invalid data.
-
If an output configuration rejects a generated partner, check Require masterdata.
-
After correcting the cause, reprocess the affected document and confirm the selected partner in its audit trail.