Methodology Guide

What Is the Lowest Intermediate Balance Rule (LIBR)?

A practical guide to commingled-account tracing, balance dips, and attorney-reviewable LIBR workpapers.

Forensic tracing methodology V1 single-claim workpaper Attorney / expert review required Not legal advice
Executive Summary

Tracing separate funds inside one commingled account

The Lowest Intermediate Balance Rule (LIBR) — also discussed as the minimum sum balance or lowest intermediate balance test — is a tracing method used when separate funds are deposited into an account that also holds marital or community funds. Rather than treating every dollar as fungible, LIBR replays the account chronologically and asks how much separate property could still be identified after withdrawals reduce the balance.

The critical step is the lowest intermediate balance: the lowest account balance reached after the separate-property deposit. If the balance dips below the claimed separate amount, the traceable separate-property figure is reduced to that low point. Under the LIBR assumption, later deposits generally do not automatically restore earlier separate-property trace value unless applicable facts and legal theory support a different treatment.

Exit Protocol applies LIBR as a deterministic tracing assumption on selected financial records, then exports an attorney-reviewable workpaper with disclosed calculation settings, a material transaction ledger, source provenance, and SHA-256 snapshot integrity. Attorneys and forensic accountants must decide whether LIBR is appropriate for the jurisdiction, the account history, and the legal theory in the matter.

LIBR is a calculation methodology discussed in tracing literature and case law in some jurisdictions. It is not legal advice, not an expert opinion, and not universally mandated.
Visual Modules

How LIBR replays as a state machine and V1 export path

These diagrams complement the worked example below. They show the chronological LIBR assumption and how Exit Protocol turns selected records into an attorney-reviewable workpaper with integrity surfaces.

Visual Module 01

LIBR state machine

After a separate-property deposit, withdrawals can create a balance dip that caps traceable value. Later deposits do not automatically restore earlier trace under the LIBR assumption.

Swipe horizontally if the diagram extends beyond the screen.

stateDiagram-v2
    [*] --> Baseline: pre-existing balance
    Baseline --> ClaimOpen: separate-property deposit
    ClaimOpen --> Replay: chronological replay
    Replay --> AboveTrace: balance at or above trace level
    Replay --> DipDetected: withdrawal below trace level
    DipDetected --> TraceReduced: cap at lowest intermediate balance
    TraceReduced --> Replay: continue replay
    AboveTrace --> Replay
    Replay --> LaterDeposit: later marital or community deposit
    LaterDeposit --> HoldTrace: account balance rises
    HoldTrace --> FinalRemainder: replay complete
    FinalRemainder --> [*]: export traceable remainder

What it provesLIBR is sequential state logic, not a one-shot formula. The dip transition is the ceiling for traceable separate property unless facts and legal theory support a different method.

What can breakSame-day ordering ambiguity. Missing opening balance. Treating post-dip deposits as replenishment. Spreadsheet row transpositions. Jurisdiction may require direct tracing or another doctrine instead.

Visual Module 02

V1 LIBR workpaper data flow

Exit Protocol's V1 single-claim path from selected account to PDF, Evidence Vault copy, and public verification.

Swipe horizontally to follow the left-to-right export path on tablet widths.

flowchart LR
    A[Selected account] --> T[Transactions]
    T --> C[SeparatePropertyClaim]
    C --> S[Disclosed settings]
    S --> L[LIBR calculation]
    L --> FR[ForensicReport]
    FR --> PDF[Attorney-reviewable PDF]
    PDF --> EV[Evidence Vault]
    PDF --> V["/verify/"]

What it provesReviewers can follow one deterministic path: calculation settings on the workpaper face, material ledger rows, source provenance, and byte-exact verification of the exported PDF.

What can breakLedger totals disagreeing with summary. Calculation settings not visible. Multi-claim scope presented as default V1. Any PDF byte change breaks hash verification — expected, not a platform defect.

Worked Example

How a balance dip limits traceable separate property

The table below uses round numbers for teaching purposes. It illustrates the LIBR assumption that a later marital deposit does not replenish trace value after a withdrawal creates a dip.

Swipe horizontally to view all ledger columns on tablet widths.

Date Event Account Balance LIBR Traceable Amount
Jan 1 Opening balance (pre-existing funds) $5,000
Jan 3 Separate-property deposit $105,000 $100,000
Feb 10 Withdrawal $45,000 $45,000
Mar 1 Later salary deposit (marital/community) $65,000 $45,000
Date Event Account Balance LIBR Traceable Amount
Jan 1 Opening balance (pre-existing funds) $5,000
Jan 3 Separate-property deposit $105,000 $100,000
Feb 10 Withdrawal $45,000 $45,000
Mar 1 Later salary deposit (marital/community) $65,000 $45,000

Account balance rises to $65,000 after the salary deposit, but the LIBR traceable amount remains $45,000 because the lowest intermediate balance after the separate-property deposit was $45,000. Reviewers should treat this as a teaching illustration — real matters require source records, jurisdiction-specific doctrine, and professional judgment.

Balance dip visualization

The red dip marks the lowest intermediate balance. The amber bar shows a later balance increase that does not, under the LIBR assumption, restore the earlier $100,000 trace level.

Why It Matters

Commingled accounts are the default failure mode

In divorce and high-conflict asset disputes, separate inheritances, premarital savings, and business distributions are often deposited into joint or operating accounts. Once commingled, the burden shifts to the spouse claiming separate property to trace those funds with documented support.

  • Manual spreadsheet tracing is slow and vulnerable to ordering mistakes.
  • A single transposed row or balance error can change the traceable remainder.
  • Narrative summaries can outrun the underlying transaction replay.
  • Deterministic replay gives reviewers a inspectable calculation path.
Jurisdiction Note

LIBR is not the only tracing method

Courts and commentators discuss multiple approaches, including direct tracing and family expense or exhaustion methods in some community-property contexts. Texas tracing doctrine, for example, has long emphasized rigorous tracing requirements with jurisdiction-specific case development.

Exit Protocol implements LIBR as a disclosed calculation assumption so reviewers can test it against source records. Whether LIBR, direct tracing, or another method applies is a legal and factual question for counsel and retained experts — not software.

Exit Protocol V1 Workflow

How Exit Protocol applies LIBR deterministically

Exit Protocol converts selected financial records into a V1 single-claim LIBR workpaper. The platform does not silently substitute narrative for math. Each stage is inspectable.

  1. User selects the account or financial record to analyze.
  2. Transactions are normalized into consistent dated ledger rows.
  3. Opening balance, deposits, withdrawals, and closing balance are reconciled.
  4. A separate-property claim is opened on the selected account.
  5. The selected same-day ordering mode is applied deterministically.
  6. A material transaction ledger is generated for review.
  7. The workpaper discloses methodology, source provenance, snapshot SHA-256 integrity, traceable remainder, and final file hash verification for generated exports.

Disclosed settings

The selected same-day ordering mode and engine version appear on the workpaper face.

Material ledger rows

Key transactions that moved the separate-property trace.

Source provenance

Supporting rows linked to selected statements or exports.

Ordering & Assumptions

Calculation assumptions, not legal conclusions

When same-day transactions or ordering ambiguity exist, Exit Protocol exposes mechanical ordering modes so reviewers can compare sensitivity scenarios. These settings change calculation order — they do not favor a party or decide legal ownership.

Recorded-order replay

Preserves source row order where available, then uses stable creation and record identifiers as deterministic tie-breakers.

Deposits-first same-day scenario

Places positive amounts before withdrawals on the same date to expose one boundary of timestamp ambiguity.

Withdrawals-first same-day scenario

Places withdrawals before positive amounts on the same date to expose the other boundary of timestamp ambiguity.

Boundary

What LIBR does not decide

  • Legal ownership of any asset or account
  • Witness credibility or intent
  • Whether records are complete or authentic
  • Whether a court will accept the tracing method
  • Whether an expert must testify
  • Whether jurisdiction-specific doctrine supports the argument
V1 Scope

Single-claim workpaper boundary

Exit Protocol's V1 LIBR workpaper export is scoped to single-claim accounts. Multi-claim pro-rata workpapers require separate review and are not presented as the default V1 workpaper path.

The output is attorney-reviewable. It is not legal advice and not an expert report.

Comparison

Manual spreadsheet tracing vs. Exit Protocol LIBR workpaper

Swipe horizontally to compare all review surfaces on tablet widths.

Review surface Manual spreadsheet tracing Exit Protocol LIBR workpaper
Transaction replay Depends on reviewer discipline and formula hygiene Deterministic replay from normalized ledger inputs
Visible assumptions Often buried in hidden tabs or ad hoc notes Calculation settings and methodology disclosed on workpaper face
Material ledger Manually filtered; easy to omit key rows Generated material transaction ledger for inspection
Source provenance Frequently detached from final totals Rows linked to selected source records
Snapshot hash Typically absent SHA-256 snapshot integrity at export time
Export verification Manual version control Final file hash verification for generated exports
Professional review boundary Still requires counsel or expert review Still requires counsel or expert review — software organizes review material; it does not substitute for professionals
Review surface Manual spreadsheet tracing Exit Protocol LIBR workpaper
Transaction replay Depends on reviewer discipline and formula hygiene Deterministic replay from normalized ledger inputs
Visible assumptions Often buried in hidden tabs or ad hoc notes Calculation settings and methodology disclosed on workpaper face
Material ledger Manually filtered; easy to omit key rows Generated material transaction ledger for inspection
Source provenance Frequently detached from final totals Rows linked to selected source records
Snapshot hash Typically absent SHA-256 snapshot integrity at export time
Export verification Manual version control Final file hash verification for generated exports
Professional review boundary Still requires counsel or expert review Still requires counsel or expert review — software organizes review material; it does not substitute for professionals
FAQ

Common questions from attorneys and forensic accountants

What does LIBR stand for?

LIBR stands for Lowest Intermediate Balance Rule. It is a commingled-account tracing method that models a traceable remainder no higher than the lowest balance reached after an identified source deposit. Legal treatment remains jurisdiction- and fact-dependent.

Is LIBR legal advice?

No. This page is educational. Exit Protocol applies LIBR as a deterministic calculation assumption inside structured workpapers. Counsel and retained experts must decide whether the method fits the matter.

Does LIBR apply in every jurisdiction?

No. Tracing standards vary. Some discussions emphasize direct tracing, family expense or exhaustion methods, or lowest intermediate balance approaches depending on state law and facts. Confirm applicable doctrine before relying on any tracing output.

Why does a later deposit not automatically restore traceable value?

Under the LIBR assumption, once withdrawals reduce the account below the separate-property trace level, the traceable amount is capped at the lowest intermediate balance. Later deposits do not automatically replenish earlier separate-property trace value unless applicable facts and legal theory support different treatment.

What is a “red dip”?

In reviewer shorthand, a red dip is the point where the running balance falls below the separate-property trace level after a separate-property deposit. That low point often becomes the LIBR ceiling for traceable separate funds in the worked example.

What does Exit Protocol export?

A V1 single-claim attorney-reviewable LIBR workpaper with disclosed calculation settings, material ledger rows, source provenance, snapshot SHA-256 integrity, traceable remainder, and final file hash verification for generated exports.

Can the workpaper be verified?

Generated exports from live matters can be checked against stored snapshot and file hashes through the platform's verification surfaces. Static synthetic demo files are for workflow evaluation and may not appear in the public integrity ledger unless the exact bytes match a stored export.

Is this an expert report?

No. The workpaper is structured review material. It is not an expert report, not legal advice, and not a court filing.

How does this connect to Clio?

Users of Clio Manage can authorize access, choose a matter and source document, and stage extraction candidates for explicit local review. Staging does not import a ledger, run LIBR, generate a workpaper, or upload a result. After separate row approval and source confirmation, the staging user may explicitly run LIBR, save the local workpaper, and attempt to upload a new PDF to the selected matter. This is not a Clio endorsement, approval, or certification claim.

What happens with multiple separate-property claims?

Exit Protocol's V1 LIBR workpaper export is scoped to single-claim accounts. Multi-claim pro-rata workpapers require separate review and are not presented as the default V1 workpaper path.

Further Reading

Research sources consulted for this guide

  • See v. See, 64 Cal.2d 778 (1966) — California Supreme Court discussion of tracing burdens, acquisition-time proof, and adequate recordkeeping after commingling. It is background for California tracing principles, not a specification of Exit Protocol's LIBR algorithm.
  • In re Marriage of Walrath, 17 Cal.4th 907 (1998) — addresses Family Code section 2640 tracing of separate contributions through refinanced property into later assets. The opinion notes that different tracing methods apply to commingled bank accounts, so it is not presented here as authority for the product's LIBR formula.
  • Charles J. Fitzpatrick, The Commingling of Separate and Community Funds: The Requirement of Tracing in Texas, 6 St. Mary's L.J. (1974) — Texas-specific tracing and commingling analysis.
  • Forensic and family-law educational summaries describing direct tracing, family expense/exhaustion methods, and minimum sum balance / lowest intermediate balance approaches (methods vary by jurisdiction).

These sources inform the educational framing of this page. They do not constitute legal advice, and they do not mean LIBR applies in every matter or jurisdiction.

Professional disclaimer. This page is educational and product-oriented. It is not legal advice, not an expert opinion, not a court filing, and not a guarantee of admissibility. LIBR and related tracing doctrines are jurisdiction-specific and fact-dependent. Attorneys and retained experts must review all source records, assumptions, calculations, and conclusions.