LedgerAtlasEvidence directorySubmit a tool

Evidence comparison / two records

DualEntry vs Vic.ai

Read two dated LedgerAtlas records side by side. Differences are shown as recorded observations, not as scores or recommendations.

01 / Recorded observations

Evidence matrix

Each value is copied from the registry and its dated source record. Unknown fields remain visible.

FieldDualEntryVic.ai
Category
Bookkeeping automation
Document intake
Recorded workflows
Bookkeeping automation · Close & reconciliation · Reporting & advisory
Document intake · Bookkeeping automation
Ledger integrations
Other
Other · Unverified
Firm-size fit
50+ clients · Not stated
50+ clients · Not stated
Workflow replaced
Legacy ERP accounting, close, and reporting workflows within a general ledger platform.
Manual invoice data capture, coding, approval routing, and AP review.
Pricing model and notes
Contact sales — The official site uses a demo and sales-contact path; public prices were not stated.
Contact sales — The official site provides a demo path; public prices were not stated.
AI depth
Mixed
Mixed
Free tier
No free tier stated
No free tier stated
Other integrations
Own general ledger · Migration connectors
ERP systems
Verification status
Unverified
Unverified
Last checked
2026-09-14
2026-09-14

02 / Source registers

What each record cites

DualEntry

  1. 01
    DualEntry AI-native ERP

    ERP and general-ledger product scope.

    DualEntry · observed 2026-09-14
  2. 02
    DualEntry integrations

    Published platform and migration connections; QBO/Xero are not recorded as active ledger integrations here.

    DualEntry · observed 2026-09-14

Vic.ai

  1. 01
    Vic.ai autonomous finance

    Invoice processing and AP automation scope.

    Vic.ai · observed 2026-09-14
  2. 02
    Vic.ai integrations

    Published ERP connections; QBO/Xero status remains unverified.

    Vic.ai · observed 2026-09-14