PrestaShop Accounting & Invoicing

Bank Transfer Reconciliation for PrestaShop 8 & 9

Import the bank statement, transfers find their orders on their own.

A B2B shop collects a large share of its orders by bank transfer. Every morning someone opens the online bank, reads the labels, looks for the matching order, adds the payment and changes the status so the order can be prepared. With thirty transfers a week that takes an hour, and a mistake is expensive: an order shipped without payment, or a customer reminded after paying. This module imports your bank statement, finds the order behind each transfer from its reference, order number, amount and customer name, records the payment in PrestaShop and changes the status. Anything uncertain is proposed to you with the reasons for the match, and customers whose transfer does not arrive receive a reminder with your bank details.

At a glance
  • Imports CSV statements from any bank, OFX, QFX and CAMT.053, with no duplicates when you re-import
  • Matching on order reference, order number, amount, bank fees and customer or company name
  • Native payment recorded on the order and status changed, automatically above the confidence threshold
  • Grouped transfers split across several orders, partial payments followed until settled
  • Email reminders for transfers not received in 8 languages, optional automatic cancellation
PrestaShop 8 & 9 CSV, OFX, CAMT.053 Native payment Reminders in 8 languages
  • 30-day refund
  • 12 months updates
  • 24h support
www.datafirefly.com/en/
Bank Transfer Reconciliation for PrestaShop 8 & 9
v1.0.0 · updated 2026-09-23
What it does

The short version.

01

Your bank statement as it is

For CSV files, the separator, the encoding and the header row are detected, even when the bank adds balance lines above it. Separate debit and credit columns, signed amounts and the 1 234,56 or 1,234.56 formats are recognised. OFX and QFX (1.x and 2.x) and CAMT.053 import with no setting, and CAMT batches are split into individual transfers. Re-importing a period that overlaps the previous one creates no duplicate.

02

A confidence score you can read

Each transfer is compared with the orders awaiting payment: order reference in the label, order number after CMD, Order or Bestellung, exact amount, amount less bank fees, customer or company name. Every proposal shows its score out of 100 and its reasons, for example “Order reference found, Exact amount”.

03

Automatic validation when it is safe

Above the threshold you set (90 by default) and with a clear lead over the second proposal, the payment is recorded during the import. A reference quoted with the exact amount scores 95. Everything else waits for your review: one-click validation, bulk validation, manual assignment by order reference or number.

04

PrestaShop native payment

The transfer becomes a payment of the order, with the bank reference as transaction ID and the operation date. It shows in the order, on the invoice and in your accounting exports. The status changes to the one you choose without creating a second payment, and an invoice already generated receives the payment.

05

Grouped transfers and partial payments

A B2B customer pays three orders with one transfer: if the references are in the label and the total matches, the amount is split between the orders. A transfer below the amount due is recorded as a partial payment, with an optional dedicated status and the balance due displayed.

06

Reminders that hit the right customers

Up to 5 reminders, on day 3, 7 and 14 by default, the last one being a final reminder, with your bank details, the amount due and the reference to quote in the transfer. No reminder is sent when a transfer awaiting review matches the order. Cancelling unpaid orders after a delay is available as an option, never on a partial payment.

The long version

Everything you'd want to know before you install.

A detailed look at how Bank Transfer Reconciliation for PrestaShop 8 & 9 works, why we built it the way we did, and the thinking behind the features above.

§ 01

Ticking off bank transfers, time lost every week

In B2B, the bank transfer is still the most common payment method: professional buyers pay on invoice from their company account. On the shop side, every transfer received requires the same steps: read the label, find the order, add the payment, change the status. Until that is done, the order waits. When it is done wrong, an order ships unpaid or a customer who paid gets a reminder.

§ 02

How the module finds the right order

A bank label rarely looks like the expected reference: “SEPA CREDIT TRANSFER /FROM DUPONT LTD /REF ORDER 1542”. The module searches it for the order reference, even split by spaces, for the order number after words such as Order, CMD or Bestellung, and for the name of the customer or their company. It compares the amount with the balance due of each order awaiting payment. Reference plus exact amount scores 95 and is validated automatically, and so are order number, exact amount and customer name together. An amount and a name without reference give a proposal to review.

§ 03

A payment recorded as if you had entered it

The module uses the PrestaShop native payment: the transfer appears in the Payments tab of the order, on the invoice and in accounting exports, with the bank reference as transaction ID. The status change reuses this payment instead of creating a second one, and an invoice already generated receives the payment. Orders split between carriers share one reference: they are handled as a single order, as PrestaShop does.

§ 04

Real B2B payment cases

A customer pays several orders with one transfer quoting their references: the amount is split between them. An international transfer arrives a few euros short because of fees: the bank fee tolerance still settles the order. A customer pays a deposit: the partial payment is recorded, the balance due stays visible and the order stays followed. A transfer matches nothing: you assign it by typing an order reference or number, or you ignore it.

§ 05

Reminders that do not miss

Reminders are sent by a daily cron task, at the delays you set after the order. The email states the amount due and your bank details and asks the customer to quote the reference in the transfer, which makes the next match easier. An order whose transfer is awaiting your review is not reminded, and neither are orders that are too old. You can also remind a customer in one click from the dashboard or the order page.