Posting

Method

Posting(PostingRequest)

This section will provide example posting workflows as well as the REST methods available (overview of the parameters for the request, response, and examples).

In planning the design for your solution, below are additional considerations specific to posting that should be reviewed beyond the considerations outlined in the section Real-time Workflow Considerations.

Memo vs Hard post: One of the first things you should review before planning the design for your solution is to review the capabilities of the core system and the methods available to you regarding handling posting. There are pros and cons to posting in real-time via a memo or hard post, but the core may have limitations that dictate which options are available for real-time posting through your solution.

Memo posting real-time:

• Pro: Memo posting can reduce the design complexity with minimal impact to the Financial Institution operationally as the simplest design only utilizes the Deposit Submitted alert type and relies on a posting file generated from the JHA/Ensenta system to hard post the final amount of each check and typically just allow checks that the Financial Institution rejected to expire.
• Con: There may be limitations for available options in defining funds availability and there may be challenges for the Financial Institution in identifying a process for consuming a posting file to hard post the deposits (more commonly an issue for Credit Unions).

Hard posting real-time:

• Pro: There is no need for the Financial Institution to consume a posting file and may have more flexibility in defining funds availability.
• Con: The design complexity is typically higher if you are looking to minimize the operational impact to the Financial Institution since you would need to incorporate all five alert type events and handle Multiple Status Alert Events. The simpler the design complexity your solution has, the greater operational impact it typically has on the Financial Institution. Example: If your solution supports hard posting, but only utilized the Deposit Submitted alert type, any adjustments to the check amount and any checks rejected by the Financial Institution must be manually handled by the Financial Institution on the core system (manually adjust or reverse the amount). (See - Multiple Status Alert Events)

General Ledger Account: Relating back to the section Auditing/Balancing, to simplify reporting and balancing requirements for the Financial Institution, it is recommended that you work with the Financial Institution to have a General Ledger Account created on the Financial Institution’s end for your solution to pull funds from for posting. A General Ledger Account specific to your solution will allow for greater visibility from a reporting perspective and simplify balancing procedures for the Financial Institution.

Parameters

TYPE	NAME	DESCRIPTION
PostingRequest	request

Returns

TYPE	DESCRIPTION
PostingResponse

Example Request

{
	"ECVersion": "P.1.1",
	"ECAlertEventId": "2",
	"ECAlertLogId": "122946",
	"ECAlertLogDTTMMilitary": "2019-11-04T09:30:44",
	"DataItems": [
		{
			"Name": "ECAcceptedBy",
			"Value": "Test FI"
		},
		{
			"Name": "ECAcquirerID",
			"Value": "8257"
		},
		{
			"Name": "ECReceiptNumber",
			"Value": "93083182"
		},
		{
			"Name": "ECUnmaskedAcctHolderNum",
			"Value": "55555"
		},
		{
			"Name": "ECUnmaskedAcctNum",
			"Value": "12345"
		},
		{
			"Name": "ECAcctTypeCd",
			"Value": "01"
		}
	],
	"SubItems": [
		{
			"ItemType": "DEPOSITITEM"
			"DataItems": [
				{
					"Name": "ECTransactionDate",
					"Value": "November 04, 2019 9:30 AM PT"
				},
				{
					"Name": "ECHoldCode",
					"Value": "L"
				},
				{
					"Name": "ECStatusId",
					"Value": "6"
				},
				{
					"Name": "ECCheckNumber",
					"Value": "000001"
				},

				{
					"Name": "ECOriginalAmountNoCurrency",
					"Value": "5.00"
				},
				{
					"Name": "ECApprovedAmountNoCurrency",
					"Value": "5.00"
				},
				{
					"Name": "ECRejectReasonCode",
					"Value": ""
				},
				{
					"Name": "ECRejectReason",
					"Value": ""
				},
				{
					"Name": "ECRejectReasonOverride",
					"Value": ""
				},
				{
					"Name": "ECCheckFrontBase64",
					"Value": "<!-- Base64 Image -->"
				},
				{
					"Name": "ECCheckBackBase64",
					"Value": "<!-- Base64 Image -->"
				}
			],
		}
	]
}

Example Response

{
  "DataItems": null,
  "ResponseCode": "00",
  "ResponseDescription": "success"
}