Trust Layer
Format rules that catch bad data
IBAN checksums, tax-number formats and country address rules on top of schema output. Mismatches flagged — never silently rewritten.
Packs, not one-off regex
01
Country packs
RO/TR/DE/BG formats live where your volume is — more on request.
02
Cross-field math
Totals vs rows, dates vs metadata — checked with both sides cited.
03
Honest failures
A failed check flags the value. Fieldry never edits numbers to force a match.
- 01
IBAN pack live
Mod-97 checksum plus country length and format per registry.
- 02
Tax-number pack live
RO CUI/CNP, TR VKN/TCKN, DE Steuernummer, BG EIK structures.
- 03
Address pack live
Postal code, locality and street patterns per country, matched to PoA docs.
- 04
Totals pack live
Line totals vs header totals, VAT arithmetic, currency consistency.
- 05
Date pack roadmap
Issue vs due ordering, metadata vs content dates, expiry windows.
From schema to checked data
01
Extract fills fields
Schema-constrained output arrives with per-field evidence.
02
Packs check formats
Country and math rules run automatically on matching fields.
03
Flags route with proof
Failures carry status, rule id and both cited sides to your queue.
Related use cases
IBAN mod-97 plus RO, TR, DE and BG tax and address formats at launch. Tell us your next market — packs ship with demand.
The field gets a failing status with the rule id and evidence. Your system decides: block, review or accept with note.
Never. A total that doesn't match its rows is flagged on both sides. Silent rewrites are a hallucination vector.
Yes — custom regex and cross-field rules per schema, versioned with your schema version.
Catch bad data today
IBAN, tax and address packs live.
An IBAN typo fails checksum before payout. The transfer holds with the reason attached.