OCBOA
Other Comprehensive Basis of Accounting (OCBOA) is a non-GAAP accounting framework used by some private funds. Common OCBOA variants: modified cash basis (cash transactions plus accrued items), tax basis (financial statements aligned with tax reporting), and regulatory basis (specific to industry-regulated entities). Distinct from US GAAP and IFRS; used when full GAAP would be impractical or non-comparative.
OCBOA appears most often in smaller private funds where US-GAAP-compliance overhead is disproportionate to fund size. A typical scenario: a $50M private fund with 20 LPs and a small operations team. Full GAAP would require quarterly fair-value measurements under ASC 820, accrual accounting for management fees, allocation methodology for unrealized gains, and audited financial statements. OCBOA — typically tax basis — substitutes a simpler framework: the fund tracks income and expenses on a cash-or-near-cash basis, distributes income to LPs on K-1, and the LPs report based on the K-1 numbers rather than the fund's own audited GAAP statements.
The LP-side implication is reporting complexity. An LP receiving K-1 from an OCBOA fund cannot simply compare the fund's reported NAV to GAAP-equivalent fair-value because the OCBOA basis differs. For aggregation purposes (rolling up multiple fund positions into a household-level dashboard), the OCBOA NAV must be either treated as 'as reported' (preserving the lower-detail framework) or restated to fair-value (requiring estimation).
The institutional-investor universe largely avoids OCBOA. Institutional LPs require GAAP financial statements as a condition of investment; OCBOA funds typically have retail or family-office LP bases. The retail-LP segment is fine with the simpler framework — it reduces fund operational costs which translate to lower management fees.
For synthetic-data purposes, OCBOA is mostly a flag: 'this fund reports under OCBOA, treat its NAV as cash-basis-accuracy not fair-value-accuracy'. Aggregation engines should distinguish OCBOA NAVs from GAAP fair-value NAVs in dashboards. Tax-engine code that reads OCBOA-fund K-1s correctly handles the case automatically; portfolio-analytics engines need explicit handling.
Synthetic small-private-fund positions should include an OCBOA flag at realistic frequency (~25% of sub-$100M funds in the data). The flag affects only reporting interpretation, not the tax-character flow-through. Aggregation tests should include both GAAP and OCBOA funds in the same household to exercise the dual-treatment code paths.
Common pitfalls
- Treating OCBOA NAV as comparable to GAAP fair-value — the OCBOA basis can produce values 5–15% off from a comparable GAAP estimate.
- Forgetting that OCBOA is acceptable for some retail/family-office contexts but not institutional investors.
- Letting OCBOA funds skip ASC 820 fair-value measurements — the NAV reported is on the OCBOA basis, not fair-value.
- Aggregating OCBOA and GAAP NAVs without timestamp or basis tagging — produces apparent diversification benefits that don't actually exist.