Partner upload instructions template
Give partners one practical message that explains what to submit, when it is due, how to correct it, and how they will know it is accepted.
Copyable instruction template
Replace the bracketed details with your exchange information, then copy the complete instruction set into the message or knowledge base your partner already receives.
Exchange: [EXCHANGE NAME] · Period: [PERIOD] · Deadline: [DATE, TIME, TIMEZONE]
Use the assigned DTO Flow feed so the package, period, and status remain connected.
Use the feedback attached to the submission instead of starting a separate exchange.
Acceptance tells both teams which result is ready for the receiving process.
Completed example
Specific instructions remove the questions that usually trigger follow-up messages.
| Instruction topic | Partner-facing detail | What the partner sees |
|---|---|---|
| Period | Q3 price update due 5 August at 16:00 CET | Partner selects the Q3 period |
| Package | Price workbook required; terms PDF optional | Expected files are visible before upload |
| Naming | price_update_Q3_2026.xlsx | The file is recognized for the expected package |
| Correction | Replace the workbook in the same period | The correction stays with the original period |
| Completion | Accepted status confirms readiness | Purchasing sees one current accepted package |
How to use it
Concrete file, period, and support details give partners confidence at the first submission.
Add the exchange name, period, deadline, files, formats, naming, correction owner, and support contact.
Confirm that the assigned partner can reach the feed, recognize the period, identify every expected file, and understand each status.
Share the reviewed text with the invitation or onboarding message and keep it aligned when the feed expectations change.
Turn guidance into a clear process
Partners see the same assigned feed, expected package, period, correction guidance, and accepted status described in the message.
Required and optional files appear in the selected feed and period before submission.
Invited partner users see only the exchanges and actions granted to them.
Agreed checks return precise, actionable findings on the submitted file.
Accepted status gives the partner and receiving team the same current result.
Instruction questions
The partner coordinator should own the message with input from the feed owner and the person responsible for validation or the receiving-team handoff.
Yes. List every required and supporting file, bringing Excel and CSV files together with the business documents the receiving team expects.
Send them with partner access or before the first expected period, then reuse the reviewed wording when the same exchange repeats.
Update the partner-facing text whenever the expected files, schedule, checks, support contact, or submission path changes.
Give the partner a clear path
Give the partner visible expectations, useful correction guidance, and a shared accepted result in DTO Flow.
