DTO Flow help center

Choose shared tracking, Subfeeds, or separate feeds

A feed holds the common exchange requirements. A Subfeed gives one exchange its own submissions, period status, and history beneath that feed.

• Choose Feed-wide tracking for one shared outcome per feed and period, such as the same monthly file published to several authorized recipients.
• Choose Partner-partitioned tracking when exchanges need separate outcomes but share direction, schedule, expected files, filename rules, validation contracts, and delivery behavior. A Subfeed can have several assigned Partners.
• Create separate feeds when those requirements differ. Subfeeds cannot override the parent configuration or contain further Subfeeds, and uploading one file does not split it into partner files.
• Choose the tracking scope when creating the feed. To change it later, create a replacement feed, copy the relevant configuration, update assignments and integrations, and archive the old feed when the replacement is ready.

Create and activate a Subfeed

Organization Owners and Organization Admins manage Subfeed lifecycle in the feed workspace. Creation and Partner assignment are separate steps.

1. Create a feed with Partner-partitioned tracking and configure its expected files and schedule. Open Subfeeds in the feed workspace. The feed can be active before Subfeeds are ready, but new uploads require an active feed and Subfeed.
2. Choose Create Subfeed and enter a stable key. Keys are unique within the feed, cannot be renamed, and remain reserved after archival. Use the format shown in the form.
3. Use Create and activate for a ready exchange, or save a Draft for later. Review the effective start shown in UTC; it defaults to the current minute. If activation fails after creation, keep the saved Draft and retry activation rather than creating it again. The start cannot be in the future or before the parent feed was created.
4. Activation and reactivation use your organization’s active-Subfeed allowance. Check the current limit before a large rollout. Saving a Draft or reading retained history does not activate a Subfeed.

Assign Partners and arrange portal access

A Partner identifies an external participant. The feed role determines permitted actions, while assignment determines the Subfeed the Partner can use.

1. Create or choose the Partner in your organization’s Partner catalog. The Subfeed assignment dialog does not create a Partner or send an invitation.
2. Grant that Partner access to the feed with the appropriate role. On Assigned Partners, No Subfeed means feed access exists but an assignment is still needed for operational access.
3. Assign an existing Subfeed, or create one and then assign the Partner. One Partner can have at most one Subfeed assignment within a feed. Several Partners can share the same Subfeed.
4. Arrange the portal invitation separately and confirm it is accepted when browser access is needed. Assignment gives access to the Subfeed’s retained history, including files from before assignment. Assign recipients together only when they should share that history.

Understand roles and shared visibility

Partners need both feed access and a current Subfeed assignment. Partners on different Subfeeds have separate operational views; Partners on the same Subfeed share its files and retained history.

• Organization Owners and Organization Admins create, activate, archive, and assign Subfeeds. Organization readers can inspect the Subfeeds available to them.
• Organization Operators can perform permitted operational work. Partner Operators can upload where the feed direction allows partner uploads, review results, and download authorized files in their assigned scope.
• Partner Observers can review and download authorized files but cannot upload. Organization Observers can inspect operational data without managing feed setup.
• Partner Feed Managers can upload where permitted and manage validation setup for assigned feeds. Validation setup belongs to the parent feed, so a rule change also affects its other Subfeeds; it is not a private override.

Upload, download, and follow each period

Work in the intended Subfeed and reporting period. Incoming feeds collect partner files; outgoing feeds let your team publish files for assigned recipients.

• Open the Subfeed’s submissions or the required period and choose Add submission. Internal users must select the intended Subfeed; a Partner works within the current assignment. Supply all required files and review the resulting validation status.
• To correct a file, add a new submission for the same Subfeed and period. A later accepted submission becomes current there. Earlier submissions remain in retained history, and another Subfeed’s accepted file is unaffected.
• Open the current accepted submission to collect available files. In an outgoing feed, all Partners assigned to that Subfeed can collect the same report when their permissions allow it.
• Use Overview and period monitoring to find missing, late, processing, or failed exchanges. Outgoing recipient counts record requests for download links to the current accepted submission; they do not prove that the complete file reached the recipient.
• Use the Subfeed’s periods, submissions, and activity links to inspect its history. Keep the Subfeed and period filters when investigating a correction or download. Access to older records is subject to retention.
• Ad hoc feeds do not have recurring expected periods. Use Submissions to follow their exchanges rather than looking for a recurring current-period result.

Change access, archive, or reactivate

Changing recipients and retiring an exchange have different effects. Review who should retain access before making either change.

• Remove the Partner’s Subfeed assignment to revoke current operational access. Their account, feed role, and historical attribution remain. Unassign first if you also need to remove feed access. Moving to another Subfeed gives access to that destination’s retained history.
• Archiving stops new upload sessions immediately. The chosen UTC end boundary determines which periods remain expected; it cannot be in the future or before the current activation boundary. Existing assignments and readable retained history remain. An upload session created while active may still be completed after archival.
• Reactivate with a UTC start at or after the previous archival boundary and no later than now. A recurring period is expected when its deadline falls within an active window, including its start but excluding its end. Periods before activation or in an archived gap are not automatically missing.
• Removing the last Partner does not archive the Subfeed. An active Subfeed with no recipients still creates scheduled expectations. Archive it explicitly when the exchange is retired.

Resolve common Subfeed problems

Start with the feed, Subfeed key, period, and signed-in account. Include those details when contacting support, without private token secrets or sensitive files.

• Cannot see the Subfeed or its files: confirm the account, feed role, and current assignment. An invitation alone is not an assignment. Ask an organization administrator to check Assigned Partners.
• No upload action: check the role, incoming/outgoing direction, active feed and Subfeed status, and any organization or Partner restriction. Draft and Archived Subfeeds do not accept new upload sessions.
• Key already exists: search Draft, Active, and Archived Subfeeds before retrying. Archived keys remain reserved. If creation succeeded but activation failed, activate the existing Draft.
• Activation blocked by capacity: review the organization’s active-Subfeed usage and limit. Archive genuinely retired exchanges or arrange a limit change; removing recipients does not free active-Subfeed capacity.
• A period appears missing or is not expected: check the schedule and the deadline against activation and archival boundaries. An accepted file in a different Subfeed or period cannot satisfy this one.
• Download link expired: return to the submission and request a fresh link. A fresh link requires current access and an available file. Removing access prevents new links from being issued; a link already issued may remain usable until it expires.