PROMPT BRO
Accounts desk

Find dispatches that are not billed

Truck left. Challan signed. Invoice is waiting for someone to find the challan.

Tested Claude Opus 5.5, medium effort · 15 Nov 2026 · on the practice files

By hand30–45 min
With AI10 min
Per day · estimate
Easier on your office computer.Send to my computer
I usePick yours. We'll show the right steps.

Export both line lists

Use unique challan line ref and item code, dispatched quantity and invoiced quantity. Include cancelled or non-billable lines only with their approved status. Include item code, unit, linked PO/order line ref, approved billable status and evidence. Do not assume all dispatched goods are billable.

First time? Try it on fake data first:

Confirm the period

Use the same cut-off; check actual dispatch and unit of measure.

Privacy Use business line refs and quantities only; remove delivery contact details. Delete bank account numbers; replace customer UPI IDs and phone numbers.

Fill the orange boxes
You send (the "prompt": the message you paste into your AI tool)
challans.xlsxinvoice-lines.xlsx

Whenever I send challan and invoice line lists up to [Cut-off date], match by challan line ref and item code. Scope: [Scope]. A. Validate unique challan line refs, invoice line IDs, item codes, units and numeric nonnegative quantities. Hold all occurrences of duplicated/conflicting IDs and item/unit mismatch; do not let duplicate invoice rows inflate billed qty. Show approved billable dispatched and valid billed qty by unique challan line, remaining = approved billable qty minus billed. Scope must confirm which dispatches are billable; otherwise hold for accounts. If several unique valid invoice rows reference one challan, sum those quantities. No invented qty. B. List unbilled, overbilled and invoice-only refs; count quantities by item and status. Don't combine different units as a meaningful total. C. List checks for accounts and stores before billing. For each unbilled approved line give a copyable handoff: challan line ref, linked PO/order line ref if supplied, item/SKU, unit, approved billable qty remaining, prior valid billed qty and evidence reference. Mark missing PO/order link or billing approval [confirm]; no invoice posted. Use only my data. GST rates, HSN and TDS rates only from my supplied figures; never guess tax treatment. This is a first pass; a person checks and posts any final entries in Tally/Busy.

Set it up once. Save the line matching instructions. Pick your tool at the top to see how.

After that, each time: send the day's challan and invoice exports.

First time? Try it in a normal chat: paste and send.

Which model? Use your tool's strongest model with thinking turned on.

In your AI tool: attach the files with the + button, paste, send.

What you'll get back (example, from the practice files)
2unbilled lines
1overbilled
1invoice only
  • D23 unbilled. 10 dispatched, 7 billed.
  • D32 overbilled. 8 dispatched, 10 billed.
  • D45 unbilled. No invoice line supplied.
Before you trust it

Then send this: Recheck each reference and quantity sum, verify each invoice line used once and flag missing challan refs. Reconcile unique source lines, hold duplicate/conflicting IDs, confirm item/unit and billing scope. Do not treat physical dispatch as automatically approved for billing.

If it goes wrong
It matches item only

Reply: "Match challan line ref and item."

It ignores partial billing

Reply: "Sum billed quantity per challan; show balance."

Cancelled dispatch included

Remove or mark approved non-billable records before rerun.

Sir ne bola urgent. Ab bolo: ho gaya.

Did it work?