The answer was never the job.

working balance = statement balance139 of 142 cleared automatically · 3 flagged · representative month

Any AI can tell you about your books. LedgerLock automates bank reconciliation inside Viewpoint Vista: every bank line matched to its Vista entry and cleared in CM Clear Entries, on your approval, with an audit record for every action.

CFMA Member 2026Zero Data Retention
“We live and die by LedgerLock. It’s how we scale operations without scaling the close.”
Tre Leoni, CFO · WPM Construction Services
A civil contractor running Vista. In production since 2025, renewed for year two.
The problem

Your controller spends a week a month on what an agent does in a day.

None of it is judgment. It is ticking boxes and re-keying numbers, slow work beneath the people doing it. Here is what one close actually costs.

Timesheet: month-end close
PERIOD 05/01 – 05/31/2026 · CONTROLLER
Hours
  • Tick 142 bank lines in CM Clear Entries14.0
  • Match AP invoices to POs by hand9.5
  • Chase missing PO numbers3.5
  • Re-key reference numbers4.0
  • Trace GL variances5.0
  • Hunt duplicate payments2.5
  • Reconcile card feeds1.5
One close40.0 hrs
× 12 closes a year480 hrs
× $150 fully loaded$72,000
By hand$72,000

One controller’s year, spent on the sheet above.

With LedgerLockMinutes

What the same month-end close takes now. One controller covers what used to take two.

How it works

It reads, reasons, and asks before it acts.

  1. 01
    Reads

    Queries Vista in real time. No export step, and no copy of your books.

  2. 02
    Reasons

    Works through the AP, GL, and bank rec logic the way your team would.

  3. 03
    Asks

    Surfaces the decision and waits for your call before it touches the books.

  4. 04
    Acts

    Posts the confirmed result back to Vista and renders the full audit trail. The loop closes in your books.

In production

The Bank Rec Agent runs this loop today.

It matches every bank and card line to its Vista entry and clears on your approval.

The AP and GL Agents are next on the roadmap.

User

Reconcile the May Chase operating account against Vista.

Agent
CHASE OPERATING ····4417 · STATEMENT 05/01 – 05/31/2026 · 142 LINES
Southern Aggregate Co.AP chk 10442‒48,250.00
Progress billing #14AR receipt 5567+318,400.00
Ferguson EnterprisesAP EFT 8831‒12,180.50
Sunbelt RentalsAP chk 10446‒6,180.00
Martin MariettaAP EFT 8836‒24,310.75
Herc RentalsAP chk 10467‒4,880.00
United RentalsAP chk 10449‒11,840.00
Fastenal CompanyAP EFT 8834‒2,412.90
Core & MainAP chk 10451‒7,925.40
Bank service chargeCM JE 2231‒85.00
Graybar ElectricAP EFT 8838‒3,304.10
PCT Trucking LLCno Vista match‒1,200.00
139 of 142 cleared · working balance = statement balance

Three items have no Vista entry. Flag them to the reviewer group?

Cleared state writes to CM Clear Entries on approval · illustrative
Vista specialization

We only build for Vista. Because Vista is hard enough.

Built for how Vista actually works: why reviewer groups exist, how a bank rec falls apart in week one of close. It is intelligence built on Vista, not Vista with a chatbot on top.

Vista access, as shipped
Reads
GL accounts, balances, and detail · CM bank accounts, statements, and unreconciled items · every company in your instance
Writes
CM Clear Entries and batches, only on your approval
ERP
  • Viewpoint Vista

the only one, on purpose

Bank feeds
  • Chase
  • Bank of America
  • Wells Fargo
  • Truist

+12,000 banks

Cards
  • Amex
  • Visa
  • Mastercard

One connection, over Model Context Protocol: scoped tools, documented end to end for your IT review.

Data powered byPlaid
Security & audit

Your books stay in Vista. We never store them.

Zero retention, and every action runs on your approval. The agent leaves a record a person never does, so you will never have to tell an auditor you don’t know what it did.

When a controller clears it

A tick in a box. That is the whole record. Why it was cleared, or whether anyone was sure, none of it survives the close.

When the agent clears itone line item
Timestamp
2026-05-27 09:14:22 CT
Action
Matched bank line → cleared
Vendor
Southern Aggregate Co.
Amount
$48,250.00
Vista entry
AP chk 10442
Matched on
amount + vendor + check number
Confidence
exact
Approved by
Controller
Written to
CM Clear Entries
Audit ref
LL-2026-05-27-0914

Illustrative example: every match, flag, and post, export-ready.

What this means for you

Zero data residency risk, and a cleaner audit trail than the close it replaces. Your auditor never asks who LedgerLock is.

When LedgerLock is the right call.

You run Viewpoint Vista.

Every agent is built for Vista specifically. If Vista is your ERP, nothing on the market goes this deep.

You close monthly and the books matter.

LedgerLock pays for itself in controller hours the first month if your team is reconciling by hand today.

You want Vista to stay the system of record.

The agents read and act inside your system. Your data never leaves.

And when LedgerLock is not for you.

You run a different ERP.

There are great tools for QuickBooks, Sage, and Foundation contractors.

Your close already runs smoothly.

LedgerLock pays back only when your team is reconciling by hand today.

You need reporting and BI on Vista.

That is a different category of tool.

Beta program

Beta Partners shape the next agents we build.

LedgerLock is in production at one Vista general contractor. We are opening five Beta Partner seats before general release: priority input on the workflow roadmap, locked-in launch pricing, and a direct line to the founder.

A note from the founder

I have watched controllers spend nights and weekends doing work that should not exist. LedgerLock is the agent I wanted to give them. Built for Vista, because Vista is what most of you actually run.

Mark Rodriguez, Founder · Austin, TX