We’re implementing Infor CloudSuite lease management for ASC 842 compliance and I’m looking for guidance on asset classification configuration. Our portfolio includes real estate, vehicles, equipment, and IT assets across multiple jurisdictions.
I’m particularly interested in how others have structured their asset class definitions to balance operational flexibility with audit requirements. We need validation rules that prevent misclassification while allowing for legitimate edge cases. What approaches have worked well for documenting asset classification decisions for audit purposes? Has anyone implemented a multi-tier classification system that maps to both accounting standards and operational reporting needs?
One thing we learned the hard way: plan for dual reporting requirements if you have international operations. IFRS 16 and ASC 842 have different nuances for asset classification, especially around low-value and short-term lease exemptions. Build your classification structure to support both standards from the start, even if you’re only using one currently.
Based on this discussion and our implementation experience, here’s the comprehensive approach that emerged:
Asset Class Definitions - Three-Tier Structure:
We implemented a hierarchical classification: Primary Type (8 classes: Real Estate, Vehicles, IT Equipment, Manufacturing Equipment, Office Equipment, Specialized Equipment, Intangibles, Other) → Sub-Category (25 categories with operational relevance) → Accounting Attributes (useful life bands, materiality groups, standard-specific flags). This balances operational needs with accounting precision while keeping the structure maintainable.
Validation Rule Setup - Layered Control Approach:
Implemented three validation levels:
- Hard stops: Prevent impossible combinations (equipment classified as real estate, useful life exceeding asset type maximums)
- Soft warnings: Flag unusual but valid scenarios (short-term classification for typically long-lived assets, low-value designation for expensive asset types)
- Documentation triggers: Require explanatory notes for edge cases (hybrid assets, special-purpose equipment)
Each rule includes business rationale documentation accessible within the system. We also built a classification decision tree tool that guides users through proper classification based on asset characteristics.
Audit Documentation - Integrated Compliance Framework:
Created a Classification Control Matrix stored as system documentation linked to each asset class. This includes:
- Detailed classification criteria with examples
- Useful life assumptions and supporting analysis
- Materiality threshold calculations and approval documentation
- Mapping to ASC 842 and IFRS 16 requirements
- Change control procedures with full audit trail
- Quarterly certification process where lease administrators confirm classification accuracy
Key Lessons Learned:
- Start with fewer, broader classes enhanced by attributes rather than proliferating narrow classes
- Build dual-standard support from day one even if only using ASC 842 initially - adding IFRS 16 later is painful
- Validation rules should guide users toward correct classification rather than just blocking errors
- Link every configuration decision to documented business rationale - auditors appreciate transparency
- Implement automated classification suggestions based on asset attributes to improve consistency
- Regular review cycles (quarterly) to assess whether classification rules need refinement based on new lease types
The attribute-based approach provides the flexibility to handle edge cases while maintaining strict controls on core classification decisions. This structure has held up well through two audit cycles and accommodated portfolio growth without requiring classification restructuring.
From a system design perspective, use asset class attributes rather than proliferating classes. We started with 45 asset classes and consolidated to 12 primary classes with rich attribute sets. This makes maintenance much easier and provides better flexibility for reporting. You can still enforce validation rules based on attribute combinations. For example, a ‘Computer Equipment’ class with attributes for useful life category (3yr, 5yr, 7yr) is more maintainable than three separate classes.