Bank-statements.co Logo Bank-statements

Convert Capitec Bank Statement PDF to OFX

Extract transaction rows from a PDF, review them against the original statement, then choose an export for your accounting workflow.

Last updated: September 17, 2026

Get the original Capitec statement

In the Capitec app, open the relevant account, use the three-dot menu, select Statement, choose the period and share the PDF. Keep the original PDF rather than a screenshot. Capitec's statement instructions explain the current process.

For a rand account, check the ZAR currency against your destination account before choosing OFX: this converter's OFX currency currently defaults to USD. A reviewed Xero CSV or native bank export may be more suitable. See also the South Africa statement guide.

Review the PDF before exporting

  1. Use the original digital PDF and unlock it before uploading. Include all transaction pages.
  2. Check extracted dates, descriptions and debit/credit amounts against the PDF. Compare totals and balances rather than assuming a completed conversion is correct.
  3. Choose OFX only if the destination accepts it. Review the account, currency and date range before importing.

What to check in the OFX file

  • Signs: TRNAMT is negative for a debit and positive for a credit. For example, a synthetic debit of 125.50 becomes -125.50; a synthetic credit of 1000.00 becomes 1000.00. Check these against actual money out and money in.
  • Dates: DTPOSTED uses YYYYMMDD. Confirm ambiguous dates and missing years in the preview. The exporter can fall back to the current date when a date cannot be parsed: resolve warnings before importing.
  • Account and currency: CURDEF is USD; ACCTTYPE is CHECKING; BANKID is 999999 and ACCTID is 999999999. These are placeholders, not extracted bank details. Use another export if your importer cannot resolve a mismatch safely.
  • Balances: LEDGERBAL contains 0.00, not the statement's verified closing balance. Reconcile against the original PDF.
  • Overlapping transactions: FITID is generated from transaction fields and row position. It is not a bank transaction ID. Compare overlapping statements and feeds manually.
  • Descriptions: NAME is limited to 32 characters; longer descriptions also go into MEMO. Check how the destination displays references.

These examples describe the exporter, not a live bank-to-accounting import test. We have not certified a Capitec or Barclays OFX import. See Excel review examples or Xero CSV mapping.

Frequently asked questions

Should I use a native bank export first?

Yes. If your bank provides a structured export accepted by your accounting software for the required period, use it first. PDF conversion adds an extraction step that needs review.

Is a converted OFX file ready to import without changes?

No. The current OFX export uses USD, a checking account type, placeholder bank and account identifiers, and a zero ledger balance. These are defaults, not verified details from your statement. Use a native export or reviewed CSV if they do not match your account.

Can overlapping statements create duplicates?

Yes. In OFX and QBO exports, generated transaction identifiers depend partly on row position and are not bank-issued identifiers. Do not rely on them to deduplicate overlapping statements or bank feeds. Compare the date range and individual transactions before import.

Other options: Excel, CSV, OFX. Prefer your bank's native export when available.