Bring the bank balance, the book balance and the trust liability onto one cut-off date, itemise the differences with their evidence, and hold the pack for the broker, who reviews, signs and dates it.
A bank feed, a journal and a beneficiary ledger set are pulled for one account from supported sources.
02
A deposit lands with a truncated originator string, so it is held as unidentified rather than posted.
Reason
03
The journal cash balance, the ledger balances and the reconciled bank balance meet on one date, as Colorado requires.
04
A beneficiary ledger in deficit is raised as a shortage, not netted — California deducts no such account.
05
A difference carries its evidence and a draft of the corrective action Florida records with the explanation.
Decide
06
An unidentified receipt, a deposit in transit or an outstanding cheque is aged from the date it first appeared.
07
A reconciliation falls due on the cadence the state sets, and the pack routes to the named broker of record.
Out
08
The pack, the source document behind each figure and the sign-off are retained on the state's clock.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Not one resident's balance against the property ledger: the account against what the brokerage owes everyone it holds money for — and the named broker of record reviews, signs and dates it.
Example workflow
One account, feed to signature
AgentHuman
1Cut-off date reachedBank statement, journal, beneficiary ledgers and the prior signed pack
2Balances assembledJournal cash balance, ledger cash balances and the reconciled bank balance, each with its source
3Differences itemisedReconciling items, unidentified receipts, ageing and confidence
4Controls appliedCut-off checks, negative-ledger checks, signatory and ageing checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is posted or adjusted at any of them — the agent is assembling, and the broker's lane opens at the confidence gate.
5DecisionDivides at the confidence threshold
High confidence
Goes to the broker of record to sign.
Low confidence
Adds a controller read first.
Broker sign-off
The pack is held with its differences, its ageing and the confidence.
Sign · Query · Send to controller review
Signed — dated and filed▼
6Reconciliation record updatedOnly where write access and approval policy allow it
7Outcome evaluatedUnexplained differences, ageing outcomes, examiner findings and post-signature corrections
Queries
Each broker query is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Adjusting, posting or clearing a trust ledger entry.
Moving, instructing or scheduling client money.
Deciding that a difference has been explained.
Certifying that the account and the liability agree.
Automation boundaryAgent acts unaided
✓Pull the bank, journal and ledger balances for one cut-off date.
✓Itemise each difference and carry the evidence behind it.
✓Age unidentified receipts, deposits in transit and stale items.
✓Flag what the broker should weigh, and hold the pack for them.
The agent is read-only and never signs; nothing it produces moves client money.
Funding a shortage from any account.
Filing the Nevada annual accounting or the declaration.
Adding, removing or authorising an account signatory.
Changes to cut-off, threshold or state-rule configuration.
Example output
One difference, annotated
Everything the agent reports is attached to the document it came from — after signature that pack is what an examiner re-performs.
Reconciliation output · single accountIllustrative example
Account
Difference line
Age at cut-off
Source of record
Confidence
Corrective action
Sales escrow account
Cheque to a beneficiary issued before the cut-off and not yet presented
41 days
Bank statement image
93%
Explanation and correction drafted
As receivedTaken from the bank statement and the journal on file — nothing on this side is computed by the agent.
Evidence usedBank statement lineBeneficiary ledgerDeposit slip on file
Why this is a differenceIt cleared after the cut-off, so it sits outstanding — a true shortage is cured from the broker's own funds, not edited away.
ActionSignQuerySend to controller review
What the score decidesBelow the configured threshold the pack picks up a controller read before it reaches the broker.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Each trust accountFrom the bank and the ledger
03Assembly
Assemble from the record
Draw on the statements, journal and ledgers on file and the state rules configured for the firm.
01Approved path
Three balances, one date
Routine reconciling items arrive already itemised and aged.
02Human review
Send the read to the differences
Ledgers in deficit, unidentified receipts and stale items are marked, so the broker's read starts where risk concentrates.
04Build an evidence trail
The difference, the item behind it and the broker who signed stay on the reconciliation.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
A firm-level three-way agreement rate can read clean while a few accounts carry most of the unexplained differences. Nestack reports the unexplained-difference rate by account, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Multi-bank brokerages
8.3%
3.6×
Review
Property-management pools
6.6%
2.9×
Review
Security-deposit accounts
3.7%
1.6×
Watch
Single-account sales firms
1.5%
0.7×
Normal
Bar: unexplained-difference-rate lift vs. single-account-sales baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
The loop closes on a new case
The loop shuts when the unexplained difference is a regression case. That suite is what the next month reconciled is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Unexplained differences rise in one account type.
02Diagnose
The difference nobody could name, carried month after month, is traced back to the feed that dropped it.
03Improve
Any change goes out numbered, with the accounts that caused it attached.
04Verify
One reconciliation case still failing is enough to hold the release back.
05Learn
One case joins the suite, one line joins the account record.
Learn → DetectThe return edge. The next month reconciles against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, reconciliation workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Trust workflow discovery and boundary definition.
02Bank and ledger source assessment.
03State rule, cut-off and cadence configuration mapping.
04Balance ingestion and normalisation.
05Three-way logic and evidence binding.
06Confidence scoring and difference routing.
07Broker sign-off workflow.
08Bank and ledger-system integration.
09Difference and ageing cases.
10Guardrails and signature controls.
11Account-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne account, one stateProductionProduction bank and ledger feedsAdvancedMultiple states / entities
Introduced at Pilot
Assembly to your accounts and rules✓✓✓
Broker sign-off✓✓✓
Three-way agreement baseline✓✓✓
Introduced at Production
Reporting by account—✓✓
Sign-off workflow in your systems—✓✓
Approved pack write-back—✓✓
Bank-and-ledger integration—✓✓
Introduced at Advanced
Multi-state rule sets——✓
Multi-stage brokerage sign-off——✓
High account volume——✓
Multi-state reconciliation controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your trust accounts and their bank details→Balance ingestion and account mappingWeek 1
02Representative signed reconciliations→Assembly baseline, ledger mapping and evidence bindingWeek 2
03Your state rules, cut-off dates and cadences→State rule, cut-off and cadence mapping, and the boundaryWeek 1
04Access to relevant feeds, statements or exports→Bank, ledger and accounting assessment, then integration setupWeek 2
05Reconciliations you would not want audited→Difference cases and the evaluation suiteWeek 4
06What no signed reconciliation may hide→Confidence scoring, difference routing, guardrails and sign-off controlsWeek 3
07Named brokers of record to review packs→Broker sign-off workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The chart is drawn in weeks of real work, and that is the reason week five holds a pair of bands.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Trust workflow discovery, state-rule mapping and the automation boundaryW2Source integration and the assembly baselineW3Reconciliation workflow, confidence logic and sign-off controlsW4Evaluation suite, difference cases and failure-mode testingW5Ledger integration, pilot accounts and targeted correctionsW6One monthly cycle run under the broker of record, then Agent Care handover
Reading the bandEach bar sits only on the weeks its work is named in. The week 5 overlap is real work, not padding.
At the end of W6Once the month reconciles, Agent Care assumes the running agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Real Estate AI agent
Build a trust-reconciliation agent around your state's rule.
Show us your trust accounts, your ledger of record and the states you hold money in. The signature, the explanation of each difference and the licence stay with the broker of record.
