Business Glossary

Electric vehicles supplied at scale to business clients through rental or RTO arrangements.

Monthly invoicing is a repayment process. Program and commercial arrangement, including a genuine sale-and-leaseback, remain separate classifications.

Rent-to-Own or Rent Only provided directly to individual customers.

B2C vehicles remain registered under AIZEN during the contract. Any ownership transfer is handled separately after the contractual requirements are fulfilled.

An intermediary-based commercial relationship connecting business partners with individual customers.

RF remains a B2B2C program in the business taxonomy. Some reports place RF under a B2C reporting segment; do not add both classifications together.

AIZEN purchases assets from a seller and leases those assets back to that same seller.

The seller becomes the lessee. Ordinary purchases from an OEM followed by B2B rental or B2C RTO are not S&L.

Use of a vehicle for rental payments, with return of the vehicle at program completion rather than an ownership-transfer entitlement.

The SOP calls this Rent Only. It describes a manual Finance billing/payment process for Rent Only; do not assume the RTO automatic daily-billing process applies unchanged.

Rent-to-Own: a program allowing a customer or client to obtain ownership after fulfilling the agreed contractual requirements.

For B2C, the SOP separates final repayment, document title transfer, document handover, deposit return, and account closure. B2B RTO follows its own agreement; payment completion alone does not prove legal transfer.

Retail Financing: a B2B2C program in which AIZEN acts as an intermediary and a financing institution (Multi Finance) assesses credit and approves financing.

Affiliate Partners may provide leads, wallet deductions, and repayment reports under their agreement. Wallet deduction, remittance to AIZEN, and repayment to Multi Finance are separate events; legal ownership is recorded separately.

An existing vehicle status indicating active use under source-system rules.

Does not independently prove earning, payment quality, or physical possession.

A vehicle available for the handover workflow after the required operational checks.

Credit Connect uses this status for handover creation and after eligible QC or repair completion. It does not by itself confirm a reservation or a universal “Ready to Rent” classification.

An existing status for vehicles undergoing repair or maintenance.

In Credit Connect, service completion returns the vehicle to ACTIVE or READY_TO_HANDOVER based on its history before QC.

A vehicle undergoing quality inspection before return to use or preparation for handover.

In Credit Connect, QC can lead to repair, ACTIVE, or READY_TO_HANDOVER depending on inspection and prior history. Reporting it as repair or idle still needs an agreed mapping.

An existing vehicle status requiring a more specific reason.

Does not by itself establish availability, retirement, loss, or customer possession.

An existing vehicle status whose operational meaning needs confirmation.

Separate from PENDING_COLLECTION, which explicitly means a collection request. PENDING alone does not justify excluding a vehicle from owned stock.

A vehicle flagged for collection, before collection work starts.

In Credit Connect, Request Collection sets this status; Start Collection moves it to IN_COLLECTION. Neither confirms that the vehicle has been recovered.

Vehicle collection or recovery work is in progress.

Credit Connect can mark the linked contract CHURNED when collection starts. This status alone does not confirm physical recovery; receipt evidence is still needed.

A vehicle carrying the source system’s paid-off financial label.

Verify settlement against the contract. This label alone does not establish legal ownership transfer.

The LOCKED operational label on a vehicle record.

It is separate from the reported LOCKED/UNLOCKED lock state and from the progress of a remote command.

An instruction to lock a vehicle remotely through its IoT provider.

Operational vehicle status, reported lock state, and command progress are separate. Sending a command does not confirm the vehicle is locked.

A contract that has fulfilled its contractual completion requirements.

In Credit Connect, completion requires no remaining installments and no unpaid, processing, or partly paid bills. Legal ownership transfer is verified separately.

A contract ended through the churn workflow rather than normal contractual completion.

In Credit Connect, an ACTIVE or DEFAULT contract can move to CHURNED. This does not by itself confirm customer blacklisting, debt settlement, or physical vehicle recovery.

A contract carrying the DEFAULT status in the source system.

Recorded DEFAULT and reporting DEFAULT are separate fields. Thresholds differ across PRDs and reports; neither implies the vehicle is idle or billing has stopped.

The completion workflow covering document title transfer, document collection, deposit return, and borrower-account closure after the final repayment milestone.

Keep settlement, legal transfer, document handover, and account closure as distinct events; do not assume they share one timestamp.

The RF completion process in which final installment repayment is followed by financial-institution notification and BPKB handover.

The SOP assigns BPKB handover to the financial institution; do not substitute the B2C RTO completion workflow.

A contract currently in force.

Payment health is tracked separately: an ACTIVE contract can have overdue bills. Credit Connect records DEFAULT as a separate contract status.

An existing contract status requiring confirmation of its exit and restriction semantics.

Preserve contract history. Do not automatically infer a customer blacklist flag.

A pre-activation contract record.

Credit Connect retains legacy contract-onboarding states. A DRAFT contract record is separate from an application draft or a legal document awaiting signature.

Contract-level onboarding and older status labels retained alongside the application-led flow.

Always state the entity and source version. Matching names across application and contract records do not prove the same event.

A customer record marked ACTIVE in EMMS.

Credit Connect sets this status during handover activation. Contract status, payment health, and login permissions are separate.

A customer record marked INACTIVE in EMMS.

An INACTIVE customer can still have a lead or blacklist flag. This status alone does not establish contract history or login permissions.

A customer restriction flag with a reason, effective date, and review or removal policy.

Not a lifecycle state; do not automatically derive it from contract or application labels.

An application in verification and video review after credit approval in the application-led flow.

SCHEDULING follows approval of submitted video or a NOT_REQUIRED video path; credit approval alone does not confirm handover readiness.

An application eligible for handover scheduling.

A reserved slot does not itself confirm commitment-fee payment or physical delivery.

In Credit Connect’s application-led flow, an application awaiting handover after commitment-fee settlement and schedule reservation.

A pending handover is not a completed delivery.

An application undergoing handover processing.

Not a completed physical handover.

An application that has been linked to its newly created customer contract.

Keep the application’s history separate from contract servicing and physical-delivery evidence.

An application declined following assessment.

Keep customer restrictions separate.

An application saved before submission.

This is an application record, not a signed contract or a count of unique people.

A submitted application awaiting credit assessment.

It is not an active contract. Approval in the application-led flow moves it to IN_REVIEW.

A rejection-related application value retained in the source system.

The schema marks it deprecated for new data, but recorded code paths and web filters still use it. Do not infer reapplication eligibility.

An application recorded as blacklisted or restricted.

This historical application status is separate from the customer’s current restriction flag.

A document acknowledging a specified handover or receipt between named parties.

The SOP uses BAST for OEM-to-AIZEN receipt, customer/client vehicle handover, collected-unit warehouse receipt, and BPKB handover. A BAST record is not automatically a new customer deployment.

The effective start date of a B2C contract’s billing schedule.

Use the contract’s billing start date. Physical handover, the first chargeable installment, and cash receipt can fall on different dates.

Confirmed physical retrieval of a vehicle, with a recovery date and receipt evidence.

Record the recovery date and receiving custodian. In RF, recovery can precede a later handover to AIZEN; a contract exit, remote lock, or collection initiation does not confirm physical recovery.

Release or activation of financing by Multi Finance under the relevant facility.

The SOP places B2C unit disbursement on handover day and B2B financing activation one day after client delivery. Do not use one universal disbursement-to-handover date rule.

Confirmed physical delivery of a vehicle to an individual customer or corporate client.

First handover is the vehicle’s first customer delivery; repeat handover is a later customer delivery. Warehouse or city transfers are separate events. Use the actual event date and location; later moves do not rewrite history.

Reuse of a previously handed-over vehicle under a subsequent customer agreement.

A reuse proxy is not proof of a new physical handover or a universally agreed RTO billing rule.

A customer voluntarily hands the vehicle back to AIZEN or its designated custodian.

Record physical receipt separately from the reason for return. This is distinct from repossession and does not itself settle debt or close the contract.

Bills or bill components that create a customer payment obligation under the applicable program rules.

Use actual payable components: free billing can leave fees due. Chargeable billing is a payment obligation, not cash received or accounting revenue.

Actual cash receipts during the reporting period, measured by receipt date.

Separate installments, deposits, fees, and refunds. In RF, a driver-wallet deduction is distinct from the AP remittance received by AIZEN.

Bills fully resolved through payments or valid adjustments.

Not equivalent to cash received: receipt and bill dates differ, and adjustments may be noncash.

Remaining obligations after allocated payments and valid adjustments.

Includes both overdue and not-yet-due amounts.

The overdue portion of outstanding balance after allocated payments and valid adjustments.

Do not assume the full original bill remains due when partial allocations exist.

The RF process in which the Affiliate Partner arranges driver-wallet deductions and reports repayment activity to AIZEN.

Credit Connect also uses DDE for GoPay autocharge. That flow, RF partner-wallet deductions, and AP remittances are separate.

Payment from the Affiliate Partner to AIZEN for RF customers under the monthly remittance process.

This is separate from the daily customer-wallet deductions and from onward payment to Multi Finance.

AIZEN payment to the financing institution under the financing schedule.

This is AIZEN’s financing outflow, not customer installment cash received.

An adjustment that reduces the amount to be charged on the B2B client invoice under the SOP.

Record its reason and supporting agreement. Do not automatically treat it as cash received or a refund transaction.

An onboarding fee associated with confirming a handover reservation.

Often called booking fee, but labels overlap with “deposit” in PRDs and mobile screens. No universal amount or refund promise follows from the label.

An upfront customer payment recorded separately from the booking or commitment fee and recurring installments.

Deposit, DP, and booking-fee labels vary by source. Identify the exact charge type, program, and stage before applying refund or deduction terms.

Promotional treatment that waives eligible installment charges.

Additional fees may remain due. Credit Connect’s first-sequence complimentary billing follows a separate rule.

A program’s initial installment allowance used to cover eligible bills without a new payment on each billing date.

Separate from promotional free billing and Credit Connect’s first-sequence complimentary rule.

A temporary hold on regular installment billing for a specified period.

The Done PRD calls for DPD to stay at its pre-hold value. That is documented intent, not proof of every code path. A hold is not repayment or an arrears waiver.

The number of unpaid bills that are at least one day overdue.

Count each bill once while a due balance remains, including partial payments. One bill overdue four days is still one bill. First-late-day timing varies by source.

Calendar days since the oldest due date with an unpaid overdue balance, measured at the reporting date; minimum 0.

DPD is 0 when nothing is overdue. Partial payment stays overdue while a due balance remains. Reconstruct balances and allocations at the historical cutoff. Hold-adjusted values and billing-cycle counts are different measures.

A contract classified as DEFAULT in the specified reporting snapshot.

State the snapshot and its bucket rules. Calendar DPD ≥4 is a separate glossary convention; it is not a verified equivalent of the dashboard bucket. Default alone does not establish idle or stopped billing.

Source-provided delinquency labels such as DPD 1–3, Near Default 1/2, and Default.

They are categorical labels; do not convert them into calendar days or current snapshot buckets without a verified mapping.

A record of an amount due, its due date, and payment status.

Payments and allocations are separate transactions. A bill can receive several partial payments; payment date does not replace due date.

Suspension or cessation of creating new customer charges from an effective date.

Existing debt remains unless separately settled or adjusted. Default or recovery does not imply billing has stopped; use the actual schedule and effective stop or hold.

Suspension of accounting revenue recognition under the applicable accounting policy.

This is separate from creating bills and receiving cash. No automatic Default threshold or accounting policy is established by this glossary.

A contract’s billing-health field, separate from its lifecycle and individual bill payments.

Recorded values are NORMAL, LATE, SUSPENDED, and COMPLETED. SUSPENDED does not by itself establish contract termination.

The recorded settlement state of an individual bill.

UNPAID, PROCESSING, and PARTIAL_PAID remain distinct from PAID. A failed payment attempt does not prove that the bill is settled.

Vehicles in the declared reporting scope with a confirmed customer handover on or before the cutoff, excluding paid-off vehicles.

Use unique vehicles and states effective at the cutoff. Declare treatment of disposed, written-off, and missing units; paid-off exclusion alone does not resolve fleet scope. Unknown exit mapping is a coverage gap, not zero.

Eligible vehicles meeting the declared billing-based earning rule at the reporting cutoff.

Declare the billing window, operational-state rule, and Default treatment. Billing on the report date is a daily convention; a trailing seven-day numerator measures a different window. Neither is cash received or accounting revenue.

Earning eligible vehicles divided by eligible fleet at the same reporting cutoff.

Use the same scope, unique vehicles, and earning rule on both sides. Never-handed-over stock is outside this denominator. Zero denominator or incomplete coverage means unavailable.

Non-paid-off vehicles in the declared reporting scope that do not meet the billing-based earning rule at the cutoff.

Includes never-handed-over and previously-handed-over vehicles under one earning rule. Declare disposal, write-off, and missing-unit treatment. Unknown billing or exit coverage is unavailable, not automatically idle or zero.

Idle vehicles with no confirmed customer handover on or before the reporting cutoff.

Exclude paid-off vehicles. Warehouse or city transfers are not customer handovers. Count each vehicle once.

Eligible vehicles not earning under the billing-based rule on the reporting date.

Exclude paid-off vehicles and apply the same fleet scope, cutoff, and earning window as the numerator. Count each vehicle once; never subtract total idle from eligible fleet.

Elapsed idle time measured with a stated start event and end event or reporting cutoff.

Total downtime may include recovery, repair, and QC. Ready-to-rent waiting time starts only when readiness is confirmed. State clocks and targets separately for never-handed-over and previously-handed-over vehicles.