upsert-octopus-transactions

Reconcile Octopus transactions using a strict two-pass upsert workflow that matches existing entries first, then adds new ones, enforcing exact date/time matching and mandatory payee mappings to prevent guessing.

The two-pass upsert workflow requires Pass 1 to match and update existing ledger entries based on exact time matching, and Pass 2 to add new transactions, ensuring deterministic reconciliation without guessing.

Handle confidential payees by reading configurations from private.yaml, applying mandatory payee mappings to ensure sensitive transaction details are correctly processed and mapped during the ledger reconciliation.

Exact date and time matching within a strict tolerance of ±1.5 hours is enforced to ensure deterministic upserts, preventing ambiguous matches and guaranteeing that only the correct existing ledger entries are updated.

Yes, the reconciliation workflow updates existing journal entries with duration where applicable, ensuring the ledger accurately reflects transaction durations during the first pass of the upsert process.

The workflow enforces strict guardrails with no guessing, requiring mandatory payee mappings and chronological ordering, meaning unmatched transactions without valid mappings will fail unless explicitly clarified by the user.