Closes the month. Day by day, not at the end.
Aleq closes a little every day. Month-end becomes a sign-off, not a sprint.
Today, the close is a day you block off.
First Monday of the month, extra-large cold brew, the whole day held on the calendar because "everything going smoothly" rarely happens. Pull statements from four banks and seven accounts, export the GL from NetSuite, tie every subledger out by hand in Excel, chase a $2,445.86 variance through outstanding checks and unrecorded fees, key the correcting entries, then build the audit folder and write the sign-off email to the CFO. One controller, most of a day — and that's before a single judgment call. This is the choreography Aleq runs instead.
The close runs continuously.
Reconciliations, accruals, and cutoff don't wait for the calendar to flip. Aleq works each task the moment its inputs are ready, so by the time you sit down it's day 3 of 5 with most of the work behind you — not a five-day fire drill that starts on the first.
Subledgers tie out daily, not at month-end.
Every subledger reconciles to the GL as transactions land — AR to the lockbox, the Stripe clearing account to its payouts, AP to bills. Routine accruals and depreciation post on their own schedule, area checklists clear themselves green, and the period stays open and live until you seal it. There's no end-of-month tie-out because the tie-out never stopped running.
Across every entity, one close.
US parent, MX, UK, DE — each on its own books, all on one board. Aleq tracks the critical path across them, so a missing vendor invoice in Germany shows up as the one thing standing between you and a sealed period — not something you discover on day five.
It earns autonomy one close task at a time.
TAMi, the mind behind Aleq, watches how your team works each close and learns which tasks are routine and which are judgment. A reconciliation it has tied out clean for months runs alone; a material accrual estimate it's still calibrating drafts and asks first; the period seal stays yours by design, no matter how confident it gets. Autonomy is earned per task, you can see the belief behind each one, and you can pull any of them back.
Sealed and signed.
You sign off and the period seals. Every journal in it is signed, the audit package is built, and the whole thing is pinned where it can't quietly change. When someone asks how a number was reached three quarters from now, the answer is already saved.
What CFOs ask first.
Who seals the period?
You do. Aleq does the work — reconciles, ties out the subledgers, posts the routine accruals and depreciation, drafts the judgment calls — but the flux review and the period seal are always a person's. Nothing locks until you sign, no matter how confident TAMi gets. You stay the controller of record on every close.
How do prior-period adjustments work once a period is sealed?
Not silently. A sealed period is pinned tamper-evident and Aleq can't post into it, same as anyone else. A correction either goes through a clearly recorded reopen-and-re-sign, or posts to the open period as a prior-period adjustment — visible, attributed to who made it, and tied to the original entry. History is never rewritten; it's reversed and re-posted in the open period.
How does timing work across multiple entities?
Each entity closes on its own books, but Aleq tracks the critical path across the whole group and seals them in dependency order. A missing vendor invoice blocking a VAT reconciliation in your German entity shows up as the one thing standing between you and a sealed group — flagged with what's needed and who owns it, on day two, not day five. The rest of the close keeps moving while it's open.
What stays human, every close?
The flux review and the period seal — by design, not because TAMi can't get there. Material accrual estimates and anything over your threshold come to you drafted and explained, ready to accept. Routine tie-outs and recurring postings run on their own once TAMi has earned them, and you can pull any of them back to drafted at any time.
What's your support for a SOX or financial-statement audit?
Every close task carries its own support — the entries it posted, the documents behind them, the reason each was made, and a signature. Sign-off and period seal are logged to the person who made them. The whole trail exports as your audit package, so each number reviews like well-documented work, not a black box, and your controls over what posts automatically are visible and testable.
Can a closed period be changed?
Not silently. Once you sign and lock a period it's sealed and pinned tamper-evident; Aleq can't post into it, same as anyone else. A correction goes through a clearly recorded reopen-and-re-sign, or posts to the open period as a prior-period adjustment — visible, attributed, and never quietly slipped into closed books.
Run your next close with Aleq.
Watch Aleq run a real month on your books — every entity on one board, every entry explained, the period sealed on schedule. You sign off.