Sage Intacct Implementation Lead

About Fika

Fika (formerly "Bridges to Prosperity") advances innovative, cost-effective rural infrastructural solutions through advocacy, evidence, and technical assistance to promote safe access for geographically isolated communities through partnership with governments and donors. Our evidence-based approach demonstrates that safe, reliable access unlocks opportunity and drives economic and social development in rural areas.

Job Purpose

The Sage Implementation Lead is a time-bound delivery role responsible for completing Fika’s Sage Intacct implementation beyond the core accounting foundation. Fika went live on Sage Intacct in Q2 FY26. Phase I, covering the general ledger & core accounting configuration, has been led by a member of the in-house Finance team & is nearing completion. The four remaining phases move the implementation outward from accounting configuration into integration, compliance, & operational territory, crossing Finance, Business Development, Programs, Compliance, & Information Systems. This role exists to carry that cross-functional delivery so that the Finance team can stay focused on operating the system it now depends on.

The role designs the integration architecture for the phases in scope & then delivers against it. Where the business & functional requirements for a phase have not yet been documented, the role facilitates & drafts them with the owning department before design begins. Requirements ownership & approval remain with the department; producing the documented requirement set is part of this role's delivery scope. Design authority is exercised under approval: the Implementation Lead produces the architecture, data flow, & configuration approach for each phase, & the Director of Enterprise Platforms reviews & signs off before build begins. That sign-off exists to keep each phase consistent with Fika’s org-wide platform architecture & multi-year systems roadmap, which the Director owns. Within an approved design, the Implementation Lead makes the technical decisions.

This is also a build-and-hand-off role. Over 12 months the Implementation Lead delivers Phases II through V & leaves behind design documentation, trained users, & named internal owners for every module, so that Fika does not require a successor contract.

Phases in Scope

Phase I is closing out under Finance leadership and sits outside this role’s scope, though the Implementation Lead inherits its configuration decisions and constraints. Requirements maturity varies by phase. Phase I was delivered in house and its requirements exist largely as configuration history rather than documentation. Phases II-V should be assumed to require requirements definition from a standing start.

Phase Module Timeframe

II Salesforce Integration FY26 Q4

III Banking and Integration FY27 Q1

IV Grants Management FY27 Q2

V Warehouse and Project Billing FY27 Q3

One technical question the role inherits: the Divvy and BILL integration proved limited enough that Finance chose to keep using a journal entry import in order to retain both Project and Grant dimensions. Assessing whether Phase III changes that decision is part of the work. The Gusto payroll integration is operational and posts directly into Sage.

Duties & Responsibilities

Integration Architecture & Technical Delivery (30%)

Design the Salesforce to Intacct integration architecture, covering object and field mapping, dimension alignment, error handling, reconciliation logic, and failure recovery. Present the design to the Director of Enterprise Platforms for review and sign-off before build begins.

Design the Phase III banking and payment integration architecture, including a recommendation on whether it replaces or supplements the existing journal entry import, and secure sign-off on that recommendation.

Design the configuration approach for grants management, warehouse, and project billing, working from business requirements approved by the owning departments, and facilitating and drafting those requirements where they do not yet exist.

Design every phase so that dimensional integrity, particularly Project and Grant, is preserved end to end, and document the data mapping that proves it.

Present designs with the options considered and the trade-offs rejected, so that sign-off is an informed decision rather than a formality. Where a design conflicts with Fika’s org-wide integration standards, raise it to the Director rather than resolving it locally.

Route material design changes discovered during build back to the Director for re-approval rather than absorbing them silently.

Deliver the technical build in partnership with the Salesforce Lead and Salesforce Administrator once design sign-off is secured.

Requirements Definition, Phase Delivery & Implementation Management (30%)

Facilitate requirements definition for each phase with the owning department, producing a documented business and functional requirement set covering process, data definitions, dimensional needs, reporting outputs, and control implications. The owning department approves the requirement set; this role drafts it.

Reconcile competing definitions of the same data across Finance, Programs, Business Development, and Enterprise Platforms into a single agreed definition, and record it. A substantial share of this role is getting teams that describe the same data in different vocabularies to agree on one.

For Phase IV, derive the dimensional and reporting requirements implied by Fika's live institutional and government award agreements, in partnership with Finance and Compliance, and secure their confirmation before design.

Own the delivery plan for Phases II through V, including scope definition, dependency mapping, and timelines validated with each affected function.

Run each phase as a discrete project with a schedule, decision log, risk log, and reporting cadence agreed with the Director of Enterprise Platforms.

Hold scope discipline across the sequence. A phase does not open until its requirements are approved, each phase closes before the next opens, and the core financial system stays stable throughout.

Identify and escalate resourcing constraints and requirements gaps early, particularly where phase delivery depends on Finance, Salesforce, or country team capacity or decisions that this role does not control. Where a department cannot resolve a requirements question within an agreed window, escalate to the Director of Enterprise Platforms and the department lead jointly rather than proceeding on assumption.

Sequence Phase IV grants management configuration against Fika’s live institutional and government donor reporting obligations rather than against convenience.

Data Integrity, Testing & Financial Controls (20%)

Design and execute testing for each phase in a Sage Intacct sandbox environment, including unit, integration, and user acceptance testing, with parallel validation where financial risk warrants it. Nothing deploys to the production environment until it has been tested and accepted in sandbox to the fullest extent the environment allows, with any untested element identified and mitigated in the deployment plan.

Build an automated reconciliation and exception-handling report that confirms complete data transfer between integrated systems, reconciling record counts and control totals on a scheduled basis and surfacing exceptions to Finance. The report must be one Finance can operate and interpret without ongoing support from this role.

Ensure each phase meets Fika’s internal control, approval, and segregation of duties requirements, and coordinate with Finance and Compliance on any control change an integration introduces.

Maintain the access, authentication, and audit trail standards already established for Sage, including two-factor authentication for all users.

Preserve the integrity of the reporting layer already in use, including the role-based dashboards and the