approved mappings
Applied only after an explicit approval changes a matching workflow.
Rowva product
Rowva understands the file, performs safe repairs, resolves uncertainty internally, builds business outputs, and proves what happened.
One operating loop
Input
| Date | Item | Total | Payment |
|---|---|---|---|
| 05/6/26 | Latte | €3,5 | cash |
| 2026-06-05 | LATTE | 3.50 | Cash |
| 06-05-26 | Croissant | — | blank |
| 2026/06/05 | Tea | 2,80 | card |
Active stage · Upload
10,248 rows · 14 columns · CSV
Completion preview
| Date | Item | Total | Payment |
|---|---|---|---|
| 2026-06-05 | Latte | 3.50 | cash |
| 2026-06-05 | Latte | 3.50 | cash |
| 2026-06-05 | Croissant | Rowva resolving | Rowva resolving |
| 2026-06-05 | Tea | 2.80 | card |
Business files first
JSON manifests remain available for APIs and audit. These are the files most SME teams see first.
Workflow memory
Rowva never claims it remembered something unless an approved persisted rule changed the result.
Applied only after an explicit approval changes a matching workflow.
Applied only after an explicit approval changes a matching workflow.
Applied only after an explicit approval changes a matching workflow.
Applied only after an explicit approval changes a matching workflow.
Applied only after an explicit approval changes a matching workflow.
Proof by default
Every material change stays inspectable.
Ready, partial, blocked, or unavailable with exact reasons.
Only accepted rules improve the next matching run.
Reviewer identity, worker phases, retries, and package files.
Leave with business files your team can use and proof you can inspect.