From Wiki

Introduction

The main change to v2 is the ability to amend commission values at a Transaction and Commission Group Level.

Configuring batch commission validation for an account

Goto the merchants account.

On the right hand menu select ‘Batch Process Commissions’. This page allows you to set up batch processing:

• Select your transfer method (you have the option of FTP, HTTP or Manual Upload).
• Tell us where your commissions file is.
• Indicate whether your CSV file contains a header row.
• Indicate whether you would like to have duplicate commissions removed automatically.
• If you selected FTP or HTTP as you transfer method, select how frequently you would like for us to fetch the file from your server.
• Click ‘Save settings and Fetch Files’. You will now be taken through the validation process. If you scheduled daily or weekly data collection, this process will happen automatically from now on.

Scheduled data collection and processing

Daily collection will happen each morning at 2 am. Weekly collection and processing will happen on a Wednesday at 2 am. An email will be sent to you confirming that the process happened and giving you feedback on each commission validated.

Format of the commissions file

The process works by reading in commissions from a CSV (comma separated value) file. This file contains 1 record for each commission that requires processing. Commissions can be accepted or declined.

The CSV file must contain the following fields in the following order, each field being separated by a comma and each record being on a new line:

The order ref is the reference you passed to us as the extra field on your sales confirmation page.

The Transaction Date field must be in European date format (day/month/year) as shown above. The time must be 24 hour format.

The status must be either of:

• amended
• accepted
• declined

Sale Amendment Rules

• must contain a new value in 'New Sale Price' for the whole transaction
• format for Commission Group Breakdown mirrors that on confirmation tracking code you have used. See Here for formatting
• All Commission Group Codes must be listed if the transaction contains more than one CG
• If the transaction has only one Commission Group associated and the Commission Group does not change the CG Code and Price may be ommited
• Status will move from pending to validated

Example of a transaction with a single CG which is only changing sale value

OrderRef,TransactionDate,Status,StatusNote,NewSalePrice,CGBreakdown,Currency
85068320NYCMQ,23/11/2009 22:30:00,Amended,,265.30,

Example of a transaction with multiple CG's

OrderRef,TransactionDate,Status,StatusNote,NewSalePrice,CGBreakdown,Currency
85068320NYCMQ,23/11/2009 22:30:00,Amended,,265.30,DEFAULT:23.00|CODEA:129.30|CODEZ:113.00,GBP

Note: when multiple CG's make up a transaction that is to be amended the whole breakdown must be detailed to ensure data integrity, this includes CG's that have not changed value

Non-unique Order References

Non-unique order references should be used if the you cannot guarantee that your order reference will be unique. Each transaction must still be assigned an order reference and these must still be unique within a time span of 24 hours.

If you requested that your account is set up to use non-unique order references, both the order reference and the transaction date will be used to find a matching transaction.

To allow for discrepancies in the date and time of the transaction as recorded by our and your systems, any record recorded by us with a transaction date of + or - 12 hours from the date provided by you will be deemed a match.

Auto De-duplication

If auto de-duplication is selected, when duplicates are found the oldest is confirmed and all others are declined with the reason for declining set to ’de-dup’.

Unmatched commissions

Any unmatched commissions will be reported back to you. These will need to be confirmed by hand.