1. VERSIONSHISTORY MERCHANT TRANSACTION RECONCILIATION FILE GENERAL STRUCTURE FILE DETAILED FILE DESCRIPTION...

Transcription

1 MERCHANT TRANSACTION RECONCILIATION FILE FILE DESCRIPTION ACTUAL FROM APRIL 2014 VERSION 2.1 CONTENT 1. VERSIONSHISTORY MERCHANT TRANSACTION RECONCILIATION FILE GENERAL STRUCTURE FILE DETAILED FILE DESCRIPTION MTR FORMAT DEFINITION MTR File Header MTR Batch Header Format MTR - Line Item Format MTR formats for DTL/REJ/ADJ MTR File trailer FILE EXAMPLE...9 Nordea Bank Norge ASA, org. nr Styrelsens säte Stockholm 1

2 1. VERSIONSHISTORY Version Record type Field number Change 2.0 Initial 2.1 DTL/REJ/ADJ 4 Corrected length to MERCHANT TRANSACTION RECONCILIATION FILE GENERAL The Merchant Reconciliation (MR) Service aims for companies that would like to have some form of automated reconciliation of their card transactions. The daily file (MTR- Merchant Transaction Reconciliation file) is a comma separated file that contains: details of all successful daily card transactions the calculated service fees for those transactions adjustments the customer is credited/debited for (not yet including chargebacks) miscellaneous fees monthly notification of the fee settlement rejected items The file will be delivered via Girolink or FTP/VPN with Nordea. Companies can subscribe to this service and receive the file daily. The reporting is based on the organization number of the company. If the Group owns one or more daughters with different organisation numbers, each individual organisation number has to have an agreement with Nordea. All merchant ids within the same organisation number will be automatically included in the file. Nordea can deliver the file that contains all transactions/batches to the specified connection; this can be the main organisation number (mother) as well as individual daughters. This has to be specified in the agreement. These distribution details and certain selection parameters will be saved centrally for every organization number subscribed to the service. Nordea Bank Norge ASA, org. nr Styrelsens säte Stockholm 2

3 3. STRUCTURE FILE The MTR file is build up per organization number, which means that the file can get fairly complex when the organization has several merchants connected to the same organization number. Below you can find a simplified overview of how the file is structured. The monthly notification of fee settlement (BHF), miscellaneous fee (BHM) and batch header (BHD) can occur for all separate merchants connected to the organisation number (0 to many). Every batch header contains at least 1 item (detailed transaction, rejected transaction or adjustment). Adjustments will always have their own header, rejects and detailed items can share a header, based on the batch-id and currency. FHD File Header BHM Misc. Fees BHF Fee Settlement REJ Rejected Item FTR File Trailer BHD Batch Header DTL Detailed Item ADJ Adjustment Nordea Bank Norge ASA, org. nr Styrelsens säte Stockholm 3

4 4. DETAILED FILE DESCRIPTION 4.1. MTR FORMAT DEFINITION The encoding principle of the file is Comma Separated Values MTR File Header The file header consists of one line, which has the following values: # Any line starting with hash sign denotes a comment # Under format the number between the brackets represent the maximum # length # Optional/mandatory states if a field must be present or not # recordtype,mtrid,filereference,company,dateprocess,timeprocess # Example: FHD, ,MTR-file-ref,MTR-company, , # Name Format * Optional= O Mandatory=M Description and Example 1 Record Type Alpha [3] M The constant string FHD 2 MTR id Alpha [12] M Organization number for 3 File Reference the receiver of this file Alpha [10] O File ID generated at file creation (use as reference for Nordea) 4 company Alpha [32] M Company name, enclosed within doublequote characters 5 Date Process YYYYMMDD M Date of creation of file 6 Time Process HHMMSS M Time of creation of file MTR Batch Header Format A batch consists of all transactions for one merchant with the same currency, i.e. a merchant with multi-currency acquiring should get one batch and hence one batch header per currency. A batch header can imply: 1. summary of a normal batch (BHD, including DTL and REJ records) 2. summary of all adjustments for the merchant (BHD) 3. miscellaneous fee (BHM) 4. monthly settlement of the service fees (BHF) The BHM- and BHF-records will be first in the file, they can switch in sequence based on the referenced batch-id (referencebatchid: field 9). After those records the BHD should follow if present. The header consists of one line, which has the following values: Nordea Bank Norge ASA, org. nr Styrelsens säte Stockholm 4

5 # Any line starting with hash sign denotes a comment # Under format the number between the brackets represent the maximum # length # Optional/mandatory states if a field must be present or not # recordtype,merchantid,settlementcurrency,totalsettlement, # signsettlement,totalbatch,signbatch,nrtransactions, # ReferenceBatchId,expSettlDate,bankAccount,totalFee,signFee, # totalfeesettle,feesettleperiod # Examples: BHD, ,SEK, ,D, ,D,1122, # batch-id, , ,1200,c,, # BHF, ,NOK,0,D,0,D,,,,,0,D,815, # BHM, ,SEK,0,D,0,D,1, ,,,50000,D,0, # Name Format * Optional= O Mandatory=M BHM BHF BHD Description and Example 1 Record Type Alpha [3] M M M The constant string BHM/BHF or BHD 2 Merchant ID Alpha [9] M M M Merchant ID 3 Settlement Alpha [3] M M M The settlement currency in Currency 4 Total Settlement 5 Sign SettlementA mount 6 Total Batch 7 Sign Batch 8 Nr Transactions 9 Reference BatchId 10 Exp Date Settle 11 Bank Account 12 Total Fee 13 Sign Fee ISO 4217, all caps. Numeric [12] M M M The total amount settled, with two digits in the fractional part but no decimal point Alpha [1] M M M [D]ebit transaction = Numeric [12] M M M The total amount in the batch including rejects, with two digits in the fractional part but no decimal point Alpha [1] M M M [D]ebit transaction = Numeric [7] M M M The total number of transactions in this batch. Alpha [25] O O M Reference for a batch. YYYYMMDD O O O The expected date of settlement. Alpha [34] O O O The bank account to be used for settlements. Numeric [12] M O M The total amount of calculated service fees for this batch Alpha [1] M O M [D]ebit transaction = Nordea Bank Norge ASA, org. nr Styrelsens säte Stockholm 5

6 14 Total Fee Settle 15 Fee Settle Period Numeric [12] O M O Fee settlement Numeric [6] O M O The period for the fee settlement, YYYYMM, only filled when it concerns a settlement MTR - Line Item Format Every line corresponds with exactly one settled transaction. There will be three different line item record types; DTL normal purchase, including returns and reversals REJ rejected DTL items ADJ adjustments items Adjustments are grouped and always have an own batch header. REJ and DTL can share a batch header and the sequence of the record type is depending on the retrieval reference no (txreference_1: field 2) MTR formats for DTL/REJ/ADJ The record consists of one line, which includes the following values: # Any line starting with hash sign denotes a comment # Under format the number between the brackets represent the maximum length # Optional/mandatory states if a field must be present or not # recordtype,txreference_1,txreference_2,txreference_3,settlement, # signsettlement,settlementcurrency,orig,origcurrency,pan, # txdate,txtime,authapprovalcode,txtype,txcardaccept,adjtext,fee, # signfee # Example:DTL,reference_1,reference_2,,123400,D,SEK,,,,523456******1234, # , ,101112,123456,PURCHASE,VISA,,200,C # ADJ,,,,22,D,EUR,22,D,EUR,,, ,123456,,ADJUSTMENT,,Round,0,D The table below shows the meaning of the following values: # Name Format * Optional= O Mandatory=M Description and Example DTL REJ ADJ 1 Record Type Alpha [3] M M M The constant string DTL/REJ/ADJ 2 Tx Reference_1 Alpha [14] M O O The unique transaction reference that was initially passed during the authorization or capture phase. Retrieval reference no, mandatory in all transactions (I037) Nordea Bank Norge ASA, org. nr Styrelsens säte Stockholm 6

7 3 Tx Reference_2 4 Tx Reference_3 5 SettlementA mount 6 Sign SettlementA mount Alpha [35] O O O The unique transaction reference that was initially passed during the authorization or capture phase. Special reference defined by the merchant. Alpha [23] O O O Additional transaction reference. Numeric [12] M M M The total amount settled, with two digits in the fractional part but no decimal point (I004) Value = zero for record type REJ Alpha [1] M M M [D]ebit transaction = Alpha [3] M M M The settlement currency in ISO 4217, all caps. 7 Settlement Currency 8 Orig Numeric [12] O O O Conditional, if rejects present options, The original transaction amount (I004) 9 Sign Orig 10 Orig Currency Alpha [1] O O O [D]ebit transaction = Alpha [3] O O O Conditional, if field 8 present. The original currency in ISO 4217, all cap 11 PAN Alpha [19] M O O Card number adjusted according to PCI (I002), masked 12 Terminal ID Alpha [8] O O O Card acceptor terminal identification 13 Tx Date YYYYMMDD M O O The authorization date of the transaction. (I012) 14 Tx Time HHMMSS M O O The authorization time of 15 Auth Approval Code the transaction. (I012) Alpha [6] O O O The authorization approval code (I038) 16 Tx Type Alpha [12] M O M The transaction status type. PURCHASE PURCHASE REV REFUND Nordea Bank Norge ASA, org. nr Styrelsens säte Stockholm 7

8 17 Tx Card Accept REFUND REV ADJUSTMENT Alpha [15] M O O Mastercard Visa Finax Swedbank Handelsbanken Nordea SEB Resurskortet Everyday card Lounaskortti Virikekortti Other* 18 Adj Text Alpha [35] O O M Adjustment reference information 19 Fee Numeric [12] M O O The total fee connected to this transaction. The fee is rounded and can therefor differ slightly from the 20 Sign Fee actual debited fee. Alpha [1] M O O [D] = Credit merchant account [C] = Debit merchant account *More details can be found in the statement in CSV-format MTR File trailer The file trailer consists of one line, which has the following values: # Any line starting with hash sign denotes a comment # Under format the number between the brackets represent the maximum # length # Optional/mandatory states if a field must be present or not Nordea Bank Norge ASA, org. nr Styrelsens säte Stockholm 8

9 # recordtype,mtrid,filereference,company,amountfile,numrecfile # Example: FTR, ,MTR-file-ref, MTR-company, , # Name Format * Optional= O Mandatory=M Description and Example 1 Record Type Alpha [3] M The constant string FTR 2 MTR id Alpha [12] M Organization number for 3 File Reference the receiver of this file Alpha [10] O File ID generated at file creation (use as reference for Nordea) 4 Company Alpha [30] M Company name, enclosed within doublequote characters 5 File Numeric [12] M Dummy amount, two 6 Num Rec File implicit decimals Numeric [12] M of records including header and trailer 5. FILE EXAMPLE FHD, , , TESTBUTIK , , BHF,88888,SEK,0,D,0,D,1,,,,0,D,249, BHM,88888,SEK,0,D,0,D,1, ,,,50000,D,0, BHD,88888,SEK,84,D,84,D,2, ,,,0,D,0, ADJ,,,,22,D,SEK,22,D,SEK,,, ,012345,,ADJUSTMENT,,Round,0,D ADJ,,,,62,D,SEK,62,D,SEK,,, ,054321,,ADJUSTMENT,,Round,0,D BHD,88888,SEK,412700,D,412700,D,2, , ,,0,D,0, DTL, ,888888,,35000,D,SEK,,,,543321******1157, , ,164212,983216,PURCHASE,MASTERCARD,,30,D DTL, ,999999,,377700,D,SEK,,,,543321******1511, , ,171057,295192,PURCHASE,MASTERCARD,,30,D BHD, ,SEK,364300,D,364800,D,3, , ,,3331,D,0, DTL, ,428428,,189300,D,SEK,,,,453321******3081, , ,124506,534681,PURCHASE,VISA,,70,D DTL, ,441880,,175000,D,SEK,,,,453321******3081, , ,124631,222595,PURCHASE,VISA,,70,D REJ, ,C008383,,0,D,SEK,500,D,SEK,554501******0480, , ,172000,607271,PURCHASE,,,, FTR, , , TESTBUTIK ,777584,14 Nordea Bank Norge ASA, org. nr Styrelsens säte Stockholm 9