DTP Guide
Understand DTP Processing & Reporting
DTP Framework
A Data Transfer Process (DTP) enables the automated exchange of data between your system and the vExchange platform.
The DTP framework standardizes how files are received, processed, and delivered between systems. Incoming data is converted into our internal data standard, allowing it to be validated, stored, and used consistently across the platform. Once processing is complete, output files are generated in the format required by the destination system.
Depending on the integration, a DTP may support:
- Inbound processing – receiving and converting files from a DTP client
- Outbound processing – generating files for delivery to a DTP client
- Status reporting – scheduled reports generated from historical data
Some integrations include both inbound and outbound processing, while others may only require one-way processing.
Key Terms
Data Transfer Process (DTP)
A configured integration that enables structured file exchange between systems.
Business Adapter
A component that formats data to match the requirements of a Receiver’s System of Record (SOR).
vExchange Data Standard
A normalized internal format used to standardize data across all integrations.
System of Record (SOR)
The Receiver system that ultimately owns and manages the data.
All DTP integrations follow a standardized workflow that converts external file formats into the internal data standard and then generates files in the format required by the destination system.
Processing occurs in three primary stages:
- File ingestion
- Data standardization
- File generation and delivery
Inbound processing is completed before outbound processing begins.
Files are exchanged using designated directories on the FTP server at https://vftp.vertican.com/WebClientNew/Login.
Directory Structure:
- ./[DTP or Business Adapter]/toVertican – Files uploaded by external systems for processing
- ./[DTP or Business Adapter]/fromVertican – Files generated by our system and delivered to the external system
Clients upload files to the toVertican folder and retrieve processed output files from the fromVertican folder.
Inbound processing occurs when a DTP client sends files to be processed by our platform. The Inbound Workflow can be summarized as: DTP Client → vExchange Data Standard → Business Adapter.
- DTP Client
- The DTP client uploads files to the appropriate FTP toVertican directory.
- vExchange Data Standard
- The vExchange system retrieves the uploaded files.
- File data is validated and converted into Vertican’s data standard.
- The standardized data is loaded into the platform database.
- Business Adapter
- Output files are generated in the format required by your System of Record.
- The generated files are delivered to the fromVertican directory for retrieval.
Outbound processing occurs when your system sends files that must be translated and delivered to a DTP client. The Outbound Workflow can be summarized as: Business Adapter → vExchange Data Standard → DTP Client.
- Business Adapter
- Your system generates files using the Business Adapter format.
- Files are uploaded to the FTP toVertican directory.
- vExchange Data Standard
- The vExchange system retrieves and processes the files.
- Data is converted into Vertican’s data standard.
- Standardized data is loaded into the platform database.
- DTP Client
- Output files are generated in the format required by your DTP client.
- The generated files are delivered to the fromVertican directory.
DTP processing follows a defined sequence to ensure data is processed and delivered in a consistent and predictable manner.
Processing Order
The following sequence ensures that any inbound data updates are reflected in the outbound files generated during the same processing cycle.
- Inbound processes run first
- Data from inbound files is validated and loaded into the platform database
- Outbound processes run
- Output files are generated and delivered to the appropriate FTP directories
Processing Schedule
DTP processing runs multiple times throughout the business day:
- 6:00 AM
- 8:00 AM
- 10:00 AM
- 12:00 PM
- 2:00 PM
- 4:00 PM
Processing times are approximate and may vary slightly depending on system activity and file volume. Generally processing takes place 365 days per year, except during system maintenance or unforeseen emergencies.
Files placed in the appropriate toVertican directory before a scheduled processing time will be included in that cycle. Files uploaded after a cycle begins will be processed during the next scheduled run.
To ensure successful file processing and delivery, you should follow these guidelines.
Uploading Files
- Upload files to the correct toVertican directory.
- Upload files before the next scheduled processing cycle.
- Ensure files are fully uploaded before processing begins.
File Integrity
- Do not modify files after upload.
- Do not overwrite files during processing.
- Duplicate or incorrectly formatted files may be rejected.
- To verify the correct file format, please refer to Individual DTP Documentation for each of your DTPs.
Retrieving Output Files
- Output files will appear in the corresponding fromVertican directory.
- Retrieve files after the processing cycle completes.
If expected output files are not available, verify upload location, timing, and file format.
During processing, uploaded data is validated to ensure it conforms to system requirements and expected data formats. When data does not meet these requirements, it may be rejected at the account, record, or field level.
- All rejected data is reported in an Excel file delivered to:
- ./[DTP or Business Adapter]/fromVertican/data_issues
- The file name follows the format:
- [agent_id]_Data_Issues_[YYYY]_[MM]_[DD]T[HH]_[MM].xlsx
- Example:
- XX99_Data_Issues_2026_03_16T15_23.xlsx
- This report provides visibility into any records or fields that were rejected during processing.
| Rejection Level | Description | Result |
|---|---|---|
| Account | Placement data not found for the account. Reported as 'Record with No Parent Key'. | Record Rejected |
| Record | Record structure or format is invalid (e.g., invalid record number or malformed record). | Entire Record Rejected |
| Field | Field value is invalid, exceeds length limits, or has a data type mismatch. | Field value nullified, record accepted |
Each DTP integration has its own documentation page that includes the following information. To find documentation for your firm’s subscribed DTPs, open the DTPs page in vPortal.
- Supported file types
- File delivery schedules
- Field mappings
- Data transformation rules
- Output file specifications
