About this skill

Problem

After a business trip, invoices often sit scattered across phone galleries, download folders, and chat attachments. It is easy to miss whether the invoice title matches the company, whether dates fall inside the trip window, whether travel exists between cities, whether hotel records are missing, or whether meal spend exceeds internal limits. Special invoices, reissues, refunds, and red-letter reversals make the cleanup even harder.

Core capabilities and flow

The skill advances through six steps:
- Context capture: confirm home city, trip dates, destination, company name, and optionally collect finance policy and per-diem standards.
- Invoice intake: accept photos, pasted text, or a local folder such as ~/Downloads/出差发票, then batch-read JPG, PDF, OFD, and files inside ZIP archives.
- Classification and trip log: organize entries by transport, hotel, meals, and other, then infer a day-by-day itinerary.
- Report generation: emit Markdown, CSV, or a custom template, including per-diem, deductible tax, and red-letter reversals.
- Compliance review: separate structural checks, invoice validity checks, and threshold checks; without a company policy it only checks items that have evidence and avoids inventing rules.

Boundaries

It does not replace finance approval, does not connect directly to ERP/SAP/Yonyou, and does not verify invoice authenticity or final tax deductibility. Title checks require the company name, threshold checks require a user-provided finance policy, and the scope is mainly mainland China invoice formats rather than overseas invoices.