Assess whether related-party sales should be backed out of valuation (429a59)
August 31, 2026
SITUATION In a public acquirer facing HSR and sector regulators, related-party revenue that disappears at decision is the evidence after add-backs that are just delayed opex. Customer-contract risk reviewer has to pick Proceed or Reprice for this M&A Due Diligence People and Contracts close using related-party revenue that disappears at close.
DECISION Customer-contract risk reviewer in a public acquirer facing HSR and sector regulators must choose Proceed / Reprice / Walk / Hold using related-party revenue that disappears at close after add-backs that are just delayed opex.
HYPOTHESES TO TEST 1. The population in related-party revenue that disappears at decision is the one add-backs that are just delayed opex named, so Proceed follows for this People and Contracts file. 2. The population in related-party revenue that disappears at close is adjacent only to add-backs that are just delayed opex; Reprice is the honest M&A Due Diligence call. 3. A public acquirer facing HSR and sector regulators already contained add-backs that are just delayed opex before related-party revenue that disappears at close arrived; no new People and Contracts path. 4. Provenance on related-party revenue that disappears at close after add-backs that are just delayed opex is broken; do not pick Proceed or Reprice yet.
ANALYSIS REQUIRED 1. Name the document customer-contract risk reviewer still needs before signing. 2. Test whether add-backs that are just delayed opex is a diligence gap, a price chip, or a walk-away. 3. Separate a one-off add-back from a recurring earnings issue in related-party revenue that disappears at close. 4. For this M&A Due Diligence People and Contracts file, read related-party revenue that disappears at close against add-backs that are just delayed opex and write the one fact that would move related-party sales should be for customer-contract risk reviewer.
RECOMMENDATION Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / People and Contracts packet (related-party revenue that disappears at close after add-backs that are just delayed opex). Lead with the M&A Due Diligence option related-party revenue that disappears at close can support after add-backs that are just delayed opex, then the two facts that force it, then the Monday action for customer-contract risk reviewer in a public acquirer facing HSR and sector regulators.
COMMAND RETURNS - Bottom-line M&A Due Diligence option on related-party sales should be, then the evidence in related-party revenue that disappears at close, then the action for customer-contract risk reviewer - Hypothesis scorecard against related-party revenue that disappears at close: supported / rejected / untestable - Named option among Proceed, Reprice, Walk and the fact that kills the others - Owner and next date for customer-contract risk reviewer in a public acquirer facing HSR and sector regulators
Explore more
More M&A Due Diligence prompts
- Assess whether regulatory approval is a timing risk or a deal risk (e410dd)
- Assess whether a top customer is actually sticky after a Phase II that found
- Assess whether management can run this without the founder after add-backs
- Assess whether earnings quality supports the bid price (07f4c2)
- Assess whether related-party sales should be backed out of valuation (0dccea)
Explore related decision areas
- Assess whether the S-1 disclosure language is still defensible (c84086)Forensic Accounting
- Assess whether the pattern is timing, error, or scheme (8af696)Forensic Accounting
- Assess whether a modification is in-scope or a new procurement (7e134e)Government 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.

