Currently, when Dext is connected to QuickBooks Online (QBO), all transactions published from Dext are recorded in the QBO Audit Log under the user who originally established the connection — regardless of who actually performed the publishing within Dext. This creates a significant issue for audit trails and accountability.

For example, if an external accountant sets up the Dext–QBO integration, but the client processes and publishes all transactions thereafter, the QBO Audit Log will incorrectly show the accountant as having posted every transaction from Dext (and the audit log does not say this came from Dext, so makes it look like the accountant actually posted in QBO).

This misrepresentation:
- Obscures the true source of entries
- Creates confusion during year-end reviews, audits, and compliance procedures
- May raise unnecessary audit flags or concerns around user activity

Requested improvement:
Dext should pass through the identity of the actual user who publishes each item so that QBO Audit Logs accurately reflect the individual responsible for the transaction.
At a minimum, should at least pass information in the log that this is a Dext import

Accurate audit attribution is essential for transparency, compliance, and maintaining trust in financial reporting.