Skip to main content

Solutions

Products

Recommended products

Questions? We are here to help.
Contact us

Purchase

Questions? We are here to help.

Resources

Data file integrator (DFI)

Processing files with DFI

Each submission to Data File Integrator (DFI)'s made up of 2 or 3 files.

Input files

File type
Required
Description
File extension
Data File
Yes
Contains the transaction or configuration information you want to process.
.csv
Properties File
No
Contains the definition of the corresponding data file. File name must match the data file.


If you don't include a properties file, DFI attempts to find a mapping with a name that matches the parent folder for your submission. If no mapping's found, the data file isn't processed.


The properties file must contain the Home Firm and External Company Id of the Company that was selected when the mapping was created. If these 2 required elements aren't included, the job will fail.

.properties
Trigger File
Yes
Empty file that indicates your submission is ready to process. File name must match the data file.


You must only place the trigger file into the input directory after the corresponding data and properties files are fully copied into the input directory. DFI attempts to process your submission as soon as it finds a trigger file and returns an error if a matching data file isn't found.

.trg
note
Certificate Manager's Certificate Import Service allows you to import certificate images, which have special considerations for error handling:
  • If a referenced image isn't found in the .zip file, the certificate's imported without the image, and the issue's noted in the log. The import continues.
  • If a referenced image's larger than Certificate Manger allows (6 MB), the certificate's imported without the image, and the issue's noted in the log. The import continues.
  • If an image .zip file's referenced but can't be found in the input directory, all records in the import fail.

Log files

Data File Integrator (DFI) creates a log file for every submission. The log file contains general information about the job and information about any errors that occurred.
This example shows the contents of a log file for a successful submission.


Beginning to process job for trigger file


C:\DataFileIntegrator\TaxServiceA\input\DecemberInvoices.trg.


loading properties file DecemberInvoices.properties


Beginning to parse input


Sending request to Determination


Processing response from Determination


Saving completed status for job.


Deleting files for job. Done processing job.


Deleting files for job.


Done processing job. Saving final status.


Closing log file for job.

Log files get named with the format, <InputFilename>_<ProcessingDate-Time>.log. For example, DecemberInvoices_12302012101500.log.

Output files

Each submission to Data File Integrator (DFI) results in 1 or more output files.
note
If the number of errors in the input file exceeds the threshold defined in your settings processing will stop and neither a reprocess or results file will be created. The log file will contain the error-related information up to the last line processed.
File type
Description
File extension
Results File
Contains the results of your submission. Results files are named with the format: < InputFilename>.out.csv. For example, DecemberInvoices.out.csv.


Skipped header lines from your input file aren't included in the results file. Use the comment character instead to include rows from your input file in your results file.

.csv
Reprocess File
For submissions that contain errors a reprocess file's created containing the lines with errors. This file can be compared to the errors listed in the log file. Once the errors have been identified and corrected this file can be submitted for processing. Reprocess files are named with the format: < InputFilename>.reprocess.csv. For example, DecemberInvoices.reprocess.csv.
.csv
Confirmation File
Empty file indicating your submission's completely processed. Confirmation files are named with the format: < InputFilename>.end. For example, DecemberInvoices.end.
.end
Depending on your configuration, Data File Integrator may split your results into multiple files or may compress your results file into a .zip file. In the case of multiple files, each output file includes a number in the file name. For example:
  • DecemberInvoices1.out.csv
  • DecemberInvoices1.end
  • DecemberInvoices2.out.csv
  • DecemberInvoices2.end

This article applies to:

  • PRODUCT: ONESOURCE Determination,ONESOURCE Indirect Tax
  • Subject: Integration