Skip to main content

Sources & Research Methodology

FGL aims to make technical material practical without weakening the evidence behind it. This page explains the research approach used for serious guides, case analyses, case briefs, calculators and other professional resources.

1. Start with the question, not the conclusion

Research begins by defining the practical question, the relevant jurisdiction, the period being analysed and the type of authority needed to answer it. FGL should not search only for material that confirms a preferred conclusion.

2. Source hierarchy

Where available and relevant, FGL generally prefers sources in this order:

  • Primary legal and regulatory material: legislation, regulations, gazettes, court and tribunal decisions, regulator notices and official administrative guidance.
  • Professional standards and standard setters: IFRS Foundation material, recognised auditing or professional standards, and official guidance from professional bodies.
  • Original institutional evidence: audited reports, official inquiries, company filings, board or government reports and published statements from the organisation concerned.
  • High-quality secondary sources: reputable professional-firm commentary, academic work and established journalism used for context, comparison or explanation.

Secondary sources can be useful, but they should not silently replace an available primary source on a material technical point.

3. Tax and regulatory research

For Uganda tax content, FGL should identify the relevant statutory provision, amendment, effective date and current administrative guidance where practicable. A Finance Act, statutory amendment, URA publication or tribunal decision may need to be read together rather than in isolation.

4. Accounting and professional standards

Where an article explains an accounting or auditing standard, FGL should prefer the standard setter or recognised professional authority. Explanatory examples should be clearly presented as illustrations rather than quotations from the standard unless they actually originate there.

5. Court, tribunal and regulator cases

Case analysis should identify the forum, date, parties, issue and procedural status where these are material. FGL distinguishes a party's allegation or submission from a court, tribunal or regulator finding. Settlements are not treated as admissions unless the source says so.

6. Calculations and tools

Material rates, thresholds and assumptions used in FGL calculators should be traced to authoritative sources where possible and reviewed when rules change. A calculator is a planning or learning aid, not an official assessment or filing system.

7. Cross-checking

High-impact technical claims should be checked against more than one source where doing so materially reduces the risk of misreading a rule, date, procedural status or calculation. Apparent conflicts between sources should be investigated and, if unresolved, disclosed.

8. Interpretation and professional judgement

FGL may explain why a rule or case matters in practice. That interpretive layer should be separated from the authority itself. Readers should be able to tell whether a statement is a documented source fact, an attributed view, or FGL's own professional interpretation.

9. Currency and review

Technical content can become stale. FGL therefore records review dates on important evergreen resources and rechecks material when legislation, standards, regulatory practice or the status of a dispute changes.

10. Research limitations

Not every official document is always available online, complete, searchable or current. Where FGL cannot verify a material fact from an adequate source, the gap should be stated rather than filled with assumption.

Comments

Popular posts from this blog

Ernst & Young v URA: VAT on Imported Services and the UGX 3.48 Billion Assessment

Jurisdiction: Uganda · Decision: Commercial Court, Civil Appeal No. 26 of 2022 · Judgment date: 11 June 2026 · FGL review: September 2026 Uganda's Commercial Court has upheld a VAT assessment of UGX 3,482,492,210 against Ernst & Young Uganda in a dispute over services received from non-resident group entities and other foreign service providers. The decision is important because it gives businesses a current judicial example of how Uganda's imported-services VAT rules can apply to cross-border support, technology and professional-service arrangements. What the case was about In Ernst and Young v Uganda Revenue Authority , Civil Appeal No. 26 of 2022, the dispute concerned services obtained from entities outside Uganda, including members of the wider EY network and third-party foreign suppliers. URA treated the services as imported services and assessed VAT for the period January 2014 to June 2018. EY challenged the treatment, including arguments about where the s...

Stanbic-URA Transfer-Pricing Dispute: What Finance Teams Should Learn While the Case Is Pending

Jurisdiction: Uganda · Topic: Transfer pricing and tax dispute management · Status: Pending before the Tax Appeals Tribunal at the time of this FGL review · FGL review: 21 September 2026 Stanbic Bank Uganda Limited and Stanbic Uganda Holdings Limited are contesting a major transfer-pricing assessment by the Uganda Revenue Authority (URA). Public reporting places the working dispute figure at approximately UGX 117.8 billion , and the Tax Appeals Tribunal listed TAT Application No. 170 of 2025 for conferencing in June 2026. This article does not attempt to decide who is right. The dispute is still being litigated. Instead, it uses the publicly available record to explain what finance teams can learn about related-party charges, evidence, tax governance and the management of unresolved assessments. What the dispute is about The dispute arises from URA's review of related-party transactions involving Stanbic's Ugandan operations and entities within the wider...

Reconciling ERP Sales, EFRIS, VAT and Income Tax Returns: A Practical Guide

Scope: Uganda · Topic: Revenue reconciliation across ERP, EFRIS, VAT and income tax · FGL review: September 2026 Sales should be explainable across every system a business uses, but they will not always be numerically identical. An ERP may record invoices and journals, EFRIS records fiscal documents, VAT follows statutory supply rules, financial statements apply accounting standards, and the income-tax return applies tax rules to annual business income. The control objective is therefore not to force all four numbers to match. It is to build a documented bridge that explains why they differ, whether each difference is valid, and what evidence supports it. Why the numbers can legitimately differ A difference can arise from timing, classification, system configuration or tax treatment. Common examples include advance billings, deferred income, unbilled revenue, credit notes, exempt or zero-rated supplies, manual journals, foreign-currency treatment, customer-contra...