ArticlesPSA: Expense Related Revenue Not Recognized In the Expected Accounting Period

• Delays or failures in recognizing revenue for reimbursable expenses and expense credits
• Expenses billed in one period were not recognized until a later period

1. Identify impacted expense records:

• Use revenue recognition logs or error monitoring to locate records failing to create revenue transaction lines due to currency errors
• Look for messages similar to: RREL-0000### and EXP-4### Save "Dual currency rate cannot be zero.”

2. Validate currency fields on expenses.

• Inspect each affected expense and confirm the Home Currency exchange rate
• If the value is null, the system may calculate a Dual Currency rate of 0.000000, which blocks recognition

3. Correct the Home Currency exchange rate.

• Update the Home Currency exchange rate from NULL to 1.000000 for impacted expenses
• This action should automatically update the Dual Currency rate from 0.000000 to 1.000000
• Use data loader, a list view inline edit, or an admin script to apply updates at scale

4. Navigate to the Recognize Revenue page > Select Generate Data > Choose the impacted records or filter by Project and Accounting Period.

1. Submit the generation job to rebuild revenue transaction line data for the corrected expenses
2. Create revenue transactions
3. After successful data generation, select Create Transaction to produce revenue transaction lines for all selected records
4. Verify period alignment

Confirm that generated transactions align with the intended recognition period and comply with revenue policies. * If recognition must occur in a prior period and the period is closed, follow standard accounting procedures for adjustments or true-ups in the current open period.

5. Reconcile expense credits.

• Include expense credits in the same generation and transaction creation process
• Verify that credits now produce revenue entries after currency field correction

6. Recheck logs and queues.

• Review the revenue recognition logs and processing queues to ensure all previously blocked records have cleared without new errors

Revenue recognition error logs revealed messages indicating a zero Dual Currency rate.

• The root condition was expense records having a null Home Currency exchange rate, which resulted in a derived Dual Currency rate of 0.000000 which prevented revenue transaction lines from generating and posting, leaving expenses unrecognized.