A OneWorld subsidiary represents a legal-entity context in a company hierarchy. A parent and child can share account numbers without being the same company. Identify the subsidiary on the entity record, transaction and report before comparing amounts. A department answers a classification question within that context; it doesn't replace a legal entity.
The local company starts with US, EU and ELIM subsidiaries, all using USD. Those IDs are original training identifiers, not real legal entities or evidence of a foreign-exchange implementation. You can add a supported USD child and retain an inactive record for historical identification. The model doesn't reproduce legal registration, multiple accounting books or every OneWorld setup requirement. Inspect the parent, currency and active state rather than treating a similar name as proof that the subsidiary is correct.