Orco Bank provides statements for business and personal current accounts in Curaçao, in Netherlands Antillean guilders (ANG) until 2025 and in Caribbean guilders (XCG) from 2025 on. The reviewed statements are business current account statements from 2024 to 2026, including a combined statement with a summary of balances for two accounts.
Countries: Curaçao
Supported statement formats: PDF
Supported destinations: QuickBooks Online, Xero, CSV/Excel
QuickBooks Online can read a PDF statement itself: Banking, Upload transactions, choose the PDF. Try it first. Use ProperConvert when QuickBooks flags the statement for review, stops before the last page, or the account is not in QuickBooks Online.
For a short statement, type the date, memo, and amount into the destination. Reconcile the result to the closing balance.
Open the PDF statement, review the extracted transactions, choose QuickBooks Online, and save the converted file on your computer.
Choose the posted transaction date, supply a missing year from the statement period, and check statements that cross January.
Remove currency symbols from numeric cells, preserve the decimal separator, and verify debit and credit signs against the running balance.
Keep the payee or customer reference that helps identify the transaction, while avoiding repeated headers and unrelated reference numbers.
The following details were checked against Orco Bank business current account statements from Curaçao, 2024 to 2026, from three to fourteen pages each, including a combined statement with a "SUMMARY OF BALANCES" page for two accounts. The bank name is not in the text layer; it is in the logo. The page is recognized by the account line, 450012-104-001-001-01 XCG, the "C/A Business Resident" account type, and the "Starting balance on" and "Ending balance on" rows.
040126 for April 1, 2026, in MMDDYY order. The statement period is printed in the header as 04/01/2026 and 04/30/2026, month first. Both are US order on a Dutch Caribbean statement, which a converter set to day-first for the region gets wrong on every row that can be read both ways.1,782,156.43-, and a positive balance without one, 5,358.64.450012-104-001-001-01 with the currency after it. The last two digits are the sub-account, and a combined statement lists -01 and -02 under "SUMMARY OF BALANCES".The transaction table has no header row in the text layer. Dates are on the left, the description in the middle, then two amount columns and the balance. Debits are in the left amount column and credits in the right one. A converter that guesses the columns from the first row, or that reads amounts by their order in the text, has a fifty percent chance of swapping every sign. The check is the balance: for a business account that runs on a credit line, the balance has a trailing minus and grows when a debit posts, 1,801,576.99- after a 36,330.00 payment.
The reviewed fireworks importer runs its account on a credit line, so every balance on the statement is negative and printed with the minus after the number, 1,873,062.39-. A converter that reads 1,873,062.39- as text and not as a negative number loses the running balance check. One that reads it as a positive number reports the account with two million guilders of cash instead of two million of debt.
Every page ends with an "Ending balance on 4/30/2026" row that carries the running totals of debits and credits up to that page, and every page after the first starts with a "Previous page balance" row that repeats them. The final page also prints *** End of account statement ***. A converter that reads every row with a date and two numbers as a transaction picks up a "Previous page balance" transaction on each page and an "Ending balance" transaction at the end, with amounts in the hundreds of thousands. The footer and the carry-forward row are not transactions; only the last page's footer is the closing balance.
A card terminal purchase prints MAESTRO/POS with the amount on the first line, then a line of terminal and authorization codes, 0601080054 557091 120814 0527 268269, then a second code line, then the merchant, 190000 DELINOVA B.V., then the city and country code, CURACAO CW. The payee is on the fourth line. A converter that keeps the first line calls every purchase MAESTRO/POS; one that joins all five lines puts forty characters of codes before the merchant name. Card sales received from the bank's terminals are the reverse: VS-MC SALE Christmas Palace and DB OB SALE rows are credits with the merchant's own store name, and MERCH FEE rows are the debits for them.
Transfers to and from other banks on the island carry the customer's own memo as the description, mcb naar orco bank over and over orco van rbc alivio, in Dutch, followed by the account name on the next line. There is no bank code and no reference number on the row. A converter that wants a payee gets the memo, and the accountant who sets up the rules has to match on naar orco and van rbc to tell inbound from outbound, since the amount column already says which is which.
A year-end statement can start with a "SUMMARY OF BALANCES" page that lists each sub-account with its currency and balance, followed by an "IMPORTANT MESSAGES" block, before the transaction pages of each account. The summary balances have the same trailing-minus format as the transaction balances. A converter that starts parsing at the first number on page one reads the summary as transactions of the first account. The account pages are the ones with a "Starting balance on" row.
Compare the converted transaction count and totals with the statement, then confirm that the calculated final balance equals the printed closing balance.
Yes. If the PDF statement is readable, its age does not prevent conversion. Confirm the year when transaction rows omit it.
No. Convert posted transactions that contribute to the statement balance. Pending or future-dated items should not be mixed into that reconciliation.
Use the destination-specific settings below, then review the file before import. The destination may require particular columns, dates, account identifiers, or sign rules.
A bank PDF can contain searchable text, scanned page images, or a mixture of both. Searchable text still needs layout analysis because transaction descriptions wrap, columns move, and headers or balances repeat at page breaks. A scanned statement adds OCR uncertainty.
A transaction may begin at the bottom of one page and continue on the next. Continuation pages can omit column headings, repeat an opening balance, or insert footer text and legal pages between transaction pages. A conversion should join split rows and exclude repeated page furniture before it writes the output.
On scanned pages, OCR can turn 0 into O, 1 into l, or 5 into S. It can also lose a minus sign or decimal mark, read two columns in the wrong order, or struggle with skewed and faint pages. The running balance is the best check: a damaged amount or missing row breaks the balance sequence.
Yes. Review the OCR result and reconcile every balance movement. Scans with faint printing, rotation, or handwritten marks need more checking than searchable PDFs.
PDF text stores page positions rather than a spreadsheet table. Wrapped descriptions, repeated headers, and visually aligned columns can paste in the wrong order or into the wrong cells.
Try selecting a transaction description in a PDF reader. If individual words can be selected, the page probably contains text. If the whole page behaves like one picture, it requires OCR.
QuickBooks Online imports bank transactions from a file through Banking, Upload transactions. It accepts QBO, QFX and OFX files, which share the OFX structure, and CSV files. Uploaded rows land in the For Review list, where QuickBooks matches them to existing entries and the user adds or excludes them.
Since 2026 the same upload screen also takes a PDF or an image of a statement (JPG, PNG, HEIC). Intuit's AI reads the pages, and a statement it cannot read with confidence is held for a manual review by Intuit staff. If the account is in QuickBooks Online and the statement is a clean PDF, try that first; it costs nothing. A converted file is the better route when the upload flags the statement or stops before the last page, when there are many statements to catch up, when the bookkeeper wants to see and fix every row before it enters the books, or when a client's statement should not be uploaded to a third party.
Settings that matter:
MM/DD/YYYY or DD/MM/YYYY depending on the company settings, digits only, four-digit years.Use OFX, QFX or QBO when the file can be made in that format. It carries the payee, the memo and the check number and gives QuickBooks a transaction ID for duplicate checks. Use CSV when a spreadsheet is the only source and a single description is enough.
The usual causes are a date column QuickBooks cannot read, an amount with a currency symbol or thousands separator, more columns than the three- or four-column layout, or a file over the size limit. Save the file with dates as digits, amounts as plain numbers, and only the needed columns.
The account was chosen during upload. QuickBooks Online does not read the account name from the file. Exclude the rows, delete them from Excluded, and upload again with the right account selected.
In For Review, select the rows, choose Batch actions, Exclude Selected. Open Excluded, select them again, Batch actions, Delete. The rows are gone and the file can be uploaded again.
QuickBooks Online skips rows whose transaction ID it has already seen and, for CSV, rows it reads as duplicates by date, amount and description. Two genuine identical rows on the same day can be dropped from a CSV. Use an OFX-type file with unique IDs for those.
Yes. The 90-day limit applies to a live bank connection, not to a file upload. Any date range can be uploaded from a file.
For one clean statement of an account that is already in QuickBooks Online, the built-in upload is the shortest path, and this page says so. A converter earns its place when the upload flags the statement for review, when a scanned or multi-year statement does not go through, when the account is in QuickBooks Desktop, Quicken, Xero or Sage instead, or when the statement must stay on your computer. The converted file goes through the same Upload transactions screen as a QBO file, with a transaction ID per row, so re-uploading a period does not double it.