how aleq learns · TAMi

Aleq learns how your team codes the books — then does the routine work itself.

TAMi is the part of Aleq that learns from your team's own decisions. Once it has coded the same kind of transaction your way enough times, it starts posting those itself — and holds anything outside the pattern for you to review. Every entry it posts shows its support and can be reversed in one click.

learns your coding · posts the routine · holds the exceptions · shows its work
Aleq · learning to match the banklive
1 · watched412 Stripe deposits

same bank source, same memo, same clearing account

2 · learnedCode to Stripe Clearing

your team coded it the same way 412 times, never reversed

3 · took overPosts these itself now

routine deposits only, inside the limits you set

4 · this month410 posted, 2 held

$0.00 variance · the 2 over your limit wait for you

This isn't a chatbot answer. It's a posting rule — the support behind it, your limits around it, and one-click reversal.
how it works

It won't automate anything until it has proven it on your books.

It starts by watching your team code transactions. It only takes a task over after you've approved the same treatment enough times — and it still holds the judgment calls.

step 1 · it watches

It watches how your team codes each transaction.

Stripe deposit+$142,400
Where does your team code Stripe deposits?
Stripe Clearing account
step 2 · it learns the rule

Enough identical approvals become a rule.

Stripe deposits → Stripe Clearing
100%
coded the same way 412 times · 0 reversals
step 3 · it posts the routine

It posts the routine items and holds the rest.

410 routine matchesposted
2 over your limitheld
support, journal entry, and one-click reversal attached
what every entry carries

Every entry shows its support, where it stopped, and a receipt.

When Aleq posts, it attaches the documents it matched, the rule it followed, the approval limit it checked, and exactly what changed in your ledger.

the support
Nothing posts without the documents behind it.

Aleq works from the bank line, the invoice, the ledger, and your approval limits — not a typed prompt. The screen shows exactly which documents it matched before it posts anything.

Support · Stripe depositready
Bank lineStripe deposit$142,400
Matched toStripe payout batch · Apr 30100%
Journal entryDr cash · Cr Stripe Clearingbalanced
Your ruleroutine cash clearing, under the limitauto
support shown before anything posts
the stop
It stops at the judgment calls.

A reliable bank-matching rule still stops when the amount, account, vendor, or risk is outside what you approved. Then it asks instead of guessing.

Held for your approvalheld
Needs approval

$188,440 Foxconn wire

The early-pay discount is worth taking, but this is over your $100k auto-payment limit.

match confidence 92%your limit $100kmode Assist
held for sign-off · no money moved
the receipt
Every posting comes with a receipt.

The receipt shows why it posted, what triggered it, which limit allowed it, and the exact journal entry — so you and your auditor can replay it.

Action receiptposted
why

Amount, customer, and memo match invoice INV-7829 to the penny.

triggered by

ACH $312,400 · memo CYBERDYNE-MAR

your rule

exact customer match, under the exception limit, posts automatically

journal entry

Dr cash $312,400 · Cr A/R $312,400 · invoice marked paid

reversible entry · full replay attached
you set the limits

You decide how much it does — task by task.

It can post bank matches on its own while every payment waits for your approval and closing the period stays fully manual.

AutoMatching the bank

18,420 matches · 98.7% tied out · routine cash clearing only

AssistScheduling a payment

drafts the wire, attaches the support, waits for your approval

ManualLocking the period

prepares the close package, but you seal the period

the evidence · eval runs

When the stakes go up, Aleq stops guessing. We have the run to prove it.

We ran 57 high-risk accounting tasks that leading AI models got wrong on their own. Then we ran the same 57 with Aleq in the loop — same models, the only change is what Aleq lets them do when the answer isn't certain.

Ungoverned AI

no limits
Hand it a risky task and it just does it.
  • Acts on unverified data and missing documentation
  • Blows past materiality limits and usage caps
  • No gate between "uncertain" and "posted"
  • The failure is silent — it looks like success

Aleq

inside your limits
The same task routes to the safe move.
  • Asks before acting on incomplete evidence
  • Proposes the entry and waits inside your limits
  • Escalates the judgment call instead of forcing one
  • Refuses the unsafe path rather than fake a result
84%
came out right with Aleq in the loop — the same models, ungoverned, got all 57 wrong48 of 57 tasks
75%
Aleq stopped and asked, or queued the entry for your approval, instead of posting something wrong43 of 57 tasks
0
payments left without a person signing off — the controller keeps the keysacross every run
Those 57 failed tasks break into 91 issues across four risk areas — one task often trips more than one. The bar is how many Aleq caught — stopped, asked, or queued for approval — instead of letting through.
Financial reporting, close & record integrity46 failures · caught below76%
Audit, compliance & internal controls24 failures · caught below81%
Professional escalation & communication10 failures · caught below89%
Revenue, billing, contract & covenant risk11 failures · caught below67%

From Aleq's internal eval runs — leading AI models (Claude, Codex, Gemini, Qwen) on the same tasks, with and without Aleq. Request the full methodology →

vs a generic AI tool

Not a chatbot. It posts to your ledger.

Aleq

posts inside your limits
Learns your coding and posts only inside the limits you set.
  • Shows the documents behind every entry
  • You turn it on one task at a time, not all at once
  • Stops at your approval limits and asks a specific question
  • Leaves a reversible receipt for every entry

Generic AI / copilot

answers questions
Answers questions. You still do the posting.
  • Doesn't learn your team's actual coding decisions
  • No per-task limits or approval gate
  • No permission to post to the ledger
  • No receipt your auditor can replay

Watch it learn on your books.

Connect read-only and watch it learn your coding, hold the judgment calls, and post the routine work with a receipt behind every entry.