Skip to content

Commit 202c8d8

Browse files
Krishna2323Krishna2323
committed
Merge upstream/main and resolve conflict in ReportActionsList.tsx
Made-with: Cursor
2 parents 4c97a01 + 88df7ab commit 202c8d8

468 files changed

Lines changed: 36486 additions & 148 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/articles/expensify-classic/connections/certinia/Troubleshooting/Authentication-and-Login-errors/CER937-Error.md‎

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
title: CER937 Error in Certinia Integration
3+
description: Learn what the CER937 error means in Certinia and how to update the Expensify integration configuration to restore syncing.
4+
keywords: CER937, Certinia export error, update Expensify in Certinia, Certinia connection issue, Expensify Certinia sync error, Workspace Admin
5+
internalScope: Audience is Workspace Admins and Certinia Admins using the Certinia integration. Covers resolving the CER937 error caused by an outdated Certinia integration configuration. Does not cover other Certinia error codes.
6+
---
7+
8+
# CER937 Error in Certinia Integration
9+
10+
If you see the error:
11+
12+
CER937: Please update Expensify in Certinia.
13+
14+
This means Certinia has detected that the Expensify integration configuration is outdated and must be updated before exports or syncs can proceed.
15+
16+
---
17+
18+
## Why the CER937 Error Happens in Certinia
19+
20+
The CER937 error typically indicates:
21+
22+
- A newer version of the Expensify integration is available in Certinia.
23+
- The existing integration configuration has not been updated.
24+
- Certinia is blocking exports until the integration version is aligned.
25+
26+
This is a Certinia configuration issue, not a Workspace configuration issue.
27+
28+
---
29+
30+
## How to Fix the CER937 Error
31+
32+
This issue must be resolved in Certinia.
33+
34+
1. Log in to Certinia as an administrator.
35+
2. Locate the **Expensify Integration** configuration.
36+
3. Select the option to **Update** the integration.
37+
4. Follow any prompts to upgrade, reinstall, or refresh metadata.
38+
5. Confirm API credentials or OAuth tokens if prompted.
39+
6. Save your changes.
40+
41+
If you do not see an update option, contact your Certinia administrator or Certinia support to confirm access to the latest integration release.
42+
43+
After updating Certinia:
44+
45+
1. Go to **Settings > Workspaces**.
46+
2. Select your Workspace.
47+
3. Click **Accounting**.
48+
4. Click **Sync Now**.
49+
50+
Then retry exporting the report.
51+
52+
---
53+
54+
# FAQ
55+
56+
## Can I Retry the Export?
57+
58+
You can attempt to retry the export after updating the integration and selecting **Sync Now**. If the error persists, confirm the integration version in Certinia is current.
59+
60+
## Does CER937 Mean My Data Is Lost?
61+
62+
No. The report remains in Expensify. The export is simply blocked until the Certinia integration is updated.
63+
64+
## Is CER937 Caused by Workspace Settings?
65+
66+
No. CER937 is triggered when Certinia requires an integration update. Workspace accounting settings are not the cause.

‎docs/articles/expensify-classic/connections/certinia/Troubleshooting/Certinia-FAQ.md‎

Lines changed: 125 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,125 @@
1+
---
2+
title: Certinia Integration FAQ and Export Troubleshooting
3+
description: Learn why reports may not export to Certinia, how to manually export, fix company card export issues, manage project limitations, and disconnect the Certinia integration.
4+
keywords: Certinia export not working, automatic export failed, manual export Certinia, company card wrong account export, preferred exporter domain admin, disconnect Certinia, Certinia project status export limitation, assignment status export, Workspace Admin
5+
internalScope: Audience is Workspace Admins and Domain Admins using the Certinia integration. Covers common export failures, manual export restrictions, company card export mapping, project limitations, and disconnecting Certinia. Does not cover specific Certinia error codes.
6+
---
7+
8+
# Certinia FAQ
9+
10+
## Why is my report not automatically exporting to Certinia?
11+
12+
An error is preventing the report from exporting automatically.
13+
14+
You can find the error in several ways:
15+
16+
- The **preferred exporter** (as configured in Expensify) receives an email with error details.
17+
- The error appears in the report’s comments section.
18+
- Automatic exports will continue to fail until the error is resolved.
19+
20+
### How to resolve automatic export failures
21+
22+
1. Open the affected report in Expensify.
23+
2. Review the error message in the comments section.
24+
3. Make the required corrections.
25+
4. Have a Workspace Admin manually export the report.
26+
27+
---
28+
29+
## Why am I unable to manually export a report to Certinia?
30+
31+
Only reports in **Approved**, **Done**, or **Paid** status can be exported.
32+
33+
If the report is in **Draft** status, selecting export may result in an empty screen.
34+
35+
### How to resolve manual export issues
36+
37+
1. Submit the report if it is in Draft status.
38+
2. Have an approver approve the report if it is Outstanding.
39+
3. Once the report is Approved, Done, or Paid, a Workspace Admin can manually export it.
40+
41+
---
42+
43+
## Why are company card expenses exporting to the wrong account?
44+
45+
Company card expenses may export to the wrong account if the card export mapping is incorrect or if the exporter does not have proper permissions.
46+
47+
### How to verify company card export mapping
48+
49+
1. Go to the navigation tabs on the left.
50+
2. Click **Settings**.
51+
3. Click **Domains**.
52+
4. Select **Company Cards**.
53+
5. Click **Edit Export** for the affected card.
54+
6. Confirm the correct export account is selected.
55+
56+
Also confirm:
57+
58+
- The expenses display the **Card + Lock icon**, which ensures they are mapped correctly.
59+
- The preferred exporter is a **Domain Admin**.
60+
61+
If the preferred exporter is not a Domain Admin, exports will default to the fallback company card account set in the Workspace configuration.
62+
63+
### How to check the preferred exporter
64+
65+
1. Go to the navigation tabs on the left.
66+
2. Click **Workspaces**.
67+
3. Select your Workspace.
68+
4. Click **Accounting**.
69+
5. Click **Configure**.
70+
6. Review the **Export** settings.
71+
72+
---
73+
74+
## How do I disconnect the Certinia connection?
75+
76+
Disconnecting removes the active integration and clears imported options.
77+
78+
### How to disconnect Certinia
79+
80+
1. Go to the navigation tabs on the left.
81+
2. Click **Settings**.
82+
3. Click **Workspaces**.
83+
4. Select your Workspace.
84+
5. Click **Accounting**.
85+
6. Click the gray **Disconnect** button under the Certinia connection.
86+
7. Confirm to disconnect.
87+
88+
Note: Disconnecting clears all imported options from Expensify.
89+
90+
---
91+
92+
## Are there export limitations based on projects in Certinia?
93+
94+
Yes. Project settings in Certinia can prevent expenses from exporting.
95+
96+
### Expenses can be exported when:
97+
98+
- **Project Status** = Active or In Progress
99+
- **Assignment Status** = Closed, Active, or Completed
100+
- **Closed for Expense Entry** = Unchecked
101+
102+
### Expenses cannot be exported when:
103+
104+
- **Project Status** = Closed
105+
- **Closed for Expense Entry** = Checked
106+
107+
### How to resolve project export limitations
108+
109+
1. Check the Project Status in Salesforce.
110+
- If Project Status is Closed, expenses cannot be entered or exported.
111+
- If Active or In Progress, continue to step 2.
112+
2. Verify the **Closed for Expense Entry** setting.
113+
- If checked, uncheck it to allow expense exports.
114+
3. Manually test expense entry in Salesforce.
115+
- If manual entry works, the Expensify–Certinia integration should also allow export.
116+
117+
---
118+
119+
## Does assignment status affect expense exports?
120+
121+
No.
122+
123+
Assignment Status in Certinia (Closed, Active, or Completed) does not impact expense entry or export.
124+
125+
Only Project Status and the Closed for Expense Entry setting affect export eligibility.

‎docs/articles/expensify-classic/connections/certinia/Troubleshooting/Export-Errors/CER047-Error.md‎

Lines changed: 64 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,64 @@
1+
---
2+
title: CER047 Error in Certinia Integration
3+
description: Learn what the CER047 error means in Certinia and how to enable the Expense Ops Edit permission to restore syncing.
4+
keywords: CER047, Certinia export error, Ops Edit permission, Expense Ops Edit, approved records permission error, Expensify Certinia sync error, Workspace Admin
5+
internalScope: Audience is Workspace Admins using the Certinia integration. Covers resolving the CER047 error caused by missing Expense Ops Edit permissions. Does not cover other Certinia error codes.
6+
---
7+
8+
# CER047 Error in Certinia Integration
9+
10+
If you see the error:
11+
12+
CER047: "Ops Edit" permission is required to edit approved records.
13+
14+
This means the Certinia integration user does not have permission to edit approved expense records, preventing the export from completing.
15+
16+
---
17+
18+
## Why the CER047 Error Happens in Certinia
19+
20+
The CER047 error typically indicates:
21+
22+
- The connected Certinia integration user lacks the **Expense Ops Edit** permission.
23+
- Certinia requires permission to modify approved records during export processing.
24+
- The export is blocked due to missing permissions.
25+
26+
This is a Certinia permission configuration issue, not a Workspace configuration issue.
27+
28+
---
29+
30+
## How to Fix the CER047 Error
31+
32+
This issue must be resolved in Certinia.
33+
34+
1. Log in to Certinia.
35+
2. Go to **Permission Controls**.
36+
3. Select the permission set assigned to the integration user.
37+
4. Locate **Expense Ops Edit**.
38+
5. Enable the permission.
39+
6. Save your changes.
40+
41+
After updating permissions:
42+
43+
1. Go to **Settings > Workspaces**.
44+
2. Select your Workspace.
45+
3. Click **Accounting**.
46+
4. Click **Sync Now**.
47+
48+
Then retry exporting the report.
49+
50+
---
51+
52+
# FAQ
53+
54+
## Can I Retry the Export?
55+
56+
Yes. After enabling **Expense Ops Edit** and selecting **Sync Now**, retry the export. If the error persists, confirm the permission is applied to the exact user connected to the integration.
57+
58+
## Does CER047 Mean My Expense Was Deleted?
59+
60+
No. The report remains in Expensify. The export was blocked due to missing permissions.
61+
62+
## Is CER047 Caused by Workspace Settings?
63+
64+
No. CER047 is triggered by missing permissions in Certinia. Workspace accounting settings are not the cause.

‎docs/articles/expensify-classic/connections/certinia/Troubleshooting/Export-Errors/CER061-Export-Error.md‎

Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
title: CER061 Export Error in Certinia Integration
3+
description: Learn what the CER061 export error means in Certinia and how to correct credit terms configuration to restore successful exports.
4+
keywords: CER061, Certinia export error, object validation failed, credit terms not defined, PSA project account error, FFA resource account error, Expensify Certinia sync error, Workspace Admin
5+
internalScope: Audience is Workspace Admins using the Certinia integration. Covers resolving the CER061 export error caused by incorrect credit term configuration. Does not cover other Certinia error codes.
6+
---
7+
8+
# CER061 Export Error in Certinia Integration
9+
10+
If you see the error:
11+
12+
CER061: Object validation failed. The credit terms for the selected account are not correctly defined.
13+
14+
This means the account used for the export does not have properly configured credit terms in Certinia, preventing the export from completing.
15+
16+
---
17+
18+
## Why the CER061 Export Error Happens in Certinia
19+
20+
The CER061 error typically indicates:
21+
22+
- Required credit term fields are missing on the associated account.
23+
- Credit term configuration does not meet Certinia validation requirements.
24+
- The export is being blocked due to incomplete payment term settings.
25+
26+
The affected account depends on your Certinia configuration:
27+
28+
- **PSA/SRP environments** use the Project account.
29+
- **FFA environments** use the Resource-linked account.
30+
31+
This is a Certinia account configuration issue, not a Workspace configuration issue.
32+
33+
---
34+
35+
## How to Fix the CER061 Export Error
36+
37+
This issue must be resolved in Certinia.
38+
39+
1. Log in to Certinia.
40+
2. Navigate to the applicable account (Project account or Resource-linked account).
41+
3. Locate the credit terms configuration.
42+
4. Update the required fields:
43+
- Set **Base Date 1** to **Invoice**.
44+
- Enter one or more in **Days Offset**.
45+
- Ensure a **Currency** is selected.
46+
5. Save your changes.
47+
48+
After updating the account:
49+
50+
1. Go to **Settings > Workspaces**.
51+
2. Select your Workspace.
52+
3. Click **Accounting**.
53+
4. Click **Sync Now**.
54+
55+
Then retry exporting the report.
56+
57+
---
58+
59+
# FAQ
60+
61+
## Can I Retry the Export?
62+
63+
Yes. After correcting the credit terms and selecting **Sync Now**, retry the export. If the error persists, confirm all required credit term fields are populated correctly.
64+
65+
## Does CER061 Mean My Report Failed Permanently?
66+
67+
No. The report remains in Expensify. The export failed due to account validation settings in Certinia.
68+
69+
## Is CER061 Caused by Workspace Settings?
70+
71+
No. CER061 is triggered by incorrect credit term configuration in Certinia. Workspace accounting settings are not the cause.

‎docs/articles/expensify-classic/connections/certinia/Troubleshooting/Export-Errors/CER074-Error.md‎

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
title: CER074 Error in Certinia Integration
3+
description: Learn what the CER074 error means in Certinia and how to configure the required Permission Controls to restore successful exports.
4+
keywords: CER074, Certinia export error, insufficient permissions for resource, Certinia permission controls, report creator permission error, Expensify Certinia sync error, Workspace Admin
5+
internalScope: Audience is Workspace Admins using the Certinia integration. Covers resolving the CER074 error caused by missing or incorrect Permission Controls. Does not cover other Certinia error codes.
6+
---
7+
8+
# CER074 Error in Certinia Integration
9+
10+
If you see the error:
11+
12+
CER074: Insufficient permissions for Resource.
13+
14+
This means the report creator or submitter does not have the required Permission Controls configured in Certinia, preventing the export from completing.
15+
16+
---
17+
18+
## Why the CER074 Error Happens in Certinia
19+
20+
The CER074 error typically indicates:
21+
22+
- The report creator or submitter does not have access to the associated Resource.
23+
- Required Permission Controls have not been configured.
24+
- Certinia validation failed due to missing user-resource permissions.
25+
26+
This is a Certinia permission configuration issue, not a Workspace configuration issue.
27+
28+
---
29+
30+
## How to Fix the CER074 Error
31+
32+
This issue must be resolved in Certinia.
33+
34+
1. Log in to Certinia.
35+
2. Go to **Permission Controls**.
36+
3. Create a new Permission Control or update an existing one.
37+
4. Enter the required **User** and **Resource**.
38+
5. Enable all required permission fields.
39+
6. Save your changes.
40+
41+
Ensure the Permission Control applies to the report creator or submitter and the specific Resource associated with the export.
42+
43+
After updating permissions:
44+
45+
1. Go to **Settings > Workspaces**.
46+
2. Select your Workspace.
47+
3. Click **Accounting**.
48+
4. Click **Sync Now**.
49+
50+
Then retry exporting the report.
51+
52+
---
53+
54+
# FAQ
55+
56+
## Can I Retry the Export?
57+
58+
Yes. After creating or updating the correct Permission Control and selecting **Sync Now**, retry the export. If the error persists, confirm the permission is assigned to the correct user and Resource.
59+
60+
## Does CER074 Mean the Report Is Invalid?
61+
62+
No. The report remains valid in Expensify. The export failed due to missing permission configuration in Certinia.
63+
64+
## Is CER074 Caused by Workspace Settings?
65+
66+
No. CER074 is triggered by missing or incorrect Permission Controls in Certinia. Workspace accounting settings are not the cause.

0 commit comments

Comments
 (0)