Summary
Financial Edge NXT currently utilizes a single default credit card liability account for Expense Management transactions. While this functionality may be sufficient for organizations operating with a single balance sheet structure, it presents significant challenges for nonprofit organizations that utilize fund accounting and must report in accordance with U.S. GAAP and FASB standards.
We recommend enhancing Expense Management to allow organizations to assign credit card liability accounts based on fund, project, department, or other accounting dimensions rather than relying on a single global liability account.
Business Need
Many nonprofit organizations maintain multiple funds, donor-restricted activities, grants, programs, or legal entities within a single Financial Edge database. Credit card expenditures are frequently incurred across numerous projects and funding sources.
Although expense transactions can be coded to the appropriate projects and restrictions, the corresponding liability is accumulated within a single credit card payable account. This often requires organizations to perform manual allocations, journal entries, or supplemental reconciliations to properly present liabilities by fund or net asset classification.
Examples include:
Donor-restricted program expenditures
Grant-funded activities
Hospital or affiliate pass-through expenditures
Multi-entity accounting environments
Endowment-funded operating expenses
Shared services organizations managing multiple cost centers
GAAP and FASB Considerations
Under FASB ASC 958, Not-for-Profit Entities, organizations are required to accurately report assets, liabilities, revenues, and expenses in a manner that supports the presentation of net assets with donor restrictions and net assets without donor restrictions.
While the expenses associated with credit card transactions may be properly classified through projects and funds, the related liability is often aggregated into a single balance sheet account. This can obscure the true obligations associated with specific funds or programs and creates additional work during financial statement preparation.
Organizations frequently need to create manual reclassification entries to align liabilities with the activities that generated them. Allowing project- or fund-specific liability accounts would improve the relationship between expenses, liabilities, and net asset reporting while reducing manual intervention.
Internal Control and Audit Benefits
The current structure can make it difficult to:
Reconcile liabilities by fund or program
Demonstrate fund-level obligations
Support audit requests related to project-specific liabilities
Produce accurate balance sheet reporting by funding source
Maintain consistent accounting treatment across operating units
Providing greater flexibility would strengthen internal controls and reduce the risk of manual allocation errors.
Suggested Enhancement
Provide the ability to:
Assign default credit card liability accounts by fund, project, department, or accounting segment.
Define mapping rules that automatically select the appropriate liability account based on transaction coding.
Override the liability account at the transaction level when necessary.
Generate liability balances that align with project and fund reporting structures.
Maintain the current single-account option for organizations that do not require fund accounting functionality.
Benefits
Improved compliance with nonprofit fund accounting practices
Better alignment with FASB ASC 958 reporting requirements
Reduced manual journal entries and reconciliations
Enhanced auditability and transparency
Stronger internal controls over fund-level liabilities
More accurate balance sheet reporting by funding source
Increased efficiency during month-end and year-end close processes
This enhancement would significantly improve Financial Edge NXT's ability to support nonprofit organizations operating in complex fund accounting environments while reducing administrative burden and improving financial reporting accuracy.