Queue On Demand Statement

A statement in NLS is generally queued automatically, based on parameters in the loan setup. And on a periodic basis, the loan servicer will print out the statements that are currently in the queue. This is often a daily process.

It may sometimes be necessary to modify an outstanding billing on a loan and then send out a new statement that will reflect this modification. A reprint of the original statement will not be sufficient, as a reprint is an identical image to the original statement which was generated. A brand new statement needs to be queued based on the values currently present on the loan. This can be accomplished by queueing an on demand statement.

Query the loan on which the payments due have been modified. Select the menu Actions > Queue On-Demand Statement.Select Loan > Queue On Demand Statement. NLS will generate data to the statement queue table in the database which will be similar to the original statement, but which will take into account any changes that have been made to the loan since that old statement was queued.

Since an on-demand statement represents an instance in time, it has no statement period the way a standard statement does. This means that if you are using a statement code which contains transaction history for a period, there may be no such history on the on-demand statement, as there is no period in which to reflect the history.

Once the on-demand statement has been queued, it may be printed normally from the Statement Queue.

For information on printing statements, see Statements.

NLS 5.8 and later

This command may be disabled per user/group by setting the security in Reporting > Statements > Disable Queue On Demand Statement.