Imported transaction inputs are not persisted to source (saved as null)

[sergeiosipov]

Description

When importing transactions, all input fields provided during import must be persisted as is into the transaction source object.

This behavior existed in previous versions of the platform but is currently broken.
At the moment, the transaction is created with source = null, which leads to a loss of original import data.

This is a regression.

---

Expected Behavior

• During transaction import, all raw input fields must be written unchanged into the transaction source
• The source object must always be created if it was imported (manual booking is exception)
• Input values must be preserved even if they are later transformed, normalized, or recalculated
• Behavior should match previous platform versions

---

Actual Behavior

• Transaction is created successfully
• source is null
• Original import inputs are not persisted

---

Why This Is Important

Persisting raw import inputs is required for:

• auditability and traceability
• debugging and reconciliation
• comparison of input vs processed values
• parity with previous platform behavior

Loss of source data causes irreversible information loss.

---

Evidence

• In previous platform versions, source was populated correctly (see screenshot below)

• In the current version, source is not created and remains null

[sergeiosipov]

@falendary maybe the problem in name collisions with Source from Provenance