From f09328abf343f6d5d17ea4487a074604072e4968 Mon Sep 17 00:00:00 2001 From: Ossie Irondi Date: Thu, 24 Sep 2026 11:42:50 -0500 Subject: [PATCH 1/2] docs(simplefin): list the payment thank-you patterns in CategoryRules.md #180 replaced the bare 'thank you' pattern and #186 added a test that the doc mirrors the table; merged together they left main red. Co-Authored-By: Claude Opus 5.5 (1M context) --- .claude/skills/TransactionSyncing/CategoryRules.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/.claude/skills/TransactionSyncing/CategoryRules.md b/.claude/skills/TransactionSyncing/CategoryRules.md index b60bc372..3fc5cd8b 100644 --- a/.claude/skills/TransactionSyncing/CategoryRules.md +++ b/.claude/skills/TransactionSyncing/CategoryRules.md @@ -109,10 +109,12 @@ because the sync upserts the category on every row it touches. A bill payment posts twice: a debit on the funding account and a credit on the card, worded `PAYMENT - THANK YOU` or truncated by the issuer to -`AUTOMATIC PAYMENT - THANK`. `thank you` and `payment - thank` sit in Credit -Card Payment so the credit leg does not inflate income figures summed from -credits. A bounced payment posts as a `Returned Payment` debit for the amount -it unwinds; it is the mirror of a non-spend event and nets in the same category, +`AUTOMATIC PAYMENT - THANK`. `payment - thank you`, `payment thank you`, and +`thank you for your payment` sit in Credit Card Payment so the credit leg does +not inflate income figures summed from credits. A bare `thank you` is not a +pattern: merchant memos such as `THANK YOU FOR SHOPPING` would book a real +purchase as a bill payment and drop it from spend. A bounced payment posts as a +`Returned Payment` debit for the amount it unwinds; it is the mirror of a non-spend event and nets in the same category, while the issuer's separate `RETURNED PAYMENT FEE` is real spend. ## Deliberately left Uncategorized @@ -147,7 +149,7 @@ asserts the two match, so edit the code first and this list second. ### Credit Card Payment -`applecard`, `gsbapayment`, `chase payment`, `amex payment`, `discover payment`, `credit card payment`, `american express credit card`, `chase credit ca`, `wf credit card`, `apple credit card`, `amex epayment`, `chase credit card`, `thank you` +`applecard`, `gsbapayment`, `chase payment`, `amex payment`, `discover payment`, `credit card payment`, `american express credit card`, `chase credit ca`, `wf credit card`, `apple credit card`, `amex epayment`, `chase credit card`, `payment - thank you`, `payment thank you`, `thank you for your payment` ### Giving From 1b59a9d227513edf04df93d1ae2c91833241c0ae Mon Sep 17 00:00:00 2001 From: Ossie Irondi Date: Thu, 24 Sep 2026 11:43:01 -0500 Subject: [PATCH 2/2] docs(simplefin): rewrap the card-payment paragraph Co-Authored-By: Claude Opus 5.5 (1M context) --- .claude/skills/TransactionSyncing/CategoryRules.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.claude/skills/TransactionSyncing/CategoryRules.md b/.claude/skills/TransactionSyncing/CategoryRules.md index 3fc5cd8b..14a1cc8b 100644 --- a/.claude/skills/TransactionSyncing/CategoryRules.md +++ b/.claude/skills/TransactionSyncing/CategoryRules.md @@ -114,8 +114,9 @@ card, worded `PAYMENT - THANK YOU` or truncated by the issuer to not inflate income figures summed from credits. A bare `thank you` is not a pattern: merchant memos such as `THANK YOU FOR SHOPPING` would book a real purchase as a bill payment and drop it from spend. A bounced payment posts as a -`Returned Payment` debit for the amount it unwinds; it is the mirror of a non-spend event and nets in the same category, -while the issuer's separate `RETURNED PAYMENT FEE` is real spend. +`Returned Payment` debit for the amount it unwinds; it is the mirror of a +non-spend event and nets in the same category, while the issuer's separate +`RETURNED PAYMENT FEE` is real spend. ## Deliberately left Uncategorized