Match Octopus Statement Transactions

Use this ImageMagick template to convert a PDF to a high-res PNG. Do NOT include or echo any sensitive wallet numbers in filenames or outputs.

magick -density 300 "input-statement.pdf" -background white -alpha remove -quality 100 "output-statement.png"

Notes:

• Use an output pattern like output-statement-%03d.png for multi-page PDFs.
• Optional flags: -trim, -shave, -resize.

Behavior and heuristics

• Matching priority (try in order):

  1. Exact date (YYYY-MM-DD), signed amount, and a details/remarks token (merchant name or reference ID).
  2. Signed amount and reference ID (e.g. FRN... or card Ref).
  3. Fallback: signed amount and nearest date within ±1 day.

• Time update rules:

  • Typical case: journal has same date, hour and minute but lacks seconds — append statement seconds to journal time (silent by default).
  • Non-typical case: any change that alters minute, hour, or date, or changes seconds when the journal already included seconds — these must be reported and shown with original and updated datetimes.

• Tie-breaking & pairing:

  • Prefer matches containing a bank transfer reference (FRN...) when present.
  • Treat paired flows (bank transfer FRN credit followed by wallet→card debit on same date) as linked and update both times consistently.
  • After updating a bank-transfer credit, inspect the very next journal entry; if it represents the corresponding reload (either tagged activity: reload or a self-to-self activity: transfer), adjust that entry’s datetime to the wallet→card timestamp and add a duration: metadata equal to the difference between the two times.
  • If multiple candidates remain, list them and require user confirmation; do not auto-apply.

• Timezones: treat statement times as local (UTC+08:00) by default; preserve timezone tags and avoid implicit conversions unless the user requests one.

• Never modify amounts or postings — only change datetime metadata.

Summary & output

After processing produce a concise summary containing only:

• Non-typical updates: show original and updated transaction text and file path for manual review.
• Missing transactions: statement rows with no unique match.

Typical seconds-only edits are omitted from the normal summary. To include those, run with a --verbose flag (e.g. "use match octopus statement transactions --verbose").

Validation

• Optionally run formatting and validation scripts after edits:

  python -m format   # set cwd to scripts/
  python -m check    # set cwd to scripts/
  

Note: See .agents/instructions/developer-workflows.instructions.md for canonical script usage and working-directory rules.

• The skill can produce a patch/diff for review but does not commit changes.

Security & privacy

• Do not log or store full Octopus wallet numbers. Redact any full wallet numbers from outputs and filenames. The skill must never write the wallet number into repository files or skill outputs.

Notes

• Be conservative: require a unique match before auto-editing. When unsure, surface candidate matches for human confirmation.
• The user is responsible for committing any repository changes.
  • If an agent commits changes on your behalf, the agent must follow .agents/instructions/git-commits.instructions.md. For ledger transaction commits use the exact ledger(<journal-list>): add N / edit M transaction(s) header and no body.

Lessons Learned

For consolidated lessons across all skills and matching patterns, see .agents/instructions/continuous-learning.instructions.md and upsert-octopus-transactions/lessons.md.

Key insights:

• Matching priority: exact date + signed amount first; then amount + reference ID; then amount + nearest date
• Time updates: always preserve existing times; only append seconds if missing
• Paired flows: bank transfer credit + wallet reload should be linked with consistent durations
• Ambiguous matches: always surface to user for confirmation; never auto-apply

Example invocation

Use match octopus statement transactions on December 2025 PNG and update journal entries; show summary.