Parent GH: https://github.com/Expensify/Expensify/issues/589894
Context
The high-level design doc for Add Certinia to New Expensify has been reviewed and is ready for the detailed implementation section to be written.
Tracking issue: Expensify/Expensify#589894
Task
Write the detailed implementation section of the design doc, covering all three releases:
- Release 1: FFA — Connection flow (Salesforce OAuth, prerequisites, company selector) + full FFA configuration (Import: Chart of Accounts, Dimensions 1–4, Tax; Export: Preferred Exporter, Payable Invoice Status/Date, Default Vendor; Advanced: Auto Sync, Sync Reimbursed Reports)
- Release 2: PSA — PSA-specific configuration (Import: GLA Mappings, Tags mapping, Milestones; Export: Expense Report Status; Advanced: Tax Non-Billable, Foreign Currency)
- Release 3: Sandbox — Sandbox connection support with different OAuth endpoints and bundle links
The detailed section should follow the same structure as the Add Gusto to New Expensify detailed implementation — specifying every file to touch, new components to create, and API integration points.
The backend naming convention is financialForce (not certinia) — see the Nomenclature section in the doc.
Parent GH: https://github.com/Expensify/Expensify/issues/589894
Context
The high-level design doc for Add Certinia to New Expensify has been reviewed and is ready for the detailed implementation section to be written.
Tracking issue: Expensify/Expensify#589894
Task
Write the detailed implementation section of the design doc, covering all three releases:
The detailed section should follow the same structure as the Add Gusto to New Expensify detailed implementation — specifying every file to touch, new components to create, and API integration points.
The backend naming convention is
financialForce(not certinia) — see the Nomenclature section in the doc.