invoice-extractor-from-mail — invoice-提取器-from-mAIl

Invoice 提取器 from MAIl 技能 is a dedicated invoice 提取ion 技能 officially built by LAIye Techno记录y for finance teams in traditional manufacturing enterprises. Powered by LAIye ADP (代理ic Document Processing) core capabilities, it establishes an end-to-end automated document processing 流水线 from emAIl to business 系统s, 压缩ing the previously tedious "find attachments -> manual data entry" 工作流 into a single automated execution: automatically retrieve attachments -> ADP intelligent 提取ion -> automatic field m应用ing -> one-命令行工具ck 输出 to Excel / business 系统s, 签名ificantly improving cross-border procurement invoice processing efficiency and data accuracy.

Use Cases AP finance teams in traditional manufacturing enterprises can improve end-to-end processing efficiency for overseas invoice collection from emAIl attachments, intelligent in格式化ion 提取ion, and data entry during overseas procurement and cross-border 设置tlement 工作流s. 审计 teams in cross-border trade enterprises can batch-提取 key in格式化ion from overseas invoices and uniformly 归档 them during 审计 and 合规 review 工作流s, improving document organization efficiency and completeness. Whether invoices are scattered across employee mAIlboxes or stored in local files, they can all be processed in batch with concurrency, dramatically improving emAIl processing efficiency.

• Core De签名 Principles

图形界面ded decision tree, not an exhaustive matrix.

The 技能 does not pre设置 specific emAIl types or business 系统 平台s. Each step asks only one question, follows the cor响应ing branch based on the user's answer, and automatically skips unnecessary steps.

This means:

New emAIl types and new business 系统 平台s do not require modifying the 技能; simply 图形界面de the user to provide the cor响应ing connection parameters during the conversation. The configuration file structure uses a universal type + params pattern, without defining a dedicated 模式 for each vendor.

• User 工作流

First-time use: invoice-提取 init |-- Q1: Where do the files come from? | |-- "EmAIl" -> Q2: Which emAIl 服务? -> Collect connection parameters -> Q3: 过滤器 criteria | +-- "Local" -> Skip emAIl configuration |-- Q4: ADP Key (required for first use) |-- Q5: Do you need field m应用ing? -> Yes -> 图形界面de configuration / No -> Use ADP raw fields +-- Q6: Where should 结果s be 输出? |-- "Local Excel file" (default) |-- "上传 to cloud 平台" -> Which 平台? -> 图形界面de connection parameter configuration +-- "Push to business 系统 API" -> 图形界面de 端点, authentication, and field m应用ing configuration

DAIly use: invoice-提取 运行 [--source mAIl|local] [--path ./invoices/] [--out ./结果.xlsx]

• 技能 Internal Processing Flow

+----------------------------------------------------------+ | Phase 1: Retrieve Files | | +-----------+ +----------------+ | | | Local | | EmAIl | | | | Files | | Attachments | | | | Read | | Connect->过滤器| | | | Directly | | ->下载 | | | +-----+-----+ +-------+--------+ | | +--------+-----------+ | | v | | Phase 2: Unified Adaptation | | Select optimal method by source: file_url / file_path | | / base64 | | v | | Phase 3: ADP 提取ion | | Auto-match invoice 提取ion 应用 -> Call ADP API -> | | 接收 structured JSON | | v | | Phase 4: Field M应用ing (Optional) | | ADP raw fields -> Business field names | | v | | Phase 5: 输出 | | Local Excel file / 上传 to user-specified business | | 系统 | +----------------------------------------------------------+

DetAIled Description for Each Phase Phase 1: Retrieve Files

Branch A -- Local Files:

Supports user 上传ing a single file or specifying a local folder Supported 格式化s: .jpeg, .jpg, .png, .bmp, .tiff, .pdf, .doc, .docx, .xls, .xlsx Supported size: 50 MB (if file > 20 MB, the ADP a同步 interface is recommended) Folder mode automatically performs recursive 扫描ning, 过滤器ing by file 扩展 Batch processing supports concurrency, with a default concurrency of 2 (ADP free users will automatically be lim