# Not sure every job was paid in full? This checks each one against your payment files.
By The Workshaped Lab · Tier: Workflow integration · Industry: Field service · Function: Finance · Autonomy: read-only · Last verified: 2026-10-14

**Problem:** an appliance-install business earned a per-job surcharge that never showed up on weekly payouts.
**Setup:** a read-only agent matches completed jobs (from emails) to every weekly payment file, using the surcharge rules.
**Result:** $900 in surcharges not yet seen, across 9 completed jobs, each with evidence.
**Access:** read-only on email and the third-party portal. A person files every claim.

## Why it's easy to miss
Payment files show the base install line, so jobs look paid. Spotting a missing extra line means checking every job against every file.

## What broke
Payment files carry no pay dates, so findings are labelled "not yet seen" (never "never paid"), with a grace window for late payments.

## Why read-only
The team needs to understand what the agent checks before it acts on their behalf. Read-only → suggest → act with approval → autonomous.

## Free outline: try it yourself
1. Export completed jobs and the rules for any extra charges.
2. Collect every payment file since your oldest open job.
3. Have an AI or a script match them line by line and list the gaps, with the evidence for each.
4. Label findings "not yet seen" and have a person review them before anything gets claimed.

The full Blueprint is a no-code prompt pack (a recommended AI with a short why, a main build prompt plus follow-ups, a test-it checklist, a worked example, a printable PDF, and an optional developer kit for technical users). It's a paid download: https://workshaped.ai/pricing/

## The main prompt (free Blueprint)
```
You are helping me check whether every job I completed was paid correctly.
I will paste two things: (1) a list of completed jobs with date, job ID and the extra charges each job should earn, and (2) the payment file lines I received.
For each completed job, tell me whether I can find a matching payment line for the base amount and for each extra charge.
Make a table: job ID, expected amount, amount found, which payment file it was in, and status (paid / short / not yet seen).
Do not guess. If a line is ambiguous, say so. Label anything missing as "not yet seen", not "never paid", because it may arrive in a later file.
Show your matching logic so I can check it by hand.

When you want the tested version (a recommended AI, a step-by-step build prompt with follow-ups, a test checklist and a worked example; no coding needed), see the Workshaped Blueprint: https://workshaped.ai/use-cases/unpaid-surcharge-reconciliation/#blueprint
```