Settlement account posting

The Settlement engine creates posting transmissions for accumulators that are configured to post and have not already posted. Settlement performs both originator posting, which is for inbound batches, and direct send posting, which is for outbound transmissions. Settlement checks if posting transmissions need to be created for the posting accumulators when an inbound batch is received from a participant, an outbound transmission is sent to a participant, or the business day state changes. For more information about configuring an accumulator to post, see Manage Accumulators page.

If posting transmissions need to be sent, they are sent to the default account for the relevant participant. Refer to Originator posting and Direct send posting for more information about determining the participant that is used for each type of posting. If a participant with a default account is not found, the Settlement engine does not create a posting transmission and logs the following message: IZRTS017W - No account defined for originator. Cannot post balancing transactions. For more information about creating a default account for a participant, see Manage Partners Page and Accounts Pages.

Originator posting

For originator posting, Settlement checks if posting transmissions need to be created for the posting accumulators when an inbound batch is received from a participant or the business day state changes.

The account information from the participant that sent the inbound batch is used to settle with the originator. When the sending participant does not have a default account configured, the account information from the sender is used instead. The default account information from the appropriate participant is used to create payments with values that offset the amounts in the related accumulator data records.

When Transaction Server notifies Settlement that an inbound batch has been ingested, the Settlement engine examines the accumulator data associated with the inbound batch to determine if there are any posting accumulators that require that a posting transmission be created for the batch. If necessary, a posting transmission that has one batch and one payment transaction for each of the posting accumulators associated with the batch is created.

When Transaction Server notifies Settlement that a business day state change has occurred, the Settlement engine examines the accumulator data associated with the business day to determine if there are any posting accumulators that require that a posting transmission be created. Accumulator data is associated with the business day when the date of the accumulator data matches the date of the changed business day and the category of the changed business day matches the category of the business day associated with the inbound batch. If posting is necessary, one or more posting transmissions with associated batches and transactions are created. Transmissions and batches with identical attributes are combined into a single transmission and batch.

For more information about the business day states for Settlement account posting, refer to Business day status changes for posting

By default, the Transaction Server scheduler is configured to send messages to Settlement whenever an inbound batch is ingested. An example event is in the SchedulerReference.xml configuration file:
<EVENT>
   <NAME>Settlement - Prime - ACH, CPS</NAME>
   <TYPE>PresentmentStateChange</TYPE>
   <TYPE>PresentmentColumnChange</TYPE>
   <TYPE>PresentmentGroupColumnChange</TYPE>
   <EXEC>
      com.ibm.paydir.ima.txsvr.event.appbridge.PresentmentStatesEventHandler
   </EXEC>
   <PARAMETER name="workType">Settle</PARAMETER>
   <PARAMETER name="msgType">prime</PARAMETER>
   <PARAMETER name="presStates1">CAPTURED,ACTIVITY_MONITORED</PARAMETER>
   <PARAMETER name="group.condition">ACCEPTED</PARAMETER>
   <PARAMETER name="condition">ACCEPTED</PARAMETER>
   <PARAMETER name="pending">N</PARAMETER>
   <PARAMETER name="presLevel">PROC</PARAMETER>
   <PARAMETERREF>schedulerReferenceProperties</PARAMETERREF>
   <PARAMETERREF>sendToSettlement</PARAMETERREF>
</EVENT>

Direct send posting

For direct send posting, Settlement checks if posting transmissions need to be created for the posting accumulators when an outbound transmission is sent to a participant or the business day state changes.

The default account information from the participant associated with the direct send endpoint is used to create the payments that settle direct send deliveries.

When Transaction Server notifies Settlement that an outbound transmission has been sent, the Settlement engine examines the accumulator data associated with the outbound transmission to determine if there are any posting accumulators that require that a posting transmission be created for the outbound transmission. If necessary, a posting transmission that has one batch and one payment transaction for each of the posting accumulators associated with the outbound transmission is created.

When Transaction Server notifies Settlement that a business day state change has occurred, the Settlement engine examines the accumulator data associated with the business day to determine if there are any posting accumulators that require that a posting transmission be created. Accumulator data is associated with the business day when the date of the accumulator data matches the date of the changed business day and the category of the changed business day matches the category of the business day associated with the inbound batch. If posting is necessary, one or more posting transmissions with associated batches and transactions are created. Transmissions and batches with identical attributes are combined into a single transmission and batch.

For more information about the business day states for Settlement account posting, refer to Business day status changes for posting

By default, the Transaction Server scheduler is configured to send messages to Settlement whenever an outbound transmission is sent. An example event is in the SchedulerReference.xml configuration file:
<EVENT>
   <NAME>Settlement Distribution - Outbound Presentment Group</NAME>
   <TYPE>OutPresentmentGroupState</TYPE>
   <EXEC>
      com.ibm.paydir.ima.txsvr.event.appbridge.OutPresentmentGroupStatesEventHandler
   </EXEC>
   <PARAMETER name="workType">Settle</PARAMETER>
   <PARAMETER name="msgType">outboundPresentmentLoad</PARAMETER>
   <PARAMETER name="presStates1">SENT</PARAMETER>
   <PARAMETERREF>schedulerReferenceProperties</PARAMETERREF>
   <PARAMETERREF>sendToSettlement</PARAMETERREF>
</EVENT>

Business day status changes for posting

When the state of a business day changes, Settlement checks if posting transmissions need to be created for the posting accumulators. Settlement supports only the following states for posting:

  • Active
  • Reactivate_in_Progress
  • Closed
  • Close_in_Progress
  • Complete
  • Complete_in_Progress
  • Complete_Waiting
  • Purging
  • Purged
  • Purge_in_Progress
  • Purge_Paused
By default, the Transaction Server scheduler is configured to send messages to Settlement whenever a business day is activated. An example event is in the SchedulerReference.xml configuration file:
<EVENT>
   <NAME>Distribution - Business Day Active</NAME>
   <TYPE>BusinessDayStatusChange</TYPE>
   <EXEC>
      com.ibm.paydir.ima.txsvr.event.appbridge.BusinessDayStateEventHandler
   </EXEC>
   <PARAMETER name="msgType">BDayActive</PARAMETER>
   <PARAMETER name="stateName">ACTIVE</PARAMETER>
   <PARAMETERREF>schedulerReferenceProperties</PARAMETERREF>
   <PARAMETERREF>sendToSettlement</PARAMETERREF>
</EVENT>