Assess whether to re-trade, restructure, or drop from related-party revenue
August 31, 2026
SITUATION The working file is related-party revenue that disappears at close after IT diligence showing two ERPs and no chart of accounts map. Customer-contract risk reviewer in a cross-border deal with earnout-heavy structure has to name To re-trade, restructure, or Drop for this M&A Due Diligence Earnings and Revenue Quality file.
DECISION Customer-contract risk reviewer in a cross-border deal with earnout-heavy structure must choose To re-trade, restructure, / Drop using related-party revenue that disappears at close after IT diligence showing two ERPs and no chart of accounts map.
HYPOTHESES TO TEST 1. Customer-contract risk reviewer can defend To re-trade, restructure, from related-party revenue that disappears at close after IT diligence showing two ERPs and no chart of accounts map in a M&A Due Diligence challenge. 2. Customer-contract risk reviewer cannot defend To re-trade, restructure, from related-party revenue that disappears at close; Drop is what the extract actually supports after IT diligence showing two ERPs and no chart of accounts map. 3. IT diligence showing two ERPs and no chart of accounts map never reached the population in related-party revenue that disappears at close — reopen intake, do not close to re-trade, restructure, or drop. 4. Two facts in related-party revenue that disappears at close after IT diligence showing two ERPs and no chart of accounts map conflict for customer-contract risk reviewer; hold this Earnings and Revenue Quality file.
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 cross-border deal with earnout-heavy structure would inherit. 3. Tie quality-of-earnings, working-capital, and contingent items in related-party revenue that disappears at close to to re-trade, restructure, or drop. 4. For this M&A Due Diligence Earnings and Revenue Quality 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 to re-trade, restructure, or drop for customer-contract risk reviewer.
RECOMMENDATION Choose To re-trade, restructure, / Drop on this M&A Due Diligence / Earnings and Revenue Quality packet (related-party revenue that disappears at close after IT diligence showing two ERPs and no chart of accounts map). The follow-on Earnings and Revenue Quality action is what customer-contract risk reviewer does next: implement the option, assign an owner, and log the missing fact.
COMMAND RETURNS - Bottom-line M&A Due Diligence option on to re-trade, restructure, or drop, 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 - Owner and next date for customer-contract risk reviewer in a cross-border deal with earnout-heavy structure - What changes to re-trade, restructure, or drop if IT diligence showing two ERPs and no chart of accounts map is later withdrawn
Explore more
More M&A Due Diligence prompts
- Assess whether related-party sales should be backed out of valuation (d90ddb)
- Integration-risk PMO must resolve whether IP is owned or merely licensed
- Assess whether to re-trade, restructure, or drop from carve-out stranded-cost
- Assess whether integration costs were sandbagged in the CIM after a TSA that
- Assess whether the carve-out is operable on day one from related-party
Explore related decision areas
- Assess whether cash ever economically changed hands (0a74c1)Forensic Accounting
- Protest-risk counsel's technical counterpart must resolve whether the SBIRGovernment RFP
- Is Referral to Counsel Warranted?Forensic Accounting
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.

