ssdb_invoice_cdc
Pipelined Data Sets
>
Symitar
>
ssdb_invoice_cdc
| Column name | Description | Mode | Type | Length |
|---|---|---|---|---|
| institutionid | This field stores the JH Platform institution identifier | REQUIRED | STRING | |
| sourceeventtime | The timestamp of the change event from the source system (e.g., Debezium's ts_ms field). | NULLABLE | INTEGER | |
| sourceeventdate | The UTC date of the change event, derived from sourceeventtime. | NULLABLE | DATE | |
| operation | The type of operation that caused the change event (e.g., 'c' for create/insert, 'u' for update, 'd' for delete, 'r' for read). This corresponds to Debezium's 'op' field. | NULLABLE | STRING | |
| invoicekey | Internal use only; SSDB field | NULLABLE | INTEGER | |
| deleteid | This field stores a soft delete flag where 0=not deleted, 1=deleted | NULLABLE | INTEGER | |
| vendorkey | Internal use only; SSDB field | NULLABLE | INTEGER | |
| sortrank | Internal use only; SSDB field | NULLABLE | INTEGER | |
| number | This field stores the invoice number as it appears on the vendor's invoice | NULLABLE | STRING | |
| description | This field stores a description of the item purchased with the invoice | NULLABLE | STRING | |
| ponumber | This field stores your credit union's purchase order number | NULLABLE | STRING | |
| approval | This field stores the user number of the person who approved the invoice | NULLABLE | STRING | |
| invoicedate | This field stores the date when this record was created | NULLABLE | DATE | |
| duedate_1 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_2 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_3 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_4 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_5 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_6 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_7 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_8 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_9 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_10 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_11 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| duedate_12 | Each of these 12 fields stores a due date for an installment payment for this invoice | NULLABLE | DATE | |
| dueamount_1 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_2 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_3 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_4 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_5 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_6 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_7 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_8 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_9 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_10 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_11 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| dueamount_12 | Each of these 12 fields stores an amount for an installment payment for this invoice | NULLABLE | INTEGER | |
| duedatefinal | This field stores the date of the final installment payment for this invoice | NULLABLE | DATE | |
| discountdate | This field stores the date by which the credit union must pay this invoice to qualify for a discount | NULLABLE | DATE | |
| discountamount | This field stores the amount of the discount the credit union can take if the invoice is paid by the date in the Discount Date field | NULLABLE | INTEGER | |
| glacctspay | This field stores the GL Account to debit when paying this invoice | NULLABLE | STRING | |
| gldiscount | This field stores the GL Account to credit when taking a discount for this invoice | NULLABLE | STRING | |
| glexpense_1 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_2 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_3 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_4 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_5 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_6 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_7 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_8 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_9 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_10 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_11 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| glexpense_12 | These 12 fields each store the GL account that part of the invoice amount identified in the corresponding Expense Amt # field is expensed to | NULLABLE | STRING | |
| expensetable_1 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_2 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_3 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_4 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_5 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_6 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_7 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_8 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_9 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_10 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_11 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expensetable_12 | These 12 fields each store the number of the GL distribution table for that part of the invoice amount identified in the corresponding Expense Amt # field that designates the GL account the amount is expensed to | NULLABLE | INTEGER | |
| expenseamount_1 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_2 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_3 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_4 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_5 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_6 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_7 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_8 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_9 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_10 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_11 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| expenseamount_12 | These 12 fields each store the amount to expense for that part of the invoice | NULLABLE | INTEGER | |
| status | This field stores a code that indicates the status of this Invoice record | NULLABLE | INTEGER | |
| expeffectivedate | This field stores the date you want to use as the effective date of the expense posting | NULLABLE | DATE | |
| exppostdate | This field stores the current system date when the GL Posting batch program posts this expense | NULLABLE | DATE | |
| lastfmdate | This field stores the date of the last file maintenance of the Invoice record | NULLABLE | DATE | |
| paymentdate_1 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_2 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_3 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_4 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_5 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_6 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_7 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_8 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_9 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_10 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_11 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentdate_12 | These fields each store the payment date to expense for that part of the invoice | NULLABLE | DATE | |
| paymentamount_1 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_2 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_3 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_4 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_5 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_6 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_7 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_8 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_9 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_10 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_11 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentamount_12 | These fields each store the payment amount for that part of the invoice | NULLABLE | INTEGER | |
| paymentcheck_1 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_2 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_3 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_4 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_5 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_6 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_7 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_8 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_9 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_10 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_11 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| paymentcheck_12 | These fields each store the check number for that part of the invoice | NULLABLE | STRING | |
| discounttaken | This field stores the total of all discounts taken for this invoice | NULLABLE | INTEGER | |
| locator | This field stores a unique number within each Accounts Payable Invoice record that can be used as a unique identification of this record | NULLABLE | INTEGER | |
| type | This field stores a credit union-defined code the system uses to match this record with the values in the AP Invoice Type parameter type in the AP Work Flow Parameters | NULLABLE | INTEGER | |
| event | This field stores the number of the current invoice workflow event for the invoice | NULLABLE | INTEGER | |
| eventdate | This field stores the date the invoice workflow value in the Event Number field last changed | NULLABLE | DATE | |
| user | This field stores the user number of the person to whom the invoice has been forwarded or the user number of the person who created the invoice, if the invoice has not been forwarded | NULLABLE | INTEGER | |
| completedactions_1 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_2 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_3 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_4 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_5 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_6 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_7 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_8 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_9 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_10 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_11 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_12 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_13 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_14 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_15 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_16 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_17 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_18 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_19 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_20 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_21 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_22 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_23 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_24 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_25 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_26 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_27 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_28 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_29 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_30 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_31 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_32 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_33 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_34 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_35 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_36 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_37 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_38 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_39 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_40 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_41 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_42 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_43 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_44 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_45 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_46 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_47 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_48 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_49 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| completedactions_50 | These fields each store a code indicating if the associated Action in the AP workflow has been completed. Additional actions are available through a pop-up menu | NULLABLE | INTEGER | |
| paymentmethod | This field stores a code that identifies the method of payment for an invoice | NULLABLE | INTEGER | |
| achtrancodeout | This field stores the transaction code used when the outgoing ACH transactions statement is sent via ACH origination | NULLABLE | INTEGER | |
| imageid | If your credit union stores invoices on optical disk using an imaging system, this field stores the Document ID of the associated invoice image | NULLABLE | STRING | |
| achgroupnumber | This field stores the credit union-defined number of the invoice ACH group | NULLABLE | STRING | |
| createaddenda | This field stores a code that indicates whether the system should create Addenda records associated with this record to send CCD Standard Entry Class (SEC) codes | NULLABLE | INTEGER | |
| prenotedfiaccount | If the system has sent an ACH origination pre note, this field stores the number of the DFI account used for the pre note | NULLABLE | STRING | |
| dfiaccount | This field stores the processor's account number at the receiving institution. It is required for the ACH item | NULLABLE | STRING | |
| achacknowledge | NULLABLE | INTEGER | ||
| additionaldesc | This field stores additional descriptive information relating to the invoice | NULLABLE | STRING | |
| recordchangedate | The system stores the system date in this field when you create, change, or save the Accounts Payable Invoice record. Sometimes the system updates this field because the record was saved, even though there may not be any actual changes in the record | NULLABLE | DATE | |
| invoicefrequency | This field stores a code that determines the frequency of the interval between the creation of recurring invoices | NULLABLE | INTEGER | |
| recurrenceenddate | This field stores the date to end the recurring invoices | NULLABLE | DATE | |
| originatinginvoicenumber | This field stores the invoice number of the first invoice in a recurring series | NULLABLE | STRING | |
| totalinvoiceamtdue | This field stores the total invoice amount due | NULLABLE | INTEGER | |
| appaymenttermstype | This field stores a code that identifies the AP payment term table defined in the AP Payment Terms Table parameters | NULLABLE | INTEGER | |
| recurrenceday1 | This field stores the day of the month on which the first invoice should occur for semimonthly recurring invoices. This field also stores the day of the month on which all recurring invoices occur for annual, semiannual, quarterly, bimonthly, or monthly invoices | NULLABLE | INTEGER | |
| recurrenceday2 | This field stores the day of the month on which the second invoice should occur for semimonthly recurring invoices. This field is only used for semimonthly invoices | NULLABLE | INTEGER |
Have a Question?
- Have a how-to question? Seeing a weird error? Get help on our collaborative Discourse page.
- Register for the Developer Office Hours where we answer technical Q&A, in real time, from the audience.
Did this page help you?
Last updated Tue Sep 15 2026