Documentation / first reconciliation

From first sign-in to a defensible asset review. Step by step.

A practical starting path for ITAM administrators: prepare a clean CSV, preserve its source context, confirm the mappings that need a human eye, and follow the evidence into your first reconciled asset.

first reconciliation
01sign in + organization
02upload CSV + set context
03infer + confirm mappings
04commit + inspect evidence
→ every value keeps its source trail

Before you begin

Bring the right context to the first pass.

The first run is easiest to interpret when access, file structure, and evidence origin are settled before you click Transfer.

A short checklist

  • Sign in with the account that should own or administer the organization.
  • Have a CSV export ready with headers in the first row and one asset per row.
  • Know which Source each file represents and, if useful, its Location or Location Group.

first pass / operator map

Static guide
  1. 01AccessSign in · organization
  2. 02EvidenceCSV · Source · Scope
  3. 03ReconcileInfer · confirm · commit
  4. 04ReviewConfidence · provenance

The workflow

Follow the ingest rail in order.

Each handoff keeps the evidence attached to the decision that created it. If a step needs attention, fix it before moving to the next one.

  1. 01

    Step 01

    Sign in and confirm organization access

    Open the sign-in page, then make sure your account is connected to the correct AssetSentinel organization. If you have just joined, finish the organization onboarding prompt before starting an ingest run.

    Open sign in
  2. 02

    Step 02

    Prepare one or more CSV exports

    Use CSV files with the first row as headers and one asset per row. Keep each file tied to one evidence origin so its rows can be traced back after reconciliation.

    View source files
  3. 03

    Step 03

    Assign Source and optional Scope per file

    In the ingest uploader, choose the Source for each file. Add a Location or Location Group as Scope when it helps describe where that export applies. Source and Scope are recorded per file, not broadcast across the batch.

    Review ingest settings
  4. 04

    Step 04

    Transfer and infer mappings

    Select Transfer & infer mappings to move the files into the review step. AssetSentinel proposes how source columns map to canonical asset fields and keeps the file context attached to those suggestions.

    Open ingest
  5. 05

    Step 05

    Confirm low-confidence mappings

    Review every mapping that needs confirmation. Suggestions below 70% confidence require an explicit confirmation before the run can continue; correct the target field or exclude the row when the suggestion is not appropriate.

    Review mappings
  6. 06

    Step 06

    Commit observations

    When the mapping review is complete, choose Commit observations. The committed observations become the evidence behind the merged asset view, while conflicts and rejected rows remain visible for follow-up.

    Run an ingest

After commit

Read the ingest summary before you move on.

The result step is the handoff between an upload run and the inventory. Treat the counts as a diagnostic, not just a success message.

result handoff

Committed does not mean unexplained.

Use the summary to decide whether to inspect the inventory, revisit a source file, or resolve a conflict before trusting the next decision.

Committed

Observations accepted into the reconciled asset view.

Quarantined

Rows or identifier clusters held aside because source integrity needs attention.

Excluded

Rows intentionally left out during mapping review.

Conflicts

Cross-source differences that may need an operator decision.

Rejected

Rows that could not be committed and need correction in the source or mapping.

Check the per-file outcome when a batch is partial.Treat conflicts and rejected rows as follow-up work.

Your first asset review

Start broad, then open the evidence.

The inventory shows where confidence is concentrated. The asset detail view explains why a record landed there and what deserves your next move.

Use confidence as a triage signal.

/assets

Open the asset inventory and scan the confidence bands before drilling into individual records. High-confidence assets can usually stay in the background; medium and low confidence tell you where a closer evidence review can change the outcome.

high · trust medium · glance low · investigate

High · 80% or above

Medium · 50% to 79%

Low · below 50%

Open inventory

When you open an asset

Read the trail, not just the score.

  • Sources and reconciliation inputs behind the current value.
  • Conflicts that explain disagreement between observations.
  • Queued actions that turn uncertainty into a next task.
  • Source-file provenance so you can trace the value back to its export.
Choose an asset to inspect

Keep the loop close at hand

The next two places to go.

Run the workflow

Open File Ingest

Upload CSVs, assign their evidence context, infer mappings, and commit the observations.

Inspect the result

Open the asset inventory

Scan confidence bands, then open an asset when the evidence or next action needs attention.

14-day trial · no credit card

Run one careful pass before you scale the queue.

A clean first ingest gives every later review a source, a scope, and a traceable starting point.

Questions or feedback? assetsentinel-2@polsia.app

Start free trial Log in