Clovis

Documentation

Import statements safely

Bring bank, card, QFX, OFX, and CSV statements into Clovis with review before anything is committed.

npm

Import with review

The safest import workflow is: load the statement, keep rows pending, review duplicates and categories, then post only what you trust.

1. Prefer QFX or OFX when available

Bank-provided statement IDs make duplicate detection and reconciliation more reliable than hand-edited CSV.

clovis import --file statement.csv --account <checking-id> --counterpart <uncategorized-id>

2. Ask the agent to inspect pending rows

Useful tools include pending_summary, find_pending_duplicates, and uncategorized_transactions.

Review the pending import and identify duplicates, missing categories, and odd amounts.

3. Commit after reconciliation

Use dry-run tools when available, keep the original statement, and compare Clovis balances with the source account.

clovis account balances --format json

Key import tools

These generated MCP pages are the fastest way to see exact parameters and safety hints.

import_fileCan write, but supports dry-run. Preview the result before applying it.apply_reconciliation_planCan write, but supports dry-run. Preview the result before applying it.find_pending_duplicatesRead-only. Good first choice for answering questions and inspecting the ledger.