Banana Accounting: Swiss CAMT extension or text import?

A Swiss bank CAMT file and a three-column cash CSV need different import routes in Banana Accounting. Renaming the CSV to XML does not supply CAMT structure. Start with the original file type, Banana edition and actual account rather than the download extension alone.

LocalExtract prepares CSV locally from one PDF. Its date,description,amount export is not a Banana extension or a ready-made transactions.simple file.

Prefer the documented CAMT route for a native Swiss file

The Swiss CAMT extension requires Banana Accounting Plus and documents Swiss .08 and .04 schemas. This is a Swiss-format scope, not a compatibility claim for every international CAMT file. The ISO import documentation distinguishes Professional and Advanced capabilities; verify your plan and file before relying on a facility described for another edition.

Install through Extensions → Manage Extensions → Online → Import, selecting Bank Statement Camt ISO 20022 Switzerland (Banana+). In the target accounting file, use Actions → Import to Accounting, choose that extension and open Settings.

Review All/Credits/Debits, QR invoice/customer extraction and Add Contra Account Transaction. The latter can insert a temporary [CA] transaction for the total of details; the proper counter-account still needs completion. QR number extraction depends on the actual reference layout. A reference is not universal proof of the customer or invoice.

Keep QR detail and the daily bank total from being counted twice

The extension guide describes camt.054 QR details alongside an aggregate camt.053 credit. Importing both into the same bank account without the documented accounting treatment duplicates that receipt. Its clearing-account procedure is distinct from simply summing all imported rows.

Our synthetic coverage check uses two QR details of 45 and 55 and one bank aggregate of 100. These describe one 100 receipt at different levels, not 200 of new income. The route-and-grain worksheet separates that check from text-field validation; it does not execute Banana or establish a clearing-account setup for your books.

For ordinary text, build the documented TSV instead

The transactions.simple specification uses UTF-8, tab-separated fields. Its required, case-sensitive headers are Date, Description, Income. Dates use yyyy-mm-dd, decimals a dot, no thousands separators; negative Income can express an expense. Expenses is an optional separate field.

Use Actions → Import into accounting → Transactions, with file type Income & Expenses transactions. A LocalExtract column named amount must be reviewed and mapped to the required Banana field; comma-delimited text must actually be transformed to tabs. Confirm bank direction and supply the correct counter-account rather than assuming a three-column file is finished accounting.

For dates and localized decimal repair, use the CSV locale guide. Here the decision is Banana’s native Swiss extension versus its defined simple-text route. Extract a PDF locally only if no suitable original bank data is available.

Official Banana documentation checked October 16, 2026; no import executed.