All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Data Entry & Validation · Available now

Review each imported revision before it reaches its target.

Data Entry & Validation organizes imported submissions as batches tied to an organization, owner and validation schema. Operators can record the source identity, revision and row counts, then inspect row-level outcomes and failed fields.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewIncoming Batches
Data Entry & Validation · Import batches

Incoming Batches

Import batches in one list

New import batch
Import batches in view
6
Uploaded
3
Parsed
3
Uploaded3
October supplier invoicesWillow Finch Retail
13 Oct
Q4 product catalog refreshWillow Finch Retail
17 Oct
October payroll adjustmentsPine Lantern Wholesale
20 Oct
Add
Parsed3
September customer updatesMeadow Stone Services
22 Oct
Weekly shipment receiptsNorth Vale Foods
14 Oct
Vendor address correctionsMeadow Stone Services
28 Oct
Add
October supplier invoicesImport batches · IB-35785
Uploaded
Imported date13 Oct
OrganizationWillow Finch Retail
OwnerRavi Desai
DefinitionProduct catalog rules v5
Approve revisionIB-35785 · October supplier invoices

The Independent Reviewer approves, returns or rejects the source revision.

Waiting for Independent Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
14
Saved views
12
Roles with set permissions
6
Reports and dashboards
8
Features

Follow each batch from intake to decision

Every feature works on the same records. Pick one to see the screen your team works in.

Batch intake

Place each submission under a named owner and a frozen definition.

  • Batch identity
  • Source version
  • Supporting material
  • Import batches
  • Organizations
  • People
  • Validation schemas
  • Evidence documents
Explore batch intake
OverviewValidation Queue
Data Entry & Validation · Batch intake

Validation Queue

Validation waits for the import operator

New
NumberNameImported dateStatusDefinitionRow count
IB-83870October supplier invoices15 OctParsedPayroll adjustment rules v24
IB-22601September customer updates02 NovParsedSupplier invoice rules v333
IB-64140Q4 product catalog refresh20 OctParsedVendor address rules v313
IB-27755Weekly shipment receipts22 OctParsedProduct catalog rules v517
IB-17546October payroll adjustments28 OctParsedSupplier invoice rules v331
6 of 6 records
October supplier invoicesImport batches · IB-83870
Parsed
Imported date15 Oct
DefinitionPayroll adjustment rules v2
Row count4
Error count18
Example screen with sample data
Process

Move accepted rows with a clear handoff

Imported batch to reviewed commit ships ready to use. One step needs a named approval before the work moves on: Approve revision (Independent Reviewer).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Stage batch

    Identify the sender, owner and definition for the source revision.

    October supplier invoicesIB-35785 · Import Operator
    Stage batchBy Import Operator
  2. Apply rules

    Check incoming rows against the chosen definition and mappings.

    October supplier invoicesIB-35785 · Import Operator
    Apply rulesBy Import Operator
  3. Inspect exceptions

    Review rejected rows by source identifier and failed field.

    October supplier invoicesIB-35785 · Validation Steward
    Inspect exceptionsBy Validation Steward
  4. Approve revision

    The Independent Reviewer decides the exact revision.

    October supplier invoicesIB-35785 · Independent Reviewer
    Approve revisionBy Independent Reviewer
    ApprovalThe Independent Reviewer approves, returns or rejects the source revision.
  5. Commit accepted rows

    Carry the approved partition to the receiving target with an execution trace.

    October supplier invoicesIB-35785 · Execution Operator
    Commit accepted rowsBy Execution Operator
  6. Verify outcome

    Compare the receipt, target reference and any correction evidence.

    October supplier invoicesIB-35785 · Independent Reviewer
    Verify outcomeBy Independent Reviewer
Inside a record

Connect the source and receiving target

Open any import batch to see its execution attempts, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Imported date, Organization, Owner and Definition.

  2. 2
    Execution attempts

    Each line is linked to this import batch.

  3. 3
    Who works on it

    Admin, Import Operator and Validation Steward, each with their own permissions.

  4. 4
    Process stages

    Every status change, in order.

  5. 5
    Approvals

    Approve revision, with who decides.

Incoming BatchesOctober supplier invoices
Data Entry & Validation · Import batches

October supplier invoices

Willow Finch Retail · Uploaded

Log activity
1
Record details
Imported date13 Oct
OrganizationWillow Finch Retail
OwnerRavi Desai
DefinitionProduct catalog rules v5
2
Execution attempts

October supplier invoices

SourceOperation keyAttempt number
Weekly shipment receiptsimport-invoices-oct15810
Regional price list updatevalidate-contacts-sep260
Q4 product catalog refreshcommit-catalog-q4810
Execution attempts
6
Total attempt number
3,910
3

Who works on it

  • AdminManage Organizations, People, validation schemas, source…
  • Import OperatorManage import batches, validation results, evidence documents
  • Validation StewardManage validation schemas, source mappings
5

Approvals

  • Approve revisionIndependent Reviewer
    Approved
Example screen with sample data
Approvals

Review the exact source revision

The Import Operator prepares a revision; the Independent Reviewer makes its decision.

OverviewApprovals
Data Entry & Validation · Overview

Approvals

Signed in as Independent Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • IB-83870October supplier invoices
    Payroll adjustment rules v2Requested by Admin
    Parsed1dActions
  • IB-22601September customer updates
    Supplier invoice rules v3Requested by Admin
    Parsed3dActions
  • IB-64140Q4 product catalog refresh
    Vendor address rules v3Requested by Admin
    Parsed4dActions
  • IB-27755Weekly shipment receipts
    Product catalog rules v5Requested by Admin
    Parsed4dActions

Who approves what

DecisionApprover
Approve revisionThe Independent Reviewer decides the exact revision.Independent Reviewer
Approve review decisionsIndependent Reviewer
2 approval rules · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens Data Entry & Validation to the work that is theirs. Pick a role to see what it starts with.

Admin

Configures organizations, people, validation definitions and access for the import process.

  • Manage Organizations, People, validation schemas, source mappings, Users
  • View import batches, validation results, operation runs, operation steps, review decisions
Reports

See where imports need attention

Review import quality, decisions and execution outcomes.

Overview
Data Entry & Validation · Overview

Data Entry & Validation dashboard

This quarter

Follow-up actions in view
6
Open
3
In progress
3
Due date within 14 days
4

Import batches by status

How far records got this quarter

StageReachedStep
Uploaded28
Parsed1657%
Validated850%
Reviewed563%

Number of import batches by status

Sample counts per stage

200
20Uploaded
20Parsed
20Validated
20Reviewed
20Committed
Example screen with sample data
  1. 01Import volume by organization

    Group batches by organization and imported date to see source load.

  2. 02Validation outcome by rule

    Group results by rule, outcome and severity to locate recurring failures.

  3. 03Batch error review

    Compare each batch's row, accepted and error counts.

  4. 04Reviewer decisions by revision

    Show the decision, reviewer and date for each source revision.

  5. 05Execution outcomes

    Group runs and attempts by status to find failed or uncertain operations.

  6. 06Follow up workload

    Show assigned actions, due dates, statuses and resolutions.

  7. 07Receipt coverage

    Identify operation steps with receipt references and attached evidence.

  8. 08Transition history

    Show batch status changes, actors, revisions and reasons.

Controls

Keep decisions and receipts together

Each stage of imported batch to reviewed commit names the role that acts and the status it records, so a change is never anonymous.

OverviewImported batch to reviewed commit
Data Entry & Validation · Process

Imported batch to reviewed commit

Each stage, the role that acts and the status it records

Process stages
10
Approval steps
1
Roles involved
5
Tables touched
1
Apply rules
Import Operator
StatusUploaded → Parsed
Confirm result
Import Operator
StatusParsed → Validated
Approve revisionApproval
Independent Reviewer
StatusValidated → Reviewed
Imported batch to reviewed commit
  1. Start
    Apply rulesUploaded → Parsed
    Import Operator
  2. Step
    Confirm resultParsed → Validated
    Import Operator
  3. Approval
    Approve revisionValidated → Reviewed
    Independent Reviewer
  4. Step
    Commit accepted rowsReviewed → Committed
    Execution Operator
Example screen with sample data
AI agent

Ask for the evidence behind an outcome

Give your team a clear way to inspect an import and its decision trail.

It can

  • Import Operator: Show batches assigned to a selected owner and rejected results for a selected source revision.
  • Validation Steward: Compare failed fields and rules across recent batch results.
  • Independent Reviewer: Gather the decision record, source revision and supporting evidence for review.
  • Execution Operator: Inspect an uncertain attempt, its run steps and any receipt reference.

Stays with a person

  • A person must decide whether a revision is approved, returned or rejected.
  • The execution operator must reconcile an uncertain provider result against the target before another commit.
  • Keep the decision and verification evidence with the relevant records.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Data Entry & Validation
  • Source feed
  • Receiving target
  • Receipt source
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 14 tables
14tables
  • Batch intake5
  • Rules and mappings4
  • Validation review4
  • Independent decisions5
  • Commit trace5
  • Correction evidence6
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Define the source

    Register the organization, people, batch owner and incoming row identifiers.

  2. Agree on rules

    Set the validation definition, effective dates, source mappings and target field meanings.

  3. Rehearse review

    Process a sample batch with accepted and rejected rows, then record a returned and an approved decision against exact revisions.

  4. Check execution

    Compare operation steps and attempt references with the receiving target and its receipt.

  5. Practice correction

    Assign a follow up, preserve the prior run and review a successor revision.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Data Entry & Validation.

All questions
How do I get started?

Click Get started, then use Proto to configure Data Entry & Validation for your business. Begin with one organization, one validation definition and a sample batch that includes a rejected row.

What identifies an import?

A batch has a number, owner, organization and definition. Its source hash and revision help the team distinguish a corrected submission from an earlier version.

How are errors reviewed?

Open rejected row results and check the source record identifier, failed field, rule, severity and failure reason before correcting the source.

Who approves a batch?

The Independent Reviewer records a decision for the exact source revision, including a reason when the batch is returned or rejected.

What happens after approval?

The Execution Operator handles the accepted partition and retains run, step, attempt and receipt evidence against the target reference.

How do we avoid a duplicate commit?

Check an unknown attempt against its operation key, provider reference and receipt before another attempt is made.

Can we correct a completed import?

Use a successor revision and a follow up that keeps the earlier decision, run and receipt visible for verification.

Where do source documents go?

Attach them to evidence documents for the related batch and record who verified them.

What can we report on?

Review batch volume, validation outcomes, reviewer decisions, execution states, follow up work and transition history from the corresponding records.

Set up Data Entry & Validation your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appData Entry & Validation

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.