Bank reconciliation: your first statement import

Upload the first statement by hand. That way you see how the module reads your bank before anything is written.

Before you start

a statement from online banking as XML (CAMT.053) or CSV, with a few credits,
the IBAN of the account that receives the payments,
at least one order paid by invoice or UPN QR that is still waiting for payment.

1. Enter the account and the payment methods

Stores › Configuration › Magelan › Bank reconciliation › General

Enter the IBAN in Shop bank accounts (IBAN), one per line. The module then refuses a statement of another account if you upload it by mistake. In Payment methods to reconcile tick the methods your customers use to pay by invoice. Leave auto-invoice off.

2. Upload the statement

Sales › Operations › Bank reconciliation › Upload statement

Drag the file into the box or choose it and press Read the file. The module recognises the format by itself. Leave Delete the source file right after a successful import ticked: statements contain personal data.

3. Read the preview

The preview says how many entries the file has, how many are credits (debits are not stored), how many duplicates and how many payments would be reconciled. The table shows what would happen to each payment. Nothing is written until you press Import.

4. Import

After the import you see a summary and a link to the payments waiting for you. If you entered summary recipients, the module also sends them an e-mail.

You can upload the same file again: the module says it was already imported and creates no duplicates.

Common problems

The file format is not supported

CAMT.053 XML (any version) and CSV are supported. PDF and Excel files are not; export XML (CAMT.053) or CSV from online banking.

The file was already imported, or the statement belongs to another account

In the first case the module shows when the statement was imported. In the second, the IBAN in the file differs from those in the settings; correct the setting or upload the right file.

The module does not recognise the CSV columns

The screen Which column is which? opens. Pick the column for the booking date and the amount (credit), optionally the payer, reference and remittance, and keep the box for saving the layout ticked.

Was this article helpful?

Badges and labels on productsExtensions Product questions and answersExtensions Product enquiry formExtensions Product attachments (data sheets, manuals)Extensions Back in stock notificationExtensions

Cookie name	Cookie purpose
PHPSESSID	Preserves the visitor's session state across page requests.
magelan_geo	Remembers that the visitor closed the suggestion of the other language version of the store, so it is not shown again.
form_key	Protects visitor's data from Cross-Site Request Forgery Attacks.
guest-view	Stores the Order ID that guest shoppers use to retrieve their order status. Used in “Orders and Returns” widgets.
login_redirect	Preserves the destination page the customer was loading before being directed to log in.
mage-banners-cache-storage	Stores banner content locally to improve performance.
mage-cache-sessid	The value of this cookie triggers the cleanup of local cache storage.
mage-cache-storage	Local storage of visitor-specific content that enables ecommerce functions.
mage-cache-storage-section-invalidation	Forces local storage of specific content sections that should be invalidated.
mage-messages	Tracks error messages and other notifications that are shown to the user, such as the cookie consent message, and various error messages. The message is deleted from the cookie after it is shown to the shopper.
private_content_version	Appends a random, unique number and time to pages with customer content to prevent them from being cached on the server.
section_data_ids	Stores customer-specific information related to shopper-initiated actions such as display wish list, checkout information, etc.
user_allowed_save_cookie, cookie_consent	Stores the user's cookie consent state for the current domain.
X-Magento-Vary	Configuration setting that improves performance when using Varnish static content caching.

Cookie name	Cookie purpose
product_data_storage	Stores configuration for product data related to Recently Viewed / Compared Products.
recently_compared_product	Stores product IDs of recently compared products.
recently_compared_product_previous	Stores product IDs of previously compared products for easy navigation.
recently_viewed_product	Stores product IDs of recently viewed products for easy navigation.
recently_viewed_product_previous	Stores product IDs of recently previously viewed products for easy navigation.
_fbp	This cookie is installed by Facebook to store and track visits across websites.

Cookie name	Cookie purpose
dc_gtm_*	Throttles request rate when Google Analytics is deployed with Google Tag Manager.
_ga, _gat, _gid, _ga_, _gat_	This cookie is installed by Google Analytics. They are used to collect information about how visitors use our website. We use the information to compile reports and to help us improve the website. The cookies collect information in a way that does not directly identify anyone.