Renewal Notice Export Formats
File type:
There are four renewal notice formats that will export renewal information to ASCII files. The “Export” format is fixed length. The “Export Delimited” has the same fields but is pipe delimited. The “Detailed Export” and “Detailed Export 2” formats are also pipe delimited, but contain extra fields. If renewal notices are exported to the “Detailed Export” or “Detailed Export 2” formats and PRINT GRACE OWED is set to “y”, grace subscribers will be exported in the same file, but in the Grace Owed format.
Location:
/dti/exchange/cm
. The file name will be renewalsMMDDYY-nnn
, where MMDDYY are the month, day and year respectively, nnn is a sequence number for that day. For example, if renewal notices were run twice for the November 15, 2009, the file names would be renewals111509-001 and renewals111509-002.
Export and Export Delimited
Record | L | Field |
---|---|---|
Subscription Data | 2 | S1 (Subscription data begins) |
| 10 | Subscription # |
| 8 | Delivery Schedule |
| 10 | Expire Date |
| 12 | Days of Week 1 (currently not used) |
| 12 | Days of Week 2 (delivery schedule again) |
| 30 | Publication Name |
| 39 | Lockbox Scan Line Data (see About Scan Lines). Actual length varies if using the “Export Delimited” format, depending on the number of rates exported. This number is determined by the Business Rule, How many rate terms do you export and include in the scan line? |
| 10 | Renewal Run Date |
| 7 | Renewal or Invoice |
| 1 | Renewal Number |
| 8 | Start Reason Code |
| 3 | Number of Payments Since Start |
| 10 | Subscription term Start Date |
| 10 | Subscription Term End Date (for start-and-bill subscribers, start date plus smallest term) |
| 3 | Copies [day of week] (7 fields). Number of copies subscriber receives on each day of the week |
|
|
|
Carrier Data | 2 | C1 (Carrier data begins) |
| 30 | Carrier Name |
| 5 | Carrier Home Area Code |
| 8 | Carrier Home Phone |
|
|
|
Bill-to Data | 2 | B1 (Bill-to data begins) |
| 30 | Bill-to Name |
| 90 | Bill-to Address (3 fields of 30) |
| 10 | ZIP |
| 4 | ZIP Extension |
| 3 | Delivery Point Code |
| 28 | Bill-to Carrier Route or Postal Route |
| 3 | Bill-to Indicator (“yes” or “no”) |
| 10 | Bill-to Occupant ID |
| 10 | Bill-to Address ID |
| 31 | IMB (Intelligent Mail Barcode). Exported only if Presort is being used; otherwise blank. |
| 31 | Encoded IMB, mixed-case. Exported only if Presort is being used; otherwise blank. |
| 31 | Encoded IMB, upper-case. Exported only if Presort is being used; otherwise blank. |
|
|
|
Delivery Data | 2 | D1 (Delivery data begins) |
| 30 | Deliver-to Name |
| 90 | Deliver-to Address (3 fields of 30) |
| 10 | ZIP |
| 4 | ZIP Extension |
| 3 | Delivery Point code |
| 8 | Delivery Route |
| 5 | Subscription Home Area Code |
| 8 | Subscription Home Phone |
|
|
|
Rate Data |
| Note: The actual number of subscription rates exported is driven by the Business Rule, How many rate terms do you export and include in the scan line? Four (the default) are shown here. |
2 | R1 (Rates data begins) | |
20 | Subscription Rate Description (1) | |
| 10 | Subscription Rate Before Tax (1) |
| 10 | Subscription Rate (1) |
| 20 | Subscription Rate Description (2) |
| 10 | Subscription Rate Before Tax (2) |
| 10 | Subscription Rate (2) |
| 20 | Subscription Rate Description (3) |
| 10 | Subscription Rate Before Tax (3) |
| 10 | Subscription Rate (3) |
| 20 | Subscription Rate Description (4) |
| 10 | Subscription Rate Before Tax (4) |
| 10 | Subscription Rate (4) |
| 20 | Rate Code |
|
|
|
Tax Data |
| Note: The actual number of tax amounts exported is driven by the Business Rule, How many rate terms do you export and include in the scan line? Four sets (the default) are shown here. |
2 | T1 (Tax data begins) | |
10 | Country Tax Amount (1) | |
| 10 | State Tax Amount (1) |
| 10 | County Tax Amount (1) |
| 10 | City Tax Amount (1) |
| 10 | Country Tax Amount (2) |
| 10 | State Tax Amount (2) |
| 10 | County Tax Amount (2) |
| 10 | City Tax Amount (2) |
| 10 | Country Tax Amount (3) |
| 10 | State Tax Amount (3) |
| 10 | County Tax Amount (3) |
| 10 | City Tax Amount (3) |
| 10 | Country Tax Amount (4) |
| 10 | State Tax Amount (4) |
| 10 | County Tax Amount (4) |
| 10 | City Tax Amount (4) |
|
|
|
Message Data | 2 | M1 (Messages data begins) |
| 30 | Copy Message (1) |
| 30 | Copy Message (2) |
| 30 | Country Tax Message |
| 30 | State Tax Message |
| 30 | County Tax Message |
| 30 | City Tax Message |
| 20 | Purchase Order Number |
|
|
|
Messages Continued | 2 | M2 (Messages continued) |
| 30 | Renewal Period Message (1) |
| 30 | Renewal Period Message (2) |
| 30 | General Message |
| 120 | Rate Code Message (4 fields of 30) |
|
|
|
Expire Data | 2 | E1 (Expire date data begins) |
| 200 | Expire Date Change Messages (5 fields of 40) |
| 2 | E2 (Expire date data cont.) |
| 200 | Expire Date Change Messages (5 fields of 40) |
Detailed Export
Record | Max Length | Field |
---|---|---|
Subscription Data | 2 | S1 (Subscription data begins) |
| 10 | Subscription # |
| 8 | Delivery Schedule |
| 10 | Expire Date |
| 10 | End Grace Date (blank if not in Grace) |
| - | Days of Week 1 (currently not used) |
| 8 | Days of Week 2 (displays delivery schedule) |
| 30 | Publication Name |
| 39 | Lockbox scan line data. Actual length varies depending on the number of rates exported, which is determined by the Business Rule, How many rate terms do you export and include in the scan line? See see About Scan Lines for more information about scan lines. |
| 10 | Renewal Run Date |
| 7 | Renewal, Invoice or Grace |
| 10 | Last Renewal Date |
| 3 | Renewal Number |
| 8 | Start Reason Code |
| 3 | Number of Payments Since Start |
| 3 | Copies [day of week] (7 fields). Number of copies subscriber receives on each day of the week |
|
|
|
Carrier Data | 2 | C1 (Carrier data begins) |
| 42 | Carrier Name |
| 3 | Carrier Home Area Code |
| 8 | Carrier Home Phone |
|
|
|
Bill-to Data | 2 | B1 (Bill-to data begins) |
| 30 | Bill-to Name |
| 30 | Bill-to Address 1 |
| 30 | Bill-to Address 2 |
| 30 | Bill-to Address 3 |
| 10 | ZIP |
| 4 | ZIP Extension |
| 3 | Delivery Point Code |
| 28 | PO Route Type and PO Route Number (or Route ID and Truck ID if printing by route) |
| 3 | Bill-to Indicator (“yes” or “no”) |
| 10 | Bill-to Occupant ID |
| 10 | Bill-to Address ID |
| 31 | IMB (Intelligent Mail Barcode). Exported only if Presort is being used; otherwise blank. |
| 31 | Encoded IMB, mixed-case. Exported only if Presort is being used; otherwise blank. |
| 31 | Encoded IMB, upper-case. Exported only if Presort is being used; otherwise blank. |
|
|
|
Delivery Data | 2 | D1 (Delivery data begins) |
| 30 | Deliver-to Name |
| 30 | Deliver-to Address 1 |
| 30 | Deliver-to Address 2 |
| 30 | Deliver-to Address 3 |
| 10 | ZIP |
| 4 | ZIP Extension |
| 3 | Delivery Point code |
| 8 | Delivery Route |
| 8 | Route Type |
| 3 | Subscription Home Area Code |
| 8 | Subscription Home Phone |
| 12 | Trip ID |
|
|
|
Rate Data |
| Note: 1. Rates include grace owed amounts, and new expire dates will include grace days paid since last expire. 2. The actual number of subscription rates exported is driven by the Business Rule, How many rate terms do you export and include in the scan line? Four (the default) are shown here. |
2 | R1 (Rates data begins) | |
| 20 | Subscription Rate Description (1) |
| 10 | Subscription Rate Before Tax (1) |
| 10 | Subscription Rate (1) |
| 10 | New Expire Date (1) |
| 10 | Discount Amount (1) |
| 20 | Subscription Rate Description (2) |
| 10 | Subscription Rate Before Tax (2) |
| 10 | Subscription Rate (2) |
| 10 | New Expire Date (2) |
| 10 | Discount Amount (2) |
| 20 | Subscription Rate Description (3) |
| 10 | Subscription Rate Before Tax (3) |
| 10 | Subscription Rate (3) |
| 10 | New Expire Date (3) |
| 10 | Discount Amount (3) |
| 20 | Subscription Rate Description (4) |
| 10 | Subscription Rate Before Tax (4) |
| 10 | Subscription Rate (4) |
| 10 | New Expire Date (4) |
| 10 | Discount Amount (4) |
| 10 | Subscriber’s Unallocated Balance |
|
|
|
Grace Data |
| Note: grace information will appear for subscribers who owe grace. |
2 | G1 (Grace data begins) | |
9 | Grace owed amount | |
| 9 | City tax amount |
| 9 | County tax amount |
| 9 | State tax amount |
| 9 | Country tax amount |
| 9 | Total grace owed amount |
|
|
|
Tax Data |
| Note: The actual number of tax amounts exported is driven by the Business Rule, How many rate terms do you export and include in the scan line? Four sets (the default) are shown here. |
2 | T1 (Tax data begins) | |
10 | Country Tax Amount (1) | |
| 10 | State Tax Amount (1) |
| 10 | County Tax Amount (1) |
| 10 | City Tax Amount (1) |
| 10 | Country Tax Amount (2) |
| 10 | State Tax Amount (2) |
| 10 | County Tax Amount (2) |
| 10 | City Tax Amount (2) |
| 10 | Country Tax Amount (3) |
| 10 | State Tax Amount (3) |
| 10 | County Tax Amount (3) |
| 10 | City Tax Amount (3) |
| 10 | Country Tax Amount (4) |
| 10 | State Tax Amount (4) |
| 10 | County Tax Amount (4) |
| 10 | City Tax Amount (4) |
|
|
|
Message Data | 2 | M1 (Messages data begins) |
| 30 | Copy Message 1 (If subscriber receives more than 1 copy) |
| 30 | Copy Message 2 |
| 30 | Country Tax Message |
| 30 | State Tax Message |
| 30 | County Tax Message |
| 30 | City Tax Message |
| 20 | Purchase Order Number |
| 2 | M2 (Messages continued) |
| 30 | Renewal Period Message (1) |
| 30 | Renewal Period Message (2) |
| 30 | General Message |
| 120 | Rate Code Message (4 fields) |
|
|
|
|
|
|
Expire Data |
| Note: 1. An additional E segment will appear for each adjustment to the subscriber’s expire date. And, delivery schedule changes create E1 records, even if the expire date is not changed. 2. In order to appear in the export, the reason code of a transaction must be set up to print on renewals. |
2 | E1 (Expire data begins) | |
10 | Transaction Date | |
| 30 | Transaction Description |
| 8 | Reason Code |
| 37 | Vacation Dates (if restart) |
| 9 | Value of adjustment |
| 5 | Days adjusted |
| 9 | Transfer Amount |
| 5 | Transfer Days |
| 9 | Payment Amount |
| 9 | Tip Amount |
| 9 | Coupon Amount |
| 30 | Payment adjustment description (if multiple adjustments, adjustments codes will be comma-separated) |
| 9 | Payment adjustment amount |
| 9 | Update expire adjustment amount |
|
|
|
Grace Transactions |
| Note: a G2 segment will appear for each transaction that changed the grace owed amount (for example, a perm stop). |
2 | G2 (Grace transactions begin) | |
12 | Tran Type ID of transaction | |
| 10 | Tran Date |
| 30 | Renewal Description (based on reason code of transaction). |
|
|
|
Additional fields | 2 | F1 (Additional fields begin) |
| 8 | Renewal Delivery Override Code (if renewal delivery method was overridden, otherwise blank) |
| 7 | Route Walk Sequence |
| 7 | Trip Walk Sequence |
|
|
|
Transportation Cost |
| Note: a TC segment will only appear if the Taxing add-on is purchased, and the subscriber is taxed. |
2 | TC (Transportation cost segment begins) | |
40 | Transportation cost (one for each term) | |
|
| Note: The actual number of terms exported is driven by the Business Rule, How many rate terms do you export and include in the scan line? The default is four. |
|
|
|
In-Grace Rate Data (See Note below.) | 2 | Q1 (Prior rate fields begin) |
| 20 | Subscription Rate Description (e.g., “28 days”) |
| 100 | Subscription Rate Code (if multiple rates exist, rate codes will be comma-separated) |
| 10 | Subscription Rate Before Tax |
| 10 | Subscription Rate After Tax |
| 10 | Discount Amount |
|
|
|
Note: |
| The Q1 and Q2 segments will be exported if the Business Rule, Should subscribers get separate records exported for each rate code they are on while in grace? (Subscriber Billing section), is set to “yes.” These segments contain rate data for in-grace subscribers who have a rate change during the grace period: |
|
| |
|
| |
|
| |
Current In-Grace Rate Data (See Note above.) | 2 | Q2 (Current rate fields begin) |
| 20 | Subscription Rate Description [1] |
| 10 | Subscription Rate Before Tax [1] |
| 10 | Subscription Rate [1] |
| 10 | Discount Amount [1] |
| 9 | Rate By Day [1] x 7 days |
| 12 | Cost By Day [1] x 7 days |
| 9 | Discount By Day [1] x 7 days |
| 20 | Subscription Rate Description [2] |
| 10 | Subscription Rate Before Tax [2] |
| 10 | Subscription Rate [2] |
| 10 | Discount Amount [2] |
| 9 | Rate By Day [2] x 7 days |
| 12 | Cost By Day [2] x 7 days |
| 9 | Discount By Day [2] x 7 days |
| 20 | Subscription Rate Description [3] |
| 10 | Subscription Rate Before Tax [3] |
| 10 | Subscription Rate [3] |
| 10 | Discount Amount [3] |
| 9 | Rate By Day [3] x 7 days |
| 12 | Cost By Day [3] x 7 days |
| 9 | Discount By Day [3] x 7 days |
| 20 | Subscription Rate Description [4] |
| 10 | Subscription Rate Before Tax [4] |
| 10 | Subscription Rate [4] |
| 10 | Discount Amount [4] |
| 9 | Rate By Day [4] x 7 days |
| 12 | Cost By Day [4] x 7 days |
| 9 | Discount By Day [4] x 7 days |
| 10 | Subscriber’s unallocated balance |
|
|
|
End | 2 | !! (end of line) |
Detailed Export 2
Record/Segment | Max Length | Field |
---|---|---|
Group Start |
| Note: An SG record will only appear if subscription is first in the group |
| 2 | SG (Group start data begins) |
| 30 | Bill-to Name for Subscription Group |
| 30 | Bill-to Address for Subscription Group 1 |
| 30 | Bill-to Address for Subscription Group 2 |
| 30 | Bill-to Address for Subscription Group 3 |
| 10 | ZIP |
| 4 | ZIP Extension |
| 3 | Delivery Point Code |
| 28 | Route/Carrier Route/Truck |
| 31 | IMB (Intelligent Mail Barcode). Exported only if Presort is being used; otherwise blank. |
| 31 | Encoded IMB, mixed-case. Exported only if Presort is being used; otherwise blank. |
| 31 | Encoded IMB, upper-case. Exported only if Presort is being used; otherwise blank. |
|
|
|
Subscription Data | 2 | S1 (Subscription data begins) |
| 10 | Subscription # |
| 8 | Delivery Schedule |
| 10 | Expire Date |
| 10 | End Grace Date (blank if not in Grace) |
| - | Days of Week 1 (currently not used) |
| 8 | Days of Week 2 (displays delivery schedule) |
| 30 | Publication Name |
| 39 | Lockbox scan line data. Actual length varies depending on the number of rates exported, which is determined by the Business Rule, How many rate terms do you export and include in the scan line? See About Scan Lines for more information about scan lines. |
| 10 | Renewal Run Date |
| 7 | Renewal, Invoice or Grace |
| 10 | Last Renewal Date |
| 3 | Renewal Number |
| 8 | Start Reason Code |
| 3 | Number of Payments Since Start |
| 3 | Copies [day of week] (7 fields). Number of copies subscriber receives on each day of the week |
|
|
|
Subscription Data 2 | 2 | S2 (second Subscription segment begins) |
| 10 | Original Start Date |
| 8 | Source of Last Start |
| 8 | Sub-source of Last Start |
| 11 | Credit Status |
| 15 | Occupant Type |
| 11 | Census Tract |
| 10 | Dwelling Type |
| 6 | AAM Zone |
| 8 | Method of Renewal Delivery |
|
|
|
Demographic Data |
| Note: an X1 segment will appear for each address or occupant demographic answered for the subscriber. |
| 2 | X1 (Demographic data begins) |
| 8 | Demographic Type (Occupant or Address) |
| 60 | Demographic Question |
| 12 | Demographic Answer |
|
|
|
Carrier Data | 2 | C1 (Carrier data begins) |
| 42 | Carrier Name |
| 3 | Carrier Home Area Code |
| 8 | Carrier Home Phone |
| 8 | District Manager |
| 8 | Zone Manager |
| 8 | Regional Manager |
| 8 | Area Manager |
| 8 | Depot |
| 8 | Depot Drop Order |
| 8 | Truck |
| 8 | Route’s Drop Sequence on Truck |
|
|
|
Bill-to Data | 2 | B1 (Bill-to data begins) |
| 85 | Bill-to Name (+ potential Other Name) |
| 60 | Bill-to Address 1 |
| 30 | Bill-to Address 2 |
| 30 | Bill-to Address 3 |
| 10 | ZIP |
| 4 | ZIP Extension |
| 3 | Delivery Point Code |
| 28 | PO Route Type and PO Route Number (or Route ID and Truck ID if printing by route) |
| 3 | Bill-to Indicator (“yes” or “no”) |
| 10 | Bill-to Occupant ID |
| 10 | Bill-to Address ID |
| 55 | Bill-to full billing name |
| 30 | Bill-to other name |
| 31 | IMB (Intelligent Mail Barcode). Exported only if Presort is being used; otherwise blank. |
| 31 | Encoded IMB, mixed-case. Exported only if Presort is being used; otherwise blank. |
| 31 | Encoded IMB, upper-case. Exported only if Presort is being used; otherwise blank. |
| 3 | Digital Sales Indicator (“yes” or “no”) |
|
|
|
Delivery Data | 2 | D1 (Delivery data begins) |
| 85 | Deliver-to Name (+ potential Other Name) |
| 60 | Deliver-to Address 1 |
| 30 | Deliver-to Address 2 |
| 30 | Deliver-to Address 3 |
| 10 | ZIP |
| 4 | ZIP Extension |
| 3 | Delivery Point code |
| 8 | Newspaper Delivery Route (route ID) |
| 8 | Route Type |
| 3 | Subscription Home Area Code |
| 8 | Subscription Home Phone |
| 12 | Trip ID |
| 55 | Full delivery name |
| 30 | Other name |
|
|
|
Rate Data |
| Note: 1. Rates do not include grace owed amounts. New expire dates will include grace days paid since last expire 2. The actual number of subscription rates exported is driven by the Business Rule, How many rate terms do you export and include in the scan line? Four is the default. Two rates are shown here. 3. If TC segments exist, they will be interspersed with R1 records. 4. For combo subscriptions, the R1 record contains the total amounts for the combo subscription. The R2 records contains amounts for each component of the combo (i.e., there will be an R2 for print and an R2 for online) 5. If you charge premiums for bonus days, a “PD” record segment will be exported for each premium day in the term. Each PD segment will have a sequence (e.g. “PD1”, “PD2”) followed by the premium date, description, and amount. For example, if a term included three premium days, PD1, PD2 and PD3 record segments would be exported. If a term included no premium days, no PD segments would be exported. |
| 2 | R1 (Rates data begins) |
| 20 | Rate Code |
| 20 | Subscription Rate Description (1) |
| 10 | Subscription Rate Before Tax (1) |
| 10 | Subscription Rate (1) |
| 10 | Delivery Fee (1) . Optional. Exported only if delivery fees are defined. |
| 10 | Premium Amount for Term (1) |
| 10 | New Expire Date (1) |
| 10 | Discount Amount (1) |
| 9 | Rate By Day (1) x 7 days |
| 12 | Cost By Day (1) x 7 days |
| 9 | Discount By Day (1) x 7 days |
| 4 | PD1 (first premium day) |
| 10 | Premium Date (1) |
| 30 | Premium Day Renewal Description (1) |
| 10 | Premium Day Amount (1) |
| 20 | Subscription Rate Description (2) |
| 10 | Subscription Rate Before Tax (2) |
| 10 | Subscription Rate (2) |
| 10 | Delivery Fee (2) . Optional. Exported only if delivery fees are defined. |
| 10 | Premium Amount for Term (2) |
| 10 | New Expire Date (2) |
| 10 | Discount Amount (2) |
| 9 | Rate By Day (2) x 7 days |
| 12 | Cost By Day (2) x 7 days |
| 9 | Discount By Day (2) x 7 days |
| 4 | PD1 (first premium day) |
| 10 | Premium Date (1) |
| 30 | Premium Day Renewal Description (1) |
| 10 | Premium Day Amount (1) |
| 4 | PD2 (second premium day) |
| 10 | Premium Date (2) |
| 30 | Premium Day Renewal Description (2) |
| 10 | Premium Day Amount (2) |
| 10 | Grace Owed Amount (not including taxes) |
| 10 | Grace Owed Amount (including taxes) |
| 10 | Grace Owed City Tax |
| 10 | Grace Owed County Tax |
| 10 | Grace Owed State Tax |
| 10 | Grace Owed Country Tax |
| 10 | Subscriber’s Unallocated Balance |
| 10 | Subscriber’s Uncommitted Wallet (used for premium days) This field is only exported if the Business Rule Do you bill subscribers in advance for premium days? is set to “yes” and the Business Rule Should the premium day detail be exported in renewals? is also set to “yes.” |
| 10 | Tax on Subscriber’s Uncommitted Wallet |
|
|
|
Grace Data |
| Note: grace information will appear for subscribers who owe grace. |
| 2 | G1 (Grace data begins) |
| 9 | Grace owed amount |
| 9 | City tax amount |
| 9 | County tax amount |
| 9 | State tax amount |
| 9 | Country tax amount |
| 9 | Total grace owed amount |
|
|
|
Grace Transactions |
| Note: a G2 segment will appear for each transaction that changed the grace owed amount (for example, a perm stop). |
| 2 | G2 (Grace transactions begin) |
| 12 | Tran Type ID of transaction |
| 10 | Tran Date |
| 30 | Renewal Description (based on reason code of transaction). |
|
|
|
Previous Grace Data |
| Note: only grace owed from previous subscription periods will be included. |
| 2 | G3 (Previous grace data begins) |
| 9 | Grace owed amount |
| 9 | City tax amount |
| 9 | County tax amount |
| 9 | State tax amount |
| 9 | Country tax amount |
| 9 | Total grace owed amount |
|
|
|
Grace Accrual | 2 | G4 (Grace accrual begins) |
| 9 | Grace accrual amount |
| 9 | City tax amount |
| 9 | County tax amount |
| 9 | State tax amount |
| 9 | Country tax amount |
| 9 | Total grace accrual amount |
|
|
|
Tax Data |
| Note: The actual number of tax amounts exported is driven by the Business Rule, How many rate terms do you export and include in the scan line? Four sets (the default) are shown here. |
| 2 | T1 (Tax data begins) |
| 10 | Country Tax Amount (1) |
| 10 | State Tax Amount (1) |
| 10 | County Tax Amount (1) |
| 10 | City Tax Amount (1) |
| 10 | Country Tax Amount (2) |
| 10 | State Tax Amount (2) |
| 10 | County Tax Amount (2) |
| 10 | City Tax Amount (2) |
| 10 | Country Tax Amount (3) |
| 10 | State Tax Amount (3) |
| 10 | County Tax Amount (3) |
| 10 | City Tax Amount (3) |
| 10 | Country Tax Amount (4) |
| 10 | State Tax Amount (4) |
| 10 | County Tax Amount (4) |
| 10 | City Tax Amount (4) |
|
|
|
Message Data | 2 | M1 (Messages data begins) |
| 30 | Copy Message (1) |
| 30 | Copy Message (2) |
| 30 | Country Tax Message |
| 30 | State Tax Message |
| 30 | County Tax Message |
| 30 | City Tax Message |
| 20 | Purchase Order Number |
|
|
|
More Message Data | 2 | M2 (Messages continued) |
| 30 | Renewal Period Message (1) |
| 30 | Renewal Period Message (2) |
| 30 | General Message |
| 120 | Rate Code Message (4 fields) |
|
|
|
Expire Data |
| Note: an E1 segment will appear for each adjustment to the subscriber’s expire date since the last renewal notice was sent. |
| 2 | E1 (Expire data begins) |
| 10 | Transaction Date |
| 30 | Transaction Description |
| 8 | Reason Code |
| 37 | Comments. If payment, carrier tip. If stop, vacation dates. If transfer in, transfer from subscriber. If transfer out, transfer to subscriber or donation code. |
| 9 | Value of adjustment |
| 5 | Days adjusted |
| 9 | Transfer Amount (if transfer in or out) |
| 5 | Transfer Days (if transfer out does not have an amount) |
| 9 | Payment Amount (if payment - includes tip) |
| 9 | Tip Amount (if payment) |
| 9 | Coupon Amount (if payment) |
| 30 | Payment adjustment description (if multiple adjustments, adjustments codes will be comma-separated) |
| 9 | Payment adjustment amount |
| 9 | Update expire adjustment amount |
| 9 | Donation Amount |
|
|
|
Payment History Data |
| Note: a P1 segment will appear for each subscriber payment since the last renewal notice was sent. |
| 2 | P1 (Payment data begins) |
| 11 | Payment Amount |
| 5 | Payment Length |
| 8 | Payment Term |
| 10 | Effective Date |
| 20 | Rate Code |
| 10 | Payment Transaction Date |
| 12 | Transaction Type |
|
|
|
Last Payment |
| Note: The P2 segment will contain the last processed, uncanceled payment made during a subscriber's current office pay term. It will not include adjustment only subscription payments. |
| 2 | P2 (Payment data begins) |
| 11 | Payment Amount |
| 5 | Payment Length |
| 8 | Payment Term |
| 10 | Effective Date |
| 20 | Rate Code |
| 10 | Payment Transaction Date |
| 12 | Transaction Type |
|
|
|
Auto Renew Subscription | 2 | A1 (Auto-renew subscription data begins) |
| 11 | Tip Amount |
| 20 | Credit Card Number |
| 8 | Authorization Number |
| 5 | Credit Card Expires |
| 8 | Credit Card Verification Value |
| 9 | Bank Number |
| 8 | Bank Client Type |
| 8 | Account Type |
| 20 | Account Number |
|
|
|
Auto Renew Adjustment | 2 | A2 (Auto-renew subscription data begins) |
| 8 | Sub Adjust Code ID |
| 30 | Sub Adjust Code Description |
| 11 | Auto-renew Adjustment Amount |
|
|
|
Additional fields | 2 | F1 (Additional fields begin) |
| 8 | Renewal Delivery Override Code (if renewal delivery method was overridden, otherwise blank) |
| 7 | Route Walk Sequence |
| 7 | Trip Walk Sequence |
|
|
|
Transportation Cost |
| Note: 1. a TC segment will only appear if a transportation cost add-on is purchased, and the subscriber is taxed. 2. If TC segments exist, they will be interspersed with R1 records. |
| 2 | TC (Transportation cost segment begins) |
| 40 | Transportation cost (one for each term) Note: The actual number of terms exported is driven by the Business Rule, How many rate terms do you export and include in the scan line? The default is four. |
| 40 | Tax amount that will be remitted to state (does not include tax on transportation cost). Field exported only when using the Remit On Payment transportation cost add-on. |
|
|
|
Campaign Renewal Offer |
| Note: An O1 segment will only appear if the subscription qualified for an additional offer. There may be zero to unlimited number of O1 segments; there will be one O1 segment for each additional offer the subscriber qualifies for. |
| 2 | O1 (Offer data begins) |
| 30 | Campaign Code |
| 30 | Campaign Description |
| 20 | Campaign Rate Code |
| 30 | Campaign Tran Type |
| 8 | Campaign DeliveryScheduleID |
| 8 | Campaign Source |
| 8 | Campaign Reason |
| 3 | Campaign Auto Renew Length |
| 8 | Campaign Auto Renew Term |
| 30 | Campaign Script |
|
|
|
Campaign Rate Data |
| Note: rates do not include grace owed amounts. New expire dates will include grace days paid since last expire. There will be one O2 segment for each RateTerm. |
| 2 | O2 (Campaign Rates data begins) |
| 20 | Subscription Rate Description (payment length and term) |
| 10 | Subscription Rate Before Tax |
| 10 | Subscription Rate (cost including tax) |
| 10 | New Expire Date |
| 10 | Discount Amount |
| 9 | Sunday Rate |
| 9 | Monday Rate |
| 9 | Tuesday Rate |
| 9 | Wednesday Rate |
| 9 | Thursday Rate |
| 9 | Friday Rate |
| 9 | Saturday Rate |
| 12 | Sunday Extra Cost |
| 12 | Monday Extra Cost |
| 12 | Tuesday Extra Cost |
| 12 | Wednesday Extra Cost |
| 12 | Thursday Extra Cost |
| 12 | Friday Extra Cost |
| 12 | Saturday Extra Cost |
| 9 | Sunday Discount |
| 9 | Monday Discount |
| 9 | Tuesday Discount |
| 9 | Wednesday Discount |
| 9 | Thursday Discount |
| 9 | Friday Discount |
| 9 | Saturday Discount |
| 10 | Country Tax Amount |
| 10 | State Tax Amount |
| 10 | County Tax Amount |
| 10 | City Tax Amount |
|
|
|
Remaining Marketing Term Information | 2 | Marketing term record identifier for marketing term subscribers. One of the following:
All three records have the same format, as follows. |
| 20 | Rate code |
| 20 | Rate code description |
| 14 | Marketing term length |
| 10 | End of marketing term for “Z0” records; expire date for “Z1” and “Z2” records. |
| 10 | Amount |
| 10 | Discount Amount |
| 10 | City Tax Amount |
| 10 | County Tax Amount |
| 10 | State Tax Amount |
| 10 | Country Tax Amount |
| 9 | Sunday Rate |
| 9 | Monday Rate |
| 9 | Tuesday Rate |
| 9 | Wednesday Rate |
| 9 | Thursday Rate |
| 9 | Friday Rate |
| 9 | Saturday Rate |
| 9 | Sunday Discount |
| 9 | Monday Discount |
| 9 | Tuesday Discount |
| 9 | Wednesday Discount |
| 9 | Thursday Discount |
| 9 | Friday Discount |
| 9 | Saturday Discount |
|
|
|
30 | Occupant email address | |
|
|
|
Combo Rates Data |
| Note: R2 segments are exported only for combo subscriptions. One R2 record will be exported for each component of the combo (i.e., one R2 for print, another R2 for online, etc.). The R1 record contains the total amounts for the combo subscription. Also note that the applicable fields from Subscription ID through New Expire Date are exported as a group for each piece of the combo. |
| 2 | R2 (Combo rates data begins) |
| 10 | Combo ID |
| 10 | Subscription ID |
| 10 | Product ID |
| 8 | Delivery Method |
| 8 | Delivery Schedule ID |
| 20 | Rate Code ID |
| 20 | Rate Description |
| 10 | Rate Amount Before Tax and Delivery Fee |
| 10 | Rate Amount |
| 10 | Total Tax Amount |
| 10 | City Tax Amount |
| 10 | County Tax Amount |
| 10 | State Tax Amount |
| 10 | Country Tax Amount |
| 10 | Delivery Fee Amount |
| 10 | New Expire Date |
|
|
|
End | 2 | !! (end of line) |
|
|
|
End Group |
| Note: an EG record will appear only if the subscription is the last in the group. |
| 2 | EG (End group data begins) |
| 3 | Number of subscribers in group |
Fee Tax | ||
10 | Activation Fee Tax | |
10 | Printed Bill Fee Tax | |
10 | Printed Bill City Fee Tax | |
10 | Printed Bill County Fee Tax | |
10 | Printed Bill State Fee Tax | |
10 | Printed Bill Country Fee Tax |
Grace Owed
Note: If renewal notices are exported to the “Detailed Export” or “Detailed Export 2” formats and PRINT GRACE OWED is set to “y”, grace subscribers will be exported in the same file, but in this format.
Record/Segment | Field |
---|---|
Subscription Data | S1 (Subscription data begins) |
| Subscription # |
| Delivery Schedule |
| Expire Date |
| End Grace Date (? if not in Grace) |
| Days of Week 1 (currently not used) |
| Days of Week 2 (currently not used) |
| Publication Name |
| Blank |
| Renewal Run Date |
| “Grace” |
| Last Renewal Date |
| Renewal Number |
|
|
Carrier Data | C1 (Carrier data begins) |
| Carrier Name |
| Carrier Home Area Code |
| Carrier Home Phone |
|
|
Bill-to Data | B1 (Bill-to data begins) |
| Bill-to Name |
| Bill-to Address (3 fields) |
| ZIP |
| ZIP Extension |
| Delivery Point Code |
| Blank |
|
|
Delivery Data | D1 (Delivery data begins) |
| Deliver-to Name |
| Deliver-to Address (3 fields) |
| ZIP |
| ZIP Extension |
| Delivery Point code |
| Newspaper Delivery Route |
| Route Type |
| Subscription Home Area Code |
| Subscription Home Phone |
|
|
Expire Data | Note: an E1 segment will appear for each adjustment to the subscriber’s expire date since the last renewal notice was sent . |
| E1 (Expire data begins) |
| Transaction Date |
| Transaction Description |
| Reason Code |
| Comments. If payment, carrier tip. If stop, vacation dates. If transfer in, transfer from subscriber. If transfer out, transfer to subscriber or donation code. |
| Value of adjustment |
| Days adjusted |
| Transfer Amount (if transfer in or out) |
| Transfer Days (if transfer out does not have an amount) |
| Payment Amount (if payment - includes tip) |
| Tip Amount (if payment) |
| Coupon Amount (if payment) |
| Payment adjustment description (if multiple adjustments, adjustments codes will be comma-separated) |
| Payment adjustment amount |
| Update expire adjustment amount |
| Donation Amount |
|
|
Grace Data | G1 (Grace data begins) |
| Grace owed amount |
| City tax amount |
| County tax amount |
| State tax amount |
| Country tax amount |
| Total grace owed amount |
|
|
Grace Transactions | Note: a G2 segment will appear for each transaction that changed the grace owed amount (e.g., a perm stop). |
| G2 (Grace transactions begin) |
| Tran Type ID of transaction |
| Tran Date |
| Renewal Description (based on reason code of transaction). |
|
|
Grace Data | Note: G3 contains the prior grace owed (grace owed prior to the expiration date) |
| G3 (Prior grace data begins) |
| Prior grace owed |
| Prior city tax amount |
| Prior county tax amount |
| Prior state tax amount |
| Prior country tax amount |
| Prior total grace owed amount |
|
|
End | !! (end of line) |
Last updated