Skip to main content
Skip table of contents

Customer/Rate Database Maintenance

The Customer/Rate Database contains GL and rate information for customers. This database is used in Leave Screen, Leave Of Absence Invoice Interface and the Secondment Invoice Interface. Refer to these options for more information.

Customer Number

  • Enter the number of customer to work with. The customer number entered must exist in the customer database in Miscellaneous Accounts Receivable (MAR) system.

Revenue GL

  • Enter the revenue GL number to be used by the two Invoice Interface programs.

  • Fields 03-27 control the rate used in the Leave Of Absence (LOA) Invoice Interface.

Leave Days

  • Enter the maximum number of days that will apply to the rate(s) on the same line. The system will use the first line it finds where the days on the leave application are less than or equal to Leave Days field here. For example, organizations may be billed one rate for leaves of 5 days or less, and a higher rate for leaves over 5 days. If this is the case enter two rate lines, one with 5 and the other with say 999. If a leave of absence were 3 days long, it uses the line with 5 days. If a leave were 6 days it uses the line with 999 days on it.

Effect Date 1

  • Enter the date on which RATE 1 becomes effective in (YY)YYMMDD format. The reason for the two dates is in the event of a rate change. If the rate changes effective Sept 1, 1999, enter this date in the EFFECT DATE 2 field and new rate in the RATE 2 field.

Rate 1

  • Enter the rate that is effective as of Date 1.

Effect Date 2

  • Enter the date on which Rate 2 becomes effective in (YY)YYMMDD format.

Rate 2

  • Enter the rate that is effective as of Date 2.

Invoice If No Rep Emp

  • Enter 'Y' if an invoice should be created whether or not there is a replacement employee needed to cover the leave of absence.

  • Enter 'N' if there should not be an invoice created if there is no replacement employee.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.