AI Credit Expense Report

AI Credit Expense Report

Use this skill to turn personal AI tool receipts, invoices, payment records, and usage screenshots into one clean Excel workbook for reimbursement or personal cost tracking.

Output

Create one .xlsx file with a single worksheet named AI积分消耗情况表.

Default columns:

Keep the sheet simple unless the user asks for more tabs. The user's preferred scope is personal records, RMB only, one table. Do not add a separate 凭证/发票 column by default; put source file names, invoice numbers, order numbers, and uncertainty notes into 备注.

Before Building

Before generating the Excel workbook, first inspect the provided invoices, receipts, payment records, order screenshots, filenames, and folder name. Do not ask for any data that can reasonably be extracted from those sources. Ask only for missing data that materially affects estimation or reconciliation. Keep questions short and practical.

Do not ask for:

• Reporting period; infer it from the folder name, invoice dates, or purchase dates.
• Platform, date, amount, seller, invoice number, order number, product name, credits received, or payment method when visible in the provided files.

Ask only when unavailable or ambiguous:

• Platforms to exclude if the batch contains obvious non-AI services or mixed reimbursements.
• Platform account or project name if it is needed and not visible.
• Usage records needed for estimation: generated image count, generated video count, video duration, resolution, model/version, workflow name.
• Current remaining credits for each platform, only if the user wants reconciliation.
• Whether non-image/video AI services such as Suno or memberships should be included when the intent is unclear.
• Any missing user-specific estimation rule, such as a per-image price or per-second video credit rule.

Supported Platforms

Start with these platforms unless the user adds more:

• 可灵
• 即梦
• RunningHub
• Hailuo / 海螺

For current platform rules and verification notes, read references/platform-pricing.md.

Workflow

1. Collect inputs from the user:

   • invoices or receipts
   • payment screenshots
   • purchase records
   • platform usage screenshots or exported records
   • account/project names if visible data is ambiguous
   • user-provided estimation rules for image/video generation prices

2. Extract each purchase or usage event:

   • date
   • platform
   • account/project
   • recharge amount in RMB
   • credits received
   • credits consumed
   • remaining credits
   • generation type: image, video, mixed, unknown
   • generation count
   • evidence source, stored in 备注 only when useful

3. Estimate missing usage values only when needed:

   • Prefer real platform usage records over estimates.
   • If no usage record exists, estimate from generation count and platform rules.
   • Mark the 估算规则 and 备注 clearly so estimated rows are distinguishable from confirmed rows.

4. Reconcile:

   • If 获得积分 - 消耗积分 does not match visible remaining credits, add a note.
   • If a receipt amount exists but credits are missing, leave credits blank and note 缺少积分记录.
   • If credits exist but payment amount is missing, leave amount blank and note 缺少付款记录.

5. Build the Excel file:

   • Use formulas for totals where useful.
   • Format RMB as currency.
   • Freeze the header row.
   • Add filters.
   • Highlight rows with missing or estimated values.

6. Validate before delivery:

   • Open/render or inspect the workbook.
   • Confirm headers, totals, formulas, and column widths.
   • Report any rows that need user confirmation.

Estimation Rules

Use a conservative approach:

• 估算消耗金额(RMB) = 充值金额(RMB) * 消耗积分 / 获得积分 when both amount and credits are known.
• If only generation count is known, estimate 消耗积分 = 生成次数 * 单次积分消耗.
• If platform rules vary by model, duration, resolution, speed, or workflow, include those assumptions in 估算规则.
• Treat every platform rule as scoped configuration, not permanent truth. Record its source, effective date, applicable model/workflow, and whether the user confirmed it for the current report.
• Prefer user-provided rules over general web pricing only after confirming they apply to the current records.
• Do not invent exact prices when evidence is missing. Use 待确认 and ask for a screenshot or purchase record.

Spreadsheet Tooling

When creating or editing .xlsx, use the Spreadsheets skill if available. Keep the output user-friendly and suitable for reimbursement review, not just raw extraction.

Final Response

Return:

• the generated Excel file path
• a short summary of records included
• totals by platform if calculated
• unresolved items requiring user confirmation