BX Expense Reimbursement Filing

The Problem

Many reimbursement workflows do not fail because data is missing; they stall on OA form mappings and dependent calculations. The HF07. Expense Reimbursement form requires selecting the right expense item, expense name, and detail line, and fields such as tax-inclusive total depend on UI change events. Direct script writes can bypass calculation or lose saved values. This skill turns travel and meeting reimbursement filing into a structured, error-checked process.

How It Works

The workflow has three parts: map the reimbursement type, enter detail lines through the UI, and verify the form before saving.
- Mapping rules: travel maps to 02_Project Daily Expenses / 0202_Travel; meeting maps to 02_Project Daily Expenses / 0201_Project Meeting.
- Line selection: choose the matching detail, such as 020203_Lodging, 020215_Transport, 020114_Meeting, or 020112_Consulting-Expert Fee.
- Entry method: click the field, press Ctrl+A, type the value, and use Tab to trigger change events and automatic calculations.
- Checks: dates, detail line, mapped fields, receipt count, amount, tax, tax-inclusive total = amount + tax, grand total, and amount in words.

Limits and Notes

The skill assumes an existing OA account and confirmed reimbursement details, and targets the HF07 form on oa.cnppump.cn:9000. If tax is absent, leave the field blank rather than entering zero. Mixing JS writes with UI interaction can cause duplicate amount accumulation, so refresh and re-enter if anomalies appear.