diff --git a/graph/problems/sf-ca-contact-required-platform-fields-bug-in-sf-cajson-d0ac99.md b/graph/problems/sf-ca-contact-required-platform-fields-bug-in-sf-cajson-d0ac99.md
new file mode 100644
index 00000000000..b64b8b55fe1
--- /dev/null
+++ b/graph/problems/sf-ca-contact-required-platform-fields-bug-in-sf-cajson-d0ac99.md
@@ -0,0 +1,28 @@
+---
+id: d0ac9986-d5a7-4c38-acb2-5110abcbc870
+type: problem
+title: "SF-CA Contact required_platform_fields bug in sf-ca.json"
+tags: [esb, sf-ca, bug, object-handler, salesforce, commercial-aquatics]
+importance: 0.7
+confidence: 0.8
+created: "2026-03-04T17:05:56.120852+00:00"
+updated: "2026-03-04T17:05:56.120852+00:00"
+---
+
+## Bug: Contact required_platform_fields references Account fields
+
+In `packages/py-esb-integrations/src/esb_integration/mappings/sf-ca.json`, the Contact mapping has:
+
+```json
+"required_platform_fields": ["Name__c", "Account_Status__c", "Operating_Entity__c", "Primary_Email__c"]
+```
+
+`Account_Status__c`, `Operating_Entity__c`, and `Primary_Email__c` are **Account fields** — they are NOT in Contact's `field_aliases`. This will cause validation failures when the Object Handler processes Contact records if it enforces required_platform_fields as a presence check.
+
+### Location
+- File: `packages/py-esb-integrations/src/esb_integration/mappings/sf-ca.json` line 42
+- Related story: ESB-51 (Object Handler configuration)
+
+### Action needed
+- Investigate whether these are intentional cross-object references or a copy-paste error
+- Fix during ESB-51 implementation