Skip to main content

Bank statements

Bank statements import an account's statement and create transactions from it. The accepted formats are OFX and QIF.

Where it lives​

Statements are not a screen of their own and have no menu item. It's a tab inside the account:

Financial accounts → open the account → Statements tab.

That's why there is no "pick the destination account" step: the account is the one you're already in. You need a specific company selected in the header — under "all companies" the panel just tells you so.

Accepted formats​

FormatExtensionDescription
OFX.ofxOpen Financial Exchange — the standard at most banks
QIF.qifQuicken Interchange Format — a legacy format, still used by some banks

The Download sample button offers one file of each format. They are examples so you know what the format looks like, not templates to fill in — a statement is exported from the bank, not written by hand.

Importing​

  1. Export the statement from your bank in OFX or QIF.
  2. On the account's Statements tab, upload the file.
  3. The system reads the file and shows what it found: how many transactions are importable and how many were ignored.
  4. Every line comes pre-selected. Click a line to deselect it if you don't want it imported.
  5. Click Import N transactions.

The import runs in the background: you get the notice "Import started in the background" and follow along in a progress dialog — the screen isn't stuck waiting.

Imported transactions come in unreconciled. To link them to bills, use Reconciliation.

What gets ignored​

Three cases are discarded on read and counted, with the summary on screen — "Ignored: 2 future-dated, 1 zero-amount, 0 with invalid date.":

  • Future date
  • Zero amount
  • Invalid date (an unreadable value lands here too)

Deduplication​

note

Dedup identifies a line by the identifier the bank gives it (the OFX FITID) — not by "same amount, date and description". When the file carries no such identifier (always the case with QIF), the system builds a key from date, amount and description plus the order of occurrence, precisely so that two identical lines are not mistaken for one another.

What deduplication guarantees: re-uploading the same file to the same account duplicates nothing. Lines already known are skipped, and the history tells you how many.

What it doesn't guarantee — and is worth knowing:

  • Two genuinely identical transactions both come in. Two R$ 50 withdrawals on the same day, with the same description, are two real transactions. The system preserves them on purpose.
  • There is no dedup across sources. The same transaction arriving via OFX, via QIF and via Banking Gateway sync counts as three — each source builds its own key.
  • Dedup is per account, not per workspace.
  • Nothing is flagged on screen. The check happens on the server, at import time — not while you're reviewing the list.

History​

Below the import panel, the History section lists the files already imported: date, file, status, how many transactions came in out of the total, and who asked for it. The section only appears once there is history.

The statuses are Queued, Running, Completed, Failed and Cancelled.

Undo​

The Undo action deletes the transactions that file created and removes the statement from the history. The dialog warns you: "This deletes the N transactions imported from this statement. This can't be undone."

If any of those transactions was already reconciled, undoing also breaks the reconciliation.

The action doesn't appear while the statement is Queued or Running — wait for it to finish. It also doesn't appear on statements that came from Fintera: "Extratos vindos do Fintera não podem ser desfeitos aqui — desfaça no Fintera." ("Statements that come from Fintera cannot be undone here — undo them in Fintera.")

Deleting one transaction from a statement​

Deleting a single transaction that came from a statement is different from undoing the whole statement, and the difference shows on the next import:

  • You deleted the transaction — it doesn't come back. Importing the same file again, or syncing the Banking Gateway once more, won't bring it back: the system remembers that you removed it.
  • You undid the statement — then yes, importing the file again brings everything back. That's the way to start over.

This is why deleting the line works, even without Undo. The Banking Gateway statement has no batch to undo, and the sync brings the account's whole history every time. Without that guarantee, the line you deleted would return on the next sync — and if you had already entered the correction by hand, the amount would show up twice.

Other statement sources​

Besides a file, a statement can come from:

  • Banking Gateway — the Sync statement button on the integration screen pulls the transactions of the selected company's linked accounts.
  • Fintera — imports the statement mirrored from the platform.

Neither runs on its own. There is no scheduling: both are a button you press.

note

The Banking Gateway statement doesn't show in this tab's History. It isn't a file — the gateway returns a list of transactions, with no concept of an "imported statement". The transactions show up in the account as usual; the batch doesn't, and that's why there is no Undo for it. To take out a line, delete the transaction: it won't come back on the next sync (see Deleting one transaction from a statement). The record of those runs lives on the Banking Gateway screen itself.