There is a new System Setting: NSF_FEE_EXCLUDE_CREDITORIDS that allows listing CreditorIDs for which NSF Fees should not be charged.
When importing the ACH failures, if a Client has an OPEN account that is associated with one of the CreditorIDs specified in NSF_FEE_EXCLUDE_CREDITORIDS, the following message is displayed “An OPEN Creditor prevents NSF Fee” and no NSF Fee is generated.
The ability to add Custom SQL Reports has been added. The reports can be created under System Management/Document Template Management. There, select Type = SQL. Only SELECT queries can be executed. To display in the Navigation pane, select the Application. To further limit access by group, provide values to Access Groups and only members of those groups will have access to the reports.
Client Support Software’s CMS is now a HUD approved CMS able to submit electronic 9902 for the latest ARMv6 specification. Support for multiple Agencies allows multi-state submissions. Combined with seamless integration with other industry products such as Debt Management, Bankruptcy, and Student Loans, Client Support Software’s CMA offers a complete hosted solution for managing Housing Clients in need of assistance.
If set, when a CallLog record is imported, the CMA will look up the most recent Campaign whose phone matches the CallLog DID. When the CallLog is linked with a Client, if the Client Campaign is empty or the default 1, the Client’s campaign is updated.
CallLog Detail report and the Campaign report have been updated to display new columns.
There is a new Setting key: NSF_FEE_STATE_FIELD which allows specifying which field is used to determine NSF fees that are applied when importing an ACH Failure file. Either clientAddressOrigState (the contract state) or clientAddressState (the client’s current state) can be specified.
There is a new Company field that allows selection of the Default Bank Algorithm to use when determining which Bank payments should be linked with.
Default Bank Algorithm
The State Default Banks rule is ONLY applied if both the clientAddressOrigState and clientAddressState match. (If the Contract state matches the Client’s current address)
Apply rules based on clientAddressOrigState (the Contract Address State)
Apply rules based on clientAddressState (the Client’s current Address State)
Based on feedback, several small changes have been made to improve the Accounting experience. Many of the smaller changes are listed within the CMA internal Changelog.
Notable changes include:
The Client Payment and Disbursement tabs can be exported to a CSV file.
Filters have been added to the Disbursement tab for dates and to collapse fairshare. Collapsing fairshare displays gross, fairshare, and net columns for the primary Disbursement record.
Collapsed FairShare view:
In addition, when a failed Disbursement is imported via a Check Return file or RPPS Return file and it is associated with a Cleared FairShare record, the system now automatically creates a Payment record of type Operating Account Credit in the amount of the Cleared FairShare. This allows the Client funds to be balanced and simplifies the process of dealing with this scenario.
Support to mark Cleared Payments and Disbursements as Reconciled has been added. A Reconciled transaction is no longer editable through the CMA.
There is a new Setting key: RECONCILE_ACCOUNTING_TRANSACTIONS_AFTER_N_DAY which is used to specify the number of days after which a Cleared Payment or Disbursement should be marked as Reconciled by the CMA’s daily job. To disable this job, set the value of the Setting key to 0.
Filters and columns have been added to the Payment and Disbursement reports. An R appears prior to the Status column for Payments and Disbursements when that transaction has been marked as Reconciled.
An Extranet Package is a collection Extranet Phases arranged in a specific order.It is used to provide a sequence of pages that are displayed to the Client through the Extranet.
New functionality has been added to allow simpler management of multiple Extranet Packages. Previously, Extranet Steps were defined either at the Agency or Company level. If multiple packages were desired, they would be combined into the existing extranet steps and a new start step would be selected by the User under the Client/Admin tab.
Extranet Packages simplifies this by creating system level packages similar to Document Transactions. Multiple Extranet Packages can be associated with either an Agency (so that they appear under the LMA Paperwork) or a Company so they appear in the Backend Paperwork.
When adding a new Lead, there is a new field next to the Lead Source that facilitates starring the ClientID of the Client that referred this Client. In addition, there is a new report under LMA/Client Referrals that displays all Leads that have referred and have been referred by other Clients.