Retypd, Inc. — The AI company for the work between systems.

Talk to us
§ 01The Retypd platform

Read it. Do it. Run it. Prove it.

The Retypd platform covers the whole of the work between systems — reading the documents that start it, operating the applications that hold it, orchestrating the people and agents who move it, and answering for every step.

Talk to usSee it end to end
01Retypd ExtractUnstructured data
02AutofilComputer agents
03Retypd OrchestrateWorkflow engine
04Retypd GovernancePolicy, approvals & evidence
05Retypd InsightsOperations analytics
06Retypd ConnectConnectors & credentials
§ 01.1Architecture

Three layers. One record of everything.

Every component shares one policy model, one identity model and one evidence ledger — so a document read by Extract, keyed by Autofil and approved in Orchestrate is a single, auditable story.

123Work layerExtract · Autofil · OrchestrateControl layerGovernance · InsightsConnection layerConnect → SAP · Epic · 3270
  1. 1Work layer — Extract · Autofil · Orchestrate
  2. 2Control layer — Governance · Insights
  3. 3Connection layer — Connect → SAP · Epic · 3270
Fig. 1.1 The Retypd platform, exploded. Actions flow down; evidence flows up.
  1. 1

    Work layer

    Reads the documents, operates the applications and moves the process along.

  2. 2

    Control layer

    Decides what may happen, records what did, and measures what it was worth.

  3. 3

    Connection layer

    Reaches your systems through APIs where they exist and screens where they don’t.

§ 01.2Retypd Extract

Every document, read and sourced.

Reads invoices, claims, emails and scans, and returns structured fields with a source for every value.

Source · INV-48210.pdf

HALVORSEN FREIGHT AS
Strandkaien 14 · 5013 Bergen · Norway

INVOICE  INV-48210
Issued 2026-10-15   Due 2026-11-14
Your order  PO 4500018842

Container haulage BGO–OSL     41,800.00
Fuel surcharge                 4,410.00
Port handling                  2,000.00
TOTAL DUE  USD                48,210.00

Pay to  NO93 8601 1117 0442

Extracted · 6 of 14 fields

FieldValueConf.Source
1 SupplierHalvorsen Freight AS99.6%p1 · L1
2 Invoice no.INV-4821099.9%p1 · L4
3 Due date2026-11-1498.1%p1 · L5
4 Purchase order450001884299.2%p1 · L6
5 AmountUSD 48,210.0099.8%p1 · L11
6 Bank account•••• 0442Differs from vendor master97.4%p1 · L13
Fig. 1.2 Every value carries a confidence score and the line it came from. Illustrative.
  • Any format: PDFs, scans, email bodies, spreadsheets and handwriting.
  • A confidence score and a source citation for every field.
  • Validation against your master data before anything moves.
  • Low-confidence fields go to a person — never guessed.
  • New layouts learned from a handful of examples, not templates.
§ 01.3AutofilInside Autofil

Show it once. It’s handled for good.

Learns a task from one demonstration and operates any application — browser, desktop, Citrix or green screen.

  1. 01 · Record

    A process owner does the task once.

    Every screen, keystroke and spoken rule is captured — in the applications your people already use.

  2. 02 · Playbook

    Autofil writes it down in plain language.

    Steps, checks and exceptions the business can read, test and sign before anything runs.

  3. 03 · Run

    Agents operate the same screens.

    Browser, desktop, Citrix and 3270 — under Retypd Governance, at 5 levels of earned autonomy.

§ 01.4Retypd Orchestrate

Agents, APIs and people. One process.

Runs end-to-end processes across agents, APIs and people, with queues, service levels, retries and human tasks.

Workflow AP-12 · Invoice to payment · v3

  1. 01TriggerInvoice arrives in ap@Connect
  2. 02ReadFields read and sourcedExtract
  3. 03RuleThree-way matchOrchestrate
  4. 04AgentKeyed in SAP MIROAutofil
  5. 05ApprovalController, if over $50kGovernanceSLA 4 h
  6. 06CloseRemittance to supplierConnect

Exceptions at any step → human task · queue “AP exceptions” · SLA 1 business day · escalates to AP lead

Fig. 1.4 One workflow, three kinds of worker. Illustrative.
  • Triggers from email, SFTP, APIs, schedules and system events.
  • Business rules, branching and parallel steps — versioned like code.
  • Human tasks with queues, service levels and escalation.
  • Retries, timeouts and exception queues, so nothing fails silently.
§ 01.5Retypd Governance

Rules you write once. Evidence you never chase.

Policy-as-code, approvals and five levels of earned autonomy, with tamper-evident evidence for every action.

policies/ap-12.yaml

policy: AP-12
applies_to: invoice.posting
autonomy: level_4
rules:
  - when: amount > 50000
    require: approval(role: controller)
  - when: vendor.bank_details.changed
    action: hold
  - never: release_payment
evidence: field_level

Evidence record · run 7f3a-21

ActionPost INV-48210 in SAP MIRO
PolicyAP-12 v3 · VND-3
Checks14 fields read back · 3-way match ok
HeldBank details changed → reviewed 09:31
Sealedsha256 · 9c41…e07b
Fig. 1.5 The policy an agent ran under, and the record it left. Illustrative.
  • Policy-as-code: write a rule once; every agent and workflow obeys it.
  • Approvals and segregation of duties — enforced, not suggested.
  • 5 autonomy levels, promoted only on evidence you define.
  • A tamper-evident, field-level evidence ledger you can search and export.
  • SSO, role-based access and model-risk documentation for your second line.
§ 01.6Retypd Insights

Every claim, measured against your baseline.

Shows where the hours go, what agents returned and where exceptions cluster, measured against your own baseline.

WorkflowVolume · 30 daysStraight-throughHandle timeExceptions
Invoice posting12,48091%6m 10s → 40s4.2%
Credit notes1,92086%7m 05s → 58s5.6%
Vendor master changes64058%18m → 5m 20s11.0%
Fig. 1.6 Accounts payable, measured against the baseline taken before the first agent ran. Illustrative data.
  • A baseline taken before the first agent runs, so every result is measured.
  • Hours returned, cost per transaction and service levels, by workflow.
  • Exception clustering that shows which rule, field or system causes rework.
  • Exports to Snowflake, Databricks and Power BI.
§ 01.7Retypd Connect

Your systems as they are. No integration project.

Pre-built connectors, event triggers and a credentials vault, so agents reach your systems without an integration project.

  • SAP S/4HANA
  • SAP ECC
  • Oracle EBS
  • Workday
  • Salesforce
  • ServiceNow
  • Guidewire
  • Duck Creek
  • Epic
  • Oracle Health
  • Temenos
  • FIS
  • Microsoft 365
  • Gmail
  • SharePoint
  • Box
  • SFTP
  • REST & GraphQL
  • IBM 3270
  • Citrix

Through the API where one exists; through the screen, with Autofil, where it doesn’t. Trademarks belong to their owners.

  • Event triggers from inboxes, queues, webhooks and file drops.
  • A credentials vault: agents use secrets but never see them.
  • Runs in your cloud (VPC) or on-premises.
  • Nothing leaves your environment without a policy that allows it.
§ 01.8End to end

One invoice. Six components.

What thirty minutes of accounts payable looks like when the platform does the work — and keeps the record.

  1. 09:02:11ConnectInvoice email arrives in ap@; workflow AP-12 starts.
  2. 09:02:14ExtractFourteen fields read from INV-48210.pdf, each with a source. Bank account flagged.
  3. 09:02:15GovernancePolicy VND-3: bank details differ from the vendor master — hold for review.
  4. 09:31:40OrchestrateTask routed to the vendor-master team and resolved inside its service level.
  5. 09:32:05AutofilInvoice keyed in SAP MIRO; every field read back before posting.
  6. 09:32:06GovernancePolicy AP-12: under $50,000, posted at Level 4. Evidence sealed.
  7. 09:32:06InsightsThirty minutes end to end, one exception — attributed to the vendor master.
§ —Next step

Start with one workflow. Keep the platform.

Design partners start with a single process and the components it needs. Everything after that runs on the same policies, evidence and connections.

Talk to usThe design partner programme