One place for the period
Replace attachment threads with an assigned feed, expected file, due period, and visible submission state.
Partner reconciliation file intake
Make partner reconciliation files predictable before review begins.
Collect each expected reconciliation file through a controlled partner feed, check its Excel or CSV structure, preserve corrections, and give reviewers one clearly accepted submission for the period.
Incoming reconciliation feedPartner reconciliation file
ActiveReceivedChecks passedCurrent accepted
Control intake before review
Start reconciliation work with the expected file and a clear history.
Before anyone investigates business differences, your team still needs to know whether the correct partner submitted the correct period, whether the table is structurally usable, and which version is current.
File-level readiness checks
Catch missing references, invalid dates or amounts, values outside the accepted list, and duplicate values in the selected key fields.
Auditable corrections
Preserve every attempt unchanged and make the later accepted submission clearly available to reviewers.
A concrete reconciliation-file workflow
Start reconciliation with a file that is already ready for review.
DTO Flow keeps every expected file, correction, and acceptance together so finance and operations can begin with confidence.
Define the expected file
Capture the expected file, reporting cadence, and data requirements for the partner exchange.
Assign the partner
Give the intended partner users access only to the incoming feed they should submit.
Track the reconciliation period
Make the month, week, statement cycle, or ad hoc period explicit before upload.
Keep every submitted version
Keep each file connected to its partner, reconciliation period, and correction history.
Guide the partner's correction
Show clear locations and examples so the partner can correct the table and submit a new version.
Release the accepted file
Identify one current accepted submission and make it available for authorized download by the reconciliation team.
Example reconciliation file
Validate file readiness with transparent rules.
Check the submitted table for the expected structure and value formats before the business review starts.
Partner referenceInternal referenceTransaction dateAmountCurrencyRecord status
Required references
Require the identifiers your review process needs and allow approved header aliases.
Dates and amounts
Check transaction dates and decimal amounts against the agreed formats.
Currencies and statuses
Limit selected fields to the currency and status codes used by your process.
Duplicate record keys
Flag duplicate values in the selected key fields before acceptance.
Operational status
Know when the file is ready for reconciliation work.
Period status and complete history show what is due, what needs attention, and what is accepted.
- Missing reconciliation file
- Submitted late
- Processing
- Validation failed
- Accepted
- Replaced by a later acceptance
- Current accepted submission
- Complete submission history
Good fit
Use this workflow when reconciliation starts with a partner file.
The file exchange repeats, the expected layout is known, and reviewers need a dependable accepted input.
- The same partner sends a reconciliation or statement file by period.
- Your receiving team defines what makes the file ready for review.
- The important content is an Excel worksheet or CSV table.
- Finance or operations reviewers can begin matching and resolution from one accepted input.
Questions your team may ask
Before controlling reconciliation-file intake.
Which reconciliation files can be validated?
Apply detailed checks to the structured Excel or CSV table used for reconciliation, while keeping the complete supporting file package connected to the same submission.
Can a partner resubmit a corrected file?
Yes. The new file becomes another submission, and a later accepted version can become current while the earlier file remains in history.
How do reviewers receive the accepted file?
Authorized reviewers can download the accepted file, or an approved integration can retrieve it through the API.
How does DTO Flow strengthen reconciliation?
It gives the matching and resolution team one accepted, traceable partner file with clear period context and a complete correction history.
Explore the complete workflow
Connect file intake to the controls around it.
See how file expectations, validation, partner access, and adjacent recurring workflows fit together.
Start with one partner file
Give reviewers one clearly accepted reconciliation file for the period.
Define the expected file and checks, then keep submission, correction, and acceptance history in one controlled workflow.