Published

Procurement approves a supplier's replacement insurance certificate in FormKiQ. The enterprise resource planning (ERP) system needs the accepted document attached to the supplier record so its users can complete their checks. Emailing a file leaves both teams asking the same questions: is this the reviewed version, does it belong to this supplier, and did the receiving system accept it?
Connect the handoff to the document review. Agree which approved documents may be sent, which supplier record receives them, and what confirms receipt. Keep failed or uncertain deliveries visible to an owner who can resolve them.
Procurement checks the certificate and records the document decision in FormKiQ.
The configured integration uses the approved supplier mapping and destination.
Track ERP receipt, rejection or an unresolved delivery, with follow-up where needed.
FormKiQ holds the governed supplier evidence and review history. The ERP continues to own its supplier master record and operational decisions, such as whether a supplier may receive purchase orders or payment. An approved certificate is one input to those decisions.
| Question | Example agreement | Why it matters |
|---|---|---|
| Which supplier? | Use the confirmed relationship between the FormKiQ supplier file and ERP supplier record. | Similar supplier names should not send evidence to the wrong record. |
| Which document? | Send the accepted insurance certificate with its document identity and reviewed version. | A later upload should not silently replace the version approved for this handoff. |
| Which audience? | Share the certificate with the authorised procurement process. | The ERP does not need every document, internal comment or unrelated department record. |
| What counts as delivered? | Record the receiving system's reference and agreed acceptance response. | Sending a file and attaching it successfully to the ERP supplier record can be separate steps. |
| Who handles exceptions? | Assign rejected or uncertain deliveries to a named integration owner. | Procurement can see what still needs attention without assuming the handoff completed. |
The same organisation may connect Procurement documents to an ERP, employee records to an HR system, and claim evidence to a claims platform. Each connection needs its own permitted documents, audience and destination. Permission to send supplier certificates should not also permit sending employee files.
FormKiQ sites can separate departments, business use cases or customer tenants. Configure the integration around those boundaries and the applicable document permissions. For a SaaS provider serving multiple customers, also keep each customer's records and destinations separate. A destination supplied in a request still needs to match the approved connection.
The supplier solution's VEN-1042 example follows Example Facilities Services through an insurance renewal. Here is how a configured ERP handoff could follow that review.
The supplier file shows that current insurance evidence needs renewal. Procurement requests the replacement and keeps responsibility for following up.
Procurement adds Insurance-renewal.pdf. An authorised reviewer checks the document and records acceptance or rejection. A rejected certificate leaves the renewal unresolved.
After acceptance, the configured integration selects that document version and the mapped ERP supplier record. Earlier certificates remain in the governed supplier file; they are not included simply because they belong to VEN-1042.
If the ERP accepts the attachment, retain its reference with the handoff record. If the supplier mapping is missing or the response is uncertain, flag the delivery for the integration owner. Check whether the first attempt succeeded before sending a duplicate.
The ERP's responsible owner decides whether its remaining supplier checks are complete. FormKiQ retains the certificate review and earlier evidence, with the next renewal tracked through the supplier workflow.
A certificate may be corrected after delivery, or an ERP supplier record may be merged or closed. Agree whether the receiving system replaces an attachment, retains both versions or needs a new review. Keep the earlier delivery and its outcome explainable. The supplier-record merge guide follows duplicate ERP accounts into a continuing supplier file, preserving earlier references, document scope and unresolved evidence requests.
When an integration ends, stop new transfers and check work already waiting to run. Documents already delivered have their own access and retention responsibilities in the receiving system. Removing the connection does not recall those copies.
If the integration uses resources in another AWS account, configure access for the approved source, destination and operations. Where a third-party service acts for multiple customers, AWS's external-ID guidance helps prevent that service from using one customer's access for another. This is called the confused deputy problem.
Test the permitted transfer and attempts to use another department's or customer's connection. Also verify how access ends for both new requests and existing sessions. The vendor-access guide covers that AWS operating detail. These controls support the agreed document-sharing workflow.
A supplier-document integration connects a reviewed piece of evidence to the business record that needs it. Keep the supplier mapping, accepted version, intended audience and receiving outcome visible so Procurement and ERP teams can explain what was shared and what still needs attention.
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.