Clean values, however they arrive.
Give a field its rules once, and every value written to it follows them — typed, pasted, imported or read from a document. It is laid out as it is typed, stored in one shape, then checked: a mistyped IBAN is refused, and one read from a document is kept and flagged for a look.
Every value in the right shape
- 1
Input — typed in shape
An input mask lays out what a person types: CHE-___.___.___ fills in its own dots, an IBAN regroups in blocks of four, letters turn to capitals as they come.
- 2
Transform — stored in one shape
Steps run on every value before it is stored: trim, remove what doesn't belong, capitals, blocks, a prefix, a phone number written internationally, an amount rounded. A paste, an import and the AI end up alike.
- 3
Validation — checked, refused or flagged
Rules say what a value must be: required, a range, a length, a pattern, a valid IBAN, BIC, e-mail or card number, a condition on the row. An error refuses what someone types; a warning marks the cell.
What you get
Shape and check every value written to a field — typed, pasted, imported or read by the AI: input masks, clean-up steps and rules for IBANs, phones and more.
Presets for real identifiers
IBAN, BIC, international phone, e-mail, web address, payment card, EU VAT number, Swiss UID: one pick fills the mask, the steps and the rules. New e-mail, phone and web address fields start with theirs.
What the AI read is never lost
A value read from a document that breaks a rule is kept, never refused, and its cell is flagged beside the AI's mark — exactly where someone needs to look.
Rules that read the row
Required only when it matters — a VAT number once the country is Switzerland — or a condition across fields, like a due date that is not before the invoice date.
Try it before you save
Type a value in the field's settings to see what would be stored and which rule it breaks. A pattern that could run slowly is refused before it is saved.
AI reads each document, decides what it is and which table it belongs to, and pulls out the fields you care about — line items included. Every value stays linked to the spot on the page it came from and is checked against its field's rules, and Form view sets each document beside its fields for a quick review.
Used in
Frequently asked questions
What happens to the values already in the table?
Nothing is rewritten behind your back. The rules judge every cell at once, so a value that breaks one is flagged; the steps shape each value the next time it is written.
Can a rule block the AI or an import?
No. Only a person's edit can be refused, and only by a rule set to Error. A value read from a document, imported or brought back by an undo is always kept — its cell shows the rule it breaks.
How is this different from a transformation column?
A transformation column computes a new value from other fields each time it is read. Data quality shapes the field's own value once, when it is written — what is stored is already clean, and search, filters and exports see it that way.
