2030 · Bookkeeping automation
Duplicate detection
Autessa Accounting has one duplicate check shared by Mercury sync and statement uploads, built so a real charge is never deleted. Identical rows are counted rather than collapsed: re-uploading a statement adds nothing, and a genuine third $22.14 charge at the same merchant on the same day adds exactly one row.
The problem
Naive duplicate checks delete real money
Two $22.14 charges at the same merchant on the same day are two charges. A check on date, amount and description throws one away and nobody ever sees the money go missing. A visible duplicate is a nuisance; a silent deletion is a corrupted ledger.
What you get
- Distinct bank reference IDs mean different transactions: both import, silently.
- Identical reference IDs mean the same transaction re-imported: it is skipped, silently.
- No reference IDs is genuinely ambiguous: Accounting counts how many identical rows are already here against the file and asks you.
- The same transaction arriving from Mercury sync and from an uploaded statement is recognized as one, because both share the account’s scope.
- Possible duplicates have their own filter in the review inbox.
- A transaction page warns “This might be a duplicate” when it looks like one.
How it works
How does duplicate detection work in Autessa Accounting?
Fingerprint
Each incoming row is compared with what is already staged for the same account.
Use the bank’s evidence
Reference IDs decide when present: distinct means import, identical means skip.
Count when ambiguous
Without references, identical rows are counted: the file’s count minus what is already here is what imports.
Ask only when needed
Anything still unclear is marked as a possible duplicate for a person to decide in the review inbox.
Every option
Duplicate states
| Option | What it does |
|---|---|
| New | Imports normally. |
| Duplicate of a record | Already here; skipped. |
| Needs review | Ambiguous; shown under Possible duplicates for a person. |
Permissions
Who can do what?
| Role | Can |
|---|---|
| Bookkeeper and up | Resolve possible duplicates in the review inbox. |
FAQ
Questions about duplicate detection
What if I upload the same statement twice?
Nothing is added. Rows already here are recognized and skipped.
Will two identical real charges both be kept?
Yes. Identical rows are counted, not collapsed, and distinct bank reference IDs prove they are different charges.
Do Mercury sync and uploads double count?
No. They share one duplicate check, so the same transaction from both sources is one row.
100% customizable, code and all
Make Autessa Accounting fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours