RAC Cover File & Data Processes

8.1 Example Delta Cover File

8.2 Example Full Refresh Cover File With Full Refresh Cover Files, each subsequent file overrides the preceding one – therefore no transaction flags are required; each cover file represents those assets that are on cover at that point in time and remain on cover until the next cover file is received. Therefore any new records are treated as additions, and any records not sent on a subsequent file are treated as deletions. UAIs are still used to indicate changes (e.g. change of registration), as highlighted in the example below. The file and field formatting should still follow the allowed values as per Sections 6 & 7 of this document.

File 1

File 2 This file is making:

• 1 addition the final asset (FL52RFT) on File 2 did not appear in file 1, and therefore will be added as a new asset and become billable for the first time. You can see that this is the only asset that has financial data associated with it (green highlighted section) • 1 update the red highlighted section is a change of registration – the UAI is the key data item for this transaction. • 1 deletion “TK59MAN” appeared in file 1, but not in file 2, and will therefore be cancelled with immediate effect. If this is within a contractual cooling off period, then a refund will be automatically calculated.

29

Go Home