Skip to main content
FGL Knowledge Desk · Digital finance

Systems & Automation

ERP controls, data migration, reconciliations, Excel, automation and responsible technology use for finance teams.

ERP & migrationAutomationData & reconciliationControls first

Technology is useful when it improves the reliability, speed and traceability of finance work. This desk focuses on systems from the finance perspective: controls, reconciliations, data quality, migration, automation and professional judgment.

ERP systems and finance controls

ERP implementation is not only a technology project. It changes evidence, approvals, reconciliations and the control chain supporting financial reporting.

Finance automation

Automate repetitive work deliberately, while keeping controls, validation and ownership visible.

Data migration and reconciliation

A migration is complete only when opening data can be reconciled, explained and relied upon in the new system.

FGL systems principle: the objective is not automation for its own sake. A good finance system should make transactions easier to process, exceptions easier to see, reconciliations easier to complete and evidence easier to retrieve.
Need the legacy chronological feed?Browse the automation label archive →

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...