Kortelo.
EN
Use cases

Manual payment matching killing accounting

If this is you, keep reading.

The problem

Your accounting team matches bank statements to invoices by hand. Every day. The job grows linearly with revenue.

Reconciliation errors compound. Disputes with customers about "paid / not paid" eat a day per week.

Cash-visibility reports run a week behind reality. Decisions get made on stale numbers.

Your ERP vendor offers an add-on for half a million PLN and a 6-month integration. You don't have either.

What we'd build
  • 1 Automated payment matcher reading MT940 / camt.053 / CSV bank exports and reconciling against your invoices
  • 2 Fuzzy-matching engine for messy payment titles, partial payments, lumped payments, overpayments
  • 3 Exception queue for human review — every match traceable and reversible
  • 4 Daily cash-visibility dashboard with real-time DSO and outstanding A/R
  • 5 PostgreSQL data layer (battle-tested by Spotify, Reddit) for the audit trail
  • 6 Your code, your data, sits next to your ERP — no migration, no vendor lock-in
How long it takes
4–8 weeks

Pilot

Test the concept on one slice of the problem. Fixed scope. Fixed price. Working software at week 1.

3–6 months

Project

Production-ready system covering the full scope. Iterative. Weekly demos. Your repo from day 1.

12 months+

Platform

Continuous evolution. New features. Predictable monthly. No surprise license audits.

Investment

Built for SMEs, priced for SMEs.

  • ·Pilot: less than 1 Asseco consultant-week.
  • ·Project: less than what enterprise vendors charge just for needs analysis.
  • ·Platform: predictable monthly, no surprise license audits.

Free 30-min audit. Zero commitment. We'll give you actual numbers.

Outcome
01

90%+ of payments auto-matched on day 1

02

Accounting team back to analysis, not data entry

03

Cash visibility goes from weekly to real-time

Enterprise capabilities. SME pricing.