Skip to main content
F360 is a financial management platform that provides tools for accounting, invoicing, bank reconciliation, cash flow management, and integration with banks and accountants. It offers APIs for extracting data on bank accounts, transactions, invoices, people (clients and suppliers), cost centers, chart of accounts, and more.

Configuring F360 as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the F360 option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

You’ll need to provide your F360 API credentials to authorize Nekt to access your financial data. The following configurations are available:
  • Token Login: The API token for F360. Obtain this from the F360 platform when creating a public API webservice. The JWT token will be obtained automatically via login.
  • Start Date: (Required for some streams) The earliest date from which records will be synced (YYYY-MM-DD). Required by notas, parcelas_titulos, parcelas_titulos_despesa, parcelas_titulos_receita, parcelas_titulos_despesa_aberto, parcelas_titulos_receita_aberto, parcelas_cartoes, and extrato_bancario streams.
Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Below you’ll find all available data streams from F360 and their corresponding fields:
Stream for Chart of Accounts (Plano de Contas). Contains the accounting structure used for classifying revenues and expenses.Key Fields:
Stream for Cost Centers (Centros de Custo). Used for allocating expenses and revenues by department or project.Key Fields:
Stream for Product Classifications. Maps NCM and CFOP codes to chart of accounts entries.Key Fields:
Stream for Bank Accounts. Contains all bank accounts configured in F360. This stream is the parent of Extrato Bancário.Key Fields:
Stream for Bank Statement (Extrato Bancário). Child of Contas Bancárias - contains transaction-level data for each bank account. Uses the synthetic model (modelo Sintético).Key Fields:
Stream for People (Clients and Suppliers). Contains contact and company information for customers and vendors.Key Fields:
Stream for Invoices (Notas Fiscais). Contains NFe, NFSe, and Nota de Débito documents. Incremental by emission date.Key Fields:
Stream for Title Installments (Parcelas de Títulos). Contains installments of receivables and payables. Incremental by DataDeAtualizacao.Key Fields:
Stream for Expense Title Installments (Parcelas de Títulos - Despesa). Contains installments of payables specifically. Incremental by DataDeAtualizacao.Key Fields:
Stream for Revenue Title Installments (Parcelas de Títulos - Receita). Contains installments of receivables specifically. Incremental by DataDeAtualizacao.Key Fields:
Stream for Open/Unpaid Expense Title Installments (Parcelas de Títulos - Despesa em Aberto). Contains pending installments of payables specifically, filtered by due date (Vencimento). This stream fetches installments with due dates up to 2 years in the future.Key Fields:
Stream for Open/Unpaid Revenue Title Installments (Parcelas de Títulos - Receita em Aberto). Contains pending installments of receivables specifically, filtered by due date (Vencimento). This stream fetches installments with due dates up to 2 years in the future.Key Fields:
Stream for Card Installments (Parcelas de Cartões). Contains credit/debit card transaction installments. Incremental by DataDeAtualizacao.Key Fields:

Data Model

The following diagram illustrates the relationships between the core data streams in F360. The arrows indicate the parent-child and join relationships.

Use Cases for Data Analysis

This guide outlines valuable business intelligence use cases when consolidating F360 data, along with ready-to-use SQL queries that you can run on Explorer.

1. Bank Reconciliation Overview

Track bank account balances and reconcile transactions with titles and card installments. Business Value:
  • Identify unreconciled transactions
  • Monitor cash flow by account
  • Verify bank statement accuracy

2. Revenue and Expense Summary by Type

Analyze financial performance by transaction type (Receita vs Despesa) from titles and card installments. Business Value:
  • Understand revenue vs expense breakdown
  • Track cash flow by transaction type
  • Support budget vs. actual analysis

Implementation Notes

Data Quality Considerations

  • The Extrato Bancário stream automatically deduplicates records; the API may return the same transaction across pagination boundaries.
  • Start Date is required for streams that use date windows: notas, parcelas_titulos, parcelas_titulos_despesa, parcelas_titulos_receita, parcelas_titulos_despesa_aberto, parcelas_titulos_receita_aberto, parcelas_cartoes, and extrato_bancario.
  • The open installment streams (Parcelas de Títulos - Despesa em Aberto and Parcelas de Títulos - Receita em Aberto) fetch data up to 2 years in the future to capture upcoming receivables and payables.
  • Extrato Bancário is a child stream of Contas Bancárias; it fetches transaction data per bank account.

API Limits & Performance

  • For faster extractions, select only the streams necessary for your analysis.
  • Streams with incremental sync or date-based fetching (notas, parcelas_titulos, parcelas_titulos_despesa, parcelas_titulos_receita, parcelas_titulos_despesa_aberto, parcelas_titulos_receita_aberto, parcelas_cartoes) use start_date to filter data.
  • The extrato_bancario stream uses 30-day date windows for efficient API requests.

Skills for agents

Download F360 skills file

F360 connector documentation as plain markdown, for use in AI agent contexts.