Answer
Multi-country solar software must preserve the physical model while making market-specific assumptions explicit. Evaluate weather coverage, equipment documents, units, time conventions, tariffs, export settlement, currency, language, and local review requirements separately. Test a representative project in each intended market. A translated proposal, country dropdown, or code label does not prove regulatory approval or correct savings calculations.
A proposal can be translated correctly while using the wrong export credit or weather dataset. Expanding into another country requires a configuration review, not simply another currency symbol.
Use this guide to evaluate market readiness. It provides a testing framework, not current tariff, incentive, tax, grid-code, or product-availability advice for any country.
Build a market configuration register
Keep shared design practices separate from country, region, utility, and customer assumptions. A country template should identify its sources and exceptions, not hide them.
| Configuration | Record for the intended project | Reviewer |
|---|---|---|
| Location and weather | Coordinates, elevation, dataset, coverage, years, horizon and site evidence | Yield/design owner |
| Equipment | Exact model, document revision, operating limits, local supply and applicable evidence | Equipment/engineering owner |
| Billing and settlement | Customer tariff, effective date, import/export treatment, time periods and applicable fees | Commercial reviewer |
| Financial basis | Currency, tax treatment, ownership perspective, financing, maintenance and escalation assumptions | Financial reviewer |
| Local release | Utility/AHJ process, required drawings, qualified approvals and unresolved conditions | Local project reviewer |
| Presentation | Language, units, date/number formats, disclosures, quote validity and contract entity | Proposal owner |
No single row approves the others. A compatible inverter does not establish export permission; an export permission does not establish subsidy eligibility.
Check weather and modelling conventions
The European Commission’s PVGIS manual describes location-dependent radiation datasets, weather periods, and output conventions. Its grid-connected input uses kWp, while the off-grid input uses Wp. Its azimuth convention is relative to south. Daily profiles can use UTC or local time without daylight-saving adjustment; other datasets and file formats have their own timestamp meanings.
Those differences matter when exchanging files or comparing results. Record the convention for each imported field rather than assuming an angle or timestamp has the same meaning across tools. Verify the model and dataset version actually selected; the documentation is not evidence that another platform uses PVGIS.
The PVWatts V8 documentation distinguishes monthly AC energy in kWh from hourly AC power in W. Compare like output boundaries and periods. Do not apply another inverter or cable loss to a result if that loss is already included at the stated boundary.
For a review project, retain weather identity, array geometry, nameplate capacity, equipment basis, loss assumptions, and output definition. Explain differences between tools before treating them as accuracy rankings. A simulated year is not a guaranteed operating year.
Keep tariff modelling separate from energy yield
Energy production does not determine its monetary value by itself. The same generated energy may offset imports, receive export compensation, be curtailed, or serve storage under different arrangements.
SAM’s financial-model overview distinguishes retail-rate building models from projects selling power, and describes cash flows over an analysis period. That distinction is a useful question for any vendor: whose cash flows are being modelled, and how is produced energy valued? It does not establish current tariff or tax eligibility in another country.
Ask for the customer’s actual tariff and settlement documents, effective dates, and billing basis. Test the configured time periods, export caps or settlement intervals, demand and fixed charges where applicable. Review subsidies and taxes separately using current local evidence; do not transfer one country’s assumptions to another.
A hypothetical tariff test
Assume one annual model allocates 4,000 kWh to 2,500 kWh self-consumed and 1,500 kWh exported. Use invented flat values of 0.20 currency units per self-consumed kWh and 0.05 per exported kWh. The energy value is 575 currency units, not the 800 obtained by valuing all generation at the import rate. The difference is 225 currency units.
This is a software acceptance fixture, not a country tariff, customer savings forecast, or investment recommendation. It excludes timing, demand and fixed charges, taxes, finance, storage, operating costs, curtailment, and other settlement rules. A real configuration needs the applicable billing model and matched consumption/production data.
Test locale and legal documents independently
Check the proposal’s units, decimal separators, dates, currency, tax presentation, customer entity, contracting entity, and equipment identity. Have competent language and local commercial reviewers check material terms. Translation should preserve exclusions, forecast language, warranties, and unresolved conditions.
Record any conversion before display rounding. Never aggregate different currencies without an explicit exchange-rate source, date, direction, and conversion method. Distinguish display conversion from the underlying financial model.
A country dropdown or named standard is not proof of compliance. Ask which checks the current software performs, which are configurable, and which remain outside its scope. Qualified local professionals and the relevant authority must determine project approvals.
Run a controlled new-market pilot
Choose a representative test project and keep the source files. Run design, yield, financial, proposal, permissions, export, and review steps in the intended account configuration.
Reconcile the physical outputs with declared assumptions, the monetary outputs with an independent worksheet or applicable billing test, and the customer document with the approved scope. Assign an owner to each discrepancy. Freeze the accepted configuration and define which changes reopen review: tariff, dataset, equipment, template, model version, or local requirement.
For cross-border teams, agree account roles, support hours, data access and handling, and who may release a proposal for each market. Obtain legal advice on applicable privacy and transfer requirements rather than inferring them from a server location or country label.
Evaluate a workflow with evidence
For solar software integrations, add explicit mappings for units, time and currency. For solar proposal generation, test the actual intended language and financial presentation.
Bring the new-market fixture to a SurgePV demo and request a demonstration of the current supported workflow. Record any custom configuration, unsupported requirement, and local review responsibility in the offer. This guide makes no blanket claim that SurgePV supplies native integrations, automatic country compliance, a current tariff library, or every proposal language.
Frequently Asked Questions
What makes solar software suitable for multiple countries?
The required locations, weather sources, equipment, financial inputs, units, languages, documents, permissions, and local review workflows must be supported and tested. A country list alone does not establish suitability for a project.
Does a country template guarantee solar compliance?
No. A template may contain assumptions or checks, but the applicable law, utility process, equipment evidence, site design, and professional approvals still require project-specific review.
Can the same electricity tariff be used in every market?
No. Specify the actual customer tariff and effective date, import and export treatment, time periods, fixed and demand charges where applicable, and settlement rules. Currency conversion does not make one market tariff appropriate for another.
How should a company launch software in a new solar market?
Start with a representative test project and a documented configuration. Reconcile physical outputs, tariff calculations, proposal wording, equipment scope, permissions, and local review. Approve the configuration and owners before expanding its use.
Sources
Primary research and reference material used for this desk-research article.
Where this fits
This article is part of SurgePV's Solar Business & Operations hub, which works through the topic from first principles to the decisions a project team actually has to make.
