Papyrus · Agentic ERP

Backofficesuperintelligenceharness.

A deployable AI execution platform that enables organizations to automate complex back-office operations across existing systems of record using configurable data models, durable agents, human approvals, and governed workflows.

Papyrus solution brief · 4-page PDF

Get started with commercial →

Model the business. Orchestrate the process.

Enterprise Classes

Define entities and source identities spanning subsidiaries, finance systems, documents and legacy records.

Existing systems of record

Preserve Dynamics 365, Odoo, NetSuite, mainframes and other authoritative applications; connect only the permitted operations.

Durable agents and workflows

Run multi-stage operations with checkpoints, error handling, human approval and governed writes.

Forms and integration tools

Build purpose-fit interfaces with model-aware workflows, MCP tools and scoped system connections.

Inside Papyrus / Guided interface preview

Define your Classes. Design your workflows.

A product-derived walkthrough using Papyrus’s actual Class editor field types, drawer terminology, and Workflow Designer inspection semantics. Example data is illustrative; no live environment is connected.

PPapyrusEnterprise workspace

Demonstration data

Classes / Define

Vendor Invoice

Model an invoice linked to a vendor and legal entity.

DRAFT

New class

Set the class name, field types, and record statuses.

Name

Vendor Invoice

Title field

vendor_name

Fields

Add field

Vendor name

vendor_name

Short textRequired

Legal entity

legal_entity

Link to recordRequired

Invoice total

invoice_total

NumberRequired

Source system

source_system

Short textOptional

Approval status

approval_status

Short textOptional

DraftReviewPosted

Schema migrations require governance

Create class

Illustrative sample records · Interface reconstruction from Papyrus source · Animation respects reduced-motion preferences

See it work

Your ERP stays in charge. Papyrus runs between.

Working demos on sample data. Pick a system to see what Papyrus reads and writes there, then run one invoice across two legal entities.

01 / Systems map

Reads everywhere. Writes only through approvals.

Systems of record · live routesLive demo · sample data

ERP · West entity

NetSuite

Papyrus reads: Vendors, open bills
Governed writes: Vendor bills, payments

Click a system. Each stays the system of record; Papyrus writes back only after an approval.

02 / One invoice, two entities

The routine path runs. The exception waits for a person.

Run · INV-88213 · two legal entitiesLive demo · sample data

ap@agency.gov · 09:14

Acme Supply Co.
Invoice INV-88213 for October deliveries to both campuses. INV-88213.pdf

Invoice: INV-88213
Total: $18,240.17
Lines: 3
Ship-to: 2 campuses

03 / The write back

Every post is a diff you can approve.

Action ledger · proposed writeLive demo · sample data

Proposed by the AP agent · awaiting Papyrus.Action.Approve

Create vendor bill VB-20931 in NetSuite

Field	Before	After
Vendor	Acme Supply Co.	Acme Supply Co.
Legal entity	∅	Beag Holdings East
Amount	∅	$18,240.17
Matched PO	∅	PO-7741
GL account	6100 · Supplies	6120 · Facilities supplies
Due date	∅	Nov 20, 2026

Three-way match passed. PO-7741, receipt GR-1180 and the invoice agree within $0.42. GL moved to 6120 because the PO line is facilities supplies.

Approver: Maria Chen

A-2203 Update vendor terms · NetSuite · Priya Patel prev 00000000 → 4d22dd9e
A-2204 Create receipt · Dynamics 365 · Sam Okafor prev 4d22dd9e → 71f57482

Not a rip-and-replace ERP.

Traditional ERP can remain the ledger and system of record. Papyrus handles the workflows that span entities, applications and legacy interfaces. Zapier and n8n are capable automation platforms; Papyrus emphasizes a unified business data model, durable operational state and governed multi-entity execution rather than isolated trigger chains.

Explore comparisons →