Informatt

Features

Everything between a raw file and a system-ready export

Informatt is deliberately industry-neutral. The same engine prepares lead data, customer records, membership rosters or any other tabular dataset.

Project file library

Keep a master file and every related return in one place, each labelled with its purpose so the engine knows how to treat it.

Column inspection

Automatic profiling of inferred type, fill rate and sample values before you commit to any mapping.

Matching & reconciliation

Configurable match keys across files, with deterministic rules first and confidence scoring for everything else.

Ambiguity review queue

Low-confidence matches are queued for a human decision. Nothing uncertain is merged on your behalf.

Transformation recipes

Normalize casing, formats, phone regions and postal codes; derive fields; filter rows. Recipes are saved and reusable.

Configurable export schemas

Target layouts are data, not code — so a new destination system is a configuration change, not a release.

Non-destructive versioning

Original uploads are immutable. Every processing run creates a new derived version you can trace back to its source.

International-ready

Region-aware phone, address and date handling, with no assumptions baked into the core engine.

File purposes Informatt understands

Labelling a file tells the engine how to reconcile it — without hard-coding any vendor or industry.

  • Master / source

    The authoritative record set for this project.

  • Enrichment return

    Appended data returned from an enrichment provider.

  • Email verification result

    Deliverability status returned by a verifier.

  • Address verification result

    Standardized or validated postal data.

  • Phone / compliance result

    Line type, litigator or do-not-contact flags.

  • CRM export

    A file exported from an existing system of record.

  • Other dataset

    Anything else that belongs to this project.

Export schemas out of the box

Start from a neutral schema and adapt it, or define your own column layout entirely.

  • Generic CRM import

    A neutral contact schema suitable for most systems of record.

    record_idgiven_namefamily_nameemailphone_primarystreetlocalityregionpostal_codecountry

  • Email verification submission

    Minimal payload accepted by most deliverability vendors.

    record_idemail

  • Address verification submission

    Postal fields required for standardization and validation.

    record_idstreetsecondarylocalityregionpostal_codecountry

  • Phone / compliance submission

    Phone numbers prepared for line-type and contact-permission checks.

    record_idphone_primaryphone_alternateregion

  • Custom layout

    Define your own column order, headers and formats.