Whether the S-1 disclosure language is still defensible from related-party

SITUATION A live Forensic Accounting Revenue Integrity file in a pre-IPO SaaS company drafting an S-1 now turns on related-party customer map after a Big 4 inquiry on cutoff testing. FCPA investigation lead should state what that extract proves for whether the S-1 disclosure language is still defensible.

DECISION FCPA investigation lead in a pre-IPO SaaS company drafting an S-1 must choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold using related-party customer map after a Big 4 inquiry on cutoff testing.

HYPOTHESES TO TEST 1. Authorize Remove access or reverse the item now; related-party customer map already has the discriminator after a Big 4 inquiry on cutoff testing. 2. Keep Temporary compensating control in force until related-party customer map is completed after a Big 4 inquiry on cutoff testing for FCPA investigation lead. 3. Treat related-party customer map as Approve a documented exception because both readings appear after a Big 4 inquiry on cutoff testing. 4. Refuse a Forensic Accounting close: FCPA investigation lead does not have the decision the S-1 disclosure language turns on in related-party customer map.

ANALYSIS REQUIRED 1. Reconstruct vendor, journal, or inventory lines in related-party customer map through the window opened by a Big 4 inquiry on cutoff testing. 2. Trace approval, SoD, and related-party links that related-party customer map actually shows. 3. Test cutoff, reversals, and system-of-record ties for materiality on the S-1 disclosure language. 4. For this Forensic Accounting Revenue Integrity file, read related-party customer map against a Big 4 inquiry on cutoff testing and write the one fact that would move the S-1 disclosure language for FCPA investigation lead.

RECOMMENDATION Choose Remove access or reverse the item / Temporary compensating control / Approve a documented exception / Hold on this Forensic Accounting / Revenue Integrity packet (related-party customer map after a Big 4 inquiry on cutoff testing). Lead with the Forensic Accounting option related-party customer map can support after a Big 4 inquiry on cutoff testing, then the two facts that force it, then the Monday action for FCPA investigation lead in a pre-IPO SaaS company drafting an S-1.

COMMAND RETURNS - Bottom-line Forensic Accounting option on the S-1 disclosure language, then the evidence in related-party customer map, then the action for FCPA investigation lead - Hypothesis scorecard against related-party customer map: supported / rejected / untestable - Missing page in related-party customer map after a Big 4 inquiry on cutoff testing, if any - Regulatory or exam hook Revenue Integrity would cite