What Definite does
Numbers your team can defend.
Between the quarterly filing, the morning reconciliations, consultant reviews, and exam requests, proving the books consumes hundreds of hours every quarter. Definite keeps them checked as data arrives, so when a filing is due the balances are already tested.
Continuous checks. Investigated exceptions. Verified outputs.
Continuously
Reconcile the books
Tie the general ledger to loan and deposit subledgers on every data refresh.
Against the rulebook
Check every balance
Run Call Report edits, lending limits, HMDA checks, and capital and liquidity tests.
With answers
Investigate exceptions
Identify the likely cause, show the failed rule, and draft the fix for review.
Ready to use
Export verified outputs
Build Call Reports, board packs, and examiner evidence packages from checked data.
Every output starts from checked books.
Missing data is marked Cannot verify. It never becomes a false green.
Continuous assurance
Checked continuously. Ready when you need it.
Definite runs the proof work as data changes, not only when a filing deadline arrives.
What gets checked
The books and the rules.
Definite normalizes core exports into a checkable state, ties ledgers, and runs the published rules against each transaction and balance.
Daily GL to loan and deposit subledger ties
Call Report and 5300 edit checks
Legal lending limits at origination
HMDA, capital, and liquidity checks
What gets produced
Outputs your team can defend.
Filings and board packs come from the same checked state, not a quarter-end scramble.
Call Reports assembled from checked balances
Board packs with source-to-number traceability
Exception files with rule-cited findings
Audit and exam evidence packages on demand
What Definite verifies
Built around the work a bank controller owns.
Start with the checks that carry your signature, then expand across the same checked state.
Quarterly
Call Report and 5300
Apply the published edit rulebook and assemble the filing from checked balances.
Result: Every reported number tied to its supporting proof.
Every morning
Daily reconciliation
Prove that the general ledger ties to loan and deposit subledgers.
Result: Exceptions surfaced before the day begins.
At origination
Legal lending limits
Check borrower exposure, including related entities, before a loan closes.
Result: Limit breaches found before commitment.
Loan level
HMDA and capital
Test mortgage records against CFPB edits as balances change.
Result: Ongoing checks across recurring obligations.
Why the numbers hold up
AI investigates. Deterministic rules decide.
Definite uses AI only where judgment helps, such as mapping bank-specific data, investigating exceptions, and drafting explanations.
A model never decides whether a number passes. Every verdict comes from deterministic rules.
Same normalized inputs and rule version. Same result.
Deterministic
Each verdict is reproducible and cites the exact published rule. Same inputs and rule version, same result, every run.
Fail closed
Missing or incomplete data returns Cannot verify, never green. A gap in a feed can never pass a check.
Tamper proof
Every check writes a hash-chained receipt that anyone can verify independently, even after export.
How Definite works
One checked state, from source data to signature.
Definite reads bank data and public filings. It never writes back or initiates a transaction.
Each output is built from the same checked state.
1
Read-only data enters
Nightly exports and public filings arrive without giving Definite write access to bank systems.
2
Financial data is standardized
Core exports and the chart of accounts become one standardized data set ready for checking.
3
Rules run deterministically
Published edits, ledger ties, limits, and ratios produce Pass, Fail, or Cannot verify on every run.
4
Exceptions are explained
Definite investigates the cause and drafts a fix. Your team reviews it before anything changes.
5
Verified outputs are assembled
Call Reports, board packs, and examiner evidence packages are built from checked balances.
Every number, with a receipt.
Each check writes a hash-chained receipt that auditors and examiners can verify independently.
Integrations
Your numbers live in a dozen systems. Definite reads them all.
Core exports, the general ledger, loan and deposit subledgers, spreadsheets, warehouses, and public filings: closing the books means reading every one of them. Definite connects to each source and snapshots it nightly.
Every connection is read-only. No write access, no payment initiation. If a feed goes missing, its checks fail closed.
How a connection works
1
Connect read-only
SFTP, file drop, or API. No write access, no payment initiation.
2
Snapshot nightly
Every source is captured and hashed on arrival, before any check runs.
3
Fail closed
A missing or stale feed turns its checks to Cannot verify, never a false green.
Core banking
Loans · deposits · capital
Nightly core and loan-system exports, hashed on arrival.
GL, ERP & payroll
Subledger & payroll ties
Trial balance, subledger, and payroll extracts tied back to the GL.
Files & warehouses
HMDA LAR · schedules
Spreadsheets, file drops, and warehouse reads. The same checks either way.
Public filings
Peer & prior periods
Call Reports, 5300s, OSFI returns, and peer data pulled from public sources in the US and Canada.