UseAgentBEFORE YOU RUN
Know the job and the reviewer.
This playbook is for finance and operations teams reviewing invoice or payment exports.
TARGET OUTCOME
A reconciled exception packet that shows what matched, what did not, and what a person needs to investigate.
Bring these inputs
Better source material makes the result easier to review and safer to reuse.
- Two or more CSV or spreadsheet exports
- The match key and reporting period
- Rules for rounding, currency, and duplicates
- A known-good sample
COPYABLE STARTER
Start with this prompt.
Replace bracketed details, attach the source material, and keep the limits until your team has reviewed a few runs.
Compare the attached invoice and payment exports for the stated period. Preserve original values. Return matched records, missing records, value or status mismatches, possible duplicates, and exceptions needing a finance decision. Show the source row or identifier for every exception. Do not edit, approve, pay, or post any record.
THE PLAYBOOK
Move from context to a reviewed result.
- 01
Define the match
State the stable identifier and how to handle partial payments, credits, currency, and rounding.
- 02
Preserve raw values
Keep source columns beside normalized comparison fields so finance can audit each exception.
- 03
Group exceptions
Separate missing records, value mismatches, duplicates, and ambiguous cases.
- 04
Hand off decisions
A finance owner reviews the packet and makes any change in the source system.
DELIVERABLES
What the run should produce
- Reconciliation summary
- Exception table
- Duplicate candidates
- Questions for the finance owner
HUMAN REVIEW
Check this before it leaves the team
- Reporting period is correct
- Currency and rounding rules are explicit
- Every exception retains a source identifier
- No source record was changed
Keep exploring this workflow