🚀 Laiye ADP Global Document Intelligent Extraction · Fast

Developed by the ADP Intelligent Document Processing team of Laiye Technology. Tailored for global cross-border finance, automation, system integration and high-concurrency production scenarios, it delivers low-latency, high-throughput, full-format and multi-language intelligent extraction for invoices, bills and receipts. It fully supports structured standard documents, unstructured overseas purchase invoices and receipts. Whether it is electronic PDFs, scanned copies or images, each page can be parsed and output as standardized JSON structured data in as fast as 5 seconds. It supports enterprise-level batch processing and 7×24 stable service, empowering end-to-end workflow automation, intelligent reconciliation and data warehousing.

⭐ Core Advantages of High-Speed Edition

⚡ Ultra-fast Processing: Each page is parsed within 5 seconds. It supports large-scale concurrent calls to meet high-intensity processing requirements in production environments.
✅ Enterprise-grade High-throughput Architecture: Low-latency response and stable processing for massive files.
🌐 Multi-language Support: Recognizes invoices and receipts in English, Japanese, Korean, German, French, Thai and hundreds of other languages.
📄 Full-format Compatibility: Adapts to VAT invoices worldwide, tax documents from Southeast Asia, unstructured receipts and mixed-format vouchers.
🎯 Over 99% Extraction Accuracy: Accurately extracts key fields and greatly reduces costs for manual verification, translation and data entry.
🤖 Continuous AI Optimization: The model keeps iterating and improving based on business data, and supports customized adaptation for enterprises.

📌 Application Scenarios

Quick Start Guide

Core Workflow

1. Install dependencies: On first run, install the ADP CLI tool.
2. Authentication setup: On first run, execute adp config get to check credentials. If not configured, prompt the user to provide an API Key.
3. Get app list: On first run, retrieve the out-of-the-box app list via adp app-id list --app-type 0, find the invoice extraction app, and record its app_id (prefixed with ootb_). For subsequent runs, prefer adp app-id cache.
4. Execute extraction: Run adp extract url \x3CURL> --app-id \x3Cinvoice-app-id> or adp extract local \x3Cfile-path> --app-id \x3Cinvoice-app-id>.
5. Process results: Parse the returned JSON to extract structured fields such as invoice number, date, supplier, buyer, currency, tax amount, total amount, and line items.
6. Error handling: When a command fails, parse the stderr JSON to determine the error type and recovery action.

Scenario-to-Command Mapping

Single Invoice Recognition

Batch Recognition

Async Processing

Concurrency Limit: Free users support a maximum of 2 documents for concurrent processing, while paid users support up to 10 documents concurrently.

Step 1: Install ADP CLI

# Method 1: npm (recommended, cross-platform)
npm install -g @laiye-adp/agentic-doc-parse-and-extract-cli

# Method 2: Shell script (Linux / macOS, when npm is unavailable)
curl -fsSL https://raw.githubusercontent.com/laiye-ai/adp-cli/main/scripts/adp-init.sh | bash

# Method 3: PowerShell script (Windows, when npm is unavailable)
irm https://raw.githubusercontent.com/laiye-ai/adp-cli/main/scripts/adp-init.ps1 | iex

Or download prebuilt binaries from GitHub Releases.

Step 2: Get API Key & Configure Authentication

Register and obtain an API Key (100 free credits per month + limited-time bonus: 1,000 free invoice extraction pages):

• Global (all other regions): https://adp-global.laiye.com/
• China Mainland, Hong Kong, Macau, and Taiwan: https://adp.laiye.com/

adp config set --api-key \x3Cyour-api-key>
adp config set --api-base-url https://adp.laiye.com
adp config get

Step 3: Get the Invoice Extraction App ID

ADP provides out-of-the-box built-in extraction apps for global invoices/receipts, supporting multiple languages and currencies with no additional configuration required.

App Types

ADP apps are divided into two categories, distinguished by the app_type field:

Invoice recognition is an out-of-the-box app and can be queried using --app-type 0.

Query and Filter Invoice Apps

# Query OOTB apps only (recommended)
adp app-id list --app-type 0

# Or query all apps
adp app-id list

Find the app whose app_label contains "Invoice", "Receipt", "high accuracy", high-speed extraction in the returned list, and record its app_id:

[
  {
      "app_id": "ootb_*****d9e2",
      "app_label": [
        "Invoice",
        "Receipt",
        "global invoices",
        "high accuracy",
        "high-speed extraction"
      ],
      "app_name": "Invoice/Receipt",
      "app_type": 0
    }
]

In the example above, "app_id": "ootb_*****d9e2" is the global invoice extraction app. app_type of 0 indicates an out-of-the-box app; 1 indicates a custom app.

Cache App ID (Recommended)

After the initial query, prefer using cache for subsequent requests to avoid redundant API calls:

# Use cache for subsequent calls
adp app-id cache

Important: Each account's app_id is unique and fixed — it will not change unless the user explicitly deletes the app. It is recommended that the Agent save the invoice app's app_id in context and reuse it directly in subsequent calls.

Step 4: Execute Invoice Extraction

Single Invoice Extraction (URL)

adp extract url https://example.com/invoice.pdf --app-id \x3Cinvoice-app-id>

Single Invoice Extraction (Local File)

adp extract local ./invoice.pdf --app-id \x3Cinvoice-app-id>

Single Invoice Extraction (Base64)

adp extract base64 \x3Cbase64-string> --app-id \x3Cinvoice-app-id> --file-name \x3Cfilename.ext>

Response Example

ADP automatically supports invoice recognition in 100+ languages across all regions globally and automatically detects currencies. Extraction results are returned as unified structured JSON. The response contains two types of fields: regular fields and table fields (line items).

The following example is a simplified format showing only core fields. The full response also includes field_confidence (confidence score) and references (source location) metadata — see "Common Field Structure" below for details.

[
  {
    "field_key": "invoice_number",
    "field_name": "Invoice Number",
    "field_values": [
      {
        "field_value": "INV-2026-003721"
      }
    ]
  },
  {
    "field_key": "invoice_date",
    "field_name": "Invoice Date",
    "field_values": [
      {
        "field_value": "2026-03-15"
      }
    ]
  },
  {
    "field_key": "due_date",
    "field_name": "Due Date",
    "field_values": [
      {
        "field_value": "2026-04-15"
      }
    ]
  },
  {
    "field_key": "currency",
    "field_name": "Currency",
    "field_values": [
      {
        "field_value": "USD"
      }
    ]
  },
  {
    "field_key": "supplier_name",
    "field_name": "Supplier Name",
    "field_values": [
      {
        "field_value": "Acme Global Trading Co., Ltd."
      }
    ]
  },
  {
    "field_key": "supplier_address",
    "field_name": "Supplier Address",
    "field_values": [
      {
        "field_value": "1234 Commerce Blvd, Suite 500, San Francisco, CA 94105, USA"
      }
    ]
  },
  {
    "field_key": "buyer_name",
    "field_name": "Buyer Name",
    "field_values": [
      {
        "field_value": "Eastern International Trading Co., Ltd."
      }
    ]
  },
  {
    "field_key": "buyer_address",
    "field_name": "Buyer Address",
    "field_values": [
      {
        "field_value": "1000 Lujiazui Ring Road, Pudong New Area, Shanghai"
      }
    ]
  },
  {
    "field_key": "subtotal",
    "field_name": "Subtotal",
    "field_values": [
      {
        "field_value": "8,500.00"
      }
    ]
  },
  {
    "field_key": "tax_amount",
    "field_name": "Tax Amount",
    "field_values": [
      {
        "field_value": "680.00"
      }
    ]
  },
  {
    "field_key": "total_amount",
    "field_name": "Total Amount",
    "field_values": [
      {
        "field_value": "9,180.00"
      }
    ]
  },
  {
    "field_key": "line_items",
    "field_name": "Line Items",
    "field_confidence": 0.98,
    "table_values": [
      [
        {
          "field_name": "Description",
          "field_key": "line_items_description",
          "field_values": [
            {
              "field_value": "Industrial Sensor Module X200"
            }
          ]
        },
        {
          "field_name": "Quantity",
          "field_key": "line_items_quantity",
          "field_values": [
            {
              "field_value": "50"
            }
          ]
        },
        {
          "field_name": "Unit Price",
          "field_key": "line_items_unit_price",
          "field_values": [
            {
              "field_value": "120.00"
            }
          ]
        },
        {
          "field_name": "Amount",
          "field_key": "line_items_amount",
          "field_values": [
            {
              "field_value": "6,000.00"
            }
          ]
        }
      ],
      [
        {
          "field_name": "Description",
          "field_key": "line_items_description",
          "field_values": [
            {
              "field_value": "Connector Kit CK-50 (Pack of 100)"
            }
          ]
        },
        {
          "field_name": "Quantity",
          "field_key": "line_items_quantity",
          "field_values": [
            {
              "field_value": "25"
            }
          ]
        },
        {
          "field_name": "Unit Price",
          "field_key": "line_items_unit_price",
          "field_values": [
            {
              "field_value": "100.00"
            }
          ]
        },
        {
          "field_name": "Amount",
          "field_key": "line_items_amount",
          "field_values": [
            {
              "field_value": "2,500.00"
            }
          ]
        }
      ]
    ]
  }
]

Extraction Field Reference

Note: field_key and field_name are always returned in English. field_value is multilingual — its content reflects the language of the source document (e.g., Chinese invoices return Chinese values, Japanese invoices return Japanese values). Different regions/types of invoices may return different field sets — the following lists all known fields.

Regular Fields:

Table Fields (Line Items):

Common Field Structure

Each field object contains the following properties:

How to distinguish field types: If table_values is present → table field, read from table_values; otherwise → regular field, read from field_values.

Step 5: Batch Processing & Async Mode

Batch Processing (Local Folder)

adp extract local ./invoices/ --app-id \x3Cinvoice-app-id> --export ./results/ 

Response summary:

{
  "total": 10,
  "success": 9,
  "failed": 1,
  "output_dir": "/absolute/path/to/results",
  "files": [
    {
      "input": "invoice-001.pdf",
      "output": "invoice-001.pdf.json",
      "status": "success"
    },
    {
      "input": "invoice-002.pdf",
      "output": "invoice-002.pdf.json",
      "status": "success"
    },
    {
      "input": "damaged.pdf",
      "output": "damaged.pdf.error.json",
      "status": "failed",
      "error": "File is corrupted or unreadable"
    }
  ]
}

Batch Response Summary Fields:

Async Processing

# Submit async task
adp extract url https://example.com/invoice.pdf --app-id \x3Cinvoice-app-id> --async

# Query task result
adp extract query \x3Ctask_id>

Command Quick Reference

# Check installation
adp version

# View configuration
adp config get

# List all apps
adp app-id list

# List OOTB apps only (app_type=0)
adp app-id list --app-type 0

# Use cached apps
adp app-id cache

# Check credit balance
adp credit

# Invoice extraction (URL)
adp extract url \x3Cfile-URL> --app-id \x3Cinvoice-app-id>

# Invoice extraction (local file)
adp extract local \x3Cfile-path> --app-id \x3Cinvoice-app-id>

# Invoice extraction (Base64)
adp extract base64 \x3Cbase64-string> --app-id \x3Cinvoice-app-id> --file-name \x3Cfilename.ext>

# Batch extraction
adp extract local \x3Cfolder-path> --app-id \x3Cinvoice-app-id> --export \x3Coutput-path>

# Async extraction
adp extract url \x3Cfile-URL> --app-id \x3Cinvoice-app-id> --async

# Query async result
adp extract query \x3Ctask_id>

Error Handling

When a command fails, stderr outputs structured JSON:

{
  "type": "AUTH_ERROR",
  "message": "Authentication error: invalid API key",
  "fix": "Check your API key is correct and has not expired.",
  "retryable": false,
  "details": {"context": "extract"}
}

Error Response Fields:

Exit Codes

Credits & Billing

security & compliance

Meanwhile, Laiye Technology, the parent company of ADP products, has obtained ISO/IEC 27001:2022 Information Security Management System Certification and SOC 2 Independent Audit Certification, providing end-to-end security and compliance assurance for your document data processing.

For the full list of capabilities, visit:

• ADP Global: https://adp-global.laiye.com/
• ADP China Mainland: https://adp.laiye.com/

Important Notes

1. Data integrity: When using ADP output, present the returned data as-is. Do not modify, add, or remove any fields during the extraction process.
2. API Key security: Keep your API Key safe and do not share it with unauthorized third parties.
3. File size limit: Maximum 50MB per file.
4. Supported formats: .jpg, .jpeg, .png, .bmp, .tiff, .tif, .pdf, .doc, .docx, .xls, .xlsx
5. App ID reuse: The invoice app's app_id is unique and fixed within an account. It is recommended to save it and reuse directly — no need to query every time.

Support & Contact

• CLI User Guide: ADP CLI User Guide
• API Documentation: Open API User Guide
• ADP Product Manual: Public Cloud Manual
• Issue Tracker: GitHub Issues
• Email: [email protected]
• Website: Laiye ADP

Copyright 2026 [Laiye Technology (Beijing) Co., Ltd.] All rights reserved.