Rev. Proc. 2000-37 Safe Harbor · Vectr Workflow Proof
Demo exchanger: Matt Belcher (synthetic)Replacement: 456 Sunset Blvd, Los Angeles CA · $850,000Relinquished: to be sold within 180 days
AUTOMATION PROOF: Every step of a reverse exchange is deterministic, watchable, document-generating, and approval-gated — exactly the shape of a Vectr workflow. This page maps the full Rev. Proc. 2000-37 safe-harbor journey to named Vectr workflows, demonstrating that reverse exchanges are fully automatable. The claim that "reverse exchanges can't be automated" is false by construction: there are no freeform human decisions that a workflow engine cannot model.
Exchange-last flow — EAT/SPE-LLC takes title to replacement first. Rev. Proc. 2000-37 safe harbor.
Rev. Proc. 2000-37
38days
to identify relinquished45-day deadline · Jul 21, 2026§1031(a)(3)(A)
173days
EAT parking window180-day deadline · Dec 20, 2026Rev. Proc. 2000-37 §4
Exchange completion15%
Reverse Exchange StepsStep 2 of 6 — EAT Acquisition in progress
Step 1 complete — QI engaged, EAT formed· Neela AI
Your QI has been engaged as the Qualified Intermediary of record and has formed (or arranged) the EAT SPE-LLC. Your segregated EAT escrow account is open and ready to receive the replacement property deed.
Engagement completeVerified
QI Engagement LetterSignedDocuSign · Jun 3, 2026
EAT SPE-LLCOpen1031 EAT-1087 LLCCA Secretary of State
QI Engagement Letter — signed by Matt Belcher + Priya Anand (QI)
SPE-LLC Articles of Organization — Open1031 EAT-1087 LLC
EAT Operating Agreement (single-member LLC)
How a reverse exchange works· Neela AI
In a reverse exchange you buy the replacement property before you sell the relinquished one. The EAT takes title and parks it while you sell. Both the 45-day and 180-day clocks started at deed recordation. Every step has a named Vectr workflow running in the background.
Day 0 — Clock starts hereIn progress
Replacement property456 Sunset BlvdEAT holds title
What the workflow does: Records deed into EAT, starts two durable deadline timers (45-day + 180-day), creates parking arrangement record, logs Day 0 timestamp, emits events to start downstream watchers. Triggered by deed-recorded webhook.
Upload closing docs to confirm acquisition
HUD-1 / Closing Disclosure
Uploaded
Recorded Deed (EAT as grantee)
Pending
Parking Arrangement Notice
Pending upload
Upload the recorded deed first to enable confirmation.
5-business-day hard deadline· Neela AI
The QEAA must be signed within 5 business days of Day 0. Missing this window invalidates the safe harbor. I've pre-filled all fields and routed the DocuSign envelope — you just need to sign.
3 business days to sign QEAA· Hard deadline: Jun 10, 2026Rev. Proc. 2000-37 §3
In a reverse exchange you identify the property you intend to sell — the relinquished property. You have 38 days left. I will send Day 30, Day 40, and Day 44 reminders automatically. Add the address below and I will pre-fill the IRS identification notice.
38 days to identify relinquished· Deadline: Jul 21, 2026§1031(a)(3)(A)
Relinquished property to sell (not yet identified)
Enter the address of the property you will list and sell within 180 days.
No relinquished property added yet
You have 38 days — add the property you plan to sell
Add and confirm your relinquished property above to enable.
Sale proceeds must flow to QI escrow· Neela AI
When you close on the relinquished sale, the wire must go directly to your QI's qualified escrow — never to you. Neela guides and drafts. She never moves, holds, or releases your funds — that takes two authorized officers, and neither of them is you.
Constructive receipt guard — NEEDS-APPROVAL
Sale proceeds must go directly to QI escrow. The exchanger must never receive or control the funds. Wire release requires two authorized officers; the approver is never the proposer. The exchanger has no approval role and no fund-movement path.
Closing status
Relinquished property listed for sale
Not started
Sale proceeds wired to QI escrow
Awaiting closing
QI escrow receipt confirmed
Awaiting wire
Handled by Sales Hub + Escrow Hub (forward-exchange workflows reused)
This will be confirmed automatically when QI escrow receives the wire.
Two authorized officers must approve the deed transfer, proposer distinct from approver· Neela AI
The EAT deed transfer and EAT loan repayment are atomic — they happen together. Two authorized officers must approve, and the approver is never the proposer. You will be asked to acknowledge the closing figures for the record; that acknowledgement does not gate or release the wire, because an exchanger who could gate the release would control the funds. Neela guides and drafts. She never moves, holds, or releases your funds.
173 days EAT parking window· Deadline: Dec 20, 2026Rev. Proc. 2000-37 §4
QI Officer — Priya Anand ProposerPrepares the deed transfer instruction and the escrow release.
Second QI Officer — Sandra Osman ApproverThe approver is never the proposer. Enforced in the workflow and in the database.
Exchanger — Matt Belcher Acknowledgement · not an approvalConfirms the closing figures for the record. It does not gate, authorize, delay or release the wire. The exchanger has no approval role and no fund-movement path — an exchanger who could gate release would control the funds under Treas. Reg. §1.1031(k)-1(g)(6).
Deed transfer to exchanger (pending both QI approvals)
EAT loan repaid from QI escrow (pending both QI approvals)
Unlocks only after two authorized officers approve the transfer — the approver is never the proposer. Your confirmation is a record of receipt; it does not release funds.
Vectr Automation Map — Every Step Has a Workflow
8 workflows
Each timeline step below names the Vectr workflow that executes it automatically. Workflows are triggered by events (deed recorded, doc signed, deadline clock), not by manual staff action. This is why reverse exchanges are fully automatable.
Pre-Day 0
Engage QI / Form EAT
· Complete
Exchanger engages a licensed QI firm as the Qualified Intermediary of record. The QI forms (or arranges) an SPE-LLC (the Exchange Accommodation Titleholder) to hold the replacement property. The EAT has its own bank account and deed capacity.
What the workflow does: Creates SPE-LLC articles of org, opens segregated EAT escrow account, generates operating agreement, routes for QI counter-signature, sends executed docs to exchanger. All triggered on exchange creation — zero manual steps.
Day 0 — Clock starts here
EAT Acquisition & Parking
In progress
The EAT takes title to 456 Sunset Blvd ($850,000) — the replacement property. Both the 45-day identification clock and the 180-day parking clock start at deed recordation. The exchanger never holds title during parking.
Replacement property456 Sunset BlvdEAT holds title
What the workflow does: Records deed into EAT, starts two durable deadline timers (45-day + 180-day), creates parking arrangement record, logs Day 0 timestamp, emits events to start downstream watchers. Triggered by deed-recorded webhook.
Days 0–5 (business days)
Sign QEAA Agreement
5-business-day hard deadline
The Qualified Exchange Accommodation Agreement (QEAA) must be signed within 5 business days of EAT taking title. This is the Rev. Proc. 2000-37 safe harbor gate — missing this window invalidates the exchange. Vectr auto-generates the document and sends for e-signature immediately on Day 0.
What the workflows do:eat-agreement-generate pre-fills QEAA + EAT loan docs from exchange data and routes both parties to DocuSign. reverse-qeaa-5day-watcher runs a countdown timer; if unsigned at Day 3 it sends a reminder; if unsigned at Day 5 it escalates to QI staff and blocks the exchange.
Documents auto-generated by eat-agreement-generate
Qualified Exchange Accommodation Agreement (QEAA)
EAT Loan / Exchange Agreement
EAT Operating Agreement (SPE-LLC)
Parking Arrangement Notice
Days 0–45
Identify Relinquished Property
38 days remaining
Matt Belcher must formally identify the property he intends to sell (the relinquished property) within 45 days of Day 0. In a reverse exchange the relinquished property has not sold yet — he is identifying what he will sell to close the loop. This is the mirror image of the forward 45-day rule.
Relinquished property to sell (not yet identified)
Enter the address of the property you will list and sell within 180 days.
No relinquished property added yet
You have 38 days — add the property you plan to sell
What the workflow does: Runs a 45-day countdown from Day 0 timestamp, sends Day 30 and Day 40 reminders, escalates on Day 44, generates the signed Relinquished Property Identification Notice and routes it to the QI. Triggered by eat-parking-arrangement-setup completion event.
After identification · Before Day 180
Sell Relinquished Property
Matt Belcher lists and sells the relinquished property. Sale proceeds flow to the QI escrow account (not to the exchanger — constructive receipt is blocked by the qualified escrow agreement). The QI holds them until EAT transfer-out.
Constructive receipt guard
Sale proceeds must go directly to QI escrow. The exchanger must never receive or control the funds. The qualified escrow agreement, co-signed at exchange opening, makes this binding.
Handled by the Sales Hub + Escrow Hub workflows (forward-exchange workflows reused)
What happens automatically: Sales Hub settlement statement extraction confirms sale price. QI escrow receives wired proceeds. System validates the relinquished sale occurred before Day 180 and records the sale event — triggering the 180-day watcher to update its status to "relinquished sold."
Day ≤ 180
EAT Transfer-Out
173 days left
The EAT deeds 456 Sunset Blvd to Matt Belcher. Simultaneously the EAT loan is repaid from QI escrow (relinquished proceeds). This is the money-movement step — four-eyes gated: two authorized officers, the approver never the proposer. Two transactions must happen atomically: deed transfer + loan repayment.
QI Officer ProposerPrepares the deed transfer instruction and escrow release.
Second QI Officer ApproverApprover is never the proposer. No single person can release funds.
Exchanger Acknowledgement · not an approvalRecorded as the exchanger's instruction and receipt of the closing figures. It does not gate or release the wire — an exchanger approval right over qualified-escrow funds is constructive receipt under Treas. Reg. §1.1031(k)-1(g)(6).
What the workflows do:reverse-180day-parking-watcher counts down from Day 0; emits warnings at Day 150 and Day 170; blocks at Day 179 if transfer not initiated. eat-transfer-out is a four-eyes Vectr workflow: it collects two authorized-officer sign-offs — the approver is never the proposer — then atomically issues deed transfer instruction and wire release. Never a single-person action, and never an exchanger sign-off; the exchanger's acknowledgement is recorded alongside the run but is not an input to the release.
After Day 180 · Tax year filing
IRS Form 8824 — Like-Kind Exchanges
The exchanger reports the reverse §1031 exchange on Form 8824 with their tax return. Vectr pre-fills the form from all exchange data: replacement property, relinquished property, dates, prices, recognized gain calculation, and basis adjustment. The CPA reviews and files.
Replacement property (Line 4)456 Sunset BlvdAuto-filled from EAT record
What the workflow does: Triggered by EAT transfer-out completion. Extracts all exchange data from Supabase, runs the §1031(d) basis and recognized-gain calculations, pre-fills Form 8824 PDF, routes to exchanger and CPA for review, then routes to QI for counter-signature as required. Final form stored in exchange record.
Proof: Reverse Exchanges Are Fully Automatable
Every step is deterministic, watchable, document-generating, and approval-gated — the exact shape of a Vectr workflow.
All 8 Vectr workflows covering the reverse exchange lifecycle
3reverse-qeaa-5day-watcherCountdown to 5-business-day QEAA deadline. Day 3 reminder, Day 5 escalation. Trigger: Day 0 timestamp.
WatchAppr
4eat-agreement-generatePre-fills QEAA + EAT loan docs, routes to DocuSign for both parties. Trigger: parking setup complete.
DetDocAppr
5reverse-45day-relinquished-id-watcher45-day countdown for relinquished ID. Day 30 + Day 40 reminders, Day 44 escalation. Trigger: Day 0.
WatchDoc
6reverse-180day-parking-watcher180-day EAT parking countdown. Day 150 + Day 170 warnings, Day 179 block. Trigger: Day 0.
WatchAppr
7eat-transfer-outFour-eyes approval (two authorized officers, proposer distinct from approver), then atomic deed transfer + EAT loan repayment. Never single-party, never exchanger-gated.
DetDocAppr
8form-8824-generatePre-fills Form 8824 from exchange data, routes to exchanger + CPA + QI. Trigger: transfer-out complete.
DetDoc
Why "reverse exchanges can't be automated" is false
The objection is usually that reverse exchanges involve an EAT/SPE-LLC and complex deed logistics that require human judgment at every step.
The reality is that every step in the Rev. Proc. 2000-37 safe harbor is governed by a deterministic rule: form an LLC (deterministic), record a deed (event-driven), sign a QEAA within 5 business days (countdown watcher), identify property within 45 days (countdown watcher), sell within 180 days (countdown watcher), transfer deed with four-eyes QI approval (approval-gated workflow), file Form 8824 (document generation). None of these require human intuition — they require human authorization, which is exactly what approval-gated workflows provide.
The distinction is between judgment and authorization. Automation eliminates judgment bottlenecks (humans missing deadlines, forgetting to send docs, miscalculating dates). It preserves required authorizations — four-eyes QI-officer sign-off on every money movement, the approver never the proposer — because those are legal requirements, not automation gaps. The exchanger never authorizes a fund movement: an approval right over qualified-escrow funds would be constructive receipt.
The conclusion: Reverse exchanges are fully automatable under Rev. Proc. 2000-37. Open1031 + Vectr implement all 8 workflows above. The 45-day and 180-day clocks are durable Vectr timers that never sleep, never miss a reminder, and never fail to escalate.
Open1031 Reverse Exchange Automation Map · Hub Design Language v2 · Rev. Proc. 2000-37 Safe Harbor · Synthetic demo data only · No NPI
Build contract — reverse exchange automation
1 · The parking clock is server-side. The Rev. Proc. 2000-37 safe-harbour windows — the
5-business-day QEAA execution window, the 45-day identification of the relinquished property, and the
180-day parking limit — are computed and watched in Vectr, never in the browser. A page left open cannot
move a statutory date, and no user can extend one. 2 · Deadlines are adjusted, never edited. A statutory date changes only through an
approved four-eyes override carrying a recorded legal basis, written to the audit log. An overdue clock
renders in the danger role with the overrun stated; it can never resolve to a satisfied or green state. 3 · The EAT holds title; the exchanger never does. No code path on this surface lets the
exchanger take title to, or direct funds toward, the parked replacement property. Constructive receipt is a
statutory failure, not a permissions preference. 4 · Every money step is four-eyes, and both eyes belong to the QI. Draw approvals, the EAT
transfer-out and the final disbursement require two authorized officers with an approver who is not the
proposer, enforced in the workflow and in the database, not by a disabled button. The exchanger is never an
approver on a money step and has no fund-movement path: an approval right over qualified-escrow funds is
constructive receipt under Treas. Reg. §1.1031(k)-1(g)(6). Where the exchanger genuinely participates it is
modelled as an acknowledgement or instruction — recorded, non-authorizing, does not gate release — and it
must render visibly distinct from an approval slot (.ack-slot, never
.auth-slot alone). 5 · KYC is the first gate. Nothing downstream — QEAA execution, parking, or funding —
runs until identity and OFAC screening clear. A coordinator can never mark an exchanger's identity verified
on their behalf, and no document is signed on anyone's behalf: e-signature requires the signer's own
intent under the eSign Act and UETA. 6 · Capability pills are a claim about the workflow, not decoration. Deterministic,
watchable, document-generating and approval-gated each map to a named Vectr workflow with a run history.
If a step has no workflow behind it, it does not get a pill. 7 · Tokens only, both themes. The page-local palette and the Tailwind colour utilities are
gone; every colour reads from tokens.css. Reverse-hub indigo is --hub-reverse /
--hub-reverse-ink plus the shared --hub-on foreground — the filled
reverse button takes the on-fill foreground rather than a hardcoded white, which fails AA against the
dark-theme fill. All names, addresses and amounts are synthetic.
