Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Business Process Modeler
- Source records
- Execution provider
- Evidence store
Business Process Modeler organizes process revisions around a named model, its ordered nodes and a simulation scenario. A Process Owner sets the purpose of the model and assigns its owner.
Process models in one list
| Number | Name | Revision | Definition | Simulation date | Status | |
|---|---|---|---|---|---|---|
| PM-83529 | Supplier onboarding, revision 3 | 340 | Month end invoice surge | 26 Oct | Validated | |
| PM-43951 | Invoice approval, revision 5 | 400 | Refund backlog recovery | 22 Oct | Validated | |
| PM-20729 | Customer refund review, revision 2 | 500 | Reduced reviewer capacity | 28 Oct | Validated | |
| PM-64546 | Service request triage, revision 4 | 40 | Refund backlog recovery | 16 Oct | Validated | |
| PM-41369 | Purchase order release, revision 6 | 120 | Automated approval expansion | 31 Oct | Validated |
Independent Reviewer decides on the validated revision.
Every feature works on the same records. Pick one to see the screen your team works in.
Own each process revision from draft through review and publication.
Process models
| Number | Name | Revision | Cycle minutes | Completed at | Status | |
|---|---|---|---|---|---|---|
| PM-45196 | Supplier onboarding, revision 3 | 580 | 45 | Published | ||
| PM-49205 | Invoice approval, revision 5 | 70 | 20 | Published | ||
| PM-95939 | Customer refund review, revision 2 | 920 | 85 | Published | ||
| PM-64055 | Service request triage, revision 4 | 500 | 110 | Published | ||
| PM-49798 | Purchase order release, revision 6 | 600 | 15 | Published |
Map ordered work, source references and observed outcomes within a model.
Process nodes
| Id | Parent | Sequence | Description | Outcome | Source reference | |
|---|---|---|---|---|---|---|
| ACTION-2026-041 | Service request triage, revision 4 | 40 | Check invoice against purchase order | Pending | POL-INV-2026-04 | |
| RUN-2026-042 | Employee access request, revision 2 | 40 | Route high value cases to finance | Accepted | PROC-SUP-REV3 | |
| ATTEMPT-2026-043 | Service request triage, revision 4 | 90 | Notify supplier of missing documents | Pending | POL-REF-2026-02 | |
| EVID-2026-044 | Purchase order release, revision 6 | 90 | Pause refund for fraud review | Accepted | PROC-SVC-REV4 | |
| NODE-2026-045 | Purchase order release, revision 6 | 30 | Escalate aged service requests | Pending | CTRL-PO-2026-06 |
Keep effective assumptions and source mappings with the modeled revision.
Process models
| Number | Name | Revision | Status | Owner | Simulation date | |
|---|---|---|---|---|---|---|
| PM-77470 | Supplier onboarding, revision 3 | 370 | Draft | Helen Park | 04 Nov | |
| PM-42882 | Invoice approval, revision 5 | 260 | Validated | Adele Mensah | 24 Oct | |
| PM-72903 | Customer refund review, revision 2 | 230 | Simulated | Adele Mensah | 22 Oct | |
| PM-74852 | Service request triage, revision 4 | 580 | Reviewed | Marta Silva | 23 Oct | |
| PM-70530 | Purchase order release, revision 6 | 20 | Published | Helen Park | 04 Nov |
Check a revision and keep the independent decision with its evidence.
Approval conditions
| Id | Source | Source revision | Reviewer | Decision | Evidence reference | |
|---|---|---|---|---|---|---|
| ACTION-2026-041 | Purchase order release, revision 6 | 790 | Samuel Okoye | Pending | EVID-2026-101 | |
| RUN-2026-042 | Supplier onboarding, revision 3 | 800 | Yusuf Farid | Pending | EVID-2026-102 | |
| ATTEMPT-2026-043 | Contract renewal review, revision 3 | 690 | Yusuf Farid | Pending | EVID-2026-103 | |
| EVID-2026-044 | Contract renewal review, revision 3 | 150 | Nico Weber | Pending | EVID-2026-104 | |
| NODE-2026-045 | Employee access request, revision 2 | 730 | Yusuf Farid | Pending | EVID-2026-105 |
Trace a reviewed simulation through its durable run and step results.
Operation runs
| Id | Source | Operation key | Source revision | Status | Failure reason | |
|---|---|---|---|---|---|---|
| ACTION-2026-041 | Invoice approval, revision 5 | invoice-sim-20261012-01 | 810 | Reconciliation required | Decision node has no default route | |
| RUN-2026-042 | Customer refund review, revision 2 | supplier-sim-20261012-02 | 510 | Reconciliation required | Input schema omits approval amount | |
| ATTEMPT-2026-043 | Incident escalation, revision 1 | refund-sim-20261013-01 | 380 | Reconciliation required | Retry limit exceeded at handoff | |
| EVID-2026-044 | Contract renewal review, revision 3 | service-sim-20261013-02 | 100 | Reconciliation required | Referenced policy is inactive | |
| NODE-2026-045 | Incident escalation, revision 1 | access-sim-20261014-01 | 20 | Reconciliation required | Simulation arrival rate is missing |
Verify receipts, assign follow-ups and preserve superseded execution.
Evidence documents
| Id | Source | Title | Attachment | Document date | Verified | |
|---|---|---|---|---|---|---|
| ACTION-2026-041 | Contract renewal review, revision 3 | Invoice approval policy, October 2026 | invoice-approval-policy.pdf | 02 Nov | No | |
| RUN-2026-042 | Incident escalation, revision 1 | Supplier onboarding workflow map | supplier-onboarding-map.pdf | 15 Oct | No | |
| ATTEMPT-2026-043 | Invoice approval, revision 5 | Refund exception review notes | refund-review-notes.pdf | 18 Oct | No | |
| EVID-2026-044 | Service request triage, revision 4 | Service queue timing sample | service-queue-sample.csv | 19 Oct | No | |
| NODE-2026-045 | Contract renewal review, revision 3 | Purchase order control checklist | purchase-order-controls.pdf | 14 Oct | No |
Model revision to verified simulation ships ready to use. 2 steps need a named approval before the work moves on: Review validation (Independent Reviewer) and Verify outcome (Independent Reviewer).
Choose the effective assumptions and policy basis for the model.
Record ordered nodes and the source behind each observation.
Check the exact revision and keep its operation trace.
Examine the trace and record an independent decision.
Execute the reviewed revision and retain step results.
Confirm the receipt and the effect before accepting success.
Open any process model to see its evidence documents, the roles that work on it, its process stages and its approvals on one page.
Revision, Definition and Simulation date.
Each line is linked to this process model.
Admin, Process Owner and Model Designer, each with their own permissions.
Validate revision and Review model, with the role that acts.
Review validation and Verify outcome, with who decides.
Month end invoice surge · Validated
| Id | Source | Title |
|---|---|---|
| ACTION-2026-041 | Contract renewal review, revision 3 | Invoice approval policy, October 2026 |
| RUN-2026-042 | Incident escalation, revision 1 | Supplier onboarding workflow map |
| ATTEMPT-2026-043 | Invoice approval, revision 5 | Refund exception review notes |
Signed in as Independent Reviewer
| Decision | Approver | |
|---|---|---|
| Review validationExamine the trace and record an independent decision. | Independent Reviewer | |
| Verify outcomeConfirm the receipt and the effect before accepting success. | Independent Reviewer |
Everyone opens Business Process Modeler to the work that is theirs. Pick a role to see what it starts with.
Sets organization access and oversees configuration.
Owns a model revision and decides when it is ready for validation.
This is the first screen this role sees.
Follow-up actions · Process Owner
Maps process nodes and maintains scenario-linked model details.
This is the first screen this role sees.
Process models · Model Designer
Runs reviewed revisions and examines the operation trace.
This is the first screen this role sees.
Operation runs · Simulation Operator
Reviews a specific revision and its recorded evidence.
This is the first screen this role sees.
Operation runs · Independent Reviewer
Checks external receipts and resolves assigned verification work.
This is the first screen this role sees.
Follow-up actions · Evidence Steward
Read model changes, run results and verification work together.
This quarter
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 40 | ||
| Validated | 27 | 68% | |
| Simulated | 13 | 48% | |
| Reviewed | 7 | 54% |
Sample totals per stage
Compare cycle minutes by model, organization and revision.
Group process nodes by parent model, sequence and outcome.
Show models grouped by their linked scenario and organization.
Compare review decisions, deciding people and dates by model revision.
Compare run status, result reference and completion date by model revision.
List operation steps and external receipt evidence beneath each run.
Show open follow-ups by assignee, due date and source model.
Compare failed or unknown attempts by operation key and failure reason.
See how Business Process Modeler fits your kind of team.
Each stage of model revision to verified simulation names the role that acts and the status it records, so a change is never anonymous.
Each stage, the role that acts and the status it records
Use Proto to prepare model work and inspect the recorded handoffs.
Set up connections through ERP.AI and Proto workflows, with every change logged.
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 14 tablesStart with one team and one process, then add the rest once the basics are running.
Choose one operating organization, Process Owner and Model Designer. Define the model’s purpose and source references.
Create the scenario, effective dates, policy reference and any source mappings needed for the pilot.
Record the ordered nodes, validate a draft revision and inspect the run and pending review decision.
Have an Independent Reviewer decide on the exact revision. Run the reviewed model and verify each external effect and receipt.
Keep an executed revision, record a compensating step and assign the verification follow-up before expanding the scope.
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
Click Get started, then use Proto to configure Business Process Modeler for your business. Begin with one process, one scenario and a revision your team can validate and review.
A model names the work, owner, organization, scenario and revision. Its linked nodes hold the ordered observations.
A scenario carries an organization, effective dates and policy reference. A run records the revision used with its assumption basis.
The Process Owner prepares it for validation. The Independent Reviewer records a decision against the exact revision before simulation proceeds.
The workflow records a durable run and step trace, marks the model Validated and raises a pending independent review decision.
Open the run, its numbered steps, result reference and external receipt evidence. Compare it with the source model revision and linked scenario.
Investigate the attempt and provider reference. The team can keep a run for reconciliation until its effect is understood.
Yes. The correction flow retains the earlier revision, records a correction run and compensating step, creates a successor and assigns verification work.
Check the revision, scenario, node outcomes, simulation result, receipt evidence and independent decision. Keep the prior history available for later comparison.
Start free, then use Proto to change fields, steps and approvals before your team goes live.