Published

Procurement discovers two ERP accounts for the same supplier. One holds the current insurance certificate; the other is referenced by an older agreement and an open request for updated evidence. The master-data team approves a merge into one current account. What should staff see when they next open that supplier's documents?
Connect the current account to the governed supplier file while preserving the earlier references and decisions. Confirm what the source-system change means, review the documents and unfinished work, and verify the resulting access and retrieval paths. An ERP merge alone should not silently combine document permissions, accept a certificate for a wider scope or remove history.
A display-name correction, a replacement number and a duplicate-account merge answer different questions. Obtain the approved change from the system or owner responsible for supplier identity. Record the source system, business unit, old and current account references, reason and effective point. Do not infer that two records are the same supplier because their names look alike.
| Source change | What to establish | Document treatment |
|---|---|---|
| Display name corrected | The account still represents the same supplier and scope. | Update the agreed display value; preserve the name printed on earlier documents. |
| Account number replaced | The source confirms that the old and new numbers identify the same continuing record. | Retain the earlier reference and add the approved current mapping. |
| Duplicate accounts merged | The surviving account, both prior document populations, scope differences and unresolved work. | Review the continuing relationship and access; keep each document's identity and history. |
| Accounts represent different parties or are split | Which party and activity each agreement, certificate and request actually concerns. | Resolve associations explicitly; do not send all documents to one account by default. |
The same supplier number can exist in different ERP environments or business units. Keep that context with the mapping. If a retired number can later be reused, historical lookup also needs the applicable period and change history. A bare number is insufficient to select a confidential document file.
FormKiQ's entity model supports reusable business records linked to documents. The supplier relationship can therefore remain meaningful while the integration records a changed external account reference. Each agreement or certificate still has its own document identity, versions, dates and review state.
Choose explicitly whether a mapping changes, a document relationship is corrected or two existing supplier files need coordinated review. If both accounts already have separate FormKiQ supplier records, changing an external number does not by itself settle how those files should be treated. Retain the source associations and the approved outcome of that review.
Preserve the supplier and account references captured when earlier documents were issued or accepted. A current lookup may lead staff to the continuing supplier file while the original agreement still names the former reference. That is explainable history, not a reason to rewrite the agreement or create a fresh copy of every document.
Identify the authoritative change and the exact accounts, business context and documents affected.
Preserve earlier references and resolve document scope, access and outstanding work.
Test current and historical retrieval, document outcomes and permitted access.
This fictional integration extends the VEN-1042 supplier workflow. The ERP master-data owner confirms that accounts 4108 and 9821 are duplicates for Example Facilities Services in the same business unit. Account 9821 will remain current. The document file contains evidence used for two campus contracts; this consolidation does not itself change either contract's requirements.
The owner supplies the old and current references, business unit, effective point and reason. Procurement links that decision to VEN-1042. A similarly named supplier in another business unit stays outside the change.
The reviewer finds the accepted north-campus insurance certificate, the earlier south-campus agreement and an open request for south-campus evidence. The certificate's accepted scope does not establish that it satisfies the second contract. The request remains owned and unresolved.
The configured integration connects current ERP account 9821 to the reviewed supplier relationship. Earlier documents retain the source reference used at the time. Any change to a separately created supplier entity or document association follows its recorded review decision rather than a blanket number replacement.
The north-campus buyer can retrieve the evidence permitted for that role, while restricted south-campus material remains controlled. The integration reconciles a delayed message carrying account 4108 against the confirmed mapping and source history. Its configured handling prevents the message from silently recreating the retired account relationship or repeating a completed document transfer.
The owner verifies the agreed current and historical lookups, document identities and retained decisions. The south-campus evidence request still appears as open. The merge review can record the outstanding action and its owner without describing the supplier as fully qualified for every contract.
Documents linked to one supplier can serve different departments, contracts and business activities. Customer tenants may add another boundary. A merged ERP view should return only the documents the viewer may access, including through search, direct links and exports. Joining account references must not implicitly join the audiences for restricted records.
Keep holds, retention decisions and document review outcomes attached to the records they govern. Do not infer that the newest certificate supersedes every earlier certificate or that one account's approved status applies to all activities. Any deliberate change in scope needs its own authority and evidence.
For repeated, late or rejected updates, use the ERP integration guide's reconciliation approach. If a mapping was wrong, inspect the document associations, access changes and transfers already made before applying a correction. Merely restoring the earlier number cannot recall a copy already sent elsewhere.
The metadata-schema guide covers changing field definitions and migrating stored values. The folder-move guide covers document links during reorganisation. This merge decision concerns which continuing supplier relationship those records represent.
A supplier merge should leave staff with a clear current relationship and an understandable history. Confirm the business identity decision, preserve earlier references and verify the documents and access that follow it. Keep outstanding evidence work visible so account consolidation is not mistaken for supplier qualification.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.