Hold and Processed Flags

Out-of-the-box, the Hold check box is informational-only. It can be set on the Recurring Expenses page or on the Transactions page. Selecting the Hold check box DOES NOT prevent Lucernex from generating rent.

There are some clients which have configured their integrations to use the Hold flag. This is typically done as a filter to indicate that a payment should not be sent to your AP system for processing. If you have questions about how or if the Hold flag is used in your instance of Lucernex, contact your System Administrator.

If the Processed check box is selected you can no longer take action on the record. Typically this check box is selected via your AP integration, if you have one. We recommend you do not set the Processed flag to true unless you are certain you do not want to make any further changes.

Occasionally a user will need to modify a transaction after it has been marked as processed. The transaction will need to be un-processed before changes can be made. We discourage users from un-processing transactions because transactions must be reported for auditing.

Ensure that your transactions are correct prior to generating payments. If you do need to un-process a transaction, contact Support for instructions. Only System Administrators can un-process transactions.

There are some fields on transactions that can be modified via import or API call after the transaction has been marked as processed. Most of these fields relate to the Payment Information section of the Transactions page. The editable fields appear in the list below:

• AppliedToPayTranID

• CheckAmount

• CheckDate

• CheckNumber

• ClientAmount1

• ClientAmount2

• ClientAmount3

• ClientDate1

• ClientDate2

• ClientDate3

• ClientText1

• ClientText2

• ClientText3

• CodeCheckCurrencyTypeID

• CodePaymentMethodID

• ConfirmedFlag

• CoverageBeginDate

• CoverageEndDate

• Description

• Notes

• PreAltRentInvoiceAmount

• PrepaidFlag