Skip to content
Butterfly
Use case · Manufacturing · Document verification

DocumentFlow in document verification

The Turkey plant of an international cable manufacturer. A PoC for subcontractor and visitor entry.

13document types, each with its own rule set
e-DevletQR and barcode lookup
PoCin a live environment with real documents
5 minpending documents verified automatically
Problem

The challenges facing the organization

  1. For subcontractor and visitor entry, different documents were collected for each person, such as social security (SGK) declarations, criminal records, health reports and vehicle inspections.
  2. The HSE team checked document validity, age and training durations one by one, by hand.
  3. For sensitive documents, who made the decision and why it was approved were not kept in a single record.
Solution

How it was solved with Butterfly

The HSE team's rules were defined in Butterfly as document types. The system picks up pending documents every five minutes and runs the machine check for each type: e-Devlet barcoded documents are verified against the official service by reading the QR code, and documents such as vehicle inspections are verified from the report address in the external system. Documents that require human approval by rule go to the DocumentFlow review queue; the approval or rejection decision is written back to Butterfly automatically.

  • 13 document types: verification method, maximum document age, minimum training duration, review requirement
  • e-Devlet QR and barcode lookup, external system check
  • Mandatory human approval for sensitive documents
  • Decision, decision maker and note in a single record
Outcome

From the field, measured.

5 minautomatic verification cycle
13document types defined with rule sets
4/4live end-to-end test passed

The customer name is not shared for confidentiality reasons. Figures are taken from the organization’s records.

Do you have a similar process?