Skip to content
Boekhouden.farshadbashir.nl

CAMT-bankafschriften importeren
Contents and search

Import CAMT bank statements

Check statements and possible duplicates before importing their source data.

Importing reads a CAMT.053 file and stores the bank data. It does not post accounting entries or link anything to an invoice or purchase. CSV, MT940 and a direct bank connection are not supported.

Step by step

  1. 1Download a CAMT.053 statement from your bank. Open Bank imports and choose Import CAMT to inspect the file; the maximum upload is 5 MiB. A completely empty optional payment description is allowed. The original file remains unchanged; all other structure and data checks still apply.
  2. 2Explicitly map each statement to the correct configured bank account. Check the account identity, currency and current account settings.
  3. 3Review the import preview and every page of entries. Proven repetitions are recognised; for possible duplicates you decide whether the entry is new or already present. An equal amount alone does not prove duplication.
  4. 4For a single transaction you see the available payer or recipient, counterparty account and payment description. A batch entry shows its transaction-detail count, not one selected counterparty. View additional bank information lets you browse source details before import without losing account mappings or duplicate choices. A source reference identifies the entry in the statement; a bank reference is the bank’s reference. A missing reference does not mean that the counterparty is unknown.
  5. 5A single transaction detail without its own amount does not need to repeat the bank amount and, when no batch information is present, does not cause a missing-detail-amount warning. Multiple details, batch information or a detail amount in another currency retain that warning. Mismatching totals, directions and other review points also remain visible. No detail amount is filled in and no bank amount is changed. This also applies to previously imported entries.
  6. 6A detail-amount warning does not indicate missing names. The entry list searches names, account numbers, descriptions, payment text and references in source data, without distinguishing uppercase and lowercase. Search stays within the selected bank account.
  7. 7Confirm only when the account mappings and duplicate choices are correct. If the reviewed state has changed, request a new preview.
  8. 8Too many import actions in quick succession produce a wait message. Leave the form open: the selected file, account mappings and duplicate choices are retained. Retry later; request a fresh preview before confirming if needed.
  9. 9Bank imports shows the account name, account number and period from the bank file for each statement. Imported on is the upload date, not the statement period. Each card shows up to three statements, with the number of remaining statements and View all statements. All statements remain available there, 25 per page. Each statement keeps its own account and period; missing period boundaries are never inferred.
  10. 10Keep or download the original file while available. You can delete just the source file without removing imported entries. A full import cannot be removed while affected entries are linked; deleting an import does not delete accounting entries.

What is on the screen?

  • CAMT.053 file
  • Account for each statement
  • Possible duplicates and explicit choices
  • Import preview and confirmation

What happens next?

Entries, source statuses, descriptions and available batch and charge information remain reviewable. Amounts are rounded arithmetically to the smallest currency unit. The original file is kept unchanged and encrypted in private file storage until you delete it. Imported data remains in the database.

For developers

  • Inspection and preview require banking:write but no Idempotency-Key. Confirmation requires the current state_hash and an Idempotency-Key. Preview entries are paginated; request candidates for an ambiguous entry separately.
  • Inspection, preview and import share one configurable per-user limit across the website, API tokens and administrations: 30 per minute by default. Failed attempts count. Existing API limits still apply; HTTP 429 includes the wait time in Retry-After.

Common situations

I see an errorRead the message by the field, correct the value and try again. Other details remain where possible.
I cannot continueCheck that all required fields are complete. If a link no longer works, request a new one.