Reconciled to the penny, by morning.
Aleq reconciles overnight. You wake up to finished books — not a to-do list.
Today, the close is a four-hour truth-finding mission.
Log into four bank portals across seven accounts. Export 1,847 GL lines from NetSuite into a workbook. Hunt a $2,445.86 variance line by line. Trace one $46,443.72 Stripe payout — net of fees, settling two days late — back to 247 customer payments. Key the correcting entries by hand, then file the proof in a shared drive so an auditor can find it. One controller, one morning, before a single judgment call. This is the work Aleq does instead.
It works the exceptions — it doesn't hand them back.
Your operating account came in $17,488 off the books. Aleq tracked it down — an unrecorded payroll-tax draft and a duplicate Stripe payout — posted the fixes, and left them one click to undo. You see the work that got done, not a pile of flags to chase.
Bank, processor, and clearing — reconciled as one.
A Stripe payout isn't one number. It's 247 customer payments collected over two days, aggregated into a single transfer, net of $1,388.43 in fees, landing in the bank after the invoices were booked. Aleq holds all three sources at once — the bank line, the processor activity, and the clearing account — and resolves the timing and the fee split so every side ties out. The gross, the fees, and the net all reconcile to $0.00, without a workbook.
Every match shows its reasoning.
Each suggested match comes with a confidence score and the plain reason behind it — the amount, the timing, the name on the transaction. Accept it in a click, or open the receipt and check. Nothing posts on a guess.
The amount matches to the cent, it landed within five days of the invoice, and "Vanta" appears on the transaction.
Every match is a belief — earned, not a rule you wrote.
Behind each reconciliation is TAMi, the mind that runs Aleq. It forms a belief per match — these bank lines mean that payout, this counterparty settles late — and weights it by how many times it held up under your controller's eye. A pattern confirmed hundreds of times runs on its own; a new counterparty or an off amount drops back to a draft and asks first. You see the belief, how sure it is, and how many confirmations earned it the autonomy.
What controllers ask first.
How do my auditors treat entries Aleq posts?
Every reconciling entry carries its own support — the bank line, the matched document, the reason it matched, and a signature — so it reviews like a well-documented manual entry, not a black box. The complete trail exports for your audit, and you can see who (or what) touched every number.
Can it touch a period I've already closed?
No. Closed and locked periods are off-limits to Aleq, the same as anyone else. Reconciling entries post to the open period; anything that would affect a prior period is surfaced for your review, never posted silently.
What decides whether it posts on its own or waits for me?
You do. You set the materiality threshold and which accounts run automatically. Under the limit on a pattern it has proven, it posts; over the limit, on a new counterparty, or on anything unusual, it drafts and holds for your approval.
What happens when it gets one wrong?
Every posting is reversible — the reversing entry is staged before it posts — so you undo it in a click. Aleq learns from the correction and asks first on anything like it until it's sure. You stay the controller of record on every entry.
Where does my bank data live, and can it move money?
Aleq connects read-only through your existing feeds: it sees transactions but can't move money or change a bank setting. Data is encrypted and access is role-scoped — full detail on the security page.
Put it on reconciliation first.
Connect read-only and watch Aleq reconcile a real month on your books — every match explained, every entry reversible.