Bank statement to a3
Turn any bank's PDF extracto bancario into a clean CSV of dated, signed transactions you can bring into a3 — no retyping, no line-by-line entry. Any bank, scanned or digital, balance-validated before you import.
Any bank · scanned or digital · balance-validated · CSV / Excel
Get PDF extractos bancarios into a3 without retyping
a3 (Wolters Kluwer, a3ASESOR / a3innuva) imports bank movements primarily through Norma 43 — cuaderno 43, the Spanish bank-file standard your bank issues from its e-banking. Being precise matters here: Norma 43 is a bank-authored file, and FlowParse does not manufacture it, exactly as it doesn't fake MT940. Where your bank offers the N43, use it. Where you only have a PDF extracto bancario — a historical month, a bank without N43, a foreign account — FlowParse gives a3 a clean CSV of dated, signed movimientos instead.
FlowParse reads every transaction off the extracto bancario — the date, the concepto and a signed amount — and builds a clean CSV for a3 instead of you keying each line. The same upload also produces a full Excel workbook with every source column preserved, so you keep detail the a3 transaction view doesn't show.
Because extraction is AI-based rather than template-based, it reads any bank's layout on the first try — and every file is balance-validated so the figures you import into a3 are complete and correct, not a hopeful copy-paste.
Two ways in
In the file
From PDF to a3 in three steps
1 · Upload the PDF
Drop your PDF bank statement — digital or scanned, any bank, any number of pages.
2 · AI builds the file
FlowParse extracts every transaction, signs the amounts, validates balances and writes a CSV.
3 · Import into a3
Bring the file into the matching account in a3 and reconcile — no manual entry.
How to bring extractos bancarios into a3
Convert first: upload the PDF extracto bancario to FlowParse, review the editable preview, and download the CSV. Every row is a transaction with a date, a description and a signed amount, ready to use.
Then import: use the CSV to import the transactions into a3, mapping the Date, Description and Amount columns once. Where a3 offers a live bank connection for your bank, use it for the day-to-day feed and use FlowParse for the banks it can't reach and for historical catch-up.
Have a supplier bill to record too? FlowParse also maps an invoice to a clean line for your books, so the same tool covers both sides of your bookkeeping — statements and invoices — into a3.
What lands in the CSV
| Field | From the statement |
|---|---|
| Date | Transaction date, normalised |
| Description | Payee / concepto (extra columns kept in Excel) |
| Amount | Signed — money out negative, money in positive |
Works with any bank's PDF
Because extraction is AI-based rather than template-based, FlowParse reads layouts it has never seen — ideal for accounts a3's feeds don't cover and for historical months:
Reconciling a whole year? Use Smart Merge to consolidate first, then export once.
Why convert instead of typing it in
Manual entry is where small bookkeeping errors are born: a transposed figure, a skipped line on a long extracto bancario, a wrong sign on a refund. Each surfaces later as a reconciliation that won't balance and an hour spent hunting the difference. Converting removes the typing entirely — and the balance check proves nothing was dropped before it reaches a3.
For an asesoría handling a rattrapage — or a business catching up its own books — that is the difference between an evening of saisie and a few minutes of upload-and-review. And because FlowParse keeps the full detail in Excel too, you never lose a column a3 doesn't store.
How a3 handles bank data — and where this fits
The N43 is the clean path when it exists, but plenty of activity has no N43 behind it: older months, accounts at banks that don't issue cuaderno 43, or foreign accounts entirely. For those an asesoría is often handed a PDF extracto, and typing it into a3 is slow, error-prone work. FlowParse reads each movimiento — fecha, concepto and a signed importe — and builds a CSV a3 can take, balance-checked against the saldo so the period is complete.
There is also a quality angle. A live feed sometimes imports terse, codified descriptions that are hard to categorise against IVA; a PDF extracto bancario usually carries the fuller narrative. Because FlowParse preserves the complete concepto (and keeps every other column in the matching Excel export), you get richer detail to work with, not less — and because the figures are balance-validated before import, you are not trading convenience for correctness.
The practical workflow is simple: keep a3's live connection for your main bank, and use FlowParse for everything it can't reach — a second account, a card from a smaller issuer, a foreign account, or the back-months you need to get caught up. One tool, any bank, no retyping, and a clean CSV at the end that a3 takes cleanly.
Validated before it reaches a3
A bad import means a reconciliation that never balances. Before the file is built, FlowParse checks the data so what lands in a3 is complete and correct:
See the validation engine and reconciliation tools.
Accuracy, security and a real catch-up
Accuracy is the whole point of converting rather than typing, so it is worth knowing how it is achieved. FlowParse reads each extracto bancario by meaning rather than fixed coordinates, which is why an unfamiliar bank layout is handled on the first try and a redesigned statement keeps working. Scanned or photographed statements are read with OCR first, then structured into transactions, and every figure is checked against the statement's own balance before you ever import into a3. Any line the engine is unsure about is flagged for a quick look rather than silently guessed.
Because bank statements are sensitive, data handling matters as much as extraction. FlowParse processes documents in EU data centres, deletes the original PDF as soon as extraction completes, stores only the extracted data (encrypted, and deletable on demand), and never uses your documents to train models — the full posture is on the security page. For an asesoría handling client files, that means you can run a extracto bancario through without worrying where it ends up.
Picture a typical catch-up: a client joins a3 midway through the year with nine months of activity across a main account and a second account the feed doesn't support. Instead of an evening of manual entry, each PDF is converted, the balance check confirms every period is complete, and clean transactions import ready to categorise against IVA — the whole back-year reconciled in an afternoon rather than a week.
And because the same upload also yields a full Excel workbook, nothing is lost: a3 holds the transactions it needs, while the workbook keeps every original column for your records, audit trail or asesoría. One conversion, both outputs, any bank — the honest, complete way to get a extracto bancario into a3.
One upload, every format
The same extraction powers every export — so if you also run QuickBooks, Quicken, Xero or just need a spreadsheet, take the same statement to the format you need without re-uploading.
Take the same data to Excel, QuickBooks or Xero.
| Format | Best for |
|---|---|
| CSV | Importing this statement into a3 |
| Excel (.xlsx) | A full workbook with every source column for your records |
| CSV | A simple, editable table for any tool or import wizard |
| OFX / .QBO / .QFX | Bank-feed files for QuickBooks, Quicken and OFX apps |
| Xero / Sage / Wave | Tailored CSV layouts for other accounting software |
Who imports statements into a3 this way
Anyone who reconciles a a3bank or card account from statements rather than a live feed — because the feed doesn't cover the account, hasn't been set up yet, or the months they need predate it. A few of the most common:
Asesorías
Load client back-months into a3 when there is no Norma 43.
Contables
Convert PDF extractos from banks without cuaderno 43.
PYMEs
Bring a foreign account into a3 as a clean CSV.
Despachos
Standardise mixed-bank PDFs before posting into a3.
Finance teams
Reconcile accounts without N43 against signed data.
Autónomos
Turn a year of extractos into a3-ready transactions.
Any bank → one a3-ready file
Upload statements from every account you reconcile — FlowParse turns each into a clean file a3 imports.
Tips for a clean import into a3
A statement import goes smoothly when the data underneath is complete and correctly signed. A few habits make every a3 import reconcile on the first pass:
- Convert the full statement period rather than a partial export, so the opening and closing balances are present for the validation check to confirm nothing is missing.
- Import each statement period once — or use the OFX file where a3 supports it, since it de-duplicates by a per-transaction ID if you re-import.
- Match the a3 account's currency to the statement you're importing; FlowParse preserves the amounts and signs exactly as the bank reported them.
- Review the fields the validation report flags in the editable preview before you download — clean statements pass automatically, so you only check the exceptions.
- Reconciling a whole year? Consolidate the statements with Smart Merge first, then import a single clean, balance-checked set into a3.
Frequently asked questions
How do I import a bank statement into a3?
Convert the PDF extracto bancario with FlowParse to a clean CSV of dated, signed transactions, then import the CSV into a3 and map the Date, Description and Amount columns once. For banks a3 connects to live, use its feed; use FlowParse for unsupported banks and historical months.
Does a3 import a CSV bank statement?
Being precise matters here: Norma 43 is a bank-authored file, and FlowParse does not manufacture it, exactly as it doesn't fake MT940. FlowParse gives you a clean, correctly-signed CSV plus a full Excel workbook, so the transaction data is ready however you bring it into a3.
Can I convert credit-card statements for a3?
Yes. Credit-card PDF statements convert the same way — each line becomes a dated, signed transaction — so you can record card spending in a3 alongside bank activity.
What about multi-page statements?
Long, multi-page extractos bancarios are stitched into one continuous list and weak pages are retried automatically, so nothing is dropped at page breaks before the CSV is built.
Can I import historical or missing extractos bancarios?
Yes. Convert any PDF you have — including older months your bank only provides as a extracto bancario PDF — and bring them into a3 to backfill the period before you reconcile or file.
Will I lose any detail from the statement?
No. The CSV keeps Date, Description and Amount, and the matching Excel export preserves every original column 1:1 — so any reference, balance or category column on the extracto bancario is retained for your records.
Is it free to convert a statement for a3?
You can try conversion within the monthly page allowance — upload a extracto bancario and preview the extracted transactions first. Accounting exports are part of the paid plans for ongoing volume.
Can I convert statements from any bank for a3?
Yes. FlowParse uses AI extraction rather than per-bank templates, so PDF statements from UK banks (Barclays, HSBC, Lloyds, NatWest, Monzo, Starling), US banks (Chase, Bank of America, Wells Fargo, Capital One), and EU and neobanks (Wise, N26, Revolut) all convert to a a3-ready file. A layout the tool has never seen is read correctly on the first try.
Are scanned or photographed statements supported?
Yes. Image-only PDFs run through OCR first, then the AI structures the recognised text into transactions before building the file for a3. Any low-confidence field is flagged so you can check it before importing.
How are debits and credits handled?
They are normalised into a single signed amount — money out negative, money in positive — with the correct transaction type, so the imported balance reconciles against your account.
Is the conversion accurate?
FlowParse reaches around 98% field-level accuracy on standard statement formats, and every file is balance-validated (opening balance + transactions = closing balance) with per-field confidence scores you can review before importing into a3.
Can I review the transactions before importing?
Yes. An editable preview lets you correct any value, and the validation report flags duplicates, low-confidence fields and balance breaks before you download the file — so nothing wrong reaches your books.
Do I also get other formats from the same upload?
Yes. One upload can export Excel, CSV, OFX and the Intuit-tagged .QBO and .QFX for QuickBooks and Quicken, plus Xero, Sage, Zoho Books, NetSuite and MYOB — so multi-tool firms convert once and export everywhere.
Where are my bank statements processed and stored?
FlowParse processes documents in EU data centres, deletes the original PDF as soon as extraction completes, stores only the extracted data (encrypted, and deletable on demand), and never uses your documents to train models. So converting a statement for a3 is safe, not a privacy trade-off — the full posture is on the security page.
What happens with multi-page or very long statements?
They're stitched into one continuous list and any weak page is retried automatically, so nothing is dropped at a page break. The balance check then confirms the whole statement — first page to last — was captured before the file is built.
Can I automate converting statements for a3 at volume?
Yes. The same conversion runs over the bank statement API: send a PDF and receive structured JSON or a ready-to-import file per page, with the balance validation built in. That lets high-volume teams turn statement intake for a3 into a pipeline step instead of a manual task.
Do I have to enter any transactions by hand?
No. FlowParse extracts every line from the PDF and writes them into the file, so a3 loads the transactions in one import instead of you typing each one. You only review the few fields the validation report flags.