FREELANCED concept · Month-end close software
For finance teams of 3 to 15. Every night Tieout reconciles bank, card and subledger balances against your ERP. Matches are ticked with the evidence attached. Everything else is marked in red, with the difference and the likely reason.
Designed to read from NetSuite, Sage Intacct, Xero and QuickBooks Online, plus bank, card and payroll feeds. Fictional product; the walkthrough form sends nothing.
FREELANCED · Motion study
A 15-second product film, composed for landscape and portrait. Fictional software and sample accounts.
FFooted · where the days go
Most of it goes on exporting, pasting, ticking and chasing. The balances that matter turn up on day seven, when there’s no time left to explain them.
An illustration of where a manual close spends its time, not customer data. Your close will have its own shape; the walkthrough maps it.
Map your own close in a walkthroughAgreed to source · how a close runs
Connect once. From then on Tieout repeats the first three passes every night of the close, so the list of exceptions keeps shrinking while your team works it.
At 02:00 Tieout reads the trial balance from your ERP and the statements behind it: bank, cards, payroll, AR and AP subledgers, even a delivery-note export. Read-only. Nothing posts back without a person.
Transactions pair on amount, date, reference and counterparty, including partial payments and one invoice paid in three. Anything matched with less than full confidence goes to review instead of being ticked.
Accounts that tie are ticked in green and get out of the way. The rest are marked in red with the difference and the most likely cause, from missing receipts to deliveries that arrived without an invoice.
A preparer and a reviewer sign each account, and signed accounts lock. When the last one locks, Tieout assembles the close binder: every tick, comment and attachment in one PDF your auditors can follow.
Cross-footed · flux review
When a line moves more than your threshold, Tieout drafts the explanation from the transactions underneath it. You edit it, approve it, and it goes in the binder.
Every movement over your threshold is traced to the documents that caused it, then written up in plain language for you to edit and approve.
Delivery notes and receipted POs without an invoice become suggested accruals, with the reversal already scheduled.
Tasks wait on the tasks they depend on, so nobody reviews a bank rec that isn’t finished.
The person who can fix an exception hears about it in the chat your team already uses, with the receipt request already written.
Read-only access to the binder: every tick, who made it, when, and the evidence behind it.
Signed off · day four
When the last account locks, Tieout assembles the binder: every tick, comment and attachment, indexed the way your auditors read.
Day 4, 5:40 pm. Binder sent.
©Recalculated · pricing
Invite the whole team and your auditors. You pay for the companies you close, and you can stop at the end of any close.
For a single company closing up to 250 accounts with a team of two to six.
For groups with subsidiaries, intercompany balances and more than one currency.
2 included entities: $1,450 per month, billed annually.
Twelve entities or more, or an audit committee with requirements of its own.
?Queries raised · and cleared
Anything not here, bring it to the call. We answer with your data on screen.
No. Tieout reads your trial balance and subledgers through a read-only connection and maps to the chart you already have. Journals it suggests are drafted for your team to post in your ERP, under your approval rules.
Most of the setup is mapping each account to the source that supports it. We do that with you on a copy of last month’s data, so you can compare Tieout’s results against a close you have already finished before you rely on it. Plan for two working sessions.
Bring them. Your existing workpapers stay attached to each account for the first few closes, so reviewers can see the old reconciliation and Tieout’s side by side until they trust the new one.
Yes. Matching uses amount, date, reference and counterparty, and supports one-to-many and many-to-one. Anything paired with less than full confidence is sent to review with the reason, never quietly ticked.
Auditor seats are free on every plan. They see the binder read-only: every tick, who made it, when, and the evidence it rests on. Requests for more support are answered inside the account they relate to.
Tieout can read balances and transactions. It cannot move money, post journals or change master data. Suggested journals are exported for a person on your team to post.
Agreed · start with last month
We run Tieout on a copy of last month’s data first, so you can check every tick against the close you already finished. Thirty minutes, with your controller and ours.