Explicit file expectations
Document the expected filename, format, worksheet, columns, and value rules around one recurring partner exchange.
Legacy import file validation
Give legacy imports clean, predictable partner files.
Turn established import requirements into clear partner expectations, guide Excel or CSV corrections early, and give the import owner one accepted file they can trust.
Controlled import intakeLegacy import file
ActiveReceivedChecks passedReady for import
A safer path into existing imports
Give senders clear guidance before the import begins.
Make the expected file, agreed checks, correction guidance, accepted version, and handoff visible before each import run.
Actionable guidance
Show clear row-and-column guidance so the partner can deliver a table that is ready to use.
A trusted accepted input
Keep a complete correction history and identify the accepted file that is ready for the import owner.
A concrete pre-import workflow
Put a controlled gate in front of the existing import.
Consistent, agreed rules give partners and import owners a clear answer about when the table is ready to move forward.
Capture the import expectations
Define the expected file and transparent rules for the Excel or CSV table the import expects.
Give the partner a clear path
Give the partner secure access to the exchange and submission actions intended for them.
Set the business period
Tie the submission to the week, month, batch, or ad hoc period the import run expects.
Keep every submitted version
Keep each submitted file connected to its partner, import period, and correction history.
Fix issues before handoff
Show clear locations and examples so the partner can correct the file and submit a new version.
Release the accepted input
Make the current accepted original available for authorized download or API retrieval before the existing import runs.
Example import table
Turn established import requirements into reviewable checks.
Apply the rules your team already trusts consistently to every submitted partner table.
External IDRecord typeEffective dateQuantityAmountStatus
Columns and aliases
Require import fields while allowing explicitly approved partner header variants.
Types and formats
Check text, numbers, dates, times, and true/false values against the approved formats.
Accepted values and ranges
Apply accepted values, date formats, and numeric limits defined for the import.
Unique keys within the file
Flag duplicate values in the selected key fields before acceptance.
Operational status
Know whether the next import input is ready.
Separate missing, processing, failed, accepted, and replaced submissions while retaining every original attempt.
- Missing import file
- Submitted late
- Processing
- Validation failed
- Accepted
- Replaced by a later acceptance
- Current accepted submission
- Complete submission history
Good fit
Strengthen recurring imports with a predictable partner table.
Keep the process your team already uses while DTO Flow improves the quality, visibility, and readiness of every partner file entering it.
- A partner provides the same import file by period or batch.
- Your import owner can describe what a usable file looks like.
- The target is one CSV table or selected Excel worksheet.
- Authorized users can download the accepted file, or an approved integration can retrieve it through the API for the existing import.
Questions your team may ask
Before placing a validation gate in front of an import.
Which files can receive deep validation?
Apply detailed validation to the CSV table or Excel worksheet your import uses. A clean business-table export gives both the partner and import owner the clearest result.
What does the partner see when validation fails?
The partner receives clear issue details with row and column context where available, then can submit a corrected file.
How does DTO Flow work with the target import?
Authorized users can download the accepted file, or an approved integration can retrieve it through the API when the existing import is ready.
How is the validation result decided?
Clear, approved rules determine the result. Your team can see exactly which expectation was met or needs attention before accepting the file.
Explore the complete workflow
Connect pre-import validation to controlled partner intake.
See the gateway, file contract, supplier experience, and related recurring-file use cases.
Start with one important import
Give the next partner file a clear path to import readiness.
Define the expected table and checks, then let the sender correct issues before the accepted file is downloaded or retrieved for your existing import.