How to export the OFX credit-card invoice

Many Brazilian card issuers export the monthly invoice in OFX — the same format used for checking accounts. CaixaUnica recognises the <CCSTMTRS> envelope (credit-card) and routes the file to the Card module automatically. Importer: card-ofx.

OFX is the best option whenever your issuer offers it: stable FITID gives robust dedupe and there's zero heuristic — re-importing the same file never duplicates rows.

Issuers that export card-OFX

Issuer	Typical path
Itaú	Bankline → Credit cards → Invoice → Export as OFX.
Bradesco	Bradesco Net → Cards → Invoice → Export OFX.
Santander	Santander Way / Internet Banking → Cards → Invoice → Export OFX.
Banco do Brasil	bb.com.br → Credit card → Invoice → Save OFX.
Nubank	App → Credit card → open/closed invoice → Export invoice (available on some invoices; if only CSV is offered, see How to export the XP credit-card statement for the CSV pattern).

If your issuer isn't listed, search for "export OFX" in their app or internet banking under cards. The OFX envelope for credit cards is standardised (<CREDITCARDMSGSRSV1> / <CCSTMTRS>) and any well-formed file works.

Import in CaixaUnica

Open Tools → Upload.
Drop the .ofx file. The detector recognises the <CCSTMTRS> envelope and selects card-ofx automatically.
Pick the matching card account (one per holder — PF / PJ — not one per month).
Click Run.

How CaixaUnica interprets the file

Every <STMTTRN> becomes a transaction. The OFX FITID identifies the transaction, so re-importing the same file never duplicates rows.
Sign convention: most Brazilian issuers emit charges with positive <TRNAMT> (issuer's "you owe me" view). CaixaUnica flips the sign to match the unified model (outflow = negative) and keeps the raw value archived for audit.
Invoice payments come through with negative <TRNAMT> (your balance owed went down) → stored as positive here.
Refunds come through with negative <TRNAMT> → also positive in our model (they reduce what you owe).

Common issues

OFX imports but the signs look inverted: a few issuers follow the OFX 2.x spec literally (charges as negative) instead of the more common Brazilian convention. If your purchases land as inflows rather than outflows, open an issue mentioning the institution — the fix is a one-line per-issuer override.
OFX wrapped in HTML: some banks ship the OFX inside an HTML wrapper. Open the file in a text editor and strip everything before the <?xml (or OFXHEADER:100) line.
Re-imported the same file: harmless. Deduplication is by the OFX FITID — overlaps between consecutive invoices are ignored.
My issuer only exports CSV/PDF, no OFX: for XP, see How to export the XP credit-card statement. For other CSV-only / PDF-only issuers, file a request at Settings → Feedback with a redacted sample and we'll evaluate a dedicated importer.

Open in the app