⇄ Workflow integrationField ServiceFinance & Billing

Job Payment Checker: Find Surcharges Not Yet Paid

Not sure every job was paid in full? This checks each one against your payment files.

For field service and trades businesses that get weekly payment files. You walk away with a list of what was paid, what was short and what hasn't arrived yet, with the matching shown.

An appliance-install business was earning a per-job surcharge that never showed up on payouts. Nobody had time to check line by line, so an agent did it without being able to change anything.

By The Workshaped Lab·7 min read·Autonomy: read-only
Problem

A surcharge was earned on some jobs but missing from weekly payouts.

Setup

An agent matches completed jobs to every payment file using the surcharge rules.

Result

Unpaid surcharges found on 9 completed jobs, each with evidence.

Access

Read-only on email and the third-party portal. A person files every claim.

Context

This comes from a long consulting engagement with an appliance-install business. We learned the operation the way anyone new would: through its email, WhatsApp threads and the portals the installer network uses. Every agent we've built there starts the same way, by reading and reporting.

The problem

The network pays in weekly files. Some jobs earn an extra charge depending on location and what's installed. When that line is missing, the job still looks paid, because the base install line is there. Spotting the gap means checking every job against every file, and nobody had time for that.

The setup

Job emailsstatus, completions Payment filesweekly imports Reconciliation agentrules + matchingread-only Owed listreviewed by a person
Simplified structure. The agent never writes to the portal or sends anything.

For every completed job, the agent checks whether it qualifies for the surcharge, then looks for that line in every payment file received since the job was done.

# the rule, in plain terms (simplified)
for job in completed_jobs:
  if qualifies_for_surcharge(job):
    if not seen_in_any_payment_file(job, "surcharge"):
      flag(job, status="not yet seen", evidence=files_checked)

What it found

$900in surcharges not yet seen, in one test
9completed jobs flagged
0changes made by the agent

Nine completed jobs qualified for the surcharge but were paid only the base install. Each flag came with its evidence: the job, the rule it met, and which files were checked.

What broke

Payment files don't carry pay dates, so the agent can only say which file a line arrived in. A very recent job might still be paid next week. So every finding is labelled "not yet seen" rather than "never paid", and a person decides when to claim.

Lesson: honest labels beat confident ones. A wrong "never paid" claim costs more trust than it recovers.

Why read-only

The agent could technically draft and file the claims itself. It doesn't, on purpose. The team needs to understand what it checks and why before it acts on their behalf. Full autonomy is possible here, but it's a way off, and that's the right order.

Read-only → suggest → act with approval → autonomous. This setup sits at step one.

Try it yourself

  • Export a list of completed jobs and the rules for any extra charges.
  • Collect every payment file since your oldest open job.
  • Ask an AI to match them line by line and list the gaps, along with the evidence for each.
  • Label findings "not yet seen" and have a person review them before anything gets claimed.

Free · Kickstart prompt

Get a rough first version today

Paste this into Claude, ChatGPT or Grok with your own data. It gets you a useful first pass, not the tested setup.

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
Check every result by hand. Don't paste account numbers or anything you don't need to share.

✓ Prompt tested 16 Oct 2026: we ran it with gpt-5-mini on a synthetic sample and checked the output by hand.

The Blueprint

Build this yourself: payment-file reconciliation

The idea above is free. The Blueprint is a pack of tested, copy-paste prompts: your AI builds most of the workflow with you, and you finish it in your own back-and-forth. No coding needed.

Prompts tested: 16 Oct 2026
  • Which AI to use, and why: ChatGPT, because its free plan can analyze CSV files with code. Fallback: Claude.
  • A main build prompt: it asks you a few questions, then does the job with you step by step
  • 4 follow-up prompts: “Double-check your work”, “Adapt it to your situation”, “Check the next payment file”, “Make a monthly log”
  • A test-it checklist, with a synthetic sample to try before your own data
  • A worked example with the expected result, so you know what good looks like
  • A printable PDF guide, plus an optional developer kit (code, workflow file and tests) for technical users
$29
One-time · free updates for 12 months if a listed tool changes
Unlock this Blueprint Secure Stripe checkout · or have us build it

Digital download, delivered instantly. Sales are final once accessed; see our Refund Policy. By continuing you agree to our Terms. Not professional advice; see Disclaimers.

Keep going

Related workflows

More: all Field Service use cases · Finance & Billing ideas · every use case

The weekly use case

Get one tested AI use case a week.

One real job an AI can help with, the prompt we tested and what to watch out for. Free, by email. Unsubscribe any time.

We store your email, when you signed up and the page you signed up on, to send this email and to see which pages people sign up from. Unsubscribe any time by emailing hello@workshaped.ai. Privacy

Want one of these built for your business?

Workshaped designs AI systems around how your team actually works. We start read-only, prove the value, and only then talk about autonomy.

Work with us