Reporting views¶
Purpose: Explicit taxonomy of the views Xero produces, who each is for, and what each excludes. The remaining failure mode for a single Xero org serving a multi-entity / multi-jurisdiction family office is that "consolidated P&L" silently means different things in different contexts. This file makes the views explicit.
Status: v1, 2026-05-10. Lifted from accounting/accounting-policy.md
§33 into a standalone file for prominence (per Round 4 external-LLM
review).
The six reporting views¶
Every report exported from Xero, every advisor packet, and every generated markdown report should declare which view it represents.
| View | Includes | Excludes | Audience |
|---|---|---|---|
| US Operating View | RFH parent + US disregarded sub-LLCs (W 3101 Holdings, ATX/Austin/Renfroe Marine, Five Points BHM, Renfroe Hospitality Group US shell, Casa Moksha LLC, Casa Moksha Holdings LLC); Brex/Amex/Plaid feed transactions; US-side AP | Foreign statutory books except intercompany cash; personally held assets (W 3603 / Oceana 433); separate-taxpayer entities (RENFROE S-corp, possibly Renfroe Innovation depending on 8832 history) | Day-to-day operational reporting; Austin's monthly visibility |
| Legal Entity View | True legal entity books only — RFH + each disregarded sub-LLC + RHG (foreign corp) + GK (foreign corp, existing + new during transition) + Renfroe Innovation | Personally held assets (W 3603 / Oceana 433) — these are Reporting Units, not legal entities; Consolidation Eliminations | Legal counsel, audit reviewers, anyone who needs entity-by-entity legal precision |
| Austin Consolidated Management View | All business-relevant assets and units; consolidated with elimination JEs applied (per accounting/accounting-policy.md §34); foreign summary JEs flowed in |
Personal lifestyle (Monarch domain); raw foreign-book transaction-level detail | Austin's CEO snapshot; multi-year planning; net-worth visibility |
| Foreign Summary View | RHG/JME and GK/ABS summary JEs only; intercompany clearing | US-side detailed transactions; Mexican CFDI / Japanese GL transaction-level detail (those live in JME's CONTPAQ i and ABS's books, not Xero) | Pearce 5471 prep; quarterly intercompany reconciliation |
| US Tax Support View | Schedule E inputs (per-property rental income + depreciation + expenses); 5471/8858 entity inputs (RHG + existing GK + RI; proposed second GK only if formation executes pre-fiscal-year-end); FBAR threshold inputs (Santander MXN PYME + Santander USD + TSB Mita); 8938 inputs; NOL roll-forward; book-to-tax bridge schedule | Non-tax management presentation adjustments | Pearce + Kim & Rosado |
| Advisor Package View | Tailored exports per advisor: Pearce / JME / ABS / Portilla / Withers / Stuart Memory / Conley Rose | Anything outside the advisor's scope | Per-advisor, per-cadence (per accounting/xero-buildout.md §6.B Advisor export packages) |
Implementation¶
No third Xero tracking category. The five locked decisions hold: - One Xero org for US-side activity - Two tracking categories (Entity / Reporting Unit + Asset Class) - Manual journal lines support max 2 tracking elements per line
Implementation of views is therefore via: 1. Xero report templates — different filters / column sets per view 2. Markdown frontmatter — every generated report carries:
---
reporting_view: us_operating | legal_entity | management_combined | foreign_summary | tax_support | advisor_<name>
period: YYYY-MM | YYYY-Q# | YYYY-FY
confidence_level_dominant: F | P | U
---
Mapping per view¶
US Operating View¶
- Reporting Units included: Renfroe Family Holdings, W 3101 Holdings, ATX Marine Holdings, Austin Marine Holdings, Renfroe Marine Holdings, Five Points BHM, Casa Moksha LLC (post-activation), Casa Moksha Holdings LLC (post-activation), Renfroe Hospitality Group LLC (US shell)
- Excluded: Renfroe Hospitality Group SA de CV (Mexico — only intercompany cash via clearing accounts), both GKs, W 3603, Oceana 433, Renfroe Innovation, Consolidation Eliminations
- Cadence: monthly, 3-business-day close target
Legal Entity View¶
- Reporting Units included: Same as US Operating View + RHG (Mexico) + both GKs (existing + new) + Renfroe Innovation
- Excluded: W 3603, Oceana 433 (Reporting Units that aren't legal entities); Consolidation Eliminations
- Note: each entity's books may be at different confidence levels — RFH-side at [F]/[P], RHG/GK at [P] until summary JEs land
Austin Consolidated Management View¶
- Reporting Units included: ALL — including W 3603, Oceana 433
- Eliminations applied: per policy §34
- Useful for: net-worth visibility, multi-year planning, CEO snapshot
- NOT useful for: tax filings (use Tax Support View) or legal disputes (use Legal Entity View)
Foreign Summary View¶
- Reporting Units included: Renfroe Hospitality Group (RHG MX), Renfroe Holdings GK existing, Renfroe Holdings GK new
- Cadence: quarterly minimum (Path A from JME); GK cadence pending ABS
- Mapped to: Pearce 5471 prep + intercompany reconciliation
- Confidence dominant: [P] until JME §1 framing answer + ABS Mita basis confirmation land
US Tax Support View¶
- Reporting Units included: All US Operating Reporting Units + Renfroe Innovation + summary lines from RHG + GKs + W 3603 (Augusta-rule rentals) + Oceana 433 (if rented)
- Schedule E inputs: per-property rental income/depreciation/expenses for W 3101, W 3603 (Augusta), 210 Lavaca #2612 (personal), Oceana 433 (if rented)
- 5471 inputs: ownership chains, gross receipts, E&P, currency translations for RHG / GK existing / GK new
- FBAR inputs: per-account max balance for Santander MXN PYME, Santander USD (if not closed), TSB Mita
- NOL roll-forward: from
tax/nol-preservation-ledger.md - Cadence: quarterly + annual; year-end and 1040-extension drives much of the timing
Advisor Package View¶
- Per-advisor packets per
accounting/xero-buildout.md§6.B - Each carries source-document references + classification rationale + advisor uncertainty per
accounting/accounting-policy.md§27 - Tailored to scope: Pearce gets US tax slice; JME gets Mexican / intercompany slice; ABS gets GK / Mita slice; Portilla gets RHG legal slice; etc.
Discipline rule¶
Every advisor export, every internal report, every generated
markdown analysis declares its reporting_view in frontmatter.
Mixing views in a single export is a control failure — the consumer
cannot tell what they're reading.
When in doubt about which view: the answer is "create the exports explicitly for each view that's relevant" rather than "produce one mixed view and hope the audience figures it out."
Last updated: 2026-05-10. Refresh whenever the view set changes (new entity → maybe new Reporting Unit → updated mapping; new advisor → maybe new packet → updated Advisor Package View).