match-octopus-statement-transactions

Matching Octopus Wallet statements to journal times involves aligning rows by exact date, amount, and reference, with nearest-date fallbacks. It updates only datetimes, preserves amounts, and flags unmatched rows for manual review.

Timezone discrepancies arise because the statement matching respects local time zones by default when updating journal datetimes. This ensures accurate alignment between Octopus Wallet records and local accounting entries.

Unmatched rows during Octopus Wallet statement reconciliation are flagged for manual review. The process records these audit-friendly outputs alongside non-typical updates to ensure human oversight and data integrity.

No, you cannot update transaction amounts when syncing Octopus Wallet statements. The process updates only the datetime fields of matching journal transactions while strictly preserving original amounts for auditability.

Yes, Octopus Wallet statement matching supports partial and multi-match handling using reference IDs and nearest-date fallbacks. When matches remain ambiguous, it flags the transactions for manual review.

You should manually review journal entries when the statement sync flags unmatched rows or non-typical updates. This occurs when exact, reference-based, or nearest-date matches fail to find a single clear transaction.