ISC · Information Systems and Data Management · 6 practice questions
ERP Data Residency: When Local Laws Govern Deployment
Binding local storage and processing requirements govern ERP deployment even when processes are standardized and centralized hosting is cheaper. Below: compare deployment recommendations and identify which ones respect that constraint.
Try one first
Hint
Focus on which organizational attribute most directly determines whether identical processing and data definitions can be used across all divisions.
Answer B. The principal benefits of a single integrated ERP, fewer reconciliations, consistent data definitions, streamlined intercompany processing, and timelier consolidated reporting, depend on whether divisions can operate under harmonized processes. If core accounting and operational workflows can be standardized, an integrated ERP will deliver the stated priorities; if they cannot, keeping separate systems with robust interfaces may better preserve necessary divisional differences. Cost, legacy applications, and IT staffing are important implementation considerations but are secondary to the strategic feasibility of process standardization.
Why not A: Cost is a major practical constraint and often influential in the final choice, but selecting solely on short-term or even lifecycle cost can undermine the primary objectives (consistent consolidated reporting and reduced reconciliations) if processes remain heterogeneous. Determine process feasibility first, then evaluate cost-effective ways to implement the chosen approach.
Why not C: Specialized legacy apps flag where divisions may have nonstandard processes, making separate systems tempting. However, the real governing question is whether those processes truly require distinct treatments; if they can be aligned or replicated in a central system, legacy status alone should not dictate keeping disparate systems.
Why not D: IT staffing affects implementation risk and may influence the deployment model (e.g., cloud or vendor-managed services), but staffing constraints are typically solvable through outsourcing, phased rollouts, or vendor support. They are an operational constraint rather than the primary strategic factor driving whether standardization is feasible.
What should you do?
The situation
GlobalCo has standardized processes, a common chart of accounts, and effective reporting controls. Two countries require specified financial and customer data to be stored and processed locally. The proposed single centrally hosted ERP would keep that data abroad but costs less. Compliant hybrid and separate-instance designs can preserve common processes, controls, and reliable consolidation. What should govern GlobalCo's deployment decision?
Require local storage and processing compliance first, then compare compliant deployment designs.
Best The laws are binding constraints. They rule out the proposed central design without establishing whether a compliant hybrid or separate instances are preferable.
Use a hybrid deployment that stores and processes all specified data locally as required.
Acceptable This satisfies the legal constraint and preserves common processes and controls. The facts do not establish that it is better than compliant separate instances.
Use separate local instances that satisfy each country's storage and processing requirements.
Acceptable Separate instances can meet local requirements while retaining common policies, workflows, controls, and reliable consolidation. The facts do not favor this design over a compliant hybrid.
Choose the proposed centrally hosted ERP because standardized processes make it cheaper.
Wrong Standardization and cost savings cannot override laws requiring specified data to be stored and processed locally.
Keep local copies of regulated data but process it in the central system abroad.
Wrong Local copies address storage, not processing. The scenario requires both to occur locally.
Key points
- Remember: Standardized processes do not give permission to store or process regulated data outside the required country.
- A hybrid deployment is acceptable only if its local components satisfy both storage and processing requirements.
- Separate instances can retain common workflows, accounting policies, and controls.
- Legal compliance narrows the choices; it does not automatically make one compliant architecture better than another.
How the exam traps you
- Choose central hosting because it costs less. Compare costs only among deployments that meet the local storage and processing requirements.
- Treat common processes and a common chart of accounts as sufficient reasons for one centrally hosted instance. Standardization supports integration, but it cannot override binding local data laws.
- Assume a local data copy makes a hybrid deployment compliant. Confirm that both storage and processing of the regulated data occur locally as required.
Question 2
| Item | Amount |
|---|---|
| Perpetual license for the ERP core software | $500,000 |
| Fees to outside consultants to design and code a custom financial reporting module that adds functionality beyond the standard package | $150,000 |
| Payroll costs for in‑house IT staff who configured the package and performed testing during the development phase | $60,000 |
| Costs to migrate historical customer data into the new system | $30,000 |
| End‑user training before go‑live | $25,000 |
| Cost to apply a post‑go‑live patch that fixed a minor rounding error | $10,000 |
Hint
Determine which activities occurred in the application development stage (costs to create or enhance software functionality) versus those that are data conversion, training, or post‑implementation maintenance, which are normally expensed.
Answer B. Under ASC 350‑40, costs incurred during the application development stage are capitalizable. That includes the purchased on‑premises software license, third‑party fees to design and customize the software, and internal payroll for employees directly engaged in configuration and testing. Data migration/conversion, end‑user training, and routine post‑implementation maintenance (such as a minor patch) are normally expensed.
Why not A: This is tempting because consultants and internal payroll are clearly application development costs, but it incorrectly treats the purchased on‑premises license as an expense. The license cost is part of capitalizable internal‑use software when purchased for on‑premises deployment.
Why not C: Some candidates assume data migration is necessary to make the system usable and therefore capitalizable, but ASC 350‑40 generally requires data conversion/migration costs to be expensed rather than capitalized.
Why not D: This distractor plays on the mistaken idea that only external vendor costs can be capitalized. In fact, internal payroll costs for employees who directly contribute to application development (configuration and testing) are capitalizable under ASC 350‑40.
Question 3
Hint
Which choice most directly reduces the likelihood of a material misstatement in the financial statements?
Answer D. Design choices for accounting processes should be governed primarily by the risk of a material misstatement and the organization's ability to implement effective, consistent internal controls. Given auditor-identified AP deficiencies and a large overpayment, Nova should choose the model that materially reduces the likelihood of fraud or error (for example, by enabling proper segregation of duties, vendor-master governance, and standardized payment authorization). Operational factors such as cost, speed, or implementation timing are important but secondary to reducing financial-statement risk.
Why not A: This distractor tempts because consolidation often yields long-run cost savings; however, cost reduction alone should not override the need to address auditor-reported control weaknesses and potential material misstatement. Where controls and financial-statement risk are at stake, evidence that a design materially improves controls must drive the decision.
Why not B: Project risk is a valid consideration and can influence timing or rollout strategy, but it is not the primary governance criterion when there are known control deficiencies and material error exposure. Avoiding centralization solely to reduce implementation risk would leave inconsistent controls and the underlying financial-statement risk unresolved.
Why not C: This is appealing because local processing can be quicker and preserve autonomy, but those operational benefits do not fix enterprise-wide control deficiencies that led to duplicate payments and a significant overpayment. Prioritizing speed or local control risks leaving material financial-statement exposures unmitigated.
Question 4
Hint
Determine which costs qualify as implementation/application‑development costs under internal‑use software guidance for a hosting (SaaS) arrangement, and remember how capitalized implementation costs for hosting arrangements are amortized (hosting term vs. useful life).
Answer C. Implementation costs in a cloud-based hosting (SaaS) arrangement that would be capitalized under internal‑use software guidance should be capitalized, specifically external implementation vendor fees and internal payroll directly attributable to configuration and testing. Subscription fees for the hosting service and post‑go‑live end‑user training are expensed as incurred. Capitalized implementation costs for a hosting arrangement are generally amortized over the hosting contract term (including any reasonably certain renewals), beginning when the system is ready for use.
Why not A: Tempting because spreading subscription cost over the benefit period seems reasonable; wrong because subscription fees pay for ongoing hosting service and are expensed as incurred, and the internal payroll described is directly attributable to implementation and should be capitalized, not expensed.
Why not B: Tempting because SaaS is a service contract and many students assume no costs can be capitalized; wrong because current guidance requires capitalization of implementation costs that would be capitalized for internal‑use software (external implementation services and internal payroll directly related to implementation).
Why not D: Tempting because capitalized software is often amortized over its useful life; wrong because for implementation costs related to a hosting (SaaS) arrangement the amortization period is generally the hosting contract term (including reasonably certain renewals), not an unrelated longer useful life.
Question 5
Hint
Ask whether the process is indispensable to how the company competes (or legally required); if not, prefer adapting the business to the package rather than customizing.
Answer A. The principal decision driver is whether the process is essential and non‑negotiable (a core competitive capability or a legal/regulatory requirement). If it is truly indispensable, customization may be justified; if not, the company should adapt its processes to standard ERP functionality because customization increases long‑term cost, upgrade risk, and complexity.
Why not B: TCO is an important consideration and rightly discourages customization, but cost is a secondary constraint, it does not override a genuine strategic or regulatory need to preserve a capability.
Why not C: Internal capability affects feasibility and ongoing risk, but having staff does not justify customizing a nonessential process; the core business necessity should govern the decision first.
Why not D: Speed favors using out‑of‑the‑box functionality, but schedule pressures are a tactical factor. The strategic question, whether the process can or should change, should determine whether to customize at all.
Question 6
Hint
Which consideration could legally prevent a centralized ERP even if standardization and cost strongly favor it?
Answer D. Statutory reporting requirements and data‑residency laws are binding constraints that can prohibit a fully centralized ERP if they require local processing or storage of specified data. Legal compliance therefore must be the primary determinant of deployment choice. Operational or cost advantages (and hybrid architectures) can only be considered to the extent they satisfy those legal requirements.
Why not A: Standardization is tempting because it supports consolidation, consistency, and simplified reporting, but it is subordinate to binding legal or regulatory requirements. You cannot rely on standardization to justify noncompliance with statutory reporting or data‑residency laws; a hybrid design might preserve standardized processes while isolating regulated data, but compliance still governs the choice.
Why not B: A hybrid deployment is a practical mitigation and therefore tempting, it often solves mixed regulatory requirements, but it describes a possible solution rather than the governing factor. The primary influence should be whether laws permit or require local processing/storage; those legal constraints determine whether a hybrid is necessary or sufficient.
Why not C: Lower total cost of ownership is an important and persuasive economic factor, yet cost savings cannot override jurisdictional laws. If local statutes mandate storage or processing within the country, cost arguments shift to finding a legally compliant architecture (for example, a hybrid) rather than permitting full centralization.
Common questions
What governs ERP deployment when data residency laws require local processing?
The binding legal requirements govern. Lower central hosting costs and standardized processes cannot justify storing or processing regulated data outside the required country.
Can a hybrid ERP deployment satisfy data residency requirements?
Yes, if the design keeps the specified data stored and processed locally as required. Calling a deployment hybrid does not establish compliance.
Are separate ERP instances better than a compliant hybrid deployment?
The scenario does not establish a winner between them. Both can meet local requirements while preserving common processes, controls, and reliable consolidation.
Watch it solved
A full CPA ISC task-based simulation on Enterprise and accounting information systems, worked step by step.
ISC Simulation: Mapping Controls Through Order-to-Cash on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Enterprise and accounting information systems
- ERP Cores, Hybrid Architectures, and Best-of-Breed
- AP-to-GL Batch Recovery: Fix, Reprocess, and Reconcile
- ERP Revenue Recognition: Shipment vs. Invoice Date
- ERP Vendor Master Data Governance: One Controlled Source
- Auditing ERP Automated Controls: ITGCs and Data Conversion
All Enterprise and accounting information systems practice →
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.