Intacct Integration

[renatorossiter]

Summary

Create an integration that syncs project budget data from Intacct into Cord so Finance and Field teams do not have to maintain overlapping budget figures manually. The goal is for Intacct to remain the source of truth for active-project financial data while Cord surfaces the latest approved values in a reliable, read-only or system-managed way.

Background / User Problem

• When project budgets change, Financial Analysts are advised not to update the figures manually in Cord.
• Intacct is treated as the reliable source of truth for active-project financial data.
• Manually re-entering budget information into Cord creates duplicate work for Finance and increases the risk of mismatch or data-entry errors.

Because of this, Cord is not recommended as the source of truth for financial information for active projects in general.

This gap is also reflected in current practice and related system behavior:

• For some budget scenarios, users are explicitly told not to enter partner budget values into Cord, and only the SC commitment is expected there.
• For reporting, pipeline budget values are pulled from Cord, but for active projects DOMO pulls budget values from Intacct.
• Existing Cord work already recognizes the need to make budget-related data available in Cord and downstream reporting/exports, rather than relying on side files alone.

Desired Outcome

For active projects, Cord should display budget data that is synchronized from Intacct so users can confidently reference financial information in Cord without creating a second manual maintenance process.

Proposed Solution

Phase 1

Implement an Intacct-to-Cord budget integration for active projects that:

• Pulls the relevant approved budget values from Intacct into Cord on a defined sync cadence or event-driven trigger.
• Stores or surfaces those values in Cord as system-managed data rather than requiring manual entry by FAs.
• Clearly indicates that the values originate from Intacct.
• Makes the synced values available anywhere Cord or downstream reporting depends on active-project budget data.
• Reduces or eliminates the need for Finance to maintain the same budget data in both systems.

Recommended behavior

• Intacct remains the source of truth for active-project budget figures.
• Cord displays the synced values for visibility, workflow context, and downstream use.
• Manual editing of Intacct-owned budget fields in Cord should either be disabled or tightly controlled.
• If edits are needed, they should happen in Intacct and flow back into Cord through the integration.

Use Cases

• A Financial Analyst updates a project budget in Intacct and expects Cord to reflect the new value without additional manual work.
• An FPM views an active project in Cord and sees the current approved budget from Intacct.
• DOMO, Cord workflows, and any Cord-based reporting use aligned budget values rather than conflicting data from separate systems.
• Teams can reference budget information in Cord for operational context without treating Cord as an independently maintained financial record.

Acceptance Criteria

• Active-project budget data can be synced from Intacct into Cord.
• Cord surfaces synced Intacct budget values for the appropriate active-project views and use cases.
• The synced values are identified as originating from Intacct.
• Users are not required to manually duplicate active-project budget updates in Cord after updating Intacct.
• Permissions and editing behavior are defined so Intacct-owned financial values are not unintentionally overwritten in Cord.
• Any downstream reporting that depends on active-project budget values can use the synchronized data consistently.

Open Questions / Dependencies

• Which exact budget fields should sync first (for example: total budget, SC commitment, partner funding amounts, budget-to-actual fields, or other financial breakdowns)?
• Should the first release be read-only in Cord, or should there be any exception paths for manual override?
• What should trigger the sync: scheduled jobs, status changes, or direct integration events from Intacct?
• Should this apply only to active projects initially, since pipeline currently relies on Cord-entered budget values?
• What historical/backfill behavior is needed for already-active projects?
• Which Cord surfaces and downstream outputs must consume the synced values in phase 1?