Reseller Record Correlation Reports

If you store entitlement data on your own systems, you should supply it daily to Bango to allow Bango to perform a record correlation process and send you correlation reports.

The record correlation process checks that your data matches the Bango data, and highlights any discrepancies.

Access control

When you sign up to use the Bango Resale API for resellers, Bango Support will supply you with:

• Amazon S3 endpoint: all your correlation data will be uploaded here
• Access key: your unique username for accessing the S3 endpoint
• Secret key: your unique password for accessing the S3 endpoint

Correlation types

Bango supports two types of correlation:

For both types of correlation, if there is more than one record for an entitlement in the same period you should provide us with the latest one.

Bango performs similar record correlation processes with merchants who make their products and services available through Bango Resale.

Unless otherwise agreed, the Bango data is considered the source of truth.

Supplying correlation data to Bango

To supply correlation data to Bango, you must upload it to your reporting Amazon S3 bucket provided by Bango by 04:00 UTC on the day after the end of the reporting period. Provide one file for each merchant for each correlation period.

Upload location

s3://{customer}/CorrelationReports/{merchant}/Input

Where:

• customer is your unique Amazon S3 bucket
• merchant is a merchant account key, as used when creating an entitlement

Filenames

There are three correlation periods: monthly, weekly (Monday to Sunday), and daily.

Filenames include the start and end dates for the correlation period. Use this format:

{start}-{end}.csv

Where start and end are YYYYMMDD UTC dates. For monthly and weekly periods, the end date is inclusive. For daily periods, the end date is exclusive (in other words, the day after the start day). Here are some examples:

File format

All files must be Windows-1252 encoded and contain RFC 4180-compliant comma-separated values (CSV). All times must be UTC.

The data you provide to Bango must be in the following format:

Data comparison results

When comparing the data you supply to the data in the Bango Platform, Bango checks the following:

Record correlation report output files

Bango will generate four output files for each correlation period and store them in your S3 bucket at the location:

s3://{customer}/CorrelationReports/{merchant}/Output

Where:

• customer is your unique Amazon S3 bucket
• merchant is a merchant account key, as used when creating an entitlement

The four correlation reports are:

All report files are Windows-1252 encoded and contain RFC 4180-compliant comma-separated values (CSV). The columns are:

To resolve any discrepancies, Bango recommends using our Batch processor. If you are unsure on the best steps to take to resolve the discrepancies please contact Bango Support.

Here are some example correlation reports:

Matched correlation report:

EntitlementId,ExternalEntitlementId,CorrelationResult
f5666778-dcee-4365-93a1-5f385f40eafc,,OK: Entitlement data matches
15dc371d-8c62-4c14-8cfc-5561d352f2e1,,OK: Entitlement data matches
5ec1ff0f-dc1d-4d0c-bc9e-b50b172193d6,,OK: Entitlement data matches
bb39454e-1841-4077-8ceb-a3828c0a9047,,OK: Entitlement data matches

Bango-only correlation report:

EntitlementId,ExternalEntitlementId,CorrelationResult
8a679908-2004-4ec8-a8c7-4c36e8dd5a5f,,Error: Extra Entitlement detected in Bango system
af6268b7-2029-4a60-b435-b21747efc54f,,Error: Extra Entitlement detected in Bango system

Reseller-only correlation report:

EntitlementId,ExternalEntitlementId,CorrelationResult,CorrelationDescription
bbb63636-3fe7-450e-bcda-073e2b6eee89,,Error: Missing Entitlement detected in Bango system
dfc92708-362c-472c-9052-d21e1e5b68fa,,Error: Missing Entitlement detected in Bango system

Unmatched correlation report:

EntitlementId,ExternalEntitlementId,CorrelationResult
6c92895b-b521-44f2-afb8-1a83db9aff50,,Error ProductKey is different
ee803684-847b-4549-84cf-7c7879221571,,Error Status is different
9915b3f5-d5bb-4569-afb0-3e64bde9909e,,Error CustomerIdentifier is different
d1a70dcc-0b24-4531-991a-47df73b5caf3,,Error: Multiple differences