Version 2.
2 – August 2016
Signature Reconciliation Feed – Implementation Guidelines
Rakuten Affiliate Network's Signature Reconciliation Feed provides transaction and payment data to publishers
who use our U1/Signature matching functionality. These feeds make it easier for you to match the Signature data
with payment information. To receive these reports, you must have an FTP or SFTP server and be set up by
Rakuten Affiliate Network to receive Signature Reconciliation feed.
Report Types
Rakuten Affiliate Network sends four reports as part of the Signature Reconciliation Feed:
Daily U1 Transaction Report – Sent daily. This report provides detailed, transaction-level reporting of all
U1 transactions that have matched since the previous day’s report. This report is sent daily, and the
process for matching data is typically completed within a day. Any unmatched transactions are sent with
the next file. On the fourth day of each month, the report also includes all unmatched transaction data
from the previous month.
Note that if an unmatched transaction from this list matches after we have sent it as unmatched, the same
transaction ID will be sent again.
Monthly Reports – There are two reports that are sent once a month.
The Monthly U1 Reports contain all daily U1 transactions sent for the previous month. The MonthlyU1 Report
th
is sent twice on the 4 day of each month
th
The DailyU1_Monthly Report is sent on the 5 day of the month. The Monthly U1 Reports are sent after
Rakuten Affiliate Network has sent advertiser invoices. These reports contain adjusted commissions.
Payment Report – This report includes invoice-level detail of the payments. Rakuten Affiliate Network
sends this report daily and will only include data if a payment was issued on the previous day. Matching
with its transaction-level detail, advertiser payments can be easily reconciled with the U1 data.
Daily U1 Transaction Report
File Name – The daily U1 transaction report will have a file name like
2574052_DailyU1_2016June01-1649.xml if 2574052 is the SID and 16:49 is the time (GMT) when
the file was generated.
Top Level Data Structure – The main tag is <XROOT> and </XROOT>. The next nested tag is
<PRJ_LOYALTY_METADATA_HDR> and </PRJ_LOYALTY_METADATA_HDR>.
Please note: the close tag appears directly above </XROOT> at the bottom of the file.
Metadata – Here is what the metadata will look like:
Page 1 of 8
<FILENAME>2574052_DailyU1_2016June01-1645.xml</FILENAME>
<SID>2574052</SID>
<START_DATE>2016-05-31</START_DATE>
<END_DATE>2016-06-01</END_DATE>
<REPORT_TYPE>U1 Member Daily Feed</REPORT_TYPE>
The tags are <FILENAME>, <SID>, <START_DATE>, <END_DATE>, and <REPORT_TYPE>.
Transaction Data – There is only one type of record in this file, U1 Daily Data. Its tags are
<PRJ_LOYALTY_U1_DAILY> and </PRJ_LOYALTY_U1_DAILY>. There is one record for each transaction.
Here is what a Daily Data record will look like:
<MEMBER_ID>U1_here</MEMBER_ID>
<MATCH_DATE>2016-May-31</MATCH_DATE>
<MATCH_TIME>1730</MATCH_TIME>
<MERCHANT_PARTNER_ID>33</MERCHANT_PARTNER_ID>
<MERCHANT_PARTNER_NAME>Rakuten Affiliate Network
merchant</MERCHANT_PARTNER_NAME>
<PRODUCT_SKU_NUMBER>1</PRODUCT_SKU_NUMBER>
<PRODUCT_NAME>HEADPHONES</PRODUCT_NAME>
<TRANSACTION_ID>123</TRANSACTION_ID>
<ORDER_ID>21</ORDER_ID>
<TRANSACTION_DATE>2016-May-30</TRANSACTION_DATE>
<TRANSACTION_TIME>1807</TRANSACTION_TIME>
<SALES_AMOUNT>99.95</SALES_AMOUNT>
<QUANTITY>1</QUANTITY>
<BASELINE_COMMISSION>10</BASELINE_COMMISSION>
<ADJUSTED_COMMISSION>0</ADJUSTED_COMMISSION>
<TOTAL_COMMISSION>10</TOTAL_COMMISSION>
<PROCESS_DUE_DATE>2016-May-31</PROCESS_DUE_DATE>
<PROCESS_DUE_TIME>1701</PROCESS_DUE_TIME>
The tags here are: <MEMBER_ID>, <MATCH_DATE>, <MATCH_TIME>, <MERCHANT_PARTNER_ID>,
<MERCHANT_PARTNER_NAME>, <PRODUCT_SKU_NUMBER>, <PRODUCT_NAME>,
<TRANSACTION_ID>, <ORDER_ID>, <TRANSACTION_DATE>, <TRANSACTION_TIME>,
<SALES_AMOUNT>, <QUANTITY>, <BASELINE_COMMISSION>, <ADJUSTED_COMMISSION>,
<TOTAL_COMMISSION>, <PROCESS_DUE_DATE>, and <PROCESS_DUE_TIME>. Definitions for these
can be found in Appendix A.
Monthly Reports
MonthlyU1 Report
th
File Name – The first monthly report, MonthlyU1 Report, is sent on the 4 day of the month and will have a
filename like 2574052_MonthlyU1_2016June04-1645.xml if 2574052 is the SID and 16:45 is the
time (GMT) when the file was generated.
Page 2 of 8
Top Level Data Structure – The main tag is <XROOT> and </XROOT>. The next nested tag is
<PRJ_LOYALTY_METADATA_HDR> and </PRJ_LOYALTY_METADATA_HDR>. Note that the close tag
appears directly above </XROOT> at the bottom of the file.
Metadata – Here is what the metadata will look like:
<FILENAME>2574052_MonthlyU1_2016June04-1645.xml</FILENAME>
<SID>2574052</SID>
<START_DATE>2016-05-01</START_DATE>
<END_DATE>2011-05-31</END_DATE>
<REPORT_TYPE>U1 Member Monthly Feed</REPORT_TYPE>
The tags are <FILENAME>, <SID>, <START_DATE>, <END_DATE>, and <REPORT_TYPE>.
Transaction Data – There is only one type of record in this file, monthly adjusted commission data. It is identified
by tags <PRJ_LOYALTY_U1_DAILY> and </PRJ_LOYALTY_U1_DAILY>.
Here is what a monthly data record will look like:
<TRANSACTION_ID>E31DACCA3234ECC27253A14FB5C59F38</TRANSACTION_ID>
<ADJUSTED_COMMISSION>5</ADJUSTED_COMMISSION>
<TOTAL_COMMISSION>50</TOTAL_COMMISSION>
The tags are <TRANSACTION_ID>, <ADJUSTED_COMMISSION>, and <TOTAL_COMMISSION>. Definitions
for these can be found in Appendix A.
This Transaction ID can be matched against the daily U1 report to identify a transaction.
DailyU1_Monthly Report
th
File Name – The DailyU1_Monthly Report is sent on the 5 day of the month and will have a file name like
2574052_DailyU1_Monthly_2016June05-1649.xml if 2574052 is the SID and 16:49 is the time
(GMT) when the file was generated.
Top Level Data Structure – The main tag is <XROOT> and </XROOT>. The next nested tag is
<PRJ_LOYALTY_METADATA_HDR> and </PRJ_LOYALTY_METADATA_HDR>. Please note: the close tag is
directly above </XROOT> at the bottom of the file.
Metadata – Here is what the metadata look like:
<FILENAME>2574052_DailyU1_Monthly_2016June01-1645.xml</FILENAME>
<SID>2574052</SID>
<START_DATE>2016-05-01</START_DATE>
<END_DATE>2016-05-31</END_DATE>
<REPORT_TYPE>U1 Member Monthly Feed</REPORT_TYPE>
The tags are <FILENAME>, <SID>, <START_DATE>, <END_DATE>, and <REPORT_TYPE>.
Monthly U1 Data – There is only one type of record in this file, monthly U1 data. Its tags are
<PRJ_LOYALTY_U1_DAILY> and </PRJ_LOYALTY_U1_DAILY>. There is one record for each transaction.
Here is a sample monthly record:
<MEMBER_ID>U1_here</MEMBER_ID>
Page 3 of 8
<MATCH_DATE>2016-May-31</MATCH_DATE>
<MATCH_TIME>1730</MATCH_TIME>
<MERCHANT_PARTNER_ID>33</MERCHANT_PARTNER_ID>
<MERCHANT_PARTNER_NAME>Rakuten Affiliate Network
merchant</MERCHANT_PARTNER_NAME>
<PRODUCT_SKU_NUMBER>1</PRODUCT_SKU_NUMBER>
<PRODUCT_NAME>HEADPHONES</PRODUCT_NAME>
<TRANSACTION_ID>123</TRANSACTION_ID>
<ORDER_ID>21</ORDER_ID>
<TRANSACTION_DATE>2016-May-30</TRANSACTION_DATE>
<TRANSACTION_TIME>1807</TRANSACTION_TIME>
<SALES_AMOUNT>99.95</SALES_AMOUNT>
<QUANTITY>1</QUANTITY>
<BASELINE_COMMISSION>10</BASELINE_COMMISSION>
<ADJUSTED_COMMISSION>0</ADJUSTED_COMMISSION>
<TOTAL_COMMISSION>10</TOTAL_COMMISSION>
<PROCESS_DUE_DATE>2016-May-31</PROCESS_DUE_DATE>
<PROCESS_DUE_TIME>1701</PROCESS_DUE_TIME>
The tags here are: <MEMBER_ID>, <MATCH_DATE>, <MATCH_TIME>,
<MERCHANT_PARTNER_ID>, <MERCHANT_PARTNER_NAME>,
<PRODUCT_SKU_NUMBER>, <PRODUCT_NAME>, <TRANSACTION_ID>, <ORDER_ID>,
<TRANSACTION_DATE>, <TRANSACTION_TIME>, <SALES_AMOUNT>, <QUANTITY>,
<BASELINE_COMMISSION>, <ADJUSTED_COMMISSION>, <TOTAL_COMMISSION>,
<PROCESS_DUE_DATE>, and <PROCESS_DUE_TIME>. Appendix A provides definitions for these.
Unmatched Monthly U1 Transactions – This file includes transactions that matched for Member ID in that month.
The file also includes unmatched transactions from the previous month. These transactions have the value NULL
for Member ID and Match Date.
Payment Report
File Name – The payment reconciliation report will have a filename like 2574052_Payment_2016May31-
1645.xml if 2574052 is the SID and 16:45 is the time (GMT) when the file was generated.
Top Level Data Structure – The main tag is <PRJ_LOYALTY_METADATA_HDR> and
</PRJ_LOYALTY_METADATA_HDR>.
Metadata – Here is what the metadata will look like:
<FILENAME>2574052_Payment_2016May31-1645.xml</FILENAME>
<SID>2574052</SID>
<START_DATE>2016-05-30</START_DATE>
<END_DATE>2016-05-31</END_DATE>
<REPORT_TYPE>Payment Feed</REPORT_TYPE>
The tags are <FILENAME>, <SID>, <START_DATE>, <END_DATE>, and <REPORT_TYPE>.
Page 4 of 8
Payment Summary – Inside the metadata tag and after the metadata, the top level of data is the Payment
Summary. Its tag is <PRJ_LOYALTY_PAYMENT_SUMMARY> and
</PRJ_LOYALTY_PAYMENT_SUMMARY>. There is one Payment Summary per payment. It includes both data
and a series of Payment Details.
Here is what the data in it will look like:
<PAYMENT_ISSUE_DATE>2016May31-1120</PAYMENT_ISSUE_DATE>
<CHECK_ACH_NUMBER>12345</CHECK_ACH_NUMBER>
<LS_PAYMENT_ID>67890</LS_PAYMENT_ID>
<PAYMENT_TYPE>Domestic Check</PAYMENT_TYPE>
<PAYMENT_CURRENCY>Dollar</PAYMENT_CURRENCY>
<PAY_AMOUNT>10000.00</PAY_AMOUNT>
The tags are <PAYMENT_ISSUE_DATE>, <CHECK_ACH_NUMBER>, <LS_PAYMENT_ID>,
<PAYMENT_TYPE>, <PAYMENT_CURRENCY>, and <PAY_AMOUNT>. Definitions for these can be found in
Appendix B.
Payment Detail – In addition to this data in the Payment Summary, there will be a series of Payment Details. The
tags for Payment Detail are <PRJ_LOYALTY_PAYMENT_DTL> and
</PRJ_LOYALTY_PAYMENT_DTL>. There is one Payment Detail per invoice.
A record includes data about the payment and a series of Transaction Details. Data about the payment are
formatted as:
<PARTNER_NAME>Rakuten Affiliate Network Merchant</PARTNER_NAME>
<PARTNER_ID>32</PARTNER_ID>
<INVOICE_NUMBER>25243</INVOICE_NUMBER>
<INVOICE_PERIOD_START_DATE>2016May01-
0000</INVOICE_PERIOD_START_DATE>
<INVOICE_PERIOD_END_DATE>2016May31-0000</INVOICE_PERIOD_END_DATE>
<COMMISSION_AMT_EARNED>100.00</COMMISSION_AMT_EARNED>
<FORWARD_BALANCE_AMT>0</FORWARD_BALANCE_AMT>
<ADJUSTMENT_BONUS_AMT>0</ADJUSTMENT_BONUS_AMT>
<HOLD_AMT>0</HOLD_AMT>
<PAYMENT_AMT>100.00</PAYMENT_AMT>
The tags are <PARTNER_NAME>, <PARTNER_ID>, <INVOICE_NUMBER>,
<INVOICE_PERIOD_START_DATE>, <INVOICE_PERIOD_END_DATE>, <COMMISSION_AMT_EARNED>,
<FORWARD_BALANCE_AMT>, <ADJUSTMENT_BONUS_AMT>, <HOLD_AMT>, and <PAYMENT_AMT>.
Definitions for these can be found in Appendix B.
Transaction Detail – In addition to this data, each Payment Detail includes a series of Transaction Details. There is
one Transaction Detail for each transaction covered by the invoice. The tags for a
Transaction Detail are <PRJ_LOYALTY_TRANSACTION_DTL> and
</PRJ_LOYALTY_TRANSACTION_DTL>.
There is one record for each transaction detail. Here is a sample transaction detail:
<MEMBER_ID>U1_here</MEMBER_ID>
<MATCH_DATE>2016-May-31</MATCH_DATE>
<MATCH_TIME>1730</MATCH_TIME>
Page 5 of 8
<MERCHANT_PARTNER_ID>33</MERCHANT_PARTNER_ID>
<MERCHANT_PARTNER_NAME>Rakuten Affiliate Network
merchant</MERCHANT_PARTNER_NAME>
<PRODUCT_SKU_NUMBER>1</PRODUCT_SKU_NUMBER>
<PRODUCT_NAME>HEADPHONES</PRODUCT_NAME>
<TRANSACTION_ID>123</TRANSACTION_ID>
<ORDER_ID>21</ORDER_ID>
<TRANSACTION_DATE>2016-May-30</TRANSACTION_DATE>
<TRANSACTION_TIME>1807</TRANSACTION_TIME>
<SALES_AMOUNT>99.95</SALES_AMOUNT>
<QUANTITY>1</QUANTITY>
<BASELINE_COMMISSION>10</BASELINE_COMMISSION>
<ADJUSTED_COMMISSION>0</ADJUSTED_COMMISSION>
<TOTAL_COMMISSION>10</TOTAL_COMMISSION>
<PROCESS_DUE_DATE>2016-May-31</PROCESS_DUE_DATE>
<PROCESS_DUE_TIME>1701</PROCESS_DUE_TIME>
The tags here are: <MEMBER_ID>, <MATCH_DATE>, <MATCH_TIME>, <MERCHANT_PARTNER_ID>,
<MERCHANT_PARTNER_NAME>, <PRODUCT_SKU_NUMBER>, <PRODUCT_NAME>, <TRANSACTION_ID>,
<ORDER_ID>, <TRANSACTION_DATE>, <TRANSACTION_TIME>, <SALES_AMOUNT>, <QUANTITY>,
<BASELINE_COMMISSION>, <ADJUSTED_COMMISSION>, <TOTAL_COMMISSION>,
<PROCESS_DUE_DATE>, and <PROCESS_DUE_TIME>.
Definitions for these can be found in Appendix A.
How Do I Get Enabled for the Signature Reconciliation Feed?
To become enabled for Signature Reconciliation Feed, please send an email to
[email protected] with
this information:
FTP Server Name
FTP Username
FTP Password
Target Folder (Optional)
After you send us this info, the Customer Support team will integrate your FTP with our system and send a test file
to it. Once you confirm receiving the test file, the Customer Support team will finalize the setup process and in 24
to 48 hours you will begin receiving Signature Reconciliation files.
Who Do I Contact Regarding a Problem or Feedback?
Please contact your Network Development Manager for questions regarding Signature Reconciliation Feeds. If you
do not have a Network Development Manager, please contact our Customer Support team via email at
[email protected] or via phone at 888-880-8430 in the U.S. and 1-646-943-8200 for publishers outside
the U.S.
Page 6 of 8
Appendix A: Definitions for Transaction Description
Info Tag Name
Member ID A variable field that you define. This can contain
up to 72 alphanumeric characters, with mixed-
case letters.
Match Date The date on which Rakuten Affiliate Network
matches a transaction with the member of your
site who made it.
Match Time The time at which Rakuten Affiliate Network
matches a transaction with the member of your
site who made it.
Merchant Partner ID Rakuten Affiliate Network’s numeric value that
identifies a particular advertiser. This value is a
constant.
Merchant Partner Name An advertiser’s name as it appears within the
Rakuten Affiliate Network . The advertiser can
alter this value without notice to either Rakuten
Affiliate Network or publishers.
Product SKU Number The stock-keeping unit that is assigned by the
advertiser. Each product in an advertiser’s
inventory has a unique SKU value.
Product Name The name an advertiser gives to a product.
Transaction ID A numeric ID that Rakuten Affiliate Network
assigns to each transaction.
Order ID The order number that is assigned by the
advertiser. This represents one shopping session.
Transaction Date The date that the consumer (your member)
completes his or her order as reported by the
advertiser.
Transaction Time The time in GMT that the consumer (your
member) completes his or her order as reported
by the advertiser.
Sales Amount The total pre-tax and pre-shipment price of the
line item multiplied by the quantity.
Quantity The number of each product a consumer buys in
his or her order.
Baseline Commission Commission amount before any adjustments are
made.
Adjusted Commission Commission amount after adjustments are made.
When you reach a certain level of sales, orders,
clicks, or impressions in a month, advertisers
often pay additional commissions. To do so, they
make an adjustment.
Page 7 of 8
Total Commissions ($) The total dollar amount of the commission
earned by you. All commissions are pending
credit card authorization and returned
merchandise.
Process Due Date The date the transaction was processed by the
Rakuten Affiliate Network system.
Process Due Time The time in GMT that the transaction was
processed by the Rakuten Affiliate Network
system.
Page 8 of 8
