EOSReconcileA worked example, static
Reconcile two exports of your purchase orders
Your ERP says one number, your AP system says another, and neither is wrong about itself. Given both exports, EOS finds where they disagree, shows the evidence for each figure, and lets a named person decide. Worked through below on two synthetic exports with fixed figures; reconciliation only reads, and nothing on this page signs in, uploads or calls a service.
A fixed example on two synthetic exports. Nothing on this page signs in, uploads or calls a service; interactive tools live in the platform.
1 · Two sources, two exports Demo · sample data, fixed
Source A · ERP purchase-order export
Four purchase orders, in USD: 4500012345 for 48,250.00; 4500012346 for 12,480.00; 4500012347 for 7,310.40; 4500012348 for 3,905.00.
Source B · AP system export
Three of the same purchase orders, in USD: 4500012345 for 48,250.00; 4500012346 for 12,980.00; 4500012347 for 7,310.45. 4500012348 has no invoice yet.
Purchase orders are matched by PO number. In this example an amount is contested only when the difference exceeds both tolerances, 0.01 and 0.5 percent; in EOS your organization declares its own.
2 · Reconcile and read Demo, computed once, shown as it came out
3 purchase orders appear in both exports. 4500012345 agrees exactly. 4500012347 differs by 0.05, under 0.5 percent, so it agrees within tolerance. 4500012346 differs by 500.00, 4.0 percent of the ERP figure and above both tolerances, so it is contested.
| Purchase order | Field | Source A | Source B | Difference |
|---|---|---|---|---|
| 4500012346 | amount | 12,480.00 USD | 12,980.00 USD | 500.00 USD4.0 percent · tolerance 0.01 and 0.5 percent |
Source AERP purchase-order export
- row
- 2
- amount
- 12,480.00 USD, observed
- order date
- 2026-08-04
Source BAP system export
- row
- 7
- amount
- 12,980.00 USD, observed
- order date
- 2026-08-04
What happens next: nothing chooses a side. Both values stay on the record with their rows, the 500.00 difference is labeled derived, and a named person with authority over purchase orders decides, through the approval the organization's policy routes.
3 · Where this runs on your data
In an assessment, the same reconciliation runs in the EOS service on your own exports, read-only, and the findings are delivered to you: request an assessment, or open the platform on its synthetic tenant.
How the two layers feed each other
Activity in the spatial layer produces records; EOS reconciles them, keeps the evidence and routes the decision; what EOS settles is meant to return to the spatial layer as a capability people can use. Each stop below states what it is today, not what it could become.
Read this literally: the two EOS stops are live in the service and tested; one spatial stop is a scaffold and one is planned. Nothing here claims a live connection between the two layers, because none is deployed.
Boundary: this page signs nobody in and calls no service; it is a fixed example. Interactive tools live in the platform at app.html.
The cash flow impact simulator: terms, MOQ and lead time, worked through on fixed figures →
Portunus: reconcile enterprise records against the physical thing itself →