Maduro and Curiel's Bank provides current and savings account statements in Curaçao and Bonaire, in Netherlands Antillean guilders until 2025, Caribbean guilders from 2025 on, and US dollars. The reviewed statements are seven business current account statements from 2023 to 2026, including one Bonaire account in US dollars.
Full name: Maduro and Curiel's Bank
Countries: Bonaire, 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 seven Maduro and Curiel's Bank current account statements from Curaçao and Bonaire, 2023 to 2026, in Netherlands Antillean guilders (NAF or ANG) before 2025, Caribbean guilders (XCG) after, and US dollars on the Bonaire account. The layout is the same across all three currencies. MCB Ltd of Mauritius is a different bank with a different statement and is not covered here.
DD/MM with no year, 06/03, under a column headed "DATE D/M". The header prints only one date, "Statement Period MARCH 13 2026", which is the closing date, so the year and the start of the period come from that date and from the "PREVIOUS BALANCE" row, 30/12 on a January statement.1.259,95 and 364.028,96. Debit and credit are two unsigned columns. The balance carries a CR suffix glued to the number, 364.097,23CR, on every row; an overdrawn balance would read DR. Foreign amounts on detail lines switch to the other convention, 12,305.00 EUR @ 2.108600000, so one file holds both formats.XCG - CURRENT ACCOUNT# ******9409, with the currency code in front. The full number is not on the statement.NAF - CURRENT ACCOUNT, XCG - CURRENT ACCOUNT or USD - CURRENT ACCOUNT. The same account changed its code from NAF to XCG when the currency changed in 2025.Merchant card settlements, which are most of the rows on a business account, print the net amount on the dated row, MMDT LC EDC BTC# 222 TID# 3583 68,27, then XCG 69,00 COMM. 0,69 on the next line, the gross sale and the commission, and NAOB TAX 0,04 on a third, the tax on the commission. On Bonaire the tax line reads ABB 0,05. The net amount is the transaction and is what moves the balance; the gross, the commission and the tax are not separate transactions. A converter that reads every number as an amount produces three or four rows per settlement and a balance that never reconciles. The commission and tax lines are worth keeping as memo text for the bookkeeper who has to expense them at month end.
364.097,23CR is three hundred sixty-four thousand guilders and twenty-three cents, in credit. A converter set to North American format reads it as 364.097, a converter that does not strip CR reads nothing, and one that strips it but reads CR as a credit-card credit inverts the account. The running balance is the check for every row, so getting this one token right is the first job on an MCB statement.
"Statement Period MARCH 13 2026" is the only date in the header, and it is the closing date. The opening date is the date on the "PREVIOUS BALANCE" row, 06/03 on a statement that closes on 13 March, because MCB issues statements weekly for busy accounts, and 30/12 on a January statement, which is in the previous year. A converter that assigns the header year to every row puts the December opening balance in the wrong year.
An incoming transfer prints the counterparty on the dated row, MOSA RESTAURANT B.V. 2.768,53, then one or two memo lines as the payer typed them, SERVIS FRAIS, INVOICE 2026-23002, Statement februari, in Papiamentu, Dutch or English. Outgoing transfers print the payee the same way and add TRANSFER CHARGES XCG 25,47 as a separate fee row with reference 0. A converter that keeps only the dated line has the payee and loses the invoice number; joining the lines keeps both.
A payment abroad prints 12,305.00 EUR @ 2.108600000 under the row, in point-decimal format inside a comma-decimal statement. The guilder amount on the dated row is the transaction; the euro amount and the rate are memo. A converter that applies one number format to the whole file reads the euro figure as twelve guilders.
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.