Reporting and reconciliation
Get the data you need to complete your accounting and reconciliation workflows.
Fintoc's reports help you understand and reconcile the activity in your account. You can view and download these reports directly from the Dashboard or schedule reports to be sent automatically.
Select a report
When using Fintoc's Payment Initiation API, Fintoc has two reports that provide information about your transactions. Start with the task you’re looking to perform and use the table below to identify the best report.
| Task | Suggested Report |
|---|---|
| - Break down the individual transactions included in each payout to your bank account | Payout reconciliation |
| - Download daily transaction history - View daily transaction totals | Daily transaction |
Payout reconciliation report
The payout reconciliation report is only available when Fintoc collects payments.
The payout reconciliation report
The Payout reconciliation report shows which transaction is included in a specific payout. This report helps you reconcile each payout you received in your bank account against the transactions included in that batch.
By default, every time Fintoc makes a payout to your bank account an email is sent to you with the payout reconciliation report for that batch. To see other available delivery channels see automatic report delivery.
Structure
The payout reconciliation report is a semicolon-delimited CSV file in which the first row is column headers. The filename is yyyy-mm-dd-fintoc-payout-<orgname>.csv. For example, if your orgname is "My Company" the filename will be yyyy-mm-dd-fintoc-payout-mycompany.csv.
The file contains the following columns:
| # | Column | Type | Description |
|---|---|---|---|
| 1 | id | string | Unique identifier for the transaction. It is case-sensitive. |
| 2 | created_at | string | The transaction's creation date, in ISO 8601 format. |
| 3 | amount | integer | Gross amount of the transaction, in cents. In the case of refunds, this value will be displayed as negative unless a refund fails, in which case it will be shown as positive. |
| 4 | fee | integer | Fees (in cents) paid for this transaction. If your account is configured to receive the payout full amount, then the fee is always 0. |
| 5 | net_amount | integer | Net amount of the transaction, in cents. |
| 6 | currency | string | Transaction currency ISO code |
| 7 | payout_holder_id | string | Identifier of the owner of the bank account the payout was sent to. In Chile, it is a RUT and in Mexico it is an RFC. |
| 8 | payout_recipient_account | string | The account number the payout was sent to. |
| 9 | payout_recipient_bank | string | The bank the payout was sent to. |
| 10 | resource_type | string | Whether the transaction is a payment_intent, a charge or a refund. |
| 11 | metadata | string | A JSON string of the transaction metadata. |
Sample
For an example of the included data and structure, download a sample of the payout reconciliation report.
Daily Transaction report
Delivery schedules
The daily transaction report can be scheduled for delivery on two schemes: banking cut-off time and chronological day cut-off time. Configured schedules have two effects:
- They change the day and hour that reports are delivered.
- They change the time window of data that each file contains.
| Delivery schedule | Available country | Description |
|---|---|---|
| chronological day | Chile Mexico | The report will be delivered every day without exception. The file will contain data from a single day from 00:00 to 23:59. Files will be delivered between 00:20 and 01:20. |
| banking day | Chile | The report will be delivered according to Chile's banking cut-off time, which is business days at 14:00. Therefore, data for a specific day will be between 14:00 and 13:59 of the next business day. Files will be delivered on business days between 14:20 and 15:20. For example, holidays aside, a report received on a Wednesday will contain data from Tuesday at 14:00 until Wednesday at 13:59. Another example is that a report received on Monday will contain data from the previous Friday at 14:00 until Monday at 13:59. If that Friday happens to be a holiday, the data window will be even larger (it would start on Thursday at 14:00). |
Structure
The daily transaction report is a semicolon-delimited CSV file in which the first row is column headers. The filename is yyyy-mm-dd-daily-summary-fintoc-<orgname>.csv. For example, if your orgname is "My Company" the filename will be yyyy-mm-dd-daily-summary-fintoc-mycompany.csv.
The file contains the following columns:
| # | Column | Type | Description |
|---|---|---|---|
| 1 | created_at | string | The Payment Intent's creation date, in ISO 8601 format. |
| 2 | payment_id | string | Unique identifier for the payment. It is case-sensitive. |
| 3 | id_given_by_sender_institution | string | Operation number from the bank of the sender account. |
| 4 | updated_at | string | The Payment Intent update date, in ISO 8601 format. |
| 5 | amount | integer | Amount of the payment, in cents. |
| 6 | currency | string | The payment currency ISO code |
| 6 | sender_institution_id | string | The bank that initiated the payment. |
| 7 | sender_institution_cmf_code | string | The CMF code of the bank that initiated the payment. In Mexico is empty. |
| 8 | sender_account_number | string | The account number that initiated the payment. |
| 9 | sender_account_type | string | The sender account type. |
| 10 | sender_holder_id | string | Identifier of the owner of the bank account that initiated the payment. In Chile, it is a RUT and in Mexico it is an RFC. |
| 11 | sender_name | string | The name of the owner of the bank account that initiated the payment. It can be empty. |
| 12 | recipient_holder_id | string | Identifier of the owner of the bank account that received the payment. In Chile, it is a RUT and in Mexico it is an RFC. |
| 13 | recipient_account_number | string | The account number that received the payment. |
| 14 | recipient_institution_id | string | The bank that received the payment. |
| 15 | organization_name | string | Your organization name in Fintoc's system. |
| 16 | metadata | string | A JSON string of the transaction metadata. |
Sample
For an example of the included data, download a sample of the daily transaction report.
Available delivery channels
Instead of manually downloading files from the Dashboard, reports can be scheduled for automatic delivery via different channels. If configured, reports will be delivered periodically so that each file contains data for a specific time interval.
Email
Files can be automatically delivered to an email of your choice. The subject of the sent emails is also configurable. For instance, it is common to include the date of a given report on the subject for easier identification.
For email and subject configuration, please contact our sales team.
SFTP
The recommended way of receiving the reports is via Fintoc's SFTP. This allows to automate the extraction of files easily and securely.
Connecting to the SFTP server
Use the following information to connect to Fintoc's SFTP server:
- Host:
sftp.fintoc.com - Port:
80 - Username: your organization's ID. It starts with
org_ - Password: the password provided by your Account Executive.
For access credentials, please get in touch with our sales team.
Reports path
Fintoc uploads each report in the following paths:
| Report | File path |
|---|---|
| Payout reconciliation | OUT/payout/<mode>/yyyy-mm-dd-fintoc-payout-<orgname>.csv |
| Daily transaction | OUT/daily_summary/<mode>/yyyy-mm-dd-daily-summary-fintoc-<orgname>.csv |
Where <mode> can be either live or test.
Updated about 2 months ago