> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bango.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Reseller correlation file format

> Input and output CSV formats for reseller entitlement correlation.

Use this format when submitting reseller entitlement data for correlation with DVM.

<Note>
  Optional columns must still be present in the CSV header even when no value is supplied.
</Note>

## Input file format

| Column name | Type | Required | Description |
| - | - | :-: | - |
| `ExternalEntitlementId` | String | No | Your unique entitlement identifier |
| `CustomerIdentifier` | String | Yes | Unique customer identifier used for correlation |
| `EntitlementId` | UUID | Yes | Unique entitlement identifier |
| `Status` | String | Yes | Current entitlement status |
| `MerchantAccountKey` | String | No | Merchant account identifier |
| `ProductKey` | String | Yes | Product identifier used for correlation |
| `OfferKey` | String | No | Offer identifier |
| `DisplayName` | String | No | Human-readable entitlement name |
| `CreatedDate` | RFC 3339 timestamp | No | Entitlement creation date |
| `ActivatedDate` | RFC 3339 timestamp | No | Activation date |
| `SuspendedDate` | RFC 3339 timestamp | No | Suspension date |
| `ResumedDate` | RFC 3339 timestamp | No | Resume date following suspension |
| `ExpiryDate` | RFC 3339 timestamp | No | Scheduled expiry date |
| `EndDate` | RFC 3339 timestamp | No | Entitlement end date |

## Correlation processing

DVM uses the unique `EntitlementId` to identify the corresponding entitlement.

The following values are then compared:

* `CustomerIdentifier`
* `ProductKey`
* `Status`

## Output file format

The output contains both the values supplied by you and the corresponding values held by DVM.

| Column name | Description |
| - | - |
| `ExternalEntitlementId` | Your entitlement identifier |
| `CustomerIdentifier` | Customer identifier supplied in your input file |
| `EntitlementId` | Entitlement identifier supplied in your input file |
| `MerchantAccountKey` | Merchant account supplied in your input file |
| `Status` | Status supplied in your input file |
| `ProductKey` | Product supplied in your input file |
| `OfferKey` | Offer supplied in your input file, if provided |
| `CorrelationResult` | Overall correlation outcome |
| `CorrelationResultReason` | Detailed explanation of the correlation outcome |
| `BangoEntitlementId` | Matching entitlement identifier held by DVM |
| `BangoCustomerIdentifier` | Customer identifier held by DVM |
| `BangoStatus` | Status held by DVM |
| `BangoProductKey` | Product key held by DVM |

Depending on your configuration, additional custom fields can be supported.

## Related documentation

<CardGroup cols={2}>
  <Card title="Correlation reports" icon="arrows-left-right" href="/reconciliation/correlation-reports">
    Upload, processing, results, and output options.
  </Card>

  <Card title="Content provider correlation file format" icon="file-csv" href="/reconciliation/content-provider-correlation-file-format">
    Input and output format for content provider correlation.
  </Card>
</CardGroup>