Documents
Documents is the filing cabinet for every piece of paper a load generates — the rate confirmation, the bill of lading, the signed delivery receipt, the customs papers, the fuel and lumper receipts — filed automatically under the right load, stamped with who sent it and how, checked against what that load is legally required to carry, and chased up when something is missing.
From the Lanexa 2.0 capability register · version 2.0.37 · reviewed 2026-08-24
What happens on its own.
The work nobody does. These run in the database rather than the browser, which is why they still happen when someone forgets, closes the tab, or was never told they were supposed to.
Every document write is audited twice, from two different places
The application writes structured events through a recording routine that stamps the actor server-side; independently, a database change-log trigger writes its own created / updated / deleted entry carrying a field-by-field record of exactl
Deletions are logged by the database, not by the application
The deletion policy trigger writes the audit event itself, recording whether it was a self-delete inside the 24-hour window or an admin action, the document's age in hours to one decimal place, its type code, its older type value, load numb
A POD arriving raises a notification
Every document-created entry is inspected the moment it lands in the audit trail; if the type is a proof of delivery — either the catalogue code or the older value — a notification is recorded against the load, carrying the load number, the
A POD arriving may create a payable
A -coded row inserted — or an existing row re-coded to, which is exactly what a dispatcher does in the Review queue — fires a trigger that resolves the load and asks the interline biller whether a carrier bill is now due for the partner car
What you can do here.
Every item below is live in production today. Anything not yet built is listed further down rather than left out.
What we haven’t built here — by design.
Publishing this is the point. Documents ships 30 capabilities today; these 3 are not built yet, and you should know that before a sales call rather than after one.
| Capability | Status |
|---|---|
| AI classification of inbound documents | Not built |
| Document version chains | In progress |
| Retention and archiving | Not built |