Periodic billing statement does not include transaction code 530 in the transaction activity

• Related Articles

• Periodic Billing Statement Shows Transaction Activity for Entire History of the Loan instead of only Last Month's Transaction Activity

  When you produce a Periodic Billing Statement for a loan, you may find that the transaction activity on the Periodic Billing Statement shows activity for the entire history of the loan, instead of just the expected activity for the past month. ...

• Periodic Billing Statement Event Does Not Include Loans that are set up with Exception Mail Stops or Coupon Stops

  You may find that when you run the Periodic Billing Statement Event to produce and print the Periodic Billing Statements, that loans with either Exception Mail Stops or Coupon Stops are not included. You want to produce and print Periodic Billing ...

• Periodic Billing Statement is Incorrectly Generated for a Current, Fixed Rate, Coupon Loan

  You may find that on a loan that is set up as payment method Coupon, and is a current fixed rate loan, and is included in your NCP normal export or the NCP-Year End export, that a Periodic Billing Statement is being generated and produced by the ...

• HFS Billing Statement Export Event Does Not Include the Delinquency Notice Information in the F1 Record

  You may find that the delivered Servicing Director Periodic Billing Statement will display a Delinquency Notice message box for an appropriate loan, but this message does not appear on the Servicing Director HFS Billing Statement Export Event file ...

• Disbursement Error Code 8104 Intervening Payment Activity

  Disbursement Error Code 8104 Intervening Payment Activity Root Cause: The Error occurs when attempting to post a Disbursement with an Effective date prior to the last payment posted to a loan. The procedure calculates accrual adjustments for ...