Demo library
SKILL / WORKFLOW DEMONSTRATION

Finance Operations: Reconcile Amount Differences Between Orders and Invoices

Check quantities, unit prices, and totals item by item against procurement records, and output a variance table for accounting review.

Finance operationsCodex · ClaudeIllustrative demo · Prepared sample
Fictional purchase order: PO-110; currency CNY
Order: 10 units, 120 yuan per unit, 0 yuan shipping, total 1,200 yuan
Invoice record: 10 units, 125 yuan per unit, 0 yuan shipping, total 1,250 yuan
The demo uses the same amount basis and does not infer tax amounts.
Prepared example · No live AI execution
Read both input and output

Input

Fictional purchase order: PO-110; currency CNY
Order: 10 units, 120 yuan per unit, 0 yuan shipping, total 1,200 yuan
Invoice record: 10 units, 125 yuan per unit, 0 yuan shipping, total 1,250 yuan
The demo uses the same amount basis and does not infer tax amounts.

Output

Predefined variance table
Quantity: 10 vs 10, no difference
Unit price: 120 vs 125, difference +5 yuan/unit
Total: 1200 vs 1250, difference +50 yuan
Suggested checks: price change authorization, contract unit price, and original documents.
Conclusion: pending manual review; no booking, no payment initiated, and not tax advice.

Use Cases

Check quantities, unit prices, and totals item by item against procurement records, and output a variance table for accounting review.

This demo uses fictional business data and pre-prepared outputs to show a customizable workflow and is not a customer case, live AI execution, or actual business result.

Work Steps

  1. Match document numbers, currencies, and amount bases.
  2. Use deterministic calculations to check differences in quantities, unit prices, and totals.
  3. Output source fields and items pending verification; do not automatically determine document validity.

Human Review and Boundaries

Accounting decides on booking and payment after checking original documents, tax bases, and approval records.

Customizable Content

Connect invoice and procurement export data, set variance thresholds and financial review templates, and retain field sources.

How to Validate

Test separately with normal inputs, missing fields, and conflicting materials; check that key fields can be traced to inputs, missing content is clearly marked, and numerical calculations are completed by reviewable rules. The agreed samples and delivery scope shall prevail.

Platform and Delivery

Instructions, templates, auxiliary scripts, and review steps can be customized for Codex or Claude. Specific product versions, tool permissions, and system interfaces are confirmed and tested separately during the requirements phase. Deliverables may include source files, test samples, and usage documentation; this page does not connect to external systems, send notifications, or execute business operations.

YOUR NEXT USEFUL IDEA

What could work better?

Bring a task. We’ll help you find a practical place to start.