Optional, Ignored, and Output Fields

These fields in the F03B13Z1 table are optional for the user to complete, ignored by the system, or updated by the system and should be left blank:

Field Name	Alias	Type	Length	Definition
Batch Number	RUICU	Number	8	A number used to group receipts together that are processed simultaneously. This number must be uniquely identified in the F03B13Z1 table. If you leave this field blank, the system assigns the batch number from Next Numbers when the Update Receipts Header program is run. It is recommended that you leave this field blank.
Statement Number	RUCTL	Alpha	13	Leave this field blank. The system cannot perform invoice matching if this field contains a value. If you want to pay invoices by statement number, enter the statement number in the Generic Matching Field (RUGMFD).
Generic Matching Field	RUGMFD	Alpha	50	This field is used to reference and locate an invoice for the Known Invoice Match With Amount (R03B50D) and Known Invoice Match Without Amount (R03B50E) algorithms. You can enter one of these values: Document Number Sales Order Number Customer Reference Number Statement Number The system locates the invoice from the value entered in either the RUDOC field or this field.
Reference	RUVR01	Alpha	25	A text field used to enter information about the invoice that is paid by the receipt. This field is informational only.
Payment ID	RUPYID	Number	15	A field used to identify the receipt. The system assigns a number to this field when receipts are processed. The system uses this value as an internal reference to locate the receipt. It is recommended that you leave this field blank.
Auto Cash Upload Status	RUEUPS	Alpha	1	A field used to indicate the status of the transaction during the automatic receipt process. Values are: Blank: The transaction is not processed. B: The transaction is eligible for processing. E: The transaction was processed with errors. H: The transaction was processed by the Update Receipts Header program but was not matched to invoices using the Apply Receipts to Invoices program (R03B50). Y: The transaction is successfully processed. It is recommended that you leave this field blank.
Batch Date - Century	RUDIC#	Number	2	A field to enter the century associated with the batch date. If you leave this field blank, the system assigns the appropriate value to this field based on the batch date entered. It is recommended that you leave this field blank.
Batch Date	RUIDCJ	Date	6	The date that the transaction was entered into F03B13Z1 table. If you leave this field blank, the system updates it with the date that the transaction is processed.
User ID	RUUSER	Alpha	10	The User ID of the person processing transactions.
G/L Date - Century	RUDG#	Number	2	The century associated with the G/L date. It is recommended that you leave this field blank.
Receipt Date - Month	RUDMTM	Number	2	See the note after this table.
Receipt Date - Day	RUDMTD			See the note after this table.
Receipt Date - Year	RUDMTY			See the note after this table.
Receipt Date - Century	RUDMT#			Leave this field blank. The system assigns the century based on the receipt date.
Receipt Date	RUDMTJ	Date	6	The date on the payor's check or the date that you received the check. The system uses the receipt date for informational and reporting purposes only. Enter the receipt date in the format that the database accepts. Some databases enable you to enter the date in the Gregorian format (mmddyy), while others require a Julian date format. The Julian date format is cyyddd (where c=century). Complete the century field by entering 0 (zero) for transactions in the 20th century and 1 for transactions in the 21st century. For example, June 01, 1999 corresponds to a Julian date 099152, while June 01, 2000 corresponds to a Julian date 100153. Alternatively, leave this field blank and complete the fields RUDMTM (mm), RUDMTD (dd), and RUDMTY (yy) in the month/day/year format.
Remark	RURMK	Alpha	30	A text field used to enter information about the receipt. Alternatively, if you are processing drafts and did not complete the Customer Bank Account (RUCBNK) and Customer Bank Transit (RUTNST) fields, you can enter the payor's bank name into this field. The name is used to locate the bank account information from the Bank Transit Number Master File table (F0030). If the system cannot locate the payor's bank account information, the transaction is not processed.
Account Mode	RUAM	Alpha	1	This field specifies the account format of the G/L Bank Account entered. It is recommended that you leave this field blank.
Home Bank Account	RUEHBK	Alpha	20	See the note after this table.
Home Bank Transit	RUEHTN	Alpha	20	See the note after this table.
Payment Instrument	RUPYIN	Alpha	1	A field that specifies the customer's payment method. The value entered in this field must exist in UDC 00/PY (Payment Instrument).
Receipt Type Code	RUTYIN	Alpha	1	Leave this field blank. The value of this field is assigned by the system when the receipt is processed.

Note: Use the Receipt Date - Month (RUDMTM), Receipt Date - Day (RUDMTD) and Receipt Date - Year (RUDMTY) fields to enter the date on the payor's check or the date that you received the check. The system uses the receipt date for informational and reporting purposes only.Enter the receipt date in the mm/dd/yy format if desired. Alternatively, leave these fields blank and complete the Receipt Date field (RUDMTJ).If the system cannot locate a receipt date, it uses the G/L date.

Note:

The Home Bank Account (RUEHBK) and Home Bank Transit (RUEHTN) fields can be used to identify the G/L bank account if the G/L Bank Account field (RUGLBA) is left blank. The G/L bank account must be set up in the F0030 table for the system to locate it based on the values entered in these fields.

If all fields (RUEHBK, RUEHTN, and RUGLBA) are left blank, the system uses the value entered in the default Short Bank Account ID field in the processing option of the Update Receipts Header program.

If the system cannot locate a G/L Bank Account, the system does not process the receipt.