FORM & DATA ENTRY AUTOMATION
From messy submissions to controlled records.
Emails, PDFs, portal forms and spreadsheets arrive in every shape. Henswick builds the layer that extracts what matters, checks it against your rules, routes it for approval and writes it into the systems that need it, with a trace of every step.
Acme Ltd. — starting next Mon, insurance cert attached
ACME LIMITED · 03/09/26 · Cert: —
Acme Limited (UK) · 9 Mar 2026 · cert uploaded
acme ltd - FINAL v3 · 3/9 · cert?
Intake record
Merged from 2 sources · fields mapped
Audit trail · 7 events
Every extraction, check and approval is stored with the record.
Shown: a supplier onboarding submission. The same intake pattern governs customer changes, employee records, compliance forms and operational requests. Your inboxes, portals and systems stay where they are; the layer between them does the structuring.
WHAT THIS MEANS
When people are the integration between an inbox and a system.
Every team has one: a shared inbox, a folder of PDFs, a portal export, and someone who reads them and types the details into the system that needs them. It holds until volume grows, that person is away, or the same submission arrives four different ways.
PDF form
Name ACME LIMITED Date 03/09/26 Document Cert: —Web portal
Name Acme Limited (UK) Date 9 Mar 2026 Document Cert uploadedSpreadsheet
Name acme ltd - FINAL v3 Date 3/9 Document Cert?One supplier, four formats, no common structure. Until someone reconciles them by hand, no system can trust any of them.
GOVERNANCE BUILT IN
Rules decide what goes through, who signs off, and what stops.
Every workflow carries its own rules, written in your terms. These are examples of what they look like, and of the record they leave behind.
Example rules
Written in your terms
A required field or document is missing
ThenHold the record, name what is missing and tell the submitter
A sensitive detail has changed
ThenSend it to the accountable approver before anything is written
The record already exists
ThenUpdate it in place instead of creating a duplicate
A value does not match the expected format
ThenStandardize it, or flag it when it cannot be standardized
More than one department is affected
ThenSend each team the part it owns, in parallel
An approval sits unanswered
ThenRemind the approver, then escalate to their delegate
Record history
Illustrative
Received by email with two attachments.
Fields extracted and mapped: 9 of 10.
Formats standardized; 3 corrections logged.
Required document missing. Record held; submitter notified.
Document received. Checks re-run.
Sensitive change approved by Finance.
Written to 3 systems. Confirmations stored.
Every extraction, check, approval and write stays attached to the record, so the question of who did what, and when, always has an answer.
WHAT THIS CAN LOOK LIKE
Three intake workflows, each ending in more than one place.
Examples of how a submission is checked, approved and distributed across departments and systems.
Case 01
Supplier onboarding
Procurement, finance and the supplier each get what they need from one submission.
Arrives as
What the workflow does
Extract details and map them to the vendor record.
Format-check names, identifiers and dates; flag what is missing.
Procurement approves. Finance signs off too, only when payment details changed.
Anything incomplete is held with the missing item named.
Then lands in
Case 02
Customer detail changes
One change request updates every team's view of the customer.
Arrives as
What the workflow does
Match the request to the existing account, so nothing is duplicated.
Check the change against rules for names, addresses and billing details.
The account owner approves changes to legal name or billing.
Then lands in
Case 03
Regional spreadsheet submissions
Every region reports in its own template; one structure comes out.
Arrives as
What the workflow does
Map each region's columns to a single structure.
Run required-field and rule checks on every row.
Split failures off with the reason attached; release the rest.
Then lands in
WHAT CHANGES
What changes for the teams involved.
Procurement
Vendor details re-typed from whichever format arrived, then chased for missing documents.
Records arrive structured and complete, and the submitter is asked for any gaps automatically.
Finance
Payment and billing changes accepted from an inbox, with no consistent sign-off.
Sensitive changes go to the right approver, and the decision is stored on the record.
Operations
Typos and duplicate records surface weeks later, in downstream reports.
Values are format-checked and matched against existing records at the door.
Every team that submits
Each team has its own template, its own fields and its own idea of complete.
One intake structure and one set of required fields, whatever the channel or team.
Compliance and IT
Working out who entered what, and on whose say-so, after the fact.
Every extraction, check, approval and write is traceable from one record history.
Bring us the messiest submission you receive.
Send one real example, such as the email, the PDF or the spreadsheet, and where its details have to end up. We will show you how it would be structured, checked, approved and routed.
A single form filled in repeatedly on one screen may only need a ready-made form filler. Intake that spans systems, rules and approvals is custom workflow work.
What to bring
A sample submission, with anything sensitive redacted.
The systems its details have to reach.
Who reviews or approves it today, and when.