The following is a sample file layout for the PITNEY.EXE program.
Program: PITNEY.EXE
Note: There are 5 possible Pitney Bowes formats that this program supports.
Format 1: Format for A120, A130, G120, G140, G150, or G170
Data File: TRAN_CMS.TXT
File Type: Fixed Length (record length = 170 bytes)
TRAN_CMS.TXT File Layout
Name Start Length Description
--------- ----- ------ --------------------------------------------------
User Code 26 11 Used in descriptions
ID Number 37 11 Used in descriptions
Date 54 6 Transaction date in MMDDYY format
Amount 76 7 $1.23 stored as 1.23 (padded with spaces on left)
Account 88 16 Client/matter number - must have a "." between the
client and matter numbers
Note: The User Code and ID Number fields are only displayed on a list
of rejected transactions that do not successfully merge in with TABS III.
Sample TRAN_CMS.TXT data file
Notes:
1) The first 3 lines are not part of the TRAN_CMS.TXT file.
2) Each record has been divided into 3 separate sections (two 70 byte
sections followed by a 30 byte section) so the records won't be truncated
on the page.
3) The "[" and "]" characters have been added to illustrate where the carriage
return/line feed combination would appear in each record.
4) ASCII code 2 is in the first column of each record. ASCII code 3 is in the
last column (in column 128 before the carriage return & line feed) of each
record. These 2 ASCII codes are part of the "real" data as it comes out
of the Pitney Bowes system.
1 2 3 4 5 6 7
1234567890123456789012345678901234567890123456789012345678901234567890
----------------------------------------------------------------------
00000680 JPO 1207040133072892 42Y
001 0.500 100.00 0.00 0.00 0.00 0.00 0.00
0.000 0 0.00 0.001a35[]
00008680 JPO 1207040302072892 52A
2.870 101.00 0.00 0.00 0.00 0.00 0.00
0.000 3 0.00 0.0019f0[]
00008680 JPO 1207040332072892 232A
1.910 123.45 0.00 0.00 0.00 0.00 0.00
0.000 5 0.00 0.001a18[]
00008680 JPO 1207040409072892 62A
1.910 102 0.00 0.00 0.00 0.00 0.00
0.000 5 0.00 0.001a06[]
00008680 JPO 1207040447072892 32A
0.870 103.00 0.00 0.00 0.00 0.00 0.00
0.000 3 0.00 0.0019ff[]
00000680 JPO 1207040503072892 62A
0.000 200.01 0.00 0.00 0.00 0.00 0.00
0.000 0 0.00 0.0019f2[]
00008680 JPO 1207040559072892 132A
2.080 200.02 0.00 0.00 0.00 0.00 0.00
0.000 4 0.00 0.001a08[]
00008680 JPO 1207040636072892 252A
1.330 200.03 0.00 0.00 0.00 0.00 0.00
0.000 3 0.00 0.001a0b[]
00008680 JPO 1207044135072892 92A
1.740 300.00 0.00 0.00 0.00 0.00 0.00
0.000 6 0.00 0.001a13[]
00008680 JPO 1207044200072892 92A
0.870 402 0.00 0.00 0.00 0.00 0.00
0.000 3 0.00 0.0019f3[]
==============================================================================
Format 2: Format for A-10000, Star 190 Carrier Management System, or
G-300 series
Data File: TRAN_CMS.TXT
File Type: Variable Length (comma-delimited)
TRAN_CMS.TXT File Layout
Note: The input file is composed of 2 record types. The first is a
"header" record followed by 1 or more transaction records. There may be several
header records followed by the associated transactions records in each file.
Header Record (contains 21 fields - don't know what is contained in the
fields not listed)
Field Description
----- ------------------------------------------------------------------
4 User Code
5 ID Number
6 Transaction date in MM/DD/YY format
Transaction Record (contains 64 fields - don't know what is contained in the
fields not listed)
Field Description
----- ------------------------------------------------------------------
5 $1.23 stored as 00001.230
8 Client/Matter number - can have a "." or no separator between the
client and matter number
Note: The User Code and ID Number fields are only displayed on a list
of rejected transactions that do not successfully merge in with TABS III.
Sample TRAN_CMS.TXT data file
Notes:
1) Each record ends with a semicolon character. The sample data has a header
record followed by 3 transaction records followed by another header record
followed by 2 transaction records.
2) Each header record is composed of 2 lines. This data was NOT reformatted
for this document - this is the way the data is exported out of the Pitney
Bowes system.
3) Each transaction record is composed of 5 lines. This data was NOT
reformatted for this document - this is the way the data is exported out
of the Pitney Bowes system.
7B5B,00000,02,01, USPS,05/06/93,11:40, ,0106,05,04/07/93, ,
E840,00001,04/08/93,04/08/93, , , ,;
42EE,00002,0001, ,00000.290,00000.000,00000.000, 10000,000 00.00,A,01, ,
5296,00003, USPS,40,0001,0,00000.000,0,00000.000,0,00000.000,0,00000.000,0, ,
F4C7,00004,000000.000,00000.000,0,000000.000,00000.000,0,000000.000,00000.000, ,
54C4,00005,0,0,000000.000,00000.000,0,00000.000,0,00000.000,0,000000.000, ,
088F,00006,00000.000,0,000000.000,0,00000.000, ,;
209E,00007,0002, ,00000.580,00000.000,00000.000, 10100,000 00.00,A,01, ,
F2CB,00008, USPS,40,0002,0,00000.000,0,00000.000,0,00000.000,0,00000.000,0, ,
72EF,00009,000000.000,00000.000,0,000000.000,00000.000,0,000000.000,00000.000, ,
DA59,00010,0,0,000000.000,00000.000,0,00000.000,0,00000.000,0,000000.000, ,
E06B,00011,00000.000,0,000000.000,0,00000.000, ,;
2B95,00012,0003, ,00000.290,00000.000,00000.000, 12345,000 00.00,A,01, ,
83C4,00013, USPS,40,0001,0,00000.000,0,00000.000,0,00000.000,0,00000.000,0, ,
2595,00014,000000.000,00000.000,0,000000.000,00000.000,0,000000.000,00000.000, ,
8596,00015,0,0,000000.000,00000.000,0,00000.000,0,00000.000,0,000000.000, ,
D9DD,00016,00000.000,0,000000.000,0,00000.000, ,;
DBB6,00017,02,03, USPS,05/06/93,11:40, ,0133,05,04/08/93, ,
E2B7,00018,04/09/93,04/09/93, , , ,;
E9DB,00019,0001, ,00000.520,00000.000,00000.000, 88888,000 01.23,A,03, ,
3FFC,00020, USPS,41,0001,0,00000.000,0,00000.000,0,00000.000,0,00000.000,0, ,
695E,00021,000000.000,00000.000,0,000000.000,00000.000,0,000000.000,00000.000, ,
C95D,00022,0,0,000000.000,00000.000,0,00000.000,0,00000.000,0,000000.000, ,
8003,00023,00000.000,0,000000.000,0,00000.000, ,;
EE46,00024,0002, ,00000.520,00000.000,00000.000, 88888,000 01.81,A,03, ,
D68B,00025, USPS,41,0001,0,00000.000,0,00000.000,0,00000.000,0,00000.000,0, ,
E650,00026,000000.000,00000.000,0,000000.000,00000.000,0,000000.000,00000.000, ,
202A,00027,0,0,000000.000,00000.000,0,00000.000,0,00000.000,0,000000.000, ,
1A18,00028,00000.000,0,000000.000,0,00000.000, ,;
================================================================================
Format 3: Format for J-700 or Star 700
Data File: TRAN_CMS.TXT
Note: The format for the J-700 or Star 700 can be in a fixed length format
or a variable length format. In either case, exactly the same fields are present
in the source file.
File Type: Fixed Length (record length = 37 bytes) or Variable Length (comma
delimited)
TRAN_CMS.TXT File Layout (Fixed Length)
Name Start Length Description
------- ----- ------ ---------------------------------------------------
Account 1 10 Client/Matter number - can have "." or no separator
between client and matter numbers
Amount 11 8 $1.23 stored as 1.230 (padded with spaces on left)
Date 21 6 Transaction date in YYMMDD format
Carrier 27 5 Used in descriptions
Service 32 4 Used in descriptions
Note: The Carrier and Service fields are only displayed on a list of rejected
transactions that do not successfully merge in with TABS III.
Sample fixed length TRAN_CMS.TXT data file
Notes:
1) The first 3 lines are not part of the TRAN_CMS.TXT file.
2) The "[" and "]" characters have been added to illustrate where the carriage
return/line feed combination would appear in each record.
1 2 3
1234567890123456789012345678901234567
-------------------------------------
100.00 2.90019970329POS 1C []
101.00 12.65019970329POS IL []
123.45 0.27619970329POS 1N []
102.00 2.90019970329POS 1C []
103.00 0.26719970329POS 1B []
200.01 0.24219970329POS 1Z []
200.02 2.90019970329POS 1C []
20001 0.24219970329POS 1Z []
20002 2.90019970329POS 1C []
20003 30.22019970426POS 1C []
30000 2.90019970426POS 1C []
40000 27.33019970426POS 1C []
=== O R ===
TRAN_CMS.TXT File Layout (Variable Length)
Field Is Field
Number Converted? Field Description
------ ---------- ------------------------------------------------------------
1 Yes Client/Matter number - can have "." or no separator
between client and matter numbers
2 Yes $1.23 stored as 1.230 (padded with spaces on left)
3 Yes Transaction date in YYMMDD format
4 Yes Carrier - used in descriptions
5 Yes Service - used in descriptions
Note: The Carrier and Service fields are only displayed on a list of
rejected transactions that do not successfully merge in with TABS III.
Sample variable length TRAN_CMS.TXT data file
"100.00","2.90","19970329","POS","1C"
"101.00","12.65","19970329","POS","IL"
"123.45","0.27","19970329","POS","1N"
"102.00","2.90","19970329","POS","1C"
"103.00","0.26","19970329","POS","1B"
"200.01","0.24","19970329","POS","1Z"
"200.02","2.90","19970329","POS","1C"
"20001","0.24","19970329","POS","1Z"
"20002","2.90","19970329","POS","1C"
"20003","30.22","19970426","POS","1C"
"30000","2.90","19970426","POS","1C"
"40000","27.33","19970426","POS","1C"
==============================================================================
Format 4: Format for Ascent/Solo
Data File: TRAN_CMS.TXT
File Type: Variable Length (comma-delimited)
TRAN_CMS.TXT File Layout
Field Is Field
Number Converted? Field Description
------ ---------- ------------------------------------------------------------
1 Yes Client/Matter number - can have a "/" or "-" or "." or no
separator between the client and matter number
2 Yes Timekeeper
3 No User Description 1
4 No User Description 2
5 Yes Date of Shipment (MM/DD/YYYY)
6 No Time of Day in HH:MM format (military time)
7 Yes All Carrier Charges ($1.23 stored as 1.23)
8 No Number of Pieces
9 Yes Carrier Code
10 No Service Type
Note: The Timekeeper and Carrier Code fields are only displayed on a
list of rejected transactions that do not successfully merge in with TABS III.
Sample TRAN_CMS.TXT data file
"100.00","1111"," "," ",07/23/1997,"16:19",3.00,1,"POS","1C"
"101-00","2222"," "," ",07/23/1997,"16:19",6.40,20,"POS","1C"
"123/45","1111"," "," ",07/24/1997,"16:20",3.20,10,"POS","1C"
"102.00","1111"," "," ",07/24/1997,"16:20",3.00,1,"POS","1C"
"103-00"," "," "," ",07/25/1997,"11:50",8.40,1,"POS","1C"
"200/01","1111"," "," ",07/25/1997,"16:19",0.00,1,"POS","1C"
"200.02","2222"," "," ",07/26/1997,"16:19",6.40,20,"POS","1C"
"200-03","1111"," "," ",07/26/1997,"16:20",3.20,10,"POS","1C"
"300/00","1111"," "," ",07/27/1997,"16:20",3.00,1,"POS","1C"
"402.00"," "," "," ",07/27/1997,"11:50",8.40,1,"POS","1C"
==============================================================================
Format 5: Format for Accutrac
Data File: TRAN_CMS.TXT
File Type: Variable Length (comma-delimited)
TRAN_CMS.TXT File Layout
Field Is Field
Number Converted? Field Description
------ ---------- ------------------------------------------------------------
1 Yes Date (Month/Day/Year)
2 No Transaction Type (postage transactions are type S)
3 No Address of Terminal
4 No Elapsed Time
5 No End of Transaction Time of Day (hours:minutes:seconds)
6 No Piece Count
7 No Reserved for Internal Use
8 Yes Account - converted as the Client/Matter number - can have
a "/" or "-" or "." or no separator between the client
and matter number.
9 No Reserved for Internal Use
10 No Sub Account
11 No Sub Sub Account
12 No Job ID
13 Yes Carrier
14 No Class
15 No Surcharge
16 Yes Amount
17 No Reserved for Internal Use
18 No MDS Error
19 No Serial Number
20 No Ascending Register
21 No Descending Register
22 Yes User ID
23-38 No Special Fee Codes (16 fields total)
39-54 No Special Fee Amounts (16 fields total)
Note: The User ID and Carrier fields are only displayed on a list of
rejected transactions that do not successfully merge in with TABS III.
Sample TRAN_CMS.TXT data file
Note: Since Accutrac records are quite long, each record has been
divided into 3 sections with sections 2 and 3 wrapped to the next line and
indented 5 spaces. "Actual" records in the real world would have 1 line per
transaction no matter how long they were.
7/1/01,S,A0,0:06,16:12:05,1,0,100.00,,,,,1,6,.000,3.000,37089,,8358649,
20602.775,197.225,RSM,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0
7/2/01,S,A0,0:09,16:07:18,1,0,101-00,,,,,1,6,.000,6.400,37088,,8358649,
20602.435,197.565,RSM,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0
7/3/01,S,A0,0:24,16:06:28,7,0,123/45,,,,,1,6,.000,3.200,37087,,8358649,
20600.025,199.975,RSM,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0
7/4/01,S,A0,0:04,16:05:45,1,0,102.00,,,,,1,6,.000,3.000,37080,,8358649,
20597.645,202.355,RSM,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0
7/5/01,S,A0,0:07,16:05:13,2,0,103-00,,,,,1,6,.000,8.400,37079,,8358649,
20597.305,202.695,RSM,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0
7/6/01,S,A0,0:11,16:04:34,2,0,200/01,,,,,1,6,.000,0.000,37077,,8358649,
20596.165,203.835,RSM,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0
7/7/01,S,A0,0:13,16:03:56,1,0,200.02,,,,,1,6,.000,6.400,37075,,8358649,
20595.485,204.515,RSM,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0
7/8/01,S,A0,0:17,11:24:26,1,0,200-03,,,,,1,6,.000,3.200,37074,,8358649,
20594.225,205.775,2,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0
7/9/01,S,A0,1:03,10:15:42,4,0,300/00,,,,,1,6,.000,3.000,37073,,8358649,
20593.885,206.115,RSM,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0
7/10/01,S,A0,0:05,19:04:40,1,0,402.00,,,,,1,6,.000,8.400,37069,,8358649,
20591.605,208.395,RSM,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0
==============================================================================
Validation File: The PITNEY program can create a client validation file
named CLIENT.DAT in 4 different formats. The validation file option is only
available if you have a Pitney Bowes J-700/Star 700 or an Ascent/Solo. There
will be a record in the validation file for each active client in TABS III.
Format for J-700/Star 700
-------------------------
<c/m num ><client/matter name>
<c/m num ><client/matter name>
<c/m num ><client/matter name>
.
. (and so on for all clients in TABS III)
.
--OR--
<c/m num ><client/matter name search>
<c/m num ><client/matter name search>
<c/m num ><client/matter name search>
.
. (and so on for all clients in TABS III)
.
Notes:
1) The CLIENT.DAT file is written in a fixed length ASCII text format.
2) The text "<c/m num >" stands for the the TABS III client/matter number.
It can be a maximum of 10 characters long. If the client/matter number is
less than 10 characters long, it is padded with spaces on the right to be
exactly 10 characters long. If the client/matter number is greater than
10 characters long, it will be truncated on the right.
3) The text "<client/matter name>" stands for the TABS III client/matter name.
It can be a maximum of 20 characters long. If the client/matter name is
less than 20 characters long, it is padded with spaces on the right to be
exactly 20 characters long. If the client/matter name is greater than 20
characters long, it will be truncated on the right.
4) The text "<client/matter name search>" stands for the TABS III client/matter
name search. It can be a maximum of 20 characters long. However, since the
client/matter name search is less than 20 characters long, it is padded with
spaces on the right to be exactly 20 characters long.
Format for Ascent/Solo
----------------------
"<client/matter number>","<client/matter name>"
"<client/matter number>","<client/matter name>"
"<client/matter number>","<client/matter name>"
.
. (and so on for all clients in TABS III)
.
--OR--
"<client/matter number>","<client/matter name search>"
"<client/matter number>","<client/matter name search>"
"<client/matter number>","<client/matter name search>"
.
. (and so on for all clients in TABS III)
.
Notes:
1) The CLIENT.DAT file is written in a comma delimited ASCII text format.
2) Both fields will be enclosed in double quotes.
3) The text "<client/matter number>" stands for the TABS III client/matter
number. It can be a maximum of 20 characters long, though it may be less
than that. In fact, TABS III only allows client/matter numbers up to a
maximum length of 12 characters.
4) The text "<client/matter name>" stands for the TABS III client/matter name.
It can be a maximum of 20 characters long, though it may be less than
that. If the client/matter name is greater than 20 characters long, it
will be truncated on the right.
5) The text "<client/matter name search>" stands for the TABS III client/matter
name search. It can be a maximum of 20 characters long, though it may be
less than that. In fact, the client/matter name search is a maximum of 16
characters, so it will always be less than the maximum.