Skip to main content

EOSReconcileYour data, live

Reconcile two exports of your purchase orders

Your ERP says one number, your AP system says another, and neither is wrong about itself. Upload both exports; EOS finds where they disagree, shows the evidence for each figure, and lets a named person decide. Read-only toward the systems you already run: nothing here writes back, and nothing on this page is simulated.

Checking the estate API...
  1. 1Sign inidentity and organization
  2. 2Two sourcesname each system
  3. 3Ingestrows kept with provenance
  4. 4Reconcilematch, then compare
  5. 5Decidea named person, on the record
  6. 6Take it with youCSV or JSON, audited

1 · Sign in and choose your organization

2 · Two sources, two exports Choose an organization first.

Source A

Columns appear here after you choose a file. The file is read on your device; nothing leaves it until you ingest.

Source B

Columns appear here after you choose a file.

Column mapping, the same for both files

Type a column name or pick one from the file. PO numbers are compared case-insensitively without spaces; amounts accept thousands separators and decimal commas; dates in year-month-day or month/day/year order; supplier names lose case, punctuation and legal suffixes before comparison.

3 · Reconcile and read Ingest both exports first.

An amount is contested only when the difference exceeds both tolerances. Currency, order date, status and supplier are compared exactly after normalization. Purchase orders are matched by PO number.

Contested rows here follow the estate’s published closure criteria: surfaced early with provenance attached, closed only by a named decision with the correction verified back in the system of record, never by a timeout and never by silence. The criteria, and the six-beat standard they belong to, are on the Asset Passport.

4 · Take it with you Run a reconciliation first.

CSV and JSON carry every contested figure with both source values, the difference, the decision and who made it; cells that begin with a formula character are escaped. The evidence pack is one JSON file with the run, both sources and files with their hashes, every contested figure with both source rows and their provenance, each decision with actor and role, and the audit events of the run: what a reviewer needs to re-derive the result without access to this workspace. Each export is written to your organization's audit with the person who took it.

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.

Spatial layerActivity produces records People act in a realm and systems record it. The realm and its door exist; what reaches EOS today is an export a person uploads, not a live feed. Partial EOSReconcile and evidence Two exports of the same purchase orders, matched, compared against your tolerance, every contested figure kept with both source rows, their hashes and the person who ingested them. Built EOSDecide and measure A named person decides with a note, on the record, and precedent shows what this organization decided before. The optimizer prices the models you already have and records what a month actually cost. Built Spatial layerCapability returns What EOS settles is meant to come back as something people can use in the house of products. The door is open; the return path is not built. Entry

Read this literally: two stops are built and verified in a browser against the real API, one is partial, one is a door. Nothing here claims a live connection between the two layers, because none is deployed.

Boundary: sign-in needs this project's Firebase web key on the page (meta as-firebase-web-key), and every call goes to the estate API; when either is absent this page reports it and does nothing else. The demo at app.html stays a demo; this page is the first real capability.

The cash flow impact simulator: terms, MOQ and lead time, modeled on your inputs →

The Asset Passport: reconcile enterprise records against the physical thing itself →