Difference postings in customer manual payment

Hi
Has anyone used this option?.. In case of manual payment of customer say from F-28, after choosing open line item if there is a difference in amount from the open line items selected, this can be nullified by offseting the difference amount in a small tab in right hand bottom of the screen "difference posting".
It is not residual payment, partial payment or cash discounts.
The posting that results from this, clears the open line items and creates a new open line item for the difference amount like residual payment but unlike it the new open line item contains the baseline date as document date of the payment not the original invoice.
This is making incorrect interest calculations in such cases. Is there any setting to make these new open items to select baseline date as the date of original invoice.
Let me know..
Regards
Priyadarshini

Hi,
Why don't you edit the baseline date before posting ? Or else you may have to take help of substitution/validation.
Regards
Partha

Similar Messages

  • ZLSCH in customer manual payment

    Good morning,
    As you can see from my picture , i have an invoice with payment condition  equal to "C" ...
    Why in the payment transaction I cannot see the same payment condition?
    See the row where I put the label "payment"...
    I would like to use FBl5N to see all the residual item (invoice - minus payment) filtered by payment condition... In this situation, how should I do?

    Hi Silvana,
    Which transaction do you use for the "manual payment"? Is it F-28 or a similar one?
    If so, then - in my view - the only way to copy the payment method (ZLSCH) from the invoice to the payment (clearing document) is, to include this field in a definition of a clearing rule. It is done like this:
    1. Define a clearing rule
    SPRO: Financial accounting - General ledger accounting - Business transactions - Open item clearing
    - Define clearing rules (view V_TFAG)
    Task: Create a clearing rule with a 2-char code and a meaningful description (e.g., Customer clearing rule). Include Payment method (ZLSCH) field in it.
    2. Assign this clearing rule
    SPRO: Financial accounting - General ledger accounting - Business transactions - Open item clearing
    - Assign clearing rules to account types (view V_TFAGM)
    Task: For account type D (customers), assign the 2-char code of the clearing rule which you created above.
    What it will do:
    Whenever you clear items on a customer, it will always balance the selected field (in this case, ZLSCH) to zero. It means that if the customer invoice has a payment method "C" as in your example, then during a payment clearing, it will get copied into the clearing item (payment document).
    If you first book the payment on account (without clearing), then it will be blank - and once you do the clearing later, the clearing document will have at least two entries: one with "C" and one with "blank", to set both to zero.
    Is it something you want to have?
    Note that this rule is always universal - i.e., it will work for all customers (you cannot make exceptions in the standard system).
    If you use trans. F110 for payments then the payment method is filled automatically on the payment item (even if it is blank on the invoice). Then you should not set this clearing rule. But given your example, this is probably not your case.
    Did this answer your question? Let me (us) know if you have any further question.

  • Customer Difference postings

    Hi all,
             Can anyone tell me how to do the difference postings in AR. The tolerence limits are set to $5.But when I tried to post the overpay/underpayment for a customer,its asking me to create a new line item and assign it to a GL account.To what GL account should I assign that new line item, because overpay/underpay accounts are already defined in OBXL.I am confused ..please anyone help me out with the whole process...will assign points for the right answer.
    Thanks
    Meghna
    Edited by: meghna on Jan 19, 2008 7:28 PM

    please ...i need detail explanation on how u post the difference postings using the tcode f-28.i tried to post the differences but its either creating a new line item or i cannot post.My question is how can I post to the difference accounts automatically and when do I use the reason codes during posting payments in f-28...please anyone help me...its very urgent for me....
    Thanks ,
    Meghna

  • Customer residual payment  in F-28 urgent

    Hi,
    I am trying to create residual payment for customer in F-28. But when I post the payment of 50 $ against invoice of 300$ it is creating a invoice of 350$. So it is not reducing it & making it 250 for new residual invoice but creating a residual invoice for 350 $ . Tell me why its not creating a new residual invoice for
    250.
    please help..its urgent.
    Thanks
    Nik
    Edited by: Nik Wallace on Jun 18, 2008 7:49 PM

    generally what i do to post residual payment is goto F-28 enter the amount i want to post i.e in this case $50. fill all the fields like ref, bank acc#, customer acc# etc.
    next click on process open items and then click on 'residual items' tab.
    next double click on invoice you want to pay against so that it alone appears in blue and rest all other appears in black.
    once you select the invoice you want to pay against, double click on the blank residual field. The field automatically gets filled with $50 you entered earlier and the difference postings become 0.
    award pts if it is helpful
    thanks
    Edited by: prince light on Jun 18, 2008 9:17 PM

  • Due date payment restriction during manual payment posting

    Hi Team.
    We have a requirement to pay bills only after the due date is over,and not before that.
    For Ex :- If i have payment terms of 30 days and i am booking invoice on 1st of mar then due date would be 31st of mar.
    our requirement is to pay this bill only on or after this 31st march.user should not allowed to post any payment entry before 31st march.
    Can some one please give the settings required for achieving this requirement during manual payment entry..
    appreciate your help..
    Thanks
    Vinai

    Hi Vinai,
    Sorry for giving confusion..It is as simple as below.
    1). Manual payment should happen only after  the invoice is due....and that too for only one vendor.rest of all vendors should be able to pay as usual before due dates. so we are creating one new payment term for particular vendor and trying to restrict the payment by creating validation.
    2). And this restriction should also apply when vendor is configured as customer.
    For Ex :- If vendor invoice value is 10,000 where i need to pay, and he is also a customer and has sale value 1000 which i need to receive.
    net balance is 9000.
    during this vendor & customer clearance also the due date calculation should work.
    Please help in building validation logic or any BADI , EXIT' s at lease for first one..
    Thanks
    Vinai

  • Manual payments process

    Hello Experts,
    We're creating a new local solution (web based)  in order to manage "Manual Payments", so, we need to integrate it with our Sap. For this integration we detected 4Outbound Master data interface (from Sap vs Web solution), 1 extraction program for Bank, and 1 inbound interface with releated batch input creation.
    Inbound Interface:
    Manual Payment accounting  (Inbound interface)
    An interface is required in order to upload in Sap a file containing manual payment requests.
    The program should read an input txt file containing for every manual payment a header row information and two or more rows with detailed item information.
    The manual payment document will be created according the document type and transaction type inserted in the header.
    Two different transaction types are required:
    FB01   Post Document
    F-48   Post Vendor Down Payment  
    The interface should be scheduled to capture every new input file inserted on a local FTP server.
    In detail the program must perform the following activities:
    1) Read a test input file
    2) reate  batch input session to post Manual Payment document for every manual payment request (header record ) according transaction code header field (F-48 or FB01)
    3) Maintain request history (custom table)
    Outbound Interfaces
    Vendor master data, Cost Centre master data, Internal Order master data, wbs element master data.
    In detail the program must perform the following activities:
    1) Select  Vendor/CC/IO/WBS element Master Data according defined criteria
    2) Create  output file.txt 
    Extraction Programme
    Payment Medium for Bank (Outbound interface)
    An interface is required in order to create Payment information  to the bank via Home Banking .
    A similar solution is in charge for Automatic payment , see pgm   ZITFU_RFFOIT_B (FA_DD_451_LIT).
    In detail the program must perform the following activities:
    1) Read accounting document for manual payment according selection criteria  
    2) Create DME file
    3) Create Letter for Bank and vendor 
    4) Create Summury list 
    5) Create return file with Protocol Number vs WEB to confirm payment
    Please suggest how to achieve this..
    your inputs will be rewarded..
    Thanks in advance,
    Satya

    Hi,
    This is not question to give answer, this is requirement for inbound and outbound interfaces
    Mainly you have to concentrate on interfaces is
    Inbound
    What are the selection screen parameter (like company code etc whether it is select option or parameter and is it required or optional) and you need to check with customer that any validation required on selection screen
    You need to sit with an abaper to write BDC to update SAP data (you need to decide which fields are required in BDC recording)
    You need to decide the input file format (colums, rows, Char or numc and their length)
    You need to map input file fields into sap fields
    Outbound
    What are the selection screen parameter (like company code etc whether it is select option or parameter and is it required or optional) and you need to check with customer that any validation required on selection screen
    You neeed to decide the output file format (colums, rows, Char or numc and their length) and you need to decide from which sap fields data should be pick
    Where the output file shold palce
    Moreover you need to sit with sr abaper to design the document Flow (FDD)
    Reg
    Vishnu

  • Clearing Customer down payment for down payment amount not equal to Customer Invoice amount

    Dear All,
                   Below process are posting Customer transaction directly via FI without SD cycle.
                Customer down payment = 102 INR
                Customer Invoice = 103 INR
    While doing Customer clearing w.r.t Invoice system has cleared the down payment document but posted an open item in Customer account with clearing document number  of value Rs 102  .
    Concern:-
                   1) How 1 INR difference will be countered , via receipt payment from customer from bank account ?
                   2) In case we have defined tolerance limit of 5% for Customer and this come to be > 1 INR ,does SAP provide clearing Customer items
                       automatically via any Standard Customer clearing process based on rule defined  ?
    Pls suggest
    Regards
    MJ

    Hi,
    the information of the exchange rates used for down payments, is
    stored in table TCURR ( exchange rates)
    For the request down payment the actual exchange rate of table TCURR
    or the rate of document header is taken.
    When this down payment request is payed, also the exchange rate of
    the actual day (TCURR) is taken.
    That´s why the amount in the bank posting in local currency result
    from translating the foreign currency amount at the current rate,
    instead of resulting from the total of the local currency amounts
    from the settled items.
    Regards,
    Attila

  • F110-Customer incoming payment

    hi,
    i have a strange scenario while running F110. i am clearing the outstanding customer invoice using the same.
    the payment term is '5% discount in first 15 days, item due in 30 days'.
    But when i create the proposal , it assigns cash discount to the line item even if the due date has passed ( i created an invoice with baseline date 01.01.2010, and run date 13.09.2010,even then the system deduce the cash discount)
    Kindly help me out.
    NB:in FBZP 'All company codes' the entry for 'Outgoing pmnt with cash disc.from' is NIL and the 'Max.cash discount' is unchecked.
    Thnks,
    ficoguy.

    Dear ficoguy,
    If I well understood Your question,  the situation You're reporting
    is not a system error but its normal functioning.                                                                               
    In the coding for the automatic payment program, if the document                    
    is a Customer Invoice, the first condition of the payment term will                 
    always be selected.  The reason for this design is that the customer                
    has already agreed for the payment to be taken on a specific day at a               
    specific rate.  He should not be penalized if the automatic entry is                
    not created on that day.                                                            
    For a manual payment, it makes sense to penalize the customer if they               
    pay late, but not for an automated payment.                                                                               
    The customer has no influence over the time of payment. Therefore, one              
    may not be able to hold the customer responsible, if collections are too            
    late for the time period set for the highest cash discount terms.  There            
    is no legal or business reason for raising the payment amount because               
    the payment program was run late.                                                                               
    Keeping the above scenario in mind, and considering the Note               
    31345.
    I hope this helps.
    mauri

  • Customer Down Payment

    Dear Gurus,
    Have a question on Customer Down Payment.
    We first create a request, next when the Down Payment is received then we clear the request against the payment received.  When the invoice is raised can we do automatic clearing of the Down Payment with the Invoice?
    If yes, what would be the process... do we have to clear the Down Payment first manually and then we do automatic clearing?
    Do let me know this, thanks in advance.
    regards,
    Raj

    Raj,
    Here is how it goes :
    1. Down Payment Request ( F-37 - Need to post it to Alternative Reconciliation Account YYYYY - not part of the double-entry bookkeeping)
    2. Down Payment ( F-29)
    3.Invoice (FB70 )
    4. Down Payment Clearing -( F-39)
    5.Payment and Clearing
    Check the following document for more info:
    http://help.sap.com/bestpractices/BBLibrary/Documentation/J03_AR_BPP_01_EN_SG.doc
    Hope that helps - Let me know if you need more info.
    Thanks,
    N

  • Manual Accruals and Manual Payment in rebates

    Hi,
    what is the difference between manual accurals and manual payment in a rebate scenario.
    1)can someone explain a functional scenario.
    2) also iam aware that a credit memo request and then a credit memo is made in case of a manual payment.
    what document type(debit memo request or credit memo req) is made in case of a manual accrual and why ?
    regards
    sachin

    Dear Sachin,
    In rebate process we ahve Manuall accruals and Posting accruals manually but I don't know about manual payment.
    Please go through this SAP help link it will help you about Rebates process detailly in the Sales and Distribution.
    http://help.sap.com/saphelp_47x200/helpdata/en/dd/561270545a11d1a7020000e829fd11/frameset.htm
    I hope this will help you,
    Regards,
    Murali.

  • Customer Down Payment Configuration

    Hi All,
    Can any one guide me how to configure customer down payment.
    I have to raise the invoice for down payment to customer for specfic %age out of total order value. Please guide at earliest. Thanks in advance.
    Regards,
    Mahendra

    Dear Mahendra
    The following Customizing settings have to be made for down payment processing:
    Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
    You need to implement the following activities in the billing plan for down payments:
    Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
    Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
    Maintaining a Pricing Procedure with the Condition Type AZWR:
    In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
    Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
    Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
    Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
    Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
    Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
    Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
    Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
    Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
    the G/L accounts you have selected, you should assign the field status definition G031.
    Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
    You must also carry out a G/L account number assignment for the tax account.
    Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
    Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
    sales order as an optional field !!!
    Assign the company code to the field status variants (transaction OBC5)
    thanks
    G. Lakshmipathi

  • Extended Rebate Manual Payments

    Hello
    I am configuring extended rebate processing for my company.  We need to use extended rebate processing particularly for the variable key functionality.  i have noticed that manual payments are no longer active for extended agreements, but OSS NOTE 1156159 indicates perhaps that the correction will activate manual payments.  We do not see this behavior after implementing the correction specified.
    Is it possible to create a manual payment when using extended rebates?  If so can anyone provide details of how to do so. 
    If i have a rebate which is volume dependent...say 20,000 items and customer buys 19900 items and sales decides to pay the rebate based on what has been accrued, how can i accomplish this with an extneded agreement? 
    If anyone has implemented this particular note, what functionality does it provide?

    Hello Thomas,
    within Extended rebate processing, the manul settlement by VBO2 is not allowed.
    Settlement can only be performed by transaction RBT_ENH_VB7.
    The purpose of note 1156159 is to allow the modification of payment amount in the credit memo created by periodic partial settlement (by run RBT_ENH_VB7), if it is not transferred to accounting.
    Best regards,
    Ivano.

  • Customer late payment invoice

    Good morning
    I'm trying to fix minimum amount for calculation of customer late payment invoive, with different currencies using calculation on open item and not balance sheet , but it doesn't work, in customizing i set this program SAPLFI_INTVW and SAPL0F05.
    Could you help me please
    Best regards
    Giovanni

    Hi,
    please select a particular document type(except DR/KR) for customers/vendors for interest postings.
    so that system post interest postings only this document type. While doing the interest calculation you can exclude this document type, so that interest can be calculated only on invoice line items only.
    please use the following path to determine document type for transactions OBV1, OBV9, OBV3 & OBV4.
    Goto---Doc. type.
    Rgds
    Murali. N

  • Validation for Customer Incoming Payment

    Dear All,
    We are facing one issue regarding customer incoming payment. When user is making income payment via f-28, he enters the credit control area and GL Account according to division.
    Problem is, though customer master in Sales Area is not maintained, system allows to post the incoming document. Due to it, customer credit limit does not get updated and we have to update it manually every time by resetting the customer master.
    Do anyone have any validation for that in F-28?
    Regards,
    Jigar

    Hi,
    Look in to the given link for Create Validations.
    http://help.sap.com/saphelp_erp60_sp/helpdata/EN/5b/d231e143c611d182b30000e829fbfe/frameset.htm
    Regards,
    Sridhar Sha

  • Manual payment run

    Hi,
    I have few questions regarding manual payment run:
    1.Whats the difference between manual payment run and automatic payment run
    2.Which tables get updated through both payment runs.
    3.In which tables are all bank details updated through manual payment run.
    Thanks.

    Hi abhishek
    1. For manual payment , you need to select the open item that you want to make payment and choose bank account and others thing but automatic payment run , the system will check the condition in the configuration for example checking reference in the document ,
    if the documents have a same condition , the system will select that documents to make payment .
    2.,3.
    Bank Accounting: Payment
    <b>PAYR</b>     Payment Medium File                    
    <b>PCEC</b>     Pre-numbered Check 
    Bank Accounting: Payment Transactions – Automatic Payments
    <b>F111G </b>  Global Settings for Payment Program for
                   MANDT Payment Requests
    <b>FDZA</b>    Cash Management Line Items in Payment  
                   Requests
    <b>PAYRQ </b>  Payment Requests                       
    Regards
    Wiboon

Maybe you are looking for