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
Admin API
Create solutions for an institution's back office support tools.
Authentication Framework
Map customer identities to your existing system IDs.
Consumer API
Access financial data for user accounts, transactions, and more.
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.
Plugin Framework
Embed the best of the fintech world directly into your user's dashboard.
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.

Transaction Sets

General Ledger > Guides > Transaction Sets

Overview

Transaction Sets are balanced journal entries that post to general ledger accounts. Each transaction set maintains double-entry bookkeeping principles by ensuring debits equal credits.

What are Transaction Sets?

A Transaction Set is a journal entry with one or more debit and credit transactions that affect GL accounts. Transaction Sets ensure your ledger stays balanced according to standard accounting principles.

Requirements

Minimum Transactions

Every Transaction Set must include:

  • At least two transactions (one debit and one credit minimum)
  • At least one debit entry
  • At least one credit entry

Balanced Entries

Transaction Sets must balance according to these rules:

  • Total debits must equal total credits
  • If using multiple effective dates, debits and credits must balance per date
  • Balance is validated before posting

Effective Dating

Current Day Posting (Default)

By default, transactions post to the current business day:

  • No effectiveDate parameter required
  • Simplest method for real-time transactions
  • Updates today’s balances immediately

Prior Date Posting

Post to a prior business day by setting effectiveDate:

  • Use for corrections or adjustments
  • Subject to system-configured limits
  • Useful for period-end adjustments

Date Constraints

  • Prior-date posting limits are configurable
  • Cannot post beyond the configured date range
  • Transactions with the same effective date must balance together

Reversals

Reverse a Transaction Set to negate a previously posted entry.

How Reversals Work

When you reverse a Transaction Set:

  1. A new Transaction Set is created with opposite entries
  2. Debits become credits and credits become debits
  3. Original entry remains in history
  4. New reversal is linked to the original

Reversal Dates

Choose how to date the reversal:

  1. Use Original Date: Omit effectiveDate - reversal uses the same date as the original entry
  2. Use New Date: Provide an effectiveDate to post the reversal on a different date

Common Uses

  • Error Corrections: Reverse incorrect entries
  • Period Adjustments: Reverse and repost with corrections
  • Provisional Entries: Undo temporary entries when final amounts are available

Best Practices

Planning Entries

  1. Group Related Transactions: Keep related debits and credits in one set
  2. Use Clear References: Include meaningful descriptions and reference numbers
  3. Balance by Date: When using multiple dates, ensure each date balances independently
  4. Consider Reversals: Design entries with potential reversals in mind

Effective Date Strategy

  1. Current Day for Operations: Use current-day posting for normal transactions
  2. Prior Dates for Corrections: Use prior-date posting for adjustments only
  3. Check Date Limits: Verify allowed date ranges before backdating
  4. Document Adjustments: Maintain clear audit trails for backdated entries

Error Prevention

  1. Validate Balance: Verify your transaction set balances before submitting
  2. Check Date Ranges: Ensure effective dates are within allowed ranges
  3. Verify Accounts: Confirm all referenced accounts exist and are active
  4. Review Responses: Check API responses for the new Transaction Set ID

Institution Level Configuration

Your administrator can configure:

  • Prior-date posting limits: How far back transactions can be posted
  • Date constraints: Business rules for effective dates
  • Validation rules: Additional requirements for entries

Contact your institution administrator for specific configuration details.

Did this page help you?
Last updated Thu Feb 26 2026