Fintra is the AI finance platform that lets a controller own the close and the controls on one governed ledger. AP, AR, and expenses post their own journal entries as work happens, so the books stay current; reconciliations are auto-matched with exceptions surfaced; the AI drafts accruals and variance narratives into a review queue where a named person approves every entry; and continuous control testing checks every transaction against SOX 404 and SOC 2 frameworks with an exception center and evidence attached. The month-end close becomes a review rather than a reconstruction, and every governed action is sealed as recomputable, audit-ready evidence.
A live close board, matched reconciliations and control tests on every transaction
A live close board, auto-matched reconciliations, an AI-drafted journal queue, and continuous controls, on one governed ledger, with a named person approving every entry that posts.
Close and controls board
Illustrative- Month-end close: reviewing
- on track
- Reconciliations: matched
- 48 of 50
- Journal review queue: approve
- 7 drafts
- Continuous controls: exception
- 1 open
- Board & CFO pack: ready to sign
- draft
The close, reconciliations, controls and reporting a controller owns, on one ledger.
Close, reconcile, post, control and report on one set of books, drafted by AI and signed by a person, instead of stitched across spreadsheets and inboxes.
A close that is a review, not a rebuild
AP, AR, and expenses each post their own journal entries as work happens, so the books stay current. Month-end becomes reconciling and signing off on a live close board, not reconstructing the numbers from a stack of exports.
Reconciliations that match themselves
Bank feeds and sub-ledgers are auto-matched against the general ledger, and only the breaks surface for review. You work the exceptions instead of ticking every line by hand across six spreadsheets.
A journal queue AI drafts and you approve
Accruals, allocations, and adjustments are drafted for you, grounded in your own books and policies, and land in one review queue. Adjust the ones that need it, approve the rest, and every entry keeps a named approver.
Continuous, full-population control testing
Controls test every transaction against SOX 404 and SOC 2 frameworks, not a quarterly sample, so a control break is caught when it happens, not at year-end when the evidence is cold.
An exception center with evidence attached
Every failed control and unmatched item lands in one exception center with the transaction, the rule it broke, and the trail already attached, so working an exception starts from evidence, not a spreadsheet hunt.
Board & CFO reporting from posted journals
Financial statements and variance come straight from posted journals, so a question from the CFO or the board drills to the transaction instead of starting a reconciliation from scratch.
Today the close is a hunt through exports, and controls are tested on a sample.
The tools push a controller's work into spreadsheets, inboxes and a quarterly control sample. Fintra puts it on one ledger, so posting and controlling happen together as the work does.
- Close week is a hunt
- Which accounts are reconciled, which entries are still drafts, who is sitting on an approval: all of it lives in spreadsheets and inboxes, so the first days of close go to finding the state of the close rather than finishing it.
- Controls are a quarterly scramble
- Controls get tested on a sample once a quarter, and evidence is screenshotted together the week before the auditor arrives. A break that happened in month one is not caught until it is expensive to fix.
- Every entry is defended, not trusted
- Journal entries are drafted by hand, emailed for review, and reconciled against a ledger nothing posts to cleanly, so the number in the pack gets defended after the fact instead of trusted because it was controlled as it happened.
The usual close
Reconciled by hand, controlled by sample
- Spreadsheet reconciliations
- Journal entries drafted by hand
- Close tracker in a doc
- Controls tested on a sample
- Evidence screenshotted at year-end
- Statements exported and re-keyed
Fintra: one ledger
Close and controls on the same books
- Automated close & posted statements
- Auto-matched reconciliations
- AI-drafted journal review queue
- Full-population continuous controls
- Exception center with evidence
- Board & CFO reporting
Because every entry posts to one ledger and every transaction is tested, the evidence comes out of the close instead of a year-end scramble. Fintra runs single-company books per entity today; multi-entity consolidation is on the roadmap.
Nothing posts until the controller signs it.
Fintra drafts the reconciliation, the journal entry and the variance narrative, routes anything consequential to a named person, and keeps the decision as evidence you can hand an auditor.
AI drafts the close work
Reconciliations, accruals, allocations, and variance narratives are drafted for you (grounded in your own books and policies, not generic assumptions), so your team spends close week on judgment, not data entry.
A person approves every entry
No journal entry posts and nothing consequential lands without a named approver, routed by the policies you set. The controller stays the control: the AI proposes, a person disposes.
Every decision leaves a trail
Each governed action is recorded as hash-chained, recomputable evidence (the draft, the reasoning, the approver, and the result), so an audit starts from a trail you can replay rather than a reconstruction.
Every score can be explained
Control scoring is deterministic and explainable. Governance decides and records on every wired-in action and gates where it is enforced; broader automatic enforcement is staged, and we say so plainly.
What is production-ready, and what we are building with you.
Available today
- A real double-entry ledger with automated close and statements straight from posted journals
- Auto-matched bank and sub-ledger reconciliations with exceptions surfaced for review
- An AI-drafted journal review queue where a named person approves every entry before it posts
- Full-population continuous control testing mapped to SOX 404 and SOC 2, with an exception center and evidence attached
- Governed approvals with recomputable, hash-chained evidence on every wired-in action
Early access and on the roadmap
- Multi-entity consolidation: Fintra runs single-company books per entity today; roll-ups are on the roadmap
- Card, bill-pay, and financing rails simulate until you explicitly enable a provider, so no real money moves in demos
- Some governance surfaces run on seeded demo data today
- Live connectors to the tools you already use are a pluggable provider seam, live for design partners
SOC 2 readiness means mapped controls and audit-ready evidence: a formal SOC 2 attestation is issued by an independent auditor, never by us. In demos, no real money moves. We will always tell you what is production-ready and what we are building with you.
The close and the controls, set up for how your industry runs.
The same ledger, reconciliations and control tests, with the monthly work your industry adds on top.
What is Fintra for controllers?
Controller questions, answered
What does Fintra do for a controller?
It gives the controller a live close board, an AI-drafted journal review queue, auto-matched reconciliations, and full-population continuous control testing in one place. The close becomes a checklist you run instead of a fire you fight, and every entry keeps a named approver and a recomputable evidence trail.
How does Fintra speed up the month-end close?
AP, AR, and expenses each post their own journal entries as work happens, so the books stay current instead of being rebuilt at month-end. Reconciliations are auto-matched and only the breaks surface, the AI drafts accruals and variance narratives, and a named person signs off. Because statements come straight from posted journals, the close is a review rather than a reconstruction.
How do reconciliations and journal entries work?
Bank feeds and sub-ledgers are auto-matched against the general ledger, and unmatched items surface as exceptions. Journal entries (accruals, allocations, adjustments) are AI-drafted into one review queue grounded in your own books; you adjust what needs it and approve the rest. Nothing posts without a named approver, so the controller stays the control.
How does Fintra support SOX 404 and SOC 2 controls?
Controls test every transaction (full-population, not a quarterly sample) and are mapped to SOX 404 and SOC 2 frameworks. Failed controls land in an exception center with the transaction and evidence already attached, and every governed action is recorded as recomputable evidence. This is control alignment and evidence, not a certificate: a formal SOC 2 attestation is issued by an independent auditor, never by Fintra.
Does the AI post entries on its own?
No. Fintra is draft-first: the AI proposes the reconciliation, the journal entry, or the narrative, and no entry posts and nothing consequential lands without a named human approver, routed by the policies you set. Every decision is sealed as a traceable record, so automation supports the controller rather than bypassing review.
Does Fintra support multiple entities and consolidation?
Fintra runs single-company books per entity today, and multi-entity consolidation is on the roadmap. We flag that honestly rather than imply a roll-up ships today: a controller gets one governed close and controls per entity now, with consolidated views coming.
See your close and controls on one ledger.
Bring your books. We will show the continuous close, auto-matched reconciliations, the AI-drafted journal queue, and full-population control testing on your numbers, with a named person approving every entry.