CSV Schema
| Column Name | Data Type | Accepted Values | Description | Example | Required |
| DealID | String | A unique reference for this deal which allows us to identify the price in the system. | MLC00001P | Yes | |
| CAP ID | Integer | The CAP ID of the vehicle | 71036 | Yes | |
| CAPType | String | The type of vehicle (Car or Van) | Van | No* | |
| FinanceType | String | B / P | Whether the deal is for business or personal users. | B | Yes |
| DepositValue | Integer | 3 / 6 / 9 /12 | The initial rental of the deal in months | 6 | Yes |
| Term | Integer | 24 / 36 / 48 | The length of the deal in months | 24 | Yes |
| MonthlyPayment | Float | The monthly payment amount for the deal in pounds and pence | 213.50 | Yes | |
| AnnualMileage | Integer | 5000 / 8000 / 10000 / 12000 / 15000 / 20000 | The annual mileage of the deal | 8000 | Yes |
| DocumentFee | Float | The fee which you charge for the deal in pounds and pence | 150.00 | Yes | |
| InStock | Integer | Whether or not you have the vehicle in stock | 1 | No | |
| ExpiryDate | Date String (dd/mm/yyyy) | An optional expiration date for the deal | 30/06/2018 | No |
*Important: LeaseFetcher does not currently support vans so if your CSV contains van data then the CAPType column is required. Any rows not marked as 'car' will simply be ignored. If your CSV does not contain van data then you can omit this column.
Column Headers
The first row of your CSV should contain the required column names from the above schema. The order of the columns does not matter but the names do have to match with the schema exactly. Don’t worry about any additional columns you have in your feed - these will simply be ignored.