Autonomous month-end close for owner-operated trucking firms running 3 to 12 trucks
It closes the month while nobody is watching.
I build back-office software for finance teams. Archon is the month-end close for the firms it never reaches: an owner-operator trucking firm of three trucks, doing the books at the kitchen table on Sunday night. On the month below it found 612.85 quietly leaking.
Replay walks the eleven steps of the close that
a file landing in Cloud Storage already triggered. Nothing re-runs and no model is called.
A fresh close runs the month again on synthetic data, takes about a minute, and is
discarded when you leave.
Loading the latest close…
1Documents arriveReceipts, invoices and remittances land in Cloud Storage. Pub/Sub pushes the event and the close starts itself. Nobody presses anything.
→
2The agent closes and checksGemini decides what to do about each exception; the tool order is prescribed and deterministic code does every calculation.
→
3The owner reviewsThe books close and the whole trail is recorded. External letters wait for human approval.
✓Human control stays where it matters. Archon drafts and files every broker or supplier letter, but never sends one without approval.
Latest close outcome
What Archon found and finished
Every figure below opens the ledger it came from.
Agentic controlADK + GeminiExact arithmetic deterministic ledgerSelf-checked seven close gatesAuditable source hashes + run id + step-by-step trail
One payment, proven to the cent
The identity the whole product rests on: what landed in the bank equals
what the remittance lines pay, less the fee charged once on the batch.
Where the money went
Operating cost by category, largest first.
Earned and spent, per mile
The ratio that decides whether a haulier survives.
Where this close came from
Books tie back to bytes, a build and a control flow, or they are trusted
on faith. These are the receipts.
The autonomous close
Eleven steps, start to finish, with nobody in the loop. The trail is written as the run
happens and persisted with the books, so the owner can retrace a close they
were not present for. Replay re-renders the recorded run without executing
anything; the button runs a fresh close through the agent, which takes about a
minute on a thinking model.
Step by step, as it happened
The mailbox this close was built from
Every object the close read, with its size, generation and sha256, and every
object it refused, with the reason. Hash an object yourself and match the
books to the bytes; that is what this table is for. When the mail is the
bundled synthetic sample, it says so here instead of dressing up.
One payment, split back across the loads it settles
This is the step that makes a haulier's month closeable, and it is not
matching. The broker sent one credit covering several loads, minus a fee
charged once on the batch. The books need each load settled at what it was
actually paid, and the identity below has to close: what landed equals what
the lines pay, less the fee.
Who owes whom
The register an owner actually opens, because it answers the two questions
that decide whether payroll clears: who has not paid me, and who have I not
paid. A load paid short leaves the difference open rather than counting as
settled. Age is measured to the end of the period being closed, never to
today, so re-running an old month gives the same answer.
Owed to the firm, by age
Owed by the firm, by age
What does not add up
Ten detectors, worst first by severity then by money. Every threshold is
learned from this firm's own books: a charge is an outlier because it is far
above what this firm normally pays that supplier, not because it crossed a
figure someone wrote down.
By kind
The owner's close package, composed and filed
A haulier does not open a bookkeeping console on the first of the month,
because a haulier is driving. So the last thing the close does is write the
owner a letter and hand it to a delivery seam. This is the exact letter, and
the pill on it says what actually happened: delivered when a mail channel is
configured, composed and filed when none is. Every figure in it came out of
the close and not out of a model; the opening sentence is the one thing a
model may phrase, and the run stamps which of the two wrote it.
Each dispute, next to the letter it produced
Filed, not sent. This is the one human gate in the product.
The letters below go to brokers and suppliers, and they stop here. An email
to a broker cannot be un-sent, so an unattended run does not get to send
one. Every draft is written, costed and filed, and a person decides.
Approve or reject one and watch the state change. This is a public
sandbox: no message is sent, and your decision is not kept. A configured
deployment records who approved, when, and the delivery receipt; here the
approver is "sandbox visitor" and the delivery is the thing that does not
happen, which is the whole point of the gate.
Against the month before
Side by side
Each pair is the earlier month then this one. Direction is a rule, not a
sign: fuel rising is worse, revenue rising is better.
Per truck
Direct cost is fuel and maintenance, the two an owner can act on per truck.
Insurance and driver pay stay at firm level: apportioning them would invent
a figure.
Margin a mile, by truck
The close checked its own work
Seven gates stand between the books and a closed month. Each one with
something to check runs; one with no inputs reads skipped rather than
passing quietly, so the count is what was actually verified. A failure
blocks the close and names the gate rather than filing a confident report
nobody checked.