<!--                                                                  -->
<!--  Copyright (C) 2006 RoyaltyShare, Inc.   All Rights Reserved     -->
<!--  $Id$  -->
<!--                                                                  -->
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0" xmlns:dyn="http://exslt.org/dynamic" extension-element-prefixes="dyn">
    <xsl:output method="html" indent="no" doctype-system="http://www.w3.org/TR/html4/strict.dtd" doctype-public="-//W3C//DTD HTML 4.01//EN" encoding="utf-8" />

    <xsl:include href="/app/tools/rps/templates/help/help_layout.xsl" />

    
    <xsl:template name="helpPage">
        <div class="sectionHeader">
            <h1>Help - Payor Transactions</h1>
    	</div>
        <div class="sectionBody">    
            <div class="section">
                <p>
                   The publisher payor transaction page contains details concerning minimum payments, pending transactions, and historical transactions for the specific publisher within a payor.
                </p>
                
                <img src="/production/images/help/rps/{Params/a}/account.gif" /> 
                
                <br class="superBreak" /> 
                
                <p>The transaction interface is separated into four sections.</p>
                
                <h2>
                    "Publisher" section:         
                </h2>
                
                <p>
                    The publisher section is informational only and notes the specific publisher that is being viewed or edited.  Within this section the publisher name, publisher type, and associated admin and/or agent are listed.
                </p>
                
                <h2>
                    "Payor" section:         
                </h2>
                
                <p>
                   The payor section provides the name of the payor that is being  edited for the publisher, with the ability to set a minimum payment for the publisher / payor combination.
                </p>                
                
                <dl>
                    
                    <dt>Name</dt>
                    <dd> - Notes the name of the payor that is being addressed.  This is informational only.</dd>
                    
                    <dt>Client Payor #</dt>
                    <dd> - Notes the client payor number of the payor that is being addressed.  This is informational only and is pulled from payor level information that is entered through the admin tab.</dd>
                    
                    <dt>Status</dt>
                    <dd> - Notes the status of the payor that is being addressed.  This is informational only and is pulled from payor level information that is entered through the admin tab.</dd>
                    
                    <dt>Default</dt>
                    <dd> - Notes if the payor is configured as the default payor.  This is informational only and is pulled from payor level information that is entered through the admin tab.
                        <ul>
                            <li>Default payor is automatically populated on all licenses created.  The payor can be adjusted, through a dropdown on the license, by the user.</li>
                        </ul>
                    </dd>
                    
                    <dt>Minimum Payment</dt>
                    <dd> - Sets the minimum payment for the publisher associated with a specific payor.  This sets the minimum payment level for statements that are generated for this publisher.
                        <ul>
                            <li>If the "Ending Balance" on a statement is less than the assigned "Minimum Payment", the "Amount Payable" will be $0.00, and the balance will be forwarded to subsequent statements until the Minimum Payment is surpassed.</li>
                            <li>Minimum payments are configured separately for each payor.</li>
                        </ul>
                    </dd>
                    
                </dl>
                
                <br />
                
                <h2>"Pending Transactions"</h2>
                
                <p>
                    The pending transactions area provides an interface for creating advances and adjustments that apply to a license.
                </p> 
                
                <p>
                    Note:  Payment information that is entered through the royalty run "Edit Payments" interface will also appear in the interface.
                </p>
                
                <img src="/production/images/help/rps/license/account-pending.gif" />  
                
                <br class="superBreak" />
                
                <dl>
                    <dt>Type</dt>
                    <dd> - Notes the type of transaction that will be applied at the publisher level statement for this payor.
                        <ul>
                            <li>Adjustment</li>
                            <li>Advance</li>
                            <li>Payment</li>
                        </ul>    
                    </dd>
                    
                    <dt>Amount</dt>
                    <dd> - Notes the amount associated with the transaction type that will be applied to the publisher with the next mechanical royalty run.
                        <ul>
                            <li>Adjustments follow the sign of the amount entered by the user.
                                <ul>
                                    <li>Positive adjustments add to the payee balance.</li>
                                    <li>Negative adjustments subtract from the payee balance.</li>
                                </ul>
                            </li>
                            <li>Advances are always considered to be payment out to the publisher and can only be entered as a positive number.</li>
                            <li>Payments are subtracted from the publisher balance and can only be entered as a positive number.</li>
                        </ul>
                    </dd>
                    
                    <dt>Transaction Date</dt>
                    <dd> - Notes the user specified date that will be associated with the transaction.  Associated dates will be shown next to the publisher level transaction on mechanical royalty statements.</dd>
                
                    <dt>Check #</dt>
                    <dd> - Notes the user specified check number that will be associated with the transaction.  Check number will be shown next to the publisher level transaction on mechanical royalty statements.</dd>
                
                    <dt>Memo</dt>
                    <dd> - Notes user specified information that will be associated with the transaction.  Memos will be shown next to the publisher level transaction on mechanical royalty statements.</dd>
                    
                    <dt>Delete</dt>
                    <dd> - Allows the user to delete a specific transaction by selecting the "Delete" checkbox and then "Updating" the license page.
                        <ul>
                            <li>Only transactions that have not been committed in a mechanical royalty run can be deleted.</li>
                        </ul>
                    </dd>
                    
                    <dt>Add Another Transaction</dt>
                    <dd> - By selecting this field multiple transactions can be added to a license at one time.</dd>
                    
                </dl>
                
                <br />
                
                <h2>
                    "Transaction History"       
                </h2>
                
                <p>The transaction history area provides a listing of transactions for the publisher that have been included as part of a committed mechanical royalty run.</p>
                
                <img src="/production/images/help/rps/publisher/account-history.gif" />    
                
                <p>
                    This section is informational only without the ability to make edits or changes to this data.
                </p>
               			
                <br class="superBreak" />
    	    </div>
    	</div>
    </xsl:template>
    
    
</xsl:stylesheet>    

