Skip to content

Entrusit case study · Finance & accountingBank statement import & automatic reconciliation

Statements in, transactions categorised and matched to invoices and receipts.

Shipped Under NDAAutomationData & documentsERP
Discuss a similar project

The problem

Each morning someone downloaded statements from several banks and matched payments to invoices by eye. Card fees, salaries, loans and supplier payments all had to be booked to the right category by hand.

What we built

A finance automation module inside the ERP that reads the statement formats of major Macedonian banks, resolves who each counterparty is, classifies every transaction and matches it to open invoices, purchases and receipts.

How it works

  1. 1Statements are imported per bank through dedicated parsers.
  2. 2Counterparties are resolved and invoice references read from payment descriptions.
  3. 3A rule engine categorises transactions; it suggests new rules from repeated corrections.
  4. 4Payments are matched and settled against invoices, with locks so nothing is settled twice.

Highlights

  • Learns categories from the team's own corrections
  • Settlement locks prevent double-booking
  • Location-level rules for multi-site businesses

Stack & integrations

  • Laravel
  • MT940 statement parsers
  • Rule engine
  • MySQL

Project 06 of 16

Want something like this?

Tell us about your version. The first 30-minute process teardown is free, and we'll sign an NDA before it.