Pays the right bills. On your approval.
Every bill checked and ready to pay. You approve — money never moves on its own.
Today, every bill is keyed, chased, and matched by hand.
A PDF lands in the shared AP inbox. Someone keys the vendor, the invoice number, and the amount into Bill.com — then matches the PO and the receipt by eye, chases a CFO approval across Slack and email, and prays a duplicate doesn't slip through. One specialist, one batch, most of a morning. An expired card quietly fails an AWS autopay until service is threatened, and a vendor paid twice has to be clawed back. This is the work Aleq does instead.
It reads the bill, not just files it.
A PDF lands in your inbox and Aleq pulls out the vendor, the bill number, the due date, and the amount — then suggests the GL account it belongs in, with a confidence score on each read. No ABBYY ritual, no "8" misread as "B," no re-keying into a second system. Nothing is keyed by hand, and nothing posts on a guess.
From inbox to approved batch, in one place.
Watch a single bill move: extracted with confidence on every field, tied out three ways against the PO you raised and the goods you received, run up the approval chain your policy defines, then dropped into a payment run — matched, coded, approved, and ready for your rails. No Stripe-to-Chase timing dance, no four bank portals, no spreadsheet priority matrix.
Three-way match before a dollar moves.
Aleq ties the bill back to the purchase order you raised and the goods you actually received. Quantities, prices, and totals have to agree across all three before it's cleared to pay — so you're never paying for a PO you didn't approve or a shipment that never arrived.
The right approval, every time.
Your $100k limit isn't a suggestion. A $188,440 wire climbs the approval chain to a second signer before it can be released; a $4,200 vendor bill over your $3k threshold routes to the CFO; small, routine bills on a vendor you trust move on their own. No Slack message lost in a thread — every approval is logged, so the trail reads cleanly months later.
A bill never gets paid twice.
When a vendor mails a check for an invoice that's also set to ACH autopay, the old way is a phone call and a scramble to cancel before both clear. Aleq holds it instead: same vendor, same amount, same invoice number gets caught and flagged, not paid twice. Bank details that change on a known vendor, or a brand-new payee, are surfaced for a human before anything moves.
It learns each vendor — then earns the autonomy, one at a time.
Every payment starts as a belief in TAMi, the mind behind Aleq: it watches how your AP team codes and approves each vendor, weights it by how often it held up, and only runs on its own once the belief is strong enough — per vendor, never all at once. A monthly AWS bill it has seen dozens of times runs alone; a $188k Foxconn wire over your limit drops back and asks first. You can see every belief, how sure it is, and switch any of them off.
What CFOs ask first.
Does Aleq actually send the payment?
No. Aleq prepares the payment — matched, coded, approved, and ready — and hands an approved batch to your existing rails for execution. It routes a clean run to your bank or payment provider; it does not move the money itself and has no standing authority to. You stay in control of the release.
How do you stop a duplicate or fraudulent payment?
Every bill is matched against the ones already in your system before it can be scheduled — same vendor, same amount, same invoice number gets caught and held, not paid twice. A check arriving on an invoice that's also set to ACH is flagged before both clear. Bank details that change on a known vendor, or a brand-new payee, are flagged for a human to confirm. And nothing is cleared to pay until it ties to a real PO and a real receipt, so an invented invoice has nothing to match.
Who approves before money moves?
You set the approval chain, and Aleq follows it exactly. Below your threshold on a vendor it has proven, it can clear a routine bill on its own; over the limit, on a new vendor, or on anything unusual, it routes the bill up the chain — a $4,200 bill over a $3k threshold goes to the CFO, and a $100k+ wire needs your second signer before it can be released. Every approval is logged with who approved what, and when.
What about 1099s and missing W-9s?
Aleq knows which vendors are 1099-reportable and tracks what's on file. If a bill comes in from a 1099 vendor with no W-9, it's held — coded and ready, but not cleared to pay — until the form is collected, so you're never short the information you need at year-end. It keeps the running totals you'll report, but it does not file your taxes.
Will an auditor accept this trail?
Yes. Every bill carries its own provenance — the PDF it was read from, the PO and receipt it matched, who approved it and when, and the journal entry it posted — so it reviews like a well-documented manual payment. The complete trail exports for audit, and closed periods stay off-limits: a bill belonging to a prior period is surfaced for your review, never posted silently.
Put Aleq on your bill inbox.
Forward a week of real bills and watch Aleq read each one, run the match, and route it for approval — every payment prepared, nothing moved without your yes.