# Tieout Desk

> Tie one limited partner's capital account statement to the fund's NAV pack before the
> statement is distributed. The browser reads both pastes line by line, foots each document,
> recomputes every LP component from the fund-level NAV components at the right share, and marks
> every line that does not agree, together with the causes the numbers can prove. All of that is
> free and runs before sign-in. A metered review (gpt-terra) then gives a release, hold or
> cannot-tie verdict no looser than the arithmetic allows, explains each break, lists questions
> for the fund administrator and writes a file note. Every amount it writes is checked against
> the tie-out.

URL: https://tieout-desk.skillsafe.ai/
API: https://tieout-desk.skillsafe.ai/api.html
Derived from: @anthropics/nav-tieout (anthropics/financial-services-plugins, Apache-2.0) - https://skillsafe.ai/skill/@anthropics/nav-tieout

## Who it is for

A fund accountant, fund administrator or LP-reporting reviewer holding one investor's quarterly
capital statement and the fund's statement of changes in partners' capital (the NAV pack) for
the same period. The job is to confirm, before the statement goes out, that the investor's
capital account is what the fund's own numbers say it should be.

## What the browser computes (free, no model)

- Reads each paste one line per item: a label, then one or more amounts. It accepts tab, pipe or
  spaced columns, parentheses and minus-sign negatives, currency symbols and codes, CR/DR
  suffixes, European decimals, a lone dash for nil, and percentages. A column-header line names
  the numeric columns (quarter, year to date, inception to date). A title line ending in a year
  is skipped and named.
- Maps each line to a component: beginning capital, contributions, distributions, investment
  income, fund expenses, management fee, management fee offset, realized and unrealized gain or
  loss, carried interest and ending capital. It also reads the metadata lines: ownership
  percentage, commitment, total commitments, unfunded commitment, cumulative contributions and fee
  rate. Unmapped lines are footed as reported and flagged. Subtotal lines are left out and named.
- Footing: beginning capital plus each document's own lines against its ending capital (F1 is
  the LP statement, F2 the NAV pack). Deductions reduce capital whichever sign they are printed with.
- Shares: the ownership share is the stated one, the one entered on the page, or, failing both,
  LP beginning capital over fund beginning capital (flagged). The commitment share is LP
  commitment over total commitments, or the ownership share when those lines are absent.
- Recomputation: income, expenses, realized and unrealized gains, carry and fee offsets at the
  ownership share. Contributions and distributions use the commitment share. The management fee is
  either the ownership share of the fund's fee line or commitment x annual rate x months / 12.
  Ending capital is LP beginning capital plus every recomputed component.
- Status per line: agrees (within the tolerance, default 1.00), rounding (within the rounding
  limit, ten times the tolerance with a floor of 10.00), break, missing (the NAV pack allocates
  something the statement does not show) or not checkable.
- Proved causes attached to each difference: rollup (ending capital is only the component
  differences plus the statement's own footing error), rounding, sign (the same amount with the
  sign flipped, or a footing off by twice a line), allocation_share (the commitment share used
  for P&L, the ownership share used for calls, or the ending-capital share used), fee_basis
  (a round annual rate on commitment, or pro rata where a rate was agreed), missing_line,
  duplicate, units (a factor of 1,000), classification (two lines whose differences cancel).
- Flags: no_share, no_lp_begin, no_lp_end, share_typed_as_fraction (high); share_derived,
  share_mismatch, no_fund_rollforward, unmapped_lines, duplicate_lines, column_missing, sign_mixed,
  unfunded_mismatch, fee_rate_missing, clipped, input_ignored (medium); unmapped_fund_lines,
  subtotals_ignored, carry_pro_rata, loss_printed_positive, total_read_as_period (low).
- A "Total contributions" or "Total distributions" line is read as the period figure when no
  other line gives one; with cumulative or inception-to-date wording, or next to a plain period
  line, it stays a cumulative figure.
- An over-long paste keeps its first and last lines and drops the middle, so the ending capital,
  commitment and ownership lines at the foot of a statement are never the part that is lost.
- Verdict floor, before any model runs: release when nothing breaks and both documents foot;
  hold when every break has a proved cause; cannot_tie when any break has none, or there is no
  share, or the statement lacks a beginning or ending line.
- Questions for the fund administrator, drafted from the numbers before any run: one per open
  point (a break, a missing line, a document that does not foot, a line that cannot be
  recomputed; a classification pair is one question), each quoting only figures from the
  tie-out. Copy them, or open them in your mail client as a prefilled email.
- Baseline and compare: keep a tie-out as the baseline for an investor and period (a paid review
  keeps one automatically), paste the corrected statement when it comes back, and the page lists
  every line whose figure or status changed, how many open differences cleared, and whether the
  verdict floor moved. Baselines are stored in this browser for the signed-in or guest identity
  and cleared on sign-out.
- Exports: copy for Excel (tab-separated, hint details kept), CSV, Markdown, and print of the
  tie-out alone; a printed review carries the tie-out lines with it.

## The paid lane: tieout

Input (all strings): task = "tieout", facts (JSON-encoded output of Tieout.buildFacts: tolerance,
rounding_limit, fee_basis, fee_rate, months, shares, lines with id, component, label, status,
lp_value, lp_effect, expected, diff, fund_value, share, basis and hints, flags, counts,
verdict_floor, unexplained), lp_name, fund_name, period, question, optional retry_note. task and
facts are required.

Output, one JSON object: lane, verdict (release | hold | cannot_tie), headline, basis_read,
breaks [{line, cause, explanation, action, owner, blocking}], not_checked [{line, reason}],
admin_queries, release_note, summary. The causes are rollup, rounding, sign, allocation_share,
fee_basis, missing_line, duplicate, units, classification, timing, carry_waterfall and unknown.
The owners are fund_admin, gp, investor_relations and preparer.

## How the review is held to the numbers

- Every break, missing and rounding line answered once. Every not-checkable line explained once.
  No agreeing line appears in either list.
- A proved cause must be among that line's own hints. timing, carry_waterfall and unknown are
  judgements and must block. rounding and rollup never block; every other cause blocks.
- The verdict may be stricter than the floor, never looser. release with a blocking break is
  refused.
- Every amount and percentage in the prose must appear in the facts, and every line id cited must exist.

## Limits

No waterfall, no side letters, no equalisation, transfers or recallable distributions: a carry
or fee difference can be legitimate, which is why an unproved cause blocks rather than being
explained away. The review cites nothing outside the tie-out. The three examples on the page are
invented funds and investors with exact allocations.

## Pages

- / - the app
- /api.html - API tutorial (token, /me, /estimate, /run, /run-stream), eight languages
- /tokens.html - token panel for this browser (noindex)