Custom Procedure: Application Charge Override

Created by Jake Killin, Modified on Tue, Apr 23 at 2:46 PM by Jake Killin

A customization is in place that will allow to charge a different application charge amount for the primary resident and a different application charge amount for roommates that are not "Other".


This is needed because Yardi does not have a way to charge a different amount by resident type. Even if you setup the application charge screen to have two detail lines for the application charge (ie one line for the primary at one rate and the second line for the roommates with a different rate), Yardi will charge the primary along with the roommate for the second line amount as well.


Property Reporting Info

New fields have been added to the table that stores if the property utilizes this automation or not. The first setting is a Yes or No. The second field is what they want the primary resident to be charged. The third field is what they want any additional roommate charged that is not set to "Other"


Unit Type Application Charges

Setup one line for the Application Fee. You can make the dollar amount equal to the amount the primary resident should be charged. Make this required and not modifiable. Uncheck all Roommate, Spouse, Guarantor and Other check boxes for this line.


Stored Procedure

To eliminate any conflicts or bottlenecks in the transaction table, I made the update to be a stored procedure. This means that the update is not instant. When the application charges are posted, they will post as to what was setup in the Unit Type Application Charges screen and not with the override logic. Approximately 5 mins after the charges post, the stored procedure will run and update the charges.


Before the procedure runs:


After the procedure runs:


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article