PhinAppbeta
Imports

Bank statements

Supported banks and formats, how to import, and what PhinApp does with every file.

Supported banks

BankOFXPDFCSVExcel (.xls / .xlsx)Notes
Itaú✓✓-✓Account statement and card bill, for business and personal accounts (Itaú, Uniclass, Personnalité) - the app's PDF and online banking's are one format. Export the detailed statement in Excel: it carries the name and the CPF/CNPJ of every payment. A statement with supplier payments grouped together (SISPAG FORNECEDORES) is refused - see Grouped payments.
Santander✓✓✓✓Two PDFs - the monthly statement (Extrato Consolidado) and the account statement (extrato de conta) - and two spreadsheets - business banking's and the account statement's. The account statement's PDF, CSV and spreadsheet count as one format.
Bradesco-✓✓-Account statement and card bill - including the cards Bradesco issues under other brands, such as Amazon's. The open bill from the Bradesco Cartões app too - see Bradesco's open bill.
Nubank✓✓✓-Account and credit card - for the card, its bill's CSV as well. Neither CSV says which account it is - see Files that do not name the account.
C6 Bank✓✓--C6's OFX carries no balance: on the first import, PhinApp asks for the balance of the day before the statement starts. The PDF states each day's balance.
Inter✓✓✓-
Mercado Pago-✓--Account and credit card. The bill is one account, even when it lists more than one card (the physical one and the virtual ones).
PicPay-✓✓-Account and credit card. Payments made with the card are not part of the account's statement - see What is not a movement.
XP and Rico✓✓--
RecargaPay-✓--Wallet and credit card. The CDI yield (Rendimento CDI) is not imported - see What is not a movement.
Nomad-✓--Dollar account. The report in English and the one in Portuguese count as one format. Only completed transactions are imported - see What is not a movement - and the report's balance counts when the period runs to the day it is generated, which is the app's default.
Wise--✓✓Multi-currency account: send the statement's .zip as it came, and each currency becomes an account. Also as QIF, exported in English. See Wise: one account per currency.

Is your bank not on the list?

Other banks that export standard OFX usually work with nothing to set up - it is worth a try. A PDF, CSV or spreadsheet from a bank that is not in the table is refused rather than half read - the message says the file is not supported yet and gives the address to send a sample to. Adding a new bank is quick.

E-mail

Discord community

discord.gg/XRFVcuM5JF

How to import

Export the statement from your bank

In your online banking or your bank's app, open the account statement (or the card bill), choose the period and save it as OFX, PDF, CSV, QIF or Excel - whichever your bank offers from the table above. Periods that overlap earlier imports are not a problem. Always use the same format for each account (why).

Send it to PhinApp

Under Account Management → Banking Transactions, click Import statement and drop the file (.ofx, .pdf, .csv, .qif, .xls, .xlsx or Wise's .zip) - or click to choose it. You can also drop the file straight onto the list of transactions: the import opens already reading it. One file may carry more than one account - Wise's .zip carries one per currency.

Check the result

For each account in the file, PhinApp shows how many transactions were imported, how many were already there, how many new partners were registered, how many were replaced by a format switch and how many were left out for being on days the account takes in another format (if any), the balance adjustment written at your request (if any), and the account balance now - the figure to check against your banking app. Below the accounts, it says how many transactions were reconciled automatically - for the whole file, since reconciliation runs once every account is in - and the balance discrepancies of the file's accounts, if any.

On Windows, close the spreadsheet in Excel before importing it: while it is open, Excel locks the file and the browser cannot read it.

Large files

A file can hold up to 25 MB and 50,000 entries. Past that it is refused before a single entry is written: split the period into smaller parts - each part imports as the whole would, and overlapping periods duplicate nothing.

A large import - years of an account's history, tens of thousands of entries - can take a few minutes. The dialog says the import is still running and waits for it; if you close it, the import carries on on the server and the entries appear in the list when it is done.

What happens on every import

The right account, no duplicates

The account is recognized by the bank code, the branch and the account number - and by the same number written another way: the OFX, the PDF and the CSV of one account land on that one account, even when one writes 12345678-9 and another 123456789 - and the account then takes only one of those formats (see below). If it does not exist yet, it is created - as a connected account.

Importing the same file again, or a period that overlaps another, duplicates nothing: what was already imported is recognized and reported as "already there", and only what is new comes in. So there is no need to keep track of which days were imported - when in doubt, import again.

One format per account

An imported entry is recognized by the identifier the file gives it, and each format identifies its entries in its own way: the OFX carries the bank's identifier, and the PDF and the spreadsheet often carry none. Comparing what the entries say cannot do it safely: two R$ 8.50 coffees on consecutive days are identical to a single coffee each format dated on a different day - and a wrong balance is worse than a warning.

So each day of an account belongs to one format. The account starts in the format of the first file imported, shown beside it in the account list (for instance, Statement · OFX). A file in another format brings only the days no format has - those before the account's first day (older statements) -, and for the days after, PhinApp offers to switch the account's format. The days the account already takes in another format stay as they are, and the result says how many of the file's transactions were left out for that.

Some banks give each entry the same identifier in more than one format, and those formats count as one - you can alternate between them freely:

BankFormats that count as one
InterOFX, PDF and CSV
Nubank (account)OFX and CSV
BradescoPDF and CSV
PicPayPDF and CSV
SantanderThe account statement's PDF, CSV and Excel
WiseQIF, CSV and Excel

At Santander, the consolidated statement and the account statement are two formats, although both are PDFs - each names the entries its own way - and so are business banking's spreadsheet and the account statement's. An account that was fed by the consolidated statement and starts receiving the account statement goes through a format switch like any other.

For credit cards, the PDF bill and the OFX are always different formats - and at Bradesco, so are the open bill and the monthly one.

Bradesco's open bill

The Bradesco Cartões app exports the bill still open as a PDF (Situação do Extrato: EM ABERTO). It does not say when the period opened or when it closes - only the day it was exported - so PhinApp places it on the card's calendar: the period starts on the last closing day before the export, and an entry dated before it (posted late) goes on the period's first day, as on a closed bill. For a new card, PhinApp first asks for the closing day and the due day.

The open bill words every purchase differently from the monthly bill - the merchant's name is cut short - so the two are different formats. When you import the closed bill after the open one, PhinApp asks to switch the format from the period's first day: the open bill's entries go and the closed bill's, which is the final word, take their place. An open bill exported on the closing day that still only shows the previous period is refused: import that period's closed bill instead.

Switching formats

When your bank stops offering the format you use - or you prefer another one - import the new file as usual. Before importing anything, PhinApp asks from which day the new file applies: the entries up to the day before stay as they are, and from that day on only files in the new format come in. No day ends up with entries from both. The old format's entries from that day on leave the account and are replaced by the new file's - the dialog says how many before you confirm, and the result shows how many were replaced. The days before the switch stay the old format's, older statements you import later included. On a card, the future instalments of purchases in instalments are raised again from the new format.

The days offered run from the new file's first day - chosen for you when possible: the new file then applies to everything it covers - to the day after the account's last entry. Beside each day, PhinApp says whether the account's balance and the new file's balance agree at the end of the day before. When they do, switching on that day is exact: no entry comes in twice or is left out, even when each format dates an entry on a different day.

When they do not, it is almost always an entry each format dates on a different day, right next to the switch - for instance, a purchase posted late, which the PDF bill puts on the bill's first day and the OFX on the day it was made. The dialog then shows, side by side, the account's entries in the week before the switch and the new file's in the week from it, with those of the same amount highlighted. Tick the account's entries the new file also has: they are removed, the new file's stay, and the difference is recalculated at once.

If a difference remains that no entry explains - a few cents of rounding between one format and another, as can happen between a card's OFX and its PDF bill -, choose between:

  • writing an adjustment: an entry for the difference, on the day before the switch, so the balances agree. It comes in unclassified, for you to classify as you see fit, and later imports in either format take it into account;
  • leaving the difference: the account then shows the balance discrepancy on that day.

If the file states no balance and there is nothing to check, you have to confirm you want to go ahead anyway.

A day that would remove an entry already reconciled cannot be chosen - undo the reconciliation or pick a day after it. A switch is offered only by a file that reaches the account's last day; one that ends before it brings only its own format's days. And when the new file also has days that are already its format's - a statement in the format the account used before, for instance -, you can answer don't switch: only those days come in, and the account stays as it is.

Older statements

An older statement can be imported at any time, in any format the account has taken: it brings that format's days and leaves the others as they are. After switching from OFX to PDF, for instance, an old OFX fills in the days that are still the OFX's, and an old PDF those that are already the PDF's.

The days before the account's first day belong to no format yet, and come in in the file's format, whatever it is. If it is another format, PhinApp checks the file's balance against the account's opening balance at the end of the day before its first. When they agree, the days come in without a question. When they do not, the dialog shows the file's entries in the last week before the account beside the account's in its first week: tick the file's entries the account already has - they do not come in, and the account's stays -, and settle whatever remains with an adjustment or by leaving the difference, as in a switch. Nothing leaves the account.

The account's currency

The currency comes from the file itself: an OFX declares it, and PDF, CSV and Excel files print it - R$ beside the amounts, or as the unit of a column (Valor (R$)) or of the whole statement (Valores em R$). PhinApp asks only when the file shows no currency anywhere - Inter's and Nubank's CSV exports, and Santander's account statement in CSV and Excel, carry bare numbers - and the import is about to create an account; the organization's main currency is already chosen, and the question is there because an account's currency never changes afterwards. For an account that already exists, its own currency applies. A file in a currency different from the account's is refused for that account, and the result names both: an amount in dollars does not go into a real account. A card bill is in the currency of its total: a purchase made abroad, printed in its own currency beside what it cost in reais, does not change that. At Wise, the CSV and the spreadsheet state the currency on every transaction, and the QIF, which does not, comes inside the .zip in a file with the currency in its name (see below).

Password-protected files

Several banks lock their PDFs with a password - usually the first digits of the holder's CPF or CNPJ. PhinApp first tries the digits of your company's CNPJ; if none of them opens the file, it asks for the password. It is used only to open the file there and then, and is not kept.

Files that do not name the account

Some CSVs - Nubank's account export and PicPay's - carry the transactions and nothing else: neither the account nor a balance. PhinApp recognizes the account by the transactions it already holds (Nubank's CSV carries the same identifiers as its OFX); when it cannot, it asks which account the file is for. The same happens with the PDF bill of a card you already set up from its OFX: the choice is remembered, and the next bills land on the same card without asking. Since a card's PDF and OFX identify purchases differently, PhinApp then offers to switch the card's format.

Nubank's card bill CSV does not even say which card it is. PhinApp asks, on every file, which of your Nubank cards it belongs to - or opens a new one, asking its name, its closing and due days, and the balance on the day before the bill starts. A bill's CSV and its PDF word the payment differently and can disagree about an IOF by a cent, so they are two formats of the card: to move from one to the other, PhinApp offers to switch the format.

Wise: one account per currency

At Wise, the account holds a balance in each currency, and the statement is a .zip with one file for each, in the format chosen for the export: QIF, CSV or Excel. Send the .zip as it came. Each currency becomes an account in PhinApp, in its own currency and under the number Wise gives that balance; currencies with no transactions in the period are left out.

The number, the currency and the period come from the name Wise gives each file inside the .zip - for example statement_12345678_USD_2026-07-01_2026-09-30.qif - because a QIF carries none of the three. A file taken out of the .zip and renamed is still imported, but PhinApp asks which account it is for and, for a new account, in which currency.

  • QIF in English only. Wise writes the file in the language chosen for the export, and a QIF date does not say whether the day or the month comes first: 07/04/2026 is 4 July in English and 7 April in Portuguese. So PhinApp reads a QIF in English and refuses one in any other language, saying to export it again. The CSV's column headings are in English whatever the language; only the descriptions follow it.
  • The balance. The CSV and the spreadsheet carry the balance after each transaction, and PhinApp uses it as it does any statement's. The QIF carries no balance at all: on the first import of each currency, PhinApp asks for the previous balance.
  • One format. The QIF, the CSV and the Excel file name every transaction with the same Wise number, so you can switch between them freely. A conversion between two currencies shows on both accounts: money out of one, into the other.

Each day's balance

PhinApp uses the balance the file itself states - in OFX, the statement's balance; in Itaú's spreadsheet, the SALDO TOTAL DISPONÍVEL DIA; in Santander's, the Saldo column; in a PDF, each day's balance, the period's or the balance column, depending on the bank - to settle the balance of every day the file covers that has already ended. Today stays open, because it may still have movements.

At Itaú, the OFX balance includes yield on the automatic investment that has not been paid as a transaction yet - usually a few cents. Since the OFX does not say how much, the balances of the days it covers come out those cents above what the bank shows, until a later statement covers those days again. The PDF and the Excel export state each closed day's balance and match the bank to the cent.

When the file carries no usable balance and the account does not know one yet, the import stops and asks for the previous balance: what the account closed at on the day before the statement starts. It is asked once; from then on the account keeps itself up to date. Not even a file that starts after a stretch with no statement brings the question back: the balances carry on from the last one the account knows, adding the file's entries, and the entries of the stretch fall on their own days when that period is imported.

Partners and classification

Itaú's spreadsheet carries the company name and the CPF/CNPJ of whoever paid or was paid. PhinApp links each transaction to the matching partner - and registers whoever is not there yet, as a supplier, a customer or both, following which way the money went. For other banks, the name is read out of the transaction's own wording whenever it carries one reliably.

First the classification rules - yours and the ones PhinApp learned from what you already classified - classify what they recognise; then, if the partner has a default category, the transaction arrives already classified. The import's summary says how many the rules classified. At the end, reconciliation looks for the titles these transactions settled - and, with automatic reconciliation on, reconciles by itself those of partners with a default category and those a rule that may reconcile by itself classified.

The document number

When the bank prints a number beside a transaction - Bradesco's Docto., Santander's Nº documento, an OFX file's CHECKNUM (or, without one, its REFNUM) -, PhinApp keeps that number on the transaction. It appears in the Document no. column of Banking Transactions, on the open transaction and on both sides of reconciliation, and the search finds the transaction by it.

In reconciliation, a transaction whose document number is one of the title's numbers - a boleto's bank number, the document number, the ERP code - is that title's transaction. That is what tells apart two titles of the same partner, day and amount.

What is not a document is left out: in OFX, Itaú repeats the transaction's own identifier there, and Inter the bank's code. Transactions imported before the number was kept have none until the statement is imported again - the ones already there are not duplicated, they only get their number.

What is not a movement

  • Balance rows (SALDO ANTERIOR, SALDO TOTAL DISPONÍVEL DIA and the like) never become transactions - they are used for the balances.
  • At Itaú, the scheduled entries (lançamentos futuros) that the online banking PDF and the Excel export list after the transactions - scheduled PIX, TEDs and debits - are not imported: the money has not left yet. What follows them, the consolidated position and the limits, is left out too.
  • At Itaú, the automatic investment (APL APLIC AUT MAIS and RES APLIC AUT MAIS) is ignored: it is the bank parking and returning the account's own balance, without the money ever leaving the company. The interest that investment pays (RENDIMENTOS REND PAGO APLIC AUT MAIS) is imported as usual, because it is income.
  • At PicPay, what was paid with the card (a Pix or a bill paid on credit) appears on the account's statement, but the account's balance does not move: the amount is on the card's bill. So those lines are not imported with the statement - importing them would count the expense twice.
  • At RecargaPay, the CDI yield (Rendimento CDI) appears on the wallet's statement but is not part of its balance: it goes to the card's guaranteed limit, along with cashback. So it is not imported - the wallet's balance in PhinApp is the one the app shows.
  • At Nomad, only completed transactions are imported (Settled, or Concluído in the Portuguese report). One still pending is left out, with a warning in the import's result, until a report shows it completed.

Grouped payments

Some statements lump several payments into a single transaction. At Itaú it is SISPAG FORNECEDORES (and SISPAG FORNECEDORES PIX QR-CODE): a whole batch of supplier payments shows up as one debit, with nobody's name on it. A transaction like that cannot be classified or reconciled - it is the sum of several titles, from several suppliers.

That is why a statement containing SISPAG FORNECEDORES is refused as a whole, OFX or spreadsheet, and nothing in it is imported.

Export the detailed statement

In your online banking, export the detailed statement for the same period - on it, every payment in the batch has a line of its own, with the company name and the CPF/CNPJ of whoever was paid - and import that file. At Itaú, use the spreadsheet (.xls or .xlsx) of the detailed statement: the OFX lumps the batches together.

The other SISPAG batches - SISPAG SALARIOS, SISPAG DIVERSOS, SISPAG TRIBUTOS - are imported as usual: many companies would rather see the payroll, for example, as a single figure in the cash flow.

Balance discrepancy

If two balances stated by the bank do not add up with the transactions between them, the import result shows a balance discrepancy for the file's accounts: the account, the period and the difference. It is almost always a missing statement - import the period shown and the warning goes away. A difference you chose to leave at a format switch stays, and is shown whenever that account is imported.

Credit cards

The PDF bill is the simplest way: it states the closing and due days, and the card sets itself up on the first import, under the name the bill gives it (which can be changed later). Instalment purchases are recognized by the part the bill prints - "Parcela 2/5", "Parcela 4 de 12", "(03/12)" or, on Itaú's, the "04/05" beside the name - and each part lands on the month it belongs to; the parts the bill lists for the next bills are left to them. The part is not part of the partner's name: every instalment of "Store X - Parcela 4/12" goes to the partner Store X. If the bill does not add up - the previous bill's total plus what this one posts is not this one's total - the import result says so.

A card's OFX is imported the same way, but states neither the closing nor the due day: the first time, PhinApp asks for the card's name and those two days, and holds on to the file while you answer - there is no need to choose it again. From then on, whatever the format:

  • each purchase counts on the day it posted to the card;
  • the future parts of an instalment purchase become open payables, one per month;
  • paying the bill is a transfer between accounts, neither income nor a partner - and it is linked on its own to the checking account's debit of the same day and amount (see how).

See Credit cards.

After importing

An imported transaction is a quotation from the bank: date, amount and description cannot be changed, because each day's balance is worked out from them. What can (and should) be filled in is the classification, the partner and the reconciliation.

On this page