REFUND AMOUNT

IAM NOT PURCHASE THIS APPS BUTN MY CARD AUTOMATICE CERDIT 550 RS PLS MY PAYMENT RETURN MY ACCOUNT
Billed To:
[email protected]
imran hanfi
8 south hatipala
8
indore
m.p 452001
IND
Order ID: MH3W6NJDZK
Receipt Date: 27/06/13
Order Total: Rs 550
Billed To: Visa .... 9008
Item
Developer
Type
Unit Price
Hair Salon - Fun Kids games, Unlock Everything
Report a Problem
George CL
In App Purchase
Rs 550
Order Total:
Rs 550
Please retain for your records
Please See Below For Terms And Conditions Pertaining To This Order.
Apple Inc.
You can find the iTunes Store Terms of Sale and Sales Policies by launching your iTunes application and clicking on Terms of Sale or Sales Policies
Answers to frequently asked questions regarding the iTunes Store can be found at http://www.apple.com/uk/support/itunes/store/

We are itunes users just like you.
Contact itunes support

Similar Messages

Refund amount and disable auto charge for subscrip...

Hello , Here is my order number ****************272
Please refund the amount and how can i disable auto recharge option ? I want it for USA but unfortunately subscribed for UK .. Please help
Thanks

You can use the links below to view and control any possible recurring charges:
Subscriptions: (Cancel any subscriptions you may be a part of)
https://secure.skype.com/account/call-phones/packages
Usage History (6 months):
https://secure.skype.com/account/usage
Billings & Payments: (If enabled, disable Auto-Recharge)
https://secure.skype.com/account/payment/atu/entry
Purchase History: (Every payment you've made since you had the account)
https://secure.skype.com/wallet/account/orders
Skype Number (Under settings, cancel any recurring number subscriptions)
https://secure.skype.com/account?page=onlineNumber
Once complete, request a refund for unused/unauthorised services
https://support.skype.com/en/faq/FA297

Check Refunds Authorization

Hi All,
We have a requirement at our client place-
We would like to issue checks to the business partners through automatic payment program FPY1.
Clerk should be able to issue the check if the amount is les than $ 500
If the amount is greater than $ 500 and less than $ 1000 supervisor approval is needed.
If the amount is greater than $ 1000 and less than $ 2000 Manager approval is needed.
Please let me know how we can customize this..
thanks.

Hi,
I think you need to design a workflow to meet your requirements.
However, there are certain prerequisites which you need to follow for the same-
(a) You need to first map the org. structure in SAP (PPOMA)
(b) You need to assign a tolerance level against each clerk. You can use the standard tolerance level functionality for the purpose or desing a cusotmised one.
Now when you are marking an item for refund either thru FPE2\FPE2M, and press save, event 1120 is triggerred.
In thie event you can check whether the refund amount is more than the tolerance amount of the user or not. If not, then it exits.
However, if yes, it places a payment lock \clearing lock against the item and triggerres a workflow which initmates it's next level supervisior to action on the same.
If a clearing lock\payment lock is placed against the item , it will not be picked in the FPY1 run.The clearing lock will only get removed once it is approved by the supervisior, if it is under his\her tolerance limit, other wise it will be referred to the manager.
You can also built in custom rules in the workflow, so as to ensure that a particular item does not get stuck in one person's queue for a X no. of days.
Hope it helps...
Thanks,
Amlan

How to return full amount to customer?

The payment on security deposit has been released and applied to the customer's receivables. Unfortunately, the customer changed his mind and wants the full check refund.
Paid sec dep = 750
Partially returned - already cleared $175 from March 2008 bill (remaining 575)
Customer called and wants 750 in check refund instead of applying credits to bills
How do you return the full amount (750) to the customer?

Hello,
For the cleared item, reset the amount by using FP07.
Now all your SD amount should be ready for refund.
Ensure that the refund amount posted is 'On Account' payment....Now you can refund the amount....
Not sure about the refund process u'd follow @ u r prj...you can create repayment requests using FPTCRPO and then Refund run using FPY1.
Hope this helps
Rgds
Rajendra

Garnishment Refund - Credit Memo

Hello experts,
I have the following scenario of Garnishment refund -
An employee was garnished $54.75 which generated check number . Vendor returned the check as the Garishment was satisfied.A/P has voided this check and a refund has been created in SAP to issue refund to the employee on the Garnishment amount.
Now I have to create a credit memo for the refund amount and that record needs to be tied to the voided check by A/P to prevent the check from re-spooling.
Could anyone please let me know the steps of how to create a credit memo and tie it to the voided check in A/P?
Regards,
Malathi V

Thanks for your response . Your inputs helped me analyse the problem.
The employee was paid the refund through the Garnishment adjustment and it is showing as refund in the Garnishment history . But we do not do third party evaluation and posting on the refunds .
Hence the invoice on the AP side for the check returned by the vendor has to be offset manually .
First the returned check is voided which creates open line item in AP for the vendor .
Second the credit memo is created to offset the open AP line item .
Credit memo is created through tcode FB01 . Reverse posting entry is generated by linking it to the original accounting document .
My issue is resolved .
Regards,
Malathi V.

Customer Refund without VAT

Hi Friends,
we have a requirement, My Client want to refund Amount to Customer but with Out VAT.
For Example : Received : $1100 (1000+ 100 VA at 10%)
goods Delivered worth $600
Now we have to refund to customer $400.
But when ever i am trying to post $400 system automatically calculating VAT also which we don not want..
Can anybody help me on this..
Regards,
Satya

Friends Can anybody help me on this..
Edited by: Satyam on Mar 17, 2010 5:57 AM

HT201272 refund please

Hello, I am writing this email in order to get refund amount for motion x gps application . i have purchased this app to see hows the performance . I am sorry but did not like that app . please process my refund back to my credit card. Name : biren b shah country : canada. please contact me at 519 566 4990

You do not get a refund because you do not like it.
There are no refunds.
All sales are final

PO condition type for Refundable Container Deposit.

Dear all,
Container deposit is a refundable amount we pay to the shipping line,
along with the other relevant charges for imports of full container
shipments coming by sea.
In the present set-up the container deposit amount is getting added to the
"material price" at GRN.
Container deposit amount should go to the "GL account"
without it getting added to the "material price".
please advice how to do it.
regards
viru

Hi
thanks for replying.
We have created the Condition Type but still it is added to material cost.
Configuration below...
Condition Class - A
Calculation Type - B
Condition Category : B
header Condition - ticked
item Condition - ticked
delete - ticked
amount/percentage - ticked
value - ticked.
Group Condition - Ticked
Accruals - Ticked
vendor in GR - 2
and in pricing procedure Account key and Accrual key is maintained.
in OBYC G/L account is assigned.
regards
Viru

Garnishmet refund retroactive enteries error

Hai Sap Gurus,
My client needs to refund garnishment amount to an employee. The status on infotype is showing released .In order to enter the refund amount i had to change the status to reactivate for refund.However when i try to activate it gives me the error
Retroactive enteries are only possible after some date (10/05/2007).
When i double click it the perfomance assistant gives me this message
Retroactive entries are possible only after 10/05/2007
Message no. PG342
Diagnosis
You cannot change data for this infotype before 10/05/2007.
The 'Past entry all.' field (EPAST) of the Infotypes table (T582A) contains the entry 'I'. This means that checks for changes to past payroll data are infotype-specific.
System Response
The system therefore does not allow you to change this data.
I went to payroll status info type and checked the dates
Earlies RA date accounted to:09/29/2007
Earliest md change:10/01/2007
Master data change bonus:10/01/2007
I am not sure what exactly the problem is.
Please help me.
All replies are awarded with points.
thanks in advance

Alright guys,
I have been able to figure out why the error comes.Its really a simple mistake and it makes me feel stupid now.All you had to do was copy the garnishment document and then reactivate it for refund.I was trying to directly change it before copying so i was getting the error.
I would like to thank the guys who took their time to help with this.
Until next time
jason.

Prepayment amount is greater than invoice amount, what to do

Hi all
I am using GL, AP and CE. the problem is as follows:
I register a lot of prepayments for my employees. When i give a prepayment to one employee, he brings me back the invoice and than i register the invoice and then apply this prepayment to this invoice. But most of the cases the amount in the prepayment is bigger than the amount of the invoice. The employee is bringing me back the invoice and some money. Now what i should register on the system to reflect the money back. The system does not allow to apply prepayments on debit/credit memo. If i register a credit memo, the next time i register an invoice for a supplier which it has some value from the prepayment the system is suggesting this prepayment, but this is wrong because i have registered a document for this amount of money(which is credit memo).
Please advice because the customer is asking and i do not have any answer yet.
Thank you and Best Regards

What version of EBS are you on? My comments below apply to EBS 11.
As Vinip noted, you can have a distribution line that debits the cash account.
Another possibility would be to record a standard invoice for the entire amount, with the refund amount debited to some clearing account, and apply the prepayment to that invoice. Then in accounts receivable, record a miscellaneous cash receipt against the clearing account. Not a real good solution, as involves two different applications.
So I think the way to go is to appy a debit for the refund amount to your cash account when recording the invoice to apply the prepayment to. Makes sense?
If you want a simpler way, then submit an enhancement request to okay.
Perhaps for this company, it is common to give employees money in advance to buy something, but this is I think very rare for the corporate world at large. Usually the employee buys something and then submits an expense report to get reimbursed after the fact. Or the employees use a company credit card to make the purchase. Maybe your company needs to look at changing its current process? Just something to think about.
John Dickey

Unable to Apply Refund activity against Credit Memo

Hi ,
I have created a Credit memo for Rs.100 /- . I want to Apply this credit meme against Refund Activity through Front end.
Navigation is Transaction Screen -> Actions -> Application .
When i select Refund Activity in the Activity Screen and Tab out Applied amount is Defaulting as -100 Rs...When i am trying to save the record it is giving me the Error message "APP-AR-295224: Only positive refund amounts are allowed"...When i changed the Amount to +ve value ( 100 Rs.) and tried to save the record it is again giving different Error "APP-AR-295232: You cannot refund more than the credit memo amount".
Can anybody tell me what is the Problem . Why i am not able to Apply Refund Activity against "Credit Memo".
Thanks & Regards,
Surfraz Mitegar

check the transtion type for this credit memo, i think its Natural applicaiton is enabled (uncheck it)
Nitin

Withdraw refund from App Store

I Recently cancelled a subscription that came out from App Store and Apple ID. The refund is sitting in the account - how can I withdraw this back into my bank account?
many thanks

You can't transfer a balance from your iTunes account to your bank.
From See your iTunes credit balance - Apple Support :
You can't redeem or return iTunes Gift Cards, Gift Certificates, and unused store credit balances for cash except as required by law. If your jurisdiction allows for refund of redeemed gift balances, you can request a refund by contacting iTunes Store Support, selecting a support category and topic, and including the following information in your request detail:
Your Apple ID.
The store credit refund amount.
Your current shipping address.
Additional information might be requested for verification purposes.

I am changing phones from an iphone but i have still having money in my itunes.... What are my options for the blance in itunes??

Will i lose the money or will it just sit there in my itunes account???

From iTunes Gift balances :
You can't redeem or return iTunes Gift Cards, Gift Certificates, and unused store credit balances for cash except as required by law. If your jurisdiction allows for refund of redeemed gift balances, you can request a refund by contacting iTunes Store Support, selecting a support category and topic, and including the following information in your request detail:
Apple ID (this is your iTunes Store account name)
Store credit refund amount
Current shipping address
Additional information may be requested for verification purposes.
So you might be able to get it back

Issues in WSDL Import

Hi all,
I'm trying to import a WSDL file into XI and I get this error
Unable to convert imported document to WSDL
Reason: Tag definitions cannot have an attribute version from namespace urn:ebay:api:PayPalAPI
Check the selected category
Kindly provide inputs
Thanks
Geetha
My WSDL strcuture looks like this.
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions ns:version="2.4" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns="urn:ebay:api:PayPalAPI" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:cc="urn:ebay:apis:CoreComponentTypes" targetNamespace="urn:ebay:api:PayPalAPI">
<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ebay:api:PayPalAPI" elementFormDefault="qualified" attributeFormDefault="unqualified">
<import namespace="urn:ebay:apis:CoreComponentTypes" schemaLocation="CoreComponentTypes.xsd" />
<import namespace="urn:ebay:apis:eBLBaseComponents" schemaLocation="eBLBaseComponents.xsd" />

<xs:element name="RequesterCredentials" type="ebl:CustomSecurityHeaderType" />

<xs:element name="RefundTransactionRequest" type="ns:RefundTransactionRequestType" />
<xs:element name="RefundTransactionResponse" type="ns:RefundTransactionResponseType" />
<xs:element name="RefundTransactionReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:RefundTransactionRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="RefundTransactionRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="TransactionID" type="ebl:TransactionId">
<annotation>
<documentation>
Unique identifier of the transaction you are refunding.
 
 
Required
 
 
Character length and limitations: 17 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
<xs:element name="RefundType" type="ebl:RefundType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Type of refund you are making
 
 
Required
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Refund amount.
 
 
Amount is
required
if RefundType is Partial.
 
 
NOTE: If RefundType is Full, do not set Amount.
</documentation>
</annotation>
</xs:element>
<xs:element name="Memo" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Custom memo about the refund.
 
 
Optional
 
 
Character length and limitations: 255 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="RefundTransactionResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<sequence>
<element name="RefundTransactionID" type="ebl:TransactionId" minOccurs="0" maxOccurs="1" nillable="true">
<annotation>
<documentation>
Unique transaction ID of the refund.
 
 
Character length and limitations:17 single-byte characters
</documentation>
</annotation>
</element>
<element name="NetRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>Amount subtracted from PayPal balance of original recipient of payment to make this refund</documentation>
</annotation>
</element>
<element name="FeeRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>Transaction fee refunded to original recipient of payment</documentation>
</annotation>
</element>
<element name="GrossRefundAmount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>Amount of money refunded to original payer</documentation>
</annotation>
</element>
</sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="GetTransactionDetailsRequest" type="ns:GetTransactionDetailsRequestType" />
<xs:element name="GetTransactionDetailsResponse" type="ns:GetTransactionDetailsResponseType" />
<xs:element name="GetTransactionDetailsReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:GetTransactionDetailsRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="GetTransactionDetailsRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="TransactionID" type="ebl:TransactionId">
<annotation>
<documentation>
Unique identifier of a transaction.
 
 
Required
 
 
The details for some kinds of transactions cannot be retrieved with GetTransactionDetailsRequest. You cannot obtain details of bank transfer withdrawals, for example.
 
 
Character length and limitations: 17 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="GetTransactionDetailsResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:PaymentTransactionDetails" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="BillUserRequest" type="ns:BillUserRequestType" />
<xs:element name="BillUserResponse" type="ns:BillUserResponseType" />
<xs:element name="BillUserReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:BillUserRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="BillUserRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element ref="ebl:MerchantPullPaymentDetails" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="BillUserResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:BillUserResponseDetails" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="TransactionSearchRequest" type="ns:TransactionSearchRequestType" />
<xs:element name="TransactionSearchResponse" type="ns:TransactionSearchResponseType" />
<xs:element name="TransactionSearchReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:TransactionSearchRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="TransactionSearchRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="StartDate" type="xs:dateTime" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The earliest transaction date at which to start the search. No wildcards are allowed.
 
 
Required
</documentation>
</annotation>
</xs:element>
<xs:element name="EndDate" type="xs:dateTime" minOccurs="0">
<annotation>
<documentation>
The latest transaction date to be included in the search
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="Payer" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the buyers email address
 
 
Optional
 
 
Character length and limitations: 127 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
<xs:element name="Receiver" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the receivers email address. If the merchant account has only one email, this is the primary email. Can also be a non-primary email.
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="ReceiptID" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the PayPal Account Optional receipt ID
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="TransactionID" type="ebl:TransactionId" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the transaction ID.
 
 
Optional
 
 
The returned results are from the merchants transaction records.
 
 
Character length and limitations: 19 single-byte characters maximum
</documentation>
</annotation>
</xs:element>
<xs:element name="PayerName" type="ebl:PersonNameType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by the buyers name
 
 
Optional
 
 
Salutation: 20 single-byte character limit.
 
 
FirstName: 25 single-byte character limit.
 
 
MiddleName: 25 single-byte character limit.
 
 
LastName: 25 single-byte character limit.
 
 
Suffix: 12 single-byte character limit.
</documentation>
</annotation>
</xs:element>
<xs:element name="AuctionItemNumber" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by item number of the purchased goods.
 
 
Optional
 
 
To search for purchased items not related to auctions, set the AuctionItemNumber element to the value of the HTML item_number variable set in the shopping cart for the original transaction.
</documentation>
</annotation>
</xs:element>
<xs:element name="InvoiceID" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by invoice identification key, as set by you for the original transaction. InvoiceID searches the invoice records for items sold by the merchant, not the items purchased.
 
 
Optional
 
 
The value for InvoiceID must exactly match an invoice identification number. No wildcards are allowed.
 
 
Character length and limitations: 127 single-byte characters maximum
</documentation>
</annotation>
</xs:element>
<xs:element name="CardNumber" type="xs:string" minOccurs="0" maxOccurs="1" />
<xs:element name="TransactionClass" type="ebl:PaymentTransactionClassCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by classification of transaction. Some kinds of possible classes of transactions are not searchable with TransactionSearchRequest. You cannot search for bank transfer withdrawals, for example.
 
 
Optional
 
 
All: all transaction classifications.
 
 
Sent: only payments sent.
 
 
Received: only payments received.
 
 
MassPay: only mass payments.
 
 
MoneyRequest: only money requests.
 
 
FundsAdded: only funds added to balance.
 
 
FundsWithdrawn: only funds withdrawn from balance.
 
 
Referral: only transactions involving referrals.
 
 
Fee: only transactions involving fees.
 
 
Subscription: only transactions involving subscriptions.
 
 
Dividend: only transactions involving dividends.
 
 
Billpay: only transactions involving BillPay Transactions.
 
 
Refund: only transactions involving funds.
 
 
CurrencyConversions: only transactions involving currency conversions.
 
 
BalanceTransfer: only transactions involving balance transfers.
 
 
Reversal: only transactions involving BillPay reversals.
 
 
Shipping: only transactions involving UPS shipping fees.
 
 
BalanceAffecting: only transactions that affect the account balance.
 
 
ECheck: only transactions involving eCheck
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by transaction amount
 
 
Optional
 
 
You must set the currencyID attribute to one of the three-character currency codes for any of the supported PayPal currencies.
</documentation>
</annotation>
</xs:element>
<xs:element name="CurrencyCode" type="ebl:CurrencyCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by currency code
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="Status" type="ebl:PaymentTransactionStatusCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Search by transaction status
 
 
Optional
 
 
Pending: The payment is pending. The specific reason the payment is pending is returned by the GetTransactionDetails APIPendingReason element. For more information, see PendingReason.
 
 
Processing: The payment is being processed.
 
 
Success: The payment has been completed and the funds have been added successfully to your account balance.
 
 
Denied: You denied the payment. This happens only if the payment was previously pending.
 
 
Reversed: A payment was reversed due to a chargeback or other type of reversal. The funds have been removed from your account balance and returned to the buyer.
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="TransactionSearchResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:PaymentTransactions" minOccurs="0" maxOccurs="unbounded">
<annotation>
<documentation>Results of a Transaction Search.</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="MassPayRequest" type="ns:MassPayRequestType" />
<xs:element name="MassPayResponse" type="ns:MassPayResponseType" />
<xs:element name="MassPayReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:MassPayRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="MassPayRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="EmailSubject" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Subject line of the email sent to all recipients. This subject is not contained in the input file; you must create it with your application.
 
 
Optional
 
 
Character length and limitations: 255 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
<xs:element name="ReceiverType" type="ebl:ReceiverInfoCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Indicates how you identify the recipients of payments in all MassPayItems: either by EmailAddress (ReceiverEmail in MassPayItem), PhoneNumber (ReceiverPhone in MassPayItem), or by UserID (ReceiverID in MassPayItem).
 
 
Required.
You must specify one or the other of EmailAddress or UserID.
</documentation>
</annotation>
</xs:element>
<xs:element name="MassPayItem" type="ns:MassPayRequestItemType" minOccurs="1" maxOccurs="250">
<annotation>
<documentation>
Details of each payment. A single MassPayRequest can include up to 250 MassPayItems.
 
 
Required
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="MassPayResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType" />
</xs:complexContent>
</xs:complexType>
<xs:complexType name="MassPayRequestItemType">
<xs:annotation>
<xs:documentation>MassPayRequestItemType</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element name="ReceiverEmail" type="ebl:EmailAddressType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Email address of recipient.
 
 
Required
 
 
You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
 
 
Character length and limitations: 127 single-byte characters maximum.
</documentation>
</annotation>
</xs:element>
<xs:element name="ReceiverPhone" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Phone number of recipient.
 
 
Required
 
 
You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
 
 
</documentation>
</annotation>
</xs:element>
<xs:element name="ReceiverID" type="ebl:UserIDType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Unique PayPal customer account number. This value corresponds to the value of PayerID returned by GetTransactionDetails.
 
 
Required
 
 
You must specify ReceiverEmail, ReceiverPhone, or ReceiverID, but all MassPayItems in a request must use the same field to specify recipients.
 
 
Character length and limitations: 17 single-byte characters maximum.
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Payment amount. You must set the currencyID attribute to one of the three-character currency codes for any of the supported PayPal currencies.
 
 
Required
 
 
You cannot mix currencies in a single MassPayRequest. A single request must include items that are of the same currency.
</documentation>
</annotation>
</xs:element>
<xs:element name="UniqueId" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Transaction-specific identification number for tracking in an accounting system.
 
 
Optional
 
 
Character length and limitations: 30 single-byte characters. No whitespace allowed.
</documentation>
</annotation>
</xs:element>
<xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Custom note for each recipient.
 
 
Optional
 
 
Character length and limitations: 4,000 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:element name="BAUpdateRequest" type="ns:BAUpdateRequestType" />
<xs:element name="BAUpdateResponse" type="ns:BAUpdateResponseType" />
<xs:element name="BillAgreementUpdateReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:BAUpdateRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="BAUpdateRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="MpID" type="ebl:MerchantPullIDType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Preapproved Payments billing agreement identification number. Corresponds to the FORM variable mp_id.
 
 
Required
 
 
Character limit: 19 single-byte alphanumeric characters. The format of a billing agreement identification number is the single-character prefix B, followed by a hyphen and an alphanumeric character string:
 
 
B-unique_alphanumeric_string
</documentation>
</annotation>
</xs:element>
<xs:element name="Custom" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Custom annotation field for your exclusive use
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="Desc" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Description of goods or services associated with the billing agreement
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="MpStatus" type="ebl:MerchantPullStatusCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
The current status of the billing agreement
 
 
Optional
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="BAUpdateResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:BAUpdateResponseDetails" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="AddressVerifyRequest" type="ns:AddressVerifyRequestType" />
<xs:element name="AddressVerifyResponse" type="ns:AddressVerifyResponseType" />
<xs:element name="AddressVerifyReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:AddressVerifyRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="AddressVerifyRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="Email" type="ebl:EmailAddressType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Email address of buyer to be verified.
 
 
Required
 
 
Maximum string length: 255 single-byte characters Input mask: ?@?.??
</documentation>
</annotation>
</xs:element>
<xs:element name="Street" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
First line of buyers billing or shipping street address to be verified.
 
 
Required
 
 
For verification, input value of street address must match the first three single-byte characters of the street address on file for the PayPal account.
 
 
Maximum string length: 35 single-byte characters Alphanumeric plus Whitespace and case of input value are ignored.
</documentation>
</annotation>
</xs:element>
<xs:element name="Zip" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Postal code to be verified.
 
 
Required
 
 
For verification input value of postal code must match the first five single-byte characters of the postal code on file for the PayPal account.
 
 
Maximum string length: 16 single-byte characters Whitespace and case of input value are ignored.
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="AddressVerifyResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="ConfirmationCode" type="ebl:AddressStatusCodeType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Confirmation of a match with one of the following tokens:
 
 
None: The input value of the Email object does not match any email address on file at PayPal.
 
 
Confirmed: If the value of the StreetMatch object is Matched PayPal responds that the entire postal address is confirmed.
 
 
Unconfirmed: PayPal responds that the postal address is unconfirmed
</documentation>
</annotation>
</xs:element>
<xs:element name="StreetMatch" type="ebl:MatchStatusCodeType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
PayPal has compared the postal address you want to verify with the postal address on file at PayPal.
 
 
None: The input value of the Email object does not match any email address on file at PayPal. In addition an error response is returned. No further comparison of other input values has been made.
 
 
Matched: The street address matches the street address on file at PayPal.
 
 
Unmatched: The street address does not match the street address on file at PayPal.
</documentation>
</annotation>
</xs:element>
<xs:element name="ZipMatch" type="ebl:MatchStatusCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
PayPal has compared the zip code you want to verify with the zip code on file for the email address.
 
 
None: The street address was unmatched. No further comparison of other input values has been made.
 
 
Matched: The zip code matches the zip code on file at PayPal.
 
 
Unmatched: The zip code does not match the zip code on file at PayPal.
</documentation>
</annotation>
</xs:element>
<xs:element name="CountryCode" type="ebl:CountryCodeType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>Two-character country code (ISO 3166) on file for the PayPal email address.</documentation>
</annotation>
</xs:element>
<xs:element name="PayPalToken" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
The token prevents a buyer from using any street address other than the address on file at PayPal during additional purchases he might make from the merchant. It contains encrypted information about the users street address and email address. You can pass the value of the token with the Buy Now button HTML address_api_token variable so that PayPal prevents the buyer from using any street address or email address other than those verified by PayPal. The token is valid for 24 hours.
 
Character length and limitations: 94 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="EnterBoardingRequest" type="ns:EnterBoardingRequestType" />
<xs:element name="EnterBoardingResponse" type="ns:EnterBoardingResponseType" />
<xs:element name="EnterBoardingReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:EnterBoardingRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="EnterBoardingRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element ref="ebl:EnterBoardingRequestDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="EnterBoardingResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
A unique token that identifies this boarding session. Use this token with the GetBoarding Details API call.
 
 
Character length and limitations: 64 alphanumeric characters. The token has the following format:
 
 
OB-61characterString
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="GetBoardingDetailsRequest" type="ns:GetBoardingDetailsRequestType" />
<xs:element name="GetBoardingDetailsResponse" type="ns:GetBoardingDetailsResponseType" />
<xs:element name="GetBoardingDetailsReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:GetBoardingDetailsRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="GetBoardingDetailsRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
A unique token returned by the EnterBoarding API call that identifies this boarding session.
 
 
Required
 
 
Character length and limitations: 64 alphanumeric characters. The token has the following format:
 
 
OB-61characterString
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="GetBoardingDetailsResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:GetBoardingDetailsResponseDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="SetExpressCheckoutRequest" type="ns:SetExpressCheckoutRequestType" />
<xs:element name="SetExpressCheckoutResponse" type="ns:SetExpressCheckoutResponseType" />
<xs:element name="SetExpressCheckoutReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:SetExpressCheckoutRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="SetExpressCheckoutRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element ref="ebl:SetExpressCheckoutRequestDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="SetExpressCheckoutResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
A timestamped token by which you identify to PayPal that you are processing this payment with Express Checkout. The token expires after three hours. If you set Token in the SetExpressCheckoutRequest, the value of Token in the response is identical to the value in the request.
 
 
Character length and limitations: 20 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="GetExpressCheckoutDetailsRequest" type="ns:GetExpressCheckoutDetailsRequestType" />
<xs:element name="GetExpressCheckoutDetailsResponse" type="ns:GetExpressCheckoutDetailsResponseType" />
<xs:element name="GetExpressCheckoutDetailsReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:GetExpressCheckoutDetailsRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="GetExpressCheckoutDetailsRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="Token" type="ebl:ExpressCheckoutTokenType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
A timestamped token, the value of which was returned by SetExpressCheckoutResponse.
 
 
Required
 
 
Character length and limitations: 20 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="GetExpressCheckoutDetailsResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:GetExpressCheckoutDetailsResponseDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoExpressCheckoutPaymentRequest" type="ns:DoExpressCheckoutPaymentRequestType" />
<xs:element name="DoExpressCheckoutPaymentResponse" type="ns:DoExpressCheckoutPaymentResponseType" />
<xs:element name="DoExpressCheckoutPaymentReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoExpressCheckoutPaymentRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoExpressCheckoutPaymentRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element ref="ebl:DoExpressCheckoutPaymentRequestDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="DoExpressCheckoutPaymentResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:DoExpressCheckoutPaymentResponseDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoDirectPaymentRequest" type="ns:DoDirectPaymentRequestType" />
<xs:element name="DoDirectPaymentResponse" type="ns:DoDirectPaymentResponseType" />
<xs:element name="DoDirectPaymentReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoDirectPaymentRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoDirectPaymentRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element ref="ebl:DoDirectPaymentRequestDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="DoDirectPaymentResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>The amount of the payment as specified by you on DoDirectPaymentRequest.</documentation>
</annotation>
</xs:element>
<xs:element name="AVSCode" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Address Verification System response code. Character limit: One single-byte alphanumeric character
<table>
<tr>
<th>AVS Code</th>
<th>Meaning</th>
<th>Matched Details</th>
</tr>
<tr>
<td>A</td>
<td>Address</td>
<td>Address only (no ZIP)</td>
</tr>
<tr>
<td>B</td>
<td>International A</td>
<td>Address only (no ZIP)</td>
</tr>
<tr>
<td>C</td>
<td>International N</td>
<td>None</td>
</tr>
<tr>
<td>D</td>
<td>International X</td>
<td>Address and Postal Code</td>
</tr>
<tr>
<td>E</td>
<td>Not allowed for MOTO (Internet/Phone) transactions</td>
<td>Not applicable</td>
</tr>
<tr>
<td>F</td>
<td>UK-specific X</td>
<td>Address and Postal Code</td>
</tr>
<tr>
<td>G</td>
<td>Global Unavailable</td>
<td>Not applicable</td>
</tr>
<tr>
<td>I</td>
<td>International Unavailable</td>
<td>Not applicable</td>
</tr>
<tr>
<td>N</td>
<td>No</td>
<td>None</td>
</tr>
<tr>
<td>P</td>
<td>Postal (International Z)</td>
<td>Postal Code only (no Address)</td>
</tr>
<tr>
<td>R</td>
<td>Retry</td>
<td>Not applicable</td>
</tr>
<tr>
<td>S</td>
<td>Service not Supported</td>
<td>Not applicable</td>
</tr>
<tr>
<td>U</td>
<td>Unavailable</td>
<td>Not applicable</td>
</tr>
<tr>
<td>W</td>
<td>Whole ZIP</td>
<td>Nine-digit ZIP code (no Address)</td>
</tr>
<tr>
<td>X</td>
<td>Exact match</td>
<td>Address and nine-digit ZIP code</td>
</tr>
<tr>
<td>Y</td>
<td>Yes</td>
<td>Address and five-digit ZIP</td>
</tr>
<tr>
<td>Z</td>
<td>ZIP</td>
<td>Five-digit ZIP code (no Address)</td>
</tr>
<tr>
<td>All others</td>
<td>Error Not applicable</td>
<td />
</tr>
</table>
</documentation>
</annotation>
</xs:element>
<xs:element name="CVV2Code" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Result of the CVV2 check by PayPal.
<table>
<tr>
<th>CVV2 Code</th>
<th>Meaning</th>
<th>Matched Details</th>
</tr>
<tr>
<td>M</td>
<td>Match</td>
<td>CVV2</td>
</tr>
<tr>
<td>N</td>
<td>No match</td>
<td>None</td>
</tr>
<tr>
<td>P</td>
<td>Not Processed</td>
<td>Not applicable</td>
</tr>
<tr>
<td>S</td>
<td>Service not Supported</td>
<td>Not applicable</td>
</tr>
<tr>
<td>U</td>
<td>Unavailable</td>
<td>Not applicable</td>
</tr>
<tr>
<td>X</td>
<td>No response</td>
<td>Not applicable</td>
</tr>
<tr>
<td>All others</td>
<td>Error</td>
<td>Not applicable</td>
</tr>
</table>
</documentation>
</annotation>
</xs:element>
<xs:element name="TransactionID" type="ebl:TransactionId" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Transaction identification number.
 
 
Character length and limitations: 19 characters maximum.
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoCaptureRequest" type="ns:DoCaptureRequestType" />
<xs:element name="DoCaptureResponse" type="ns:DoCaptureResponseType" />
<xs:element name="DoCaptureReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoCaptureRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoCaptureRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="AuthorizationID" type="ebl:AuthorizationId" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The authorization identification number of the payment you want to capture.
 
 
Required
 
 
Character length and limits: 19 single-byte characters maximum
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Amount to authorize. You must set the currencyID attribute to USD.
 
 
Required
 
 
Limitations: Must not exceed $10,000 USD in any currency. No currency symbol. Decimal separator must be a period (.), and the thousands separator must be a comma (,)
</documentation>
</annotation>
</xs:element>
<xs:element name="CompleteType" type="ebl:CompleteCodeType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Indicates if this capture is the last capture you intend to make. The default is Complete. If CompleteType is Complete, any remaining amount of the original reauthorized transaction is automatically voided.
 
 
Required
 
 
Character length and limits: 12 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
<xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
An informational note about this settlement that is displayed to the payer in email and in transaction history.
 
 
Optional
 
 
Character length and limits: 255 single-byte characters
</documentation>
</annotation>
</xs:element>
<xs:element name="InvoiceID" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Your invoice number or other identification number.
 
 
The InvoiceID value is recorded only if the authorization you are capturing is an order authorization, not a basic authorization.
 
 
Optional
 
 
Character length and limits: 127 single-byte alphanumeric characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="DoCaptureResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element ref="ebl:DoCaptureResponseDetails" minOccurs="1" maxOccurs="1" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoReauthorizationRequest" type="ns:DoReauthorizationRequestType" />
<xs:element name="DoReauthorizationResponse" type="ns:DoReauthorizationResponseType" />
<xs:element name="DoReauthorizationReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoReauthorizationRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoReauthorizationRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The value of a previously authorized transaction identification number returned by a PayPal product. You can obtain a buyers transaction number from the TransactionID element of the PayerInfo structure returned by GetTransactionDetailsResponse.
 
 
Required
 
 
Character length and limits: 19 single-byte characters maximum
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Amount to reauthorize.
 
 
Required
 
 
Limitations: Must not exceed $10,000 USD in any currency. No currency symbol. Decimal separator must be a period (.), and the thousands separator must be a comma (,).
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="DoReauthorizationResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
A new authorization identification number.
 
 
Character length and limits: 19 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoVoidRequest" type="ns:DoVoidRequestType" />
<xs:element name="DoVoidResponse" type="ns:DoVoidResponseType" />
<xs:element name="DoVoidReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoVoidRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoVoidRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The value of the original authorization identification number returned by a PayPal product.
 
 
If you are voiding a transaction that has been reauthorized, use the ID from the original authorization, and not the reauthorization.
 
 
Required
 
 
Character length and limits: 19 single-byte characters
</documentation>
</annotation>
</xs:element>
<xs:element name="Note" type="xs:string" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
An informational note about this settlement that is displayed to the payer in email and in transaction history.
 
 
Optional
 
 
Character length and limits: 255 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="DoVoidResponseType">
<xs:complexContent>
<xs:extension base="ebl:AbstractResponseType">
<xs:sequence>
<xs:element name="AuthorizationID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The authorization identification number you specified in the request.
 
 
Character length and limits: 19 single-byte characters
</documentation>
</annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="DoAuthorizationRequest" type="ns:DoAuthorizationRequestType" />
<xs:element name="DoAuthorizationResponse" type="ns:DoAuthorizationResponseType" />
<xs:element name="DoAuthorizationReq">
<xs:complexType>
<xs:sequence>
<xs:element ref="ns:DoAuthorizationRequest" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DoAuthorizationRequestType">
<xs:complexContent>
<xs:extension base="ebl:AbstractRequestType">
<xs:sequence>
<xs:element name="TransactionID" type="xs:string" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
The value of the orders transaction identification number returned by a PayPal product.
 
 
Required
 
 
Character length and limits: 19 single-byte characters maximum
</documentation>
</annotation>
</xs:element>
<xs:element name="TransactionEntity" type="ebl:TransactionEntityType" minOccurs="0" maxOccurs="1">
<annotation>
<documentation>
Type of transaction to authorize. The only allowable value is
Order
which means that the transaction represents a customer order that can be fulfilled over 29 days.
 
 
Optional
</documentation>
</annotation>
</xs:element>
<xs:element name="Amount" type="cc:BasicAmountType" minOccurs="1" maxOccurs="1">
<annotation>
<documentation>
Amount to authorize.
&l

can you remove this from WSDL <wsdl:definitions> tag.
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:ebl="urn:ebay:apis:eBLBaseComponents" xmlns:cc="urn:ebay:apis:CoreComponentTypes"
and add name="yourmessage interface" in <wsdl:definitions> tag.

How to clear Prepayment account in the subledger

A prepayment amount of 1000 was paid to a supplier for the last month of the service contract using the profoma invioce. When the invoice for the last month was received it was 800. Now we have over paid the supplier by 200. when the refund is received, how do I clear the subledger with the difference?
Please assist

This is what I found in Oracle documentation-
To record a prepayment refund:
1.     In the Invoices window, enter an invoice in the amount of the refund from the supplier. Enter Standard for the type. Enter a description on the invoice to indicate that you are retiring a prepayment. Create an invoice distribution for the amount of the refund and debit your Cash account or an accounts receivable account. Credit the accounts payable liability account as always.
Approve the invoice.
2.     Choose the Actions button to navigate to the Invoice Actions window. Select the Apply/Unapply Prepayment check box and choose OK.
Select the prepayment to which you want to apply the refund. Enter the refund amount in the Amount To Apply field. Optionally change the GL Date, which is the accounting date for the reversing prepayment distributions that Payables creates when you apply a prepayment. If you want to see more information on a prepayment, select it and choose the Invoice Overview button.
If you want to approve the new prepayment distributions that the application will create and the Allow Online Approval Payables option is enabled, select Approve. If the Allow Online Approval Payables option is not enabled, you can submit Payables Approval from the Submit Request window.
If you want to print a Prepayment Remittance Advice for the supplier, select Print.
3.     Choose the Apply/Unapply button to apply the prepayment amount to the invoice you entered for the refund and to save your work.
This fully retires the prepayment and reduces the amount remaining on the invoice to 0. Payables automatically enters a reversing distribution on the prepayment to credit the prepayment account. This credit balances the debit you entered on the invoice (Step 1) to the Cash account.

REFUND AMOUNT

Similar Messages

Maybe you are looking for