Manage your reports

Sips report types and formats

Sips provides reports in CSV files form only, with two different possible formats:

• The legacy format, also known as the "TABLE_VX" format.
• The new format, also known as the "TAB20_VX" format.

You can confirm your report format in the file header. In Sips, you can choose the field separator (delimiter). We provide fixed field lists for each format to ensure consistency and reliable parsing.
Sips provides 4 types of reports which are described in the following chapters:

• Transaction reports (JT)
• Operation reports (JO)
• Financial reconciliation reports (JRB)
• Chargeback reconciliation reports (JRI)

Transactions and Operations Reports

• Transaction Reports list all transactions in your webshop since the previous report, including accepted and refused payments.
• Operation Reports list status changes in the transaction lifecycle, such as cancellation, validation, refund, and capture.

Reconciliation Reports

A reconciled transaction is one where:

• The acquirer bank or financial institution (card-payment processor) sends feedback to the Sips payment platform in a dedicated feed, with additional data.
• The payment platform verifies the transaction and integrates this data.

With reconciled transactions, we produce reconciliation reports for you that combine payment platform data with acquirer data.

There are two types of Reconciliation Reports for two different purposes:

• Financial Reconciliation Reports: The acquirer sends feedback confirming that transactions were successfully sent to clearing (settlement processing). This feedback adds financial data such as amounts credited to your bank account and fees. In general, this feedback and its associated reconciliation come shortly after we sent the transactions to the acquirer.
• Chargebacks Reconciliation Reports: The acquirer’s feedback to the payment platform may flag transactions as chargebacks (cardholder disputes) and provide data such as date, reason code, and a chargeback reference for dispute handling. A chargeback can occur after a delay, as the dispute process takes time.

Create reports in Direct with the e-Portal

The e-Portal is our web interface composed of several modules. The "Omnichannel Reporting" module lets you visualise and manage your transactions. You can set up, monitor, and analyse your payments and transactional data. You can access the full e-Portal User Guide on the e-Portal itself. Click the question mark next to your user name.

Choose "Immediate Reports", then Journal to open an interactive transaction view. The rows depend on your selected time range and filters. The columns depend on your settings under "Customize display". You can add, remove, and reorder columns.

The Data Dictionary is the complete list of available columns. You can consult and download this document from the e-Portal.

Immediate Reports generate reports directly in the e-Portal user interface. You can download them with the "Export" button. If you want to automate report generation and delivery:

• Use "Create a subscription" to configure automated exports.
• Use "Scheduled reports" to set up regular delivery.

Refer to the e-Portal User Guide for step-by-step procedures. We are happy to help you.

Financial Reconciliation Reports

You can generate a Financial Reconciliation Report (an equivalent of a Sips JRB) by

• Applying a filter to include only transactions where the "Reconciliation status" equals "Reconciled". This field is in the "Reconciliation information" category.
• Using "Customize display" to add the columns you need from the "Reconciliation information" category.

Field equivalences for the TABLE_VX format

Here is the HTML table with the content unchanged from the document:

#	JRB field name	e-Portal equivalent field(s)	Comments
1	ENTETE	-	Record type identifier within JRB, no need for an equivalent
2	MERCHANT_COUNTRY
3	MERCHANT_ID	PSPID
4	CONTRACT	Merchant ID
5	PAYMENT_DATE	Transaction ID (Worldline)	See (1)
6	TRANSACTION_ID	Transaction ID (Worldline)	See (1)
7	ORIGIN_AMOUNT	-
8	CURRENCY_CODE	Currency	Currency in which BRUT_AMOUNT is expressed; see (2)
9	CARD_TYPE	Scheme
10	ORDER_ID	Order reference
11	RETURN_CONTEXT	-
12	CUSTOMER_ID	-
13	OPERATION_TYPE	Transaction type	Also, in some way "Amount"; see (2)
14	OPERATION_NUMBER	Transaction ID (Worldline)	See (1)
15	REMITTANCE_DATE	Capture date	See (3)
16	REMITTANCE_TIME	Capture date	See (3)
17	BRUT_AMOUNT	Amount	See (2)
18	MATCH_STATUS	Reconciliation status	To be used with filter "Reconciliation status = Reconciled"
19	REMITTANCE_NB	Capture number (acquirer)
20	NET_AMOUNT	Net amount (acquirer)
21	COMMISSION_AMOUNT	Commission	See (4)
22	COMMISSION_CURRENCY	Commission	See (4)
23	COMMISSION_OPER_CODE	Commission	See (4)
24	AUTHOR_ID	Authorization number
25	SPECIFIC_DATA	-
26	REJECT_AMOUNT	-
27	REJECT_REASON	-
28	ORDER_CHANNEL	Transaction channel; ECI	Imperfect equivalence; two fields globally cover the need
29	BRUT_AMOUNT_ACQ	-	See (5)
30	REMITTANCE_TYPE	-	See (5)
31	TOTAL_BRUT_REM_ACQ	-	See (5)
32	TOTAL_COM_REM_ACQ	-	See (5)
33	TOTAL_NET_REM_ACQ	-	See (5)
34	BANK_TRANSFER_ID	-
35	BANK_TRANSFER_DATETIME	-
36	COMMISSION_TVA	-
37	VALUE_DATE	-
38	INTERCHANGE_FEE	Interchange fee
39	CARD_INTERCHANGE_CATEGORY_CODE	Card type	Imperfect equivalence
40	SETTLEMENT_MODE	-
41	ACQUISITION_TYPE	-
42	FEES_DEBIT_NUMBER	-
43	ACQUIRER_RESPONSE_MESSAGE	-
44	ACQUIRER_RECONCILIATION_DETAIL	-

(1) Sips and e-Portal use different data models and names. A Sips JRB (Financial Reconciliation Report) lists reconciled Sips operations. In Sips, you identify an operation with the triplet (PAYMENT_DATE, TRANSACTION_ID, OPERATION_NUMBER). In e-Portal, the equivalent entity is a Transaction. You identify it with the field "ID transaction (Worldline)". Therefore, the correct field mapping is:

Sips (PAYMENT_DATE, TRANSACTION_ID, OPERATION_NUMBER)
Vs
e-Portal "ID transaction (Worldline)".

(2) Amounts in e-Portal are managed differently from Sips. Sips uses three fields. e-Portal uses one.

In e-Portal, you enter amounts in a single Amount field that contains:

• A sign character (blank for positive, "-" for negative) indicating the DEBIT/CREDIT direction.
• A numeric value as a floating number in currency units (for example, 12.34).
• A currency code as a three-letter ISO code (for example, EUR).

In Sips, amounts are split across three fields:

• An absolute numeric value in an "amount"-suffixed field, expressed as an integer in a fractional unit of the currency. By default this is the least subunit (for example, cents for euros). In some cases the unit is smaller (for example, one hundredth of a cent).
• A separate field for the DEBIT/CREDIT direction.
• A separate field for the currency.

Example: the field equivalence is

Sips (OPERATION_TYPE, BRUT_AMOUNT, CURRENCY_CODE)
VS
e-Portal Amount.

(3) The e-Portal field "Capture date" is a datetime and is equivalent to the Sips pair "REMITTANCE_DATE" and "REMITTANCE_TIME".

(4) As in (2), the field equivalence is:

Sips (COMMISSION_OPER_CODE, COMMISSION_AMOUNT, COMMISSION_CURRENCY)
Vs
e-Portal "Commission".

(5) These fields applied only to Sips when LCL was the acquirer. You can ignore them in e-Portal.

Field equivalences for the TAB20_VX format

#	JRB field name	e-Portal equivalent field(s)	Comments
1	recordCode	-	Record type identifier within JRB, no need for an equivalent
2	merchantId	PSPID
3	transactionReference	Transaction ID (Worldline)	See (6)
4	operationSequence	Transaction ID (Worldline)	See (6)
5	transactionDateTime	Server date
6	orderId	Order reference
7	orderChannel	Transaction channel; ECI	Imperfect equivalence; two fields globally cover the need
8	paymentMeanBrand	Scheme
9	paymentMeanType	-
10	operationType	Transaction type	Also, in some way "Amount"; see (7)
11	remittanceDateTime	Capture date
12	remittanceNumber	Capture number (acquirer)
13	paymentStatus	Reconcilation status	To be used with filter "Reconciliation status = Reconciled"
14	currencyCode	Currency	Currency in which grossAmount is expressed; see (7)
15	originAmount	-
16	grossAmount	Amount
17	netAmount	Net amount (acquirer)
18	feeCurrency	Commission	See (8)
19	feeAmount	Commission	See (8)
20	s10TransactionIdDate	-	See (9)
21	s10TransactionId	Transaction ID (Worldline)	See (9)
22	acquirerContractNumber	Merchant ID
23	authorisationId	Authorization number
24	feeType	Commission	See (8)
25	fundTransferNumber	-
26	settlementMode	-
27	returnContext	-
28	customerId	-
29	interchangeFee	Interchange fee
30	cardInterchangeCategoryCode	Card type	Imperfect equivalence
31	lastMerchantOperationDateTime	-
32	lastMerchantOperationName	-
33	mandateId	-
34	acquisitionType	-
35	feesDebitNumber	-
36	settlementArchivingReference	Acquirer Reference
37	acquirerResponseMessage	-
38	acquirerReconciliationDetail	-
39	paymentMeanDataProvider	-
40	initialHolderAuthentProgram	-
41	initialAuthentDateTime	-
42	initialHolderAuthentType	3DS flow	The equivalence holds if the transaction is a CIT
43	initialChallengeMode3DS	3DS challenge indicator	The equivalence holds if the transaction is a CIT
44	merchantToken	-

(6) Sips and e-Portal use different models and names. A Sips JRB lists reconciled Sips operations. You identify a Sips operation with the pair (transactionReference, operationSequence). In e-Portal, the equivalent entity is a Transaction, identified by the field "ID transaction (Worldline)". Therefore, the field mapping is

Sips (transactionReference, operationSequence)
VS
e-Portal "ID transaction (Worldline)".

(7) Amounts in e-Portal differ from Sips. Sips uses three fields. e-Portal uses one.

In e-Portal, the Amount field includes:
* A sign character (blank for positive, "-" for negative) indicating the DEBIT/CREDIT direction.
* A numeric value as a floating number in currency units.
* A currency as a three-letter ISO code.

In Sips, amounts are split across:
* An integer value in an "…amount" field, expressed in a fractional unit of the currency. By default this is the least subunit (for example, cents for euros). In some cases the unit is smaller (for example, one hundredth of a cent).
* A separate field for the DEBIT/CREDIT direction.
* A separate field for the currency.

Example:
Sips (operationType, grossAmount, currencyCode)
Vs
e-Portal Amount

(8) As in (7), the field equivalence is:
Sips (feeType, feeAmount, feeCurrency)
Vs
e-Portal "Commission"

(9) The fields s10TransactionIdDate and s10TransactionId are Sips 1.0 legacy identifiers for a transaction. Sips 2.0 replaces them with transactionReference. You should map them in e-Portal to the same field: "ID transaction (Worldline)".

Chargeback Reconciliation Reports

You can generate a Chargebacks Reconciliation Report (equivalent to a Sips JRI, chargeback reconciliation) by following these steps:

• Open "Immediate Reports" and select "Chargeback".
• Apply desired time range and filters.
• Use "Customize display" to add columns, especially those in the Chargeback information category.

Field equivalences for the TABLE_VX format

#	JRI field name	e-Portal equivalent field(s)	Comments
1	ENTETE	-	Record type identifier within JRI, no need for an equivalent
2	MERCHANT_COUNTRY	-
3	MERCHANT_ID	PSPID
4	CONTRACT	Merchant ID
5	DATE_NUM	Transaction ID (Worldline)	See (10)
6	TRANSACTION_ID	Transaction ID (Worldline)	See (10)
7	OPERATION_TYPE	Transaction type
8	SOURCE_AMOUNT	Initial transaction amount
9	SIRET	Merchant legal ID
10	UNPAID_NB	Chargeback reference
11	UNPAID_CODE	Chargeback reason code
12	CURRENCY_CODE	Currency
13	CONTRACT_TYPE	-
14	POS_NB	POS
15	REMITTANCE_DATE	Capture date
16	EXCHANGE_AMOUNT	-
17	VALUE_DATE	-
18	UNPAID_AMOUNT	Chargeback amount
19	EXCHANGE_UNPAID_AMOUNT	-
20	EXCHANGE_CURRENCY_CODE	-
21	CHARGED_BANK_CODE	-
22	CHARGED_COUNTER	-
23	CHARGED_ACCOUNT	-
24	CHARGED_ADMIN_COUNTER	-
25	REMITTANCE_ID	Capture number (acquirer)
26	MATCH_STATUS	-
27	CUSTOMER_ID	-
28	ORDER_ID	Order reference
29	RETURN_CONTEXT	-
30	TRANSACTION_STATUS	-
31	CURRENT_AMOUNT	-
32	ORIGIN_AMOUNT	-
33	CARD_TYPE	Scheme
34	CHARGED_CARD_TYPE	-
35	UNPAID_SETTLE_DATE	Chargeback settlement date
36	UNPAID_DOC_REASON	Document request reason
37	UNPAID_DOC_DATE	Document request date
38	ORDER_CHANNEL	Transaction channel; ECI	Imperfect equivalence; two fields globally cover the need
39	BANK_TRANSFER_ID	-
40	BANK_TRANSFER_DATETIME	-
41	COMMISSION_TVA	-
42	COMMISSION_AMOUNT	-
43	UNPAID_NATIVE_CODE	-
44	SDD_MANDATE_ID	-

(10) Sips and e-Portal use different models and names. A Sips JRI lists operations reconciled with a chargeback.

You identify a Sips operation by (DATE_NUM, TRANSACTION_ID, OPERATION_NUMBER). In e-Portal, the equivalent entity is a Transaction identified by "ID transaction (Worldline)".

Field mapping:
Sips (DATE_NUM, TRANSACTION_ID, OPERATION_NUMBER)
Vs
e-Portal "ID transaction (Worldline)". OPERATION_NUMBER is not provided in JRI.

Field equivalences for the TAB20_VX format

No.	JRB field name	e-Portal equivalent field(s)	Comments
1	recordCode	-	Record type identifier within JRI, no need for an equivalent
2	merchantId	PSPID
3	acquirerContractNumber	Merchant ID
4	transactionDateTime	Server date
5	transactionReference	Transaction ID (Worldline)
6	operationType	Transaction type
7	sourceAmount	Initial transaction amount
8	merchantLegalId	Merchant legal ID
9	chargebackAcquirerReference	Chargeback reference
10	chargebackReasonCode	Chargeback reason code
11	currencyCode	Currency
12	contractType	-
13	posNb	POS
14	remittanceDatetime	Capture date
15	exchangeAmount	-
16	valueDate	-
17	chargebackAmount	Chargeback amount + Currency
18	exchangeUnpaidAmount	-
19	exchangeCurrencyCode	-
20	chargedBankCode	-
21	chargedBankCounter	-
22	chargedBankAccount	-
23	chargedBankAdminCounter	-
24	pbaRemittanceNumber	Capture number (acquirer)
25	customerId	-
26	orderId	Order reference
26bis	transactionStatus	transactionStatus	-
27	currentAmount	-
28	originAmount	-
29	paymentMeanBrand	Scheme
30	paymentMeanType	-
31	chargebackSettlementDate	Chargeback settlement date
32	chargebackDocumentRequestReason	Document request reason
33	chargebackDocumentRequestDate	Document request date
34	orderChannel	Transaction channel; ECI	Imperfect equivalence; two fields globally cover the need
35	s10TransactionId	Transaction ID (Worldline)
36	s10TransactionIdDate	Transaction ID (Worldline)
37	maskedPan	Card number
38	settlementArchivingReference	Acquirer Reference
39	mandateId	-
40	returnContext	-
41	networkCode	-
42	acquirerResponseMessage	-
43	acquirerReconciliationDetail	-
44	paymentMeanDataProvider	-
45	initialHolderAuthentProgram	-
46	initialAuthentDateTime	-
47	initialHolderAuthentType	3DS flow	Holds if this transaction is an initial CIT. See (11)
48	initialChallengeMode3DS	3DS challenge indicator	Holds if this transaction is an initial CIT. See (11)
49	authentDateTime	-
50	authentAmount	-
51	paymentPattern	-
52	holderAuthentStatus	-
53	holderAuthentProgram	-
54	holderAuthentRelegationCode	3DS liability
55	holderAuthentType	3DS flow	Holds if this transaction was (re)authenticated. See (11)
56	challengeMode3DS	3DS challenge indicator	Holds if this transaction was (re)authenticated. See (11)
57	transactionInitiator	-
58	merchantToken	-

(11) In Sips, you use two sets of authentication fields. CIT means "Cardholder Initiated Transaction". Fields with the "initial" prefix store authentication from the initial CIT. Fields without the prefix store authentication or reauthentication of the current transaction. In e-Portal, equivalent fields relate only to the current transaction. Field population varies based on whether the current transaction is the initial CIT and whether it was authenticated or reauthenticated.