Vahanse Statement of Work / Order Form Template

Status: DRAFT — FOR LEGAL REVIEW — NOT FOR EXECUTION

Version: 0.9 - Counsel Review Draft

Draft date: 31 August 2026

Operator: Vahanfin Solutions Private Limited (CIN U52290JH2023PTC021512)

Brand: Vahanse

Head office: Vahanfin Solutions Pvt Ltd, Nabibux House, 3rd Floor, Vakola Bridge Road, Santacruz (E), Mumbai 400 055, Maharashtra, India

This document is a Vahanse-specific working draft prepared for Vahanfin Solutions Private Limited (CIN U52290JH2023PTC021512), which operates the Vahanse brand. It is not legal advice and must be reviewed, approved and adapted by qualified Indian counsel before publication, signature or reliance. Commercial values, support contacts, regulatory representations, security commitments, service levels and any customer-specific terms must be validated against actual operations and contracts.

Purpose: Customer-specific scope, implementation and commercial order instrument under the MSA.

Audience: Enterprise, API and white-label customers

1. Parties

Provider: Vahanfin Solutions Private Limited (Vahanse), CIN U52290JH2023PTC021512. Customer: [Customer Legal Name], [CIN/LLPIN/Registration], [Registered Address]. This Order Form is governed by the Vahanse Enterprise MSA dated [date].

2. Products Purchased

• [ ] Vahanse Enterprise
• [ ] White Label
• [ ] API + Embed
• [ ] Compliance Gate
• [ ] Managed Compliance Operations
• [ ] Other: ______

3. Business Scope

Customer use case: [fleet compliance / embedded API / white-label monetization / compliance gate / other]. Initial vehicle/customer population: [ ]. Target production scale: [ ]. Geographies/vehicle classes: [ ].

4. Enabled Modules

• Vehicle Master
• RC/Vehicle Data
• Challan Monitoring
• Court/Virtual Court Workflow
• Insurance
• Fitness
• Permit/National Permit
• PUC
• Road Tax
• Document Management
• Orders/Payments
• Notifications
• Reconciliation/MIS
• API/Webhooks
• Compliance Gate rules

5. Implementation Plan

Milestone 1 – discovery/data mapping: [date]. Milestone 2 – sandbox/configuration: [date]. Milestone 3 – UAT: [date]. Milestone 4 – production go-live: [date]. Dates depend on Customer dependencies and source availability.

6. Customer Dependencies

• Authorized vehicle/customer data and lawful basis
• Technical contacts and API/network access
• Brand/domain assets if white label
• UAT resources and sign-off
• Payment/commercial approvals
• Required documents/KYB/security review

7. Success Criteria

• Vehicles successfully onboarded: [ ]
• Compliance records/alerts validated: [ ]
• API success/error target: [ ]
• Transaction/workflow completion: [ ]
• SLA support process validated: [ ]
• Reconciliation/reporting validated: [ ]

8. Term

Initial term: [12/24/36] months from [Effective Date/Go-Live]. Renewal: [automatic/renewal by written order]. Minimum commitment, if any: [ ].

9. Commercials

Fees are set out in the attached Commercial Schedule. Taxes extra as applicable. Payment terms: [ ]. Billing start date: [ ].

10. Service Levels and Support

Plan: [Standard/Growth/Enterprise]. SLA values: [ ]. Named support contacts: [ ].

11. Data and Security

DPA: [applicable/not applicable]. Hosting/region requirements: [ ]. Approved subprocessors exceptions: [ ]. Customer security requirements: [ ].

12. Special Terms

[Insert only customer-specific negotiated terms. Avoid repeating the MSA.]

13. Signatures

Authorized signatories for Vahanse and Customer, with name, title, date and electronic-signature acceptance.