Developer Programs
Getting Started
Get started working with Jack Henry's developer programs today.
Fintech Integration Network (FIN)
Jack Henry's Integration Program for Fintechs.
Technical Account Manager (TAM)
Get technical integration help from a single point of contact.
Developer Account
Create a developer acccount to access resources that help you integrate with Jack Henry.
Learn
Shared Responsibility
Learn about shared roles and responsibilities of customers and Jack Henry in open banking.
Developer Use Cases
Find a use case that fits your development needs.
Developer Video Gallery
Watch the latest demos, webinars, and more.
Developer Conference
Connect with industry leaders, gain insights from expert speakers, and explore our latest innovations.
Docs
Authentication Framework
Map customer identities to your existing system IDs.
Banno SDK
Create exceptional banking experiences.
Data Hub
Get deeper access to financial institution data.
Digital Core
Modernize with cloud-native core banking technology.
Enterprise Event System
Respond to events in real-time using this powerful pub/sub-based solution.
jXchange - REST API
Translate business information between Jack Henry and 3rd-party apps using a REST-based API.
jXchange - SOAP API
Translate business information between Jack Henry and 3rd-party apps using a SOAP-based API.
Operational Data Integration (ODI)
Get customized queries for bulk data needs.
Payments
Embed check deposits, ACH, bill pay, cards, and real-time payments.
Payments Orchestrator
Embed multiple payment rails and virtual accounts into your solution.
SymXchange
Query Symitar core member accounts, post transactions, run PowerOn scripts, and more.
Full List of APIs
Begin working with Jack Henry's public APIs to build financial applications today.

ssdb_reserve_plan_transaction_cdc

Pipelined Data Sets > Symitar > ssdb_reserve_plan_transaction_cdc

Column nameDescriptionModeTypeLength
institutionidThis field stores the JH Platform institution identifierREQUIREDSTRING
sourceeventtimeThe timestamp of the change event from the source system (e.g., Debezium's ts_ms field).NULLABLEINTEGER
sourceeventdateThe UTC date of the change event, derived from sourceeventtime.NULLABLEDATE
operationThe 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.NULLABLESTRING
reserveplantransactionkeyInternal use only; SSDB fieldNULLABLEINTEGER
deleteidThis field stores a soft delete flag where 0=not deleted, 1=deletedNULLABLEINTEGER
reserveplankeyInternal use only; SSDB fieldNULLABLEINTEGER
dealerkeyInternal use only; SSDB fieldNULLABLEINTEGER
dealernumberThis field identifies the dealer who originated the loan affected by the transactionNULLABLESTRING
commentflagThis field either stores a comment or indicates that the transaction was monetaryNULLABLEINTEGER
consolenumberIf the transaction is performed from a console, the system stores the console number (0-8999) in this field; otherwise, the system stores 9999 in this fieldNULLABLEINTEGER
effectivedateThis field stores the effective date of the transactionNULLABLEDATE
sequencenumberThe system assigns this number in sequence to each transaction posted on a specific dayNULLABLEINTEGER
postdateThe system updates this field with the current system date when a batch program creates the transaction or you OK the adjustment transactionNULLABLEDATE
posttimeThe system updates this field with the system time when a batch program creates the transaction or you OK the transactionNULLABLEINTEGER
usernumberThe system updates this field with the user number of the person or the batch ID of the batch program that initiated the transactionNULLABLEINTEGER
useroverrideThe system updates this field with the user number of the person who provided an override for the transactionNULLABLEINTEGER
batchsequenceThe system assigns a batch sequence number to each batch job that runs throughout the day to uniquely identify each transaction with a specific batch jobNULLABLEINTEGER
branchThe system updates this field with the branch number associated with the console that initiated the transactionNULLABLEINTEGER
memberbranchThe field is for corporate credit unions only; it is blank for all Dealer Reserve Accounting transactionsNULLABLESTRING
accountnumberThis field identifies the account affected by the transactionNULLABLESTRING
planidThis field contains the value in the Reserve Plan ID field for the related Dealer Reserve Plan involved in this transactionNULLABLESTRING
actioncodeThis field identifies the action performed by the transactionNULLABLESTRING
sourcecodeThis field identifies the source of the transactionNULLABLESTRING
descriptionFor most transactions this field contains a 16-character system-defined description of the transactionNULLABLESTRING
activitydateThe system updates this field with the current system dateNULLABLEDATE
balancechangeThe system updates this field with the amount of the transactionNULLABLEINTEGER
newbalanceThis field stores the sum of the Balance field (for that reserve plan) and the Balance Change fieldNULLABLEINTEGER
commentThis field stores the text entered for Comment transactionsNULLABLESTRING
participanttypeThis field stores a numeric group identifier for the participantNULLABLEINTEGER
loanidThis field stores the ID of the Loan record related to the transactionNULLABLESTRING
adjustmentcodeThis field indicates whether the transaction included an Adjustment (Z) transactionNULLABLEINTEGER

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