Community

The bit that only gets better with people.

beatrax ships with a community corpus: a shared, human-curated set of patterns that turn cryptic statement descriptors into names you recognise. It is the one part of the product that improves because someone contributed, not because someone shipped a release.

The problem it solves

A bank statement does not say "Albert Heijn". It says something closer to a till number, a city, a payment-terminal identifier and an abbreviation, jammed together. Multiply that by every shop, utility, tax office and subscription you deal with, and a fresh ledger is a wall of noise.

beatrax already learns from what you correct — label a counterparty once and every transaction sharing that IBAN follows. The corpus is the head start: a shared body of knowledge so the first import already knows what most of those descriptors mean.

What's in it

Merchants

Statement descriptors mapped to a friendly name and a sensible default category — supermarkets, transport, utilities, streaming, the everyday names.

Government bodies

Tax offices, municipalities and agencies, which are the descriptors people most often cannot decode at all.

Bank fees

The fee and charge lines banks give their own opaque names, recognised so they land in the right category.

Support resources

Where to turn for help with money trouble, kept per country rather than assuming everyone is in the same place.

How it reaches you

  • It ships with the app — The corpus is bundled. There is no lookup service, no phone-home, and no request leaves your machine to classify a transaction — matching happens locally against data you already have.
  • Your own corrections always win — The corpus seeds a global tier. Anything you set yourself sits above it, so a shared pattern can never overwrite a name you chose.
  • Patterns, not personal data — An entry is a public descriptor fragment and a public business name. Nobody's transactions are in it — there is nothing personal to contribute even by accident.

How to contribute

When beatrax meets a merchant it cannot name, the transaction detail offers to suggest a mapping. Filling that in opens a pre-filled pull request in your browser against the product repository — you review it, you submit it, and nothing is sent anywhere until you do.

You can also edit the corpus files directly. They are plain YAML, one file per country, and an entry is a single line.

  • From inside the app — Suggest a mapping on any unrecognised counterparty; beatrax composes the change and opens the draft for you.
  • From the repository — Edit resources/corpus/merchants/<country>.yaml and open a pull request. Pattern, name, and optionally a category.
  • A country that isn't listed — Add the file. A new country corpus needs no code change — the loader picks it up from the filename.

Where the coverage is today

Below is the current state, read from the repository when this page was built. Countries with a small count are not broken — they are simply where the least work has been done, which makes them the easiest places to make a visible difference.

32countries with a corpus
609merchant patterns
81government patterns
CountryMerchantsGovernmentBank fees
GBUnited Kingdom487
USUnited States453
EUEurope-wide36
CACanada342
DEGermany3344
NLNetherlands3382
FRFrance3264
BEBelgium272
ESSpain273
ITItaly263
ATAustria213
UAUkraine182
IEIreland154
PLPoland152
CZCzechia142
HUHungary141
FIFinland132
RORomania132
SESweden133
HRCroatia122
DKDenmark122
PTPortugal121
SKSlovakia122
BGBulgaria111
SISlovenia113
EEEstonia102
GRGreece102
LTLithuania102
CYCyprus9
LVLatvia91
MTMalta82
LULuxembourg62

Counts are pattern totals, not a quality score. A small number is an invitation to contribute, not a warning — and the country list is read from the repository when this page is built, so a corpus somebody adds appears here on the next rebuild.