Assess whether related-party sales should be backed out of valuation (d30cc2)
August 31, 2026
SITUATION In a PE platform evaluating a founder-led SaaS add-on, environmental known-condition schedule is the evidence after IT diligence showing two ERPs and no chart of accounts map. Buy-side QoE lead has to pick Proceed or Reprice for this M&A Due Diligence Earnings and Revenue Quality close using environmental known-condition schedule.
DECISION Buy-side QoE lead in a PE platform evaluating a founder-led SaaS add-on must choose Proceed / Reprice / Walk / Hold using environmental known-condition schedule after IT diligence showing two ERPs and no chart of accounts map.
HYPOTHESES TO TEST 1. Authorize Proceed now; environmental known-condition schedule already has the discriminator after IT diligence showing two ERPs and no chart of accounts map. 2. Keep Reprice in force until environmental known-condition schedule is completed after IT diligence showing two ERPs and no chart of accounts map for buy-side QoE lead. 3. Treat environmental known-condition schedule as Walk because both readings appear after IT diligence showing two ERPs and no chart of accounts map. 4. Refuse a M&A Due Diligence close: buy-side QoE lead does not have the decision related-party sales should be turns on in environmental known-condition schedule.
ANALYSIS REQUIRED 1. Map reps, earnout mechanics, and integration risk a PE platform evaluating a founder-led SaaS add-on would inherit. 2. Tie quality-of-earnings, working-capital, and contingent items in environmental known-condition schedule to related-party sales should be. 3. Name the document buy-side QoE lead still needs before signing. 4. For this M&A Due Diligence Earnings and Revenue Quality file, read environmental known-condition schedule against IT diligence showing two ERPs and no chart of accounts map and write the one fact that would move related-party sales should be for buy-side QoE lead.
RECOMMENDATION Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Earnings and Revenue Quality packet (environmental known-condition schedule after IT diligence showing two ERPs and no chart of accounts map). The follow-on Earnings and Revenue Quality action is what buy-side QoE lead does next: implement the option, assign an owner, and log the missing fact.
COMMAND RETURNS - Bottom-line M&A Due Diligence option on related-party sales should be, then the evidence in environmental known-condition schedule, then the action for buy-side QoE lead - Hypothesis scorecard against environmental known-condition schedule: supported / rejected / untestable - Regulatory or exam hook Earnings and Revenue Quality would cite - Earnings and Revenue Quality finding in environmental known-condition schedule that a second reviewer can re-perform
Explore more
More M&A Due Diligence prompts
- Assess whether earnout definitions will cause a post-close fight (26568e)
- Assess whether regulatory approval is a timing risk or a deal risk
- Assess whether management can run this without the founder from IP ownership
- Whether environmental liability is capped or open-ended from related-party
- Whether working capital should be a walk-away from post-merger
Explore related decision areas
- Assess whether bonus triggers were gamed by cutoff after a whistleblowerForensic Accounting
- Assess whether a warranty should be converted to a condition precedentInsurance Underwriting
- Assess whether to price to win or walk from a buy-in from price-to-win versusGovernment RFP
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

