Document to Data

    Customer documents read and checked before they reach your system.

    Lookdocu reads ID cards, tax IDs and bank statements, matches the NIK against the written details, checks bank statement balances, and can redact personal data before documents are shared.

    The problem

    Customer data is typed by hand and personal documents circulate unredacted.

    • ID card, tax ID and bank statement data is retyped by staff.
    • A mistyped NIK or name is caught only at a later stage.
    • Documents with NIK, family card, tax ID and account numbers are shared unredacted.

    How it works

    1. 1

      Receive documents

      Customer documents are uploaded in the app or sent from the onboarding system through the API.

    2. 2

      Read and check

      Data is read into fields, the NIK is matched against the written details, and bank statement balances are checked.

    3. 3

      Redact personal data

      NIK, family card, tax ID and account numbers can be redacted before documents are shared.

    4. 4

      Staff decide

      Staff review flagged data and run official verification under the company's procedures.

    In use

    Real deployments related to this use case.

    Questions

    Is reading an ID card the same as verifying identity?

    No. Lookdocu reads and checks what the document says. Identity verification against official population data is a separate process through authorized channels.

    How is personal data protected?

    The Redact Personal Data module redacts NIK, family card, tax ID and account numbers, so documents can be shared without exposing personal data.

    Start with one use case.

    Tell us which process you want to test.

    Discuss your use case