Qualify the client first
3PM applies to PRC-creditworthy clients with a relationship and fleet opportunity worth pursuing.
No matching sections.
Try a client need, growth play, journey stage, system, or decision.
Try a client need, growth play, journey stage, system, or decision.
Capture the fleet. Solve the client need.
3PM gives PRC more ways to win, retain, and expand creditworthy client relationships by combining leasing with hardware, software, installation, data, and ongoing fleet-management capability enabled by TelemetryX.
Working definition
Third-Party Management enables PRC to finance and manage a creditworthy client’s broader fleet—including equipment not originally financed by PRC—through a coordinated hardware, software, installation, data, and service offering.
Customer relationshipPRC owns the commercial experience and financing relationship.
enabled by
3PM capabilityTLX supplies the technology, fulfillment, and operating capability.
Start with the client need
The net-new, renewal, or retrofit need determines the value story and the route.
Present one PRC experience
Internal entities and systems should not fragment the client’s commercial experience.
Match execution to the promise
Pricing, contracts, records, fulfillment, billing, and support must represent what was sold.
Concepts & terminology
Commercial labels do not determine accounting.
These terms provide a common vocabulary for route design. They are educational guardrails—not approved PRC or TLX accounting conclusions.
A contract contains a lease when it conveys control of the use of an identified asset for a period in exchange for consideration.
3PM question: does the client control a specified asset, or only receive a service outcome?Commercial shorthand for ongoing access to software, data, support, or fleet-management capability. The label alone does not establish the accounting.
3PM question: what distinct service is provided, over what period, and what event activates or ends it?A lease meeting ASC 842 classification criteria indicating transfer of control. It can produce selling profit or loss and a net investment at commencement, subject to the applicable requirements.
3PM question: has Finance approved the classification, commencement date, values, and collectibility assessment?A lease that does not qualify as sales-type or direct financing. The lessor retains the underlying asset and generally recognizes lease income over the lease term.
3PM question: who retains the asset and residual exposure, and what is the approved income pattern?The third lessor classification under US GAAP: not sales-type, but it meets the direct-financing criteria. Selling profit is not treated the same as in a sales-type lease.
3PM question: do not force every lease into only “sales-type” or “operating.”One contract can contain a lease plus hardware, installation, software, or service components. Components may require separation and allocation before recognition is determined.
3PM question: are the promises distinct, and are product, contract, tax, and system mappings aligned?Under ASC 606, revenue follows the promised good or service transferred to the customer. Distinct promises are identified, priced, allocated, and recognized when or as satisfied.
3PM question: are hardware, installation, activation, software, and ongoing service separate or one combined promise?Contract signing, shipment, delivery, installation, acceptance, lease commencement, software activation, and billing can be different events.
3PM question: which approved event transfers control or begins the service for this route?Freight, duties, tariffs, usage, estimates, and true-ups may affect transaction price, allocation, invoicing, and the risk of later reversal.
3PM question: is the amount fixed, estimated, constrained, financed, or billed only when actual?Revenue-recognition checkpoint
- What contract and legal entity?
- Lease, service, sale—or a combination?
- What are the distinct promises?
- When does control or service transfer?
- Which owner approved the treatment?
Authoritative framework: FASB Topic 842 · Leases and Topic 606 · Revenue from Contracts with Customers. Exact 3PM treatment remains subject to Finance, Accounting, Tax, and Legal approval.
Classify the deal before execution.
Use the client relationship, geography, equipment relationship, customer charge, and contract structure to route the opportunity into a working deal flavor.
Decision ruleAny item marked Open, TBD, Needs clarification, or pending review must be resolved by the accountable Finance, Tax, Legal, Accounting, Systems, or Operations owner before execution.
Purpose and scope
This guide classifies 3PM opportunities into eleven working deal flavors before execution. Start with client relationship and geography, then identify whether the opportunity involves new equipment, an active lease, a renewal, a standalone transaction, or a pilot. The selected flavor points to the expected Creatio setup, LeaseWave structure, NetSuite handling, accounting review, documents, and client invoice; it does not replace Finance, Tax, Legal, or Operations approval.
Current 3PM scope: PRC-creditworthy clients in the US and Mexico (Matrix A, flavors 1–8). Adjacent routes: standalone TLX, retail, and pilot transactions (Matrix B, flavors 9–11) are retained from the supplied guide as candidate routes and require governance confirmation before they are treated as standard 3PM scope.
Rule for use: any item marked Open, TBD, or Needs clarification requires Finance, Legal, or Operations confirmation before execution. This guide does not fill gaps; where the source matrix is silent, the cell says "Not stated."
Decision flow
Read left to right. Each column is a question; each rounded box is an answer. The flavor box color shows how settled that path is today.
Supported direction
Working control
Unresolved or incomplete
Placement requires confirmation
† The matrix does not state a geography for flavor 8; it is drawn under US for placement only. ‡ The matrix lists pilots under Matrix B but does not restrict them to non-PRC clients. See clarifications R3 and R5.
How the flavors differ
Most misclassification risk sits in five pairs that look alike on the surface. The deciding factor for each pair is named first.
1 Mexico Net New vs 4 US Net New
Decides it: geography.
Mexico treats TLX as a vendor: vendor PO to TLX, one PRC Mexico schedule, no split, one normal invoice, and TLX records an intercompany sale. The US has no vendor PO to TLX; TLX lines move to a -TLX schedule after final docs are executed, both schedules book, and the client gets one combo invoice.
2 Mexico Retrofit vs 5 US Paid Retrofit
Decides it: geography.
Mexico generally continues on the existing PRC schedule under the vendor model with no US-style split lease. The US creates a separate TLX-R schedule under a Service Agreement, and the invoice may be standalone or combo depending on the deal.
5 US Paid Retrofit vs 8 Free Retrofit
Decides it: ownership and customer charge.
Flavor 5 is a PRC-owned active lease where the client pays an incremental monthly 3PM amount. Flavor 8 is a syndicated or non-PRC-owned lease where rent does not change; there is no customer billing, and TLX takes deferred treatment with value received through remarketing at payoff.
6 Managed Service vs 7 Sales-Type Lease (US renewal)
Decides it: contract structure, not the presence of devices.
Flavor 6 is a flat monthly service with equipment not separately identified; the source proposes over-time recognition and $0 OEC in the booking presentation, subject to Accounting confirmation. Flavor 7 requires contract language supporting an equipment lease, with a distinct TLX schedule carrying actual OEC, payment, and LRF. If documentation does not support the lease, it is not flavor 7.
9 Standalone TLX Lease vs 10 Retail Sale
Decides it: financed or purchased.
Flavor 9 finances TLX hardware for a credit-qualified client with actual OEC booked in LeaseWave. Flavor 10 is a direct purchase with no LeaseWave lease, a standard NetSuite order and invoice, and candidate point-in-time hardware recognition, subject to transfer-of-control and Accounting review.
11 Pilot sits outside the tree until award
Decides it: whether a production deal has been awarded.
A pilot is not classified as net new, retrofit, or renewal. At conversion it is reclassified into flavor 4-type new equipment, a retrofit, a renewal retrofit, a standalone lease, or retail. Conversion rules are not yet documented.
Flavor differentiation matrix
One row per flavor, one column per system or decision. Text is taken from the source matrix; "Not stated" means the source does not address it.
| Flavor | Use when | LeaseWave schedule | TLX PO | OEC | NetSuite | Accounting / revenue review | Client invoice | Status |
|---|---|---|---|---|---|---|---|---|
| Matrix A: PRC creditworthy clients, Mexico | ||||||||
| 1. Mexico Net New | New PRC lease; new MHE; 3PM bundled | One PRC Mexico schedule; no split | Yes, to TLX; installer PO where required | MHE real OEC; TLX hardware, service, install lines $0; TLX Price separate | TLX intercompany SO and invoice; PRC Mexico settles | Proposed client-lease and intercompany treatment; Accounting and Tax confirmation required M1 | One invoice from PRC Mexico; no combo | Defined |
| 2. Mexico Retrofit to Active PRC Lease | PRC Mexico lease active; 3PM added to equipment in the lease | Generally existing PRC schedule; no US-style split M2 | Yes, to TLX; installer PO where applicable | TLX lines $0; TLX Price for PO and settlement M3 | TLX records intercompany sale | Mexico intercompany/vendor model | PRC invoices; added to existing invoice or separate per executed amendment | Mostly defined |
| 3. Mexico Renewal Plus 3PM | Equipment renewing; 3PM added at or around renewal and kept separate from renewed MHE schedule | Separate TLX-R schedule where approved | Not stated (Creatio Renewal = No to trigger VM activities) | Can be zero where no additional customer charge M4 | Not stated | Not stated M5 | Not stated | Emerging |
| Matrix A: PRC creditworthy clients, United States | ||||||||
| 4. US Net New, MHE Plus 3PM | New US lease; MHE and 3PM sold together before commencement | Two schedules: original and -TLX; split after finals executed, before finals check-in | None | TLX $0 before split; actual TLX OEC, payment, LRF on -TLX after split | SO from executed ELS and Service Agreement; inventory to Fixed Asset module | Configured treatment, pending documented Accounting rule U1 | One combo invoice, one number, one total | Defined target |
| 5. US Retrofit to Existing Lease, Paid | PRC lease commenced; client adds 3PM and pays incremental monthly amount | Separate TLX-R schedule tied to existing PRC schedule | Not stated | Depends on sales-type lease vs managed service U2 | Not stated | Lease classification if true lease; over service term if service | Standalone TLX invoice or combo, decided per transaction U3 | Partially defined |
| 6. US Renewal Retrofit, Managed Service | At renewal; flat monthly service; equipment not separately identified | May require separate TLX schedule or service billing record; not settled | Installation PO rules open | $0 in service/booking presentation; equipment cost kept in NetSuite | SO identified as 3PM Renewal | Working service hypothesis: over time; Accounting confirmation required | Not confirmed | Open design |
| 7. US Renewal Retrofit, Sales-Type Lease | At renewal; intent is sales-type accounting; contract supports lease and OEC | Distinct TLX lease booked separately | Not stated | Actual TLX OEC, payment, LRF | Reconcile LW items to NetSuite picking list and inventory/fixed-asset records | Sales-type only if contract supports it; otherwise over-time service | Not stated | Operationally unresolved |
| 8. Free Retrofit, Remaining Term | Lease syndicated or not PRC-owned; 3PM for remaining term; rent unchanged | No new customer lease | Not stated | Not stated | SO, pick and ship; no customer invoice from NetSuite | Deferred; value through remarketing at payoff | None | Special case |
| Matrix B: Non-PRC and standalone TLX | ||||||||
| 9. US Standalone TLX Lease | TLX hardware and services financed; no new PRC MHE lease; credit-qualified | Standalone TLX lease in LeaseWave | Not stated | Actual equipment OEC | Not stated | Approved lease classification; service and license separate | Depends on whether PRC services billing or TLX contracts directly B1 | Framework only |
| 10. TLX Retail Sale | Boxes purchased, not leased; any direct buyer type | None | Not applicable | Not applicable | Standard SO, fulfillment, invoice | Candidate point-in-time treatment for hardware and over-time treatment for services; confirm transfer-of-control and allocation rules | TLX via NetSuite | Playbook incomplete |
| 11. Pilot or Demonstration | Temporary hardware for evaluation; no rollout awarded | Recorded as pilot/demo until a production deal is awarded, then reclassified. Lease, billing, and accounting conversion rules are not documented. B2 | Rules undocumented | |||||
Roles and ownership
The source names owners only for opportunity setup and for the open gaps. A step-level RACI for each flavor is not in the source. G1 Needs clarification
| Activity | Owner named in source | Status |
|---|---|---|
| Create the opportunity | PM or AE | Needs correction G2 |
| Add products, price, and award | Pricing | Needs correction G2 |
| Finalize US renewal-retrofit rules | Finance, Accounting, Legal, Operations | Open |
| Finalize US paid-retrofit invoicing | Booking, AR, Accounting | Open |
| Add mandatory deal-treatment field | Creatio/System team | Open |
| Complete booking and AR maps | Booking, AR, and Operations leads | In progress |
| Publish the guide as the canonical classifier | 3PM process owner after required approvals | In progress |
Recommended Creatio decision fields and controls
These fields let Creatio carry the classification instead of relying on naming conventions.
| Field | Values |
|---|---|
| 3PM included? | Yes; No |
| Client relationship | PRC client; TLX direct; PRC-serviced non-PRC asset |
| Geography | US; Mexico |
| Equipment relationship | New PRC equipment; existing active PRC lease; PRC renewal; client-owned equipment; third-party leased equipment; no MHE relationship R4 |
| 3PM commercial treatment | Equipment lease; managed service/subscription; retail sale; intercompany sale; free retrofit/remarketing; pilot/demo |
| Customer charge | Incremental monthly charge; included in MHE payment; no additional charge; upfront purchase |
| Accounting treatment | Sales-type lease; operating/direct-finance lease; ASC 606 service/subscription; ASC 606 retail/intercompany; deferred/remarketing; pending Accounting review |
| Required schedule type | Single PRC schedule; PRC plus -TLX; existing PRC plus -TLX-R; standalone TLX; no LeaseWave schedule |
| Billing type | Normal PRC invoice; combo invoice; standalone TLX-R invoice; sundry/recurring charge; TLX direct invoice; no customer billing |
Required controls
- Block Award or Closed Won until deal treatment is selected.
- Block Booking when treatment, OEC, schedule type, and document type conflict.
- Keep TLX Price separate from OEC.
- Make TelemetryX selection mandatory at the applicable product or equipment-set level.
Needs clarification
Each item below is either a gap in the source matrix or a conflict with another current source (PRC_OPS_MAP workbook, 9/18/2026 update, and the 3PM Lease Split E2E Test Summary, April 29–30, 2026). Nothing here has been resolved by assumption.
Routing gates
| Ref | What the source says | Why it needs clarification |
|---|---|---|
| R1 | Gate 2 lists "standalone TLX financing or retail" as a US option for PRC clients. Gate 1 routes TLX-direct and non-PRC clients to Matrix B, where flavors 9 and 10 live. | Can a PRC client land in flavor 9 or 10? If yes, the gates overlap and the tree needs a rule for which gate wins. |
| R2 | Matrix A is titled "PRC Investment-Grade Clients"; Gate 1 says only "PRC client." | No path is defined for a PRC client that is not investment-grade. |
| R3 | Flavor 8 applies when the lease is "already syndicated or PRC does not own the lease/equipment." No geography is stated. | Confirm whether flavor 8 applies in Mexico. Also undefined: a syndicated lease where the client does want to pay, and a PRC-owned lease where 3PM is free. |
| R4 | Flavor 8 sits in Matrix A (PRC clients), but "PRC does not own the lease" overlaps the Creatio value "PRC-serviced non-PRC asset" and the equipment values "client-owned" and "third-party leased." | Which flavor do client-owned and third-party-leased equipment map to? None of the 11 flavors names them. |
| R5 | Pilots are listed under Matrix B. | Confirm pilots can occur for PRC clients too, which would move flavor 11 ahead of Gate 1. |
| R6 | An active service-only exception in the working operations map: "TLX = Service Only; MHE vendor buying hardware directly from TLX and installing themselves." | This does not match any of the 11 flavors. Needs a flavor or an explicit exception rule. |
Mexico
| Ref | What the source says | Why it needs clarification |
|---|---|---|
| M1 | Flavor 1: "over-time treatment for the client lease economics." | It is not clear which entity or which standard this refers to for the client lease itself. |
| M2 | Flavor 2: "generally continue with the existing PRC schedule." | Conflicts with the operations map, which calls the Mexico retrofit a stand-alone schedule with its own ELS, and with active TLX-R examples in the controlled opportunity records. |
| M3 | Flavor 2: TLX product lines at $0 OEC. | Conflicts with the ops map note that Mexico retrofits include their own ELS, OEC, and monthly payment on the proposal with everything disclosed. |
| M6 | Flavors 1 and 2 list acceptance certificates, and flavor 2 lists a "Telemetry AC when installation is complete and operational." | Conflicts with the ops map, which says "No AC for TLX units" for Mexico New/New and Retrofit. |
| M4 | Flavor 3 used an illustrative per-device monthly amount while "stating that the amount was already included in the renewal"; OEC "can be zero." | Unclear whether the client pays an incremental 3PM charge on a Mexico renewal. Confirm whether any referenced amount is approved pricing or only an example. |
| M5 | Flavor 3 has no revenue treatment or invoice guidance. | The US splits renewals into managed service (6) and sales-type lease (7). Confirm whether the same classification applies in Mexico. |
United States
| Ref | What the source says | Why it needs clarification |
|---|---|---|
| U1 | Flavor 4: Accounting "applies the configured revenue treatment." | The treatment itself is not stated. |
| U2 | Flavor 5 asks whether the arrangement is a sales-type TLX lease or a managed service. | This is the same split as flavors 6 and 7. Confirm whether flavor 5 is one flavor or two. |
| U3 | Flavor 5: standalone TLX invoice or combo invoice, "decision required by transaction." | No decision rule exists. Also listed as a priority gap (Booking, AR, Accounting). |
| U4 | Flavor 6: "per-device monthly subscription model." | Confirm whether the referenced amount is approved pricing or only an example. |
| U5 | Flavors 6 and 7 depend on a Creatio deal-treatment field that does not exist yet. | Until it is built, who makes and records the managed-service versus sales-type call? |
| U6 | E2E test decisions: property tax stays on the PRC lease only; AC handling for mixed TLX and non-TLX schedules; prorated rent before split. | None of these appear in the matrix for flavor 4. Confirm whether they belong in the playbook. |
Matrix B
| Ref | What the source says | Why it needs clarification |
|---|---|---|
| B1 | Flavor 9: determine whether PRC services billing or TLX contracts directly before creating documents. | Undecided, and it changes the documents and invoice. Also, flavor 9 is labeled US only; Mexico standalone leases are not addressed. |
| B2 | Flavor 11: conversion rules need formal documentation. | No lease, billing, or accounting rules exist for converting pilot hardware already installed. |
Governance and terminology
| Ref | What the source says | Why it needs clarification |
|---|---|---|
| G1 | Owners are named only for opportunity setup and open gaps. | A step-level RACI per flavor is needed. Metrics and review cadence are also not defined. |
| G2 | Matrix: PM or AE creates the opportunity; Pricing prices and awards. | The E2E test summary has OM/Sales creating and awarding the opportunity, and OM re-awarding after the split. Confirm the correct owners. |
| G3 | Ops map columns are "Renewal New/New" and "Renewal Retrofit." The matrix uses flavors 3, 6, and 7. | The mapping between the two naming sets is not stated. Earlier working drafts also carried a "Deferred Retrofit" flavor; the matrix has no such flavor, and "deferred" appears only as flavor 8's revenue treatment. Confirm whether Deferred Retrofit is retired or is flavor 8. |
Controlled source register
The deal-type matrix, operations map, lease-split test summary, and revenue-recognition/E2E working documents are maintained in the controlled internal workspace. Source files, customer records, prices, and evidence are not published in this public repository.
One journey. Different routes through it.
Every deal moves from client need to ongoing value. The growth play changes the entry point and message; operating decisions change the contract, records, handoffs, booking, invoice, and settlement route.
Deal flavorThe same journey, with a different commercial trigger and operating emphasis
Net newDifferentiate and winDeveloped variants
New financing needCredit-qualified prospect
Bundle lease + 3PMHardware, software, install
Win awardOne value proposition
Client signsApproved package
Deploy capabilityFulfill and install
Book routeUS or Mexico structure
Operate & expandGrow fleet penetration
RenewalRetain and capture fleetWorking route
Renewal windowInstalled base + fleet
Design fleet captureRenewal economics
Renewal proposalRetention + expansion
Approve treatmentService or lease path
Refresh / addHardware and installation
Bill approved modelRecognition still governed
Positive relationship valueRenew and expand
RetrofitSolve data and trackingControlled exception
Operating problemVisibility or tracking gap
Scope retrofitAssets, devices, software
Solution awardProblem solved first
Check ownershipPRC or investor-owned
Install in fieldCoordinate live assets
Choose approved routeStandalone or linked
Operate & prove valueData, tracking, expansion
Net new · bundled leasing route
Lead with the combined PRC financing and 3PM value proposition, then select the correct country and booking structure.
- Qualify the client and fleet opportunity.
- Price hardware, software, installation, financing, and delivery assumptions.
- Present one coordinated client offer and contract package.
- After signing, route fulfillment and booking through the approved US or Mexico model.
Commercial promisePRC differentiates through a combined lease and 3PM offering.
Developed variantsUS coterminous PRC-serviced and Mexico intercompany.
Primary controlCountry and legal entity must be known before booking.
Renewal · retention and fleet-capture route
Use the renewal event to retain the client, expand fleet coverage, and improve the long-term economics of the relationship.
- Start with the current schedule, renewal date, ownership, and installed base.
- Design the fleet-capture offer and define the hardware refresh, software term, and installation scope.
- Obtain Accounting and Legal approval for the contract and treatment.
- Do not operationalize the route as repeatable until booking and billing rules are approved.
Commercial promiseRenew with PRC and manage more of the fleet in one solution.
StatusCommercial direction is clear; operating treatment remains in progress.
Primary controlApproved service-versus-lease classification before contracting and booking.
Retrofit · data and tracking solution route
Begin with the client’s operating problem and the assets already in service, not with a generic lease product.
- Document the visibility, tracking, utilization, or data problem.
- Identify affected assets, current schedules, ownership, and installation constraints.
- Build the hardware, software, and field-installation solution.
- Escalate investor-owned and unsupported accounting routes before award commitments are finalized.
Commercial promiseSolve an immediate fleet problem without waiting for wholesale replacement.
StatusMidterm and investor-owned paths remain controlled exceptions.
Primary controlConfirm ownership and approved transaction treatment before execution.
Need the operational detail?
Open detailed journey diagrams →Open the team-and-system swimlanes for Creatio, TLX, NetSuite, LeaseWave, Billing, and Treasury handoffs.
Close the moving pieces. Measure the result.
Unresolved work belongs in one decision area—not scattered across the playbook. As routes mature, the same journey should show where growth, profitability, cash, capacity, and efficiency are affected.
Commercial offering
In progressApproved component bundles
Define standard hardware, software, installation, and service combinations by growth play.
Pricing and soft costs
Set treatment for shipping, installation, pass-through costs, exceptions, and materiality.
Customer presentation
Standardize what appears in the proposal, contract, invoice, and renewal story.
Transaction and accounting
In progressRenewal classification
Approve managed-service, sales-type, or other treatment and supporting contract language.
Recognition triggers
Resolve shipment, installation, acceptance, commencement, and service-period rules by route.
Investor-owned retrofit
Approve the path when the existing lease cannot be reopened or modified.
Systems and records
In progressCreatio route selector
Require growth play, country, ownership, contract, installation, and treatment before award.
Schedule and item logic
Standardize split timing, suffixes, product mapping, OEC, rent, term, and invoice behavior.
Termination and service data
Expose the TLX term and cutoff event to downstream systems.
Ownership and execution
In progressInstallation ownership
Define payer, PO issuer, coordinator, evidence, and exception route by flavor.
Team handoffs
Confirm accountability across Sales, OM, LA, VM, AM, TLX, Booking, Billing, and Treasury.
Repeatability gate
Define the evidence and approvals required before a route becomes standard.
Decision rule
A working assumption can support a controlled pilot, but it cannot become a repeatable route until the owner, rationale, effective date, affected journeys, controls, and approval are recorded.
Economic impact across the journey
This is a measurement framework, not approved accounting guidance. Exact recognition timing and P&L treatment require Finance approval.
Journey stage
Top line
Bottom line & cash
Capacity & efficiency
Qualify and design
Pipeline quality
Eligible opportunities and potential fleet coverage.
Margin quality
Sound scope, price, cost, and structure.
Focus
Less time on ineligible or unworkable deals.
Propose and sign
Win rate and bookings
Client conversion and contracted value.
Commercial discipline
Fewer unsupported exceptions and concessions.
Cycle time
Faster approval and contracting.
Fulfill and install
Revenue enablement
Hardware and installation delivery supports billing.
Delivery cost
Hardware, shipping, labor, and field-service cost.
Throughput
Installation capacity, scheduling, and first-time completion.
Book, bill and collect
Billable revenue
Accurate invoice and recurring charge setup.
Cash and working capital
Collections, settlement, and error reduction.
Administrative effort
Fewer reconciliations and manual corrections.
Operate and renew
Recurring growth
Software revenue, retention, renewal, and expansion.
Relationship value
Support cost, renewal economics, and lifetime value.
Service leverage
More fleet supported with better data and process.
Current direction
- Commercial narrative and growth plays reflect owner direction provided for this release.
- US net-new and Mexico net-new operating variants remain the most developed routes.
- Renewal and retrofit routes remain working or unresolved where accounting and ownership decisions are open.
Evidence boundary
- The operating detail is based primarily on the current 3PM TLX Integration E2E document.
- The site has not yet been fully reconciled against the accounting workbook, prior versions, meetings, or live system behavior.
- Financial impact labels are a management framework—not approved recognition policy.