
A supplier sends an onboarding form, registration document and bank details in separate attachments. An administrator copies values into the ERP. Later, a revised form arrives with a different legal name. The useful automation is a reviewed proposal linked to its sources, with approved master data protected until the right person accepts the change.
This applies before invoice matching. Establishing the supplier record helps future processing, but an extracted form does not prove an identity, authorize a payment or verify a bank-account change.
Define the destination record before extracting fields
Start with the fields your purchasing or accounting system actually requires. Specify legal name, supplier identifier, relevant registration reference, address and contact fields under your existing onboarding policy. Separate required fields from optional information.
Name the person responsible for checking each field and approving creation. Your workflow should not collect unnecessary data simply because it appears in an attachment. Apply the organization's access and retention rules to source documents.
Store proposed and approved values separately
In a fictional supplier record SUP-082, the approved name is Atlas Components SARL. A revised form states Atlas Components Distribution SARL. Preserve the approved name, proposed name, source version and review status. Do not overwrite the existing record because the new form has a later file timestamp.
A reviewer may need another source, clarification or an authorized master-data process. Keep missing evidence visible. Similar names should trigger a review of the possible existing supplier, not an automatic merge.
If a registration document and form disagree, show both sources. An extraction confidence score does not decide which is authoritative.
Treat payment-detail changes as a separate approval process
The workflow may identify that a proposed bank field differs from the approved value. That finding must enter your established verification and authorization process. Reading an IBAN correctly is not proof that the account belongs to the supplier or that the request is legitimate.
Keep such changes from automatically reaching payment instructions. Use the responsible team's independently controlled procedure. Do not claim fraud detection because an extraction or comparison succeeded.
Access to sensitive source files should follow the controlled document workflow.
Confirm creation before closing the task
After approval, create or update the destination record using permitted access. Read it back and retain its identifier and confirmed values. If the response is uncertain, inspect the destination before repeating the operation.
A proposed supplier, approved proposal, attempted ERP update and confirmed supplier record are different states. Track them separately. Preserve the approval history and previous values so a later invoice exception can be traced.
For reference differences between sources, see document matching and exceptions. Once the supplier exists, the invoice-entry workflow covers the next operational stage.
Choose the smallest useful intake flow
If your ERP already offers supplier onboarding with suitable approval controls, use it. For low volume, a controlled form and review register may suffice. A custom flow becomes useful when attachments arrive through several channels, fields are copied repeatedly or versions lose their approval history.
Kaliits can scope intake, extraction, missing-field review and a controlled destination handoff. Identity verification, bank verification and payment authorization remain explicit responsibilities requiring appropriate procedures.
Test the changes that could damage the record
Use authorized samples with incomplete forms, conflicting names, duplicate submissions and revised documents after approval. Include a failed ERP response and a suspected existing supplier. Verify that no unapproved value overwrites the record and that a retry does not create another supplier.
Measure missing-field resolution, review time, confirmed record creation and unintended overwrites. Count savings only from observed work, with operating cost included.
For a Kaliits diagnostic, describe the incoming document types, fields copied, destination system and approval owner. A redacted example can identify the workflow gap without exposing live payment details.


