Assess whether related-party sales should be backed out of valuation (9a138d)

SITUATION Integration-risk PMO in a roll-up of three regional service companies has one working extract — related-party revenue that disappears at close — after IT diligence showing two ERPs and no chart of accounts map. Integration-risk PMO in a roll-up of three regional service companies has related-party revenue that disappears at close after IT diligence showing two ERPs and no chart of accounts map. If that extract cannot support related-party sales should be, the only defensible M&A Due Diligence Legal, IP, and Regulatory output is hold.

DECISION Integration-risk PMO in a roll-up of three regional service companies must choose Proceed / Reprice / Walk / Hold using related-party revenue that disappears at close after IT diligence showing two ERPs and no chart of accounts map.

HYPOTHESES TO TEST 1. The population in related-party revenue that disappears at decision is the one IT diligence showing two ERPs and no chart of accounts map named, so Proceed follows for this Legal, IP, and Regulatory file. 2. The population in related-party revenue that disappears at close is adjacent only to IT diligence showing two ERPs and no chart of accounts map; Reprice is the honest M&A Due Diligence call. 3. A roll-up of three regional service companies already contained IT diligence showing two ERPs and no chart of accounts map before related-party revenue that disappears at close arrived; no new Legal, IP, and Regulatory path. 4. Provenance on related-party revenue that disappears at close after IT diligence showing two ERPs and no chart of accounts map is broken; do not pick Proceed or Reprice yet.

ANALYSIS REQUIRED 1. Separate a one-off add-back from a recurring earnings issue in related-party revenue that disappears at close. 2. Map reps, earnout mechanics, and integration risk a roll-up of three regional service companies would inherit. 3. Tie quality-of-earnings, working-capital, and contingent items in related-party revenue that disappears at close to related-party sales should be. 4. For this M&A Due Diligence Legal, IP, and Regulatory file, read related-party revenue that disappears at close 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 integration-risk PMO.

RECOMMENDATION Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Legal, IP, and Regulatory packet (related-party revenue that disappears at close after IT diligence showing two ERPs and no chart of accounts map). The follow-on Legal, IP, and Regulatory action is what integration-risk PMO 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 related-party revenue that disappears at close, then the action for integration-risk PMO - Hypothesis scorecard against related-party revenue that disappears at close: supported / rejected / untestable - Legal, IP, and Regulatory finding in related-party revenue that disappears at close that a second reviewer can re-perform - Missing page in related-party revenue that disappears at close after IT diligence showing two ERPs and no chart of accounts map, if any