Skip to content
VietGara Docs

RELEASE PLAN — PHASE 17

VietGara — Insurance & Partner Expansion

Version 17.0 — October 9, 2026 · Cloud: Google Cloud Platform (GCP) · Backend: Go

1. Introduction

In Vietnam the vehicle owner files the insurance claim. The garage supports it with a quote, the repair and the documents. The claim goes through five steps:

  1. Report. The owner secures the scene, calls the insurer’s hotline, and notifies the insurer in writing, by its app or by e-mail within 5 working days of the incident (Decree 67/2023/ND-CP). Serious or disputed accidents also need the traffic police’s report.
  2. Assessment. The insurer’s assessor inspects the vehicle, at the scene or at the garage, within 24 hours, and writes the assessment report (biên bản giám định).
  3. Quote and agreement. The garage (in the insurer’s network or an outside garage under contract) prepares the repair quote; the insurer and the owner or garage agree the cost and the repair method.
  4. Claim file. Vehicle registration, driver’s licence, ID card of the owner or driver, insurance certificate or e-policy, accident report (if any), damage and assessment reports, repair invoices and vouchers.
  5. Approval and payout. The insurer approves, usually in 3-5 days for small losses and 7-15 for complex ones. The garage repairs the vehicle and the owner pays only the deductible or out-of-cover part, or the insurer pays the owner.

So the module is a claim-tracking workflow attached to a repair order, with deadlines and a document checklist, not a payer split on the settlement and not first of all an API integration. Direct submission to an insurer is an optional layer on top.

2. Overview of the 3 Releases

ReleaseNameMain ModulesDemoable Value
17.0Insurance Claim TrackingInsurance (new), Billing, Receivables, Customer AppFollow a claim from report to payout, with deadlines, the document checklist and the settlement split
17.1Partner Expansion & Claim SubmissionE-Invoice, Insurance IntegrationMISA and BKAV e-invoices; claim file submission to insurers that support it
17.2Supplier PortalSupplier, Inventory, IdentityA supplier with a VietGara user sees the garage’s purchase orders and confirms delivery

3. Release Details

Release 17.0 — Insurance Claim Tracking

  • Backend (FR-INS-01..05): an Insurance module with insurance_claims linked to a repair order, a vehicle and an insurer from the garage’s own insurers directory (FR-INS-07). The insurer is a record of the Insurance module: not a customer (the policy holder is the vehicle’s customer) and not a supplier, plus claim_events and claim_documents (private files in the file registry, signed URLs only).
    • Status flow: reported → assessed → quote agreed → file submitted → under review → approved or rejected → paid.
    • Deadlines and reminders: 5 working days from the incident to notify the insurer; 24 hours for the assessment; the expected review time by loss size. Overdue steps are flagged and reminded by e-mail and push.
    • The insurer-agreed quote is a versioned snapshot of the garage’s quote.
    • A document checklist with the items listed in the introduction and an upload from the Customer App by the vehicle owner.
  • Settlement split (FR-INS-05) and receivables (FR-REC-02): when a claim is approved, the settlement splits into the owner’s deductible or out-of-cover part and the insurer’s payable part. Payments from the insurer are recorded against the claim and appear in Receivables per claim; vouchers (Release 5.0) are issued for each collection.
  • Frontend: a claim screen on the web console with timeline, deadlines, checklist and attachments; claim status on the repair order and settlement in the owner app; the claim and document upload in the Customer App.
  • Database and API: the planned sections of Database Design and API Specification describe the tables and endpoints.
  • Definition of Done: from a repair order of an insured vehicle, staff create a claim, attach the assessment report, mark the quote as agreed, tick the document checklist and update the status by hand as the insurer answers; the owner uploads a document from the app; after approval the settlement splits and the insurer’s payment clears its receivable.

Release 17.1 — Partner Expansion & Claim Submission

  • E-invoice providers: MISA and BKAV adapters in the E-Invoice Service (Integration Design Section 3.3), selectable per garage next to VNPT and Viettel.
  • Claim file submission (FR-INS-06): package the claim file as a PDF set according to each insurer’s template for manual e-mail or portal submission, and integrate by API with the insurers that offer one (PVI, PTI, Bao Viet first, then others by real onboarding demand).
  • Definition of Done: a garage can choose among four e-invoice providers and issue an invoice with each in its sandbox; a claim file is exported per template, marked submitted, and for one insurer submitted by API in the sandbox.

Release 17.2 — Supplier Portal

  • Supplier link (FR-SUP-02). A garage links a supplier record to a VietGara user with a request that the user confirms (OTP or in-app). It has its own table supplier_user_links and its own consent text; it is a business-to-business link and never touches the customer links of Release 5.1 or the Customer App.
  • Portal (FR-SUP-03). A supplier-facing surface for the linked user, separate from the Customer App: the purchase orders addressed to them (Release 13.0), confirm or decline lines, attach delivery notes and invoices (private files), and see which orders were received. It reuses purchase orders and goods receipts; it never exposes the garage’s costs, customers or stock.
  • Scope guard. The portal sees only documents addressed to the linked supplier. A user who is both a supplier of one garage and a customer of another has two unrelated links and two surfaces.
  • Definition of Done: a garage sends a purchase order to a linked supplier; the supplier user confirms two lines and attaches a delivery note; the garage receives the goods against the order with the delivery note attached; the supplier cannot see any other garage or any customer data.

4. Dependency Diagram

flowchart TD
  P16(["Phase 16 complete"]) --> R170["Release 17.0<br/>Claim tracking"]
  R170 --> R171["Release 17.1<br/>Partner expansion + claim submission"]
  P16 --> R172["Release 17.2<br/>Supplier portal"]
  R171 --> DONE
  R172 --> DONE(["Phase 17 complete / full VietGara"])

Release 17.0 needs the settlement, vouchers and receivables, and the Customer App’s document upload. The partner work of 17.1 can start earlier in parallel for the e-invoice adapters, once Phase 16’s E-Invoice Service exists.