QI Hub / Money / Escrow settings
Fri, Aug 29, 2026

Escrow settings QI Hub

How this organization's exchange funds are held, synced and disbursed: the sub-escrow provider this org runs, the master and sub-account position at its bank, reconciliation standing, and the payment rails the bank makes available. Every balance carries the moment it was measured.

QI of record holds funds
Org in scope
Meridian Pacific Northwest Escrow settings are per QI org — the election below is this org's
Funds custody. Meridian Pacific Northwest is the Qualified Intermediary of record. Client funds sit in the QI's escrow accounts at its bank — the platform never holds, receives or controls client funds, in either provider mode. Exchangers request disbursements and verify instructions; release requires approval by two authorized officers, proposer distinct from approver. The exchanger is never an approver.
Sub-escrow provider One workflow contract, two providers — this org runs exactly one This org: incumbent
Mode A · Incumbent integration

Sub-escrow platform (incumbent) Active · connected

Sub-accounts are created and managed on the bank's existing sub-escrow accounting platform through its API. The bank keeps its master-account and wire-execution arrangement unchanged.
Adapter subescrow-adapter/incumbent · driven by the eight family workflows
Connection Connected · credential valid, rotated 12 days ago · inbound events accepted only with a verified signature
Last balance sync 14:17 UTC — paused. The 14:17 sync filed RECON-2214 and paused sync for this org until it is resolved on the record · 214 sub-accounts · snapshots written per sub-account
Exceptions 1 open — RECON-2214, reconciliation mismatch on sub ····5001, in the QI Ops work queue
Chosen where the bank already operates the incumbent platform: the QI keeps its current bank arrangement, and Open1031 drives sub-account lifecycle through the adapter.
Mode B · Built-in

Built-in ledger Available

Open1031's master/sub ledger provides the same capabilities directly against the bank core's real-time API — for organizations whose bank does not run a sub-escrow platform.
Adapter subescrow-adapter/builtin · same eight family workflows, same contract
System of record The bank core remains system of record for the master deposit; the ledger is the authoritative record of allocation across sub-accounts
Used by 4 of 6 linked orgs — MMW, MGC, MNE, MSW
Mode changes are scheduled with Open1031 operations — both modes run the same workflow contract, so the election can move without changing how exchanges behave.
Same contract in both modes: subescrow-account-open subescrow-account-close subescrow-balance-sync subescrow-interest-split subescrow-segregation-attestation subescrow-disbursement-handoff subescrow-kyc-aml-export subescrow-exception-router
Master & sub accounts The QI's escrow position at its bank — one master, one sub-account per exchange with funds on deposit Measured today · 14:17 UTC
Account chain: bank, QI org, master escrow account, sub-accounts, exchanges — with the platform outside the chain Open1031 — software layer Ledger, consoles, Vectr workflows. Not an account level — never in the chain of custody. reads and writes through the bound adapter ↓ Bank Depository · payment rails wire · RTP · FedNow execution runs its own compliance program QI org — the bank's customer Meridian Pacific Northwest fiduciary of record for every exchange holds the funds — the platform never does Master escrow account ····4410 — the QI's escrow DDA all-in rate set here by the bank system of record: the bank core 214 sub-accounts one per funded exchange zero-balance start QI split applies here 1:1 one exchange
$98,412,760.00 Master balance · measured ····4410 · today 14:17 UTC · bank-reported
214 Active sub-accounts the 214 of 412 active files with funded escrow · 18 opened this month
12 Closed at zero this month closed on exchange completion, residual interest posted first
1 Held past exchange period (g)(6) — the period ends at the earlier of day 180 or the return due date (with extensions); release-eligibility governs
Sample data. All organizations, banks, account numbers, balances, people and references on this page are synthetic — none of it is real customer information.
Reconciliation & segregation Nightly attestation · examiner-ready report per run 1 exception open
Segregation attested today, 05:00 UTC. Every dollar of the master balance allocated to exactly one sub-account — 213 of 214 sub-accounts matched the bank.
1 mismatch, on the record: sub ····5001 is −$482,600.00 against the ledger snapshot. Filed as RECON-2214 in the QI Ops work queue at 14:17 UTC; balance sync for this org is paused until it is resolved. Resolving records a decision — it never moves money.
Reconciliation report retained per run — per QI org, archived with the audit record and exportable for an examiner.
Payment rails Bank-side capabilities on master ····4410
Wire
same-day · bank cutoff 2:00 PM PT · settlement confirmation returned
 Available
RTP
24×7 instant settlement · receiving-bank participation required
 Available
FedNow
24×7 instant settlement · receiving-bank participation required
 Available
Rails are capabilities of the QI's bank, exercised by the bank. A disbursement hands off to the bank only after multi-party verification of the instructions and approval by two authorized officers, proposer distinct from approver. The platform transmits instructions; the bank executes.
Provider election across linked orgs Each QI org elects one mode — 2 on the incumbent platform, 4 on the built-in ledger
QI org Provider mode Connection Sub-accounts Reconciliation
Meridian Pacific Northwest MPN incumbent Connected · sync paused 14:17 UTC 214 1 exception
Great Lakes Exchange Co. GLX incumbent Connected · synced 5m ago 84 Attested 05:00
Meridian Mountain West MMW built-in ledger Bank core · real-time 96 Attested 05:00
Meridian Gulf Coast MGC built-in ledger Bank core · real-time 61 Attested 05:00
Meridian Northeast MNE built-in ledger Bank core · real-time 73 Attested 05:00
Meridian Southwest MSW built-in ledger Bank core · real-time 48 Attested 05:00
A mode election is an org-level decision recorded on the audit trail. Both modes run the same eight workflows, so reporting, reconciliation and the exchanger experience are identical across this table. Sub-account counts are the active exchanges with funded escrow — a subset of each org's active files (MPN: 214 of 412) — so they read lower than the file counts on the portfolio surfaces.
Build contract — escrow settings (QI Hub)
1 · The election is the seam, drawn as configuration. This page renders the issue 2146 dual-mode decision as a per-org setting: Mode A (sub-escrow platform, incumbent) or Mode B (built-in ledger), one active per QI org, both running the identical subescrow-* workflow contract shown on surfaces/vectr-ops.html. Roles only, everywhere: the incumbent platform, the bank and every organization are named by role or by synthetic name — no real vendor or bank name may ever appear here.
2 · The account chain never contains the platform. The diagram encodes the pinned issue 2146 hierarchy — platform (software) above bank → QI org → master → subs → exchange 1:1 — and the platform box is dashed and outside the chain. The bank core is system of record for the master deposit; the ledger (or the incumbent platform) is the authoritative record of allocation. Copy on this page must never place Open1031 in the chain of custody.
3 · Constructive-receipt-safe copy is a fixed grammar. Exchangers request and verify instructions; QI officers approve, approver ≠ proposer; the bank executes; the platform transmits and records. The custody statement at the top is a compliance-control disclosure — in code it routes through components/compliance/ComplianceDisclosure.tsx, and it is removed only by shipping a change to the control, never by editing copy.
4 · Zero-balance is a lifecycle, not an invariant. The "held past exchange period" tile exists because a failed exchange after identification locks funds under the §1.1031(k)-1(g)(6) limitation. The exchange period ends at the EARLIER of day 180 or the due date (with extensions) of the taxpayer's return for the year of transfer — never a flat day 180 (docs/COMPLIANCE.md IRS1031-003, finding EXF-06). The release-eligibility date is a distinct field from either date, and a sub-account in that state is drawn as attention, never as an error the QI should force closed — nothing auto-releases when the period ends.
5 · Rails are bank-side capabilities. Wire, RTP and FedNow are listed as what the bank makes available on this master account — availability is the bank's fact, cutoffs are the bank's cutoffs, and no control here initiates a movement. The one deep action offered is the hand-off chain's paper trail (work queue, reports), not a "send" button.
6 · One exception, told the same way three times. RECON-2214 (sub ····5001, −$482,600.00) is the same synthetic exception drawn in the balance-sync drawer on surfaces/vectr-ops.html and as the unexplained delta on surfaces/qi-escrow-and-banking.html — the demo tells one coherent story across the platform console, the QI Ops money surface and this settings page. It stays alarming until resolved on the record; it is never dimmed by acknowledgement.
7 · Provenance. Mockup; every figure synthetic; demo date Fri, Aug 29, 2026. The provider seam, the adapter records and the election UI are design, not shipped code — the workflow family and adapter contract are the issue 2706 catalog and the issue 2718 draft API contract. Fully tokenized against ../tokens.css, zero raw hex, light and dark both designed; --tier and the console-scope tokens are [PROPOSED] and go into packages/web-app/src/index.css before any call site is written. Shell idiom follows surfaces/qi-hub-tier.html; the mode chips follow the adapter-chip contract on surfaces/vectr-ops.html.