Capitec Bank provides statements for personal and business Global One transaction and savings accounts in South African rand. The reviewed document is a Flexible Savings Account statement produced by the Capitec app as a stamped tax invoice.
Full name: Capitec Bank
Countries: South Africa
Supported statement formats: PDF
Supported destinations: QuickBooks Online, Xero, Sage Pastel, 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.
The app produces a stamped PDF with a SkyQR code, which is the file the converter reads. Pick date ranges that do not overlap when you export more than one statement.
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 a Capitec Global One Flexible Savings Account statement issued from the Capitec app as a stamped tax invoice. Capitec prints transaction, savings and credit facility statements from the same system, so the layout should carry over, but check the converted file against the printed balances for any account type not listed here.
01/11/2023. Read it as 1 November, not January 11. Use Posting Date; the two were equal on every row of the reviewed statement, and Posting Date is the one the running balance follows.12 495.94 and -2 265.40. The Available Balance on the last page has no separator, 10672.17, so the two formats appear in one file.Payment Received: Ridge Painters or Banking App Payment: Annual Golf Day. A reference number printed under the description belongs to the same transaction.Capitec posts a separate row for every fee: Debit Order Fee -3.50 after each debit order, Payment Fee -1.00 or -2.00 after each app payment, Immediate Payment Fee (RTC) -7.50 after each real-time payment, and SMS Payment Notification Fee -0.30 at the end of the day. The balance moves by the fee amount on each of those rows, so they are real transactions and must stay in the converted file. A short statement can have almost as many fee rows as payment rows. This is the opposite of a Nedbank month-end statement, which lists fees in a side column and collects them once a month, so a rule written for one bank cannot be reused for the other.
If you want fees out of the way in the accounting app, do it with a rule or a category after import rather than by deleting the rows, or the bank balance will never match.
Long descriptions wrap onto a second line. Eft Debit Order (1302918877): Oak Legacy (240011983 continues as NETC) on the line below, and the second line has no date and no amount. The first line also contains the full amount and balance, so a converter that reads only one line per date creates a correct amount with a cut-off memo, while a converter that treats every line as a row creates an empty transaction from NETC).
Incoming payments add two more pieces. The row Payment Received: Fernwood Ent. has the word Payment or Transfer further to the right, between the description and Money In (R), and a ten-digit reference such as 1365208469 on the next line. The type word is not part of the payee name, and the reference belongs to the row above it. The expected result for that row is one transaction, dated 01/11/2023, for 6 050.00, with Payment Received: Fernwood Ent. 1365208469 as the memo.
6 050.00, -2 265.40 and -10 000.00 are single amounts, but a text extractor can hand them over as two pieces, -10 and 000.00. If the converter keeps the last piece, the payment becomes 0.00 and the sign is lost with the first piece. Join the pieces into one number before checking the sign and the balance. A balance check catches this at once: -10 000.00 moves 24 255.42 to 14 255.42, and nothing else does.
The statement carries a branch stamp over the header area with the print date, a branch number and a device number. The stamp text is extracted in pieces: Ca pitec Bank, 06/ 11/2023, 0010, Branch : 47 and Device: 9003 on page 1, and Capitec B ank, 06/ 11/ 2023, Branch: 4 70010 and Device: 9 003 on the last page. The pieces sit at different heights and can land inside the header row or next to the From Date and To Date lines.
A converter must not read 06/ 11/2023 as a transaction date or 0010 and 9003 as amounts or check numbers. The stamp is on every statement produced by the app, so this is the normal case rather than an exception.
The header lists From Date, To Date and Print Date, and the Transaction Date column heading itself wraps as Transaction over Date. The table ends with a line that says only End. The second page holds Transactions not yet processed on your account up to 05/11/2023, Cheques not yet processed, two VAT notes with the dates 1 April 2018, and Available Balance: 10672.17.
None of these are transactions. The Available Balance is not the closing balance either: on the reviewed statement the last running balance was 13 240.12 and the available balance 10672.17, the difference being holds not yet posted. Reconcile the converted file to the last running balance, not to the Available Balance.
The app lets the customer pick any date range, so a statement can be five days long with thirty rows, most of them fees under R10. When importing a series of short statements into QuickBooks, Xero or Quicken, overlapping date ranges create duplicates that are hard to see because the fee rows look alike: three Debit Order Fee -3.50 rows on the same day are normal. Export date ranges that do not overlap, or use the converter's date filter to trim the file to the new days only.
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.