Proof, not
promises.

The problem

Hours a day, with money riding on every keystroke

Billing lived in three places at once: manifests and vendor invoices arriving by email, ledgers maintained by hand in spreadsheets, and transactions keyed into QuickBooks one at a time. Every flight meant repeating the whole ritual.

The cost wasn't only the hours. Manual transcription across three systems means the numbers can silently disagree, and nobody finds out until a customer does.

What Noctix built

A system that closes the loop on its own

The platform runs the entire billing cycle without an operator. It detects the flight through the logistics platform's API, ingests shipment manifests and vendor PDFs, writes formatted ledgers with live formulas, and generates customer invoices and vendor bills in QuickBooks.

Because the system moves real money, nothing is written on trust. Every value is re-checked against its source document before it executes — and if the numbers don't reconcile, the transaction halts and a human is called.

That ordering matters. A deterministic core does all of the real work, and an AI exception-handler is summoned only when the deterministic layer flags something it can't account for. The clever part stays on a short leash; the boring part is what you trust with the money.

Details worth noting

The unglamorous parts that make it trustworthy

• Weights the vendor API doesn't expose. Billing weight had to be reconstructed from incomplete data — verified exact to the kilogram across 470 of 470 shipments.
• Machine-gated financial controls. Approval isn't a person remembering to look; it's a check that must pass before anything is written.
• Alerting with three volumes. Silence when it's fine, a nudge when something needs eyes, an alarm when it doesn't add up.
• 105 tests in CI. Nothing reaches the runner without passing first.
• One-script migration. Moving the whole system to a new machine is a single command, not a weekend.