BeryX · Banking and fintech
The regulatory report won't reconcile. And it's due Friday.
IBANs, tax IDs, SEPA movements and cards — data that feeds reporting to the central bank and the tax authority, and doesn't forgive a single digit. BeryX checks it before the regulator does.
Free account, no card. The demo opens with data from a Portuguese neobank.
The pain
In banking, bad data is a fine, not a bug.
Data quality is a regulatory requirement — yet it's still checked by hand, in Excel, the night before the report.
Reports that don't reconcile
Migrated accounts without a balance, 8-digit tax IDs: liquidity and CRS/FATCA reports bounce back and the team loses the week reconciling.
Customers seeing double
A reprocessed SEPA batch duplicates debits. Customers see it first — and call support, or the press.
Accidental PCI incidents
A full card number copied from a support log into an analytics table is a reportable incident. Nobody looked for it there.
Partners with their own formats
Value dates as DD/MM/YYYY, reversals with the wrong sign: the interest calculation skips movements and nobody notices.
How BeryX fixes it
Ready-made Portuguese banking rules, PII detection and an audit trail.
Financial rule pack
PT IBAN and NIF format and checksum, transaction_id uniqueness, non-negative amounts, ISO dates and masked card numbers — applied in one click.
PII and sensitive data
Automatic classification of sensitive columns (card number, IBAN, tax ID) and an alert when they show up where they shouldn't.
Read-only and auditable
BeryX only reads, using the vendor's official methods; credentials are encrypted; every scan, rule and decision lands in the audit log.
Contracts with a CI gate
ODCS contracts between data producers and consumers: a change that would break the report is stopped before it reaches production.
Proof, not mockups
BeryX running on the «PT neobank» demo workspace.
Real screenshots of the app, taken on the vertical's seed pack: fictional but plausible data, generated deterministically, with 7 planted issues — each with the backstory of the incident that caused it. The industry rule pack comes already applied, so the first scan flags exactly these issues. It's what you see when you open the demo.
What the first scan catches
7 issues, 7 stories you've seen happen.
- 01
IBANs with spaces
contas.ibanIn assisted account opening, IBANs were pasted from the PDF statement in groups of 4 — SEPA transfers to those accounts are rejected.
- 02
8-digit tax numbers
contas.nifTax numbers (NIF) typed by hand at the branch lost a digit — the tax authority's CRS/FATCA reporting rejects these holders.
- 03
Migrated accounts without a balance
contas.saldo4 accounts coming from the legacy core migration have no opening balance — the liquidity report to the Bank of Portugal doesn't reconcile.
- 04
Duplicate SEPA transactions
movimentos.transaction_idReprocessing the 12 September SEPA batch duplicated 9 transactions — customers saw the same debit twice.
- 05
Value date as DD/MM/YYYY
movimentos.data_valorA partner's clearing file arrives with the value date in Portuguese format — the daily interest calculation skips those movements.
- 06
Reversals with a negative sign
movimentos.montanteReversals were stored with a negative amount instead of type «C», breaking the D/C convention and doubling the effect on the balance.
- 07
Card number in clear text
cartoes.pan_mascaradoTwo full card numbers were copied from a support log into the table — a PCI DSS incident to report.
fictional data
Other industries
Get to the next report with your data already validated.
Open the demo with a Portuguese neobank's data and walk through the seven planted issues — or connect your own source, read-only, in minutes.