DAC7 Reporting Posture

Current pilot scope assumption

For pilot readiness, ElevateCSX treats creator-side payouts facilitated through the platform as potentially DAC7-relevant and prepares data collection/reporting controls accordingly, unless counsel confirms a narrower posture.

This means the product should be ready to identify reportable creators, collect the core seller data set, and reconcile annual totals against payout records.

Who is treated as the reportable seller class

The working assumption for the pilot is that creators receiving consideration through marketplace agreements are the main seller class to assess for DAC7 reporting.

• Creators: primary class to classify as reportable / non-reportable sellers based on jurisdiction and activity.
• Sponsors: generally treated as payers/buyers in the current marketplace flow, not the default seller class for DAC7 seller reporting.
• Stripe Connect / PSP data may support reconciliation, but does not replace platform-side due diligence on required seller fields.

Data fields the pilot should be ready to collect

Where a creator falls into scope, the pilot should be ready to collect and validate the following fields before unrestricted payouts continue:

• Legal name or business name, plus seller type (individual / entity).
• Address, country of residence/incorporation, and related jurisdiction fields.
• TIN / VAT ID or local equivalent, with reason codes where a tax identifier is not collected.
• Payout identifier context needed for reconciliation (for example PSP account reference or linked payout account metadata).
• Annual activity totals: consideration paid, fees withheld, number of relevant activities/agreements, and reporting year.

Operational workflow for the pilot

The pilot posture is intentionally lightweight but should still support annual reporting readiness and payout safety.

• Collect DAC7-required fields progressively in creator onboarding / payout readiness instead of showing them to all users upfront.
• Flag missing or invalid DAC7 fields for ops review and restrict new payouts until the creator record is complete.
• Use a manual-first annual reporting runbook with CSV export, payout reconciliation, and stored evidence for each reporting year.
• Retain DAC7 evidence and supporting records according to the tax/legal retention policy adopted for the pilot.

Questions

Questions about DAC7 readiness or tax reporting posture can be raised through support. ElevateCSX may request additional creator information before enabling or continuing payouts.