Amy, you’ve identified the root cause. The patch introduced enhanced depreciation compliance features including the half-year convention option. Here’s the complete picture:
1. Patch Impact Analysis:
Patch 23.1.4 introduced three new depreciation parameters that weren’t in previous ICS 2023-1 versions:
- apply_half_year_convention (default: TRUE)
- mid_quarter_convention_threshold (default: 40%)
- salvage_value_floor_percentage (default: 10%)
These parameters were added for US GAAP compliance but weren’t prominently documented. The half-year convention affects first and last year depreciation calculations, which explains your 20% variance.
2. Depreciation Logic Validation:
To verify the calculation is now correct according to standards:
SELECT asset_id, depreciation_method,
half_year_convention, calculated_amount
FROM asset_depreciation_schedule
WHERE method_code = 'DDB'
AND calculation_date >= '2025-04-01'
Your asset EQUIP-2024-0156 is likely in its first year of service. With half-year convention enabled, the system now calculates:
- First year: 50% of normal annual depreciation
- Subsequent years: Full depreciation based on remaining book value
- Last year: Remaining 50% of final year
This is why you’re seeing $2,278 instead of $2,847.50 - the system is applying the half-year rule.
3. Financial Compliance:
You have three options to resolve this:
Option A - Accept New Calculation (Recommended for US GAAP):
If you report under US GAAP, the new calculation is actually more compliant. Update your financial statements to reflect the corrected depreciation method. Document the change as a “change in accounting estimate” per ASC 250, which is applied prospectively.
Option B - Disable Half-Year Convention:
Navigate to Asset Management > Configuration > Depreciation Rules and set:
apply_half_year_convention = FALSE
mid_quarter_convention_threshold = NULL
This reverts to your previous calculation method. However, you should validate this with your auditors.
Option C - Asset-Specific Configuration:
For assets already in service before the patch, you can set individual override flags to maintain original calculation:
// Pseudocode - Batch update for existing assets:
1. Query all assets with in_service_date < '2025-04-01'
2. For each asset using DDB method:
a. Set override_convention_flag = TRUE
b. Set use_legacy_calculation = TRUE
c. Update depreciation_schedule with recalculated values
3. New assets acquired after patch date use new convention
4. Document this hybrid approach in accounting policies
// This maintains continuity for existing assets
For your quarter close, I recommend:
- Immediately set apply_half_year_convention to FALSE to match your historical method
- Recalculate depreciation for all affected assets
- Document the configuration change and rationale
- Schedule a meeting with your auditors to determine the appropriate long-term approach
- For next fiscal year, consider adopting the half-year convention if it aligns with your reporting standards
The patch didn’t break anything - it enhanced compliance features but should have made the defaults configurable during upgrade. Log a support case with Infor requesting better documentation of calculation logic changes in future patches.
This draft is based on general Infor CloudSuite knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.