Keep everyone on the same requirements
The parent feed holds the schedule, expected files, filename rules, validation contracts, and delivery settings. Each Subfeed follows that configuration, so a common change belongs in one place.
Subfeeds for partner file exchanges
One setup. Separate partner exchanges.
When partners follow the same file requirements, you should not have to configure the exchange again for each one. Subfeeds keep one shared setup while giving each exchange its own submissions, status, and history.
Illustrative monthly sales feedShared rules. Separate progress.
North · SubfeedOwn submissions and history
AcceptedSouth · SubfeedOwn submissions and history
Needs correctionWest · SubfeedOwn submissions and history
Awaiting submissionLess repeated setup
Manage the requirements once. See each exchange clearly.
A partitioned feed brings related exchanges together without combining their files or their progress.
Find the exchange that needs attention
One partner’s accepted submission does not hide another Subfeed’s missing report. Review each period, follow corrections, and keep earlier submissions in their own history.
Choose who shares an exchange
Assign one or more Partners to a Subfeed. Those Partners share its files and retained history. Use separate Subfeeds where the exchanges need to stay separate.
Two ways to use Subfeeds
Collect separate files or publish separate reports
Monthly sales reports from distributors
Three distributors send the same Excel or CSV layout every month. Create one incoming feed and a separate Subfeed for each distributor, with the same deadline and validation rules.
Your team can see whose report is accepted, whose needs correction, and whose has not arrived. Each distributor works within its assigned Subfeed.
Reports for different recipient groups
Your team prepares a separate monthly report for each region. Use one outgoing feed with a Subfeed per region, then assign the regional manager and finance contact to the same regional Subfeed.
Both recipients can collect that region’s report and see its retained history. Other regions use their own Subfeeds, while the publication schedule and expected files stay consistent.
Choose the right tracking scope
Start with what the exchanges have in common
The choice depends on whether you need one shared result, separate results under the same rules, or genuinely different requirements.
One shared exchange
Use shared tracking when several authorized recipients should collect the same published files and work from one period result.
Separate exchanges, common rules
Use Subfeeds when partners or recipient groups need their own submissions and period results, with the same direction, schedule, expected files, and validation rules.
Different requirements
Use separate feeds when the schedule, file definitions, validation rules, or delivery behavior differ. Each feed can then be maintained around its own requirements.
A few things to know about Subfeeds
Can several people receive the same report?
Yes. Several Partners can be assigned to the same Subfeed. Each needs the appropriate feed role and assignment, and all share that Subfeed’s retained files and history.
Can a Subfeed have its own validation rules?
Subfeeds inherit the parent feed’s configuration. Choose separate feeds for exchanges that need different validation rules or schedules.
How do files reach the right Subfeed?
Your team, partner, or integration submits each file set to its intended Subfeed. DTO Flow tracks the exchange there; your source system prepares the separate files.
Bring the next exchange into focus
Set up the common rules. Give each exchange its own place.
Start with one recurring partner file exchange and build from the requirements you already know.