Close the evidence gap before closing the period.
Finance teams compare ledgers and statements, isolate differences and prepare reconciliations for sign-off. NodeFox connects the input, reference checks and human decision in one executable workflow.
Interpret the input. Establish the facts. Control the action.
AI interprets
- Statement rows normalized
- Transaction dates extracted
- Bank fee description identified
Systems provide context
- Ledger fee entry: absent
- Statement fee: $150
- Other transactions matched
Code applies exact checks
- 124,800 − 124,650 = 150
- Difference equals documented fee
- Adjustment requires review
People retain the decision
- Controller reviews fee evidence
- Approve proposed adjustment
- Posting remains separately authorized
What proceeds—and what waits
Matching account data reconciles under the agreed period and tolerance rules.
A discrepancy carries its source transactions into review. The proposed fee adjustment is not a posted journal.
Raw input → usable output
Give reviewers the reconciliation and the reason.
The reviewer receives a reconciliation package with the fee adjustment, remaining difference and sign-off together. Posting authority remains separate.
- Input 1
- Reconciliation RC-110 · October
- Input 2
- Ledger balance: $124,800
- Input 3
- Statement balance: $124,650
- Input 4
- Difference: $150
RC-110 · reconciliation package
Proposed adjustment
$150 fee
- Unexplained difference: $0
- Evidence and sign-off attached
Decision attached
Approve proposed adjustment
Source references and configured checks accompany the result.
Inspect the structured record
{
"reconciliation_id": "RC-110",
"currency": "USD",
"proposed_adjustment": 150,
"unexplained_difference": 0,
"journal_posted": false
}Synthetic sample files with inputs, checks and decisions. System updates require configured access and authorization. Documents and reports depend on the chosen Writer format and template.
Give reviewers the reconciliation and the reason.

Transcript and demonstration details
Illustrative execution, not a customer deployment. Narration is AI-generated. Actions and outputs depend on workflow configuration.
- 0–8s · The balances differ by one hundred and fifty dollars
October’s ledger and bank statement disagree. The team needs an explanation before proposing an adjustment.
Reconciliation RC-110 · October · Ledger balance: $124,800 · Statement balance: $124,650 · Difference: $150
- 8–18s · Reconcile the difference
The workflow normalizes the exports and matches transactions. A documented bank fee explains the difference; the ledger entry is absent.
124,800 − 124,650 = 150 · Difference equals documented fee · Adjustment requires review
- 18–26s · Keep arithmetic and review in the same process
Exact code checks the balances. The graph carries the matched evidence and proposed adjustment to the controller.
General ledger export · Bank statement · Close checklist
- 26–34s · Review before posting
The controller approves the proposed fee adjustment. Journal posting remains a separately authorized action.
Controller reviews fee evidence · Approve proposed adjustment · Posting remains separately authorized
- 34–44s · A close package with no unexplained balance
The reconciliation report includes the proposed adjustment, evidence and sign-off. No journal has been posted by this example.
RC-110 · reconciliation package · Proposed adjustment: $150 fee · Unexplained difference: $0 · Evidence and sign-off attached
- 44–54s · Inspect the explanation later
The recorded inputs and checks remain available for review. Measure preparation time and review rework, not just execution speed.
Reconciliation RC-110 · October · Ledger balance: $124,800 · Statement balance: $124,650 · Difference: $150
What could financial close reconciliation release?
Editable hypothetical example · USD
What could less coordination be worth?
Change four assumptions to estimate annual capacity. These are example inputs, not customer results. Calculations stay in your browser.
- Annual capacity potentially released
- 953.3 hours
- Annual labor-capacity equivalent
- $61,967
- Reduction in hands-on time
- 61.1%
1,040 cases / year × 55 minutes removed per case ÷ 60. Includes eligibility, exception effort and rework when entered.
Capacity is not automatically cash savings. Value depends on how the released time is used and what the workflow costs to operate.
Measure the work removed—and the quality that remains.
- Preparation hours per account
- Unexplained differences
- Review rework
Start with one financial close reconciliation process.
Access, ownership and acceptance
Provide period-matched ledger and bank exports, reconciliation rules and a reviewer. Scope package creation separately from journal posting.
- General ledger export
- Bank statement
- Close checklist
Name the process owner and technical operator. Agree acceptance criteria and costs before implementation. A successful evaluation leads to recurring platform use; proven connections and checks can support the next workflow. When feasibility is already established, scope production directly.
Is this work your team keeps coordinating?
Bring the current steps, systems and approximate volume. Discuss financial close reconciliation, what would remain human-owned and whether a paid implementation makes sense.