Lemon Cloud Batch Invoice Verification and Duplicate Reimbursement Prevention

Problem

Batch invoice verification often stalls on concrete issues: invoices are scattered across folders as PDF, OFD, or images; checking tax-bureau status manually is slow; failed or empty results need repeated retries; reimbursement and ledger fields are inconsistent; duplicate invoices are easy to miss. batch-invoice-verify targets this workflow by splitting verification, duplicate-risk checking, and ledger generation into an auditable two-stage process.

How It Works

The first stage runs verify: it reads an invoice folder or a .xlsx/.csv list, identifies valid invoices, calls the verification API, and writes an intermediate XLSX. If failed or empty results need another attempt, reverify refreshes only unsuccessful records while preserving successful ones. The second stage runs manage: it checks invoice headers, flags duplicate risk, reconciles reimbursement and accounting status, and outputs a final XLSX plus JSON statistics. Historical lists must be standard CSV; enabling reimbursement or accounting checks requires a list with the corresponding status fields.

Boundaries

The skill does not replace tax-bureau login, does not download invoices, and does not automatically map arbitrary custom history schemas. The API key is used only at runtime and should not be written into configuration, logs, or output files. When multiple headers return failed, the user must confirm the header before rerunning the second stage.