Drop in a PDF bank statement and get clean rows: date, description, debit, credit, and balance. For the subsidiary, foreign, and low volume accounts your Workday bank statement feed does not cover. Start free, no credit card.
Upload your bank statement
Drop file here or click to upload
PDF, JPG, PNG, BMP, HEIC, TIFF, MT940
Uploading...
Workday brings statements in through its Bank Statements connector, which supports the BAI2 standard at version 2 and the ISO 20022 customer bank statement format. Neither of those is a PDF. When an account has no such file behind it, and plenty do not, you need the transactions as structured rows before anything can be loaded or reconciled. Upload the statement PDF here and each line comes back as a dated row with description, amount, and running balance, ready for your loader, your integration team, or a manual reconciliation in Excel. Last updated July 2026.
The connector does its job for the accounts it covers. The friction is always the accounts it does not.
Workday reads BAI2 and ISO 20022 customer bank statements. A PDF e-statement is not a format the integration can consume, and there is no fallback parser for it.
Balance reporting is a treasury service that smaller US banks, credit unions, and many overseas banks either do not sell or price out of reach for a low volume account.
Adding an account to an existing transmission means bank paperwork, test files, and an integration window. Meanwhile the close is on a fixed calendar.
A newly acquired entity has months of statements and no bank interface. Somebody still has to reconcile the opening period.
A transmission fails quietly for two weeks and nobody notices until reconciliation. The bank will resend a statement PDF far faster than it will rebuild a file.
Workday matches on amount and date. Retyped statements produce transpositions, and every transposition becomes an unmatched item somebody investigates by hand.
Structured, column separated transaction data that matches what a bank file would have carried.
Date, description, reference, debit, credit, and balance each land in their own field instead of one merged string.
The control totals stay with the data, so you can prove the extracted lines add up to the statement before anything reaches Workday.
Sign and direction are preserved rather than inferred, which is what keeps a reconciliation from flipping a payment into a receipt.
Convert a year of monthly statements in one pass and get a single date ordered sheet you can split by period.
Take the CSV if an integration team is building the load, or the workbook if the reconciliation is happening in Excel this month.
No connection to Workday, no bank credentials, no integration system user. You upload a document and download a spreadsheet.
The path for accounts with no bank statement feed behind them.
Drag the file into the box above. Add several months at once if you are backfilling a period.
Tip: Scanned statements work too.
Confirm the converted rows sum to the movement between the opening and closing balance printed on the statement. This is the one check worth doing every time.
Tip: A mismatch here always beats finding it in an unmatched queue later.
Hand the CSV to whoever owns the load into Workday, or reconcile directly in Excel against the Workday transaction register for that account and period.
Tip: Keep the file naming per account and period so the audit trail stays obvious.
Almost always the person holding a reconciliation that is short one account.
Bring low volume, foreign, and subsidiary accounts into the same reconciliation discipline as the accounts on the feed.
Close the month when a transmission failed and the bank can only resend a PDF in the time available.
Load historical periods during a deployment, before the Bank Statements connector goes live for that account.
Reconcile an acquired entity from the statement history it actually has, which is rarely a set of BAI2 files.
Workday imports statements through its Bank Statements connector, part of Workday Integration Cloud Connect. The BAI2 connector handles bank statements compliant with the Bank Administration Institute standard at version 2, and the connector set also covers the ISO 20022 customer bank statement format, which is the camt.053 family. That is the shape of file a bank has to transmit. A PDF is a rendering of a statement, not a data file, so it has no route through the connector.
| Account situation | Best route into Workday | Where conversion helps |
|---|---|---|
| Main operating account, bank transmits BAI2 | Bank Statements connector | Not needed |
| European account on camt.053 | ISO 20022 connector | Not needed |
| Small US bank, no balance reporting product | No feed available | Convert the PDF to rows |
| Acquired entity, pre integration | No feed yet | Convert the PDF history |
| Closed account, missing period | Nothing left to transmit | Convert the archived statement |
Because it is the format US banks standardized on for cash management balance reporting long before ISO 20022 existed. A BAI2 file is a flat text structure of record types: a file header (01) and trailer (99), group header (02) and trailer (98), account records (03 and 49), and transaction detail on type 16 lines. Most large US banks will deliver it for an operating account. The reason it does not solve everything is that it is a product the bank sells, so coverage falls away sharply as accounts get smaller. Our BAI2 record code guide walks through the structure if you need to read one by hand.
For a one off gap, often yes, and it is usually faster. Pull the Workday transaction register for the account and period, put the converted statement rows beside it, and match on amount and date. What you are looking for is the same short list every time: deposits in transit, outstanding checks, bank fees not yet booked, and anything that only exists on one side. Document the reconciling items and attach both files. When the same account needs this every month, that is the signal to go get a real feed rather than repeat the manual pass.
Three things, in order. Dates, when the statement shows a value date and the ledger used the booking date, which pushes items across a period boundary. Sign convention, when a converted credit is loaded as a debit and the variance is exactly twice the amount. And truncated descriptions, where a bank shortens the payee so the match on text fails even though the amount is right. Keeping the reference field separate from the description helps with the third one, which is why the converter does not merge them. Once transactions are in columns you can also categorize them for management reporting, and if a smaller entity in the group runs its own books a CSV to QBO converter gets the same rows into QuickBooks without extracting twice.
No, and it should not. A transmitted BAI2 or camt.053 file arrives automatically, carries structured bank codes, and needs no human. If you can get one for an account, get one. Conversion is for the tail: the accounts too small to justify a treasury service, the ones outside the US where the bank works differently, the historical periods that predate the integration, and the emergencies where a file did not arrive and the close cannot wait.
Workday imports statements through its Bank Statements connector, which supports the BAI2 standard at version 2 and the ISO 20022 customer bank statement format used for camt.053. Those are the file types a bank transmits. Workday does not read a PDF statement.
No. The Bank Statements connector consumes structured files, not rendered documents, and there is no PDF parser to fall back on. The practical route is to convert the PDF into transaction rows first, then either load those rows or reconcile them in Excel against the Workday register.
BAI2 is the Bank Administration Institute cash management statement format, a flat text file built from record types: file header 01, group header 02, account records 03 and 49, transaction detail 16, and the matching trailers 98 and 99. US banks standardized on it for balance reporting well before ISO 20022 arrived.
That is common for smaller banks, credit unions, and low value accounts, because balance reporting is a paid treasury service. Convert the statement PDF into rows and reconcile from there. Keep asking the bank in parallel, since a real transmission is always the better long term answer.
Convert its statement history into one sheet, split it by period so opening and closing balances line up with each statement, and reconcile period by period against the ledger you brought over. That establishes a clean starting balance before the account is added to the bank feed.
No. It produces Excel and CSV transaction rows. If you already hold a BAI2 or camt.053 file, load it through the connector, which will always be cleaner than any conversion. This is for accounts where no such file exists at all.
Yes. Statements that were printed and scanned, or received as image based PDFs, go through OCR before the table structure is read. Check the totals against the printed closing balance afterward, which is a good habit on any conversion but especially on a scan.
As far back as you still hold statements. Most US banks keep PDF e-statements online for around seven years, and any statement you archived locally works regardless of what the bank still shows. There is no date limit on the conversion itself.
The same gap in an Oracle Fusion shop.
Import ready data for SAP cash management.
Read a BAI2 file you already have.
Volume conversion for finance teams.
Statement data prepared for audit testing.
From the same family of tools
Get started converting bank statements to spreadsheets.
USD
per month
billed as
$288 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 2,500 pages |
| Pro AI Best accuracy | 500 pages |
Scale statement conversion across your team with automation.
USD
per month
billed as
$888 yearly
Choose speed vs accuracy when extracting
| Base AI Faster | 10,000 pages |
| Pro AI Best accuracy | 2,000 pages |
Enterprise-grade bank statement conversion and controls.
USD
per month
billed as
$ yearly
Choose speed vs accuracy when extracting
| Base AI Faster | pages |
| Pro AI Best accuracy | pages |
