Knowledge Article Page 1 of 2

Settlement Transactions are

cleared in SAP but are not settled
in XiPay
Description Applicable Versions :
SAP R/3 4.0 and greater

Overview / Symptoms :
A Settlement Batch is cleared in SAP; meaning all transactions in the batch have been
cleared from the Credit Card G/L account and a Clearing doc has been posted and
applied to the Bank Settlement Clearing account. However, ALL of the Transactions are
still in the Authorized status in the XiPay Server, the BatchID does not exist in XiPay and
the processor has not yet received a settlement batch request. Or the BatchID does exist
in XiPay but some transactions are missing (e.g are not yet staged for settlement and are
still in authorized status).

Cause :
This can occur when network or RFC failures occur during the Settlement batch process
or if there are data issues with the batch. The standard SAP Settlement process is a send
and forget action – there is no immediate acknowledgment that the batch was sent
and received as in the authorization process. The Settlement process will normally clear
the items in SAP from the Credit Card Clearing Account to the Bank Settlement Clearing
Account and then send the data to Xipay across the Settlement RFC. If the RFC is down
or fails before the RFC call is complete, then XiPay will not receive the batch request.
But as far as SAP is concerned, the batch has been settled and the G/L accounts appear
as if a deposit is pending.

Solution :
Caution: As with any re-capture attempt, verification must be made with the
processor/issuing bank to ensure funding has not occurred for the transactions in
question. Otherwise, potential double-charging of your customers may occur. The
following instructions will resubmit the Batch transactions to XiPay to attempt settlement
again : You will need to know the SAP Batch ID and/or the SAP Clearing Document
number associated with the settlement batch. And for partial batches will need to know
exactly which transactions to resubmit.

Warning: If resubmitting Transactions that are Verbal Auths ( e.g. no value exists in the
Auth Ref Code field in SAP ), a new transaction will be created and settled in XiPay for
each successful attempt of resubmitting, therefore the risk exists for over-charging the
customer if care is not taken.

Prerequisite Checks :
Ensure the data, Network or RFC problems have been resolved.
Validate that ALL transactions in the batch have been cleared in SAP and applied to a
clearing doc ( to discover what SAP documents are associated with a clearing document,
use FB03 to view the Clearing document Overview, then select menu option
"Environment-->Payment usage" ).
Validate that the Settlement Log entry in the TCCLG table for the Batch ID in question
has been recorded by executing SAP transaction FCC4 or FCCR for the Batch ID. If the
Settlement Log entry does not exist for the Batch ID, Run the appropriate Paymetric utility
program called "Manually Update Host Details of SAP Batch" to add the entry (See
Solution 1306 for instructions). Without this program, a manual table update will be
required.
Validate that the SAP BatchID does NOT exist in XiPay, and
Validate that ALL transactions from the Batch are still in the Authorized status 100 in
Xipay. (AuthRefCode in SAP is the TransactionID in XiPay) OR Validate that the SAP
BatchID DOES exist in XiPay, and that the missing transactions from the Batch are still in
the Authorized status 100 in Xipay. (AuthRefCode in SAP is the TransactionID in XiPay)
Validate that the processor has not received a settlement request for the items missing in
the batch.

Solution Options - If all of the above criteria is met, then you have 4 options for re-
attempting a Settlement of the data from SAP to XiPay (listed in order of preference)
CHOOSE ONE:

https://paymetric.force.com/clients/articles/Documentation/Settlement-Transactions-a... 2016/01/22
Knowledge Article Page 2 of 2

**Preferred Method** Execute the Paymetric Repeat Settlement program to re-send the
batch data to XiPay. SAP T-code /n/PMPAY/FCC2. This allows you to enter a batch
number and retransmit ONLY the details of the batch to XiPay. This program will NOT
perform any G/L postings – it simply re-attempts to transmit details of a settled
batch. Selective transactions can also be resubmitted if the batch was partially funded.
For partially settled batches please see related solution "Securing Funding With Partially
Settled Batches or Transaction(s) Missing From Settled Batches".

**Alternate Methods** Execute the SAP transaction FCC2 - Repeat Settlement to re-
send the batch data to XiPay. SAP's transaction does not allow resubmission of a
successful batch (if batch status is in 'OK' status as viewed from FCC4). This scenario
will error out with "Settlement run XXXX already successfully transferred". But SAP did
provide an OSS note to get around this and enable it to be resent. See note: 520771 -
FCC2 Loss of settlement data.

Use SAP transaction FBRA to RESET and REVERSE the batch clearing document as
found in transaction FCC4. Transaction FBRA will basically “un-settle” the
transactions, placing them back in the CREDIT CARD RECEIVABLE account allowing
you to re-run the SETTLEMENT program to capture those transactions into a new batch
with a new batch number and clearing document. All reference on those documents to
the previous batch will be lost.

Settle all the transaction manually from the XiPay GUI using Operations settle. This
option assumes that the settlement amounts MATCH the authorized amounts.

Validate the transactions in XiPay are now staged for Settlement.

Prevention Steps :
If you are not already doing so, we recommend you utilize the Paymetric version of the
Settlement program (/PMPAY/PU_FCC1) to perform your daily settlement batch runs.
This program is an enhanced version of SAP Transaction FCC1. It has the selection
option to PING the RFCs and abort the settlement before the document clearing occurs, if
the RFCs are down at time of execution.

Please review the following XiAssist link for more information:

https://paymetric.info/xiassist/index.html?repeat_settlement_sap.htm
username: pmclient
password: help@paymetric
Please document these credentials for future use.

Related Solutions :
How to update the SAP Settlement Batch log table with the Batch ID
Settlement reconciliation from SAP to Xipay
How to reverse a settled batch in SAP
Securing Funding With Partially Settled Batches or Transaction(s) Missing From Settled
Batches
Configuring the Paymetric Settlement program as a background batch job

Keywords :
/PMPAY/PU_FCC2, /PMPAY/PU_FCC1, PMPAY, FCC2, PCMA Resubmit settlement,
Repeat settlement

https://paymetric.force.com/clients/articles/Documentation/Settlement-Transactions-a... 2016/01/22