Skip to main content

Platform & security

AI you can actually check.

Every GreenBar tool runs on the same foundation: it shows its reasoning for every suggestion, learns from your corrections so it gets better the more you use it, and won't take a step that needs judgment until a person signs off. And every step is recorded in one audit trail you can hand to a reviewer: what the AI did, and who approved it. No black boxes, and your bank and ledger files never leave your computer.

Where the data sits

One architecture: your machine.

GreenBar tools run entirely on your computer. There's no GreenBar server for that data to go to. Clearing works this way today, and AP Pay is being built the same way. The bank and ledger files you import never cross that line.

In Clearing, optional team sync on Pro and Firm runs between you and a server your firm hosts, and never routes through GreenBar. Both diagrams below are the same claim from two angles: where your data goes relative to everyone else's tool, and exactly what crosses the line inside your own install.

LOCAL-FIRST TOOLSYour computerbooks, matching, the learningNo GreenBar server. No shared model. Nothing pooled.TYPICAL CLOUD AI TOOLYour client booksbank + ERP exportsVendor’s serversyour data, their diskShared modeltrained across every firmother firmsSame grid, same scale. Everything Clearing and the local-first suite do happens in the first column.

Clearing and the local-first suite: what crosses the line

Everything below the dashed line runs on your machine. The one connection you can turn on is optional team sync on Pro and Firm, to a server your firm hosts, and it never carries client files or transaction rows.

Optional connection · only if you turn it on

Team sync on Pro and Firm · a server your firm hosts

Your bank and ledger files stay below this line

Your machine

Your data

Bank + accounting files, on your computer

Local AI engine

Does the transactional work

You sign off

A person approves before it posts

None of your financial data from Clearing is sent to GreenBar. When a license key is saved, Clearing checks that key with greenbarsystems.com and checks for an update. Both calls send the key only, never your books. If its built-in spreadsheet reader ever fails to load, Clearing downloads a fresh copy (SheetJS) from a public CDN, and that download carries no file data. Every other outbound connection stays off until you turn it on: optional team sync on Pro and Firm, to a server your firm hosts.

Clearing works from files you import. It does not connect to your bank out of the box. Live two-way QuickBooks Online and Xero sync is not shipped; file import works today.

AP Pay is being built the same way. Join the waitlist to hear when it ships.

Built for audit

An audit trail that covers the AI, too.

This is what makes everything else provable. Every entry carries both halves of the decision: what the software proposed, with its confidence and the signals behind it, and the named person who accepted or changed it. An auditor reads separation of duties off a single line, without joining two records.

Once you sign off, the period is sealed; change anything afterward and it shows. Most AI tools cannot tell an auditor what the AI actually did. GreenBar can. Clearing ships this first, and it is the model for the whole suite.

  • What the AI did, with its reasoning — not just the result.
  • Who reviewed and decided each item.
  • The named preparer and reviewer sign-off that finalized the work.
  • A tamper-evident record: sealed at sign-off, exportable straight to your auditors.
Download a sample audit trail (PDF) ↗

Demonstration data. Clearing ships this audit trail first.

Ledger entry · 1 of 412

ACH 04/18 · SYSCO FOODS 8841

$1,284.60

Proposed by the software

MatchINV-20412
Confidence94%
Signalsamount · date · vendor
PatternP-118 · 6 prior closes
At30 Apr 09:12

Approved by a person

DecisionAccepted
Changed—
PreparerR. Moore
ReviewerJ. Alvarez
At30 Apr 14:07

Sealed at period close, 30 Apr 17:22. Any later change shows.

Demonstration data. One entry, both halves on the same line.

Gets better every month

Every tool learns how you work.

GreenBar's engine learns from your own corrections: the match you fixed, the vendor you re-coded, the exception you cleared. Next time it already knows, so it proposes more and asks you less. It learns per account and per client.

  • Learns from your corrections: fix something once and it sticks for next time.
  • Per account and per client, so one messy client's quirks never bleed into another's.
  • Every suggestion carries a confidence score. The sure things move fast; only real judgment calls reach you.
  • Never a shared model — your patterns stay on your machine.

Illustrative example.

Why, in plain English

Every AI action shows its work

No GreenBar tool asks you to trust a result you can't check. Whatever the job (clearing, payables, data, forecasting), when it flags something or proposes a change, it shows why, how sure it is, and exactly what it's basing that on.

  • When something's flagged, you see why — and the exact figures behind it.
  • Match suggestions show how sure GreenBar is and which details lined up.
  • Every decision is saved to a complete history you can export.

Example from Clearing · why a transaction was flagged

Tech Solutions · WIRE-55 — $5,000.00

Why flaggedAmounts don't match
How sure62%
What we sawYour records show $5,000; bank cleared $4,950
SuggestedCheck the $50 difference

You decide. Every tool only surfaces and explains; it never acts on its own. Same four lines, whatever the job.