Related-Party Disclosures Under ASC 850: When Paying Your Spouse's LLC Needs a Footnote

You hired your spouse's marketing LLC for $18,000 this year. Your teenager's lawn-care company mows the office property for $400 a month. Your brother-in-law leases you a warehouse at what you swear is "the family rate." None of these hit your radar as accounting events — they were just convenient, trusted help. Then your bank asks for GAAP financials to renew your line of credit, or a potential buyer opens your books during due diligence, and suddenly every one of those payments needs a footnote. Under ASC 850, it doesn't matter that the price was fair. If the counterparty is related to you, the relationship itself is a required disclosure.

Related-party disclosures trip up profitable small businesses precisely because the transactions feel normal to the owner. This guide explains who counts as a related party, what GAAP actually requires you to disclose, why lenders and investors care so much, and how to build simple bookkeeping habits that make the footnote write itself.

What Counts as a Related Party? More Than Family​

ASC 850, Related Party Disclosures, defines a related party as anyone who can control or significantly influence your company's management or operating policies — enough that you might not pursue your own interests as aggressively as you would with a stranger.

For a small business, that captures far more than you expect:

Family and Close Relations​

• Immediate family: a spouse, parent, child, sibling, in-law, or anyone sharing your household. If you own the business, they are related parties to the business — even if they own nothing themselves.
• Family-owned entities: an LLC, corporation, partnership, or sole proprietorship owned by any of those family members. Paying your spouse's LLC is the classic example. So is renting from an LLC owned by your parents, or buying supplies from your cousin's wholesale company.
• Children's businesses: even small, informal entities count if the dollar amounts are material. The lawn-care example above is material for many micro-businesses.

Business-Side Relationships​

• Owners and key managers: any person who owns 10% or more, plus officers, directors, and anyone who directs policy — and their family members.
• Affiliates and entities under common control: two LLCs you own are related to each other. If you own 60% of Company A and 55% of Company B, a loan between them is related-party.
• Equity-method investees and trusts: entities you account for under the equity method, and benefit trusts (pension, profit-sharing) sponsored by the company.
• Principal owners' other businesses: your 40%-owner's separate consulting firm is related to your company.

The threshold is influence, not ownership percentage alone. A 15% investor who is also your general manager, or a father who guarantees your bank debt, can create a related-party relationship through influence even without a majority stake.

A useful test: would you have chosen this counterparty, at this price, on these terms, if you had shopped the open market with no prior relationship? If the answer is "we didn't shop" or "we gave them preference because of trust," you are likely in related-party territory.

What GAAP Actually Requires You to Disclose​

ASC 850 does not prescribe how to measure or recognize a related-party transaction. It does require you to describe it so a reader can understand the economic reality behind the numbers.

For each material related-party transaction (and for material aggregated groups of similar transactions), disclose four things in the footnotes:

1. The Nature of the Relationship​

Identify who the related party is and how they are related. If knowing the name is necessary to understand the effect, include it. Otherwise "an entity owned by the spouse of the company's majority owner" is often sufficient.

2. A Description of the Transactions​

What was bought or sold, what services were rendered, what was leased, lent, or guaranteed. Include the period covered ("during the year ended December 31, 2026") so the reader knows the scope.

3. Dollar Amounts​

The amount of transactions for each period for which an income statement is presented, and the amount of any balance due to or from the related party at the balance-sheet date. Disclose terms and the manner of settlement when it affects understandability — for example, "payable on demand, unsecured, non-interest bearing."

4. Any Change in Method of Establishing Terms​

If you changed how you set the price or terms versus the prior period, say so.

ASC 850 also contains a critical guardrail: do not state that the transaction was on arm's-length terms unless you can substantiate it. "We paid market rate" is easy to write and hard to prove. Unless you have comparable third-party bids, an appraisal, or a benchmarking study, omit the claim. A footnote that says the transaction occurred, but does not claim it was at fair value, is compliant and safer than an unsubstantiated assertion the auditor must challenge.

What Does Not Need a Separate Footnote​

Routine compensation arrangements, expense allowances, and similar items occurring in the ordinary course of business do not need related-party disclosure just because the employee happens to be related. Your spouse's W-2 wages as a legitimate employee at a documented market rate are compensation, not a related-party transaction requiring the ASC 850 footnote — though officer compensation may be disclosed elsewhere. The gray area is when the "employee" is really a contractor through their own entity; that reverts to related-party.

Separate Presentation on the Face of the Statements​

Beyond footnotes, GAAP expects material related-party balances to be visible. Receivables from officers or affiliates should be shown separately from trade receivables. A $25,000 advance to a shareholder is not "accounts receivable." Revenue from, or the cost of goods sold to, a related party should also be separately identified if material, so a reader is not left reverse-engineering the income statement.

Why Lenders, Buyers, and Auditors Care So Much​

The economic concern behind ASC 850 is straightforward: related-party transactions may not reflect the economics that would exist between independent parties. That cuts both ways, and both concern a capital provider.

1. Earnings quality. If your largest customer is also your brother's company, revenue concentration risk is different than diversification across unaffiliated customers. A buyer will discount revenue that might not survive a change in ownership. If your rent is below market because your parents own the building, EBITDA is overstated relative to what a buyer will actually pay after a market-rate lease.

2. Hidden leverage and guarantees. Loans from owners, advances to affiliates, and personal guarantees are often documented informally or not at all, with oral "pay when you can" terms. A lender needs to know what is really debt, what is equity, and what might be called.

3. Substance over form. Advances booked as "accounts receivable" can mask distributions. Consulting fees to a related entity can be recharacterized as compensation upon audit. The footnote is where you control the narrative by describing substance accurately.

4. Audit and tax cross-checks. GAAP disclosure does not determine tax treatment, but inconsistency does create questions. Related-party losses, above-market rents, and below-market loans have specific tax rules (Section 267 loss disallowance, Section 482, imputed interest under Section 7872). A clean GAAP disclosure that matches the tax return's related-party schedules reduces back-and-forth with both auditor and CPA. Conversely, omitting the disclosure and having it discovered on a bank covenant compliance certificate creates a credibility problem that is harder to fix than the footnote itself.

In 2024 and 2025, audit quality reviews continued to flag omitted related-party disclosures as a common deficiency in small-company audits — not because the dollars were always large, but because the omission suggested a control weakness: the company had no process to identify related parties in the first place.

The Small Business Scenarios That Most Often Get Missed​

These are anonymized patterns that repeatedly surprise owners during their first GAAP audit or sale process:

• The spouse's service provider. Owner pays $2,000/month to a branding agency owned 100% by a spouse. No disclosure because "it's just marketing." Required: nature of relationship, annual amount ($24,000), and $2,000 payable at year-end if unpaid.

• The below-market lease. Owner rents 3,000 sq ft from an LLC owned by parents for $1,200/month when comparable space is $2,800. Booked at $1,200 with no footnote. Required: disclose the lease, annual rent, terms, and related-party nature. Do not claim it is at market without an appraisal.

• The intercompany advance. Owner has two LLCs. LLC 1 lends LLC 2 $45,000 on no written terms, interest-free, to cover payroll. Recorded as "other receivable." Required: separate presentation, amount outstanding, terms (or lack thereof), and that it is interest-free and unsecured. Consider imputed interest for tax even if GAAP does not force remeasurement.

• The child's company. A 19-year-old's S corporation does IT support for $900/month. Parent owns 100% of the parent company. Required: if material in total, disclose the relationship and aggregate amount. Materiality is judged at the financial-statement level, not per invoice.

• The round-trip. Company A sells inventory to Company B (same owner) at a 40% markup to move income between entities. Booked as third-party revenue. Required: disclose that the sale was to a related party and the profit remaining in intercompany inventory must be eliminated in combined statements — and that standalone statements include an intercompany profit that a buyer would eliminate.

Materiality is the filter, but "material" for a small business is lower than founders assume. A $12,000 annual transaction can be material if net income is $40,000, or if the transaction terms would change a lender's decision. When in doubt, disclose. An immaterial disclosure that is later deemed unnecessary is harmless; a material omission that surfaces in diligence is not.

A Bookkeeping Process That Makes Disclosure Automatic​

You cannot disclose what you do not track. Build identification of related parties into your normal bookkeeping, not just at year-end.

Step 1: Maintain a Related-Party List​

Keep a one-page register updated at formation, at each ownership change, and annually. Include:

• Every individual who owns 10%+ or is an officer/director/key manager, plus their immediate family members
• Every entity those individuals own or control (even partially)
• Every entity under common control with the company
• Employee benefit trusts sponsored by the company

Share it with your bookkeeper and CPA. Review it at year-end close — "Did we transact with anyone on this list?"

Step 2: Tag the Accounts​

In your chart of accounts, create separate GL accounts rather than burying related-party activity in general headings:

• Accounts Receivable — Related Parties (not trade AR)
• Accounts Payable — Related Party
• Due From/Due To Affiliate and Due From/Due To Shareholder
• Related-Party Rent Expense, Related-Party Consulting Fees or at least a class/tag that lets you filter them

In Beancount, this maps naturally to distinct accounts like Assets:Receivable:RelatedParty:FamilyLLC or Expenses:Rent:RelatedParty with metadata (related_party: "Spouse LLC") so the footnote population is a query, not a memory exercise.

Step 3: Keep Terms in Writing​

Even for family transactions, draft a one-page agreement: amount or rate, payment terms, duration, interest if a loan, security if any, and renewal terms for leases. This satisfies the "terms" element of the disclosure and gives your auditor something to tie to. Oral advances with no terms are the hardest to disclose cleanly.

Step 4: Reconcile Balances Monthly​

Related-party receivables and payables that sit unreconciled accumulate silently. Reconcile them like bank accounts. Confirm directly with the counterparty at year-end — even if that counterparty is your other LLC — and retain the confirmation.

Step 5: Document Arm's-Length Evidence When You Claim It​

If you intend to state the transaction was at arm's length, retain support contemporaneously: two competing vendor quotes, a broker opinion of market rent, a rate card. Without it, remove the sentence.

What a Good Footnote Looks Like​

Auditors do not expect legal prose. They expect four facts stated plainly. A model for a small company with two transactions:

Related-Party Transactions

During the years ended December 31, 2026 and 2025, the Company purchased branding and web services totaling $24,000 and $22,500, respectively, from an entity 100% owned by the spouse of the Company's majority member. Amounts due to the related entity were $2,000 and $1,500 at December 31, 2026 and 2025, respectively, payable within 30 days.

The Company leases office space from an entity owned by the parents of the majority member under a month-to-month agreement entered in January 2024. Rent expense recognized was $14,400 in each of 2026 and 2025. The Company has not claimed that the lease terms are equivalent to those that would prevail in an arm's-length transaction. No amounts were owed under the lease at either balance-sheet date.

Notice what the note does not do: it does not claim market rates, it quantifies both years, it states payable terms, and it leaves the evaluation to the reader. That is exactly what ASC 850 asks for — transparency, not justification.

For a company that has no material related-party transactions in the period, consider a negative assurance sentence if your lender or audit firm expects it: "The Company had no material related-party transactions during the years presented." It sounds trivial, but it documents that you looked.

Common Mistakes That Turn a Disclosure Footnote Into a Finding​

• Netting instead of gross presentation. Combining related-party sales and purchases into a net number hides volume. Show each direction separately if material.
• Burying owner advances in "Other Receivable." Create a separate line. If it is really a distribution, reclass it to equity before it distorts working capital.
• Forgetting guarantees and commitments. A personal guarantee on a company loan by a related party is a disclosable relationship even if no dollars have been exchanged yet.
• Assuming nonprofits and LLCs are exempt. The standard applies to all entities that present GAAP financials, regardless of tax structure. Even compiled or reviewed statements under SSARS that claim GAAP presentation should include the disclosure.
• Disclosing only one year. Comparative statements require disclosure for each period presented. Forgetting the prior year when you add the current year is a common review comment.
• Inconsistent disclosure across tax and GAAP. Deducting "contract labor — related party" at a different amount than the GAAP footnote without a reconciling explanation invites questions.

The 10-Minute Year-End Checklist​

Copy this into your close procedure:

1. Update the related-party list for ownership, officer, and family changes.
2. Query the GL for any account or vendor tagged as related party; include manual journal entries.
3. Confirm year-end balances with the related party and retain evidence.
4. Quantify aggregate dollars per counterparty per period; assess materiality.
5. Draft the four-element footnote (relationship, description, dollars, balances/terms) for each material group.
6. Remove any unsubstantiated "at fair value" or "arm's length" claim.
7. Verify face-statement presentation: related-party receivables/payables are separate.
8. Tie footnote totals to the trial balance and to the tax return's related-party schedules.
9. Retain written terms (lease, loan, service agreement) for the audit file.
10. Have an owner who is not the preparer review the note for completeness.

An owner who completes these ten steps in December will spend less time explaining the transactions in February than one who discovers them when the auditor asks, "Who is Vendor X?"

Keep Your Related-Party Ledger Audit-Ready​

Related-party transactions are not inherently problematic — most small businesses could not launch without family help, owner advances, or a related-entity lease. The risk is not the transaction itself but the surprise. A footnote that plainly states who, what, and how much converts a perceived concealment into documented governance.

That governance rests on everyday bookkeeping: separate accounts for related balances, consistent tagging, written terms, and monthly reconciliation. Beancount.io gives you a plain-text, version-controlled ledger where Assets:Receivable:RelatedParty and Expenses:Rent:RelatedParty are queries, not month-end searches through a general ledger dump — and where every related-party advance has a date-stamped entry you can show an auditor without exporting a proprietary database.

Simplify Your Financial Management​

As you tighten your related-party process — and the close checklist that supports it — maintaining clear, auditable records is what makes the next financing or diligence request uneventful. Beancount.io provides plain-text accounting that is transparent, version-controlled, and AI-ready, so your related-party trail is always complete and exportable. Get started for free and keep every dollar to family and affiliates traceable.