Académique Documents
Professionnel Documents
Culture Documents
3
New reporting sections
• Summary
• Earnings
• Payments
Multi-location
For partners operating in more than
one area, the option for switching
location is available within the
Summary section.
NOTE: Earnings and payment reporting will now be displayed in your local currency per your registered location.
This will differ from how it is displayed today in PIEX, where earnings and payments reporting is presented in the
currency per your user settings. The payment currency selected in your payment profile will not be impacted by this
change. You will continue to receive payment in the currency selected.
Earnings example
Earnings are split into “Paid” and “Unpaid”. “Unpaid earnings” are
yet to be scheduled to be paid.
A hypothetical example of how this works:
A partner earns $10 per month, after months 1 to 5:
• Their total earnings will = $50
• Their paid earnings will = $0
• Unpaid earnings will = $50
After month 7:
• Their total earnings will = $70
• Their paid earnings will = $60
• Unpaid earnings will = $10
The earnings
section … cont
3. More dimensions available
• Fee vs. adjustment.
4. Unpaid earning transaction data
can be downloaded for further
analysis as a statement. This is
covered in more detail within the
‘Use cases – download statements
section’.
Subscription ID A13f41f6-3sge-5fwx6-6253-5274326
Lever/accelerator Accelerator
Calculation rate 6
Payment ID Both 123456789 An internal number used to reconcile earned incentives with
payments
Payment Status Both Payment Sent Where a payment is in the payment process
Earning period Semester Jul – Dec 2017 No need for period when you have exact Transaction Date
Withholding tax applicable Redundant because only a Y/N field equal to "Y" as long as “WHT” amount is higher than zero
WHT amount currency INR Redundant field because WHT currency is in the partner currency (=“Payment amount currency”)
SAP company code 1234 These SAP-related fields used to reference Microsoft internals systems, hence not as relevant externally
ROC APOC Useful for Microsoft internally but not as relevant externally
Claim amount currency Claims-dedicated columns are being deprecated, claims will be treated as a type of earning
Approved claim amount Claims-dedicated columns are being deprecated as redundant. This value will be available in another column (see
"payment amount" column)
Ad hoc payment amount .00 Claims-dedicated columns are being deprecated as redundant. This value will be available in another column.
Invoice paid amount 742.80 Column deprecated but value still available in “payment amount”
Reason code
SAP BP# 123456789 These SAP-related fields used to reference Microsoft internals systems, hence not as relevant for partners.
SAP CA# 12345678987654 These SAP-related fields used to reference Microsoft internals systems, hence not as relevant for partners.
Earning Period Semester Jan – Jun 2017 Unavailable in payment file but available in earning file. Use "Payment ID" as lookup key.
Comments
Disputes
• The Dispute payment functionality is
no longer integrated within PIEX.
• Payment disputes are sent to
Microsoft Support. The standard SLA
for a response is 5 days.
• When contacting Support to dispute
a payment it is helpful to include the
individual Payment Clearing
Number (only available from the
Export to Excel file within the
Download payment details option).
What is not changing
What is not changing
Use case Change Entry point
Setting up and managing bank and tax As usual – no change Partner Membership Center (accessed via Manage my
details account on MPN)
https://partners.microsoft.com/PartnerProgram/PartnerMe
mbershipCenter.aspx
Q – How do I download cross-program monthly earnings down to transaction and customer level?
A – Please navigate to Payments > Click on “View” Statement > Click on “Download Transactions”