Version 1.1 · Published 16 Oct 2026
Expense Allocation and Dispute Policy
Version 1.1 · Status: Final – Approved and Published · Afsa Event Management Private Limited
1. Three separate questions
For every incident or recovery expense ZippyCarna records separately:
- Initial payer — who advanced the money (Host, ZippyCarna, Customer, Insurer, a recovery-vendor credit or another authorised third party);
- Ultimate responsibility — who is responsible after assessment (Host, ZippyCarna, Customer, Insurer, Warranty provider, Third party, several parties, or unallocated pending review);
- Final settlement — who reimburses whom, and what remains outstanding after payments, insurance proceeds, refunds and approved allocations.
2. Assessment, not presumption
No expense is payable by a customer or host merely because an incident occurred. Each allocation considers evidence and cause, the actual contractual responsibilities, insurance and warranty coverage, applicable law and court orders, contributions from several parties, and amounts already paid or reimbursed. ZippyCarna bears costs attributable to its own contractual obligations or proven fault where legally applicable.
3. Default rules are proposals
ZippyCarna maintains configurable default rules per expense category (for example: ordinary wear and scheduled maintenance — Host; proven customer misuse — potential Customer liability after review; accident — investigate and claim insurance; company-caused damage during custody — review ZippyCarna responsibility; unknown cause — unallocated pending investigation). A default is a proposal for review, never an automatic legal finding.
4. Approvals
4.1 Allocations are approved under delegated limits: Fleet manager up to ₹10,000; Finance manager up to ₹50,000; a Director above that and for every write-off. Limits may be revised by a Director with a recorded reason. 4.2 Finance verifies every vendor invoice before allocation. Legal reviews criminal incidents, police seizures, disputed liability and legal expenses. The person who proposes an allocation cannot approve it. System administrators do not automatically hold authority to decide legal liability. 4.3 Every decision records the actor, time, reason, evidence references and the rule version applied.
5. Evidence and visibility
Charges allocated to a customer are supported by evidence shared with that customer. Hosts receive itemised statements for their vehicles.
6. Duplicate and double recovery
Duplicate invoices are rejected. Receipts can never exceed the outstanding amount of a party's share, and insurance receipts can never exceed the insurer-approved amount. Insurance money is never assumed until received; expected, approved, received, rejected and disputed amounts are tracked separately.
7. Disputes
7.1 A host or customer may dispute any proposed or approved allocation in the app, with reasons and documents. While a dispute is open, collection of the disputed amount is suspended. 7.2 Disputes are decided by a Finance manager or Director who did not raise them. If a dispute is upheld, the allocation is reversed by auditable reversal entries — completed ledger entries are never edited or deleted. 7.3 Unresolved complaints may be escalated under the Grievance Redressal Policy.
8. Collection
Approved customer charges are collected by ZippyCarna's team with an itemised statement and supporting evidence; ZippyCarna does not automatically debit a customer's card or deposit for incident charges. Host shares are settled through the host payout statement.
Document Status: Final – Approved and Published · Version 1.1