Assess whether integration costs were sandbagged in the CIM (f494d0)
August 31, 2026 · SmartSolo
Situation
A health-system acquiring a specialty practice cannot treat IT diligence showing two ERPs and no chart of accounts map as color commentary on post-merger systems-integration risk register. Integration-risk PMO must close integration costs were sandbagged from that extract under M&A Due Diligence / Separation and Integration.
Decision
Integration-risk PMO in a health-system acquiring a specialty practice must choose Proceed / Reprice / Walk / Hold using post-merger systems-integration risk register after IT diligence showing two ERPs and no chart of accounts map.
Hypotheses to test
- The population in post-merger systems-integration risk register is the one IT diligence showing two ERPs and no chart of accounts map named, so Proceed follows for this Separation and Integration file.
- The population in post-merger systems-integration risk register is adjacent only to IT diligence showing two ERPs and no chart of accounts map; Reprice is the honest M&A Due Diligence call.
- A health-system acquiring a specialty practice already contained IT diligence showing two ERPs and no chart of accounts map before post-merger systems-integration risk register arrived; no new Separation and Integration path.
- Provenance on post-merger systems-integration risk register after IT diligence showing two ERPs and no chart of accounts map is broken; do not pick Proceed or Reprice yet.
Analysis required
- Name the document integration-risk PMO still needs before signing.
- Test whether IT diligence showing two ERPs and no chart of accounts map is a diligence gap, a price chip, or a walk-away.
- Separate a one-off add-back from a recurring earnings issue in post-merger systems-integration risk register.
- For this M&A Due Diligence Separation and Integration file, read post-merger systems-integration risk register against IT diligence showing two ERPs and no chart of accounts map and write the one fact that would move integration costs were sandbagged for integration-risk PMO.
Recommendation
Choose Proceed / Reprice / Walk / Hold on this M&A Due Diligence / Separation and Integration packet (post-merger systems-integration risk register after IT diligence showing two ERPs and no chart of accounts map). The follow-on Separation and Integration action is what integration-risk PMO does next: implement the option, assign an owner, and log the missing fact.
Explore more
More M&A Due Diligence prompts
- Assess whether related-party sales should be backed out of valuation (43caff)
- Assess whether related-party sales should be backed out of valuation (7c7458)
- Assess whether regulatory approval is a timing risk or a deal risk (309eb6)
- Assess whether the carve-out is operable on day one (ee92eb)
- Assess whether related-party sales should be backed out of valuation (5b09e4)
Explore related decision areas
- Assess whether SAB 99 qualitative materiality is triggered (af4394)Forensic Accounting
- Assess whether Section M scoring math was applied consistently (e12043)Government RFP
- Assess whether cash ever economically changed hands (2b792e)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.

