Skip to content

[Certinia] R2 PSA: Export page (PSA branch) and CertiniaReportExportStatusPage #89440

Description

@yuwenmemon

Parent: Expensify/Expensify#589894
Design doc: https://docs.google.com/document/d/1qQXU4EIij-OyCpk6z8idi0ch0rP4XtIQ0770STZeF5E/edit

Scope

Branch CertiniaExportPage to render PSA content when hasPSA === true, and create the new CertiniaReportExportStatusPage for picking the PSA expense report status.

Implementation notes (from design doc)

CertiniaExportPage.tsx — Add PSA conditional rendering

If hasPSA === true, replace FFA rows 2–6 with PSA content:

  1. Preferred Exporter (shared, unchanged)
  2. Expense Report Status: MenuItemWithTopDescriptionPOLICY_ACCOUNTING_CERTINIA_REPORT_EXPORT_STATUS.getRoute(policyID).
  3. Export reimbursable as Expense Reports (static): interactive={false}, helper text: "Expenses marked as reimbursable will be exported as Expense Reports made out to the employee."
  4. Export non-reimbursable as Expense Reports (static): same.

No Default Vendor, no Payable Invoice Date for PSA.

src/pages/workspace/accounting/certinia/export/CertiniaReportExportStatusPage.tsx — Create

Two radio options:

  • 'APPROVED' → "Approved"
  • 'SUBMITTED' → "Submitted"

Calls updateFinancialForceReportExportStatus(policyID, value).

Tests

  • PSA export page: Preferred Exporter, Expense Report Status, two static rows — no Default Vendor, no Invoice Date.
  • FFA export page renders the original Release 1 content unchanged.
  • Report Export Status page selection fires the action with pending indicator and reverts on simulated failure.
Issue OwnerCurrent Issue Owner: @thelullabyy

Metadata

Metadata

Labels

DailyKSv2EngineeringNewFeatureSomething to build that is a new item.Skip PaymentSkips all the payment process steps for an issue. Use it for fixed-price projects.

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions