Finance shared services needs coordinated year-end testing across many controls at once. What should the compliance lead configure?
Select an answer to reveal the explanation.
Short Explanation
Year-end is a wave, not twenty forgotten onesies. Stand up a multi-control testing campaign for finance shared services so the work moves together. Random December tests, postponing past close, or coin-flip sampling will not impress auditors.
Full Explanation
Testing campaigns coordinate many control tests across a defined scope and timebox such as year-end. Configuring a multi-control campaign for finance shared services aligns due dates, ownership, and reporting so civic finance close activities receive coordinated compliance assurance. Opening unrelated one-off tests randomly throughout December with no campaign structure fails by concept because uncoordinated tests lack shared status, coverage tracking, and management visibility for period-end. Postponing all finance testing until after the fiscal year closes fails by concept because evidence needed for close and audit readiness arrives too late to support stewardship of public funds. Testing only one control per year and sampling the rest with coin flips fails by concept because arbitrary undersampling does not demonstrate designed period-end coverage. Exam caveat: CIS-RC uses testing campaigns to orchestrate multi-control period work rather than ad-hoc or deferred testing. Operational check: create a year-end testing campaign scoped to finance shared service controls, assign due dates inside the close window, and verify campaign reporting shows completion status across the included controls before fieldwork.