We will be pleased to ship you the
software and manual.
PCO file splitter for Pershing Data Translation
To order, please download the Order Form save it, print it, fill it in and fax or
e-mail it back to:
We will be pleased to ship you the
software and manual.
Introduction and Overview
XPCO is a software product developed maintained, supported and marketed by AS&A brokersoft that extracts Pershing data files from the PCO file container into which they have been placed. Once extracted, those data files can be loaded directly into our ViewPoint Consolidated Client Statements, or translated by Xlate into a format usable by E-Z Data's Client Data System, or made available for other uses or software programs.
Pershing, a division of Donaldson, Lufkin, Jenrette, is a correspondent clearing firm that executes stock, bond, mutual fund and other types of transactions on behalf of its correspondent clients. A great deal of data is generated in this process, some of which is made available and is very useful to the Broker/Dealer correspondent clients of Pershing, and their Registered Representatives.
Making effective use of that very valuable and possibly voluminous data can be a daunting task. One of the ways that the process of managing that data can be aided, is through the use of programs that take data in one format and convert it to the format of a software product that you may use to help manage your client information. Making use of that valuable data requires first that the data be made available to the end user.
Normally, Pershing files are made available to Broker Dealers via the Pershing supplied InfoDirect software. In many cases, these Broker Dealers allow users to interact directly with Pershing's InfoDirect software and obtain the data files on an individual Financial Professional basis. In other cases, Broker Dealer obtain the data, and pass it on via some download mechanism as separate data files which the user in turn would individually download to his PC, as shown in the following examples:
We have a product called SDD (Securities Data Distributor) which takes Pershing ( and DST, DAZL and other data) and extracts from the larger office or Broker Dealer level data feed, data for a single office, multiple offices, single or multiple Financial Professionals. The Home or Branch office can then supply those data files as it sees fit at much lower cost and on a "one stop shopping" basis for the Financial Professional.
Some Broker Dealers acting as their own data providers however (Pershing is NOT among them) have elected to make the Pershing data files available in a single file container known as a PCO file. A PCO file is a single file containing all of the other individual Pershing data files, as illustrated below:
The data provider may provide the files in this single format rather than as a group of discrete data files, or even as a single Zip format file. PCO files are not usually zipped, although there is nothing preventing a data provider from zipping a PCO file once created.
The PCO file format is a known file format allowed under the public domain Generic Interface Specification.
The Generic Interface Specification is a format for exchanging data between financial entities and programs, and has been placed into the public domain by Financial Computer Support, Inc. Many programs and financial industry companies and organizations make use of this specification.
Data in the Pershing data format (or some Broker/Dealer provided variants of that format) can be used directly by portfolio and investment tracking software that requires the raw Pershing data such as our ViewPoint Consolidated Client Statement software. Other investment software packages require that the raw Pershing data first be converted from the Pershing format to the Generic Interface Specification format before it can be used. We have another software module Xlate, that translates the extracted data to the Generic Interface Specification data format. Regardless of the ultimate format required for using Pershing by your software program, in most instances, it must not be delivered to your software as a single PCO file, but as the separate components as originally produced by Pershing.
XPCO is our product that unpacks the PCO container files into its separate constituent elements so that your software, whether spreadsheet, ViewPoint or some other investment and client data management system, can make use of it.
It helps you to automate what would otherwise be a complicated, time consuming and costly manual process of editing and attempting to remove the files manually from the container and somehow getting the bulk results it into your software system.
XPCO can process a single PCO file containing many individual file components containing hundreds or thousands of transactions in a very short time, and put that data back into the original file format that your investment tracking software can then import into its databases.
As an example: Our own ViewPoint Consolidated Client Statement software is just such a system. It requires that the individual file components be available to import into its database. Using XPCO and ViewPoint you can reduce severely or eliminate entirely the manual data entry process for this type of data, saving a great deal of time ( and consequently money ) and helping to prevent the kinds of mistakes that the manual data entry process can introduce into your client records.
If you obtain or are provided with Pershing data on a daily basis, you can run XPCO every day, importing the results into ViewPoint or other Investment Tracking software, maintaining a very current client database of securities transactions!
If you are provided with data on a weekly or occasional basis, or if you store your daily or weekly Pershing data for future use, you may run XPCO and process it into ViewPoint or your other software whenever you need to.
XPCO not only processes your PCO data file into these discrete files that can be used by your software, but provides you with a log file for each step. The Log file can be reviewed for any exceptions that may occur and for statistics on total records processed for each type of data input file. These log files provide you with a means of evaluating what action you may wish to take, if any, for such things as partial files and other possible errors.