Financial Extract in OFX
A file of type OFX is known as Open Financial Exchange. Inside an OFX file are contained all the movements made in a certain period, being possible that you integrate this file to different management systems.
Gerencianet allows you to export your financial statement in OFX format, which can help you in the bank reconciliation of your financial.
How to export extract in OFX file on Gerencianet
Log in to your Gestornet account and click on the menu
Meu Dinheiro > Extrato Financeiro
;Now, in the upper right corner, click
Exportar Extrato Financeiro
ans select the format typeOFX
, as shown in the image:
- An export confirmation message will be returned in a modal, containing the summary of the parameters/filters considered, as shown in the image below:
Example of OFX file with its particularities and layout
- Modelo
Much of the file will be as shown in the example, only the tags listed below will be modified.
OFX > SIGNONMSGSRSV1 > SONRS
Tag | Description |
---|---|
DTSERVER | File generation date in format yyyymmddhhmmss[-3:BRT] . |
OFX > BANKMSGSRSV1 > STMTTRNRS > STMTRS > BANKACCTFROM
Tag | Description |
---|---|
ACCTID | Gerencianet's account numer. |
OFX > BANKMSGSRSV1 > STMTTRNRS > STMTRS > BANKTRANLIST
Tag | Description |
---|---|
DTSTART | Date of the first movement record in the format yyyymmdd120000[-3:BRT] . |
DTEND | Date of the last movement record in the format yyyymmdd120000[-3:BRT] . |
OFX > BANKMSGSRSV1 > STMTTRNRS > STMTRS > BANKTRANLIST > STMTTRN
The STMTTRN
tag and its sub-tags will be repeated for each transaction returned by the Kernel.
Tag | Description |
---|---|
TRNTYPE | Accept the values CREDIT or DEBIT . |
DTPOSTED | Transaction posting date. That is, the date of availability of the amount in the current account. Format: yyyymmdd120000[-3:BRT] . |
TRNAMT | Transaction value to two decimal places for cents (separated by dot). If the transaction is a debit, there will be a negative sign in the amount. Exemples:
|
FITID | Unique transaction code with 34 characters, arranged as follows:
|
CHECKNUM | Transaction protocol with 15 characters. Example:
|
REFNUM | Transaction reference code. It must always contain 22 characters, being like that: 7 characters to the transaction code 15 characters to the transaction number (charge_id or charge's number) This field will be displayed in the OFX file only for transactions associated with a Boleto or Credit Card payment confirmation. |
MEMO | Cherge description. |
OFX > BANKMSGSRSV1 > STMTTRNRS > STMTRS > BANKTRANLIST > LEDGERBAL
Tag | Description |
---|---|
BALAMT | Represents the partial account balance at the time of the most recent transaction. Examples: 1050.32 ,-223.95 |
DTASOF | Posting date of the most recent transaction in the format. Format: yyyymmdd120000[-3:BRT]. |
Table listing all possible Tag Transaction Codes FITID
Transaction code | Description |
---|---|
2002001 | Receipt of boleto and parcel |
1001002 | Credit card intermediation fee |
2001002 | Credit card intermediation chargeback |
2002002 | Credit card billing receipts |
1002002 | credit card return |
1001001 | Boleto and parcel intermediation fee |
2009001 | intermediation bonus |
1013001 | Boleto's Refund - Debit of the return |
2013001 | Boleto's Refund - credit of the return |
2002046 | Transfer payment marketplace boleto |
1001046 | Ticket marketplace transfer fee |
1002046 | Refund of marketplace transfer boleto |
2002047 | Transfer payment marketplace card |
1001047 | Marketplace card transfer fee |
1002047 | Refund of card marketplace transfer |
1003004 | Payment via barcode |
1001004 | Payment via barcode fee |
2002017 | Payment via barcode refund - Refund made from the bank or analysis |
1002025 | Refund payment via barcode - Credit to signal insufficient balance (scheduling) |
2002026 | Payment via barcode - Debit to signal insufficient balance (schedule) |
1002003 | Transfer - TED type transfer; or between Gerencianet accounts; or by email |
1001003 | Transfer fee |
2002016 | Transfer chargeback - Bank chargeback or analysis |
2002045 | Transfer chargeback - credit of the transfer fee canceled by the customer |
2004003 | Transfer chargeback - credit of the transfer fee canceled by the customer |
2002003 | Transfer between Gerencianet accounts - Credit of the Gerencianet transfer from the target account |
1003021 | Cellular charge |
2004021 | Cellular charge chargeback |
2002044 | Payment approved card, carnê and parcel |
1002044 | Payment sent card, carnê and parcel |
2002013 | manual credit |
1002013 | manual debit |
1001048 | Inactivity fee |
1001014 | deposit fee |
Notification queue status (callback)
Gerencianet notifies the integrated systems of each change in the status of a given charge through its associated notification URL.
Notifications are processed and always sent through a submission queue. It is also worth remembering that, if the callback is rejected by the destination system, it automatically returns to the queue and is rescheduled for a new delivery attempt. Callbacks are dynamic and can occur throughout the day.
Thinking about offering new ways of consulting the processing of this queue, Gerencianet provides a screen that allows consulting the consumption status of the notifications queue (callbacks) processed until then. In this way, if the customer is in doubt as to whether a callback has already been sent or not, he can follow the daily processing of this queue.
To see the status and processing of the queue, see the link status das confirmações de pagamentos - Gerencianet.