# Lanexa > Lanexa is an AI-native Transportation Management System (TMS) built for Canadian motor carriers, freight brokers and 3PLs running cross-border across Canada, the United States and Mexico. Twenty-two modules in one platform, including a Unified Communications Hub (SMS, WhatsApp and email in one inbox), in-app eManifest (ACE/ACI/PARS/PAPS) and a real double-entry general ledger. Headquartered in Scarborough, ON, Canada. ## What Lanexa is Lanexa replaces the traditional 3–4-tool stack a Canadian carrier runs today (TMS + broker portal + driver chat + accounting) with a single platform of twenty-two modules: 1. **Dashboard** — the operating picture: today's loads, exceptions, money and alerts on one screen. 2. **Trip Board** — live load grid to assign, dispatch and track every trip across Canada, the US and Mexico. 3. **Load Board** — create loads in seconds or import a rate-confirmation PDF and let AI fill the fields (FTL, LTL, reefer, dry van). 4. **Load Status** — the dispatch board: every load's live stage, driver, truck and next stop. 5. **eManifest** — ACE (US-bound), ACI (Canada-bound), PARS and PAPS filed in-app for every crossing, no second system. 6. **Interline Desk** — tender loads to partner carriers with an offer clock, live sell/buy/margin, partner authority numbers (USDOT/MC, SCAC, CBSA code, CVOR, CTQ) and insurance-expiry compliance, plus a rate confirmation that files itself and a partner bill that creates itself in AP on delivery. 7. **Quotation management** — build quotes from rate tables, send them, and convert an accepted quote into a live load. 8. **Unified Communications Hub** — SMS, WhatsApp and email in one threaded inbox, every message anchored to its load. WhatsApp is one channel among several, not the whole system. 9. **Fleet & asset management** — trucks, trailers and yards in one registry, with availability, location and lifecycle history. 10. **Drivers** — driver records, credentials, licences, medicals and time off in one place. 11. **Customer CRM** — every shipper and broker with their loads, contracts, revenue and credit status. 12. **Billing & accounting** — invoices auto-built from the load, AR aging, credit memos and statements; QuickBooks Online sync in CAD and USD. 13. **Accounts payable** — carrier bills for brokered and interlined loads, with approvals, payment terms and payments. 14. **Payroll & driver settlement** — company, owner-operator and team pay splits with deductions, advances and bonuses; a settlement run needs a second person to release it. 15. **Ledger** — a real double-entry general ledger that every invoice, bill, settlement and fuel receipt posts into automatically. Void a document and it unposts, along with anything it created. 16. **Unified document management** — BOLs, PODs, rate cons and permits filed to the right load automatically, with provenance and a full audit trail. 17. **Compliance, IFTA and safety** — driver and vehicle credential expiry alerts, quarterly IFTA with a four-source mileage engine and per-litre Canadian rates, an accident register, and CBSA CARM readiness. 18. **Advanced analytics** — revenue, margin, on-time delivery and lane profitability across any date range. 19. **Reports** — a catalogue of operational, financial and compliance reports, run with inline parameters and exported to CSV or PDF. 20. **Activity & audit log** — a tamper-evident record of who did what, when. 21. **Settings** — company profile, operations, tax rates and rules, chart of accounts, pay templates, rate cards, accessorials, customs brokers, notifications, message templates, users and roles, custom fields, automations, integrations and data import. 22. **Multi-organization operations** — run several companies from one login, books and users separated per entity. Integrations that are live today: QuickBooks Online (with a dedicated sync centre), Samsara, Twilio for SMS and WhatsApp, Resend and SendGrid for email, PC*Miler for truck-legal mileage, live CBSA and CBP border wait times, the US EIA diesel index behind fuel surcharges, weather alerts from Environment Canada and the US National Weather Service, and Cloudflare Turnstile on public pages. More are on the roadmap; this list is what is connected now. Drivers are reached over SMS, WhatsApp and email — there is no app for them to install. Customer-facing documents (invoices, bills of lading, proof of delivery) are produced in English or French. Pricing is per-seat (dispatchers, ops, billing), not per-truck. ## How much is built Lanexa publishes a capability ledger: 716 capabilities live in production today across 22 modules, each listed by name with the module that owns it, from the Lanexa 2.0 capability register (version 2.0.37, reviewed 2026-08-24). Everything the site lists is in production. What has deliberately not been built is published too, by name, as a design choice — including hours-of-service automation and a driver mobile app. - Ledger: https://lanexa.io/platform/capabilities - What we haven't built, and why: https://lanexa.io/trust/what-we-havent-built - Full site text in one file: https://lanexa.io/llms-full.txt ## Who Lanexa is for - Canadian carriers running 10–200 power units on cross-border lanes into the US and Mexico - Freight brokers and 3PLs that need cross-border eManifest filing, full billing and settlement, and unified driver communications - Owner-operators who want a real TMS instead of spreadsheets and chat ## Where Lanexa is Headquartered at Suite 400 – 1940 Eglinton Ave E, Scarborough, ON M1L 4R1, Canada. Implementation and onboarding done by people who have dispatched freight on the corridor. ## How Lanexa is delivered - Web app (dispatchers / ops / billing) - Unified driver communication over SMS, WhatsApp and email — no separate app for drivers to install - Customer-facing branded tracking portal (no login required for shippers) - Hosted on Cloudflare globally; data residency in Canada ## A Canadian company, close to the carriers it serves Lanexa is built and run in Canada by Cygnik Tech, its Canadian parent company — a real Canadian business with real people behind it, not software run from far away behind a Canadian-looking name. This presence is a core part of the value proposition, framed as trust and closeness (not as a warning): - **Stands behind its work.** The company operates to Canadian standards and is here to honour its commitments — reachable in the client's own time zone and responsible for the software carriers run their business on. - **Insured in Canada.** Lanexa carries its business insurance in Canada, for Canadian clients, in Canadian dollars — so the protection standing behind the service is real and local, valued the way a Canadian carrier would expect at home. - **Data stays in Canada.** Data is hosted in Canada and handled under Canadian privacy law (PIPEDA), so freight and customer information stays home under the rules clients already know. The contrast is stated positively and generally (no competitor named): plenty of software is run from far away, by people a customer can't easily reach. Lanexa is built the other way — a Canadian company, close to the people it serves, in the same time zone, easy to reach when it matters. ## Pricing Pricing is per-seat (dispatchers, ops, billing) in Canadian dollars — not per truck. Trucks, trailers, drivers and loads are unlimited on every plan. - **Lane** — per-user pricing in CAD, coming soon. The operational essentials a carrier needs to run day to day: Trip Board and Load Board (dispatch across Canada, the US and Mexico), in-app eManifest (ACE/ACI/PARS/PAPS), billing and invoicing with QuickBooks sync (CAD and USD), driver settlement and pay, fleet and asset management, customer records and branded tracking portal, document management, compliance and quarterly IFTA, and email and SMS driver messaging. - **Corridor** — per-user pricing in CAD, coming soon. Everything in Lane, plus the premium layer: the Unified Communications Hub (SMS, WhatsApp and email in one inbox), the Interline Desk, advanced analytics and reporting, the activity and audit log, multi-company operations, single sign-on, and onboarding support. - **Solo** — free, coming soon. A tier for single-truck owner-operators to run loads, documents and invoicing without a subscription. CAD is the billed currency. Final per-seat pricing has not been published yet. ## Contact - Website: https://lanexa.io/ - Login / app: https://app.lanexa.io/ - Phone (sales): +1-888-777-1672 - Email: info@cygnik.com - LinkedIn: https://www.linkedin.com/company/lanexa-tms/ ## Canonical name and aliases - Canonical product name: **Lanexa TMS** - Legal entity / operator: Cygnik Tech (https://cygnik.tech). Lanexa is a product of Cygnik Tech. - Common search terms: Lanexa, Lanexa TMS, Canadian TMS, unified communications TMS, cross-border eManifest TMS, driver settlement software, freight billing Canada, dispatch software Canada ## Page index - Home: https://lanexa.io/ - Platform (22 modules, six pillars): https://lanexa.io/platform - Capability ledger: https://lanexa.io/platform/capabilities - Module pages: https://lanexa.io/product/ — dashboard, loads, trip-board, load-status, emanifest, interline, quotes, messages, fleet, drivers, customers, billing, accounts-payable, payroll, ledger, documents, compliance, analytics, reports, activity, settings, group - Why Lanexa (four proof pages): https://lanexa.io/why - Trust, security and what we haven't built: https://lanexa.io/trust - Who it is for: https://lanexa.io/customers and https://lanexa.io/solutions/ - Pricing: https://lanexa.io/pricing - Glossary of cross-border and trucking terms: https://lanexa.io/glossary - Integrations: https://lanexa.io/integrations - Compare approaches: https://lanexa.io/compare - Changelog: https://lanexa.io/changelog - Contact and demo: https://lanexa.io/contact - Sitemap: https://lanexa.io/sitemap.xml --- # Full site text Generated at build time from the 72 indexable pages of https://lanexa.io. Each section is one page: its URL, title and description, then the page text. Figures come from the Lanexa 2.0 capability register; the pages state the version and review date. --- ## Lanexa — AI-Native TMS for Canadian Carriers URL: https://lanexa.io/ Summary: AI-native TMS for Canadian carriers running cross-border. Unified comms, in-app eManifest, billing, settlement and a real general ledger — 22 modules, priced in CAD. # Enter the shipment once. Dispatch, the border and the books in one system — built and run in Canada for carriers that cross it every day. Book a 20-min demo See the platform - 22 modules - 716 capabilities, all live - 100% in production today - Ontario built and run ## One record. Eleven steps. Typed once. A shipment enters Lanexa at the quote and leaves it as a settled driver payment. Every step below reads from the same record — which is why nothing is re-keyed at a department boundary, and why nothing quietly goes missing there either. - Quote price the job - Load customer books it - Trip plan the run - Assign driver + truck - Border ACE / ACI filed - Pickup BOL signed - Deliver freight lands - Proof POD on file - Invoice customer billed - Collect money in, partners paid - Settle driver paid ## One platform. The whole operation. 01 ◉ Dashboard The screen you open first. Today's loads, what is stuck, what is owed and which credentials are about to expire — on one page. 02 ▤ Loads The book of every shipment you have agreed to haul, from pending to paid. Drop in a rate-confirmation PDF and the fields fill themselves. 03 ⇄ Trip Board The dispatcher's command centre. Drag and drop a trip onto a truck, watch it on the map, and pop the load pool onto a second monitor. 04 ◫ Load Status The triage wall. Every live load as a card, a timeline or a map — so what is late shows itself instead of being discovered. 05 ◈ eManifest ACE and ACI prepared, validated and barcoded in-app, with PARS and PAPS labels and a broker packet built from the load you already have. 06 ⇉ Interline Desk Hand a load to a partner carrier with an offer clock and live margin — and the bill you owe them writes itself at proof of delivery. 07 ≈ Quotes Price against your own lane history, send it as a PDF, and let the customer accept online without an account or a login. 08 ◍ Unified Communications SMS, WhatsApp and email in one threaded inbox — every conversation anchored to the load it belongs to. 09 ◱ Fleet Trucks, trailers and yards in one registry, with availability, position and a lifetime history that cannot be rewritten. 10 ◐ Drivers Everyone who turns a wheel for you — licences, medicals, time off — with expiry alerts that actually reach somebody. 11 ◧ Customers Every shipper and broker with their loads, terms, revenue and credit limit. An over-limit customer is stopped before the load moves. 12 $ Billing Invoices built from the load, AR aging, credit memos and statements — and an invoice cannot go out until its paperwork is attached. 13 ▽ Accounts Payable Carrier bills entered, approved, paid and papered — with a duplicate-bill check watching for the same invoice twice. 14 ¤ Payroll & Settlements Company, owner-operator and team pay splits, calculated from the trip. A settlement needs a second person before it is released. 15 ⊞ Ledger A real double-entry general ledger inside the TMS. Every invoice, bill, settlement and fuel receipt posts itself. Void one and it unposts. 16 ▦ Documents BOLs, PODs, rate cons and permits filed to the right load automatically against a 49-code catalog, with a full provenance trail. 17 ◷ Compliance, IFTA & Safety Credential expiries, an accident register, and quarterly IFTA built from a four-source mileage engine with per-litre Canadian rates. 18 ◆ Analytics Revenue, margin, on-time delivery and lane profitability across any date range — and it tells you when the data behind a number is thin. 19 ▥ Reports Twenty-one registers, a custom report builder, and 360 views that put everything about one truck, driver, trailer or customer on a page. 20 ◎ Activity & Audit Log Who did what, when, and what it was before. Each entry is sealed to the one before it, so a change would show. 21 ⚙ Settings Company profile, tax rules, chart of accounts, rate cards, users and roles — eleven role templates and thirty-nine permissions. 22 ⊟ Multi-Company Run several companies from one login. Books, loads and users stay separate — the database keeps them apart on every query. ## Every re-typing is where money leaves. A missed accessorial. An invoice that never went out. A border filing that arrived late. A driver paid on the wrong rate. None of it is dramatic, and all of it is expensive — and every one of them happens at a boundary between two systems that do not talk. ## Canada runs this lane. So do we. The dispatch desks running the Canada–US corridor work differently, and the product is built that way: eManifest inside the load, IFTA in litres, invoices in CAD, and customer documents that come out in English or French. Built and run in Canada by Cygnik Tech. 22 Modules, one platform 716 Capabilities, all live 100% Of what we list is live CA·US·MX Cross-border coverage Talk to our Canadian team Toronto Oakville Kitchener Niagara Falls Rochester London Brampton Mississauga Hamilton St. Catharines Peace Bridge Buffalo, NY N ❚❚ Load L-0248 Brampton, ON → Buffalo, NY · Dry van · 42,000 lb ETA 09:05 on time - 06:12 Dispatched - 06:48 On the 401 → QEW - 07:25 Skyway · on time - 08:02 ACE manifest accepted - 08:41 Border · CBP wait 12 min Live wait time from CBP. Detention at the crossing becomes a billable line automatically. - 09:05 Delivered · POD by link A synthetic load on a real map. Every event shown is something the product does today. ## The border is a routing decision. Not a second platform. Thirty-two eManifest capabilities, twenty-nine of them live — including the two states most systems skip: rejected, and amended after acceptance. ACE ### US eManifest Filed before you dispatch. PARS barcodes generated in-app, printed to the rate con. ACI ### Canada eManifest Southbound returns filed automatically on the return leg. Drivers never touch a portal. PARS / PAPS ### Barcodes, bonded Auto-numbered, auto-linked to the shipment, auto-sent to the broker. Gone from your todo. CBSA ### Compliance Trusted Trader flags, bond balances, FAST lane eligibility — in the load record, not in your email. ## Built in Canada. Run from Canada. Lanexa is built and run in Ontario by Cygnik Tech — close to the carriers it serves, in the same time zone, and easy to reach when it matters. ## A Canadian company that stands behind its work. Built in Canada and run from Canada — real people you can reach in your own time zone, responsible for the software you run on. Being close to the carriers we serve isn't a detail. It's the point. INC. ### A real Canadian company Lanexa is built and run from Ontario by Cygnik Tech, our Canadian company — a real business with a real address and real people behind it, close to the carriers we serve rather than half a world away. OUR WORD ### We stand behind what we promise Your agreement is with a Canadian company that works to Canadian standards and is here to honour it. When you need us we're reachable, in your time zone, and responsible for the software you run your business on. INSURED ### Properly insured, right here We carry our business insurance in Canada, for Canadian clients, in Canadian dollars — so the protection standing behind your service is real and local, valued the way you'd expect at home. PIPEDA ### Your data stays in Canada Hosted in Canada and handled under Canadian privacy law (PIPEDA). Your freight and customer information stays home, under the rules you already know. Plenty of software is run from far away, by people you'll never quite reach. We built Lanexa the other way — a Canadian company, close to the people it serves, easy to reach and glad to be. When your business depends on it, that closeness is worth everything. ## Already on something else? We'll move you in 15–30 days. Timeline depends on fleet size and data complexity — data migration scripts, a parallel-run period, and a Canadian team that's done this before. Simplest transition Spreadsheets & paper Up and running in as little as 15 days. → Keep what works WhatsApp & manual tracking We plug into existing habits — no retraining shock. → Data export + import Legacy / on-prem TMS Full load, driver and customer history migrated. → API or CSV migration Another cloud TMS Most fleets are live within 20–30 days. → ## Priced per user. Not per truck. Lane · Most popular Coming soon Per-user pricing · CAD Everything a carrier needs to run day to day — dispatch, file at the border, bill and get paid. - Trip Board & Load Board — dispatch across Canada, the US & Mexico - eManifest — ACE / ACI / PARS / PAPS filed in-app - Billing & invoicing — QuickBooks Online sync (CAD & USD) - Driver settlement & pay - Fleet & asset management (truck, trailer, yard) - Customer records & branded tracking portal - Document management (BOL, POD, rate con) - Compliance — credential expiries & quarterly IFTA - Email & SMS driver messaging Join the waitlist Corridor Coming soon Per-user pricing · CAD For growing operations that want the premium layer — unified comms, deeper analytics, multi-company and enterprise controls. - Everything in Lane - Unified Communications Hub — SMS, WhatsApp & email in one inbox - Interline Desk — tender to partners, carrier bill writes itself - Advanced analytics & reporting — executive & financial BI - Activity & audit log — tamper-evident - Multi-organization operations - Single sign-on - Onboarding support Talk to us Owner-operators Running a single truck? Lanexa Solo is on the way — a free tier for one-truck operations to run loads, documents and invoicing without a subscription. Tell us you want it and you'll be first in. ## Run your corridor like you mean it. Twenty minutes with someone who has dispatched freight on this corridor. A working demo on your own lanes. A straight answer on what is built. Get early access Talk to a human · (888) 777-1672 Book a 20-min demo ### What happens next - A 20-minute call with someone who has run dispatch on the Canada–US corridor — not a sales script. - A demo on your lanes , with your border crossings, your customers' paperwork, and your pay rules. - A straight answer on what is built today and what isn't. Our full capability list is published, so nothing is a surprise later. Office Suite 400 – 1940 Eglinton Ave E Scarborough, ON M1L 4R1 Phone (888) 777-1672 Email info@cygnik.com Hours Eastern time — your dispatch desk's time zone Built and run in Ontario by Cygnik Tech. Your data stays in Canada under PIPEDA. --- ## Changelog — What Changed and When | Lanexa URL: https://lanexa.io/changelog Summary: A dated record of capability status changes. Baseline: 716 capabilities live in production, as of 2026-08-24. Changelog # What changed, and when. The capability ledger is only meaningful if it moves. This page records the movement — every time something goes from planned, to in progress, to live. It is also the honest test of the ledger: a visitor who saw a capability listed as unbuilt in September and finds it live in November has learned something no testimonial could tell them. ## The baseline. Entries start from the capability register snapshot below rather than being reconstructed backwards. We would rather begin an honest record today than publish a history we cannot evidence line by line. 01 Capability register published 716 capabilities live across 22 modules · version 2.0.37 2026-08-24 ## What this page will fill with. What we have chosen not to build yet is listed by name, and each item is a future entry here. These are the modules with the most still to come — which is also, deliberately, public information. Analytics 12 capabilities still to come. 25 live today Accounts Payable 11 capabilities still to come. 24 live today Multi-Company 11 capabilities still to come. 12 live today Drivers 10 capabilities still to come. 20 live today Activity & Audit Log 7 capabilities still to come. 32 live today Quotes 6 capabilities still to come. 35 live today See what we haven’t built, by name Open the full ledger --- ## How Lanexa Compares to How You Work Today URL: https://lanexa.io/compare Summary: An honest comparison against the three ways carriers actually run today — spreadsheets, a dispatch tool plus accounting, or a TMS plus a customs specialist. Approaches, not competitors. Compare # Compared to how you work today. We do not publish comparisons against named products. Partly because they go stale the week the other vendor ships something, and partly because the honest competitor for most carriers is not a vendor at all — it is the arrangement they already have. 01 Spreadsheets, email and a whiteboard Free, flexible, familiar, and completely dependent on the person holding it together. Plenty of real carriers run real businesses this way, and it works right up until it doesn't. 02 A dispatch system plus an accounting package Two good products, each strong at its own job, with a person in between reconciling them. The gap between the two is where the money leaks. 03 A general TMS plus a customs specialist Deep at the border, disconnected from the shipment. The specialist knows customs better than any TMS vendor does — and knows nothing about the load until someone tells it. ## Questions worth asking any vendor. Including us. Every one of these has a specific answer, and a vendor who cannot give you one is telling you something. Does it post to a general ledger, or export to one? The difference decides whether your books are current or reconstructed monthly. What happens when I void an invoice? If the accounting entry does not unpost with it, someone is fixing that by hand later. Can you show me which capabilities are not built? Every product has gaps. The question is whether you find out now or in week three. Who can see rate and margin fields? If the answer is "everyone with a login", that is a decision someone made for you. Where does my data physically live? And under whose privacy law, which is a different question from where the company is. What does the border filing actually do? Prepared, or transmitted? Both are useful. They are not the same claim. Our answer to question three And what we haven't built --- ## Lanexa vs Spreadsheets, email and a whiteboard — How They Compare URL: https://lanexa.io/compare/spreadsheets-and-email Summary: Free, flexible, familiar, and completely dependent on the person holding it together. Plenty of real carriers run real businesses this way, and it works ri Compare / Spreadsheets, email and a whiteboard # Running on spreadsheets, email and a whiteboard. Free, flexible, familiar, and completely dependent on the person holding it together. Plenty of real carriers run real businesses this way, and it works right up until it doesn't. ## Being fair about it. This approach is not a mistake. It is how almost every carrier starts, it costs nothing, and it bends to whatever you need on a given Tuesday. The question is not whether it works — it is how much re-typing it needs, and what that costs you over a year. ## Where the work crosses a line. The useful comparison is not a feature checklist — it is how many times the same shipment has to be entered. Every row below is a hand-off, and every hand-off is a chance for something to be typed wrong or not typed at all. | The hand-off | Spreadsheets, email and a whiteboard | Lanexa | | Quote to load | Retyped from an email into a sheet | The accepted quote becomes the load | | Load to border filing | Retyped into the customs portal | The filing is built from the load | | Delivery to invoice | Retyped into accounting | The invoice is raised from the load | | Invoice to books | Retyped, or reconciled monthly | Posts to the ledger on its own | | Trip to driver pay | Rebuilt from trip sheets | Calculated from the trip | | Fuel receipts to IFTA | Reconstructed at quarter-end | Assembled through the quarter | ## Where this approach genuinely wins. It costs nothing to start No subscription, no implementation, no decision to justify to anyone. It bends instantly A new customer wants something unusual? Add a column. No vendor, no roadmap, no waiting. Everyone already knows how There is no training cost, and no risk of a tool being rejected by the people meant to use it. ## Where it breaks down. It breaks on people, not on volume. The system lives in one person's head and in files only they maintain confidently. When they are away, the operation slows; when they leave, some of it goes with them. The second failure is quieter: nothing is recorded well enough to be checked later, so a missed accessorial or an unbilled load is not discovered, because there is nothing to discover it against. ## Other ways of working. A dispatch system plus an accounting package ↗ A general TMS plus a customs specialist ↗ Compared as of August 2026. We compare approaches rather than named products, because a named comparison goes stale the week the other vendor ships something — and because our own capability list is published in full, you can check every claim we make about ourselves. --- ## Lanexa vs A general TMS plus a customs specialist — How They Compare URL: https://lanexa.io/compare/tms-plus-customs-service Summary: Deep at the border, disconnected from the shipment. The specialist knows customs better than any TMS vendor does — and knows nothing about the load until s Compare / A general TMS plus a customs specialist # A general TMS alongside a customs service. Deep at the border, disconnected from the shipment. The specialist knows customs better than any TMS vendor does — and knows nothing about the load until someone tells it. ## Being fair about it. Customs specialists are specialists for a reason. They handle edge cases a general product will not, they keep up with rule changes as a full-time job, and if your cross-border volume is complex enough, that expertise is worth paying for. This comparison is not an argument against them. ## Where the work crosses a line. The useful comparison is not a feature checklist — it is how many times the same shipment has to be entered. Every row below is a hand-off, and every hand-off is a chance for something to be typed wrong or not typed at all. | The hand-off | A general TMS plus a customs specialist | Lanexa | | Quote to load | Handled in the TMS | The accepted quote becomes the load | | Load to border filing | Retyped into the customs tool | The filing is built from the load | | Filing rejected | Discovered in the other system, by phone | The load knows, on the board | | Delivery to invoice | Handled in the TMS | The invoice is raised from the load | | Border paperwork to the file | Emailed, then filed by hand | Filed against the load automatically | | Load changed after filing | Remember to amend, in two places | Amendment is part of the filing lifecycle | ## Where this approach genuinely wins. Genuine depth at the border Unusual commodities, complex entries and rule changes are their entire business rather than one module of it. A person to call A specialist service usually comes with expertise attached, which software does not replace. It scales past us At high complexity or high volume, a dedicated customs operation is the right answer and we would say so. ## Where it breaks down. When the load changes. A filing is only correct as of the moment it was made, and freight changes — a trailer swap, a driver change, an added shipment. In a two-system arrangement the TMS knows and the customs tool does not, and the gap between them is discovered at the border rather than in the office. The second break is rejection: it arrives somewhere the load record cannot see. ## Other ways of working. Spreadsheets, email and a whiteboard ↗ A dispatch system plus an accounting package ↗ Compared as of August 2026. We compare approaches rather than named products, because a named comparison goes stale the week the other vendor ships something — and because our own capability list is published in full, you can check every claim we make about ourselves. --- ## Lanexa vs separate accounting — How They Compare URL: https://lanexa.io/compare/tms-plus-separate-accounting Summary: Two good products, each strong at its own job, with a person in between reconciling them. The gap between the two is where the money leaks. Compare / A dispatch system plus an accounting package # A dispatch tool plus a separate accounting package. Two good products, each strong at its own job, with a person in between reconciling them. The gap between the two is where the money leaks. ## Being fair about it. There is nothing wrong with either half of this arrangement. Dispatch software that focuses on dispatch is usually good at dispatch, and accounting packages are mature, well understood and trusted by the person who has to sign the return. The problem is not the tools. It is the seam. ## Where the work crosses a line. The useful comparison is not a feature checklist — it is how many times the same shipment has to be entered. Every row below is a hand-off, and every hand-off is a chance for something to be typed wrong or not typed at all. | The hand-off | A dispatch system plus an accounting package | Lanexa | | Quote to load | Usually handled inside the dispatch tool | The accepted quote becomes the load | | Load to border filing | A separate portal or service | The filing is built from the load | | Delivery to invoice | Exported, or retyped, into accounting | The invoice is raised from the load | | Invoice to books | Import, then reconcile | Posts to the ledger on its own | | Trip to driver pay | Often a third system or a spreadsheet | Calculated from the trip | | Fuel receipts to IFTA | A fourth process entirely | Assembled through the quarter | ## Where this approach genuinely wins. Your accountant already trusts it The accounting half is familiar, audited and unlikely to surprise anyone at year end. Best-of-breed on each side You are not compromising on dispatch to get accounting, or the other way round. Switching one does not mean switching both The two halves can be replaced independently, which is genuine flexibility. ## Where it breaks down. At the seam, and only at month end. The dispatch system says one thing and the books say another, the difference is small enough to be plausible, and finding it is somebody's afternoon. Meanwhile the things that should have been billed at the moment they happened — detention, an extra stop, a lumper fee — never made the crossing, because the person raising the invoice was not the person who saw them. ## Other ways of working. Spreadsheets, email and a whiteboard ↗ A general TMS plus a customs specialist ↗ Compared as of August 2026. We compare approaches rather than named products, because a named comparison goes stale the week the other vendor ships something — and because our own capability list is published in full, you can check every claim we make about ourselves. --- ## Contact / Book a Demo | Lanexa URL: https://lanexa.io/contact Summary: Talk to the team building Lanexa. Book a demo, ask a question, or join the early-access list. Built and run in Canada by Cygnik Tech. Home / Contact # Let's talk . Real humans on the corridor. Tell us a bit about your fleet and we'll get back to you within one business day. Built in Canada, priced in CAD — and yes, we answer the phone. Name * Company Email * Phone * Anything we should know? Send to our team By submitting, you agree we may email or call you about Lanexa. Your information stays with Lanexa and our parent, Cygnik Tech — we do not sell or share contact details. Lanexa Suite 400 – 1940 Eglinton Ave E Scarborough, ON M1L 4R1 Canada (888) 777-1672 info@cygnik.com Parent company Cygnik Tech Lanexa is designed and developed by Cygnik Tech, a Canadian product studio building software for the trucking and logistics industry. Visit cygnik.tech --- ## Who We Serve — Carriers, Brokers, 3PLs & Owner-Operators | Lanexa URL: https://lanexa.io/customers Summary: Lanexa for Canadian carriers, freight brokers, 3PLs and owner-operators — and for the dispatchers, owners, accountants and drivers who actually use it. Who we serve # Same system. Four different days. A dispatcher, an owner, a bookkeeper and a driver want completely different things from the same shipment record. Rather than a single tour that suits none of them, each has its own page — with the friction it actually removes, and the modules that person would live in. ## By the job you do. 01 Dispatchers You are the integration layer. You shouldn't have to be. The person holding it together 02 Owners You can feel the money leaking. You just can't find where. Running the business 03 Accounting & billing You shouldn't be rebuilding the same shipment a third time. Where the money actually lands 04 Drivers There is no app for your drivers to install. The one who has to actually use it ## By the business you run. 01 Carriers One system from the first phone call to the settled driver. Asset-based, 10 to 200 power units 02 Freight brokers Price it, win it, cover it, bill it — on one record. Freight-first, ops-light 03 3PLs The loads you move and the loads you hand over, in one set of books. Asset-light, customer-heavy 04 Owner-operators The paperwork shouldn't be waiting for you after a full day of driving. One truck, no back office ## Underneath, it is one product. 22 modules and 716 live capabilities, 716 of them live. There is no accounting add-on and no cross-border module to buy separately — which is why the dispatcher's border filing and the bookkeeper's invoice are reading the same record. See the platform Read the capability ledger --- ## Dispatch — Trip Board & Load Board | Lanexa URL: https://lanexa.io/dispatch Summary: Drag-and-drop trip board with unified driver communications over SMS, WhatsApp and email. Built for Canadian carriers running 10–200 power units across cross-border corridors. Home / Product / Dispatch # Dispatch built like a logistics company thinks. A board, a driver, one thread across every channel. Everything else is a distraction. Book a 20-min demo See the modules Compliance Billing Tracking Driver Comms Dispatch Board One board · live Brampton → Buffalo In transit Mississauga → Detroit Assigned Oakville → Cleveland At pickup ## The single pane your dispatcher lives in. Loads, drivers, documents, billing, tracking and compliance — six tools collapsed into one board your team never has to leave. Pick a load below and watch the record follow it. Loads · Today DDT-L0248 Brampton, ON → Buffalo, NY transit DDT-L0249 Mississauga, ON → Detroit, MI assigned DDT-L0247 Brampton, ON → Erie, PA delivered DDT-L0250 Toronto, ON → Rochester, NY assigned DDT-L0251 Oakville, ON → Syracuse, NY transit Load · DDT-L0248 Brampton, ON → Buffalo, NY Pickup 06:00 Delivery 13:44 Driver Gurpreet S. · Unit 12 Status transit Brampton Buffalo Driver · unified inbox Morning boss — any loads for tomorrow? 04:38 Brampton, ON → Buffalo, NY . 06:00 pickup. 04:38 ✓✓ Copy. Heading out. 04:40 Assign to driver ## One board, instead of a portal, a spreadsheet and a phone. 01 One-click assign Drag, drop, done. Driver gets it over SMS, WhatsApp or email. You get the ack. 02 Exception-first The board doesn't show you loads going fine. It shows you loads going wrong. 03 Auto-status ELD ping, a photo over any channel, POD signature — status changes without a keystroke. 04 Detention clock Starts when the truck hits the geofence. Bills without an argument. 05 HOS-aware Lanexa refuses to assign a load a driver can't legally finish. You never have to check. 06 Driver-friendly Simple, fast, and the same thread they already use — reached over the channel they read, no new app to learn. ## Run your corridor like you mean it. Twenty minutes with someone who has dispatched freight on this corridor. A working demo on your own lanes. A straight answer on what is built. Get early access Talk to a human · (888) 777-1672 Book a 20-min demo ### What happens next - A 20-minute call with someone who has run dispatch on the Canada–US corridor — not a sales script. - A demo on your lanes , with your border crossings, your customers' paperwork, and your pay rules. - A straight answer on what is built today and what isn't. Our full capability list is published, so nothing is a surprise later. Office Suite 400 – 1940 Eglinton Ave E Scarborough, ON M1L 4R1 Phone (888) 777-1672 Email info@cygnik.com Hours Eastern time — your dispatch desk's time zone Built and run in Ontario by Cygnik Tech. Your data stays in Canada under PIPEDA. --- ## Freight & Cross-Border Glossary | Lanexa URL: https://lanexa.io/glossary Summary: Plain-English definitions of the freight, customs and compliance terms Canadian carriers actually deal with — PARS, PAPS, ACE, ACI, IFTA and more, explained operationally. Glossary # The words, defined once. Freight is full of terms that sound interchangeable and are not, and most definitions online are written by the agency that owns the term rather than for the dispatcher who has to act on it. These are written the other way round: what it is, who deals with it, when it shows up, and what usually goes wrong. ## Crossing the border ACE — Automated Commercial Environment ACE is the United States Customs and Border Protection system that carriers file an electronic truck manifest into before a shipment crosses into the US, listing the truck, driver, trailer, shipments and their entry references. ACI — Advance Commercial Information ACI is the Canada Border Services Agency programme requiring carriers to transmit an electronic cargo and conveyance manifest before a truck arrives at the Canadian border, so CBSA can risk-assess the shipment in advance. PAPS — Pre-Arrival Processing System PAPS is the US Customs and Border Protection process that lets a customs broker file entry information before a truck reaches the United States border, so the shipment can be processed on arrival instead of at the booth. PARS — Pre-Arrival Review System PARS is the Canada Border Services Agency process that lets a customs broker submit release information before a truck reaches the Canadian border, so the shipment can be reviewed and released on arrival rather than held at the booth. ## Compliance and regulation IFTA — International Fuel Tax Agreement IFTA is an agreement among 48 US states and 10 Canadian provinces that lets a carrier file one quarterly fuel tax return covering every jurisdiction it ran in, based on distance travelled in each and fuel purchased in each. SCAC — Standard Carrier Alpha Code A SCAC is the two-to-four letter code that uniquely identifies a motor carrier in North American freight and customs systems, issued by the National Motor Freight Traffic Association. ## Day-to-day operations BOL — Bill of Lading A bill of lading is the contract of carriage issued at pickup — it records what is being shipped, who is shipping it, where it is going, and on what terms the carrier accepts it. POD — Proof of Delivery A proof of delivery is the signed document confirming freight arrived and was accepted, and it is usually the thing a customer requires before they will pay the invoice for it. Probill — Progressive bill number A probill is the carrier-facing reference number that identifies a shipment on paperwork — the number printed on the bill of lading and rate confirmation that everyone quotes when they call about a load. TONU — Truck Ordered, Not Used TONU is a charge billed when a load is cancelled after a truck has already been committed to it, compensating the carrier for capacity that was reserved and can no longer be sold. ## Money Accessorial An accessorial is any charge on a load beyond the line-haul rate — detention, lumper fees, tarping, scale tickets, advances, layover and similar — billed for work or delay outside the basic move. Detention Detention is a charge billed to a customer when a truck is held at a pickup or delivery beyond an agreed free period, compensating the carrier for capacity lost while the driver waits. --- ## What is Accessorial? | Lanexa Glossary URL: https://lanexa.io/glossary/accessorial Summary: An accessorial is any charge on a load beyond the line-haul rate — detention, lumper fees, tarping, scale tickets, advances, layover and similar — billed f Glossary / Accessorial # Accessorial An accessorial is any charge on a load beyond the line-haul rate — detention, lumper fees, tarping, scale tickets, advances, layover and similar — billed for work or delay outside the basic move. ## In plain terms. The line-haul rate covers getting freight from A to B. Everything else that happened on the way is an accessorial: the two hours waiting at the dock, the lumper who unloaded it, the extra stop, the tarp, the reweigh. Individually they are small, which is exactly why they leak. A single missed accessorial is not worth chasing; a missed accessorial on every third load across a year is a meaningful share of margin that never reaches an invoice. They are lost at the boundary between the person who experienced the charge — usually the driver — and the person raising the bill, who was not there. WHO ### Who deals with it Incurred by the driver, communicated to dispatch, billed by accounting. WHEN ### When it shows up During the move, and then again at invoicing when someone has to remember it. RISK ### What goes wrong It never makes the invoice. Nobody wrote it down at the time, and by billing day the detail has gone. ## How Lanexa handles it. This lives in Billing , where 46 capabilities are live. A catalogue, not free text Charges come from a defined catalogue with agreed rates, so the same thing is not billed three different ways by three different people. Some raise themselves Detention is derived from stop timestamps and fuel surcharge from the published diesel index, so two of the most commonly missed charges do not depend on being remembered. ## Related terms. Detention money ↗ TONU Truck Ordered, Not Used ↗ --- ## What is ACE (Automated Commercial Environment)? | Lanexa Glossary URL: https://lanexa.io/glossary/ace Summary: ACE is the United States Customs and Border Protection system that carriers file an electronic truck manifest into before a shipment crosses into the US, l Glossary / ACE # ACE — Automated Commercial Environment ACE is the United States Customs and Border Protection system that carriers file an electronic truck manifest into before a shipment crosses into the US, listing the truck, driver, trailer, shipments and their entry references. ## In plain terms. ACE is the filing the carrier is responsible for, as distinct from the entry the broker files. It describes the conveyance — which tractor, which trailer, which driver, which shipments are aboard — and it has to be transmitted and accepted before the truck reaches the border, with a required lead time. The two filings are easy to confuse because both are called the manifest in conversation. The practical split: the broker handles the commercial entry for the goods, the carrier handles ACE for the truck carrying them. If the ACE manifest is wrong or late, it does not matter how clean the entry is — the truck is the problem. WHO ### Who deals with it The carrier files it, usually the dispatcher, and it is the carrier's legal responsibility rather than the broker's. WHEN ### When it shows up Before arrival, with a mandatory lead time. Late is treated as not filed. RISK ### What goes wrong A plate number that does not match the trailer actually hooked, a driver swapped after filing, or a shipment added at the last minute without amending. Each can draw a penalty as well as a delay. ## How Lanexa handles it. This lives in eManifest , where 29 capabilities are live. Built from the load you already have Truck, trailer, driver and shipment details come off the trip record rather than being re-entered into a separate portal. A lifecycle with the awkward states Seven states including rejection and amendment after acceptance — the ones that actually happen at a border and that most systems leave you to handle by phone. ## Related terms. ACI Advance Commercial Information ↗ PAPS Pre-Arrival Processing System ↗ SCAC Standard Carrier Alpha Code ↗ --- ## What is ACI (Advance Commercial Information)? | Lanexa Glossary URL: https://lanexa.io/glossary/aci Summary: ACI is the Canada Border Services Agency programme requiring carriers to transmit an electronic cargo and conveyance manifest before a truck arrives at the Glossary / ACI # ACI — Advance Commercial Information ACI is the Canada Border Services Agency programme requiring carriers to transmit an electronic cargo and conveyance manifest before a truck arrives at the Canadian border, so CBSA can risk-assess the shipment in advance. ## In plain terms. ACI is the Canadian equivalent of ACE, and the same division of labour applies: the carrier files the conveyance and cargo manifest, the customs broker handles the release using a PARS number. CBSA requires the transmission at least one hour before arrival for highway carriers, which is the rule most often breached by a dispatcher trying to be helpful about a last-minute load. For a carrier running both directions, ACI and ACE are two filings, two systems and two sets of rules covering the same truck on the same day. That duplication is precisely why border work tends to end up with one specialist person in the office, and why it stops when that person is away. WHO ### Who deals with it The carrier, under its own carrier code. A broker cannot file it on the carrier's behalf. WHEN ### When it shows up At least one hour before the truck reaches the border, for highway shipments. RISK ### What goes wrong Missing the one-hour rule, a cargo control number that does not match the broker's release, or a conveyance detail changed after transmission without an amendment. ## How Lanexa handles it. This lives in eManifest , where 29 capabilities are live. Both directions in one place Northbound and southbound filings are prepared from the same load record, so a carrier running a round trip is not switching systems mid-journey. The clock is visible The filing sits on the load rather than in someone's inbox, so the one-hour rule is something the board shows you rather than something you remember. ## Related terms. ACE Automated Commercial Environment ↗ PARS Pre-Arrival Review System ↗ --- ## What is BOL (Bill of Lading)? | Lanexa Glossary URL: https://lanexa.io/glossary/bol Summary: A bill of lading is the contract of carriage issued at pickup — it records what is being shipped, who is shipping it, where it is going, and on what terms Glossary / BOL # BOL — Bill of Lading A bill of lading is the contract of carriage issued at pickup — it records what is being shipped, who is shipping it, where it is going, and on what terms the carrier accepts it. ## In plain terms. It is three things at once: a receipt for the freight, a contract between shipper and carrier, and a description of the goods that customs and consignees rely on. It is created at pickup, travels with the load, and is signed at delivery to become the proof of delivery. Because it is a contract, what is written on it matters later. Weights, piece counts, commodity descriptions and any noted damage are the reference point in a claim, and a cross-border shipment inherits those details into its customs filing. A bill of lading typed carelessly at six in the morning becomes a customs discrepancy at the border and a disputed claim months afterwards. WHO ### Who deals with it Produced by the carrier or shipper at pickup, signed by the driver, and signed again by the receiver at delivery. WHEN ### When it shows up At pickup, before the freight moves. RISK ### What goes wrong Details that do not match the freight or the customs filing — piece counts, weight, commodity — which surface at the border or in a claim rather than at the dock. ## How Lanexa handles it. This lives in Documents , where 30 capabilities are live. Generated from the load The document is produced from the shipment record you already built, so the description on the paperwork and the description on the filing come from one source. Available in English or French Customer-facing documents render in the company's document language, which matters for shipments touching Quebec. ## Related terms. POD Proof of Delivery ↗ Probill Progressive bill number ↗ --- ## What is Detention? | Lanexa Glossary URL: https://lanexa.io/glossary/detention Summary: Detention is a charge billed to a customer when a truck is held at a pickup or delivery beyond an agreed free period, compensating the carrier for capacity Glossary / Detention # Detention Detention is a charge billed to a customer when a truck is held at a pickup or delivery beyond an agreed free period, compensating the carrier for capacity lost while the driver waits. ## In plain terms. Most contracts give a shipper or receiver a couple of hours to load or unload. After that, the clock is billable. The rate and the free period are agreed in advance, so detention is rarely disputed in principle — what gets disputed is whether it happened, and for how long. That is the whole problem. Detention is almost never lost because the customer refuses to pay it. It is lost because nobody recorded when the truck actually arrived and left, so a week later there is a recollection on one side and a denial on the other, and the carrier drops it rather than argue. It is one of the most reliable revenue leaks in trucking, and it leaks quietly. WHO ### Who deals with it The driver experiences it, dispatch hears about it, and billing has to justify it to a customer who was not there. WHEN ### When it shows up At any stop that runs long, which means it competes for attention with whatever else is going wrong that day. RISK ### What goes wrong It goes unrecorded. By the time the invoice is raised, the arrival and departure times are a memory rather than a record, and the charge is quietly written off. ## How Lanexa handles it. This lives in Billing , where 46 capabilities are live. Dwell is calculated, not remembered Arrival and departure timestamps already exist on the trip stop, so the waiting time is derived rather than reconstructed from someone's recollection. It reaches the invoice as a real line The suggested charge lands on the load as an accessorial for someone to confirm, so the conversation with the customer starts from a record instead of an assertion. ## Related terms. Accessorial money ↗ TONU Truck Ordered, Not Used ↗ POD Proof of Delivery ↗ --- ## What is IFTA (International Fuel Tax Agreement)? | Lanexa Glossary URL: https://lanexa.io/glossary/ifta Summary: IFTA is an agreement among 48 US states and 10 Canadian provinces that lets a carrier file one quarterly fuel tax return covering every jurisdiction it ran Glossary / IFTA # IFTA — International Fuel Tax Agreement IFTA is an agreement among 48 US states and 10 Canadian provinces that lets a carrier file one quarterly fuel tax return covering every jurisdiction it ran in, based on distance travelled in each and fuel purchased in each. ## In plain terms. The idea is simple and the arithmetic is not. You pay fuel tax where you burn the fuel, not where you buy it. So every quarter you report how far you ran in each jurisdiction and how much fuel you bought in each, and the difference is settled — you owe some jurisdictions and are credited by others. For a Canadian carrier the awkward part is units. Fuel is bought in litres and taxed per litre at home, and in gallons across the border, and the rates change quarterly. A system that assumes gallons will be wrong for every Canadian purchase, quietly, in a way that only surfaces under audit. WHO ### Who deals with it Whoever does the books, usually with the dispatcher supplying mileage and the driver supplying receipts. WHEN ### When it shows up Quarterly, with the filing due the month after the quarter closes. RISK ### What goes wrong Mileage nobody can defend. If the distance figures come from an odometer note or a car-routing tool, an auditor can reasonably reject the basis of the whole return. ## How Lanexa handles it. This lives in Compliance, IFTA & Safety , where 40 capabilities are live. Four sources of mileage, compared Route geometry split by jurisdiction, telematics, truck-legal mileage and manual entry — shown side by side rather than one picked silently on your behalf. Per-litre Canadian rates Canadian jurisdictions are calculated per litre rather than converted from a gallon rate, which is where a lot of quietly wrong returns come from. ## Related terms. SCAC Standard Carrier Alpha Code ↗ --- ## What is PAPS (Pre-Arrival Processing System)? | Lanexa Glossary URL: https://lanexa.io/glossary/paps Summary: PAPS is the US Customs and Border Protection process that lets a customs broker file entry information before a truck reaches the United States border, so Glossary / PAPS # PAPS — Pre-Arrival Processing System PAPS is the US Customs and Border Protection process that lets a customs broker file entry information before a truck reaches the United States border, so the shipment can be processed on arrival instead of at the booth. ## In plain terms. PAPS is the American counterpart to PARS. A carrier assigns a PAPS number — your SCAC code plus a unique reference — puts it on the paperwork as a barcode, and the customs broker files the entry against it before the truck arrives. CBP processes the entry, and if it is clear the driver is released at primary inspection. The easy way to keep the two straight: PA**P**S has the P of CB**P**, the American agency, so PAPS goes into the United States. PARS, the other one, goes into Canada. Getting them the wrong way round is a common and expensive mistake, because the filing lands with the wrong authority and the truck arrives with nothing on file. WHO ### Who deals with it The carrier assigns the number using its SCAC. The US customs broker files the entry. The driver presents the barcode at the border. WHEN ### When it shows up Before departure, with enough margin for the broker to file and CBP to process. Filing while the truck is in the queue defeats the point. RISK ### What goes wrong A missing or wrong SCAC, a number reused from an earlier load, or an entry filed against paperwork that no longer matches the freight on the trailer. ## How Lanexa handles it. This lives in eManifest , where 29 capabilities are live. Numbered against your SCAC automatically The code comes off your carrier record rather than being typed per load, which removes the most common source of a rejected entry. Barcoded onto the paperwork Generated as a real scannable barcode on the documents the driver carries, not hand-written into a box. ## Related terms. PARS Pre-Arrival Review System ↗ ACE Automated Commercial Environment ↗ SCAC Standard Carrier Alpha Code ↗ --- ## What is PARS (Pre-Arrival Review System)? | Lanexa Glossary URL: https://lanexa.io/glossary/pars Summary: PARS is the Canada Border Services Agency process that lets a customs broker submit release information before a truck reaches the Canadian border, so the Glossary / PARS # PARS — Pre-Arrival Review System PARS is the Canada Border Services Agency process that lets a customs broker submit release information before a truck reaches the Canadian border, so the shipment can be reviewed and released on arrival rather than held at the booth. ## In plain terms. A PARS number is a barcode you put on the paperwork of a load heading into Canada. The carrier generates it, the customs broker uses it to file the release information with CBSA ahead of the truck, and the border officer scans it when the driver arrives. If everything was filed correctly and reviewed in time, the truck is released and keeps moving. The number itself is your carrier code followed by a unique reference you assign. That matters more than it sounds: the number has to be unique per shipment, it has to reach your broker before the truck does, and it has to match what is physically on the paperwork in the cab. Most PARS problems are one of those three things going wrong, not a customs decision going against you. WHO ### Who deals with it The carrier generates the number and puts it on the paperwork. The customs broker files against it. The driver presents it at the primary inspection booth. WHEN ### When it shows up Before the truck leaves for the border — the filing needs to be in and reviewed ahead of arrival, not while the driver is in the queue. RISK ### What goes wrong A duplicate number, a barcode the scanner cannot read, a broker who never received the paperwork, or a load that changed after the filing went in. All of them look the same to a driver: sent to secondary inspection. ## How Lanexa handles it. This lives in eManifest , where 29 capabilities are live. The barcode is generated from the load Auto-numbered against your carrier code, linked to the shipment, and printed onto the paperwork rather than written on by hand. The broker packet is assembled for you The documents your broker needs are gathered from the load record you already built, rather than rebuilt in an email. ## Related terms. PAPS Pre-Arrival Processing System ↗ ACI Advance Commercial Information ↗ --- ## What is POD (Proof of Delivery)? | Lanexa Glossary URL: https://lanexa.io/glossary/pod Summary: A proof of delivery is the signed document confirming freight arrived and was accepted, and it is usually the thing a customer requires before they will pa Glossary / POD # POD — Proof of Delivery A proof of delivery is the signed document confirming freight arrived and was accepted, and it is usually the thing a customer requires before they will pay the invoice for it. ## In plain terms. The bill of lading is the contract at pickup; the proof of delivery is the evidence at the other end. Signed by whoever received the freight, it records that the shipment arrived, in what condition, and when. Commercially it is not paperwork, it is a payment gate. Many customers will not process an invoice without the signed proof attached, which means a POD sitting on a driver's phone is not an administrative loose end — it is unbilled revenue standing still. The gap between delivery and getting the document filed is, for a lot of carriers, the single largest controllable delay in getting paid. WHO ### Who deals with it The driver obtains it, the receiver signs it, billing needs it before the invoice can go out. WHEN ### When it shows up At delivery — and then again, repeatedly, as someone chases the driver for the photograph. RISK ### What goes wrong It exists but never gets filed. The freight was delivered days ago, the customer is waiting to be invoiced, and the document is in a camera roll. ## How Lanexa handles it. This lives in Documents , where 30 capabilities are live. A link, not an app Dispatch sends a request; the driver photographs the document from their phone with no login and no install, and it files itself against the right load. The invoice will not go without it Where a customer requires particular documents, an invoice cannot be created until they are attached — the rule lives in the database rather than in someone's memory. ## Related terms. BOL Bill of Lading ↗ Detention money ↗ Probill Progressive bill number ↗ --- ## What is Probill (Progressive bill number)? | Lanexa Glossary URL: https://lanexa.io/glossary/probill Summary: A probill is the carrier-facing reference number that identifies a shipment on paperwork — the number printed on the bill of lading and rate confirmation t Glossary / Probill # Probill — Progressive bill number A probill is the carrier-facing reference number that identifies a shipment on paperwork — the number printed on the bill of lading and rate confirmation that everyone quotes when they call about a load. ## In plain terms. Every load needs a number people can say out loud. The probill is that number: sequential, unique to your company, and printed on the documents so a driver, a customer and a broker are all talking about the same shipment without ambiguity. It sounds trivial and it is not, because two people creating loads at the same moment must not get the same number. If they do, you have two shipments sharing an identity, and every downstream document — the bill of lading, the rate confirmation, the invoice — inherits the collision. Sorting it out afterwards means correcting paperwork that has already left the building. WHO ### Who deals with it Dispatch creates it, drivers and customers quote it, billing bills against it. WHEN ### When it shows up At load creation, before any paperwork is produced. RISK ### What goes wrong Duplicates, usually from two people creating loads simultaneously or from a numbering scheme kept in a spreadsheet. ## How Lanexa handles it. This lives in Loads , where 44 capabilities are live. Reserved from the database, not guessed Numbers are issued sequentially per company through a database reservation taken when the form opens, so two people creating loads at the same moment cannot collide. The same number everywhere It appears on the load, the paperwork and the invoice from one source, rather than being retyped onto each document. ## Related terms. BOL Bill of Lading ↗ TONU Truck Ordered, Not Used ↗ POD Proof of Delivery ↗ --- ## What is SCAC (Standard Carrier Alpha Code)? | Lanexa Glossary URL: https://lanexa.io/glossary/scac Summary: A SCAC is the two-to-four letter code that uniquely identifies a motor carrier in North American freight and customs systems, issued by the National Motor Glossary / SCAC # SCAC — Standard Carrier Alpha Code A SCAC is the two-to-four letter code that uniquely identifies a motor carrier in North American freight and customs systems, issued by the National Motor Freight Traffic Association. ## In plain terms. It is your carrier's identity in every system that is not looking at your name. Customs filings, electronic messages, load tenders and border references all key off it, and it is the prefix on the PAPS numbers you assign. For a carrier crossing into the United States it is not optional, and it is not something to improvise. A wrong or missing SCAC on a filing means the entry cannot be matched to the truck presenting it, which produces exactly the kind of delay that looks inexplicable from the driver's seat. It also has to be renewed, which is the sort of annual task that quietly lapses. WHO ### Who deals with it Held by the carrier as a company, used by dispatch on every cross-border filing. WHEN ### When it shows up On every US-bound customs reference, and on the paperwork that carries it. RISK ### What goes wrong Typed per load instead of held once, or allowed to lapse at renewal and only discovered at a border. ## How Lanexa handles it. This lives in Settings , where 37 capabilities are live. Held on the carrier record, used everywhere The code lives on your company profile and flows into the filings and barcodes that need it, rather than being retyped per shipment. Checked on partners too Interline partners carry their own authority numbers, and missing identifiers are flagged before a load is tendered to them. ## Related terms. PAPS Pre-Arrival Processing System ↗ ACE Automated Commercial Environment ↗ --- ## What is TONU (Truck Ordered, Not Used)? | Lanexa Glossary URL: https://lanexa.io/glossary/tonu Summary: TONU is a charge billed when a load is cancelled after a truck has already been committed to it, compensating the carrier for capacity that was reserved an Glossary / TONU # TONU — Truck Ordered, Not Used TONU is a charge billed when a load is cancelled after a truck has already been committed to it, compensating the carrier for capacity that was reserved and can no longer be sold. ## In plain terms. A customer books a load, you assign a truck and a driver, the driver heads for the pickup, and then it is cancelled. The freight never moves, so there is no line-haul to bill — but the capacity is gone, the driver has been paid for their day in every practical sense, and the truck cannot be re-sold at short notice. TONU is the charge that covers it. Whether you can bill it depends on what was agreed, which is exactly why it is worth having the commitment recorded somewhere other than a phone call. A TONU load also needs handling carefully inside a system: it is a real commercial event that should be billable, but it is not a shipment that moved, so it must not appear on the dispatch board or feed driver pay as though it had. WHO ### Who deals with it Billing raises it; dispatch is usually the one who knows it happened. WHEN ### When it shows up After a truck has been committed and before the freight moves. RISK ### What goes wrong It gets forgotten. The load is cancelled, everyone moves on, and the charge that was legitimately owed is never raised — which is a quiet, recurring revenue leak. ## How Lanexa handles it. This lives in Billing , where 46 capabilities are live. A terminal state, not a deletion TONU is a real load status with a dedicated fee, so the commercial event survives rather than the record being cancelled away. Kept off the board and out of pay TONU loads are excluded from the dispatch board and from driver-pay calculations, so a billable cancellation cannot accidentally pay someone for a trip they never ran. ## Related terms. Accessorial money ↗ Detention money ↗ Probill Progressive bill number ↗ --- ## Integrations — What Is Actually Connected | Lanexa URL: https://lanexa.io/integrations Summary: Lanexa connects to 10 services today, including QuickBooks Online, Samsara, PC*MILER, Twilio and live CBSA and CBP border wait times. This is the full list. Integrations # What is actually connected. A short list, published honestly, rather than a long one padded with logos of companies we have never exchanged a request with. An integration appears here the day it is connected — not the day somebody put it on a roadmap. ## Connected today. 10 services. Each entry says what it does and where it stops. CONNECTED · Accounting QuickBooks Online Pushes customer invoices and partner-carrier bills into your own QuickBooks, in Canadian and US dollars, through a dedicated sync centre with an error queue and one-click retry. Where it stops: It is one-way, from Lanexa into QuickBooks. It does not pull your existing books back the other way. More on this → CONNECTED · Telematics Samsara Live truck position by scheduled polling, plus pushed events when a truck crosses a geofence or reaches a stop. Where it stops: Requires your own Samsara API key. Other telematics providers are not connected yet. CONNECTED · Mileage PC*MILER Truck-legal mileage between stops, which is the industry standard basis for rating and for fuel-tax filing. Where it stops: A paid per-truck licence you hold, and a real cost line that scales with fleet size. CONNECTED · Messaging Twilio SMS and WhatsApp to drivers, customers and partners, with replies coming back into the same threaded inbox. Voice for the highest-urgency alerts. Where it stops: Requires your own Twilio account and number. CONNECTED · Email Resend and SendGrid Outbound email for invoices, quotes and document requests, sent from your own company domain. Where it stops: Inbound email ingestion into the inbox is not built yet. CONNECTED · Border CBSA and CBP wait times Live border wait times from both agencies, read directly and shown inside the load rather than in another browser tab. Where it stops: Wait times only. Neither agency is a filing channel here. CONNECTED · Fuel US EIA diesel index The published weekly on-highway diesel price that fuel surcharges are calculated from, so the surcharge traces to an official figure on a specific date. Where it stops: Nothing to configure — it is read for you. CONNECTED · Weather Environment Canada, NWS and MET Norway Weather and hazard alerts along the route, from the national services on both sides of the border. Where it stops: Advisory only. It does not re-route a truck for you. CONNECTED · Protection Cloudflare Turnstile Bot protection on every page reachable without logging in — tracking, shared documents, shared quotes and document-upload links. Where it stops: Not a customer-facing feature; it is there so the public pages can exist safely. CONNECTED · Access Single sign-on Sign in with your existing identity provider rather than another password. Where it stops: Requires registration per environment with your provider. ## Built, not switched on. This is the state most vendors would simply list as an integration. It is not one yet, so it says so. BEING BUILT · Border filing BorderConnect The channel that would carry finished customs filings from Lanexa to CBSA and CBP electronically. Built and readiness-checked, with credentials and carrier code stored. Where it stops: It is not switched on. No filing is transmitted through it today — finished filings still travel via your broker or portal. More on this → ## Why the list is short. Because most of what Lanexa does, it does itself. The border filing, the ledger, driver settlement and fuel tax are inside the product rather than integrations to something else — which is the reason there is less to connect than you might expect, and the reason the things that would normally sit between systems do not need to. See what is built in Ask about one that isn't here --- ## Lanexa and BorderConnect — Being built URL: https://lanexa.io/integrations/borderconnect Summary: The channel that would carry finished customs filings from Lanexa to CBSA and CBP electronically. Built and readiness-checked, with credentials and carrier Integrations / BorderConnect BUILT — NOT SWITCHED ON · Border filing # Built, readiness-checked, and not switched on. The channel that would carry finished customs filings from Lanexa to CBSA and CBP electronically. Built and readiness-checked, with credentials and carrier code stored. This is the connection that would carry a finished customs filing from Lanexa to CBSA and CBP electronically. The client is written, the credentials and carrier code have a home in settings, and the readiness check runs. What has not happened is switching it on with a live account. So today Lanexa prepares, validates, barcodes and packages the filing end to end — and then the finished filing travels the way it does now, through your customs broker or the portal. Nothing about that is hidden in a footnote elsewhere on this site; it is stated on the border pages too. It is worth being clear about why this matters more than most integrations. Everything else Lanexa connects to degrades gracefully: if the weather service is unavailable you lose an advisory. Once filings run through this connection, an outage would stop cross-border loads from proceeding — which is exactly why it gets switched on deliberately rather than quietly. TODAY ### Your broker still files The filing is assembled for you; the transmission is not ours yet. STORED ### Credentials have a home API key and SCAC are held in settings, ready for the day it goes live. WE WILL SAY ### You will hear about it When this switches on it becomes a changelog entry and this page changes state. ## Where it stops. It is not switched on. No filing is transmitted through it today — finished filings still travel via your broker or portal. See everything connected What we haven't built --- ## Lanexa and QuickBooks Online — Connected URL: https://lanexa.io/integrations/quickbooks Summary: Pushes customer invoices and partner-carrier bills into your own QuickBooks, in Canadian and US dollars, through a dedicated sync centre with an error queu Integrations / QuickBooks Online CONNECTED · Accounting # A live sync, not a file export. Pushes customer invoices and partner-carrier bills into your own QuickBooks, in Canadian and US dollars, through a dedicated sync centre with an error queue and one-click retry. Most transportation software hands your accountant a CSV. Lanexa pushes the actual records — customer invoices and partner-carrier bills — into your own QuickBooks Online, and does it carefully: the sync first reads what QuickBooks already holds, including customers, tax codes and existing invoice numbers, so it updates rather than duplicates. Because Lanexa also runs its own double-entry ledger, you end up with accounting-grade numbers inside the TMS and the same figures inside the package your bookkeeper already works in. That is deliberate. This is meant to remove the re-typing between the two, not to remove the accountant. It has its own sync centre rather than a checkbox buried in settings, because a sync that can fail needs somewhere to show you what failed. Errors queue with a reason and a one-click retry, and a reconciliation count tells you how many records made it across. AUTH ### You approve it on Intuit’s own screen Lanexa never handles your QuickBooks password. The connection is authorised through Intuit directly. CAD + USD ### Both currencies Invoices carry their own currency, with the exchange rate the entry needs rather than a silent conversion. IF IT IS DOWN ### Nothing is lost Invoices remain complete in Lanexa and the sync catches up later. An outage at Intuit does not stop you billing. ## Where it stops. It is one-way, from Lanexa into QuickBooks. It does not pull your existing books back the other way. See everything connected What we haven't built --- ## The Platform — 22 Modules, One Record | Lanexa TMS URL: https://lanexa.io/platform Summary: Lanexa is 22 modules across six pillars — 716 capabilities, all live in production today. Dispatch, the border and the books in one system. Platform # Twenty-two modules. One record. Twenty-two modules is too many to hold in your head. Six is not. Below they are grouped the way an owner would describe the departments of a trucking company, rather than the way an engineer would describe a codebase — and every one of them reads and writes the same shipment record. 22 Modules 716 Capabilities, all live 100% Of what we list is in production 6 Pillars From the Lanexa 2.0 capability register · version 2.0.37 · reviewed 2026-08-24 · what we have chosen not to build is listed on its own page ## One record. Eleven steps. Typed once. A shipment enters Lanexa at the quote and leaves it as a settled driver payment. Every step below reads from the same record — which is why nothing is re-keyed at a department boundary, and why nothing quietly goes missing there either. - Quote price the job - Load customer books it - Trip plan the run - Assign driver + truck - Border ACE / ACI filed - Pickup BOL signed - Deliver freight lands - Proof POD on file - Invoice customer billed - Collect money in, partners paid - Settle driver paid ## Revenue & Movement This is the business. Everything else exists to serve or observe it — pricing work before it is committed, turning an accepted quote into a load, planning which truck runs it, watching what gets stuck, and handing work to a partner when you cannot cover it yourself. Loads This is the book of every shipment the company has agreed to haul — you write the job down here when a customer books it, you put a driver and truck on it, you watch it move from pickup to delivery, and the moment it delivers the system turns it into an invoice. 44 live Trip Board The Trip Board is the dispatcher's command centre — one screen that shows every truck currently working on top, every piece of booked freight waiting below, and lets the dispatcher build a run, put a driver and a truck on it, and tick off each stop as the day happens. 40 live Load Status Load Status is the wall a dispatcher watches all day — every shipment in the company shown as a card in a lane, on a map, or on a driver calendar, so that moving a load from "booked" to "on the truck" to "delivered" is one drag, and the system refuses the moves that would corrupt the money behind them. 36 live Interline Desk The Interline Desk is where you hand a load you already sold to another trucking company, watch them accept or decline the offer, send them the signed-rate paperwork, and get the bill you owe them created automatically the moment they deliver — while you stay the carrier the customer knows and invoices. 28 live Quotes Quotes is where a price offer is built, priced against your own past lanes and your own cost floor, emailed to the customer as a real PDF with a link they can accept online without an account — and, the moment they accept, turned into a booked Load automatically unless their unpaid bills say otherwise. 35 live ## Resources The people and equipment the business runs on. These three modules answer the same question from different angles — is there a driver, is there equipment, and is the customer good for the money. Fleet Fleet is the one register of every truck, trailer and yard the company owns — what each unit is, where it is sitting right now, whether its plates, insurance and safety papers are still valid, and how hard it has been working. 41 live Drivers Drivers is the people file for everyone who turns a wheel for you — their contact details, their licence and medical paperwork with expiry warnings, their border and dangerous-goods documents, how many hours they have left to drive today, what truck they are married to, when they are on holiday, and every load they have run — held in one screen so a dispatcher never puts an out-of-date driver on a load. 20 live Customers Customers is the one book of everyone who pays you — shippers, brokers, bill-to parties and interline partners — holding their contacts, their credit limit, what they owe you right now, the paperwork you insist on before you invoice them, and the fuel-surcharge terms you agreed to, so that dispatch, billing and the border desk all quote the same firm from the same record. 45 live ## Border & Compliance Most transportation software treats the border as somebody else's problem and fuel tax as a spreadsheet exercise. Here both are first-class parts of the load lifecycle — which, for a carrier running into the United States, is the difference between one system and three. eManifest The eManifest module — called the Border Desk inside the product — is where a dispatcher gets a truck legally across the Canada/US border: it assembles every fact customs demands for a crossing, scores how ready that crossing is, prints the barcoded paper the driver carries, emails the customs broker their package, and runs a countdown clock so nobody arrives at the booth without an accepted filing. 29 live 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. 30 live Compliance, IFTA & Safety This is where a carrier proves it is legal to be on the road — how many hours each driver has left, which licences and medicals are about to expire, what happened in every crash, and the quarterly fuel-tax return that has to be filed with the province or state that issued the plates. 40 live ## Money Money in, money out, and the books that reconcile them. The ledger is what makes this a financial system rather than a billing screen: every invoice, bill, settlement and fuel receipt posts double-entry lines on its own. Billing Billing is where a delivered load turns into a bill the customer actually receives, and where the company watches, chases, corrects and banks the money that comes back. 46 live Accounts Payable Accounts Payable is the screen where you enter every bill another carrier or vendor sends you, decide whether it is right, approve it, pay it, and keep the paper trail — so the money going *out* of the company is as controlled as the money coming *in*. 24 live Payroll & Settlements Payroll is where a freight company works out exactly what each driver has earned for a pay period — miles run, waiting time, fuel charged back, advances and loans — puts the numbers in front of a second person to sign off, and then records that the driver was actually paid. 47 live Ledger The Ledger is the company's own set of books — every invoice, customer payment, carrier bill, bill payment, driver settlement and fuel receipt writes itself into a double-entry ledger automatically, and this screen lets you read those books, prove they balance, see where cash is heading, and click any number straight back to the paperwork it came from. 18 live ## Command & Insight Knowing what is going on, and being able to prove what went on. Analytics is for exploring when you do not know what you are looking for; Reports is a catalogue for when you know exactly what you need and want it as a file. Dashboard The Dashboard is the screen a freight company opens first every morning — it pulls together, on one page, how many trucks are rolling, how much money has come in and how much is still owed, which drivers are close to running out of legal driving hours, which licences and insurance policies are about to expire, and which delivered jobs have never been billed or are missing the paperwork that gets them paid. 22 live Unified Communications Messages is the one place where every text, WhatsApp and email between your office and a driver, customer or broker lives as a running conversation — so nobody has to ask "did anyone reply to him?" ever again. 36 live Analytics Analytics turns the freight you already booked, billed, paid for and fuelled into seven boards of business numbers — what you earned, what you kept, whether you delivered on time, who owes you money, and where your fuel tax is heading — and every number on those boards states out loud how much of your business it was actually able to measure. 25 live Reports Reports is where you pull the paperwork and the numbers out of the business — twenty-one ready-made registers you can run and download, four "everything about one truck / driver / trailer / customer" pages, and a build-your-own report tool that answers a plain-English question without ever inventing a number. 29 live Activity & Audit Log Activity is the tamper-evident diary of the whole company — one scrolling, filterable, exportable list of every record anyone created, changed, deleted or was refused permission to touch, written automatically by the database itself so nobody has to remember to log anything and nobody can quietly erase it afterwards. 32 live ## Platform & Control The configuration layer. Settings has the widest reach of any module — it writes the rules the other twenty-one obey — which makes it the highest-privilege surface in the product and the one most worth guarding. Settings Settings is the back office where the owner sets up the trucking company once — its legal name and safety numbers, its logo and invoice wording, its tax rates and pay formulas, its customs brokers and rate agreements, who on staff can touch what, and which outside services (QuickBooks, email, PC*Miler, BorderConnect) the business is plugged into — so every other screen in the system stops asking and just knows. 37 live Multi-Company When one owner runs several trucking companies side by side, this single screen adds them up — loads, revenue, trucks, trailers and drivers, each company in its own colour — so the owner can see the whole family of businesses at a glance without ever mixing their separate sets of books. 12 live --- ## Border & Compliance — Lanexa TMS URL: https://lanexa.io/platform/border-and-compliance Summary: Border & Compliance: eManifest, Documents, Compliance, IFTA & Safety. 99 capabilities live in Lanexa, the TMS built for Canadian carriers. Platform / Border & Compliance # Are we legal? Most transportation software treats the border as somebody else's problem and fuel tax as a spreadsheet exercise. Here both are first-class parts of the load lifecycle — which, for a carrier running into the United States, is the difference between one system and three. 3 Modules in this pillar 99 Capabilities, all live 99 Live in production Dispatchers and safety officers Who lives here ## The modules. 01 eManifest The eManifest module — called the Border Desk inside the product — is where a dispatcher gets a truck legally across the Canada/US border: it assembles every fact customs demands for a crossing, scores how ready that crossing is, prints the barcoded paper the driver carries, emails the customs broker their package, and runs a countdown clock so nobody arrives at the booth without an accepted filing. 29 capabilities, all live 02 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. 30 capabilities, all live 03 Compliance, IFTA & Safety This is where a carrier proves it is legal to be on the road — how many hours each driver has left, which licences and medicals are about to expire, what happened in every crash, and the quarterly fuel-tax return that has to be filed with the province or state that issued the plates. 40 capabilities, all live ## The other pillars. Revenue & Movement What are we moving, and how? ↗ Resources Can we take this job? ↗ Money Did we get paid, and did we pay? ↗ Command & Insight What is happening, and what happened? ↗ Platform & Control How is this set up? ↗ --- ## The Capability Ledger — 716 Live Capabilities | Lanexa URL: https://lanexa.io/platform/capabilities Summary: Every capability Lanexa ships today: 716 live in production across 22 modules, each with the module that owns it — and, on its own tab, what we have chosen not to build. Platform / Capability ledger # 716 capabilities. All live. Most software companies show you a feature grid. This is the ledger: every capability in production today, and which module owns it. On its own tab, what we have chosen not to build — because a list that is all yes is a list nobody should trust. You can read all of it before you talk to us. From the Lanexa 2.0 capability register · version 2.0.37 · reviewed 2026-08-24 · 2 rows are counted but not listed here, because they describe something we have chosen not to discuss publicly yet 716 Capabilities, all live 22 Modules 100% Of what we list is in production v2.0.37 Register reviewed 2026-08-24 Live · 716 Not built — by design · 108 ## Dashboard 22 live · Command & Insight | Capability | Who can do it | Status | | See how many jobs are moving right now | All roles | Live | | See money actually collected | All roles | Live | | See money still owed, and how much is late | All roles | Live | | Catch delivered loads that were never billed | All roles can see it | Live | | Jump into the billing work queue from that tile | Administrators and Accountants only — Billing is one of the money screens the app locks, and everyone else who clicks is bounced straight back to the Dashboard (, ) | In progress | | See driver availability at a glance | All roles | Live | | Be warned before a driver runs out of legal hours | All roles | Live | | See the fleet's working state | All roles | Live | | Read revenue as a trend, not a number | All roles | Live | | See what just happened in the company | All roles | Live | | Scan the five newest loads | All roles | Live | | Open the full load ledger | All roles — is not a gated route | Live | | Be warned before a licence, medical, insurance or safety certificate expires | All roles | Live | | Be warned before the company's own credentials lapse | All roles | Live | | Catch loads whose paperwork is missing | All roles | Live | | Be told, in words, that the paperwork is complete | All roles | Live | | Tell an empty company apart from a broken one | All roles | Live | | See that nothing has happened yet | All roles | Live | | Open the full missing-document worklist | All roles — is not a gated route | Live | | Open the specific load with the paperwork gap | All roles | Live | | Know the exact local time and today's exchange rate | All roles | Live | | See active storm warnings for where they are | All roles, if they allow browser location | Live | | See current weather where they are | All roles, if they allow browser location | Live | | See this week's diesel index | All roles | In progress | | Change anything | Nobody | Not built | | Filter by date range | — | Not built | | Manually refresh the page | — | Not built | ## Loads 44 live · Revenue & Movement | Capability | Who can do it | Status | | Book a load in seconds | Administrators, Dispatchers and Sales | Live | | Get a client-facing probill number | Anyone who can create | Live | | Read a rate confirmation PDF with AI | Administrators and Dispatchers | Live | | Be warned about a re-sent tender | Everyone creating | Live | | Apply contract pricing | Everyone creating | Live | | Be stopped from booking an over-extended customer | Everyone can be stopped; only the billing roles — Administrators, Controllers, Accounting and Billing Clerks — can override | Live | | Record freight line by line | Everyone editing | Live | | Handle temperature-controlled freight | Everyone editing | Live | | Handle dangerous goods | Everyone editing | Live | | Fill cross-border paperwork | Everyone editing | Live | | Auto-derive the border control number | Everyone editing | Live | | Inherit a customer's usual broker | Everyone editing | Live | | Book several similar loads back to back | Everyone creating | Live | | Get distance and a route without typing it | Everyone editing | Live | | Assign a driver | Administrators and Dispatchers | Live | | Assign a truck | Administrators and Dispatchers | Live | | Add a team (second) driver | Everyone editing | Live | | Move the load forward one stage | Administrators and Dispatchers | Live | | Change status directly | Administrators and Dispatchers for the write; the dropdown itself renders for everyone | In progress | | Mark a truck-ordered-not-used | Administrators and Dispatchers | Live | | Record a custody event | Everyone with the dialog open | Live | | Turn a delivered load into an invoice | Administrators and Dispatchers | Live | | Split a load at a cross-dock | Administrators and Dispatchers | Live | | Copy a load | Administrators and Dispatchers | Live | | Reuse a lane | Administrators and Dispatchers | In progress | | Farm the load out to a partner carrier | Administrators and Dispatchers | Live | | Produce paperwork | All roles — these entries sit above the mutating block | Live | | Produce a Proof of Delivery | All roles, gated by status | Live | | Send the driver their paperwork | Administrators and Dispatchers from the row menu; from the record, whenever a driver is assigned | Live | | Message the driver about this load | Administrators and Dispatchers from the row; sending from inside the thread needs message-sending permission, which Drivers, Safety and Sales also carry | Live | | Give the customer a tracking link | Anyone with the record open | Live | | See the whole story of one load | Everyone | Live | | Open the journey on its own page | Everyone | Live | | See the movement grid | Everyone | Live | | See the money on one load | Everyone with the record open | In progress | | See a predicted arrival time | Everyone | Live | | Track document completeness | Attach or generate: any role covering documents, loads or customs filing — in practice every shipped role except Driver and Viewer. Permanently delete: document roles only — Administrators, Controllers, Accounting, Billing Clerks, A/P Clerks, Safety and Sales, but not Dispatchers , | Live | | Find a load fast | Everyone | Live | | Slice the ledger | Everyone | Live | | Switch how the list looks | Everyone | Live | | See totals | Everyone sees the count; the amounts need a money-visible role — Administrators, Controllers, Accounting, Billing Clerks, A/P Clerks and Sales, but not Dispatchers | Live | | Export the ledger | Everyone | Live | | Act on many loads at once | Administrators and Dispatchers in practice — the database refuses everyone else | In progress | | Delete a load | Administrators and Dispatchers | In progress | | Jump straight to one load from anywhere | Everyone | Live | | Fill in the company's own extra fields | Everyone editing | Live | | See the lane on a map before saving | Everyone editing | Live | | Leave a note, and decide whether the driver sees it | Everyone editing | Live | | Read the freight lines back off the record | Everyone with the record open | Live | ## Trip Board 40 live · Revenue & Movement | Capability | Who can do it | Status | | See every working trip at a glance | Everyone | Live | | Spot trouble without looking for it | Everyone | Live | | Read the day's counters | Everyone | Live | | Jump to a trip or a driver | Everyone | Live | | Search the board | Everyone | Live | | Filter by what's in a cell | Everyone | Live | | Copy a cell | Everyone | Live | | Sort, hide and re-arrange columns | Everyone | Live | | Save a named layout | Everyone (stored in that browser) | Live | | Resize the split, go full screen | Everyone | Live | | Put the Load Pool on a second monitor | Everyone | Live | | See the fleet on a map | Everyone | Live | | Build a new trip | Dispatcher, Admin (button ungated on , gated on — see §12) | Live | | Edit a trip | Dispatcher, Admin | Live | | Assign a driver or a team driver | Dispatcher, Admin | Live | | Assign a truck or a trailer | Dispatcher, Admin | Live | | Work a trip's run sheet | Administrators and Dispatchers only — for anyone else the Arrive and Complete buttons are not drawn at all (, ) | Live | | Send the driver their run sheet | Anyone whose role may send messages — Administrators, Dispatchers, Safety, Sales and Drivers. For anyone else the menu entry is greyed out () | Live | | Open a trip's full record | Everyone (action buttons stay gated) | Live | | Advance the trip's own status | Dispatcher, Admin | Live | | Work the Load Pool | Everyone | Live | | Query the pool | Everyone | Live | | Pivot the pool to people and equipment | Everyone | Live | | Flag a load for attention | Anyone with edit rights over freight — Administrators and Dispatchers. Everyone else can click, and the database refuses the change | Live | | Record one of the six custody events | Administrators and Dispatchers. Recording an event touches the trip, its stops and the permanent ledger, and the database refuses all three from anyone without trip-edit rights — so a Viewer or an Accountant can open the menu but the save is refused ( · · ) | Live | | Link a pool load onto the selected trip | Dispatcher, Admin | Live | | Change a pool load's status | Administrators and Dispatchers; everyone else meets a refusal from the database | Live | | Open a load's full record | Everyone (the window's own action buttons stay gated) | Live | | See a load's full history | Everyone | Live | | Switch to the spreadsheet lens | Everyone | Live | | Edit cells inline on the Load Grid | Administrators and Dispatchers; everyone else meets a refusal from the database | Live | | Reshape the Load Grid | Everyone | Live | | Read a load's trip context without leaving the grid | Everyone | Live | | Look up any trip in the company | Everyone | Live | | Filter loads by workflow stage | Everyone | Live | | Check border readiness | Everyone | Live | | See where every asset is parked | Everyone | Live | | Preview the trip-shaped grid | Everyone | In progress | | Pop the Load Grid onto a second monitor | Everyone | Live | | Use keyboard shortcuts | Everyone | Live | | Land on a trip from a link | Everyone | In progress | | Refresh, and know how stale you are | Everyone | Live | ## Load Status 36 live · Revenue & Movement | Capability | Who can do it | Status | | See every load as a card in a status lane | Every signed-in member | Live | | Read the badges on a card at a glance | Every signed-in member | Live | | Drag a load to a new status | Administrators and Dispatchers — anyone else is refused by the database | Live | | One-click status advance | Administrators and Dispatchers | Live | | Be stopped from an impossible status move | Everyone | Live | | Be warned before a risky status move | Everyone | Live | | Search the whole board | Every signed-in member | Live | | Filter by pickup window | Every signed-in member | Live | | Filter by equipment type | Every signed-in member | Live | | Filter by customer | Every signed-in member | Live | | Reset all filters | Every signed-in member | Live | | See the filtered count | Every signed-in member | Live | | Hide old delivered loads | Every signed-in member | Live | | Focus one lane | Every signed-in member | Live | | See where every load is on a map | Every signed-in member | Live | | Tell a tracked load from a guessed one | Every signed-in member | Live | | See which loads need action now | Every signed-in member | Live | | Show only flagged loads on the map | Every signed-in member | Live | | See the planned lane for one load | Every signed-in member | Live | | Know how many loads cannot be mapped | Every signed-in member | Live | | See the work laid out as a driver calendar | Every signed-in member | Live | | See team-driver loads on both drivers' rows | Every signed-in member | Live | | Spot unassigned work | Every signed-in member | Live | | Open a load's full detail | Every signed-in member | Live | | Advance the status from inside the detail panel | Administrators and Dispatchers | Live | | Assign or change the driver / truck | Administrators and Dispatchers | Live | | Hand a moving load to a partner carrier | Administrators and Dispatchers; the partner-carrier desk has its own permissions downstream | Live | | Record a custody event | Any signed-in member of the company. The routine behind the button checks company membership and nothing else (). Editing rights only come into it when the event *also* moves the load's status, because that part is an ordinary load edit () | Live | | Read the load's whole story in plain English | Every signed-in member | Live | | Open the full-page Journey view | Every signed-in member | Live | | Copy a public tracking link for the customer | Every signed-in member | Live | | Create a new load without leaving the board | Administrators and Dispatchers directly; Salespeople only by converting a quote | Live | | Go fullscreen | Every signed-in member | Live | | Pop the board into its own window | Every signed-in member | Live | | Jump to the Trip Board | Every signed-in member | Live | | Compose an incumbent-style Run Sheet message | Dispatcher | Live | ## eManifest 29 live · Border & Compliance | Capability | Who can do it | Status | | Border Desk list | Everyone signed in | Live | | Four-number status board | Everyone signed in | Live | | Filter by direction and status | Everyone signed in | Live | | Search across the desk | Everyone signed in | Live | | Live border wait times | Everyone signed in | Live | | Filing countdown clock | Everyone signed in | Live | | Missing-broker radar | Everyone signed in (needs a single company pinned) | Live | | Create a crossing from a trip | Administrators, Dispatchers, Safety | Live | | Inherit the broker and entry type from the load | Automatic at creation | Live | | Round-trip: two crossings on one trip | Administrators, Dispatchers, Safety | Live | | Border readiness score + checklist | Everyone signed in (score); clicking navigates | Live | | Assign the conveyance reference | Administrators, Dispatchers, Safety | Live | | Derive missing shipment numbers | Administrators, Dispatchers, Safety | Live | | Print the lead sheet | Administrators, Dispatchers, Safety | Live | | Print PARS/PAPS label sheets | Administrators, Dispatchers, Safety | Live | | Print the driver crossing packet | Administrators, Dispatchers, Safety | Live | | Share the packet to the driver's phone | Administrators, Dispatchers, Safety | Live | | Portal Filing Assistant | Administrators, Dispatchers, Safety — the whole Assistant, not just "Mark Filed", sits inside the filing-rights toolbar | Live | | Email the broker packet | Administrators, Dispatchers, Safety | Live | | Track the broker loop | Administrators, Dispatchers, Safety | Live | | Open the broker's public tracker | Administrators, Dispatchers, Safety | Live | | File the acceptance evidence | Administrators, Dispatchers, Safety | Live | | Advance the filing status | Administrators, Dispatchers, Safety | Live | | Record a rejection with its reason | Administrators, Dispatchers, Safety | Live | | Filing history | Everyone signed in | Live | | Edit port and arrival time | Administrators, Dispatchers, Safety | Live | | Remove a load from a crossing | Administrators, Dispatchers, Safety | Live | | Remove the crossing | Administrators, Dispatchers, Safety | Live | | CBSA outage paper fallback | Everyone signed in (ACI crossings only) | Live | | Deep link into a crossing | Everyone signed in | In progress | | Add a load to an existing crossing | — | Not built | | Transmit the filing electronically | — | Not built | ## Interline Desk 28 live · Revenue & Movement | Capability | Who can do it | Status | | See the whole farm-out picture on one desk | Any signed-in member | Live | | Read the four headline numbers | Any signed-in member | Live | | Search everything at once | Any signed-in member | Live | | Onboard an interline partner | Administrators and Dispatchers | Live | | Onboard a partner without leaving the tender form | Administrators and Dispatchers | Live | | Edit an existing partner | Administrators and Dispatchers | Live | | Be nagged about partner compliance | Any signed-in member | Live | | Tender a load to a partner | Administrators and Dispatchers | Live | | See the margin before committing | Administrators and Dispatchers | Live | | Set an offer clock | Administrators and Dispatchers | Live | | Record a deal already agreed on the phone | Administrators and Dispatchers | Live | | Be warned about border identity before the tender goes out | Administrators and Dispatchers | Live | | Mark the partner's answer | Administrators and Dispatchers | Live | | Close out a covered load | Administrators and Dispatchers | Live | | Produce the rate confirmation | Administrators and Dispatchers | Live | | Download that PDF | Administrators and Dispatchers | Live | | Email it to the partner with the PDF attached | Administrators and Dispatchers | Live | | Edit tender details without touching status | Administrators and Dispatchers | Live | | Record that the partner files the border crossing | Administrators and Dispatchers | Live | | Stamp that the partner actually crossed | Administrators and Dispatchers | Live | | Hand a moving load to a partner mid-journey (interchange) | Administrators and Dispatchers | Live | | Re-tender a load the first partner turned down | Administrators and Dispatchers | Live | | Jump to the partner's payable | Any signed-in member | Live | | Open the load's interline paperwork | Any signed-in member (the menu item appears whenever the load is visible) | Live | | Read the load's full event history | Any signed-in member | Live | | Open the whole load from a desk row | Any signed-in member | Live | | Reach the desk from the main menu | Any signed-in member | Live | | Reach the desk from the old bookmark | Anyone | Live | | Tender straight from a partner row | Administrators and Dispatchers | In progress | ## Quotes 35 live · Revenue & Movement | Capability | Who can do it | Status | | See the quote list | Every signed-in member | Live | | Filter by status | Every signed-in member | Live | | Read the four headline counters | Every signed-in member | Live | | Read the sales funnel strip | Every signed-in member, when one company is selected | Live | | Create a quote | Admin, Dispatcher, Sales | Live | | Be forced to start as a Draft | Same | Live | | Apply a rate card | Same | Live | | See your own lane history | Same | Live | | Be warned about an off-market price | Same | Live | | Be warned about a below-cost price | Same | Live | | Set the company's cost floor | Same | Live | | Add freight items | Same | Live | | Add charge lines | Same | Live | | See the destination tax preview | Same | Live | | Get a cross-border nudge | Same | Live | | Edit a quote | Same | Live | | Email the quote to the customer | Same | Live | | Preview the attached PDF before sending | Same | Live | | Copy the public link | Same | Live | | Download the quote as a PDF | Every signed-in member | Live | | Decline a quote | Same | Live | | Convert a quote to a load | Same | Live | | Delete a quote | Same | Live | | Export the quote list | Every signed-in member | Live | | Open a quote from a link or search | Every signed-in member | Live | | Jump from a quote to its load | Every signed-in member | Live | | See the quote as a card | Every signed-in member | Live | | See the acceptance evidence | Every signed-in member | Live | | (Customer) open the quote with no account | Anyone holding the link | Live | | (Customer) choose optional charges | Anyone holding the link | Live | | (Customer) accept the quote | Anyone holding the link | Live | | Automatic expiry | System | Live | | Expiring-soon warning | System | Live | | Instant acceptance alert | System | Live | | Parked-acceptance chase | System | Live | | Revoke a public quote link | Nobody | Not built | | Convert a parked acceptance | Nobody | Not built | | See how many times a quote was viewed | Nobody | In progress | | Put a discount on a quote | Nobody | Not built | | Revise a quote into a new version | Nobody | Not built | | Read a quote's status history | Nobody | In progress | ## Unified Communications 36 live · Command & Insight | Capability | Who can do it | Status | | Triage by what needs you | Anyone who can open the page | Live | | See how long someone has waited | Anyone | Live | | Search conversations | Anyone | Live | | Narrow the list | Anyone | Live | | Group by age | Anyone | Live | | See at a glance what is yours | Anyone | Live | | Be told what an empty list means | Anyone | Live | | Remember your chosen view | Anyone | Live | | Read a thread | Anyone | Live | | Reply quickly | Admin, Dispatcher, Driver, Safety and Sales — the five roles that may send | Live | | Write an internal note | The same five roles that may send | Live | | Send a templated message with an attachment | The same five roles that may send | Live | | Change a thread's status | Any company member — this control carries no permission check at all | Live | | Assign a thread | Admin, Dispatcher and Driver for the buttons; naming a specific colleague also requires the right to manage users, which in practice means an Admin | Live | | Tag a thread | Any company member | Live | | Mark a thread personal | Any company member | Live | | Attach a conversation to a load | Any company member | Live | | Jump to the load or driver | Anyone | Live | | Log a driver's message as an exception on the load | Any company member of that load's company | Live | | Clear the Unmatched queue | Admins, anyone who can manage users, and Dispatchers — enforced both on screen and independently inside all three of the database routines behind it, so it is never a button that fails. · | Live | | See this month's message spend | Anyone | Live | | WhatsApp 24-hour window warning | Anyone | Live | | Quiet-hours courtesy hint | Anyone | Live | | Open a driver's photo or PDF | Anyone | Live | | Work on a phone | Anyone | Live | | Unread badge in the top bar | Anyone | Live | | Edit the saved reply templates | The same five roles that may send | Live | | Alerts bell | Anyone | Live | | Work an alert like a ticket | Any company member | Live | | Choose how you are told | Any company member, for themselves | Live | | Write an alert rule | Any company member can open it; the underlying recipient table is Admin-only at the database. | Live | | Set an on-call rota | Any company member | Live | | Set what inaction costs | Any company member | Live | | Allow customer-facing email | Any company member | Live | | Receive a 3am phone call for a panic alert | Whoever a rule targets | Live | | AI morning brief | Any company member, per their own settings | Live | | Resend a failed message | — | Not built | | Trip / Manifest context card | — | Not built | | Bulk actions on threads | — | Not built | ## Fleet 41 live · Resources | Capability | Who can do it | Status | | See the whole fleet at a glance | Everyone signed in | Live | | Switch between the five views | Everyone signed in | Live | | Count strip with one-click filtering | Everyone signed in | Live | | Filter by status | Everyone signed in | Live | | Switch between a dense table and cards | Everyone signed in | Live | | Add a truck | Admin, Dispatcher | Live | | Record regulatory identifiers on a truck | Admin, Dispatcher | Live | | Record engine, fuel and axle detail | Admin, Dispatcher | Live | | Record the federal annual inspection | Admin, Dispatcher | Live | | Add company-specific fields to a truck | Admin, Dispatcher | Live | | Open a truck's full record | Everyone signed in | Live | | See a truck's paperwork | Everyone signed in | Live | | See a truck's lifetime history | Everyone signed in | Live | | Edit a truck | Admin, Dispatcher | Live | | Retire a truck | Admin, Dispatcher | Live | | Add a trailer | Admin, Dispatcher | Live | | Record trailer dimensions and weights | Admin, Dispatcher | Live | | Record how a trailer is owned | Admin, Dispatcher | Live | | Record reefer detail | Admin, Dispatcher | Live | | Record trailer inspection, plate and insurance dates | Admin, Dispatcher | Live | | See a trailer's lifetime history | Everyone signed in | Live | | Delete a trailer | Admin, Dispatcher | Live | | Add a yard, dock, terminal or zone | Everyone signed in — no permission trigger on this table | Live | | Give a yard a location and a geofence radius | Everyone signed in | Live | | Record yard capacity, dock doors and hours | Everyone signed in | Live | | Mark a yard inactive | Everyone signed in | Live | | Remove a yard | Everyone signed in | Live | | Correct or move an asset's position | Admin and Dispatcher only. The ledger accepts a movement from whoever is trusted with trips or with the fleet, which in the shipped roles means those two and nobody else — a Safety user is refused () | Live | | See where each unit was last seen, with a confidence cue | Everyone signed in | Live | | See the fleet on a map | Everyone signed in | Live | | See live telematics positions | Everyone signed in | Live | | Check whether the GPS feed is healthy | Everyone signed in | Live | | Refresh live positions on demand | Everyone signed in | Live | | Rank trucks by revenue | Everyone signed in | Live | | See which trucks ran the most this month | Everyone signed in | Live | | See fleet utilisation | Everyone signed in | Live | | See which trailers are sitting | Everyone signed in | Live | | Run the full trailer idling report | Everyone signed in | Live | | Jump straight to a unit from global search | Everyone signed in | Live | | See which company owns a unit | Everyone signed in | Live | | Delete a truck outright | Nobody | Not built | | Start from an empty fleet | Everyone signed in | Live | | Filter or count on the Yards tab | — | Not built | | Un-retire a truck, or restore a deleted trailer or yard | Nobody | Not built | | Set a truck's odometer from telematics | — | Not built | | Get warned before a plate, insurance or safety date expires | Admins receive it | In progress | ## Drivers 20 live · Resources | Capability | Who can do it | Status | | Add a driver | Anyone can press the button; only Admin and Safety complete the save, because the database refuses everyone else (seg292 ) | Live | | Edit a driver | Admin and Safety only — the menu item is shown only to roles allowed to change a driver, and the panel's Edit button is withheld the same way (, ) | Live | | Change a driver's duty status | Admin and Safety | Live | | Record a communications consent | Admin and Safety | In progress | | Record border and immigration details | Admin and Safety | Live | | Mark a driver active or inactive | Admin and Safety | Live | | Fill company-defined custom fields | Admin and Safety | In progress | | Filter the list by status | Everyone | In progress | | Switch between table and card view | Everyone | Live | | Read the fleet counts strip | Everyone | In progress | | See expiry traffic lights | Everyone | Live | | See hours-of-service headroom | Everyone | In progress | | See this month's miles and revenue per driver | Everyone — money is not hidden from any role on this screen | Live | | Open a driver's full record | Everyone | Live | | Assign or change a driver's default truck | Admin, Safety or Dispatch — the truck-assignment procedure accepts either the driver permission or the fleet permission (seg292 ) | Live | | Upload a credential scan | Any signed-in member — this record type carries no permission rule at all (see section 12) | Live | | Open a stored credential file | Any signed-in member of the owning company | Live | | Delete a credential | Any signed-in member — no confirmation dialog, no permission check | Live | | Attach other documents to a driver | Uploading needs one of the document, load or customs-filing permissions (seg292 ) — between them, Admin, Safety, Dispatch, Controller, Accounting, Billing Clerk, A/P Clerk and Sales. The panel deliberately offers no delete () | Live | | Book time off | Any signed-in member — no permission rule on this record type either | Live | | Remove a booked leave period | Any signed-in member of a company the row belongs to | Live | | See who is on leave today | Everyone | Live | | Read the movement history | Everyone | Live | | Read the driver's recent loads | Everyone | In progress | | Read and reply to the driver's message thread | Reading: everyone. Sending a reply, and handing the thread to a colleague, need the messaging permissions that Admin, Safety, Dispatch, Sales and the Driver role hold () | In progress | | Jump straight to a driver from search | Everyone | Live | | Retry a failed load of the list | Everyone | Live | | Delete a driver | — | Not built | | Set a fuel card number | — | Not built | | Search or sort the driver list | — | Not built | ## Customers 45 live · Resources | Capability | Who can do it | Status | | Browse the customer book | Everyone signed in | Live | | Search | Everyone | Live | | Filter Active / Inactive / All | Everyone | Live | | Filter All / Customers / Brokers | Everyone | Live | | Sort the list | Everyone | Live | | See what each customer owes | Everyone | Live | | Add a customer or broker | Anyone can open the form; the save succeeds only for the customer-editing roles, or a dispatcher | Live | | Edit a customer | The customer-editing roles | Live | | Delete a customer | The customer-editing roles | Live | | Mark a customer inactive | The customer-editing roles | Live | | Type a record as a Broker | The customer-editing roles | Live | | Import brokers from a spreadsheet | The customer-editing roles | Live | | Set a credit limit and currency | The customer-editing roles | Live | | Set credit terms | The customer-editing roles | Live | | Require a signed delivery proof before invoicing | The customer-editing roles | Live | | Require a named document packet before invoicing | The customer-editing roles | Live | | Flag a factor's notice of assignment | The customer-editing roles | Live | | Set an index-linked fuel surcharge | The customer-editing roles, plus anyone who may change billing — which adds day-to-day accountants | Live | | Turn a fuel-surcharge schedule off | The customer-editing roles, plus anyone who may change billing | Live | | Tag a customer with a Trip Board colour | The customer-editing roles | Live | | Mark tax exempt | The customer-editing roles | Live | | Give a customer a billing address of its own | The customer-editing roles | Live | | Add tenant-specific fields | The customer-editing roles | Live | | Open a customer's 360 | Everyone | Live | | Read the header numbers | Everyone | Live | | Read the account's whole story | Everyone | Live | | Read a health score with its reasons | Everyone | Live | | Read the identity and broker details | Everyone | Live | | Add a contact person | The customer-editing roles | Live | | Say what each contact should receive | The customer-editing roles | Live | | Nominate the primary contact | The customer-editing roles | Live | | Edit or remove a contact | The customer-editing roles | Live | | Read the money picture | Everyone | Live | | See where a customer stands against its limit | Everyone | Live | | Jump from a recent load to the load itself | Everyone | Live | | Log a call or exception note | The customer-editing roles | Live | | Page through a customer's recorded events | Everyone | Live | | Review lane history and per-lane margin | Everyone | Live | | See documents filed against the customer | Everyone | Live | | Find duplicate customers | The customer-editing roles | Live | | Preview a merge (changes nothing) | The customer-editing roles | Live | | Commit a merge | The customer-editing roles — and the database checks the same thing again on its own | Live | | Open a customer straight from global search | Everyone | Live | | See which company a record belongs to | Everyone | Live | | See a saved row flash | Everyone | Live | | Set a customer-level payment-term override | — | Not built | | Set per-customer detention free hours and hourly rate | — | Not built | | Assign party roles (bill-to, customs broker, shipper, consignee…) | — | Not built | | Set a customer's default customs broker | — | Not built | ## Billing 46 live · Money | Capability | Who can do it | Status | | See the receivables book | Anyone who can reach the route | Live | | Read the four money tiles | Anyone who can reach the route | Live | | Filter by status | Anyone who can reach the route | Live | | Sort the book | Anyone who can reach the route | Live | | Spot un-billed delivered loads | Anyone who can reach the route | Live | | Invoice an un-billed load in one click | Accountants and admins | Live | | Open the load behind an un-billed row | Anyone who can reach the route | Live | | See which paperwork is missing before billing | Anyone who can reach the route | Live | | Create an invoice by hand | Accountants and admins | Live | | Add a charge line from the catalogue | Accountants and admins | Live | | Add a company accessorial at its configured rate | Accountants and admins | Live | | Price a fuel surcharge from the index | Accountants and admins | Live | | Mark a line non-taxable | Accountants and admins | Live | | Add a blank charge line | Accountants and admins | Live | | See the exchange rate before it is locked in | Accountants and admins | Live | | Add notes, override the remit-to address, fill custom fields | Accountants and admins | Live | | Edit an old invoice that has no charge lines | Accountants and admins | Live | | Edit an existing invoice | Accountants and admins | Live | | Open the full invoice | Anyone who can reach the route | Live | | Email the invoice with its document packet | Accountants and admins for the row-menu entry; the Send button inside the invoice's own detail view carries no permission check at all — see section 12 | Live | | Download the invoice as a PDF | Anyone who can open the detail | Live | | Record a payment | Accountants and admins | Live | | Flag a short payment | Accountants and admins | Live | | Void an unpaid invoice | Accountants and admins | Live | | Raise a credit memo (row menu) | Accountants and admins | Live | | Raise a credit memo (detail footer) | Anyone who can open the detail | Live | | Work the collections desk | Accountants and admins | Live | | Copy a dunning letter | Accountants and admins | Live | | Read AR aging by customer | Anyone who can reach the route | Live | | Download a customer statement | Anyone who can reach the route | Live | | Jump from aging straight to Send | Accountants and admins | Live | | Bill unbilled detention | Accountants and admins | Live | | Close and reopen accounting months | Soft close: accountants and admins. Hard close and reopen: admins only | Live | | Configure factoring | Accountants and admins | Live | | Submit a schedule of accounts to the factor | Accountants and admins | Live | | Mark a schedule funded | Accountants and admins | Live | | Charge back a funded invoice | Accountants and admins | Live | | Push one invoice to QuickBooks | Anyone who can open the detail, but only renders if that company is connected to QuickBooks | Live | | Open the QuickBooks Sync Center | Accountants and admins | Live | | Export the book | Anyone who can reach the route | Live | | Export with chosen columns | Anyone who can reach the route | Live | | Delete an invoice | Accountants and admins | Live | | Arrive from elsewhere by deep link | Anyone who can reach the route | Live | | Tell at a glance which rows are credit memos, and whose company they are | Anyone who can reach the route | Live | | Read the honest empty states | Anyone who can reach the route | Live | | Retry a book that failed to load | Anyone who can reach the route | Live | | Edit a frozen invoice with a reason | Accountants and admins | Not built | ## Accounts Payable 24 live · Money | Capability | Who can do it | Status | | Open the payables list | Administrator, Controller, Accounting, A/P Clerk | Live | | See what the company owes, at a glance | Same four roles | Live | | See trust-money separately | Same four roles | Live | | Filter by status | Same four roles | Live | | Sort the list | Same four roles | Live | | Enter a new bill | Same four roles | Live | | Attach the bill to a load | Same four roles | Live | | Compare against the rate confirmation | Same four roles | Live | | Build the bill line by line | Same four roles | Live | | Code each line to an expense account | Same four roles | Live | | Bill in another currency | Same four roles | Live | | Charge tax on the bill | Same four roles | In progress | | Edit an existing bill | Same four roles | Live | | Move a bill along its lifecycle | Same four roles | Live | | Approve a bill | Same four roles — the separate approval permission is not checked | In progress | | Record a payment | Same four roles | Live | | Pay in full in one click | Same four roles | Live | | Record a short pay with a reason | Same four roles | In progress | | Pay a bill in instalments | Same four roles | Live | | Open a bill's full detail | Same four roles | Live | | Keep the vendor's paperwork with the bill | Same four roles; uploads go through the shared document rails | In progress | | Push a bill to QuickBooks | Same four roles | Live | | Delete a bill | Same four roles | Live | | Export the payables list to Excel | Same four roles | Live | | Choose export columns / copy to clipboard | Same four roles | Live | | Jump straight to one bill from elsewhere | Same four roles | Live | | Spot an auto-created partner payable | Same four roles | Live | | Read the totals for the current view | Same four roles | Live | | See a friendly message when the list is empty | — | Not built | | Record a payment in the bill's own currency | — | Not built | | Undo a deleted bill | — | Not built | | Edit a bill's money fields after the 3-day lock | — | Not built | | See an aged payables report (30 / 60 / 90 days) | — | Not built | | Approve or pay several bills at once | — | Not built | | Email a remittance advice to the vendor | — | Not built | ## Payroll & Settlements 47 live · Money | Capability | Who can do it | Status | | Add a pay item by hand | Anyone who reaches Payroll — but the database itself will only accept the new row from someone whose role allows preparing pay | Live | | Edit a pay item | As above | Live | | Delete a pay item | As above | Live | | Filter pay items | Anyone who reaches the module | Live | | Filter pay stubs | Anyone who reaches the module | Live | | Filter fuel receipts | Anyone who reaches the module | Live | | See running pay totals | Anyone who reaches the module | Live | | Jump from a pay line to where it came from | Anyone who reaches the module | Live | | Create a pay stub by hand | Anyone who reaches Payroll. Unlike pay lines, the pay-stub records carry no extra permission check of their own inside the database, so reaching the screen is the only gate (see section 12) | Live | | Preview what a manual stub will pick up | As above | Live | | Finalize a pay stub | As above | Live | | Mark a pay stub paid | As above | Live | | Delete a pay stub | As above | Live | | Open a pay stub's detail | As above | Live | | Export pay stubs | Anyone who reaches the module — this button is not separately permission-gated | Live | | Enter a fuel receipt by hand | Anyone who reaches the module | Live | | Enter fuel in litres | Anyone who reaches the module | Live | | Charge fuel back to the driver automatically | Anyone who reaches the module; the deduction line it creates is accepted by the database only from someone whose role allows preparing pay | Live | | Approve a fuel receipt | Anyone who reaches the module | Live | | Edit / delete a fuel receipt | Anyone who reaches the module | Live | | Import a fuel-card statement (CSV) | Anyone who reaches the module | Live | | Check the file was read correctly before mapping anything | Anyone who reaches the module | Live | | Import a second statement without closing the wizard | Anyone who reaches the module | Live | | Have the importer guess the columns | As above | Live | | Save a vendor mapping for next time | Anyone who reaches the module and has an active company selected | Live | | Catch duplicate fuel rows | As above | Live | | Match imported rows to a truck and a driver | As above | Live | | Auto-deduct a whole imported batch | As above | Live | | Edit a driver's pay package | Anyone who reaches the module. The operator-chargeback block is hidden for employees and contractors, and the database refuses it for them as well. | Live | | Open an escrow, loan or recurring deduction for a driver | Needs the billing right — held by owners, controllers, accountants and billing clerks. It is checked inside the database, not on the screen, so an accountant without it sees the button and gets a refusal | Live | | Pause, resume or close a ledger account | Needs the same billing right as opening one | Live | | Set how team-driver pay splits | Anyone who reaches the module; saving the choice writes to the load itself, so it is checked the same way any other load edit is | Live | | See which team loads still block pay | Anyone who reaches the module | Live | | Create a settlement run | Anyone who reaches the module; the database accepts the new run only from someone whose role allows preparing pay | Live | | Calculate a settlement | As above | Live | | Preview a settlement's maths | Anyone who reaches the module | Live | | Review and approve a settlement | Anyone who reaches the module — but the database refuses approval by the person who created the run | Live | | Mark a settlement paid | As above | Live | | Cancel a settlement run | As above | Live | | Delete a draft settlement | As above | Live | | Download a settlement statement (PDF) | Anyone who reaches the module | Live | | File that statement automatically | Automatic — no user action | Live | | Correct a closed settlement | Anyone who reaches the module | Live | | Filter settlement runs | Anyone who reaches the module | Live | | Open a settlement from elsewhere | Anyone who reaches the module | Live | | Be told what to do when a list is empty | Anyone who reaches the module | Live | | Open Payroll on a specific tab | Anyone who reaches the module | Live | | Jump from a settlement to its pay stub | Anyone who reaches the module | In progress | | Pay by the hour | — | Not built | | Reimburse lumper fees | — | Not built | | Pay drop/hook, layover, tarp, hazmat premium, border crossing and an accessorial share | — | Not built | | Pay empty miles | — | Not built | | Approve settlements for the whole fleet at once | — | Not built | ## Ledger 18 live · Money | Capability | Who can do it | Status | | Read the company trial balance | Admin/Owner, Controller, Accountant, Billing Clerk, A/P Clerk | Live | | See balances the way an accountant reads them | Everyone who can open the page | Live | | Drill into one account | Everyone who can open the page | Live | | Jump from a posting to the paperwork behind it | Everyone who can open the page | Live | | See which postings are intercompany | Everyone who can open the page | Live | | Read the group-consolidated position | Everyone who can open the page | Live | | Switch the company lens | Everyone who can open the page | Live | | Export the trial balance to Excel or CSV | Everyone who can open the page (the button itself is not separately permission-gated — see section 12) | Live | | Run the eight tie-out checks | Everyone who can open the page | Live | | Drill a failed check to the exact offending rows | Everyone who can open the page | Live | | See problems in sibling companies | Everyone who can open the page | Live | | Read the weekly cash forecast | Everyone who can open the page | Live | | Read Days Sales Outstanding (DSO) | Everyone who can open the page | Live | | Read the anomaly flags | Everyone who can open the page | Live | | Export the health workbook | Everyone who can open the page | Live | | Watch the page load, and see honest empty states | Everyone who can open the page | Live | | Edit the ledger by hand | Nobody | Not built | | Post a manual adjusting journal entry | Nobody | Not built | | Close or reopen an accounting month | Controller / Admin, on the Billing screen | Live | | Add, archive or reactivate an account in the Chart of Accounts | Roles that can reach the Settings tab | Live | | Read a monthly Profit & Loss statement | — | Not built | | Push the postings to QuickBooks | — | Not built | ## Documents 30 live · Border & Compliance | Capability | Who can do it | Status | | Browse documents grouped by load | Everyone signed in | Live | | Switch to a flat list | Everyone signed in | Live | | Switch between table and card layouts | Everyone signed in | Live | | Search | Everyone signed in | Live | | Filter on six axes | Everyone signed in | Live | | Live counts on the tabs | Everyone signed in | Live | | Honest empty states on all four tabs | Everyone signed in | Live | | Upload documents (wizard) | Anyone whose role allows changes to documents, to loads, or to customs filings — enforced by the database, not by the browser (). The button itself is drawn for everyone — see section 12 | Live | | Automatic photo compression | Anyone who can upload | Live | | Keep original quality | Anyone who can upload | Live | | Duplicate detection | Automatic | Live | | Preview a document inline | Everyone signed in | Live | | Download a document | Everyone signed in | Live | | Row thumbnails | Everyone signed in | Live | | Mark a document verified / remove verification | Only a role allowed to change documents — for anyone else the button is not drawn at all | Live | | Edit which records a document is linked to | Everyone signed in on the screen; the database still requires a role allowed to change documents, loads or customs filings | Live | | Create a secure external share link | Everyone signed in on the screen; the row write is tenant-scoped | Live | | Revoke a share link | Everyone signed in on the screen | Live | | Request a missing document by no-login link | Everyone signed in on the screen; requires a specific company, not "All Companies" | Live | | Delete a document (soft) | Anyone allowed to change documents, or the uploader inside 24 hours | Live | | Restore a deleted document | Only a role allowed to change documents | Live | | Doc radar — the missing-paperwork worklist | Everyone signed in | Live | | Review queue — classify inbound driver photos | Everyone signed in on the screen; the database still requires a role allowed to make the change | Live | | AI classification of inbound documents | Company members only — the server re-checks membership before it will touch the file () | Not built | | Per-load required-document checklist | Automatic, shown to everyone | Live | | Deep link to one document | Everyone signed in | Live | | Deep link to the radar | Everyone signed in | Live | | Bilingual document type labels | Automatic, per company setting | Live | | Documents panels on other records | Everyone signed in on those screens | Live | | Storage meter and photo-quality preset | Only a role allowed to change settings can move the quality preset; the meter renders for anyone who can open that tab | Live | | Two compliance reports | Exporting the CSV needs a role allowed to export compliance data — Admin, Dispatcher and Safety | Live | | Document version chains | Automatic on generated PDFs | In progress | | Retention and archiving | — | Not built | ## Compliance, IFTA & Safety 40 live · Border & Compliance | Capability | Who can do it | Status | | See every driver's hours at a glance | Anyone signed in | Live | | Be warned before a driver runs out of hours | Anyone signed in | Live | | Open one driver's hours breakdown | Anyone signed in | Live | | See which credentials are about to lapse | Anyone signed in | Live | | See at a glance that nothing is expiring | Anyone signed in | Live | | Look up the rules for a country | Anyone signed in | Live | | Report an incident | Any signed-in member — no permission check in the screen or in the database | Live | | Open the register straight from the incident list | Anyone signed in | Live | | See an honest empty incident list | Anyone signed in | Live | | See the federal testing clock on a crash | Anyone signed in | Live | | Tick the tests off | Any signed-in member | Live | | See when a crash has no insurance claim | Anyone signed in | Live | | Edit or delete an incident | Any signed-in member — no permission check | Live | | Lose the ability to edit once a case is closed | Any signed-in member | Live | | Attach evidence to a crash | Any signed-in member | Live | | Record witnesses | Any signed-in member | Live | | File a First Notice of Loss | Any signed-in member | Live | | Produce the DOT accident register | Anyone signed in | Live | | Export the register (CSV / PDF) | Anyone whose role allows downloading compliance evidence — Administrator, Dispatcher, Safety officer | Live | | Refresh the register from the server | Anyone signed in | Live | | Create an IFTA quarter | Button shown only to roles that may change compliance records | Live | | Choose where the miles come from | Any signed-in member in the screen; the database refuses the write unless the role may change compliance records | Live | | Compare the sources side by side | Anyone signed in | Live | | Type miles in by hand | Any signed-in member in the screen; the database requires the change-compliance right | Live | | See what is wrong with the data before filing | Anyone signed in | Live | | Verify fuel receipts | Roles that may change compliance records — and blocked entirely once the quarter is FILED | Live | | Preview the tax calculation without saving | Anyone signed in — deliberately open | Live | | Run and save the calculation | Roles that may change compliance records | Live | | Exclude unverified fuel from the numbers | Roles that may change compliance records | Live | | Pin the mileage source for one quarter | Roles that may change compliance records; anyone can read the strip | Live | | Lock the return | Roles that may change compliance records — checked in the screen and independently in the database | Live | | Amend a filed return | Roles that may change compliance records — in the screen and in the database | Live | | Export the quarterly return report | Roles that may download compliance evidence | Live | | Export the audit-armor report | Roles that may download compliance evidence | Live | | Export the per-account filing pack | Roles that may download compliance evidence | Live | | Be told why an export is unavailable | Anyone signed in | Live | | Manage IFTA accounts | Roles that may change compliance records | Live | | Browse and edit tax rates by period | Reading open to all; editing needs the change-compliance right | Live | | Import a quarter's rate matrix | Roles that may change compliance records — enforced in the screen and by the database | Live | | Fix missing map coordinates in bulk | Roles that may change compliance records | Live | | PSP reports, MVR checks, drug and alcohol programme tracking, DOT inspection history | — | Not built | | Electronic filing of the IFTA return | — | Not built | ## Analytics 25 live · Command & Insight | Capability | Who can do it | Status | | Pick a reporting window | Anyone who can open the page | Live | | Move between seven report boards | Anyone who can open the page (Fuel is money-gated) | Live | | Bookmark or share a specific view | Anyone who can open the page | Live | | Read the five headline numbers | Total Loads: anyone. Revenue, Revenue per mile and Gross margin: anyone allowed to see money analytics — Admin, Controller and Accounting. On-time delivery: anyone allowed to see either operational or money analytics. | Live | | See a locked tile instead of a blank one | Applies to everyone below Admin/Accounting | Live | | See today's trading | Anyone who can open the page (not money-gated) | Live | | Read the revenue trend | Anyone who can open the page (not money-gated) | Live | | Read the quote funnel | Anyone who can open the page | Live | | Read fleet and driver counts | Anyone who can open the page | Live | | Break revenue down three ways | Anyone who can open the page (not money-gated) | Live | | Rank your busiest lanes | Anyone who can open the page | Live | | Export the revenue dataset | Anyone whose role allows exporting financial data — Admin, Controller, Accounting and Billing Clerk | Live | | See operations at a glance | Anyone who can open the page | Live | | Read the vehicle summary | Anyone who can open the page | Live | | Rank drivers | Anyone who can open the page | In progress | | Read gross margin honestly | Anyone allowed to see money analytics — Admin, Controller, Accounting — for the three money tiles; the Cost on file count is open to all | In progress | | Track margin over time | Anyone who can open the page (not money-gated) | Live | | See which lanes actually make money | Anyone who can open the page (not money-gated) | In progress | | See per-load profit | Anyone who can open the page (not money-gated) | Live | | Export the profitability dataset | Anyone whose role allows exporting financial data — Admin, Controller, Accounting and Billing Clerk | Live | | Separate what you booked from what you billed | Anyone who can open the page (not money-gated) | In progress | | See customer counts and terms | Anyone who can open the page | In progress | | Track customer volume and retention | Anyone who can open the page | Live | | Rank customers by revenue | Anyone who can open the page (not money-gated) | In progress | | See who owes you money | Anyone who can open the page (not money-gated) | In progress | | Export outstanding invoices | Anyone whose role allows exporting financial data — Admin, Controller, Accounting and Billing Clerk | In progress | | Read fuel economics | Anyone allowed to see money analytics — Admin, Controller, Accounting — enforced in the browser and again inside the database | Live | | Compare cost per truck | Anyone allowed to see money analytics — Admin, Controller, Accounting | Live | | Spot overpriced fills | Anyone allowed to see money analytics — Admin, Controller, Accounting | Live | | Read the IFTA tax position | Anyone allowed to see money analytics — Admin, Controller, Accounting | Live | | See the tax ladder on your own lanes | Anyone allowed to see money analytics — Admin, Controller, Accounting | Live | | Change how a chart is drawn | Anyone who can open the page | Live | | Be told when a number cannot be produced | Anyone who can open the page | Live | | Schedule this report by email | — | Not built | | Click a chart to filter the loads behind it | — | Not built | | Set your own margin thresholds | — | Not built | | Print or produce a PDF of a board | — | Not built | ## Reports 29 live · Command & Insight | Capability | Who can do it | Status | | Browse the report library | Anyone who can reach | Live | | Expand a report card | Anyone | Live | | Set a date range | Anyone | Live | | Narrow to one customer | Anyone | Live | | Narrow to one driver | Anyone | Live | | Pick an IFTA quarter | Anyone | Live | | Run a report | Anyone | Live | | Download a report as CSV | Ungated on 5 reports; needs financial export on 8; needs compliance export on 8 (, ) | Live | | Download a report as PDF | Same gate as the CSV for that report | Live | | See why a report is refused | Anyone | Live | | Truck 360 | Anyone can open it; the eight money figures appear only for a role allowed to see rates and margin | Live | | Enter a truck's fixed costs | Only a role allowed to see money — for anyone else the card is not on the page at all | Live | | Driver 360 | Anyone can open it; the seven pay-and-money figures and the pay breakdown need a role allowed to see money | Live | | Trailer 360 | Anyone can open it; the trip Revenue column needs a role allowed to see money | Live | | Customer 360 | Anyone can open it; the entire money half needs a role allowed to see money | Live | | Export a 360's underlying rows | Anyone who can open the page | Live | | Build a custom report | Anyone; the ten money numbers need a role allowed to see money | Live | | Drill into a number | Anyone | Live | | Export a custom report | Anyone | Live | | Save a report for the whole company | Anyone; requires a single company to be pinned, not All-Companies mode | Live | | Load a saved report | Anyone | Live | | Delete a saved report | Anyone in that company | Live | | Subscribe to a saved report | Anyone in that company | Live | | Unsubscribe | Anyone | Live | | Open a report straight from a notification | Anyone | Live | | Open a stale trailer straight from a notification | Anyone | Live | | Ask Lanexa a question in plain English | Any logged-in user; the money numbers are never even put in front of the AI for a role that cannot see money () | Live | | Add a filter in the Builder | Anyone | Live | | Get an honest empty answer | Anyone | Live | | Download in Excel (.xlsx) format | — | Not built | | Email a report on a schedule | — | Not built | ## Activity & Audit Log 32 live · Command & Insight | Capability | Who can do it | Status | | Read the whole company's diary in plain English | Administrators, organisation owners, and Controllers | Live | | See the true chronological order, not the write order | Administrators, organisation owners, and Controllers | Live | | Read three headline pulse numbers | Administrators, organisation owners, and Controllers | Live | | Filter to one team member | Administrators, organisation owners, and Controllers | In progress | | Filter to one module | Administrators, organisation owners, and Controllers | In progress | | Filter to one kind of action | Administrators, organisation owners, and Controllers | Live | | Search for one record by name or number | Administrators, organisation owners, and Controllers | Live | | Search safely for text containing commas and brackets | Administrators, organisation owners, and Controllers | Live | | Narrow to a date range | Administrators, organisation owners, and Controllers | Live | | Clear every filter at once | Administrators, organisation owners, and Controllers | Live | | Show the machine noise (Technical) | Administrators only | Live | | Open a row to see every field that changed | Administrators, organisation owners, and Controllers | Live | | Never see a secret in that diff | Everyone — it is unconditional | Live | | See at a glance which lines are serious | Administrators, organisation owners, and Controllers | Live | | Tell a real person from a machine or an unverified click | Administrators, organisation owners, and Controllers | Live | | Read a friendly clock and still get the exact time | Administrators, organisation owners, and Controllers | Live | | Know which company a line belongs to in All-Companies mode | Administrators, organisation owners, and Controllers | Live | | Page backwards through history | Administrators, organisation owners, and Controllers | Live | | Pull in anything new without losing your place | Administrators, organisation owners, and Controllers | Live | | Leave the screen open and have it keep itself current | Administrators, organisation owners, and Controllers | Live | | Be told plainly when there is nothing to show | Administrators, organisation owners, and Controllers | Live | | Export exactly what is on screen to a spreadsheet | Administrators, organisation owners, and Controllers | Live | | Have that export itself audited | Automatic | Live | | Check that the chain has not been broken | Administrators only | In progress | | Jump straight to one record's history from anywhere | Administrators, organisation owners, and Controllers | Live | | Read a single load's history inside the load itself | Anyone who can open the load — this panel is not permission-locked | Live | | Be told when a record has no history yet | Anyone who can open the record | Live | | Read a single trip's history inside the trip | Anyone who can open the trip | Live | | Go from a record's panel to the full feed | Anyone who can open the record — the destination is still permission-locked | Live | | Write a note against a customer that lands in the same trail | Anyone with edit rights on the customer | Live | | Page back through a customer's whole timeline | Anyone who can open the customer | Live | | Pull the audit trail as a formal report | Whoever holds the compliance-export permission — administrators and organisation owners, Dispatchers, and Safety & Compliance. Note that a Controller does not, even though they can open the Activity screen itself. · · | Live | | Read the separate deletions-and-permissions ledger | Administrators, organisation owners, and Controllers | Live | | Be told why that ledger is closed to you | Everyone sees the correct outcome | Live | | See the last few things that happened on the dashboard | Any signed-in member | Live | | Click a feed row through to the record it describes | — | Not built | | Filter the feed by severity (show me only errors) | — | Not built | | Watch events arrive live, without refreshing | — | Not built | | Run the database's real tamper check from the screen | — | Not built | ## Settings 37 live · Platform & Control | Capability | Who can do it | Status | | Switch which company you are editing | Anyone with more than one company | Live | | Edit the company's legal identity | Fields are typeable by everyone, but only someone whose role allows settings changes sees the Save button | Live | | Record safety and authority numbers | Same as above | Live | | Choose the document language | Administrators and organization admins | Live | | Upload a company logo | Administrators and organization admins | Live | | Set the remit-to address and invoice footer | Administrators and organization admins | Live | | Set the invoice numbering pattern | Administrators and organization admins | Live | | Record a branding default tax rate | Administrators and organization admins | In progress | | Set operational defaults | Typeable by everyone; persists only via the Save button, which only an Administrator sees | Live | | Choose photo upload quality | Same as above | Live | | See how much document storage you are using | Anyone who can open the tab, one company at a time | Live | | Set billing defaults | Typeable by everyone; persists via the Administrator-only Save button | Live | | Create and archive tax rates | Create: Accounting, Controller, Administrator. Archive: not permission-locked on screen | Live | | Create and delete automated tax rules | Not permission-locked on screen (section 12) | Live | | Manage the chart of accounts | Create: Accounting, Controller, Administrator. Archive / reactivate: not permission-locked on screen | Live | | Define driver pay templates | Create: Accounting, Controller, Administrator. Deactivate: not permission-locked on screen | Live | | Set the team-driver pay-split default | Accounting, Controller, Administrator | Live | | Build rate cards | New card: Accounting, Controller, Billing Clerk, Administrator. Row edit / deactivate / delete: not permission-locked on screen | Live | | Maintain the accessorial charge catalog | New accessorial: Accounting, Controller, Billing Clerk, Administrator. Row edit / deactivate / delete: not permission-locked on screen | Live | | Set the border filing identities | Administrators and organization admins | Live | | Manage customs brokers | Add: Accounting, Controller, Billing Clerk, Administrator. Row edit / delete: not permission-locked on screen | Live | | Configure notifications | Governed by that panel's own rules | Live | | Write message templates | Anyone allowed to send messages — Dispatcher, Safety, Sales, Driver, Administrator | Live | | Change your own password | Everyone — never permission-locked | Live | | Set a person's role in a company | Administrators, or organization Owners / Organization Admins | Live | | Set a person's organization role | Organization Owners / Organization Admins only (enforced on the server) | Live | | Grant or remove an individual permission | Administrators or organization admins — and you cannot grant a permission you do not hold yourself | Live | | Read what each role can do | Same as the panel | Live | | Review the audit trail | Controllers and Administrators | Live | | Define custom fields | Add: Administrators and organization admins. Row edit / delete: not permission-locked on screen | Live | | Add suggested starter custom fields | Administrators and organization admins | Live | | Toggle automations | Typeable by everyone; persists via the Administrator-only Save button | In progress | | Connect QuickBooks Online | Not permission-locked on screen; the server-side step still requires company membership | Live | | Open the QBO Sync Center | That screen is permission-locked to anyone who may edit billing or manage integrations | Live | | Set up branded email sending | Not permission-locked on screen | Live | | Store BorderConnect credentials | Not permission-locked on screen | In progress | | Configure and test PC*Miler | Not permission-locked on screen | Live | | Import Loads or Customers from CSV | Not permission-locked on screen | Live | | Browse the integration roadmap | Everyone | Live | | Deep-link straight to a tab | Everyone | Live | ## Multi-Company 12 live · Platform & Control | Capability | Who can do it | Status | | See the group's name as the page title | Anyone individually enrolled in the group | Live | | Read the group's company count | Same | Live | | Read total group revenue | Same | Live | | Read active loads across the group | Same | Live | | Read total loads ever | Same | Live | | Read combined fleet size | Same | Live | | Read combined driver headcount | Same | Live | | See revenue share as one coloured bar | Same | Live | | Hover a bar slice for exact figures | Same | Live | | Read a per-company breakdown card | Same | Live | | Reach the screen from universal search | Anyone whose group record is readable | Live | | Be told plainly when you have no group | Everyone else | Live | | Create a group | — | Not built | | Rename a group or set its reporting currency | — | Not built | | Add or remove a company from the group | — | Not built | | Enrol a person as a group admin or group viewer | — | Not built | | Set a company's brand colour or short code | — | Not built | | Switch between two groups | — | Not built | | Filter by date, quarter or year | — | Not built | | Click a company to drill into its loads | — | Not built | | Export the group view to CSV or PDF | — | Not built | | See group profit, margin, invoiced or outstanding money | — | Not built | | Refresh without reloading the page | — | Not built | --- ## Command & Insight — Lanexa TMS URL: https://lanexa.io/platform/command-and-insight Summary: Command & Insight: Dashboard, Unified Communications, Analytics, Reports, Activity & Audit Log. 144 capabilities live in Lanexa, the TMS built for Canadian Platform / Command & Insight # What is happening, and what happened? Knowing what is going on, and being able to prove what went on. Analytics is for exploring when you do not know what you are looking for; Reports is a catalogue for when you know exactly what you need and want it as a file. 5 Modules in this pillar 144 Capabilities, all live 144 Live in production Everyone Who lives here ## The modules. 01 Dashboard The Dashboard is the screen a freight company opens first every morning — it pulls together, on one page, how many trucks are rolling, how much money has come in and how much is still owed, which drivers are close to running out of legal driving hours, which licences and insurance policies are about to expire, and which delivered jobs have never been billed or are missing the paperwork that gets them paid. 22 capabilities, all live 02 Unified Communications Messages is the one place where every text, WhatsApp and email between your office and a driver, customer or broker lives as a running conversation — so nobody has to ask "did anyone reply to him?" ever again. 36 capabilities, all live 03 Analytics Analytics turns the freight you already booked, billed, paid for and fuelled into seven boards of business numbers — what you earned, what you kept, whether you delivered on time, who owes you money, and where your fuel tax is heading — and every number on those boards states out loud how much of your business it was actually able to measure. 25 capabilities, all live 04 Reports Reports is where you pull the paperwork and the numbers out of the business — twenty-one ready-made registers you can run and download, four "everything about one truck / driver / trailer / customer" pages, and a build-your-own report tool that answers a plain-English question without ever inventing a number. 29 capabilities, all live 05 Activity & Audit Log Activity is the tamper-evident diary of the whole company — one scrolling, filterable, exportable list of every record anyone created, changed, deleted or was refused permission to touch, written automatically by the database itself so nobody has to remember to log anything and nobody can quietly erase it afterwards. 32 capabilities, all live ## The other pillars. Revenue & Movement What are we moving, and how? ↗ Resources Can we take this job? ↗ Border & Compliance Are we legal? ↗ Money Did we get paid, and did we pay? ↗ Platform & Control How is this set up? ↗ --- ## Money — Lanexa TMS URL: https://lanexa.io/platform/money Summary: Money: Billing, Accounts Payable, Payroll & Settlements, Ledger. 135 capabilities live in Lanexa, the TMS built for Canadian carriers. Platform / Money # Did we get paid, and did we pay? Money in, money out, and the books that reconcile them. The ledger is what makes this a financial system rather than a billing screen: every invoice, bill, settlement and fuel receipt posts double-entry lines on its own. 4 Modules in this pillar 135 Capabilities, all live 135 Live in production Accountants and controllers Who lives here ## The modules. 01 Billing Billing is where a delivered load turns into a bill the customer actually receives, and where the company watches, chases, corrects and banks the money that comes back. 46 capabilities, all live 02 Accounts Payable Accounts Payable is the screen where you enter every bill another carrier or vendor sends you, decide whether it is right, approve it, pay it, and keep the paper trail — so the money going *out* of the company is as controlled as the money coming *in*. 24 capabilities, all live 03 Payroll & Settlements Payroll is where a freight company works out exactly what each driver has earned for a pay period — miles run, waiting time, fuel charged back, advances and loans — puts the numbers in front of a second person to sign off, and then records that the driver was actually paid. 47 capabilities, all live 04 Ledger The Ledger is the company's own set of books — every invoice, customer payment, carrier bill, bill payment, driver settlement and fuel receipt writes itself into a double-entry ledger automatically, and this screen lets you read those books, prove they balance, see where cash is heading, and click any number straight back to the paperwork it came from. 18 capabilities, all live ## The other pillars. Revenue & Movement What are we moving, and how? ↗ Resources Can we take this job? ↗ Border & Compliance Are we legal? ↗ Command & Insight What is happening, and what happened? ↗ Platform & Control How is this set up? ↗ --- ## Platform & Control — Lanexa TMS URL: https://lanexa.io/platform/platform-and-control Summary: Platform & Control: Settings, Multi-Company. 49 capabilities live in Lanexa, the TMS built for Canadian carriers. Platform / Platform & Control # How is this set up? The configuration layer. Settings has the widest reach of any module — it writes the rules the other twenty-one obey — which makes it the highest-privilege surface in the product and the one most worth guarding. 2 Modules in this pillar 49 Capabilities, all live 49 Live in production Administrators Who lives here ## The modules. 01 Settings Settings is the back office where the owner sets up the trucking company once — its legal name and safety numbers, its logo and invoice wording, its tax rates and pay formulas, its customs brokers and rate agreements, who on staff can touch what, and which outside services (QuickBooks, email, PC*Miler, BorderConnect) the business is plugged into — so every other screen in the system stops asking and just knows. 37 capabilities, all live 02 Multi-Company When one owner runs several trucking companies side by side, this single screen adds them up — loads, revenue, trucks, trailers and drivers, each company in its own colour — so the owner can see the whole family of businesses at a glance without ever mixing their separate sets of books. 12 capabilities, all live ## The other pillars. Revenue & Movement What are we moving, and how? ↗ Resources Can we take this job? ↗ Border & Compliance Are we legal? ↗ Money Did we get paid, and did we pay? ↗ Command & Insight What is happening, and what happened? ↗ --- ## Resources — Lanexa TMS URL: https://lanexa.io/platform/resources Summary: Resources: Fleet, Drivers, Customers. 106 capabilities live in Lanexa, the TMS built for Canadian carriers. Platform / Resources # Can we take this job? The people and equipment the business runs on. These three modules answer the same question from different angles — is there a driver, is there equipment, and is the customer good for the money. 3 Modules in this pillar 106 Capabilities, all live 106 Live in production Dispatchers and owners Who lives here ## The modules. 01 Fleet Fleet is the one register of every truck, trailer and yard the company owns — what each unit is, where it is sitting right now, whether its plates, insurance and safety papers are still valid, and how hard it has been working. 41 capabilities, all live 02 Drivers Drivers is the people file for everyone who turns a wheel for you — their contact details, their licence and medical paperwork with expiry warnings, their border and dangerous-goods documents, how many hours they have left to drive today, what truck they are married to, when they are on holiday, and every load they have run — held in one screen so a dispatcher never puts an out-of-date driver on a load. 20 capabilities, all live 03 Customers Customers is the one book of everyone who pays you — shippers, brokers, bill-to parties and interline partners — holding their contacts, their credit limit, what they owe you right now, the paperwork you insist on before you invoice them, and the fuel-surcharge terms you agreed to, so that dispatch, billing and the border desk all quote the same firm from the same record. 45 capabilities, all live ## The other pillars. Revenue & Movement What are we moving, and how? ↗ Border & Compliance Are we legal? ↗ Money Did we get paid, and did we pay? ↗ Command & Insight What is happening, and what happened? ↗ Platform & Control How is this set up? ↗ --- ## Revenue & Movement — Lanexa TMS URL: https://lanexa.io/platform/revenue-and-movement Summary: Revenue & Movement: Loads, Trip Board, Load Status, Interline Desk, Quotes. 183 capabilities live in Lanexa, the TMS built for Canadian carriers. Platform / Revenue & Movement # What are we moving, and how? This is the business. Everything else exists to serve or observe it — pricing work before it is committed, turning an accepted quote into a load, planning which truck runs it, watching what gets stuck, and handing work to a partner when you cannot cover it yourself. 5 Modules in this pillar 183 Capabilities, all live 183 Live in production Dispatchers Who lives here ## The modules. 01 Loads This is the book of every shipment the company has agreed to haul — you write the job down here when a customer books it, you put a driver and truck on it, you watch it move from pickup to delivery, and the moment it delivers the system turns it into an invoice. 44 capabilities, all live 02 Trip Board The Trip Board is the dispatcher's command centre — one screen that shows every truck currently working on top, every piece of booked freight waiting below, and lets the dispatcher build a run, put a driver and a truck on it, and tick off each stop as the day happens. 40 capabilities, all live 03 Load Status Load Status is the wall a dispatcher watches all day — every shipment in the company shown as a card in a lane, on a map, or on a driver calendar, so that moving a load from "booked" to "on the truck" to "delivered" is one drag, and the system refuses the moves that would corrupt the money behind them. 36 capabilities, all live 04 Interline Desk The Interline Desk is where you hand a load you already sold to another trucking company, watch them accept or decline the offer, send them the signed-rate paperwork, and get the bill you owe them created automatically the moment they deliver — while you stay the carrier the customer knows and invoices. 28 capabilities, all live 05 Quotes Quotes is where a price offer is built, priced against your own past lanes and your own cost floor, emailed to the customer as a real PDF with a link they can accept online without an account — and, the moment they accept, turned into a booked Load automatically unless their unpaid bills say otherwise. 35 capabilities, all live ## The other pillars. Resources Can we take this job? ↗ Border & Compliance Are we legal? ↗ Money Did we get paid, and did we pay? ↗ Command & Insight What is happening, and what happened? ↗ Platform & Control How is this set up? ↗ --- ## Pricing — Per Person, Not Per Truck | Lanexa URL: https://lanexa.io/pricing Summary: Lanexa is priced per user in Canadian dollars, never per truck. Trucks, trailers, drivers and loads are unlimited on every plan. Final numbers coming soon. Pricing # Priced per person. Not per truck. Add a truck and your bill does not move. ## Why it works that way. Charging per truck penalises you for growing, and it prices the thing that costs us nothing. We charge for the people using the software, because that is what actually drives our cost — which means your dispatchers, ops and billing seats, and nothing else. Solo · Free Free on the way A free tier for single-truck owner-operators to run loads, documents and invoicing without a subscription. On the way. - Loads, documents and invoicing - Quarterly IFTA with per-litre Canadian rates - Branded tracking link for your customer - Your data hosted in Canada Tell us you want it Lane · Most popular Coming soon per user, per month · CAD Everything a carrier needs to dispatch, cross the border, bill and get paid. - Trip Board and Load Board across Canada, the US and Mexico - eManifest — ACE, ACI, PARS and PAPS prepared in-app - Billing with QuickBooks Online sync in CAD and USD - A real double-entry ledger, posting on its own - Driver settlement and pay - Fleet, drivers and customer records - Document management with automatic filing - Compliance, credential expiries and quarterly IFTA - Email and SMS driver messaging Talk to us Corridor Coming soon per user, per month · CAD Everything in Lane, plus the premium layer for operations running partners, multiple companies or deeper reporting. - Everything in Lane - Unified Communications Hub — SMS, WhatsApp and email in one inbox - Interline Desk — tender to partners, carrier bill writes itself - Advanced analytics and the reporting studio - Activity and audit log - Multi-company operations - Single sign-on - Onboarding support Talk to us ## What every plan includes. 01 All 22 modules — there is no accounting add-on and no cross-border module to buy separately 02 Unlimited trucks, trailers, drivers and loads on every plan 03 Your data hosted in Canada, under Canadian privacy law 04 No setup fee ## When the numbers land. We are setting prices with our first group of carriers so they are right rather than fast. If you tell us your setup — fleet size, how many people would use it, whether you run cross-border — we will send you your price the day it is set, and early access members see it first. Send me my price when it is set See what you would be buying ### What we'll ask you - Fleet size Power units and trailers — it does not change your price, but it shapes the demo. - Seats How many dispatchers, ops and billing people would use it. - Cross-border lanes Which crossings you run, so we show you the border inside the load. Per user not per truck CAD billed in Canadian dollars Unlimited trucks, trailers and loads ## The things you're actually wondering. How is Lanexa priced? Per user, in Canadian dollars — the people using the software, not the trucks. Trucks, trailers, drivers and loads are unlimited on every plan, so adding a truck does not change your bill. Final per-seat numbers are not published yet. Do I pay more as I add trucks? No. Charging per truck penalises you for growing. Lanexa charges for the people using the software, because that is what actually drives the cost of running it. Is there a setup fee? No setup fee. Corridor includes onboarding support, scoped as part of getting you live. What is included in every plan? All 22 modules. There is no separate accounting add-on and no cross-border module to buy — it is one product. Your data is hosted in Canada under Canadian privacy law. --- ## Accounts Payable — Lanexa TMS URL: https://lanexa.io/product/accounts-payable Summary: Accounts Payable is the screen where you enter every bill another carrier or vendor sends you, decide whether it is right, approve it, pay it, and keep the Platform / Money / Accounts Payable # Accounts Payable Accounts Payable is the screen where you enter every bill another carrier or vendor sends you, decide whether it is right, approve it, pay it, and keep the paper trail — so the money going *out* of the company is as controlled as the money coming *in*. Book a 20-min demo See the Money pillar 24 Capabilities, all live 100% In production Money Pillar 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. AUTO ### The books post themselves Every insert, update and delete on a bill or a payment fires a routine that deletes the document's existing postings and re-derives them from the current state (, ). Re-posting a bill also re-posts its payments first, so a bill that becomes AUTO ### Approval starts a clock Leaving Draft or Pending marks the bill committed; from that moment plus three days, the bill's money fields are frozen against ordinary edits (, ). AUTO ### The exchange rate is resolved even when nobody supplied one Before every insert and before any change to currency, exchange rate or company, a guard sets the rate to 1 for home-currency bills, honours a genuinely booked rate, and otherwise looks one up dated to the bill's issue date — refusing the w AUTO ### A partner payable writes itself Three separate watchers — on load status, on POD documents, and on assignment completion — all call the same routine, so whichever signal arrives last produces the bill (, ). It cannot run twice for the same assignment, and it swallows its ## 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. 01 Spot an auto-created partner payable Partner bills carry a purple INTERLINE badge in the Bill # cell, and for Canadian-dollar bills it reads "INTERLINE · 0% GST" with a tooltip explaining the zero-rating. 02 Build the bill line by line Add and remove charge lines; type description, quantity and rate. The amount recalculates as you type; the last remaining line cannot be removed., 03 Bill in another currency Choose CAD, USD or MXN. The exchange rate on the day of the bill is stamped onto the record automatically., 04 Record a payment Actions menu → Record Payment (or the detail-panel button). Only offered on an Approved bill with a balance over one cent. Enter date, method (Cheque, ACH, Wire, Credit Card, Cash, Other), amount, reference number and notes., 05 Jump straight to one bill from elsewhere A link of the form opens that bill's detail immediately, then cleans the address bar. Used by the Ledger drill-through, the Interline desk and the Cmd-K search. Unknown values raise a "Not found" toast. 06 See what the company owes, at a glance Read the five summary tiles: Total Payable (everything not paid or cancelled, net of part-payments), Pending Approval, Approved, Paid, and — only when it applies — Partner Payables (trust)., 07 See trust-money separately The purple "Partner Payables (trust)" tile appears only when unpaid partner bills exist. Its tooltip explains that under Ontario law the customer's payment for a farmed load is held in trust until the partner is paid — it is not working capital., 08 Enter a new bill Press "New Bill". Fill in bill number, vendor, optional load, PO / REF / load-tender references, issue and due dates, currency, tax rate, notes, and at least one charge line. Press "Create Bill"., ## What we haven’t built here — by design. Publishing this is the point. Accounts Payable ships 24 capabilities today; these 11 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Charge tax on the bill | In progress | | Approve a bill | In progress | | Record a short pay with a reason | In progress | | Keep the vendor's paperwork with the bill | In progress | | See a friendly message when the list is empty | Not built | | Record a payment in the bill's own currency | Not built | | Undo a deleted bill | Not built | | Edit a bill's money fields after the 3-day lock | Not built | | See an aged payables report (30 / 60 / 90 days) | Not built | | Approve or pay several bills at once | Not built | | Email a remittance advice to the vendor | Not built | ## Nearby in Money. Billing 46 live ↗ Payroll & Settlements 47 live ↗ Ledger 18 live ↗ --- ## Activity & Audit Log — Lanexa TMS URL: https://lanexa.io/product/activity Summary: Activity is the tamper-evident diary of the whole company — one scrolling, filterable, exportable list of every record anyone created, changed, deleted or Platform / Command & Insight / Activity & Audit Log # Activity & Audit Log Activity is the tamper-evident diary of the whole company — one scrolling, filterable, exportable list of every record anyone created, changed, deleted or was refused permission to touch, written automatically by the database itself so nobody has to remember to log anything and nobody can quietly erase it afterwards. Book a 20-min demo See the Command & Insight pillar 32 Capabilities, all live 100% In production Command & Insight Pillar 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. AUTO ### Thirty-eight tables are watched, permanently No developer or user decides whether a change is "worth logging". The recorder is attached at the database level and fires on every insert, update and delete. onwards AUTO ### Every update produces a real field-by-field diff Not a summary — the actual old and new value of each field that differed, stored as structured data, which is why the expanded row can show rather than "load updated". AUTO ### Every row is fingerprinted into a hash chain before it lands SHA-256 over nine things in all: the previous fingerprint plus eight fields of the new row (its ID, its timestamp, company, actor, action, target type, target ID and full context). Change any of those nine afterwards and the fingerprint no AUTO ### Every row is fingerprinted a second time, into its organisation's own chain So an organisation can verify its own history independently. Rows with no company belong to no organisation and are correctly excluded. · ## 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. 01 Never see a secret in that diff Any field whose *name* contains token, secret, key or password prints as regardless of what the value looks like — applied before the value can reach the screen, a spreadsheet cell, or an exported report. · 02 Leave the screen open and have it keep itself current Every sixty seconds, while the browser tab is actually visible, the same top-up refresh runs by itself. A footnote at the bottom of the page says so, rather than the screen changing under the reader with no explanation. · 03 Write a note against a customer that lands in the same trail The customer drawer's Notes tab writes a note as an ordinary audit event, so it appears interleaved with that customer's created / updated / refused history rather than in a separate list. · 04 Search safely for text containing commas and brackets A search like would normally corrupt the query language used to talk to the database. The term is quoted and escaped before it is sent, so punctuation in a search is just punctuation. 05 Be told why that ledger is closed to you Someone without the permission gets a padlock and a sentence naming exactly what they are missing — "Your role doesn't include the 'View the audit trail' capability" — rather than an empty panel that looks broken. The Settings tab itself is also hidden from th 06 Narrow to a date range Two date pickers, From and To, both inclusive, both cut on the reader's own local midnight — because a dispatcher reads "today" on their own wall clock, not on a server's. · 07 Clear every filter at once A RESET control appears as soon as any filter is active and returns the screen to its default state. The Technical toggle is deliberately not counted as a filter, so switching it on does not make Reset appear. · 08 Show the machine noise (Technical) A checkbox that reveals the two classes of row hidden by default: ambient browser telemetry (every button click and page change, marked unverified) and anything logged at debug level. Off by default, and drawn only for administrators — for everyone else the co ## What we haven’t built here — by design. Publishing this is the point. Activity & Audit Log ships 32 capabilities today; these 7 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Filter to one team member | In progress | | Filter to one module | In progress | | Check that the chain has not been broken | In progress | | Click a feed row through to the record it describes | Not built | | Filter the feed by severity (show me only errors) | Not built | | Watch events arrive live, without refreshing | Not built | | Run the database's real tamper check from the screen | Not built | ## Nearby in Command & Insight. Dashboard 22 live ↗ Unified Communications 36 live ↗ Analytics 25 live ↗ Reports 29 live ↗ --- ## Analytics — Lanexa TMS URL: https://lanexa.io/product/analytics Summary: Analytics turns the freight you already booked, billed, paid for and fuelled into seven boards of business numbers — what you earned, what you kept, whethe Platform / Command & Insight / Analytics # Analytics Analytics turns the freight you already booked, billed, paid for and fuelled into seven boards of business numbers — what you earned, what you kept, whether you delivered on time, who owes you money, and where your fuel tax is heading — and every number on those boards states out loud how much of your business it was actually able to measure. Book a 20-min demo See the Command & Insight pillar 25 Capabilities, all live 100% In production Command & Insight Pillar 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. AUTO ### Every CSV export writes an audit line The user sees a file appear in their downloads folder. What also happens, after the download has already started, is a lookup of the signed-in user's identity and an insert into reading, for example, "Alex Laxman exported CSV: Revenue data AUTO ### Five of the seven browser-side data feeds are live Loads, invoices, drivers, vehicles and customers each subscribe to database change notifications, so a load booked, an invoice paid or a truck put into maintenance while the page is open causes that feed to refetch and every dependent chart AUTO ### The address bar is rewritten on every tab and window change Selecting a tab or a date range silently replaces the browser address with — replaced, not pushed, so toggling tabs does not fill the Back button with history. Defaults are omitted from the address. AUTO ### Date filters are quantised to the minute before they reach the server Each of the four server-call services floors the cut-off timestamp to the nearest minute before using it. This is invisible to the reader and changes no answer a human could perceive, but it is what stops a runaway loop of requests when a c ## 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. 01 Be told when a number cannot be produced In "All Companies" mode an amber banner reads "Pick a single company to see money metrics", gives the reason, and adds that load counts still cover every company. The Fuel tab shows its own version of the same refusal. · 02 See a locked tile instead of a blank one A user without the money permission sees the tile's name and a padlock reading "Restricted", with a tooltip saying it is restricted to Admin and Accounting — rather than an empty space that reads as missing data. 03 See today's trading Today's Snapshot: Orders Created today, Delivered today, and today's Revenue — counted against the calendar day, independent of the selected window. · 04 Rank your busiest lanes Top 10 Lanes table: lane, load count, revenue, average rate — ordered by load count, not by money. · 05 Export the revenue dataset Downloads with Probill, Load #, Customer, Origin, Destination, Rate, Status and Pickup for every load in the window. A load with no rate yet exports blank, not zero, so a spreadsheet cannot average an unquoted load as a free move. The download is written to th 06 Track margin over time Margin Trend: revenue, cost and margin plotted by month on one chart. 07 See per-load profit Load Profitability: the top 50 loads by revenue with Load #, Customer, Revenue, Cost, Margin and Margin %. A load with no captured cost prints "—" in all three money columns. 08 Export the profitability dataset Downloads. Uncosted loads export blank cost and margin so a spreadsheet cannot average them as 100% margin. Written to the activity log. ## What we haven’t built here — by design. Publishing this is the point. Analytics ships 25 capabilities today; these 12 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Rank drivers | In progress | | Read gross margin honestly | In progress | | See which lanes actually make money | In progress | | Separate what you booked from what you billed | In progress | | See customer counts and terms | In progress | | Rank customers by revenue | In progress | | See who owes you money | In progress | | Export outstanding invoices | In progress | | Schedule this report by email | Not built | | Click a chart to filter the loads behind it | Not built | | Set your own margin thresholds | Not built | | Print or produce a PDF of a board | Not built | ## Nearby in Command & Insight. Dashboard 22 live ↗ Unified Communications 36 live ↗ Reports 29 live ↗ Activity & Audit Log 32 live ↗ --- ## Billing — Lanexa TMS URL: https://lanexa.io/product/billing Summary: Billing is where a delivered load turns into a bill the customer actually receives, and where the company watches, chases, corrects and banks the money tha Platform / Money / Billing # Billing Billing is where a delivered load turns into a bill the customer actually receives, and where the company watches, chases, corrects and banks the money that comes back. Book a 20-min demo See the Money pillar 46 Capabilities, all live 100% In production Money Pillar 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. AUTO ### Double-entry accounting posts itself A trigger on both the invoices and the invoice-payments tables calls a re-posting routine after every insert, update and delete. For an invoice it deletes any previous postings for that document and — unless the invoice is DRAFT, CANCELLED AUTO ### The load's journey timeline gets stamped An event with the amount and currency is written on invoice insert, deduplicated by invoice id, and the whole thing is wrapped so a failure warns rather than blocking the invoice (). A separate trigger does the same for payments. AUTO ### Everything is audited three ways A change-log trigger records before and after states on invoices, invoice line items, invoice payments, factoring tables and detention charges. The payment routine writes an activity-log line naming the amount, the invoice and the resulting AUTO ### The commit clock starts on its own The first time an invoice leaves DRAFT, a trigger stamps the moment. Three days later a second trigger begins refusing changes to its financial fields (). ## 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. 01 Price a fuel surcharge from the index "+ Fuel Surcharge (indexed)" asks the database resolver for the customer's indexed schedule against this week's diesel index and writes the provenance verbatim as the line description (). 02 Add a charge line from the catalogue "+ Add Charge…" offers the fixed charge-code catalogue grouped by category; the code auto-fills the description and whether it is taxable, and refuses to add the same code twice (it flashes the existing line instead) (). 03 Download the invoice as a PDF Detail footer → Download PDF. Also files a copy into the document library automatically (). 04 Void an unpaid invoice Row menu → Void…. Requires a typed reason of at least 10 characters. Keeps the number and the history; cannot be undone (). 05 Push one invoice to QuickBooks Sync to QuickBooks in the invoice detail footer. Refuses drafts locally with an explanation rather than round-tripping (). 06 Email the invoice with its document packet From the detail footer, Send (or Resend). Generates the invoice PDF — optionally combined with Bill of Lading and Proof of Delivery into one file — attaches any other catalogued load documents, and sends one email (). 07 Record a payment Row menu → Record Payment, or the detail footer button. Enter amount, date, method, reference and notes; Pay in Full fills the outstanding balance (). The method list is fixed: Check, ACH, Wire, Credit card, Cash, Other (). 08 Raise a credit memo (row menu) Row menu → Credit memo…. Amount plus reason; issues a negative invoice numbered dated today (). ## What we haven’t built here — by design. Publishing this is the point. Billing ships 46 capabilities today; these 1 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Edit a frozen invoice with a reason | Not built | ## Nearby in Money. Accounts Payable 24 live ↗ Payroll & Settlements 47 live ↗ Ledger 18 live ↗ --- ## Compliance, IFTA & Safety — Lanexa TMS URL: https://lanexa.io/product/compliance Summary: This is where a carrier proves it is legal to be on the road — how many hours each driver has left, which licences and medicals are about to expire, what h Platform / Border & Compliance / Compliance, IFTA & Safety # Compliance, IFTA & Safety This is where a carrier proves it is legal to be on the road — how many hours each driver has left, which licences and medicals are about to expire, what happened in every crash, and the quarterly fuel-tax return that has to be filed with the province or state that issued the plates. Book a 20-min demo See the Border & Compliance pillar 40 Capabilities, all live 100% In production Border & Compliance Pillar 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. AUTO ### Every incident write leaves a trail twice over The application writes a human-readable audit line naming the user, the action and the entity — on report, on status change, and on deletion — and independently a database trigger on the table records every insert, update and delete into th AUTO ### Soft-deleting a crash preserves the whole row in the audit trail The deletion function stamps the deletion timestamp and captures the entire row in the same statement, then files that snapshot as a SOFT_DELETE audit event with the actor's name attached — so what the record contained is recoverable from t AUTO ### Every spreadsheet download is logged; PDF downloads are not The shared spreadsheet helper writes an audit line with the row count and file name after the download fires — deliberately after, so a logging failure never costs the user their file. The PDF generators save directly to the browser and wri AUTO ### The federal testing trigger recomputes on every write Both create and update re-derive the required flags from the criteria — an update with a narrow patch falls back to the stored criteria so a partial edit cannot accidentally clear a requirement., ## 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. 01 Create an IFTA quarter "New Quarter" on the IFTA workspace: year, quarter (with month ranges shown), base jurisdiction code — pre-filled with the current year and quarter and a default base of ON. The filing due date is set automatically — Q1 to Apr 30, Q2 to Jul 31, Q3 to Oct 31, Q 02 See which credentials are about to lapse Credentials tab. Scans every active driver for five expiry dates — driver licence, medical certificate, travel document, FAST card, and (only when the driver is certified for dangerous goods) the TDG certificate — and lists anything already expired or due with 03 Export the quarterly return report A spreadsheet (one row per jurisdiction plus a labelled TOTALS row) and a PDF (letterhead, quarter meta, fleet summary, per-jurisdiction table, totals, surcharge and carbon subtotals, grouped warnings, disclosure footer)., 04 Export the per-account filing pack Groups the quarter by IFTA account using the truck-to-account mapping, allocates the fleet numbers proportionally by miles, marks each line as directly attributed or defaulted, flags unrated jurisdictions, and prints a return summary plus jurisdiction schedule 05 Manage IFTA accounts Add / edit an account (number, base jurisdiction, legal name, trade name, address, separate mailing address behind a same-as checkbox), see how many trucks are assigned to each, and deactivate or reactivate — never delete., 06 Open one driver's hours breakdown Clicking any hours row opens a panel with the three counters against their limits, an "approaching daily driving limit" banner past 75%, operating country, home base, licence class, licence expiry and medical expiry. 07 Tick the tests off Reopening a saved incident reveals a Test Completion block that records each test as done, with its timestamp and result. Marking a test complete is what makes its countdown pill disappear. 08 Lose the ability to edit once a case is closed Reopening an incident that is RESOLVED or CLOSED shows every field greyed out. The record stays readable but nothing on it can be changed. ## What we haven’t built here — by design. Publishing this is the point. Compliance, IFTA & Safety ships 40 capabilities today; these 2 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | PSP reports, MVR checks, drug and alcohol programme tracking, DOT inspection history | Not built | | Electronic filing of the IFTA return | Not built | ## Nearby in Border & Compliance. eManifest 29 live ↗ Documents 30 live ↗ --- ## Customers — Lanexa TMS URL: https://lanexa.io/product/customers Summary: Customers is the one book of everyone who pays you — shippers, brokers, bill-to parties and interline partners — holding their contacts, their credit limit Platform / Resources / Customers # Customers Customers is the one book of everyone who pays you — shippers, brokers, bill-to parties and interline partners — holding their contacts, their credit limit, what they owe you right now, the paperwork you insist on before you invoice them, and the fuel-surcharge terms you agreed to, so that dispatch, billing and the border desk all quote the same firm from the same record. Book a 20-min demo See the Resources pillar 45 Capabilities, all live 100% In production Resources Pillar 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. AUTO ### Every customer change is audited twice, in two different ways The application writes an activity entry of type naming the user and the customer — "Jane created customer Acme Foods", "Jane updated customer Acme Foods", "Jane deleted customer cu-1a2b3c4d" — fired without waiting, so a slow audit write n AUTO ### Refused writes are recorded too Whenever the shared write guard refuses — no company in scope, a cross-company identifier, or a database error — a warning-severity event is emitted. This is deliberately asymmetric: successful writes are already captured by the database tr AUTO ### The row's modification timestamp maintains itself on every update (). AUTO ### The stored load count and booked total maintain themselves A trigger on the loads table recounts them for the affected customer whenever a load's customer, driver or rate changes — and the booked total is expressed in home currency, one exchange rate per document (, ). ## 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. 01 Require a signed delivery proof before invoicing Ticks "Require POD before invoicing". Invoice creation for this customer's loads is then refused until a proof-of-delivery document is filed on the specific load., 02 Set an index-linked fuel surcharge In edit mode only: turns on "Fuel surcharge indexed to the weekly diesel price", picks cents-per-mile or percent-of-linehaul, sets the base price, step size and per-step amount, sees a live preview priced at this week's published index, and saves it against it 03 Require a named document packet before invoicing Types a comma-separated list of document codes (e.g. ). Invoicing is refused, naming the missing codes, until every one is on the load., 04 Find duplicate customers Find duplicates → Scan. Compares names, emails, phones and addresses inside the company and lists candidate pairs with a match percentage and the reasons, plus each side's load and invoice counts. A clean book is reported as a result, not a blank: "No likely d 05 Add a customer or broker Opens the form, fills company name, contact, email (all required), address, terms, credit limit, and the paperwork rules; saves. 06 Set a credit limit and currency Enters an amount and picks CAD / USD / MXN. This is what arms the credit chip, the on-hold banner, and the booking block. 07 Set credit terms Picks Net 15 / 30 / 45 / 60. Shown as a badge on every row and used to date invoices. 08 Turn a fuel-surcharge schedule off Unticks the box and saves. The row is kept and marked inactive so re-enabling reuses it rather than leaving a trail of dead rows. ## What we haven’t built here — by design. Publishing this is the point. Customers ships 45 capabilities today; these 4 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Set a customer-level payment-term override | Not built | | Set per-customer detention free hours and hourly rate | Not built | | Assign party roles (bill-to, customs broker, shipper, consignee…) | Not built | | Set a customer's default customs broker | Not built | ## Nearby in Resources. Fleet 41 live ↗ Drivers 20 live ↗ --- ## Dashboard — Lanexa TMS URL: https://lanexa.io/product/dashboard Summary: The Dashboard is the screen a freight company opens first every morning — it pulls together, on one page, how many trucks are rolling, how much money has c Platform / Command & Insight / Dashboard # Dashboard The Dashboard is the screen a freight company opens first every morning — it pulls together, on one page, how many trucks are rolling, how much money has come in and how much is still owed, which drivers are close to running out of legal driving hours, which licences and insurance policies are about to expire, and which delivered jobs have never been billed or are missing the paperwork that gets them paid. Book a 20-min demo See the Command & Insight pillar 22 Capabilities, all live 100% In production Command & Insight Pillar 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. AUTO ### The page keeps itself current with no refresh button Five live database subscriptions stay open for as long as the Dashboard is on screen: loads, drivers, vehicles and invoices each listen for *any* change and re-run their read (,, ), and the activity feed listens for new entries (). A dispat AUTO ### Every reader waits for the tenant to be decided Before the active company resolves, every read is suppressed rather than fired unfiltered. Because the company identifier already sits in each reader's dependency list, the reads fire automatically the moment scope settles — no retry logic, AUTO ### Permission lookups are collapsed into one The permission reader is mounted many times per page — sidebar, route guard, page headers, every gated button — and each instance used to fire its own session and capability requests, measured at four to eight duplicates per page load. A sh AUTO ### Time is pinned so alerts do not drift while you read The compliance card captures the current moment once at mount rather than reading the clock on every render (). The consequence is that its day counts do not tick over midnight until the card remounts. ## 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. 01 Be warned before the company's own credentials lapse Reads the Compliance Alerts card — customs bond, SCAC code and liability insurance renewal dates on a severity ladder, or a green "All clear" panel. The card disappears altogether — no panel, no message — while no company has been resolved yet, for instance du 02 Be warned before a licence, medical, insurance or safety certificate expires Reads the Upcoming Expiries panel — driver licence and medical, vehicle insurance and safety, anything inside 30 days, sorted soonest-first, red under 15 days, and "EXPIRED" once past (; thresholds ) 03 See how many jobs are moving right now Reads the Active Loads tile — a count of the loads that are In Transit, At Pickup, At Delivery or Dispatched, with pending and delivered counts underneath (, rendered ) 04 See money actually collected Reads the Revenue (Paid) tile — the sum of every paid invoice, converted into the company's home currency (, rendered ) 05 See money still owed, and how much is late Reads the outstanding figure and the overdue count in the Revenue tile footer; outstanding is the unpaid balance on invoices that have been sent, part-paid or gone past due (; engine ). When nothing is overdue the footer reads "No overdue" rather than a zero ( 06 Catch delivered loads that were never billed Reads the Uninvoiced Loads tile — loads that have reached Delivered, Invoiced or Paid but carry no live invoice. Turns amber the moment the count exceeds zero (,; engine ) 07 See driver availability at a glance Reads the Drivers tile — how many are working right now (driving or on duty) with how many are free underneath (, rendered ) 08 Be warned before a driver runs out of legal hours Reads the HOS warning count in the Drivers tile, and the amber HOS panel lower down listing each driver, their country flag, hours used against their limit, and the percentage. Fires above 75% of the daily driving maximum (, panel; limits ) ## What we haven’t built here — by design. Publishing this is the point. Dashboard ships 22 capabilities today; these 5 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Jump into the billing work queue from that tile | In progress | | See this week's diesel index | In progress | | Change anything | Not built | | Filter by date range | Not built | | Manually refresh the page | Not built | ## Nearby in Command & Insight. Unified Communications 36 live ↗ Analytics 25 live ↗ Reports 29 live ↗ Activity & Audit Log 32 live ↗ --- ## Documents — Lanexa TMS URL: https://lanexa.io/product/documents Summary: 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 cus Platform / Border & Compliance / Documents # 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. Book a 20-min demo See the Border & Compliance pillar 30 Capabilities, all live 100% In production Border & Compliance Pillar 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. AUTO ### 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 AUTO ### 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 AUTO ### 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 AUTO ### 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. 01 Automatic photo compression Silent. Any JPEG, PNG or WebP over 350 KB is downscaled to a 2,400-pixel long edge and re-encoded as WebP before it is ever stored, keeping a letter page above the 200-DPI floor that scanning and text recognition need. A typical 3–8 MB phone photo lands around 02 Duplicate detection Every file is fingerprinted (SHA-256) before it is stored. If a byte-identical live file already exists in the same company, nothing is stored twice — the wizard marks the row "already on file" and hands the existing document back., 03 Create a secure external share link The share icon mints a link with a 7, 30 or 90-day expiry, copies it to the clipboard, and lists every link on that document with its state (Active / Expired / Revoked), its expiry date and how many times it has been opened. The recipient needs no login: they 04 Request a missing document by no-login link From a load group header or a radar row, pick the document you need, a 7/14/30-day expiry, and an optional note ("the signed copy from the receiver, please"). The link is copied to the clipboard. Whoever opens it — driver, broker, warehouse — passes a bot chec 05 Per-load required-document checklist Computed from the load's own attributes rather than a fixed list: every load needs a Rate Confirmation and a BOL; a POD becomes required once it is delivered; a cross-border load adds PAPS/PARS, an ACE/ACI eManifest confirmation and a Commercial or Canada Cust 06 Documents panels on other records The same catalogue surfaces as an embedded panel on Customers (contracts, carrier packets, notices of assignment), Fleet vehicles (permits, interchange receipts), Drivers (non-credential documents), Interline partner loads, and Accounts Payable carrier bills. 07 Honest empty states on all four tabs Nothing in this module ever shows a blank panel. The radar says "All clear — every active load has its required documents." The Review queue shows an inbox icon, "Review queue is clear", and one line explaining what will land there and why. The Deleted view sa 08 Upload documents (wizard) Pick several files at once, choose a document type per file from the 49-code catalogue grouped by category, optionally tick "Keep original quality", then link the whole batch to a load, invoice, manifest, driver, vehicle and customer — each chosen from a searc ## 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 | ## Nearby in Border & Compliance. eManifest 29 live ↗ Compliance, IFTA & Safety 40 live ↗ --- ## Drivers — Lanexa TMS URL: https://lanexa.io/product/drivers Summary: Drivers is the people file for everyone who turns a wheel for you — their contact details, their licence and medical paperwork with expiry warnings, their Platform / Resources / Drivers # Drivers Drivers is the people file for everyone who turns a wheel for you — their contact details, their licence and medical paperwork with expiry warnings, their border and dangerous-goods documents, how many hours they have left to drive today, what truck they are married to, when they are on holiday, and every load they have run — held in one screen so a dispatcher never puts an out-of-date driver on a load. Book a 20-min demo See the Resources pillar 20 Capabilities, all live 100% In production Resources Pillar 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. AUTO ### Every driver change writes an activity entry Creating writes "[user] added driver Jane Smith"; updating writes "[user] status → ON_DUTY driver Jane Smith" when the status changed, or "[user] updated driver …" otherwise; deleting writes "[user] removed driver [reference]". Each carries AUTO ### Every successful change also writes a full before/after comparison A database rule records who changed what, when, and the old and new values on the driver table, on leave periods, and on the three payroll tables. This is the record the Activity page reads. AUTO ### Every refusal is recorded too When a tenant-guard primitive refuses — no active company, cross-company record, or a database error — it fires a warning-severity event named with the reason. This is deliberately asymmetric: successful writes are already captured by the c AUTO ### Deleting a credential writes its own event , carrying the credential type and file name, the driver, the storage location and whether the file was actually removed. ## 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. 01 Add a driver Presses Add Driver, fills first/last name, email, phone, licence number, licence class and province, licence expiry, medical expiry, status, duty status, home base, operating country and HOS rules, notes, and optionally the whole International / Border Crossin 02 Retry a failed load of the list If the driver list cannot be fetched, the screen shows a named error with a Retry button rather than an empty table that would read as "no drivers".; the precedence rule is 03 See expiry traffic lights Reads the two dots in the Expiry column — for licence, for medical. Green over 30 days out, amber within 30 days, red once expired, grey when the date is missing or unreadable. Hovering shows the exact date.,; thresholds in 04 Record border and immigration details Expands the 🛂 International / Border Crossing panel and fills date of birth, gender, home address, citizenship country, licence issuing country, travel document (14 types incl. Passport, NEXUS, SENTRI, FAST Card, Permanent Resident Card), FAST card number and 05 Change a driver's duty status Inside the edit form, picks from Available / On Duty / Driving / Sleeper / Off Duty / Vacation / Terminated., 06 Assign or change a driver's default truck Picks Assign Vehicle from the kebab menu or presses Assign / Change in the detail panel's Default Vehicle box, then searches by unit number or location and selects a truck.,; 07 Delete a credential Presses the red trash icon on a credential row. The record is removed permanently and the stored file is deleted with it.; 08 Attach other documents to a driver Below the credentials list, the shared documents panel lists and accepts anything else filed against this driver — trip sheets, expense receipts, fuel receipts.;, ## What we haven’t built here — by design. Publishing this is the point. Drivers ships 20 capabilities today; these 10 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Record a communications consent | In progress | | Fill company-defined custom fields | In progress | | Filter the list by status | In progress | | Read the fleet counts strip | In progress | | See hours-of-service headroom | In progress | | Read the driver's recent loads | In progress | | Read and reply to the driver's message thread | In progress | | Delete a driver | Not built | | Set a fuel card number | Not built | | Search or sort the driver list | Not built | ## Nearby in Resources. Fleet 41 live ↗ Customers 45 live ↗ --- ## eManifest — Lanexa TMS URL: https://lanexa.io/product/emanifest Summary: The eManifest module — called the Border Desk inside the product — is where a dispatcher gets a truck legally across the Canada/US border: it assembles eve Platform / Border & Compliance / eManifest # eManifest The eManifest module — called the Border Desk inside the product — is where a dispatcher gets a truck legally across the Canada/US border: it assembles every fact customs demands for a crossing, scores how ready that crossing is, prints the barcoded paper the driver carries, emails the customs broker their package, and runs a countdown clock so nobody arrives at the booth without an accepted filing. Book a 20-min demo See the Border & Compliance pillar 29 Capabilities, all live 100% In production Border & Compliance Pillar 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. AUTO ### Every crossing action is audited Creating a crossing, every status transition (with the from-state, the to-state and the rejection reason where one exists) and every removal write an entry into the shared activity log under the type — a category that had existed since Apri AUTO ### Every status change appends a permanent history row The atomic routine writes it in the same transaction as the status change, capturing the status, the reason, the message, the source, the user's identity and their name. A database trigger then makes that row impossible to edit or delete (, AUTO ### The database stamps the milestone timestamps itself Moving to Filed sets, Accepted sets, Released sets — belt and braces, since the routine also stamps them (). AUTO ### Marking a crossing Released writes a border event onto every load riding it A trigger fans out one timeline row per member load, titled by regime, detailed with the port name, and de-duplicated so a repeat can never double-post (). ## 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. 01 Print PARS/PAPS label sheets A 2×5 grid of barcoded stickers per A4 page, four copies per shipment, sized to the CBSA 4.5-inch symbol cap — replaces bought label rolls. 02 Print the lead sheet A regime-aware cover sheet with a scannable barcode of the trip number or CRN, the port, ETA, driver, power unit, loaded/empty indicator, and one barcode per shipment. 03 Print the driver crossing packet A multi-page PDF: conveyance barcode, trip facts, a regime-specific "at the booth — have ready" checklist, a shipment detail table, and two labels per shipment. 04 Record a rejection with its reason Choosing Rejected opens a required free-text box — you must record what the portal actually said before the status will move. 05 Filing history An append-only, tamper-blocked list of every status change on the crossing with time, reason and the person's name. 06 Filter by direction and status One-click filters: All directions / ACE ↓ US / ACI ↑ Canada, plus status chips for All, Draft, Filed, Accepted, Held, Released and Rejected — six of the seven states. There is no Cancelled chip, so cancelled crossings cannot be filtered for at all; they can on 07 Border Desk list See every border crossing for the company — direction, trip, port, arrival time, status, a readiness percentage, load count and the conveyance reference — in one table. 08 Live border wait times Each row and the detail header show the current commercial-lane delay at that port, plus the FAST-lane delay where the feed supplies one, red once the wait is 30 minutes or more. ## What we haven’t built here — by design. Publishing this is the point. eManifest ships 29 capabilities today; these 3 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Deep link into a crossing | In progress | | Add a load to an existing crossing | Not built | | Transmit the filing electronically | Not built | ## Nearby in Border & Compliance. Documents 30 live ↗ Compliance, IFTA & Safety 40 live ↗ --- ## Fleet — Lanexa TMS URL: https://lanexa.io/product/fleet Summary: Fleet is the one register of every truck, trailer and yard the company owns — what each unit is, where it is sitting right now, whether its plates, insuran Platform / Resources / Fleet # Fleet Fleet is the one register of every truck, trailer and yard the company owns — what each unit is, where it is sitting right now, whether its plates, insurance and safety papers are still valid, and how hard it has been working. Book a 20-min demo See the Resources pillar 41 Capabilities, all live 100% In production Resources Pillar 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. AUTO ### Every truck change is written to the activity feed Creating, updating or deleting a truck fires an entry naming the person and the unit, tagged to that vehicle (, → ). Status changes get their own wording — "*Name* status → MAINTENANCE vehicle T-108" (). Audit writing is deliberately failur AUTO ### Every truck, trailer and yard change is separately logged in the database with a full field diff A trigger compares the before and after row, skips a no-op update entirely, excludes noise columns like timestamps, resolves the acting user's display name, and files the result under a human-readable label — the unit number for a truck or AUTO ### Refused writes are logged too When the tenant guard blocks a write — no active company, a cross-company id, or a database error — it fires a warning-level event recording exactly which table and why. This is deliberately the one thing the change-log trigger can never se AUTO ### A trailer deletion writes an immutable before-snapshot The soft-delete routine stamps the removal time and appends an audit entry containing the whole row as it was (). ## 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. 01 Add a truck Presses Add Vehicle, fills the form and saves. Unit number, make, VIN, insurance expiry and safety expiry are required; the VIN must be a valid 17-character VIN (). Writes one row to the truck register (). 02 Record the federal annual inspection Enters the last inspection date; leaving the expiry blank auto-computes it twelve months later (, form fields at ). 03 Record how a trailer is owned Chooses Owned, Leased, Rental, Customer or Pool, plus lease vendor, lease expiry and pool name (, ). 04 Record trailer inspection, plate and insurance dates Annual inspection date and expiry, plate expiry, insurance expiry and policy number (). 05 Give a yard a location and a geofence radius Enters latitude, longitude and a radius in metres. Latitude and longitude must be supplied together or not at all, and a radius without a centre point is refused (). Supplying a radius stamps the geofence as a circle (). 06 Record regulatory identifiers on a truck Fills the Regulatory Identifiers block — IFTA decal number, IFTA account, IRP apportioned plate, Ontario CVOR number (). 07 Correct or move an asset's position Picks Relocate on a truck or trailer, chooses a registered yard or types a free-form place, adds an optional note, and saves. This does not overwrite anything — it appends a relocation entry to the movement ledger, which re-derives the asset's position (). 08 Add a yard, dock, terminal or zone Presses Add Yard on the Yards tab. Name and type are required; the eleven types are Yard, Customer Site, Dock, Zone, Terminal, Cross Dock, Border, Fuel, Shop, Rest, Other (, validation at ). ## What we haven’t built here — by design. Publishing this is the point. Fleet ships 41 capabilities today; these 5 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Delete a truck outright | Not built | | Filter or count on the Yards tab | Not built | | Un-retire a truck, or restore a deleted trailer or yard | Not built | | Set a truck's odometer from telematics | Not built | | Get warned before a plate, insurance or safety date expires | In progress | ## Nearby in Resources. Drivers 20 live ↗ Customers 45 live ↗ --- ## Multi-Company — Lanexa TMS URL: https://lanexa.io/product/group Summary: When one owner runs several trucking companies side by side, this single screen adds them up — loads, revenue, trucks, trailers and drivers, each company i Platform / Platform & Control / Multi-Company # Multi-Company When one owner runs several trucking companies side by side, this single screen adds them up — loads, revenue, trucks, trailers and drivers, each company in its own colour — so the owner can see the whole family of businesses at a glance without ever mixing their separate sets of books. Book a 20-min demo See the Platform & Control pillar 12 Capabilities, all live 100% In production Platform & Control Pillar 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. AUTO ### The menu decides for itself whether this module exists Every time the sidebar renders, for every user, on every page, it silently asks the database which groups are readable. For the overwhelming majority of customers the answer is none and the menu item is never drawn — but the question is sti AUTO ### Universal search asks the same question independently The keyboard-shortcut palette and the full search page each run their own copy of the group reader and each rebuild their index with the Group entry included or excluded. That is up to three separate group lookups per session from three sep AUTO ### Every load's revenue is converted before it is summed The conversion happens inside the database using the exchange rate stamped on each individual load at the moment it was created, never a rate looked up today. AUTO ### Foreign-currency documents get their rate stamped automatically When a load, invoice or carrier bill is saved in a currency other than the company's home currency without an exchange rate, a database trigger looks the rate up from the Bank of Canada registry, dated to the document, and stamps it. Home-c ## 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. 01 Reach the screen from universal search Presses Ctrl+K or Cmd+K (or opens the Search page), types "group", and jumps here. The entry is filtered out of the search index entirely when the user has no group., 02 Be told plainly when you have no group Someone with no readable group — or whose data request is refused — sees a centred message: "You're not part of a company group. Group admins see a consolidated view of all their companies here." 03 See revenue share as one coloured bar Reads the horizontal bar under "Revenue by company". Each company occupies a slice proportional to its share of group revenue, painted in that company's own brand colour. A slice above 10% prints its percentage inside it. This is the "three colours = three com 04 Hover a bar slice for exact figures Rests the mouse on a colour slice; the browser tooltip shows the company name, its exact revenue and its rounded percentage. This is the only interactive behaviour on the entire screen. 05 See the group's name as the page title Opens the screen. The heading is replaced by the group's own name (for example "Gill Group Logistics"), with a sub-line reading "Consolidated operational view · N companies · books kept separate". 06 Read the group's company count Reads the "Companies" tile — how many companies are currently assigned to this group. 07 Read total group revenue Reads the "Total revenue" tile — every company's booked freight rate added together and shown in the group's declared currency. 08 Read active loads across the group Reads the "Active loads" tile — every load currently sitting in Dispatched, In Transit, At Pickup or At Delivery, across all companies. A Load is one customer shipment: a pickup, a delivery, a commodity and a rate.; the four counted states are fixed in the dat ## What we haven’t built here — by design. Publishing this is the point. Multi-Company ships 12 capabilities today; these 11 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Create a group | Not built | | Rename a group or set its reporting currency | Not built | | Add or remove a company from the group | Not built | | Enrol a person as a group admin or group viewer | Not built | | Set a company's brand colour or short code | Not built | | Switch between two groups | Not built | | Filter by date, quarter or year | Not built | | Click a company to drill into its loads | Not built | | Export the group view to CSV or PDF | Not built | | See group profit, margin, invoiced or outstanding money | Not built | | Refresh without reloading the page | Not built | ## Nearby in Platform & Control. Settings 37 live ↗ --- ## Interline Desk — Lanexa TMS URL: https://lanexa.io/product/interline Summary: The Interline Desk is where you hand a load you already sold to another trucking company, watch them accept or decline the offer, send them the signed-rate Platform / Revenue & Movement / Interline Desk # Interline Desk The Interline Desk is where you hand a load you already sold to another trucking company, watch them accept or decline the offer, send them the signed-rate paperwork, and get the bill you owe them created automatically the moment they deliver — while you stay the carrier the customer knows and invoices. Book a 20-min demo See the Revenue & Movement pillar 28 Capabilities, all live 100% In production Revenue & Movement Pillar 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. AUTO ### The load's farmed-out marker keeps itself true Every insert or update on a tender re-derives the load's farmed-out flag, partner name and cost from whichever tender or coverage is currently live — and clears them when none is. Nobody writes those fields by hand any more; the desk delibe AUTO ### The load's timeline writes itself Seven lifecycle entries (tender sent, accepted, declined, expired, bounced, completed, cancelled) plus two stamp entries (interchanged, crossed the border) are projected from the database, never from the browser. Each carries a de-duplicati AUTO ### Response and completion times stamp themselves Moving a tender to Covered or Declined sets the response time; moving it to Completed sets the completion time — in the database, not the browser. AUTO ### The partner's payable creates itself Three separate triggers — load delivered, proof of delivery catalogued, coverage marked complete — call one routine that builds the bill when both conditions are finally met, whichever order they arrive in. It takes a lock so concurrent tri ## 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. 01 Onboard an interline partner Presses New partner and fills a form covering company and contact details, authority numbers (USDOT, legacy MC, SCAC, CBSA carrier code, bonded flag, Ontario CVOR, Quebec CTQ, tax ID), three insurance expiry dates plus a contingent-cargo confirmation, and paym 02 Be warned about border identity before the tender goes out When the lane crosses a border and the chosen partner has no SCAC (needed for a southbound US filing) or no CBSA carrier code (needed for a northbound Canadian filing), the form says so before you send — not at the port. 03 Be nagged about partner compliance Reads coloured chips on each partner row: missing or expired auto-liability and cargo insurance are loud, trailer-interchange cover is nagged only when a date exists, missing contact email is flagged because rate confirmations cannot be emailed without it, mis 04 Tender a load to a partner Presses Tender a load, picks from a list containing only loads that can legally be tendered, picks the partner, enters the buy rate (what you pay them), chooses a currency and an offer expiry, adds notes, and sends. 05 Set an offer clock Chooses no expiry, 2, 4, 8 or 24 hours. The desk then shows "expires in 3h 20m" or "expired 45m ago" in red on the row. 06 Jump to the partner's payable Once the auto-created bill exists, the status cell shows a link like that opens Accounts Payable focused on that bill. 07 Onboard a partner without leaving the tender form A second way in to the same form: a small New button sits beside the partner picker inside the tender dialog, so a dispatcher who reaches for a partner who is not on file yet can create them on the spot instead of abandoning the tender. · wired at 08 Record that the partner files the border crossing Ticks a box meaning the crossing rides the partner's own SCAC or CBSA code, then records their control number (PAPS/PARS) and the port. ## What we haven’t built here — by design. Publishing this is the point. Interline Desk ships 28 capabilities today; these 1 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Tender straight from a partner row | In progress | ## Nearby in Revenue & Movement. Loads 44 live ↗ Trip Board 40 live ↗ Load Status 36 live ↗ Quotes 35 live ↗ --- ## Ledger — Lanexa TMS URL: https://lanexa.io/product/ledger Summary: The Ledger is the company's own set of books — every invoice, customer payment, carrier bill, bill payment, driver settlement and fuel receipt writes itsel Platform / Money / Ledger # Ledger The Ledger is the company's own set of books — every invoice, customer payment, carrier bill, bill payment, driver settlement and fuel receipt writes itself into a double-entry ledger automatically, and this screen lets you read those books, prove they balance, see where cash is heading, and click any number straight back to the paperwork it came from. Book a 20-min demo See the Money pillar 18 Capabilities, all live 100% In production Money Pillar 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. AUTO ### The posting triggers Six database triggers, one per money table, fire on every insert, update and delete and call the single posting dispatcher. This is why the ledger is never stale and why nobody has to remember to post anything. They run with elevated privil AUTO ### Delete-and-rewrite, every time The dispatcher's first act is always to delete the document's existing postings. It never patches. That is what makes it repeatable — run it a hundred times and the answer is identical — and it is why history and live writes cannot diverge: AUTO ### The cascade to child payments Changing an invoice re-posts every payment against it; changing a bill re-posts every payment against it. A parent's state change can never again strand a child's postings — which is precisely the defect this cascade was added to fix. AUTO ### Silent unposting When a document leaves a posting state — soft-deleted, returned to draft, cancelled, a settlement backed out of paid, a receipt's verification removed — the dispatcher deletes its postings and writes nothing back. No message is sent and no ## 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. 01 Run the eight tie-out checks Press Health. Eight tiles render, one per reconciliation. A tile is green and reads when the underlying check finds no problems; red with a count when it does (). A headline above them reads either "All books tie" or "Books do not tie" (), beside a line that c 02 Drill into one account Click any row of the company trial balance. A window opens listing that account's most recent postings — date, source document, line role, debit, credit — capped at the newest 200 (). Close it with the ✕ in its header or by clicking the dimmed background (). 03 Jump from a posting to the paperwork behind it Click a posting row inside the drill window. The app routes to the source document: an invoice opens Billing focused on that invoice, a carrier bill opens Accounts Payable focused on that bill, a settlement opens the Settlements screen focused on that run, a f 04 Export the trial balance to Excel or CSV Press Export for a real Excel workbook, or the caret beside it and choose CSV. Columns: Code, Account, Type, Debit, Credit, Balance, with money cells typed as currency rather than text (; button ). The file is named. 05 See balances the way an accountant reads them Nothing to press. Liability, Equity and Revenue accounts are displayed in their *normal* balance, so a healthy revenue account reads as a positive number instead of a minus sign the operator has to mentally flip. Genuinely negative balances render in the dange 06 See which postings are intercompany Nothing to press. Any posting the system identified as business with a sibling company carries a purple "intercompany" badge in the drill list (). 07 Drill a failed check to the exact offending rows Click a red tile. A window opens listing the specific rows the check rejected — the invoice numbers, bill numbers or run ids and their drift amounts, rendered straight from the check's own columns, capped at 200 (). Green tiles are not clickable and the cursor 08 See problems in sibling companies Nothing to press. When the pinned company is clean but another company in the group is not, an amber line appears under the tiles: "N problem rows in other companies of the group — switch company to inspect" (; the counting logic is at ). ## What we haven’t built here — by design. Publishing this is the point. Ledger ships 18 capabilities today; these 4 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Edit the ledger by hand | Not built | | Post a manual adjusting journal entry | Not built | | Read a monthly Profit & Loss statement | Not built | | Push the postings to QuickBooks | Not built | ## Nearby in Money. Billing 46 live ↗ Accounts Payable 24 live ↗ Payroll & Settlements 47 live ↗ --- ## Load Status — Lanexa TMS URL: https://lanexa.io/product/load-status Summary: Load Status is the wall a dispatcher watches all day — every shipment in the company shown as a card in a lane, on a map, or on a driver calendar, so that Platform / Revenue & Movement / Load Status # Load Status Load Status is the wall a dispatcher watches all day — every shipment in the company shown as a card in a lane, on a map, or on a driver calendar, so that moving a load from "booked" to "on the truck" to "delivered" is one drag, and the system refuses the moves that would corrupt the money behind them. Book a 20-min demo See the Revenue & Movement pillar 36 Capabilities, all live 100% In production Revenue & Movement Pillar 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. AUTO ### An audit line is written for every status change Phrased as a sentence — "*name* changed *load* from *A* to *B*" — and stamped with the acting user's id and name (). Audit writing is deliberately fail-quiet: if the log write fails, the business operation is not blocked (). AUTO ### That audit line becomes a Journey event A database rule reads each new activity row for a load, takes the *destination* status out of the fixed "… from A to B" sentence shape, and files a matching event on the load's timeline (). The earlier version searched the sentence for stat AUTO ### An assignment is narrated too Changing a driver, co-driver or truck writes its own audit line containing the word "assigned", so the projector types it correctly (). Before this, assignment left no trace at all — measured at 6 of 1,319 driver-carrying loads having a liv AUTO ### The status trail is appended atomically, by the database Sanctioned routines append it themselves inside the same statement that changes the status, so two dispatchers acting at once cannot lose an entry; any other writer has an entry appended for it by the trigger, marked (, ). ## 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. 01 Create a new load without leaving the board "+ New Load" opens the full load form pre-wired with customers, drivers, vehicles, rate cards and customs brokers (, ). 02 Know how many loads cannot be mapped A warning chip counts loads with no geocoded origin or destination and says they are still visible in the other two lenses (). 03 See every load as a card in a status lane Open. Four lanes — Pending, Dispatched, In Transit, Delivered — each showing its loads with route, pickup date, weight, commodity, driver and rate (, card body ). 04 Drag a load to a new status Pick a card up and drop it in another lane. Dropping it back in the lane it already occupies does nothing (). 05 One-click status advance Press the button on the card: Picked Up on a Dispatched load, At Delivery on an In-Transit load, Delivered on an At-Delivery load. A Pending load has no button — it needs a driver first (, ). 06 Be stopped from an impossible status move Attempt a move the system forbids — e.g. marking an in-transit load TONU — and get a red message explaining why, with no change written (, rule at ). 07 Be warned before a risky status move A confirmation box titled "Status Change Warning" appears before every status change (). Normally it just asks "Change DDT-L0057 from DISPATCHED to IN TRANSIT?" (). Reverse a status more than five minutes after the last change, or make a third change inside tw 08 Reset all filters A reset control appears only when at least one filter is active, and clears search plus all three pills (). ## Nearby in Revenue & Movement. Loads 44 live ↗ Trip Board 40 live ↗ Interline Desk 28 live ↗ Quotes 35 live ↗ --- ## Loads — Lanexa TMS URL: https://lanexa.io/product/loads Summary: This is the book of every shipment the company has agreed to haul — you write the job down here when a customer books it, you put a driver and truck on it, Platform / Revenue & Movement / Loads # Loads This is the book of every shipment the company has agreed to haul — you write the job down here when a customer books it, you put a driver and truck on it, you watch it move from pickup to delivery, and the moment it delivers the system turns it into an invoice. Book a 20-min demo See the Revenue & Movement pillar 44 Capabilities, all live 100% In production Revenue & Movement Pillar From the Lanexa 2.0 capability register · version 2.0.37 · reviewed 2026-08-24 ## 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. 01 Be stopped from booking an over-extended customer Pick a customer; a live credit line shows available credit, limit, open AR and utilisation. If they are ON HOLD the save is refused, 02 Auto-derive the border control number Nothing — for a southbound load the SCN is derived from your SCAC plus the probill; northbound, the CCN from your CBSA carrier code plus the probill. Filled once, visibly, only into an empty field 03 Produce a Proof of Delivery Download POD — blocked before the load reaches delivery, and the menu label says so, 04 Book a load in seconds Press New Load, type an origin city and a destination city, press Create. Everything else is optional — the load number auto-generates and a blank pickup date defaults to today 08:00, 05 Be warned about a re-sent tender Nothing — on AI import, a same-customer same-load-number match warns immediately; on manual save, a same customer + same origin + same destination + pickup within one day, or an overlapping PO number, shows an amber "this may be a duplicate" panel listing up t 06 Get distance and a route without typing it Nothing — on save, missing coordinates are geocoded from city + province and a road route is fetched, filling estimated miles only if you left it blank, 07 Mark a truck-ordered-not-used Mark as TONU — offered only on PENDING or DISPATCHED loads, and refused elsewhere by both the client guard and the database 08 Copy a load Duplicate Load — clones the details, resets status to PENDING, clears driver, truck, manifest, allocations and farm-out, and reserves a fresh probill ## What we haven’t built here — by design. Publishing this is the point. Loads ships 44 capabilities today; these 5 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Change status directly | In progress | | Reuse a lane | In progress | | See the money on one load | In progress | | Act on many loads at once | In progress | | Delete a load | In progress | ## Nearby in Revenue & Movement. Trip Board 40 live ↗ Load Status 36 live ↗ Interline Desk 28 live ↗ Quotes 35 live ↗ --- ## Unified Communications — Lanexa TMS URL: https://lanexa.io/product/messages Summary: Messages is the one place where every text, WhatsApp and email between your office and a driver, customer or broker lives as a running conversation — so no Platform / Command & Insight / Unified Communications # Unified Communications Messages is the one place where every text, WhatsApp and email between your office and a driver, customer or broker lives as a running conversation — so nobody has to ask "did anyone reply to him?" ever again. Book a 20-min demo See the Command & Insight pillar 36 Capabilities, all live 100% In production Command & Insight Pillar 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. AUTO ### Every message is threaded for you A trigger on the message table runs before every insert: it derives the counterparty from the sender (inbound) or the recipient (outbound), matches on the last ten digits of the phone (so, and are one person) or on a lowercased email, finds AUTO ### The thread's summary line maintains itself The same trigger sets, stores the first 120 characters as the preview, stamps on inbound only, adds one to on inbound only, back-fills the driver id and counterparty name if they were unknown, upgrades an UNKNOWN counterparty to DRIVER, and AUTO ### A closed thread reopens itself when the other side speaks RESOLVED flips back to OPEN on any inbound message (). AUTO ### The load's Journey gets a COMMS entry per message Written by a second trigger, deduped by message id, and wrapped so that a failure raises a warning and lets the message write succeed — a timeline projection must never cost a driver's message (). ## 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. 01 Send a templated message with an attachment The Templates button opens the full composer: pick SMS / WhatsApp / Email, pick a saved template (which auto-fills the load number, route, pickup date, equipment, rate and driver name), edit the text, attach a PDF or photo, send. 02 Mark a thread personal A "Personal / not work-related" checkbox. Flagged threads are excluded from the load's timeline, and their message bodies are auto-redacted after the company's retention window. 03 Tag a thread One-click chips for detention, breakdown, docs-needed, personal, plus free-text tags. · 04 Log a driver's message as an exception on the load When the newest inbound message reads as operational ("running 45 min behind", "truck kharab", "POD received"), a coloured bar appears saying what it matched, with Log on load and Not an issue. Logging writes a red/amber exception onto the load's Journey. · 05 See how long someone has waited Each row that owes a reply shows a clock chip —, — that turns red past four hours. · 06 Narrow the list A Filters button opens a popover with channel (SMS / WhatsApp / Email / App), status, assignee, tag and an unread-only checkbox. The button shows a count when filters are engaged and offers a one-click Clear, which keeps whatever was typed in the search box. 07 Group by age Rows sit under sticky headers: Today / Yesterday / Earlier this week / Earlier, each carrying the number of conversations under it. Empty buckets are dropped, and a conversation with an unreadable date sorts into Earlier rather than vanishing. · 08 See at a glance what is yours A purple You chip on every row assigned to the person reading, and — in All-Companies mode — a company badge and a faint tint of that company's brand colour on the row. ## What we haven’t built here — by design. Publishing this is the point. Unified Communications ships 36 capabilities today; these 3 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Resend a failed message | Not built | | Trip / Manifest context card | Not built | | Bulk actions on threads | Not built | ## Nearby in Command & Insight. Dashboard 22 live ↗ Analytics 25 live ↗ Reports 29 live ↗ Activity & Audit Log 32 live ↗ --- ## Payroll & Settlements — Lanexa TMS URL: https://lanexa.io/product/payroll Summary: Payroll is where a freight company works out exactly what each driver has earned for a pay period — miles run, waiting time, fuel charged back, advances an Platform / Money / Payroll & Settlements # Payroll & Settlements Payroll is where a freight company works out exactly what each driver has earned for a pay period — miles run, waiting time, fuel charged back, advances and loans — puts the numbers in front of a second person to sign off, and then records that the driver was actually paid. Book a 20-min demo See the Money pillar 47 Capabilities, all live 100% In production Money Pillar 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. AUTO ### Every payroll table records every change A database trigger writes a change record on every insert, update and delete on pay items, pay profiles, pay stubs, fuel receipts and settlement runs — independent of anything the screens do. AUTO ### Every write is permission-checked at the database, not just in the screen Pay items and settlement runs carry a trigger requiring the payroll permission for the row's own company, on insert, update and delete. Automated back-end contexts and cascading system writes are exempt., AUTO ### Approval is separation-of-duties-checked at the database The trigger fires on every settlement-run update where an approver is being stamped for the first time, and compares the acting user against the recorded creator. It also stamps the creator automatically on insert. AUTO ### Closed accounting periods are enforced at the database Every payroll write resolves its own effective date — the period end for settlement runs and stubs, the creation date for pay items, the transaction date for fuel receipts — and checks the period status. Hard-closed rejects; soft-closed all ## 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. 01 Enter fuel in litres A Gallons/Litres selector on the fuel form. Litres convert to US gallons on save, and a per-litre price is converted to a per-gallon price; the original litre figures are appended to the notes so the paper receipt still reconciles. 02 Charge fuel back to the driver automatically A "Create deduction for driver" checkbox on the fuel form (only shown once a driver is chosen). Creates a linked negative pay item for the full receipt amount. Editing the receipt later updates that deduction if it is still PENDING, and refuses to change it si 03 Catch duplicate fuel rows The review step flags any row that matches an existing receipt by vendor + transaction ID, or by the exact date + amount + vendor triple — including repeats inside the same file. Flagged rows are excluded by default and can be toggled back in. 04 Auto-deduct a whole imported batch A single checkbox in the review step creates a driver deduction for every imported row that resolved to a driver. 05 File that statement automatically Downloading from the row menu also files a copy in the Documents module against the driver, deduplicated by content. 06 Open a settlement from elsewhere A web address of the form opens that run's preview automatically. The Ledger's drill-through and the pay-item rows use it. 07 Pause, resume or close a ledger account Buttons on each ledger row. A paused account deducts nothing. 08 Create a settlement run Settlements screen → New Run. Driver plus period start and end; notes optional. Creates the run in DRAFT with all totals at zero. ## What we haven’t built here — by design. Publishing this is the point. Payroll & Settlements ships 47 capabilities today; these 6 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Jump from a settlement to its pay stub | In progress | | Pay by the hour | Not built | | Reimburse lumper fees | Not built | | Pay drop/hook, layover, tarp, hazmat premium, border crossing and an accessorial share | Not built | | Pay empty miles | Not built | | Approve settlements for the whole fleet at once | Not built | ## Nearby in Money. Billing 46 live ↗ Accounts Payable 24 live ↗ Ledger 18 live ↗ --- ## Quotes — Lanexa TMS URL: https://lanexa.io/product/quotes Summary: Quotes is where a price offer is built, priced against your own past lanes and your own cost floor, emailed to the customer as a real PDF with a link they Platform / Revenue & Movement / Quotes # Quotes Quotes is where a price offer is built, priced against your own past lanes and your own cost floor, emailed to the customer as a real PDF with a link they can accept online without an account — and, the moment they accept, turned into a booked Load automatically unless their unpaid bills say otherwise. Book a 20-min demo See the Revenue & Movement pillar 35 Capabilities, all live 100% In production Revenue & Movement Pillar 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. AUTO ### Every quote action is written to the activity feed by name Not just a generic field change — a purpose-built sentence per action: "*Name* created quote QT-…", "*Name* status → SENT quote QT-…", "*Name* emailed quote (PDF attached) to person@company.com for QT-…", "*Name* copied the public link for AUTO ### Every database write to is diffed automatically A table trigger computes exactly which fields changed, with their before and after values, and appends that to the hash-chained event log along with the real actor from the session. A no-op update writes nothing. Five noisy fields — route g AUTO ### Every status transition is stamped and historically recorded When a quote becomes Sent, Accepted, Declined or Expired the corresponding timestamp is set — and never overwritten if one already exists. A row is written to the status-history table capturing the from-status, the to-status and the actor; AUTO ### Every acceptance freezes itself The moment the acceptance timestamp is written, a trigger makes nine columns immutable. Any later change raises an error naming the link (). ## 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. 01 Decline a quote Requires choosing a reason from six: Price, No capacity, Transit time, Lost to incumbent, No response, Other. The database refuses the change without one., 02 Automatic expiry Every hour at seventeen minutes past, any Draft, Sent or Pending quote past its validity date flips to Expired with a history row. 03 Instant acceptance alert The moment a customer accepts, dispatcher and admin get an in-app notification stating whether the load booked automatically or was parked for review., 04 Apply a rate card When a pre-negotiated card matches the lane, customer, equipment, weight band and today's date, up to three suggestions appear with an Apply button that fills rate and currency — and turns the card's fuel-surcharge percentage into a real charge line. The sugge 05 Add charge lines Pick an accessorial from the company catalogue or add a fuel surcharge; give each a description, the exact triggering condition in words ("after 2h free, per ELD"), an amount, and an "if incurred" tick that makes it optional. Each line's total is simply the am 06 Get a cross-border nudge When origin and destination countries differ and no line mentions customs, brokerage or border, a purple prompt offers to add a customs and brokerage line. 07 Convert a quote to a load Asks for the pickup date (pre-filled from the quote's own target pickup), then creates a real load carrying the lane, equipment, commodity, weight, rate, currency, exchange rate, hazmat flag, estimated miles, notes, freight items and fuel surcharge, and marks 08 See the quote list Opens and sees every quote for the active company, newest first. Eight columns: quote number (with a company badge), status, customer, route, equipment, rate (with the currency printed underneath it), expiry date, and an actions button. An expiry date already ## What we haven’t built here — by design. Publishing this is the point. Quotes ships 35 capabilities today; these 6 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Revoke a public quote link | Not built | | Convert a parked acceptance | Not built | | See how many times a quote was viewed | In progress | | Put a discount on a quote | Not built | | Revise a quote into a new version | Not built | | Read a quote's status history | In progress | ## Nearby in Revenue & Movement. Loads 44 live ↗ Trip Board 40 live ↗ Load Status 36 live ↗ Interline Desk 28 live ↗ --- ## Reports — Lanexa TMS URL: https://lanexa.io/product/reports Summary: Reports is where you pull the paperwork and the numbers out of the business — twenty-one ready-made registers you can run and download, four "everything ab Platform / Command & Insight / Reports # Reports Reports is where you pull the paperwork and the numbers out of the business — twenty-one ready-made registers you can run and download, four "everything about one truck / driver / trailer / customer" pages, and a build-your-own report tool that answers a plain-English question without ever inventing a number. Book a 20-min demo See the Command & Insight pillar 29 Capabilities, all live 100% In production Command & Insight Pillar 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. AUTO ### Exports are audit-logged All twenty-one catalog reports write a row into the audit trail the instant a spreadsheet starts downloading, naming the user, the report, the row count and the filename (). Sixteen do it directly; the other five — the three IFTA reports, t AUTO ### The reminder clock ticks hourly A scheduled database job runs at twelve minutes past every hour, picks up to 200 due subscriptions, raises one alert each through the shared alerting spine, and advances the next due time (, ). The advance is computed from the previously sc AUTO ### Report-ready alerts are deduplicated for 60 minutes (), so a hiccup cannot produce a burst of identical alerts. AUTO ### The stale-trailer scan runs nightly At 06:20 every day a second job walks the live asset positions, finds every trailer whose dwell clock (or last logical event, if there is no dwell clock) is 30 or more days old, and raises an alert naming the unit, the days idle, where it i ## 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. 01 See why a report is refused Where the role cannot download, the buttons are replaced by a padlock and the line "Exporting this report needs compliance / financial export access" (). 02 Download a report as PDF Presses Download PDF on the five reports that produce one: Customer Statement, IFTA Quarterly, IFTA Audit-Armor, IFTA Filing Pack, Accident Register (,,, ). The PDF carries the company's own letterhead built once at the top of the page (). 03 Customer 360 Picks one customer; gets payment terms, credit limit, contact, a computed load count, booked / invoiced / collected / open AR / margin / days-to-pay, an aging table by bucket, on-time service, quote win rate, live open pipeline by currency, their top ten lanes 04 Export a 360's underlying rows Presses "Export loads (CSV)" (or "Export trips (CSV)" on Trailer 360). Rate, surcharge, currency and revenue columns are omitted entirely — not blanked — when the role cannot see money (,, ). 05 Narrow to one driver A driver dropdown on Load Register, Driver Settlement, Fuel Receipts and the Accident Register (). 06 Set a date range Two date boxes, pre-filled with the last 30 days when the report supports a range (, ). Each report labels its own date meaning — "Pickup date", "Issue date", "Delivery date", "Uploaded date", "Transaction date", "Event date", "Created date". 07 Run a report Presses Run; the button shows "Running…" and a preview table appears underneath showing the first 50 rows with a count line saying how many rows there are in total (, ). A report that fails raises a red toast naming the report and the error (). 08 Download a report as CSV Presses Download CSV. The file always covers every matched row, never the 50 shown on screen (). Opens cleanly in Excel including French accents (). ## What we haven’t built here — by design. Publishing this is the point. Reports ships 29 capabilities today; these 2 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Download in Excel (.xlsx) format | Not built | | Email a report on a schedule | Not built | ## Nearby in Command & Insight. Dashboard 22 live ↗ Unified Communications 36 live ↗ Analytics 25 live ↗ Activity & Audit Log 32 live ↗ --- ## Settings — Lanexa TMS URL: https://lanexa.io/product/settings Summary: Settings is the back office where the owner sets up the trucking company once — its legal name and safety numbers, its logo and invoice wording, its tax ra Platform / Platform & Control / Settings # Settings Settings is the back office where the owner sets up the trucking company once — its legal name and safety numbers, its logo and invoice wording, its tax rates and pay formulas, its customs brokers and rate agreements, who on staff can touch what, and which outside services (QuickBooks, email, PC*Miler, BorderConnect) the business is plugged into — so every other screen in the system stops asking and just knows. Book a 20-min demo See the Platform & Control pillar 37 Capabilities, all live 100% In production Platform & Control Pillar 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. AUTO ### Activity is stamped on every settings save After a successful save the page names exactly which facets moved — "company profile", "operational settings", or "company profile + operational settings" — and writes a line like "Jane Doe updated company profile + operational settings for AUTO ### A separate branding record fires only when branding actually changed The page compares the five branding entries against their pre-save values and records a branding-changed event against the company only if one of them moved — a deliberately narrower signal than the generic activity line. AUTO ### Custom-field changes write their own audit lines Creating, updating or deleting a custom field each writes a custom-field activity entry naming the user and the field. Renames are specifically noted as noteworthy because they orphan previously stored values. · · AUTO ### GL account archive and reactivate write billing audit lines , including the written archive reason, because hiding an account from new transactions is regulatory-significant. · ## 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. 01 Build rate cards Per-customer lane pricing: name, customer, origin zone, destination zone, equipment (6 types — dry van, reefer, flatbed, step deck, tanker, container), rate + currency, fuel surcharge %, min/max weight, effective and expiry dates, notes. Edit, deactivate or de 02 Set the border filing identities SCAC (US / ACE, 4 letters) and CBSA carrier code (Canada / ACI, 4 characters), auto-uppercased. The Border Desk derives every SCN, CCN, trip reference and CRN from these two codes. · 03 Add suggested starter custom fields When an entity has no custom fields, the tab offers real carrier fields one click at a time (or all at once), each with a one-line reason it earns its place — Customer PO Number, Seal Number, Temperature Setpoint, Appointment Required, Passport Expiry, FAST Ca 04 Import Loads or Customers from CSV Upload a CSV up to 10 MB, see a five-row preview with column count and a "… and N more rows" line, then import. Column names are auto-mapped. · · 05 Set operational defaults Default Currency (CAD / USD / MXN), Distance Unit (km / miles), Weight Unit (lbs / kg), Default Equipment Type, Default HOS Rules for new drivers (Canadian Federal / US FMCSA), Fuel Surcharge Rate %. 06 Maintain the accessorial charge catalog Reusable charges (detention, inside delivery, etc.) with a category, calculation type (flat / per unit / percentage), default rate, unit label and optional min/max amounts. A category filter with per-category counts sits beside the Add button. · 07 Manage customs brokers Name, broker code, contact, phone, email, address, city, province, country — plus the filing email PARS/PAPS packets go to, an after-hours phone, and the broker's public tracker web address, offered from a suggestion list of eight ready-made tracker links cove 08 Deep-link straight to a tab Adding either or to the Settings web address with a tab's name after it — for example — opens that tab and then cleans the parameter out of the address bar; an unknown name raises a "Not found" message. Used by global search and by the Border Desk's "fix this" ## What we haven’t built here — by design. Publishing this is the point. Settings ships 37 capabilities today; these 3 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Record a branding default tax rate | In progress | | Toggle automations | In progress | | Store BorderConnect credentials | In progress | ## Nearby in Platform & Control. Multi-Company 12 live ↗ --- ## Trip Board — Lanexa TMS URL: https://lanexa.io/product/trip-board Summary: The Trip Board is the dispatcher's command centre — one screen that shows every truck currently working on top, every piece of booked freight waiting below Platform / Revenue & Movement / Trip Board # Trip Board The Trip Board is the dispatcher's command centre — one screen that shows every truck currently working on top, every piece of booked freight waiting below, and lets the dispatcher build a run, put a driver and a truck on it, and tick off each stop as the day happens. Book a 20-min demo See the Revenue & Movement pillar 40 Capabilities, all live 100% In production Revenue & Movement Pillar From the Lanexa 2.0 capability register · version 2.0.37 · reviewed 2026-08-24 ## 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. 01 Look up any trip in the company Opens the All Trips panel above the Load Grid — a collapsible index of every trip the company has, with a live count on its header and columns Trip #, Status, Driver, Start, End, Revenue and Miles. Clicking a row opens that trip's execution window. It exists b 02 Edit a trip Right-click → *Edit Trip*. The form waits for the trip's current load links to load before it opens, so a save can never quietly unlink freight (,; save path ). 03 Read a load's trip context without leaving the grid Clicks a row; a panel opens underneath with four tabs — Stops, Freight, Driver Info, Equipment (; ). 04 Check border readiness Reads the Border column: a coloured chip per crossing showing the customs regime and how the one-hour rule clock is running (; per-trip variant ). 05 See every working trip at a glance Opens. The top grid lists one row per trip that is not finished or cancelled, with 19 columns: driver, truck, trailer, next event/place/city/date, last event/place/city/date, satellite position, next probill and status (, ). 06 Jump to a trip or a driver Types into the Trip # or Driver box; the first match is selected and scrolled into view (, ). 07 Copy a cell Right-click → *Copy cell* puts the displayed text on the clipboard (, ). 08 Save a named layout Names a layout and saves it; sort, hidden columns, both tabs, the split ratio, the pool query, both filter sets and the "show completed" toggle all come back next time (,; storage shape ). ## What we haven’t built here — by design. Publishing this is the point. Trip Board ships 40 capabilities today; these 2 are not built yet, and you should know that before a sales call rather than after one. | Capability | Status | | Preview the trip-shaped grid | In progress | | Land on a trip from a link | In progress | ## Nearby in Revenue & Movement. Loads 44 live ↗ Load Status 36 live ↗ Interline Desk 28 live ↗ Quotes 35 live ↗ --- ## Lanexa for 3PLs — Asset-light, customer-heavy URL: https://lanexa.io/solutions/3pl Summary: Mixed operations usually run two systems — one for owned freight, one for farmed-out — and reconcile them by hand. Here both live on the same shipment reco Who we serve / 3PLs Asset-light, customer-heavy # The loads you move and the loads you hand over, in one set of books. Mixed operations usually run two systems — one for owned freight, one for farmed-out — and reconcile them by hand. Here both live on the same shipment record, so nothing is tracked twice and nothing falls between them. ## What usually goes wrong. 01 Two systems, one P&L Owned freight in one place, brokered freight in another, and a monthly exercise to make them agree. 02 Farmed-out margin is invisible until later The cost you owe a partner arrives as an invoice long after the decision to use them was made. 03 Customers ask where their freight is And answering means a phone call to a partner who may or may not pick up. 04 Nobody is sure which entity owns what Especially once more than one operating company is involved. ## What answers it. Every item below is live in production today. ONE RECORD ### Moved or farmed out, same shipment The load stays yours commercially even when the wheels belong to a partner, and the board shows plainly which is which. BOTH SIDES ### Receivable and payable on one load What the customer owes you and what you owe the partner post to the same double-entry ledger, against the same shipment. SHARE ### Visibility without a phone call A branded tracking link your customer opens with no app and no login. ## The modules you would live in. 193 capabilities across these modules are live today. Interline Desk The Interline Desk is where you hand a load you already sold to another trucking company, watch them accept or decline the offer, send them the signed-rate paperwork, and get the bill you owe them created automatically the moment they deliver — while you stay the carrier the customer knows and invoices. 28 live Loads This is the book of every shipment the company has agreed to haul — you write the job down here when a customer books it, you put a driver and truck on it, you watch it move from pickup to delivery, and the moment it delivers the system turns it into an invoice. 44 live Customers Customers is the one book of everyone who pays you — shippers, brokers, bill-to parties and interline partners — holding their contacts, their credit limit, what they owe you right now, the paperwork you insist on before you invoice them, and the fuel-surcharge terms you agreed to, so that dispatch, billing and the border desk all quote the same firm from the same record. 45 live Billing Billing is where a delivered load turns into a bill the customer actually receives, and where the company watches, chases, corrects and banks the money that comes back. 46 live Ledger The Ledger is the company's own set of books — every invoice, customer payment, carrier bill, bill payment, driver settlement and fuel receipt writes itself into a double-entry ledger automatically, and this screen lets you read those books, prove they balance, see where cash is heading, and click any number straight back to the paperwork it came from. 18 live Multi-Company When one owner runs several trucking companies side by side, this single screen adds them up — loads, revenue, trucks, trailers and drivers, each company in its own colour — so the owner can see the whole family of businesses at a glance without ever mixing their separate sets of books. 12 live ## Multi-company roll-up exists and is the newest area of the product — its page says exactly how much of it is built. Book a 20-min demo See every capability ## Other kinds of operation. Carriers Asset-based, 10 to 200 power units ↗ Freight brokers Freight-first, ops-light ↗ Owner-operators One truck, no back office ↗ Dispatchers The person holding it together ↗ Owners Running the business ↗ Accounting & billing Where the money actually lands ↗ Drivers The one who has to actually use it ↗ --- ## Lanexa for Accounting & billing — Where the money actually lands URL: https://lanexa.io/solutions/accounting Summary: Operations enters the load. Dispatch enters it again to cross the border. Then it reaches you, and you enter it once more into accounting — which is where Who we serve / Accounting & billing Where the money actually lands # You shouldn't be rebuilding the same shipment a third time. Operations enters the load. Dispatch enters it again to cross the border. Then it reaches you, and you enter it once more into accounting — which is where the errors from the first two entries finally surface. ## A day in the job. 01 Invoices go out incomplete Missing a signed proof of delivery or a required document, then rejected by the customer and re-sent weeks later, with the cash delayed the whole time. 02 Detention never makes it onto the bill It happened, everyone remembers it happening, and nobody wrote down when the truck actually arrived. 03 Fuel tax is reconstructed at quarter-end From receipts, from memory, from a mileage figure nobody is confident in. 04 Corrections leave the books wrong Something is voided in one system and not the other, and the two only disagree by a little, which is worse. ## What answers it. Every item below is live in production today. GATE ### The invoice cannot go out incomplete Where a customer requires particular documents, the invoice cannot be created without them — the rule lives in the database, not on a sticky note. DWELL ### Detention is calculated, not remembered Dwell comes from the stop timestamps already on the trip, so the charge is documented before the conversation starts. UNPOSTS ### Voiding behaves like accounting Void a document and it unposts, along with anything it created. A paid invoice cannot be voided at all — it takes a credit memo, because money has moved. ## The modules you would live in. 204 capabilities across these modules are live today. Billing Billing is where a delivered load turns into a bill the customer actually receives, and where the company watches, chases, corrects and banks the money that comes back. 46 live Accounts Payable Accounts Payable is the screen where you enter every bill another carrier or vendor sends you, decide whether it is right, approve it, pay it, and keep the paper trail — so the money going *out* of the company is as controlled as the money coming *in*. 24 live Ledger The Ledger is the company's own set of books — every invoice, customer payment, carrier bill, bill payment, driver settlement and fuel receipt writes itself into a double-entry ledger automatically, and this screen lets you read those books, prove they balance, see where cash is heading, and click any number straight back to the paperwork it came from. 18 live Payroll & Settlements Payroll is where a freight company works out exactly what each driver has earned for a pay period — miles run, waiting time, fuel charged back, advances and loans — puts the numbers in front of a second person to sign off, and then records that the driver was actually paid. 47 live Compliance, IFTA & Safety This is where a carrier proves it is legal to be on the road — how many hours each driver has left, which licences and medicals are about to expire, what happened in every crash, and the quarterly fuel-tax return that has to be filed with the province or state that issued the plates. 40 live Reports Reports is where you pull the paperwork and the numbers out of the business — twenty-one ready-made registers you can run and download, four "everything about one truck / driver / trailer / customer" pages, and a build-your-own report tool that answers a plain-English question without ever inventing a number. 29 live ## What this role can and cannot see. | Can reach | Billing, payables, payroll, the ledger and reports, with the money figures a Dispatcher does not get. | | Cannot reach | Entering and approving are deliberately different jobs. A billing clerk creates invoices and applies cash but cannot approve or void; a settlement needs a second person to release it. | Permission is a property of the person in that company , not of the person — so the same individual can hold a different role in each company they work in. How that works . ## The books stop being a reconstruction of what operations did. Book a 20-min demo See every capability ## Other people who use it. Dispatchers The person holding it together ↗ Owners Running the business ↗ Drivers The one who has to actually use it ↗ Carriers Asset-based, 10 to 200 power units ↗ Freight brokers Freight-first, ops-light ↗ 3PLs Asset-light, customer-heavy ↗ Owner-operators One truck, no back office ↗ --- ## Lanexa for Carriers — Asset-based, 10 to 200 power units URL: https://lanexa.io/solutions/carriers Summary: A carrier running cross-border keeps six systems in step by hand. Lanexa carries one record through all eleven stages instead, which is the difference betw Who we serve / Carriers Asset-based, 10 to 200 power units # One system from the first phone call to the settled driver. A carrier running cross-border keeps six systems in step by hand. Lanexa carries one record through all eleven stages instead, which is the difference between software that records the work and software the work runs on. ## What usually goes wrong. 01 Six systems, one shipment A quote in email, the load in a spreadsheet, the assignment on a whiteboard, customs in a portal, the invoice in accounting, driver pay in another spreadsheet. 02 The border has its own deadlines And its own portal, and its own way of telling you something was rejected — usually late. 03 Driver pay is rebuilt every period From trip sheets, from memory, from a rate card that lives in someone's head. 04 Fuel tax arrives as a surprise Quarterly, reconstructed, and never quite defensible if anyone asks how the mileage was derived. ## What answers it. Every item below is live in production today. 29 LIVE ### The border is part of the load 32 eManifest capabilities, 29 of them live, including the two states most systems skip: rejected, and amended after acceptance. 4 SOURCES ### IFTA you can defend A four-source mileage engine with per-litre Canadian rates, and the sources compared side by side rather than picked for you. 2 PEOPLE ### Settlements need a second signature Pay is calculated from the trip, then held until someone other than the preparer releases the run. ## The modules you would live in. 246 capabilities across these modules are live today. Loads This is the book of every shipment the company has agreed to haul — you write the job down here when a customer books it, you put a driver and truck on it, you watch it move from pickup to delivery, and the moment it delivers the system turns it into an invoice. 44 live Trip Board The Trip Board is the dispatcher's command centre — one screen that shows every truck currently working on top, every piece of booked freight waiting below, and lets the dispatcher build a run, put a driver and a truck on it, and tick off each stop as the day happens. 40 live eManifest The eManifest module — called the Border Desk inside the product — is where a dispatcher gets a truck legally across the Canada/US border: it assembles every fact customs demands for a crossing, scores how ready that crossing is, prints the barcoded paper the driver carries, emails the customs broker their package, and runs a countdown clock so nobody arrives at the booth without an accepted filing. 29 live Billing Billing is where a delivered load turns into a bill the customer actually receives, and where the company watches, chases, corrects and banks the money that comes back. 46 live Payroll & Settlements Payroll is where a freight company works out exactly what each driver has earned for a pay period — miles run, waiting time, fuel charged back, advances and loans — puts the numbers in front of a second person to sign off, and then records that the driver was actually paid. 47 live Compliance, IFTA & Safety This is where a carrier proves it is legal to be on the road — how many hours each driver has left, which licences and medicals are about to expire, what happened in every crash, and the quarterly fuel-tax return that has to be filed with the province or state that issued the plates. 40 live ## Add a truck and the bill does not move — pricing is per person, not per power unit. Book a 20-min demo See every capability ## Other kinds of operation. Freight brokers Freight-first, ops-light ↗ 3PLs Asset-light, customer-heavy ↗ Owner-operators One truck, no back office ↗ Dispatchers The person holding it together ↗ Owners Running the business ↗ Accounting & billing Where the money actually lands ↗ Drivers The one who has to actually use it ↗ --- ## Lanexa for Dispatchers — The person holding it together URL: https://lanexa.io/solutions/dispatchers Summary: A dispatcher spends the day re-typing between a board, a customs portal, an email thread and a phone — and gets blamed for whatever falls through the gaps Who we serve / Dispatchers The person holding it together # You are the integration layer. You shouldn't have to be. A dispatcher spends the day re-typing between a board, a customs portal, an email thread and a phone — and gets blamed for whatever falls through the gaps between them. ## A day in the job. 01 The shipment gets typed three times Once from the rate confirmation, once into the border filing, once again when billing asks what happened. Each retype is a chance to transpose a number nobody catches until the invoice is queried. 02 The border is somebody else's system Separate portal, separate login, separate deadline — and if the filing is rejected, the load record has no idea. 03 Chasing drivers for paperwork The proof of delivery exists, on a phone, somewhere. Getting it into the right place is a series of texts and a manual upload. 04 Nobody can see what you can see The board lives in your head and in a spreadsheet. When you take a day off, the operation slows down. ## What answers it. Every item below is live in production today. PDF IN ### The load fills itself in Drop the broker's rate confirmation on the screen and the fields are extracted for you to check, rather than typed. SAME RECORD ### The filing comes off the load ACE and ACI are prepared, validated and barcoded from the shipment you already built. No second system, no second typing. NO APP ### Documents come back on their own Send a link; the driver photographs the missing document from their phone with no login, and it files itself against the right load. ## The modules you would live in. 213 capabilities across these modules are live today. Loads This is the book of every shipment the company has agreed to haul — you write the job down here when a customer books it, you put a driver and truck on it, you watch it move from pickup to delivery, and the moment it delivers the system turns it into an invoice. 44 live Trip Board The Trip Board is the dispatcher's command centre — one screen that shows every truck currently working on top, every piece of booked freight waiting below, and lets the dispatcher build a run, put a driver and a truck on it, and tick off each stop as the day happens. 40 live Load Status Load Status is the wall a dispatcher watches all day — every shipment in the company shown as a card in a lane, on a map, or on a driver calendar, so that moving a load from "booked" to "on the truck" to "delivered" is one drag, and the system refuses the moves that would corrupt the money behind them. 36 live eManifest The eManifest module — called the Border Desk inside the product — is where a dispatcher gets a truck legally across the Canada/US border: it assembles every fact customs demands for a crossing, scores how ready that crossing is, prints the barcoded paper the driver carries, emails the customs broker their package, and runs a countdown clock so nobody arrives at the booth without an accepted filing. 29 live Interline Desk The Interline Desk is where you hand a load you already sold to another trucking company, watch them accept or decline the offer, send them the signed-rate paperwork, and get the bill you owe them created automatically the moment they deliver — while you stay the carrier the customer knows and invoices. 28 live Unified Communications Messages is the one place where every text, WhatsApp and email between your office and a driver, customer or broker lives as a running conversation — so nobody has to ask "did anyone reply to him?" ever again. 36 live ## What this role can and cannot see. | Can reach | Loads, trips, the board, the border desk, partners and messages. | | Cannot reach | Rates and margin are hidden from the Dispatcher role by default — visibility of money is a separate permission from access to a module, on purpose. | Permission is a property of the person in that company , not of the person — so the same individual can hold a different role in each company they work in. How that works . ## The job stops being data entry and goes back to being dispatch. Book a 20-min demo See every capability ## Other people who use it. Owners Running the business ↗ Accounting & billing Where the money actually lands ↗ Drivers The one who has to actually use it ↗ Carriers Asset-based, 10 to 200 power units ↗ Freight brokers Freight-first, ops-light ↗ 3PLs Asset-light, customer-heavy ↗ Owner-operators One truck, no back office ↗ --- ## Lanexa for Drivers — The one who has to actually use it URL: https://lanexa.io/solutions/drivers Summary: Every driver-facing tool asks for one more login, one more install, one more thing to go wrong at five in the morning in a yard with no signal. Lanexa asks Who we serve / Drivers The one who has to actually use it # There is no app for your drivers to install. Every driver-facing tool asks for one more login, one more install, one more thing to go wrong at five in the morning in a yard with no signal. Lanexa asks for none of that, which is usually the objection an owner raises first. ## A day in the job. 01 Another app nobody opens Installed once during onboarding, never opened again, and quietly the source of every process that then fails. 02 Paperwork chased for weeks The proof of delivery is on a phone. Getting it filed is a series of texts and somebody re-uploading it by hand. 03 Instructions in four places A text, a call, a photo of a rate confirmation and a note taped to the dash. 04 No signal, no system The moment connectivity drops, a browser-based tool usually stops being useful at all. ## What answers it. Every item below is live in production today. WHERE THEY ARE ### Reached on the channel they already read SMS, WhatsApp and email — no install, no login, and every message anchored to the load it belongs to rather than lost in a group chat. TAP, PHOTO ### A missing document takes one link Dispatch sends a request; the driver photographs it from their phone; it lands classified and filed on the right load. No account required. OFFLINE ### It keeps working without signal Work captured in a dead zone syncs when the connection returns, rather than being lost or blocked. ## The modules you would live in. 110 capabilities across these modules are live today. Unified Communications Messages is the one place where every text, WhatsApp and email between your office and a driver, customer or broker lives as a running conversation — so nobody has to ask "did anyone reply to him?" ever again. 36 live 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. 30 live Loads This is the book of every shipment the company has agreed to haul — you write the job down here when a customer books it, you put a driver and truck on it, you watch it move from pickup to delivery, and the moment it delivers the system turns it into an invoice. 44 live ## What this role can and cannot see. | Can reach | Their own loads, the documents attached to them, and their messages. | | Cannot reach | Rates, margin, other drivers' pay and anything belonging to another company. The Driver role is deliberately narrow. | Permission is a property of the person in that company , not of the person — so the same individual can hold a different role in each company they work in. How that works . ## The honest version of this is a better sell than the usual one: they do not have to change what they already do. Book a 20-min demo See every capability ## Other people who use it. Dispatchers The person holding it together ↗ Owners Running the business ↗ Accounting & billing Where the money actually lands ↗ Carriers Asset-based, 10 to 200 power units ↗ Freight brokers Freight-first, ops-light ↗ 3PLs Asset-light, customer-heavy ↗ Owner-operators One truck, no back office ↗ --- ## Lanexa for Freight brokers — Freight-first, ops-light URL: https://lanexa.io/solutions/freight-brokers Summary: Built around the way a broker actually works, rather than a carrier system with the trucks taken out. Margin lives in the accessorials and in getting the c Who we serve / Freight brokers Freight-first, ops-light # Price it, win it, cover it, bill it — on one record. Built around the way a broker actually works, rather than a carrier system with the trucks taken out. Margin lives in the accessorials and in getting the carrier bill right, so both are handled where the load already is. ## What usually goes wrong. 01 Quotes live in email Sent as an attachment, accepted in a reply, and then typed into something else to become a load. 02 Credit exposure is discovered late Usually after the load has moved and the invoice is already aging. 03 The carrier bill is a separate chore Entered by hand, days after delivery, and occasionally not at all. 04 Documents chased across inboxes The proof of delivery exists somewhere in a thread nobody can find on the day it is needed. ## What answers it. Every item below is live in production today. NO LOGIN ### The customer accepts online Price against your own lane history, send a PDF, and the customer accepts on a link without an account — with a clear record of who accepted and when. GATE ### Credit is checked before the load moves A customer over their limit is stopped at quote-accept and again at booking, rather than discovered in the aging report. AT POD ### The carrier bill writes itself Tender to a partner with an offer clock and live margin; at proof of delivery the bill you owe them is created for you, pending someone approving it. ## The modules you would live in. 228 capabilities across these modules are live today. Quotes Quotes is where a price offer is built, priced against your own past lanes and your own cost floor, emailed to the customer as a real PDF with a link they can accept online without an account — and, the moment they accept, turned into a booked Load automatically unless their unpaid bills say otherwise. 35 live Loads This is the book of every shipment the company has agreed to haul — you write the job down here when a customer books it, you put a driver and truck on it, you watch it move from pickup to delivery, and the moment it delivers the system turns it into an invoice. 44 live Interline Desk The Interline Desk is where you hand a load you already sold to another trucking company, watch them accept or decline the offer, send them the signed-rate paperwork, and get the bill you owe them created automatically the moment they deliver — while you stay the carrier the customer knows and invoices. 28 live Customers Customers is the one book of everyone who pays you — shippers, brokers, bill-to parties and interline partners — holding their contacts, their credit limit, what they owe you right now, the paperwork you insist on before you invoice them, and the fuel-surcharge terms you agreed to, so that dispatch, billing and the border desk all quote the same firm from the same record. 45 live Billing Billing is where a delivered load turns into a bill the customer actually receives, and where the company watches, chases, corrects and banks the money that comes back. 46 live 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. 30 live ## The receivable and the payable land on the same shipment, in the same books. Book a 20-min demo See every capability ## Other kinds of operation. Carriers Asset-based, 10 to 200 power units ↗ 3PLs Asset-light, customer-heavy ↗ Owner-operators One truck, no back office ↗ Dispatchers The person holding it together ↗ Owners Running the business ↗ Accounting & billing Where the money actually lands ↗ Drivers The one who has to actually use it ↗ --- ## Lanexa for Owner-operators — One truck, no back office URL: https://lanexa.io/solutions/owner-operators Summary: A real system instead of a shoebox and a spreadsheet — and for a single truck, a free one. Lanexa Solo is on the way for exactly this. Who we serve / Owner-operators One truck, no back office # The paperwork shouldn't be waiting for you after a full day of driving. A real system instead of a shoebox and a spreadsheet — and for a single truck, a free one. Lanexa Solo is on the way for exactly this. ## What usually goes wrong. 01 The office happens at night After driving. Which is when mistakes get made and invoices do not get sent. 02 IFTA is genuinely frightening Reconstructed quarterly from a bag of receipts and a mileage figure you are not confident defending. 03 Getting paid takes chasing The invoice goes out late because the paperwork was not together, and then it ages. 04 Software is priced for fleets Per-truck pricing on one truck is all overhead and no leverage. ## What answers it. Every item below is live in production today. SNAP ### A fuel receipt files itself Photograph it and it is classified and filed against the right load, waiting for you at quarter-end instead of in a bag. LITRES ### IFTA in the units you actually buy in Per-litre Canadian rates and a four-source mileage engine, so the quarterly filing is assembled rather than reconstructed. FREE ### Solo is free when it lands Loads, documents and invoicing for a single-truck operation, without a subscription. Tell us you want it and you are first in. ## The modules you would live in. 201 capabilities across these modules are live today. Loads This is the book of every shipment the company has agreed to haul — you write the job down here when a customer books it, you put a driver and truck on it, you watch it move from pickup to delivery, and the moment it delivers the system turns it into an invoice. 44 live 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. 30 live Billing Billing is where a delivered load turns into a bill the customer actually receives, and where the company watches, chases, corrects and banks the money that comes back. 46 live Compliance, IFTA & Safety This is where a carrier proves it is legal to be on the road — how many hours each driver has left, which licences and medicals are about to expire, what happened in every crash, and the quarterly fuel-tax return that has to be filed with the province or state that issued the plates. 40 live Fleet Fleet is the one register of every truck, trailer and yard the company owns — what each unit is, where it is sitting right now, whether its plates, insurance and safety papers are still valid, and how hard it has been working. 41 live ## One truck, and the same books the fleets get. Book a 20-min demo See every capability ## Other kinds of operation. Carriers Asset-based, 10 to 200 power units ↗ Freight brokers Freight-first, ops-light ↗ 3PLs Asset-light, customer-heavy ↗ Dispatchers The person holding it together ↗ Owners Running the business ↗ Accounting & billing Where the money actually lands ↗ Drivers The one who has to actually use it ↗ --- ## Lanexa for Owners — Running the business URL: https://lanexa.io/solutions/owners Summary: Answering a simple question — what did that lane actually make — takes three tools, two people and a day. And the real answer only arrives when the quarter Who we serve / Owners Running the business # You can feel the money leaking. You just can't find where. Answering a simple question — what did that lane actually make — takes three tools, two people and a day. And the real answer only arrives when the quarter closes. ## A day in the job. 01 The numbers disagree with each other The dispatch system says one thing, the accounting package another, and reconciling them is somebody's afternoon. 02 You find out late A missed accessorial, an invoice that never went out, a driver paid on the wrong rate — all discovered at month-end, when nothing can be done about them. 03 True cost per load is guesswork Fixed costs sit in a spreadsheet. Fuel sits in receipts. Neither meets the load they belong to. 04 Growth costs more than it should Per-truck software means every truck you add raises a bill that has nothing to do with the work it creates. ## What answers it. Every item below is live in production today. SAME NUMBER ### One set of books, live Every invoice, bill, settlement and fuel receipt posts to a real double-entry ledger on its own, so the dashboard figure and the accountant's figure are the same figure, today. 360 ### Everything about one truck, on a page Pick a truck, driver, trailer or customer and see the whole picture, including true cost per mile from a per-truck fixed-cost profile. HONEST ### It tells you when the data is thin Reports say when coverage is incomplete and name the empty field, rather than printing a flattering number built on three records. ## The modules you would live in. 187 capabilities across these modules are live today. Dashboard The Dashboard is the screen a freight company opens first every morning — it pulls together, on one page, how many trucks are rolling, how much money has come in and how much is still owed, which drivers are close to running out of legal driving hours, which licences and insurance policies are about to expire, and which delivered jobs have never been billed or are missing the paperwork that gets them paid. 22 live Analytics Analytics turns the freight you already booked, billed, paid for and fuelled into seven boards of business numbers — what you earned, what you kept, whether you delivered on time, who owes you money, and where your fuel tax is heading — and every number on those boards states out loud how much of your business it was actually able to measure. 25 live Reports Reports is where you pull the paperwork and the numbers out of the business — twenty-one ready-made registers you can run and download, four "everything about one truck / driver / trailer / customer" pages, and a build-your-own report tool that answers a plain-English question without ever inventing a number. 29 live Ledger The Ledger is the company's own set of books — every invoice, customer payment, carrier bill, bill payment, driver settlement and fuel receipt writes itself into a double-entry ledger automatically, and this screen lets you read those books, prove they balance, see where cash is heading, and click any number straight back to the paperwork it came from. 18 live Billing Billing is where a delivered load turns into a bill the customer actually receives, and where the company watches, chases, corrects and banks the money that comes back. 46 live Payroll & Settlements Payroll is where a freight company works out exactly what each driver has earned for a pay period — miles run, waiting time, fuel charged back, advances and loans — puts the numbers in front of a second person to sign off, and then records that the driver was actually paid. 47 live ## What this role can and cannot see. | Can reach | Everything, across every company you run. | | Cannot reach | Nothing is hidden from an administrator — but every action is still recorded, including yours. | Permission is a property of the person in that company , not of the person — so the same individual can hold a different role in each company they work in. How that works . ## The question gets answered while it still matters. Book a 20-min demo See every capability ## Other people who use it. Dispatchers The person holding it together ↗ Accounting & billing Where the money actually lands ↗ Drivers The one who has to actually use it ↗ Carriers Asset-based, 10 to 200 power units ↗ Freight brokers Freight-first, ops-light ↗ 3PLs Asset-light, customer-heavy ↗ Owner-operators One truck, no back office ↗ --- ## Trust — Security, Roles and the Gaps | Lanexa URL: https://lanexa.io/trust Summary: How company separation is enforced, who can do what, where your data lives, and the full published list of what Lanexa has not built yet. Trust # Checkable, not promised. We are pre-launch, so there are no customer logos to show you. What there is instead is a product you can inspect: separation the database applies on every query, a permission model you can read, and a published list of everything we have not built. Security and roles Four independent layers, 127 tables with row-level security, 11 role templates and 39 permissions, including the honest weak point. What we haven't built What we have chosen not to build, by name — 108 capabilities, plus the four things left out on purpose. The capability ledger Every one of the 716 capabilities in production, with the module that owns it — and, on its own tab, what we have not built ## Built and run in Canada. Lanexa is made by Cygnik Tech, a Canadian company, from Ontario. Your data stays in Canada under Canadian privacy law, we carry our business insurance in Canada for Canadian clients in Canadian dollars, and when something needs fixing you are talking to the people who built it. --- ## Security, Roles & Where Your Data Lives | Lanexa URL: https://lanexa.io/trust/security Summary: Four independent layers, 127 tables with row-level security, 11 role templates and 39 permissions. Data hosted in Canada under PIPEDA. Including the honest weak point. Trust / Security # Four layers, not one promise. Security here is not a single mechanism you have to trust. It is four, stacked, so a failure in any one of them does not expose anything — and the one that matters most is enforced below the application, where a developer mistake cannot reach it. 01 ### Authentication Stops strangers getting in at all. Single sign-on is available, and every page reachable without logging in is bot-checked before any lookup runs. 02 ### Row-level security Stops one company seeing another data, applied by the database on all 127 tables, verified by listing the live database rather than by reading a policy. 03 ### Capabilities Stops a dispatcher opening payroll. Checked on the screen and again on the server, so hiding a button is never the only thing between someone and a money action. 04 ### A record of everything Stops anything happening without a trace. Tracked changes are written by the database itself, recording who, when, and the value before and after. ## Roles are bundles, evaluated per company. Lanexa ships eleven role templates and thirty-nine permissions. Permission is not a property of the person, it is a property of the person in that company, so the same individual can administer one carrier in a group and be read-only in another. 127 Tables, all with row-level security 11 Role templates 39 Permissions Canada Where your data lives The money desk is split on purpose. The clerk who enters an invoice or a carrier bill is not automatically the person who can approve, void or pay it, and a driver settlement needs a second person before it is released. ## The honest weak point. Not every screen is permission-gated, and that is a documented decision rather than an oversight. Money and privileged screens are gated; operational screens are open to any signed-in member of the company. Those screens are still company-scoped by the database and their writes are still permission-checked on the server, but telling the system that a particular dispatcher may not open Customers at all is not yet possible. It touches every module and was deferred to its own piece of work rather than half-done. How separation works What we haven't built --- ## What We Haven't Built | Lanexa URL: https://lanexa.io/trust/what-we-havent-built Summary: Lanexa catalogues 824 capabilities and 716 are live. Here are the 108 that are not, by name, plus the things we left out on purpose. Trust / What we haven't built # What we haven't built. 716 of our 824 catalogued capabilities are live. These 108 are not, and they are listed here by name. You should know this before a sales call rather than after one — and honestly, the 716 only mean something because this page exists. ## Left out on purpose. These are not gaps we are racing to close. They are decisions, and here is the reasoning. HOS ### Hours-of-service automation Held back deliberately. Getting hours of service wrong has real consequences for a driver and for a safety rating, and we would rather ship it when we are certain than ship it early. Logbooks are manual today. NO APP ### A driver mobile app There isn't one, and we are not apologising for it. Drivers are reached over SMS, WhatsApp and email — the channels they already read — so there is nothing to install, nothing to log into, and nothing to chase people about installing. FILING ### Electronic transmission to the border We prepare, validate, barcode and package the customs filing end to end. The transmission link itself is built and readiness-checked but not switched on, so filings still travel through your broker or portal today. SHORT ### A short integration list A dozen or so connections, not forty. We list what is connected and nothing else, and a new one appears the day it goes live rather than the day it is planned. ## The 108, by name. Grouped by module, deepest gaps first. Partial means some of it works; not built yet means none of it does. ### Analytics 25 of 37 live | Capability | Status | | Rank drivers | In progress | | Read gross margin honestly | In progress | | See which lanes actually make money | In progress | | Separate what you booked from what you billed | In progress | | See customer counts and terms | In progress | | Rank customers by revenue | In progress | | See who owes you money | In progress | | Export outstanding invoices | In progress | | Schedule this report by email | Not built | | Click a chart to filter the loads behind it | Not built | | Set your own margin thresholds | Not built | | Print or produce a PDF of a board | Not built | ### Accounts Payable 24 of 35 live | Capability | Status | | Charge tax on the bill | In progress | | Approve a bill | In progress | | Record a short pay with a reason | In progress | | Keep the vendor's paperwork with the bill | In progress | | See a friendly message when the list is empty | Not built | | Record a payment in the bill's own currency | Not built | | Undo a deleted bill | Not built | | Edit a bill's money fields after the 3-day lock | Not built | | See an aged payables report (30 / 60 / 90 days) | Not built | | Approve or pay several bills at once | Not built | | Email a remittance advice to the vendor | Not built | ### Multi-Company 12 of 23 live | Capability | Status | | Create a group | Not built | | Rename a group or set its reporting currency | Not built | | Add or remove a company from the group | Not built | | Enrol a person as a group admin or group viewer | Not built | | Set a company's brand colour or short code | Not built | | Switch between two groups | Not built | | Filter by date, quarter or year | Not built | | Click a company to drill into its loads | Not built | | Export the group view to CSV or PDF | Not built | | See group profit, margin, invoiced or outstanding money | Not built | | Refresh without reloading the page | Not built | ### Drivers 20 of 30 live | Capability | Status | | Record a communications consent | In progress | | Fill company-defined custom fields | In progress | | Filter the list by status | In progress | | Read the fleet counts strip | In progress | | See hours-of-service headroom | In progress | | Read the driver's recent loads | In progress | | Read and reply to the driver's message thread | In progress | | Delete a driver | Not built | | Set a fuel card number | Not built | | Search or sort the driver list | Not built | ### Activity & Audit Log 32 of 39 live | Capability | Status | | Filter to one team member | In progress | | Filter to one module | In progress | | Check that the chain has not been broken | In progress | | Click a feed row through to the record it describes | Not built | | Filter the feed by severity (show me only errors) | Not built | | Watch events arrive live, without refreshing | Not built | | Run the database's real tamper check from the screen | Not built | ### Quotes 35 of 41 live | Capability | Status | | Revoke a public quote link | Not built | | Convert a parked acceptance | Not built | | See how many times a quote was viewed | In progress | | Put a discount on a quote | Not built | | Revise a quote into a new version | Not built | | Read a quote's status history | In progress | ### Payroll & Settlements 47 of 53 live | Capability | Status | | Jump from a settlement to its pay stub | In progress | | Pay by the hour | Not built | | Reimburse lumper fees | Not built | | Pay drop/hook, layover, tarp, hazmat premium, border crossing and an accessorial share | Not built | | Pay empty miles | Not built | | Approve settlements for the whole fleet at once | Not built | ### Dashboard 22 of 27 live | Capability | Status | | Jump into the billing work queue from that tile | In progress | | See this week's diesel index | In progress | | Change anything | Not built | | Filter by date range | Not built | | Manually refresh the page | Not built | ### Loads 44 of 49 live | Capability | Status | | Change status directly | In progress | | Reuse a lane | In progress | | See the money on one load | In progress | | Act on many loads at once | In progress | | Delete a load | In progress | ### Fleet 41 of 46 live | Capability | Status | | Delete a truck outright | Not built | | Filter or count on the Yards tab | Not built | | Un-retire a truck, or restore a deleted trailer or yard | Not built | | Set a truck's odometer from telematics | Not built | | Get warned before a plate, insurance or safety date expires | In progress | ### Customers 45 of 50 live | Capability | Status | | Set a customer-level payment-term override | Not built | | Set per-customer detention free hours and hourly rate | Not built | | Assign party roles (bill-to, customs broker, shipper, consignee…) | Not built | | Set a customer's default customs broker | Not built | ### Ledger 18 of 22 live | Capability | Status | | Edit the ledger by hand | Not built | | Post a manual adjusting journal entry | Not built | | Read a monthly Profit & Loss statement | Not built | | Push the postings to QuickBooks | Not built | ### eManifest 29 of 32 live | Capability | Status | | Deep link into a crossing | In progress | | Add a load to an existing crossing | Not built | | Transmit the filing electronically | Not built | ### Unified Communications 36 of 39 live | Capability | Status | | Resend a failed message | Not built | | Trip / Manifest context card | Not built | | Bulk actions on threads | Not built | ### Documents 30 of 33 live | Capability | Status | | AI classification of inbound documents | Not built | | Document version chains | In progress | | Retention and archiving | Not built | ### Settings 37 of 41 live | Capability | Status | | Record a branding default tax rate | In progress | | Toggle automations | In progress | | Store BorderConnect credentials | In progress | ### Trip Board 40 of 42 live | Capability | Status | | Preview the trip-shaped grid | In progress | | Land on a trip from a link | In progress | ### Compliance, IFTA & Safety 40 of 42 live | Capability | Status | | PSP reports, MVR checks, drug and alcohol programme tracking, DOT inspection history | Not built | | Electronic filing of the IFTA return | Not built | ### Reports 29 of 31 live | Capability | Status | | Download in Excel (.xlsx) format | Not built | | Email a report on a schedule | Not built | ### Interline Desk 28 of 29 live | Capability | Status | | Tender straight from a partner row | In progress | ### Billing 46 of 47 live | Capability | Status | | Edit a frozen invoice with a reason | Not built | ## Why publish this at all. A capability list containing only good news gets one claim disproved in a demo, and then nothing else in it is believed either. Publishing the gaps is what makes the rest checkable — and if you find something here that you actually need, that is a better conversation than discovering it in week three of an implementation. See the 716 live capabilities Ask us about one --- ## Why Lanexa — Four Things That Are Hard to Copy URL: https://lanexa.io/why Summary: Cross-border built into the load, a real double-entry ledger inside the TMS, AI that cannot invent a number, and company separation the database applies on every query. Why Lanexa # Four things that are hard to copy. Plenty of software can show you a load list. These four are unusual in this market, and each one is checkable rather than asserted — so each page below also says where the claim stops. 01 The border desk is inside the load Cross-border is not an add-on module bought later. It is how the product was built, which for a carrier running into the United States is the difference between one system and three. 02 It doesn't export to accounting. It is accounting Every invoice, bill, settlement and fuel receipt posts double-entry lines on its own. Void a document and it unposts, along with everything it created. 03 AI that cannot invent a number It reads your documents and it understands your question. It never does the arithmetic, because a governed engine does that every time. 04 One company cannot reach another's data The separation between companies is applied by the database on every single query, not by the application remembering to ask correctly. ## And one habit. We publish the capability ledger in full — every one of the 716 that are live — and, on its own page, what we have chosen not to build. Nobody in this category does that, because it requires both an unusually complete product and an unusual willingness to be checked. Open the capability ledger What we haven't built --- ## AI that can't invent a number — Why Lanexa URL: https://lanexa.io/why/ai-that-cannot-invent-a-number Summary: It reads your documents and it understands your question. It never does the arithmetic, because a governed engine does that every time. Why Lanexa / AI that can't invent a number # AI that cannot invent a number. It reads your documents and it understands your question. It never does the arithmetic, because a governed engine does that every time. ## The usual arrangement. Letting a model answer questions directly against a database produces fast, confident, subtly different answers to the same question. Two people ask it slightly differently and get two numbers, both of which look authoritative, and neither of which anyone can check. ## What is actually there. DEFINES ### The assistant writes the question, not the answer Ask something in plain English and the model can only produce a report definition: the same subject, grouping, measures and filters a person would have chosen by hand. Then it stops. COMPUTES ### A governed engine does the maths Every figure is calculated by the product's own reporting engine, the same code path as a report built by hand. A mistake shows up as a visibly wrong question, never as a silently wrong number. STRIPPED ### Money removed for those who shouldn't see it Rate and margin fields are stripped for users without rate visibility, applied after the model has spoken so it holds even if the model ignores its instructions. NO KEY ### The product holds no AI vendor key Not one, of any kind. All AI features call a separate gateway, so the product could be inspected end to end and contain no AI credential to steal or run up a bill on. ## What it means on a Tuesday. Someone asks what a lane made last quarter. They get a real report, built by the same engine that builds every other report, and they can see the definition it used. If the question was wrong, the definition looks wrong on screen, which is the failure you want rather than a plausible number that quietly informs a pricing decision. ## Where this claim stops. The AI features depend on an external gateway being configured and reachable. If it is not set up, document reading, document classification and plain-English questions are simply unavailable, and nothing else in the product depends on them. No core operational function stops working. ## See it in the product. Loads 44 live ↗ Documents 30 live ↗ Reports 29 live ↗ Analytics 25 live ↗ ## The other three. The border is part of the load The border desk is inside the load ↗ The books are inside, not exported It doesn't export to accounting. It is accounting ↗ Separation you can verify One company cannot reach another's data ↗ --- ## The border is part of the load — Why Lanexa URL: https://lanexa.io/why/cross-border-native Summary: Cross-border is not an add-on module bought later. It is how the product was built, which for a carrier running into the United States is the difference be Why Lanexa / The border is part of the load # The border desk is inside the load. Cross-border is not an add-on module bought later. It is how the product was built, which for a carrier running into the United States is the difference between one system and three. ## The usual arrangement. In most arrangements the border lives somewhere else: a customs portal, a broker's inbox, a second piece of software with its own logins and its own deadlines. The shipment gets typed a second time to cross, and the two records drift apart from that moment on. ## What is actually there. ACE + ACI ### Both directions, in-app United States-bound and Canada-bound filings are prepared, validated and packaged from the load record you already have, rather than rebuilt in a separate tool. PARS / PAPS ### Barcodes generated for you Auto-numbered, linked to the shipment, and printed onto the paperwork instead of hand-written onto it. 7 STATES ### Including the two nobody builds for The filing lifecycle mirrors the authorities' own process, including rejection and amendment after acceptance. Real crossings have those days; most software pretends they do not. LIVE ### Wait times where you are crossing Canada Border Services Agency and US Customs and Border Protection wait times, read directly, inside the load rather than in another browser tab. ## What it means on a Tuesday. A dispatcher builds the load once. The filing is assembled from it, the barcodes come off the same record, the broker packet is generated rather than re-keyed, and if the filing is rejected the load knows about it. Nobody opens a second system, and nothing is typed twice to get a truck across. ## Where this claim stops. Lanexa prepares, validates, barcodes and packages the filing end to end. The electronic transmission link is built and readiness-checked, but it is not switched on yet, so today the finished filing travels through your customs broker or portal exactly as it does now. We will say the day that changes. Better you read it here than discover it on a call. ## See it in the product. eManifest 29 live ↗ Documents 30 live ↗ Compliance, IFTA & Safety 40 live ↗ ## The other three. The books are inside, not exported It doesn't export to accounting. It is accounting ↗ AI that can't invent a number AI that cannot invent a number ↗ Separation you can verify One company cannot reach another's data ↗ --- ## The books are inside, not exported — Why Lanexa URL: https://lanexa.io/why/real-general-ledger Summary: Every invoice, bill, settlement and fuel receipt posts double-entry lines on its own. Void a document and it unposts, along with everything it created. Why Lanexa / The books are inside, not exported # It doesn't export to accounting. It is accounting. Every invoice, bill, settlement and fuel receipt posts double-entry lines on its own. Void a document and it unposts, along with everything it created. ## The usual arrangement. The usual arrangement is a dispatch system that produces numbers and an accounting package that receives them, with a person in between reconciling the two. The gap between them is where a missed accessorial or an invoice that never went out lives, and it is only ever found at quarter-end. ## What is actually there. POSTS ### Automatically, from the source Billing, Accounts Payable, Payroll and fuel receipts all post into the ledger. Nobody journals it afterwards, so the books cannot fall behind the operation. VOID ### Corrections behave like accounting Voiding a document unposts it and its children. A paid invoice cannot be voided at all, because money has moved, so it takes a credit memo instead. History is never rewritten. CHECKS ### Continuous tie-outs The ledger runs its own reconciliation checks, so drift is surfaced by the system rather than discovered by your accountant. QBO ### Your bookkeeper keeps their tools It still syncs to QuickBooks Online, in Canadian and US dollars, through a dedicated sync centre with an error queue. This replaces the re-typing, not the accountant. ## What it means on a Tuesday. A load is delivered, the proof of delivery lands, the invoice is raised from the load, and the accounting entry exists before anyone has opened a spreadsheet. When the driver's settlement runs, it posts too. The number on the dashboard and the number in the books are the same number, today, not in April. ## Where this claim stops. This is a general ledger built for a trucking company, not a replacement for your accountant or your tax filing. It produces books you can read and reconcile. It does not file your return, and it does not remove the need for someone qualified to look at them. ## See it in the product. Ledger 18 live ↗ Billing 46 live ↗ Accounts Payable 24 live ↗ Payroll & Settlements 47 live ↗ ## The other three. The border is part of the load The border desk is inside the load ↗ AI that can't invent a number AI that cannot invent a number ↗ Separation you can verify One company cannot reach another's data ↗ --- ## Separation you can verify — Why Lanexa URL: https://lanexa.io/why/your-data-stays-separate Summary: The separation between companies is applied by the database on every single query, not by the application remembering to ask correctly. Why Lanexa / Separation you can verify # One company cannot reach another's data. The separation between companies is applied by the database on every single query, not by the application remembering to ask correctly. ## The usual arrangement. Most multi-tenant software filters by company in application code. That works right up until one query somewhere forgets its filter, and the failure is silent: the data was always reachable, it just was not asked for. ## What is actually there. 127 / 127 ### Every table, without exception All 127 tables have row-level security enabled, verified by listing the live database rather than by reading a policy document. PER COMPANY ### Permission belongs to the person in that company The same person can be a full administrator of one carrier and read-only in another. Capabilities are evaluated for the company they are working in, not attached to the person. 11 / 39 ### Eleven role templates, thirty-nine permissions The money desk is split on purpose: the clerk who enters an invoice or a carrier bill is not automatically the person who can approve, void or pay it. SEALED ### A history that would show tampering Tracked changes are written by the database itself, recording who, when, and the value before and after, with each entry sealed to the one before it. ## What it means on a Tuesday. A holding group runs several carriers on one system. A dispatcher at one of them opens a load list and sees their own company's loads, because the other company's rows are not reachable from that session at all. If a developer wrote a query that forgot to filter, it would return nothing rather than everything. ## Where this claim stops. Not every screen is permission-gated, and that is a documented decision rather than an oversight. Money and privileged screens are gated; operational screens are open to any signed-in member of the company. Their rows are still company-scoped by the database and their writes are still permission-checked on the server, but telling the system that a particular dispatcher may not open Customers at all is not yet possible. ## See it in the product. Settings 37 live ↗ Activity & Audit Log 32 live ↗ Multi-Company 12 live ↗ ## The other three. The border is part of the load The border desk is inside the load ↗ The books are inside, not exported It doesn't export to accounting. It is accounting ↗ AI that can't invent a number AI that cannot invent a number ↗