Skip to content
farmsorted

Chase the dockets still missing at the end of harvest

In the rush of harvest, dockets stay in truck cabs, get lost in a carrier’s inbox or never get sent. Without them you can’t prove a load was delivered when a payment comes up short, and the bookkeeper can’t close off the season.

The Delivery docket reconciler counts loads carted off each paddock against the dockets received, lists the loads with no docket and drafts a request to the site or carrier for copies.

When · Scheduled
A week after the last load of harvest is logged
You get
Loads with no docket by date, truck and site; requests drafted for copies; harvest delivery tally ready to close off
Approval level
Recommend. Suggests an action. You do it. You can change it.
Useful for
CroppingMixed

What it reads

  • Harvest load log from the header and chaser bin notes
  • Dockets received by email and photo
  • Carrier invoices listing loads carted

What you get

  • A list of every load with no docket, with date, truck rego and site
  • Drafted requests to each site or carrier for copies
  • A harvest delivery tally by crop and site once the gaps are filled

When it stops and asks you

  • A load in the log might have gone into the silo on farm, not to a site
  • The carrier’s count and the farm’s count disagree
  • Nobody knows which site a load went to

How often

Once a year, a week after harvest finishes

Who uses it

The farm officeOwners

What it uses

Live

Inbound email

Forward invoices, kill sheets, NVDs, soil tests and emails from your stock agent to your own farm address. The team reads each one, sums it up and suggests who handles it.

Live

SMS and voice notes

Text the team, send a voice note or a photo, or forward a message. There’s no new app to learn.

The last one makes it better, but it works without it.

Nothing official leaves the farm without your yes.This job runs at Recommend: suggests an action. You do it. You can change that any time.

See the guardrails

The conversation

How the job plays out, step by step.

Delivery docket reconciler

Started 6:00am · Scheduled

Start to done
5 min
Agent actions
4
Needed you
2×
[AGENT NAME]For the Delivery docket reconciler

On schedule · 6:00am

Last harvest load logged 7 days ago; delivery tally still open

Delivery docket reconciler

Compared 186 loads in the harvest log with 179 dockets on file

7 loads have no docket. 4 went to [site A] on 2 and 3 December in [carrier]’s truck, 3 are canola loads from 9 December with no site noted. Carrier’s invoice has 183 loads, so 3 of those may have gone to the farm silo.

[AGENT NAME] · 6:00am

The 3 canola on the 9th went in the silo bag on the north side. The other 4 are real.

You · 6:02am

Delivery docket reconciler

Noted the 3 canola loads as on-farm storage and drafted a request for the 4 missing dockets

Request to [site A] lists the 4 loads with dates, times and rego. Send it?

[AGENT NAME] · 6:02am

Approved

Yep, go.

You · 6:05am

Done · 6:05am1 waiting for you

  • A list of every load with no docket, with date, truck rego and siteSaved
  • Drafted requests to each site or carrier for copiesWaiting for you
  • A harvest delivery tally by crop and site once the gaps are filledSaved

Behind the scenes

  1. 6:00am

    Trigger On schedule

    Last harvest load logged 7 days ago; delivery tally still open

    • records.searchharvest load log
  2. 6:00am+10 sec

    Delivery docket reconciler works on it · 2 steps

    Compared 186 loads in the harvest log with 179 dockets on file

    • records.searchdockets by date and rego
    • documents.read[carrier] invoice, 183 loads
  3. 6:00am+2 sec

    [AGENT NAME] messages you

    “7 loads have no docket. 4 went to [site A] on 2 and 3 December in [carrier]’s truck, 3 are canola loads from 9 December with no site noted. Carrier’s invoice has 183 loads, so 3 of those may have gone to the farm silo.”

  4. 6:02am+3 min

    You reply

    “The 3 canola on the 9th went in the silo bag on the north side. The other 4 are real.”

  5. 6:02am+10 sec

    Delivery docket reconciler works on it · 2 steps

    Noted the 3 canola loads as on-farm storage and drafted a request for the 4 missing dockets

    • docs.draftrequest to [site A] with dates and rego
    • memory.remembercanola silo bag, 3 loads
  6. 6:02am+2 sec

    [AGENT NAME] asks for your yes

    “Request to [site A] lists the 4 loads with dates, times and rego. Send it?”

  7. 6:05am+3 min

    You approve

    “Yep, go.”

  8. 6:05am+3 sec

    Delivery docket reconciler Done

    Request sent to [site A]; 3 canola loads ready to add to the harvest record as on-farm storage; tally shows 4 loads outstanding until the copies come back

    • Email sent by your main agent after your yes
    • reports.draftharvest delivery tally

An example with made-up data. Names and figures in [brackets] are placeholders.

Put [AGENT NAME] to work on your farm.

We’re taking a small number of pilot farms in Australia. Start with one or two agents and add more as you go.

Pilot farms wanted

Want to try it out?

Join the pilot, or book a demo and we’ll walk you through this job on a farm like yours. You text the team from your phone. Some connections are still being built, and we’ll tell you which.

  • Inbound email
  • SMS and voice notes
  • Nothing to install

Free report

Getting started with AI.

A free practical guide for Australian farms and agribusinesses

Where AI actually helps on a farm, what it needs from you, the risks to watch, and a 90-day plan to start small.

  • Where it actually helps
  • What it needs from you
  • Risks and guardrails
  • Working out the return
Book a demoJoin the pilot