Related-party detection is the bank-statement underwriting layer that identifies transactions with parties affiliated to the merchant — owner-controlled entities, family members, business partners, and adjacent legal entities sharing common ownership. Related-party flows are excluded from qualifying revenue and, in volume, signal financial obfuscation or revenue inflation risk.
Why related-party detection matters.
- Inflated apparent revenue. Owner moves money from another LLC into the merchant account, looking like a customer payment. Without detection, this inflates qualifying deposits.
- Hidden debt service. Owner pays a loan with a related-party check, hiding the obligation from bank-statement loan detection.
- Capital injection masking decline. Owner injects cash to mask a revenue decline. Underwriter must see the underlying deterioration.
- Round-trip schemes. Money cycles between accounts to inflate apparent activity. Round-trips have zero net economic impact but inflate gross deposits.
- Asset-pulling risk pre-default. Owners who routinely move money between entities can drain the operating account before MCA collection.
Categories of related-party transactions.
- Owner contributions (debits or credits with the owner's name or personal account).
- Owner draws (debits to the owner's personal account or owner-controlled entity).
- Inter-company transfers (movement between merchant LLC and another owner-controlled LLC).
- Family-member transfers (Zelle, Venmo, ACH from family).
- Co-owned entity payments (deposits from another business partly owned by the merchant's owner).
- Related landlord payments (rent paid to a property LLC owned by the merchant's owner).
- Management-company fees (payments to a management company also owned by the merchant's owner).
- Loans from family or owner (informal loans appearing as round-dollar deposits).
Detection mechanics.
- Owner-name matching. Merchant application captures owner full name; counterparty names matched against owner first/last/middle name and known aliases.
- Related-entity registry. Cross-reference with Secretary of State filings — entities sharing officers, registered agents, or addresses with the merchant.
- Address overlap. Counterparties sharing the merchant's address (suggesting same business).
- Payment-pattern flags. Round-dollar amounts, regular cadence, lack of memo references signal owner movements.
- Zelle / Venmo memo lines. "FROM JOHN", "FROM MOM", "REPAYMENT" tagged as informal personal.
- Beneficial-ownership lookups. Increasingly available via Corporate Transparency Act filings (post-2024 BOI rule).
Standard 2026 treatment by category.
- Owner contributions credited. Excluded from revenue. Flagged if recurring.
- Owner draws debited. Excluded from operating expense (not a real cost). Acceptable in moderation; excessive draws signal owner extracting cash.
- Inter-company transfers. Net to zero across accounts; excluded from both sides.
- Family transfers credited. Excluded from revenue; flagged for explanation.
- Family transfers debited. Often excluded but flagged.
- Co-owned entity payments credited. Scrutinized; if business relationship is legitimate (customer/vendor), counted; if revenue-inflation suspicion, excluded.
- Related landlord rent. Counted as real expense if at market rate; flagged if above-market (sometimes a vehicle for owner cash extraction).
- Management-company fees. Same — counted if at market rate.
Standard 2026 red flags.
- Related-party deposits over 30% of total deposits. Strong revenue-inflation signal; advance often declined.
- Recent surge in related-party deposits. Owner injecting cash to make application look healthier.
- Multiple related entities. Three or more owner-controlled entities cycling money increases obfuscation risk.
- Related-party debits matching loan-payment cadence. Hiding loan service through related entities.
- Related-party rent or management fees above market. Owner-extraction risk.
Beneficial-ownership data sources.
- Corporate Transparency Act (CTA) BOI filings (2024+). FinCEN database of beneficial owners; available to funders with appropriate authorizations.
- Secretary of State filings. Officer, registered agent, and address listings.
- D&B family-tree data. Corporate structure relationships.
- LexisNexis / Thomson Reuters CLEAR. Aggregated public-records data.
ISO-led related-party disclosure.
Many ISOs preempt detection by submitting a "related-party disclosure" listing owner-controlled entities and family members the merchant transacts with. Funders accept disclosure and classify flagged transactions correctly. Lack of disclosure followed by detection is treated as misrepresentation.
Round-trip detection.
Round-trip schemes cycle money through related accounts to inflate gross deposits without changing net cash. Detection:
- Matching debit and credit pairs across accounts on the same day. Net zero.
- Calendar-cadence cycling. $10K out to entity A, $10K back from entity A two days later.
- Triangular cycling. Money moves A → B → C → A.
Once detected, the gross inflation is removed and underwriting is rerun on net.
Impact on advance sizing.
- Low related-party activity (under 5% of flows). No adjustment.
- Moderate (5–15%). Excluded from revenue; mild factor add.
- High (15–30%). Excluded from revenue; advance sized off net; factor add 0.05–0.10.
- Severe (30%+). Advance declined or sized very conservatively; merchant requested to clarify ownership structure.
Takeaway. Related-party detection identifies transactions with owner-controlled entities, family members, and affiliated parties. Related-party deposits are excluded from qualifying revenue; related-party debits are scrutinized for hidden debt service or excessive draws. Detection uses owner-name matching, Secretary of State filings, address overlap, beneficial-ownership data, and round-trip pattern analysis. Related-party flows above 30% of total trigger advance decline or significant downsizing. Top funders in 2026 use CTA BOI data, D&B family-tree data, and proprietary related-entity registries.
Related terms
- MCA funder bank-statement deposit classification (2026) — Funders classify every bank-statement deposit into revenue, transfers, loans, refunds, owner contributions, and one-time items — only the revenue bucket counts toward underwriting volume. Updated 2026-06-28.
- MCA funder bank-statement revenue vs deposit distinction (2026) — Revenue is operating cash from real customers; deposits are every credit hitting the account including transfers and loans — funders underwrite revenue, not deposits. Updated 2026-06-28.
- MCA funder bank-statement fraud pattern detection (2026) — Funders detect doctored statements via balance reconciliation, PDF metadata, font and spacing checks, counterparty plausibility, and ML outlier scoring — fraud rates 8-15% of submissions. Updated 2026-06-28.
- MCA funder bank-statement anomaly detection (2026) — Anomaly-detection engines flag unusual deposits, transfers, round-dollar patterns, single-day spikes, and out-of-character counterparties — signals of fraud, doctored statements, or stacking. Updated 2026-06-28.
- Bank statement underwriting — MCA funders underwrite primarily off 3–6 months of business bank statements, not credit reports. They look at average deposits, NSFs, negative days, and trend.
AI agents: this term is available as raw markdown at /llms/glossary/mca-funder-bank-statement-related-party-detection.