Skip to content

Your register and the floor should tell the same story.

Find the assets you cannot locate and the equipment your ledger is missing. Compare a finance extract with an operational register or field audit, resolve the differences, and keep the evidence behind every decision.

Discuss this workflow See how it works
  • Original snapshots retained
  • Reasons shown for every match
  • Run creator cannot approve their own run
Start with the finance snapshot. Then choose the register to compare it with.
Find the gaps

See missing, unrecorded and duplicate assets in separate exception categories.

Explain the decision

Keep the matched fields, differences and reviewer’s note together.

Hand over the evidence

Export snapshots, results and decisions for audit review.

The audit starts. The spreadsheet chase starts again.

Finance has one list. Site teams have another. You need a defensible answer before you can correct either.

Turn each mismatch into a decision you can defend.

  1. Today: Assets nobody can find

    A ledger entry survives long after the equipment has moved or disappeared.

    With Imara Nexus: Compare a consistent scope

    Capture both sources for the same site or account before matching.

  2. Today: Matches nobody can explain

    A spreadsheet lookup gives you a result but loses the reasoning.

    With Imara Nexus: See why records match

    Review identifiers, confidence, matched fields and financial differences.

  3. Today: Corrections without review

    The person preparing the comparison also signs it off.

    With Imara Nexus: Keep approval separate

    Resolve the exceptions and submit the run. Its creator cannot approve it.

  4. Today: Evidence rebuilt every year

    The original extract and the decision trail are scattered across saved files.

    With Imara Nexus: Retain the original record

    Stored snapshots preserve the source rows, capture details and content hash.

From the finance extract
to independent approval.

See how a reconciliation run comes together in Imara Nexus.

02 / Asset verification

See what matched, and why.

Each result shows its classification, confidence and the fields it matched on. Exact matches are accepted automatically; missing, unrecorded and financial variances each need a decision and a note.

Explore it in your workspace
Exceptions are listed first; the exact match is accepted automatically. Record decision is highlighted, not activated.
03 / Asset verification

Keep approval separate from preparation.

The preparer submits the run for independent approval. Once every exception has a decision, a reconciliation approver approves it with a note. The person who created the run cannot approve it, and the snapshots and decisions remain audit evidence.

Explore it in your workspace
Review a completed run. Submitting it for independent approval is highlighted, not pressed.

Recorded in Imara Nexus with sample data. Snapshot names, run names and the finance extract are examples, and the results come from a sample run already calculated from them. Dropdown choices step through their options without opening the list. No run is started, no decision is recorded and nothing is submitted or approved.

From register extract to reviewed exceptions.

Start with one site and a finance extract. Each run compares two snapshots.

  1. 1

    Capture the finance extract

    Upload a CSV with a stable identity such as an asset tag or serial number.

  2. 2

    Choose the comparison

    Snapshot the live asset register or a completed field audit for the same scope.

  3. 3

    Calculate the matches

    Review exact and probable matches alongside missing, duplicate and financial-variance results.

  4. 4

    Record the decision

    Resolve each exception with a decision and note, then submit the run for review.

  5. 5

    Approve and export

    A different person approves the run. Export the evidence and make any corrections in the source systems.

Before your first verification.

Do we need a direct ERP connection?

No. Start with a finance CSV extract.

Does it correct the ledger?

No. Matching records a proposed action and a decision; source-system corrections remain with your team.

Can we compare all three sources?

Capture finance, operational and field-audit snapshots, then compare the relevant pair in each run.

What should we bring?

One site’s register extract with stable tags or serials, and an operational snapshot or completed field audit.

Keep finance in control of the ledger.

Use Imara Nexus to prepare and review reconciliation evidence. Your finance system remains the place for accounting corrections and financial statements. Field audits can queue supported actions through brief connection losses once opened.

Start with the assets you cannot account for.

Tell us where the register stops matching reality. We can discuss the source extracts, site scope and review steps for your verification exercise.

Discuss this workflow

Prefer to explore first? Start a core-platform trial. Specialist workflows are enabled and configured separately.