One group, different countries: plan it in Frappe ERP

At a glance

Frappe ERP gives a group company-specific records and base currencies within a shared application model. Use that structure to repeat useful processes while keeping legal-entity responsibilities clear. Confirm local tax and e-invoicing requirements separately, with evidence for each country before launch.

Give each entity clear records

Your group buys centrally, but the invoice belongs to a local subsidiary. The warehouse needs the goods while finance needs the purchase in the right company. Frappe ERP supports separate Company records with company-specific defaults and base currencies. Start there, then build a shared process that respects who owns each transaction.

Frappe's Company setup distinguishes separate entities from branches or other structures within a company. Have finance approve that distinction for your organization. A clear entity map gives the implementation team a place to assign accounting responsibility before configuring the shared process.

For a rollout spanning the United States, Canada, African markets, Indonesia, Malaysia or Egypt, prepare a country-by-country evidence file. Africa is not one tax jurisdiction. A tested process in Kenya says nothing by itself about the requirements of a company in Egypt or South Africa.

Reuse what works across borders

Reuse the parts of the process that work across your group. A shared item-coding policy can make purchasing easier to coordinate, while local invoice numbering or tax treatment may need separate rules. Mark each decision as group policy, local configuration or a dependency needing external review. That record helps the next country team see what it can reuse.

Frappe documents company-specific accounting and operating defaults, and notes that inter-company sales and purchases still need recording in the relevant entities. Ask finance to walk through a cross-company transaction. Agree how differences will be investigated before group reporting begins.

Keep a shared process unless there is a reason to vary it. A mandatory local requirement can block launch; a preferred report layout usually should not. Record the difference and its maintenance cost rather than forcing the local team to accept it or quietly creating another version.

Give local requirements an owner

Give local teams a defined way to approve the shared design. For each obligation, identify the current authority source, the person interpreting it and the software component expected to implement it. Company setup is not evidence of regulatory readiness. This article does not verify any particular country's current tax rules or connector coverage.

Your local finance adviser should confirm the applicable registrations, tax treatment and required outputs. The implementation team should demonstrate how the configured system produces those outputs. If an external service is involved, record its supported version and failure behavior.

For e-invoicing where applicable, test the entire lifecycle required by the jurisdiction, not only creating a PDF. Ask how submission status, rejection and corrections will be recorded. Whether those steps are required, and in what form, must come from current official local guidance rather than a vendor's general brochure.

• Record the jurisdiction and legal entity beside each requirement.
• Attach the current authority source and the local reviewer's interpretation.
• Grade the implementation as standard behavior, configuration, custom work or an external service dependency.
• Keep failed and successful test evidence. An unanswered question stays unresolved; it does not become assumed compliant.

Make each company explainable

Frappe Company records have a base currency, and the setup documentation calls for appropriate accounts and exchange rates for foreign-currency and cross-company activity. Use that structure to make each entity's amounts explainable before comparing group results. Name who approves the exchange-rate source and who investigates differences.

Test an invoice and its settlement using the currencies your business actually uses, such as USD, CAD, IDR, MYR or EGP. These are examples of test currencies, not a claim that every local accounting treatment is preconfigured. Ask the accountant to approve the resulting entries.

Separate statutory reporting from management reporting. A group dashboard may use a common currency and account grouping, but it does not replace local books. Frappe provides accounting reports such as General Ledger and Trial Balance; report availability alone does not certify their local presentation or treatment.

Currency example (hypothetical, not an ERPNova result or a current exchange rate): a company with MYR as its base currency records a USD 10,000 supplier liability at an assumed MYR 4.50 per USD, or MYR 45,000. It settles at an assumed MYR 4.60, paying MYR 46,000. The MYR 1,000 difference is an exchange loss in this simplified case, with no fees or prior revaluation. Have local finance approve the actual posting rules before using the example as a test.

Make it work for local users

Let the local receiver test the process, not only the English-speaking project team. A familiar label and a readable printed document make the configured workflow easier to follow. Include Bahasa Indonesia, Bahasa Malaysia, Arabic or French where the actual operation needs them, and record the terms local staff want to use.

Test addresses and names with real character sets using anonymized examples. Frappe's data-import documentation calls out UTF-8 encoding for non-English characters. Check the resulting record and printed output, not just whether the import finished.

Frappe provides role-based and document-level permissions. Use ordinary accounts to test entity boundaries, exports and access to sensitive records. Legal and security advisers should separately assess data location and contractual requirements; this guide does not promise privacy compliance.

Carry the learning forward

Use the first entity as a working reference for the next rollout. Keep the approved process and its tests, then record the local differences before copying configuration. A pilot can make later decisions more concrete, but each country still needs acceptance criteria for its own operating and legal requirements.

Set support hours around the local working day. Name who follows changes in official requirements and who updates the affected components. Passing an e-invoice test at launch does not remove the need to retest after a rule or connector changes.

Bring ERPNova your entity map and one transaction that crosses company boundaries. In an ERP audit, we can assess the shared Frappe ERP design and identify configuration or integration work. Country-specific statutory advice and coverage must be confirmed for the proposed scope. Use the implementation roadmap for launch gates and the integration guide for external-service acceptance.