KODA · Aljex to QuickBooks Automation Plan
KODA · Financial Operations Brief

Aljex to QuickBooks
Automation Plan

Turning revenue that waits on manual work into a clean, automated system of record, with an AI layer that checks the books, flags problems, and drafts routine work for Dave to approve.

Status
Proposed
Phase
Foundation
Prepared for
Dave
System owner
Dave
How it runs today
Revenue waits on the keyboard

Every step after a load delivers runs through Dave: invoices, rate cons, carrier and customer emails, bank uploads.

How it will run
Dave becomes the controller

Aljex generates the paperwork, data syncs into QuickBooks, and Dave approves payments and handles exceptions only.

Prepared for Dave · Finance and Ownership·by Chris Parker · KODA Co.
Field 01

The Short Version

The core idea

Today, revenue waits on manual work. A trucker delivers a load, and every step after that runs through Dave's keyboard: creating the invoice, processing the rate confirmation, emailing the carrier, emailing the customer, and uploading everything into the TAB bank portal for payment.

Almost all of that typing can be eliminated. Aljex, the TMS the company already pays for, can generate invoices and rate confirmations automatically and export financial data directly into QuickBooks Online. QuickBooks then becomes the clean, automated system of record, with an AI layer that checks the books, flags problems, and drafts routine work for Dave to approve. Dave stops being the typist and becomes the controller. Nobody's job goes away. The job gets better.

How it runs today

  • POD arrives by email and sits in an inbox until processed
  • Dave hand-builds each customer invoice
  • Dave processes each rate confirmation manually
  • Dave emails carriers their pay, one by one
  • Dave emails customers to request payment
  • Dave uploads everything into the TAB bank portal
  • QuickBooks setup stalled after two years of manual effort
KODA · Aljex to QuickBooks Automation Plan · Dave LogisticsFoundation Phase · page 2
Field 02

The Architecture

Three layers, each doing one job. The bank stays exactly where it is: TAB fronts the money and settles the payments. What changes is that no human retypes data between systems.

01Operations

Aljex TMS

The load record is the source of truth. POD capture triggers invoice generation, rate confirmations auto-send, and carrier settlement runs from the platform instead of from an inbox.

02Books

QuickBooks Online

Aljex's native export maps the chart of accounts and moves customers, vendors, invoices, AP, and AR into QuickBooks automatically. The TAB bank feed reconciles what settles. No more uploads.

03Intelligence

AI Review, Human Approval

Claude connects to QuickBooks through Intuit's official MCP server. It audits carrier invoices against rate cons, flags duplicates and anomalies, drafts collections follow-ups, and produces a Monday cash report. Every action that moves money routes to Dave.

Why it holds together

Operations feeds the books, the books feed the intelligence layer, and the intelligence layer feeds Dave. Money still settles through the same banking rails at TAB. The only thing removed is the manual re-typing between each step.

KODA · Aljex to QuickBooks Automation Plan · Dave LogisticsFoundation Phase · page 3
Field 03

The Route

Phased like a dispatch: no stop begins until the previous one clears. The current process keeps running untouched until the new system proves itself alongside it.

Stop 1 · Keys & Cleanup

Weeks 1 to 2

Get access to everything and take an honest inventory of the QuickBooks account before connecting anything to it.

  • Email the Aljex rep: activate the QuickBooks Online export, get Data Sync documentation, and request Aljex Live API credentials. Confirm plan tier and any integration fees.
  • KODA registers the Intuit developer app that powers the AI layer.
  • Audit the QBO account: chart of accounts, reconciliation status, duplicate records. Set a clean cutover date at a month-end rather than repairing two years of history.
  • Security housekeeping: MFA on every Intuit login, tighten user roles, revoke stale third-party app connections.
Gate to proceedAljex access confirmed. QBO cutover date agreed.

Stop 2 · Build in Sandbox

Weeks 2 to 3

Nothing touches the real books yet. The MCP server connects to a QuickBooks sandbox company first, where reads, writes, and token handling get proven safely.

  • Stand up Intuit's official QuickBooks MCP server locally with Claude Code.
  • Connect the Aljex data flow: native QBO export as the primary path, Data Sync or scheduled CSV exports as the fallback.
  • Verify field mapping: customers, vendors, invoices, AP, AR, and carrier factor remit-to details.
Gate to proceedA completed load in Aljex appears correctly in sandbox QuickBooks with zero manual entry.
KODA · Aljex to QuickBooks Automation Plan · Dave LogisticsFoundation Phase · page 4
Field 03 · continued

The Route

Stop 3 · Parallel Run

Weeks 3 to 6

Dave keeps doing his current process exactly as-is. The automated pipeline runs alongside it against production, in read-plus-draft mode. Every week produces a comparison report: what the automation created versus what Dave created, with every mismatch explained. This is where trust gets earned.

  • Production connection goes live read-only first; delete permissions stay disabled permanently.
  • Weekly variance review, run by Dave.
Gate to proceedTwo consecutive clean weeks with zero unexplained variances.

Stop 4 · Cutover

Week 6+

Manual entry stops. The pipeline becomes primary. Dave's role formally shifts to approvals, exceptions, and review, with a written runbook so the system is genuinely his to operate.

  • All payment approvals route to Dave. All exception flags route to Dave.
  • Monday cash report goes live for ownership.

Future Stops · Parked, Not Forgotten

Later phases

Deliberately tabled until the foundation runs clean. See Field 07.

KODA · Aljex to QuickBooks Automation Plan · Dave LogisticsFoundation Phase · page 5
Field 04

The People Side

Dave is the system owner

Nothing in this architecture works without a human owner. Automation handles the typing; Dave handles judgment. He is the approver of every payment, the resolver of every flagged mismatch, the manager of the TAB and factoring relationships, and the person who reads what the system reports and decides what it means. His role moves up, from data entry toward controller.

That sentence is both the org chart and the security model: all payments route to Dave, all exceptions route to Dave. This project is Dave improving the financial operation of the company, and it is his to run.

The current bookkeeping consultant

Two years of slow progress on the QuickBooks setup is not a character problem. It is what happens when someone is asked to do a systems integration job with bookkeeping tools. Hand-configuring QBO without connecting it to the TMS turns everything into manual uploads forever, and no amount of effort fixes that.

Recommended handling: keep it generous and specific. Thank her for the groundwork, and be clear the project is changing shape from manual setup to systems integration, which is a different specialty. If she is strong at bookkeeping review, there may be a defined role in the parallel-run phase checking the automation's output. If not, a warm, clean handoff protects the relationship and the company's reputation. What should not continue is paying for manual configuration of a system that is about to be automated.

KODA · Aljex to QuickBooks Automation Plan · Dave LogisticsFoundation Phase · page 6
Field 05

What Ownership Should Understand

This pulls cash forward

Invoices that wait on an inbox delay revenue on every load. When the POD triggers same-day invoicing, days-sales-outstanding drops. Track POD-to-invoice time before and after; that number is the headline of this project.

You already pay for most of this

Aljex invoicing, rate confirmations, and the QuickBooks export are largely existing platform capabilities that were never fully activated. The main new costs are activation fees, if any, and the integration build.

TAB stays put

TAB fronts the money and settles payments, and that does not change. What gets removed is the manual uploading between systems, not the banking relationship.

Nobody is replaced

Dave runs this system. The automation removes typing, not judgment. Errors get caught by cross-checks that do not exist today, which means the books get more accurate, not less supervised.

Controls get stronger

Approval gates, permission tiers, and audit trails replace a process that currently depends on one person typing everything correctly. See the security field below.

Visibility improves

A Monday morning cash report replaces "hey Dave, where are we at": cash position, money in this week, money out, aging, and anything flagged. Five minutes of reading.

KODA · Aljex to QuickBooks Automation Plan · Dave LogisticsFoundation Phase · page 7
Field 06

Security

The honest assessment: moving payment operations from the bank portal to QuickBooks is not inherently riskier, but the risk changes shape. Bank portals come with dual authorization and hard ACH limits. QuickBooks and Intuit provide bank-grade infrastructure used by millions of businesses, and payments still settle through the same banking rails at TAB. The real risk lives in access management, so this plan rebuilds every bank-side control inside the new stack and keeps the bank-side guardrails running anyway.
  1. MFA mandatory on every Intuit login. No exceptions, no shared logins.
  2. Role-based permissions in QBO. Only Dave approves payments. Data-entry and review roles cannot move money.
  3. Approval workflows on bills above a set threshold, recreating the dual authorization the bank portal provides today.
  4. Bank guardrails stay on. ACH limits, payment alerts, and positive pay remain active at TAB as a second net.
  5. AI access is fenced. The Claude and MCP layer starts read-only. Delete permissions stay disabled permanently. The AI analyzes, drafts, and flags; only Dave approves anything that moves money.
  6. Factoring is protected. Factor payments through TAB stay exactly as they run today and migrate last, only after remit-to data is verified, because misdirecting a factored payment can mean paying twice.
  7. Vendor details verified by voice. Any new or changed payment details get confirmed by phone at a known number before the first payment, then locked.
  8. Audit trail on everything. Every automated action is logged and reviewable, which is more oversight than the current manual process has.
Configured this way, the automated process is more secure than today's, because right now accuracy depends on one person manually typing into a portal with no system cross-checking the work.
KODA · Aljex to QuickBooks Automation Plan · Dave LogisticsFoundation Phase · page 8
Field 07

Parked for Future Phases

Tabled deliberately · revisit after cutover

  • CanadaCanadian carrier payments (roughly 5 to 10 checks monthly) stay with TAB as-is. TAB is already pushing Canadian recipients toward ACH; the blocker is on their end, not ours. Melio or BILL remain documented fallbacks if volume grows or TAB cannot go electronic.
  • FactoringFactor payment migration into QBO happens only after the standard AR/AP flow runs clean for a month or more.
  • IntelAdvanced intelligence layer: rate con audit before payment release, duplicate and anomaly detection, automated AR collections sequencing, and cash flow forecasting.
  • DocsPOD capture upgrades via the Aljex inbound document portal or MacroPoint POD, removing the email inbox from the trigger entirely.
KODA Co. · AI Automation & Marketing

The foundation first. Everything else waits its turn.

Nobody's job goes away and the bank does not move. Aljex generates the paperwork, QuickBooks becomes the clean system of record, and the AI layer checks the work. Dave stops being the typist and becomes the controller. That is the whole plan, and it is his to run.

KODA · Aljex to QuickBooks Automation Plan · Dave LogisticsFoundation Phase · v1 · page 9