Return File 4.3

1. Goals
2. Definitions
3. File Structure
4. Record format: - Record 0 – Header - Record 1 - Sale Details - Record 8 - Rejected Details - Record 10 - Credit Details - Record 2 – Adjustments - Record 100 – Anticipations Batch - Record 200 – Anticipated transactions - Record 9 – Trailer
5. Remark
   1. Limitations
   2. template for saving to database
6. Atachments
   1. Table I
   2. Table II
7. Version Changes

1. Goals

• The detailed return file generated on disk is intended to allow the custommer's back-end system to download the outstanding bills.

Target Audience: Any and all customers that need to save data to disk..

• The consolidated generated file is used to check the values ​​recorded in the map of store cash against the value recorded by SiTef, for payment transactions with credit, debit and benefit cards.

• The detailed return file has its origin in the electronic statement file, sent by the authorizers, organizing them in a single model. The return file also includes information on transactions that pass through SiTef, for records reconciled with those transactions.

2. Definitions

• The generation of the file is done through the "SiTefWeb Conciliation Reports" interface, requiring only the “Start Date”, “End Date” and version information.

• The files will be generated in CSV format, that is, the fields are separated by semicolon (";").

• Only the fields available according to each network are present.

• In case there is no content for the field, there will be a separator (“;”), making the number of fields of each “Fixed” record independent of the network.

• In the case of Non-TEF transactions, the NSU Sitef field will contain the Receipt Number.

• If the user selects the date type as "Sale Date", only the Record data Sale details (in addition to Header and Trailer) will be filled. This change has occurred so that the created file is immutable regardless of the present date.
  In the case of "Credit Date", the other fields will be filled, they are: Credit Details, Anticipation Batch, Advance Transactions and Adjustments, in addition to the Header and Trailer;

• The ordering, all ascending, of the records for the Sale Details field will be:

1. Sale Date
2. Idt Rede
3. Codlojasitef
4. TipoProduto
5. NSU SiTef
6. Installment Number

• The ordering, all ascending, of the records for the Credit Details field will be:

  1. Credit Date
  2. Idt Rede
  3. Codlojasitef
  4. TipoProduto
  5. NSU SiTef
  6. Installment Number

• The ordering, all ascending, of the records for the Adjustments field will be:

1. Adjustment Date
2. Idt Rede
3. Codlojasitef

-The ordering, all ascending, of the records for the Anticipation Batch field will be:

1. Anticipation Credit Date
2. Idt Rede
3. Codlojasitef
4. Summary number
5. Installment

-- The ordering, all ascending, of the records for the Anticipated Transactions field will be:

1. Sale Date
2. Idt Rede
3. Codlojasitef
4. TipoProduto
5. NSU SiTef

• The default filename format for saving to disk will be:

  • Detailed file: “Det<Nome_Rede><Data_Atual>.csv”

  • Where:

    • <Nome_Rede> Network Name, or “miscellaneous” when two or more authorizers are selected.
    • <Data_Atual> in the format YYMMDD.

The output to database requires the creation of a table for each type of Detail Record.

3. File Structure

Filter by Sale Date:

0 – Header
    1 – Sale Details*
    8 - Rejected Details
9 - Trailer

Filter by Credit Date:

0 – Header
    10 – Credit Details*
    .
    .
    2 – Adjustments
    .
    .
    100 – Anticipation Batch
    .
    .
    200 – Anticipated Transactions
    .
    .
9 – Trailer

* For transactions in installments, one (1) record of this type will be generated per installment.

4. Record format

*Record 0 – Header

Record 1 – Sale Details

* For NON-TEF transactions, this field is filled with the receipt Number information (V06).

** In the case of Redecard Debit, Goodcard and Tecban, this data is not available in electronic statements.

*** Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:

First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.

Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.

Record 8 – Rejected Details

* For NON-TEF transactions, this field is filled with the receipt Number information (C06).

** For Redecard Débito, this data is only filled in for reconciled transactions. In the case of Goodcard and Tecban, this data is not available in electronic statements.

*** Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:

First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.

Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.

Record 10 – Credit Details

* For NON-TEF transactions, this field is filled with the receipt Number information (C06).

** For Redecard Débito, this data is only filled in for reconciled transactions. In the case of Goodcard and Tecban, this data is not available in electronic statements.

*** Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:

First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.

Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.

Record 2 – Adjustments

*** Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:

First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.

Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.

Record 100 – Anticipation Batch

*** Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:

First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.

Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.

Record 200 – Anticipated Transactions

* For NON-TEF transactions, this field is filled with the information on the Receipt Number (TA06).

** In the case of Redecard Débito, Goodcard and Tecban, this data is not available in electronic statements.

*** Exclusive field for Cielo2, this field is equivalent to the Unique Identification Number of the Operations Summary
formatted as follows:

First Part - 15 fixed positions: identifies the summary while maintaining its history at Cielo.

Second Part - 07 variable positions: for use by Cielo. Identifies the changes made to the Operations Summary
.

ATTENTION!

As of 12/09/2013, the Anticipated Transactions record will be sent for each installment of the anticipated transaction, unlike its initial behavior, where only 1 record per transaction was sent, with 1 or more anticipated installments. In SiTefGW Conciliation, this submission model for each installment of the anticipated transaction is contained only in version 3.6.1 (exclusive to SiTefGW) and above; Version 3.6 and earlier of SiTefGW Reconciliation do not have the “Anticipated Installment” field, and continue to send only one Anticipated Transaction record per transaction.

Record 9 – Trailer

4. Remark

1. Limitations

• Due to limitations of the data sent by the administrators, the Amex, Visa and Redecard have projected installments.

2. Suggestion of process for downloading the title and respective keys

   • Use record 10 (normal settlement) and records 100 and 200 (anticipated settlement)
     for the write-off of bills;
   • In the Anticipations record, the relationship between each Batch(L) (Record 100) and its
     details(TA)(Registration 200), for possible result of a new Record(LTA), are
     respectively the fields:

   L02 = TA03 (Company Code)
   
   L03 = TA14 (CodLojaSiTef)
   
   L04 = TA05 (Summary Number)
   
   L07 = TA13 (Network identity code)
   
   L08 = TA25 (Installment)
   

• The relation of settlement records (10, 100 and 200) with sales (record 1)
  is:

V03 = C03 = LTA02(result of merging records 100 and 200) Company Code

V04 = C04 = LTA04(result of merging records 100 and 200) Sale Date

V07 = C07 = LTA07(result of merging records 100 and 200) SiTef's NSU

V13 = C15 = LTA08(result of merging records 100 and 200) Installment Number

V16 = C18 = LTA07(result of merging records 100 and 200)Network identity code

• The fields to be updated upon write-off are: Amount Paid and Credit Date, being represented in Record 10:

C11 Net Value

C13 Credit Date

• The fields to be updated upon write-off are: Amount Paid and Credit Date, being
  represented in Record 100 :

  L06 Value Paid in Advance
  
  L05 Anticipated Credit Date
  

  As it is a suggestion, we recommend the customer to validate whether these columns are sufficient.

6. Code Table

Code Table

7. Version Changes

• Verson 4.3 on 03/20/2018 – Responsible.: Dimitri Giordano
  • Inclusion of the Plan Type and By-Product fields in SiTefGW Conciliation records 1, 10 and 200.
  • Inclusion table III.
• Verson 4.2 on 06/28/2017 – Responsible.: Renato Silva
  • Inclusion of the RO Number field in SiTefGW Conciliation records 1 and 10.
• Verson V3.6.2 on 06/28/2017 – Responsible.: Renato Silva
  • Removing fields that setting
• Verson V3.6 on 06/07/2016 – Responsible.: Thiago Leite
  • Inclusion of the product type “T” = Debit with change.
• Verson V3.6 on 04/15/ 2016 – Responsible.: Adriano
  • Change in product description 0010, from table II from Visa Vale to Alelo.
• Verson V4.0 on 02/11/2016 – Responsible.: Thiago Leite
  • Version 4.0 was included, exclusive to SiTefGW Conciliação / SiTef Integradores, which maintains the same layout as V3.6 of SiTef Conciliação, but with all fields present without the need for previous configuration.
  • The “Authorization Code” field is now filled for Redecard Debito, on reconciled transactions only.
• Verson V3.6.1 on 11/26/ 2015 – Responsible.: Thiago Leite
  • Added note about version V3.6.1, exclusive to SiTefGW Conciliação / SiTef Integradores, in Registry 200.
• Verson V3.6 on 11/25/2015 – Responsible.: Adriano
  • Inclusion of the product type “F” = Flex Car.
  • Inclusion of “idt_net” codes
• Verson V3.6 on 08/19/2015 – Responsible.: Adriano
  • Inclusion of item 5.2: Suggestion of process for downloading the title and respective keys.
• Verson V3.6 on 05/18/2015 – Responsible.: Adriano
  • Inclusion of credit card banner cod 0023 - Avista.
• Verson V3.6 on 10/03/2014 – Responsible.: Sérgio
  • Inclusion of the Tax Data column in Record 10.
• Verson V3.6 on 10/01/2014 – Responsible.: Adriano
  • Inclusion of the Tax Data column in Record 1.
  • Inclusion of nsu_host_Sitef column in Records 1 and 10.
• Verson V3.6 on 05/24/2014 – Responsible.: Adriano
  • Inclusion of the banner code Table II - "0022" - Hyper Debit
• Verson V3.6 on 05/13/2014 – Responsible.: Adriano
  • Iinclusion of new banner codes Table II
• Verson V3.6 on 03/18/2014 – Responsible.: Sergio
  • Inclusion of the description of the means of capture field in Record 1
• Verson V3.6 on 02/21/2014 – Responsible.: Thiago Leite.
  -Included paragraph about the source of the return file in the Objective item.
  • Changed the description of the invoice field
• Verson V3.6 on 02/18/2014 – Responsible.: Artur.
  • inclusion of POS and Means of caputre fields in Record 200.
  • Inclusion of two credit card banners (0016, 0017) in Annex I - Table II
• Verson V3. 6 on 12/23/2013 – Responsible. : Jefferson.
  • Inclusion of a new column "accounting entry type" (configurable), in Registry 10.
• Verson V3.6 on 02/09/2013 – Responsible. : MKK.
  • Changed behavior of record 200 (Advanced Transactions)
• Verson V3.6 on 11/26/2013 – Responsible. : MKK.
  • Added SisCred, Sorocred, CredSystem and CUP products to the Rede authorizer
• Version V3. 6 on 25/04/201 3 - Responsible. : Adriano.
  • Inclusion of new Time Sale column (configurable).
  • The bank fields: Bank Code, Branch and Account, now have their configurable sizes with zeros on the left.
• Verson V3.6 on 03/28/2013 – Responsible. : Adriano.
  • Inclusion of new POS column (configurable).
  • Added field “Indicates Recovery File” in registers 1, 10 and 200.
• Verson V3.5 on 11/09/2012 – Responsible. : Adriano.
• Inclusão do código de banner: 0010 - Visa Vale.
• Verson V3.5 on 09/13/2012 – Responsible. : Junior.
  • Modification of the column "Summary Number" field modified from 10 to 15
    positions.
• Verson V3.4 on 07/08/2012 – Responsible. : Adriano.
  • Inclusion of the column "Unique RO Number" field with 22 unique positions for use
    of Cielo2. Payment record identification.
• Verson V3.2 on 05/24/2012 – Responsible. : Adriano.
  • Inclusion of the "Gross Value" column in record 100
• Verson V3.1 on 5/16/2012 – Responsible. : Adriano.
  • Inclusion of comment in Record 10 column C11 - Net Value
  • Inclusion of new network codes
• Verson V3.1 on 12/08/2011 – Responsible. : MKK.
  • Inclusion of Advance Batch and Advance Transaction records
• Verson V3.0 on 09/27/2011 – Responsible. : Adriano.
  • Inclusion of sitef sales date and sitef sales time columns in records 1 and 10
• Verson V3.0 on 05/27/2011 – Responsible. : Adriano.
  • Correction in the maximum sizes of fields V07 Record 1 and C07 Record 10 from 9 to 12 characters
• Verson V3.0 on 03/10/2011 – Responsible. : Adriano.
  • Inclusion of new column: Flag Code, in Type 1 and 10 Records
• Verson V2.0 on 03/04/2011 – Responsible. : Adriano.
  • Inclusion of new Network codes
• Verson V2.0 on 04/09/2010 – Responsible. : Adriano.
  • Inclusion of Capture =5 as Non-TEF
• Verson V2.0 on 01/27/2010 – Responsible. : Adriano.
  • Inclusion of the comment in columns V07 and C
• Verson V2.0 on 01/01/2009 – Responsible. : MKK.
  • Inclusion of product type = "S"(Withdrawal)
• Verson V2.0 on 01/21/2009 – Responsible. : MKK.
  • Creation of the Credit Date and Sale Date record
  • Deletion of the Negative Values ​​record
  • Inclusion of product type withdraw (‘S’) para Redecard e Visanet
• Verson V1.9 on 11/06/2008 – Responsible. : MKK. ( return file version: 1.6.3 - 06/11/2008)
  • Mmodification in the form Redecard Installments
• Verson V1.8 on 11/06/2008 – Responsible. : Adriano. ( return file version:1.6.1-06/11/2008)
  • Inclusion of the Invoice Code
• Verson V1.7 on 10/09/2008 – Responsible. : MKK.
  • Inclusion do Código de Autorização
• Verson V1.6 on 01/31/2008 – Responsible. : Adriano Galati.
  • Changing the Network Identifier Code column with new codes
• Verson V1.5 on 04/20/2007 – Responsible. : Adriano Galati.
  • Product type inclusion “V” - voucher
  • Inclusion of catches “2”, “3” – TEF and “4” Non-TEF on 08/06/2007 – Adriano
  • Changing the delimiter to “;” (RMISERVER v. 1.5.3 11/06/2007)
• Verson V1.4 on 08/01/2006 – Responsible. : Adriano Galati.
  • Inclusion of column identRede no Header;
  • Inclusion a new record type 3 – Negative sales;
  • Inclusion of Bank, bank branch, Checking Account Number , Codlojasitef columns in the Detailing and Adjustments;
• Verson V1.3 on 07/05/2005 – Responsible. : Adriano Galati.
• Verson V1.2 on 05/04/2004 – Responsible. : Marcus Adolfo Lucio
• Verson para V1.1;
  • Inclusion of record type '2' - Adjustment record;
• Verson V1 on 05/01/2003 - Responsible: Alexandro Alves Moreira