1) The document describes Verizon's order lifecycle and validation process. Orders go through COG, provisioning systems, and billing. Compensation data is loaded to validation databases for review. 2) Validated orders are returned to vendors via SFTP with payment/chargebacks calculated based on validated orders versus initial estimates. Appeals can be submitted for additional review. 3) The validation process involves searching for orders in systems like AEDW, applying status codes, and manual review through WFM to determine order status and compliance with retention requirements for compensation.

1. National Partner Operations:
End To End Validation
Compensation
January 12, 2017
1

2. Order Life Cycle (All Verizon)
2
Global Processing
OrderCreationCOGProvisioningBilling
COG:
Acts as a landing pad for the various order entry systems. If
Cog is either unable to accept the order, or it is unable to
successfully hand it off to a provisioning system the order is
considered to be in Shadow Queue.
SQ
CLEARED
CANCELLED
Products Added to Customer Billing Profile
C2G CS ROCS
NSOP
SSP
FIOS VOICE
SSP
FIOS
INTERNET
SSP
FIOS TV
SSP
PARTNER
REFERAL
VASIP/DTV
CoA .COM
NO
PRODUCT
ACTIVATES
CANCELLED
Alternate Validation Files compiled from automated feeds
received fromC2G, CS, and ROCS entry systems. CoA sales
are only tracked if entered via the Help Desk tracker by an
ACSC agent.
AEDW visibility to order transaction activity and status reporting
does not occur until the order has successfully loaded to a
Provisioning System..

3. 3
C2G
CS
ROCS
De Dup Audit:
Record
rejected if
already exists
Adjustments
Help Desk
Supplemental
Executive Appeals
V
a
l
i
d
a
t
i
o
n
Raw Data (compensable and non compensable products)
loaded to validation.dbo.tf_dlydata_pivot
At End of Sales Period: Compensable items for prior sales period
loaded to validation.dbo.tf_[channel]_pct_sdata
Upon load, QI/Fraud indicators applied and review file passed to
Quality Investigations for review and customer contact.
P!/Initial Invoice Generated passed to IVQ via CVS Job in SQL posed to
vendor as flat file via LZ3 Sftp site. Payment reflects total potential
cash value * Rolling Install Rate for the channel If the vendor identifies
any products missing from the Initial data file they are able to submit
these items manually as supplemental files via LZ3 Sftp. Any accepted
supplemental records will be appended to the active sales file at the
time of submission.
At retention date – 1 P2 Loaded for validation review to
Validation..dbo.tf_validation_data
Upon completion of review a status is provided for every record in the
file. Results are posted to vendor via LZ3 Sftp site.
Upon receipt of validated p2 results Vendor may opt to Appeal. If the
vendor feels that any records require an additional review the vendor
will post an notice of appeal to the LZ3 site. Upon receipt we will
reprocess any unpaid items for additional review. Any items that have
been rejected as fraud are excluded from this process
If Appeal is requested, the disputed items will be submitted to
Validation.dbo.TF_Validation_data.
Upon expiration of the AP Review Period the AP/Final Invoice will be
generated.
The file is passed to IVQ via CVS job in SQL
The file is passed to Vendor via LZ#/Sftp site
Payment/Charge back is calculated by calculating the difference between
actual validated value of file and the estimated P1/initial invoice value.
Rolling Install Rate for Vendor is updated with current data.
Note: BigBox Retailers do not follow this same process.
BigBox Retailers follow a payment schedule where records will
continue to flow month over month until they have been identified as
installed and in service for the contractual minimum days in service
OR they have been identified as rejected as invalid orders, Cancelled,
or Disconnected.

4. 4
Validation
TF_VALIDATION_DATA
NORDIC
WFM
Validation Objective
1) Locate the Order
G-NO ORDER FOUND
2) Confirm Product Exists on Order
NP-NO PRODUCT FOUNDH-PRODUCT MISMATCH
HH-CUSTOMER MISMATCH
1B - NOT LOCATED IN ONEBILL
3) Confirm product constitutes a valid sale
W-EXISTING PRODUCTV- DOWNGRADE
J-INVALID SALE (FULL ORDER)
JK-INVALID SALE (PARTIAL ORDER)
S-DUPLICATE PRODUCT/ORDERIC-INVALID SOURCE CSSC
IW-INVALID SOURCE .COM/WEB
ZR-ZERO RATE ITEM LOCATED
T- NO TPV
X - SENT FOR CANCEL/PRE-BILLING CANCEL
Z - WELCOME CENTER REFERRALMA-MULTIPLE ACCOUNTS FOR SAME SSN
4) Confirm Order has Completed
F- NEW PRODUCT W/O WINBACK
F- NEW PRODUCT W/ WINBACK
O - PLAN CHANGEL - MOVE ORDER
N - PRODUCT CONFIRMED NEW LINE
R - PRODUCT CONFIRMED NEW PRODUCT
Q - PRODUCT CONFIRMED MIGRATION TO FIBER
C-CANCEL/DISCONNECT
5)Confirm that the Product was still in service for sufficient time to fulfill retention requirements.
C-CANCEL/DISCONNECT (Cancel Date is required on all items returned with this code. The
presence of an install date AND a cancel date denotes a disconnect.
Order Status
A – Accepted (Service is Active/Retention Satisfied): Install Date is required on all ‘A’ items.
P – order is located, but still Pending
D – Denied:
Post Validation Cleanup Filters
If an order is rejected as Disconnected where the initial activation occurred prior to the retention date and
the disconnect occurred after the retention date we will update the order to reflect an activated status as it
was active on the actual retention date.
If an order is validated as Active, but the install date occurred after the retention date we will update the
record to reflect a Pending status as it was pending on the actual retention date.
If ANY records exist on the file that do not have a validation status as of the Validation Due Date the file will
NOT be returned to SDATA. An alert will be triggered to notify the developer in charge to the process to
investigate and correct the issue.
Processing Start and Stop dates
are defined in:
Validation.dbo.tlh_load_track.
This also serves as an audit for
the number of records in the file
that require review at any given
time.
Upon return from Nordic, counts
are updated and any un
validated items are submitted to
WFM for manual review.

5. 5
AEDW will search and provide all data where:
Primary Search:
[MON on order matches CREC_MON or CREC_TN]
AND
Product is located in the AC IOSC Catalogue
AND
Order was created between the EFF_DATE and EXP_DATE
Secondary Search:
For ANY record identified in the Primary Search AEDW will provide details
concerning any subsequent activity on the same account that remove or
replace any trackable IOSC/Product Code as defined in AC IOSC Catalogue.
Daily: IOSC Catalogue published
to AEDW. Posted via Sftp
handoff
Daily: CREC File Posted to AEDW.
This file contains all items that are currently eligible
for Validation.
Provides search criteria
- TRANSACTION_ID- CREC_MON (Master Order
Number)
- CREC_TN (Telephone number if applicable
-EFF_DATE
-EXP_DATE
-CREC_STOP_DT
Daily Return From AEDW:
- Record Details File (contains all records located via CREC
file criteria. Results for same search grouped by
Transaction ID provided in CREC.
- Comments File: Contains all Cancel/Disconnect Verbatim
Remarks (Not used in contractual validation)
NORDIC
(AeDW Compensation)
NORDIC

6. 6
NORDIC
Daily Return File From AEDW Housed in Nordic.DBO.TF_NORDIC_RAWDATA
Per schedule housed in validatoin.dbo.tlh_load_track:
All items due for processing [today] per ProcessNoridc [DATE] are compiled per
procedure nordic.dbo.p_nordic_compile
P_nordic_Compile
- Order ties created. Inward/outward activity for same product groups and service types
joined to single row.
- join to nordi.dbo.tlh_validation_model to determine status of individual rows.
P_nordic_Compile
Account/Retention View Created
- Initial order identified-Alternate/Reissue orders Identified
- -Final Order Identified-
- joined to nordic.dbo.tl_validation_override to determine if the activity on next or final
orders override or overturn the initial order. (Retention check)
P_nordic_Compile
- Joined to nordic.dbo.iosc_master to retrieve product group, svc type, and svc tier
details.
- Joined to Nordic.dbo.tl_nordic_vendor to retrieve channel/vendor business rules-
- Validation Model-
- Contract Rules
- - Upgrade Rule
P_nordic_Compile
Results joined to validation.dbo.tf_validation_data using
nordic.dbo.tlh_product_exchange.
Validation.dbo.tf_validation_data

7. Back Up
7