No matching sections.
Try a system, deal type, role, or process term.

Working playbook · version 0.1

One operating model. Multiple deal paths.

A structured view of how PRC and TelemetryX qualify, contract, fulfill, book, bill, collect, and manage Third-Party Management engagements.

Working draft Evidence-led PRC client-facing TLX enabled

Customer relationship PRC owns the client-facing commercial experience.

operates with

3PM capability TLX supplies, fulfills, and supports the telematics layer.

2developed net-new operating models

2+retrofit and renewal variants

4core operating systems

12priority decisions still to close

02 · Operating principles

Rules that anchor every route

These principles are strongly supported by the current E2E document. Exceptions and accounting treatments still require explicit approval.

Protect the client experience

PRC remains the primary customer-facing entity. Internal schedules, wholesale economics, and system splits should not create conflicting customer communications.

ControlCustomer documents and invoices must reconcile to the approved commercial offer.

Classify before booking

Geography, lease state, ownership, installation timing, and accounting treatment determine the path. “3PM” alone is not a sufficient classification.

ControlNo booking route without an approved deal flavor and accounting treatment.

Keep the systems reconciled

Creatio lines, LeaseWave schedules, NetSuite items, warehouse picking lists, acceptance dates, and customer billing must describe the same transaction.

ControlResolve quantity, item, OEC, rent, term, and date differences before billing.

Do not hide exceptions

Renewals, midterm retrofits, mixed schedules, investor-owned leases, and installation variances require visible decisions—not silent workarounds.

ControlNamed owner, decision, evidence, expiry, and downstream impact for every exception.

03 · Common lifecycle

The seven-stage control path

A common lifecycle contains the work. Deal flavors change the route, evidence, approvals, and accounting treatment inside each stage.

Intake

Capture sponsor, parties, geography, equipment, client need, target timing, and known constraints.

Exit gateComplete request and accountable owner.

Classify

Determine net-new, renewal, retrofit, geography, lease ownership, billing model, service term, and risk attributes.

Exit gateApproved flavor and review lanes.

Design and price

Align scope, TLX price, installation, shipping, commercial presentation, monthly payment, and accounting structure.

Exit gateEconomics and delivery model approved.

Contract

Complete ELS, Service Agreement or 3PM rider, client PO, tax status, vendor POs, and approved deviations.

Exit gateExecutable documents and authority.

Fulfill and accept

Order, pick, pack, ship, coordinate installation, confirm operational status, and execute acceptance evidence.

Exit gateDelivery and installation evidence reconcile.

Book, bill, collect

Create the correct schedules, book in LeaseWave, reconcile NetSuite, invoice the client, and allocate collection.

Exit gateAccounting, AR, tax, and cash treatment verified.

Operate, renew, or exit

Monitor service, obligations, changes, termination dates, renewals, API cutoff, and asset disposition.

Exit gateReview accepted, renewal approved, or exit complete.

04 · Deal flavor catalog

Choose the path by operating difference

A separate flavor is justified only when the transaction changes an owner, control, artifact, workflow route, accounting treatment, invoice, or monitoring requirement.

MX-N

Mexico · Intercompany vendor model

TLX sells to PRC Mexico; PRC bundles the cost into one customer lease.

Developed

Customer facePRC Mexico

Internal structureVendor PO + intercompany sale

Customer invoiceSingle LeaseWave invoice

TLX lines begin with zero OEC; wholesale value is captured in the separate TLX Price field.
PRC Mexico issues a vendor PO to TLX and normally issues the installation-provider PO.
TLX creates and fulfills an intercompany NetSuite sales order and recognizes intercompany revenue under the approved ASC 606 treatment.
PRC books one LeaseWave schedule; no TLX split is required for the customer lease.
PRC Mexico settles TLX after customer collection through the intercompany invoice.

US-N

United States · Coterminous PRC-serviced model

One customer transaction becomes two internal schedules and one combo invoice.

Developed

Customer facePRC

Internal structurePRC lease + TLX schedule

Customer invoiceOne combo invoice

The client signs one grossed-up package; no vendor PO is issued to TLX.
After final documents and before check-in, TLX lines move to a new schedule with a -TLX suffix.
Both schedules use the same signed final documents and are booked separately in LeaseWave.
LeaseWave produces one invoice number and one PDF covering PRC and TLX charges.
Collections follow a PRC-first waterfall; the TLX service term is intended to remain coterminous with the ELS.

R-R

Renewal retrofit

Add 3PM when an existing PRC lease reaches renewal.

Working

TriggerEnd of firm term

Models discussedManaged service or sales-type

Primary riskRevenue misclassification

Managed-service treatment uses a flat monthly amount and recognizes revenue over time.
A sales-type renewal requires supporting contract language and an approved accounting conclusion.
Creatio currently lacks a definitive field to distinguish managed service from lease treatment.
Installation ownership, PO route, commencement timing, and invoice structure still need approval.

R-M

Midterm retrofit on an existing lease

Add 3PM after the original lease has commenced or been syndicated.

Unresolved

TriggerNo simultaneous new ELS

Potential structureStandalone TLX-R schedule

Primary riskInvestor and accounting treatment

The original equipment lease may already be owned by an investor and cannot simply be reopened.
The retrofit may be free for the remaining term, deferred until remarketing, or structured as a standalone sales-type lease.
The working naming convention is <original schedule>-TLX-R.
Accounting, billing, installation, and termination rules are not yet complete enough for a standard path.

Decision point	Mexico net-new	US coterminous	Retrofit / renewal
PRC → TLX PO	Yes, vendor PO	No	Depends on approved model
Lease split	No	Yes, after final docs	Usually separate; rule unresolved
Client invoice	Single PRC invoice	Single combo invoice	Combo or standalone; unresolved
TLX payment	Intercompany settlement	PRC-serviced waterfall	Service, lease, or deferred route
Confidence	Developed	Developed	Needs decisions

06 · End-to-end workflow

From opportunity to operating service

This is the common flow. The deal flavor controls the documents, split point, accounting route, invoice, and collection allocation.

01 · CreatioQualify opportunityEquipment lines, TLX price, 3PM and Telemetry indicators.

02 · PRCPresent customer offerApproved commercial package without exposing wholesale economics.

03 · ContractForm the agreementELS, Service Agreement, rider, tax status, POs, and deviations.

04 · TLX / vendorsFulfill and installSales order, pick, pack, ship, installation coordination.

05 · PRCAccept deliveryTruck AC, module confirmation, installation date, final AC.

06 · CreatioSplit when requiredMove TLX lines, rename schedule, add OEC, rent, and LRF.

07 · LeaseWaveBook schedulesValidate items, term, OEC, payment, and category.

08 · NetSuiteRecognize and reconcileIntercompany or PRC-serviced accounting route.

09 · BillingInvoice customerSingle or combo LeaseWave invoice under the approved flavor.

10 · Trust / NSCollect and allocateApply payment, settle TLX, and update AR status.

Critical timing control

Truck delivery, TLX shipment, TLX installation, acceptance, schedule split, and lease commencement are distinct events. The current document does not yet provide one approved date rule for every flavor.

07 · Systems and data

One transaction, four operational views

The playbook must treat system reconciliation as a control, not an administrative cleanup activity.

Creatio

Opportunity, pricing request, TLX indicators, lease lines, acceptance, split schedules, final documents, and workflow.

LeaseWave

Lease schedules, OEC and rent, combo eligibility, invoicing, property-tax treatment, aging, and payment state.

NetSuite

TLX sales orders, fulfillment, intercompany invoicing, inventory, fixed assets, revenue, COGS, and internal AR.

Trust / files / API

Bank collection, allocation workbooks, connector uploads, AssetPro visibility, and future termination cutoff.

Data element	Why it matters	Minimum control
TLX Price	Wholesale/intercompany tracking before booking	Approved value and source retained
OEC	Shell versus bookable TLX schedule	Zero until the approved split/booking step
3PM / Telemetry flags	Workflow, visibility, and delivery tracking	Required before award
Product and item category	AssetPro, tax, LeaseWave, and NetSuite mapping	Standard cross-system catalog
AC and installation dates	Commencement, proration, payment, and revenue timing	Evidence-backed dates with flavor-specific rule
Schedule suffix	Combo invoice and portfolio identification	`-TLX` or `-TLX-R` standard
Term / termination	Coterminous service and future API cutoff	Visible in Creatio and passed downstream

08 · Decision register

What must be closed before scale

These are decision topics, not assumed answers. Each requires an accountable owner, approved disposition, effective date, and impacted artifacts.

Accounting

Renewal classification

Define when a renewal retrofit is managed service, sales-type lease, or another approved treatment.

Workflow

US split timing

Confirm whether every coterminous US deal splits after final docs or whether independent commencement changes the design.

Revenue

Recognition trigger

Resolve shipment, installation, acceptance, LeaseWave setup, and service-period triggers by flavor.

Installation

Ownership and PO route

Define payer, PO issuer, coordinator, standard price, exception path, and evidence for each geography/flavor.

Billing

Retrofit invoice rule

Define combo versus standalone invoice and how truck and TLX charges appear to the customer.

Systems

Managed service indicator

Add a controlled Creatio field that prevents service and lease treatments from being confused.

Assets

Investor-owned retrofit

Approve the commercial, accounting, and operational path when the original lease has been syndicated.

Integration

Termination and API

Expose the TLX term and termination date and define the future service-cutoff event.

Master data

Product normalization

Create one item map for Creatio, LeaseWave, NetSuite, warehouse, sales tax, and AssetPro.

Automation

TLX shell routing

Define automatic numbering, post-split workflow bypass, and Creatio-to-NetSuite sales-order creation.

Commercial

Shipping and soft costs

Choose finance, pass-through, short-pay, or TLX-absorbed treatment and establish materiality rules.

Operations

Mixed schedules

Standardize acceptance and commencement when only part of an equipment schedule receives TLX.

09 · Content governance

Separate known, working, and unresolved

The website is a reading layer. It must not turn working notes into policy simply because the presentation looks finished.

Documented / developed

PRC owns the client-facing experience.
Mexico intercompany vendor model.
US coterminous split-and-combo model.
Core Creatio, LeaseWave, NetSuite, and Trust handoffs.

Working direction

Installation simplification and standard pricing.
Independent commencement of PRC and TLX schedules.
Schedule naming and shell-routing automation.
Termination-date API integration.

Unresolved

US renewal retrofit E2E path.
Investor-owned midterm retrofits.
Revenue and accrual timing by flavor.
Final installation, shipping, and invoice rules.

Current evidence boundary

This first build is based primarily on 3PM_TLX_Integration_E2E.docx. It has not yet been reconciled against the accounting workbook, prior document version, recordings, transcripts, current Creatio configuration, or approved accounting guidance.

10 · Release notes

How this playbook evolves

Every release should identify its evidence, business decisions, affected routes, reviewers, and remaining limitations.

18 September 2026 · v0.1

First structured playbook prototype

Converted the E2E document into operating principles, lifecycle, flavor catalog, workflow, systems map, and decision register. No business decisions were resolved by the prototype.

Next planned release

Evidence reconciliation

Reconcile the accounting workbook, older E2E version, recordings, transcripts, and actual system configuration; then convert approved decisions into controlled rules.

Next content milestone

Add role-level work instructions, RACI, entry/exit checklists, required artifacts, evidence references, and worked examples for each approved deal flavor.