Lock box- payment differences

Dear gurus
We have a request to change the lockbox setup to handle auto write off any short/overpayments per customer invoice of +/- 50$.
So when there is a difference of +/-50$ on the payment file (in the lock box process- statement from bank) SAP should write off the difference to a GL acct automatically.
Please advise where in config, I can make settings and give the acct number, so that differences will written off automatically and how can I test my settings?
Many thanks in advance
MSJ

Hi Vinod
Thank you for your reply. I followed your instructions.
But I see that in OBXL there is already a GL acct  499999specified  with no reason code.
And this Gl acct is hit if there is any unapplied/on acct payments from lock box.
What we need is , if there is any difference of =/- 50$ it should go to 488888 GLacct.
I tried putting 488888 in OBXL with a reason code(created a new reason code) and  tried processing a lockbox file, but after running, I see that the payment difference of +/- 50$ is not being hit to 4888888 acct.
Please advise as what other changes we need in config.
many thanks
MSJ

Similar Messages

  • Payment Advise error while uploading Lock box

    Hi,
    i am getting the below error in FBL1 transaction code. I am able to upload the lock box in FBL2 transaction with Appllied status. After that when i execute FBL1 transaction i am getting the below error related to Payment Advise. Kindly help me to fix this issue...
    Payment advice 010000000700001 does not exist for account 237059 1000
    Thanks
    Kishore

    Once the incoming payment is applied and the invoice is cleared the system would delete the payment advice immediately and you would get this error from FLB1, this is standard.

  • Lock Box Reason Code.

    Hi Experts,
    I am getting one issue in lock box, If Suppose customer has invoice of $ 1000, he is eligible for discount of $ 50 so he should pay net amount $ 950. But customer is paying full amount without knowing that he is eligible for discount i.e $ 1000. so system is crediting back $ 50 to the customer(returning back the $ 50 to customer).
    In this case i want system should accept amount $1000 and system should not credit $ 50 to customer(system should not pay back to customer $ 50), instead of this system should transfer the balance to GL account by using the reason code.
    Note : we are using BAI2 format for lockbox.
    Please be advised what should i do in this case if i want to accept the full amount from the customer without doing the credit to him and i want to transfer the amount to GL account by using reason code in BAI2 format.
    Regards,
    Sam.
    Edited by: samiuk on Nov 11, 2011 4:23 PM

    Yes you can.
    Customer and User tolerance limits, payment advice tolerance limits and reason codes
    When an incoming cash payment does not exactly pay the referenced open item(s), then the system will not be able to perform clearing without creating residual items back on the account - except when you establish tolerance limits to allow posting with a write-off of acceptable payment difference amounts.
    Reason code settings are used for description and reporting purposes, generation of specific customer correspondence letters (automatic system generation whenever this reason code is assigned to a document), and difference item write-off/dispute status assignment.

  • Lock box  reason codes

    Dear gurus
    please advise as how we can uses reason codes with lock box file processing.
    We want to write off each individual invoice on customer open item if it is paid +/-60$.
    Can we use reason codes with lock box automatic processing, so that these +/-60$ writeoff's go to a particulat GL acct.
    Many thanks in advance.
    MSJ

    Yes you can.
    Customer and User tolerance limits, payment advice tolerance limits and reason codes
    When an incoming cash payment does not exactly pay the referenced open item(s), then the system will not be able to perform clearing without creating residual items back on the account - except when you establish tolerance limits to allow posting with a write-off of acceptable payment difference amounts.
    Reason code settings are used for description and reporting purposes, generation of specific customer correspondence letters (automatic system generation whenever this reason code is assigned to a document), and difference item write-off/dispute status assignment.

  • Lock Box - item not getting cleared

    Hi,
    I m testing the lockbox process with the lock box file available online.
    I could be able to import the file and document got created. But i have some doubts, please try to reply for the same.
    1) payment advice got generated but the customer open item is still not cleared? do we need to process that further? the check status is applied and G/L document got posted.
    2) I think we can also process lock box posting through Idoc, what is the process flow? would you pease eloberate on this IDOC  process for lockbox.
    3) I am not able to understand the posting done (without clearing the customer open item). Both debit and credit posted to a bank account. would you please eloberate the posting done while lockbox processing?
    Please let me know if more information required.
    Regards,

    Hi,
    If you are able to load the lockbox file then customer items shall be cleared. Please check the posting rule config and clearing accounts maintained for lockbox.
    Thanks,
    Sachin

  • Lock Box Uploading Issue

    Hi,
    When i upload BAI file into Lock Box...I am getting the below error in FBL2 transaction.
    Accounts receivable posting Error: (F5 102) Customer * is not defined in company code 1000
    After that when i see in to FBL1,I am getting the below error.
    Payment Advise item doesnot exist
    Payment advice 010000007500001 does not exist for account 9372 1000
    Message no. FA006
    Kindly help me what is the problem and why i am not able to upload it successfully?
    Thanks
    Kishore

    I am experiencing the same issue.
    I am wondering how you went about in correcting this issue
    Thanks

  • Lock box jobs getting cancelled

    Hello All,
    I am new to lockbox processing. I am into lock box support project now. Recently lot of lock box jobs are getting cancelled. While I am going through job log it says that " Payment advice 01706525923 does not exist for account 10001009 0110 ". Similar error showing for few other jobs. Can you please anybody through some light on this regarding how to investigate this error?
    Thank you,
    Santosh

    When ever you get such kind of message then it says that it has found the customer and not found the document to post.
    Now when you got to T.code FLB1. you can see that in "on account" status.
    Now through lockbox post processing you have to post/clear the document (thru F.04) to make the document to "Applied" status.
    Assign points if useful.

  • Lock Box configuration and Lock box process

    Hi
    I immediately need detailed lock box configuration settings and do the process in easy access and also need the seetings for BAI format, which is part of lock box configuration.
    I will highly appreciate, if you immediately respond for the above.
    Thanks & Regards,
    Radhakrishna

    HI,
    To have Lock Box Customizing in the system you need to defien the following
    FA-Bank Accounting-Business Transaction-Payment Transaction-Lock Box
    Define Control Parameters for BAI format as
    Doc Length : 10
    No of Doc nu in type 6 : 3
    No of Doc nu in type 4 : 6
    GL Account posting : x
    Incoming customer payments : x
    GL account posting type : 1
    Enter all the details and save the BAI format
    Define Posting Date as
    Destination : 1000123456
    Origin : 0011000390
    Company Code : ABCD
    House Bank : HSBC
    Account ID: HSBCA
    Bank GL account: Deposit bank A/c
    Bank Clearing A/C : Clearing Account
    Bank Posting Doc type : SA
    Cus Posting Doc Type : DZ
    Posting Key  Dr : 40
    Posting Key Cr : 50
    Posting Key credit Cust : 15
    Posting Key DR cust : 06
    And save the posting date
    And in Customer master Payment Transaction Tab create Customer Bank details with bank key and Bank Account.
    then create a text file as show below
    100100012345600110003900712110100
    210001234560011000390
    5086001007250407121110001234560011000390
    60860020000150000 044115126189175247210 11000206
    408600360171800000003        0000150000000000000000   testtesttesttest
    7086007007250407121100100001500000
    80860080072504071211000100001500009    015000    015000
    9000001
    If any confusion in text file give ur mail id i will send you the file with explanation.
    Regards
    Balaji

  • Lock box post process

    Hi,
    Can anybody please let me know what is the error comes at the time of processing the Bank File?
    and can please let me know what would be happened if we getting the less amount then the invoice amount. what kind of error the system will pass?
    It's really very urgent.
    THanks,

    HI,
    To have Lock Box Customizing in the system you need to defien the following
    FA-Bank Accounting-Business Transaction-Payment Transaction-Lock Box
    Define Control Parameters for BAI format as
    Doc Length : 10
    No of Doc nu in type 6 : 3
    No of Doc nu in type 4 : 6
    GL Account posting : x
    Incoming customer payments : x
    GL account posting type : 1
    Enter all the details and save the BAI format
    Define Posting Date as
    Destination : 1000123456
    Origin : 0011000390
    Company Code : ABCD
    House Bank : HSBC
    Account ID: HSBCA
    Bank GL account: Deposit bank A/c
    Bank Clearing A/C : Clearing Account
    Bank Posting Doc type : SA
    Cus Posting Doc Type : DZ
    Posting Key  Dr : 40
    Posting Key Cr : 50
    Posting Key credit Cust : 15
    Posting Key DR cust : 06
    And save the posting date
    And in Customer master Payment Transaction Tab create Customer Bank details with bank key and Bank Account.
    then create a text file as show below
    100100012345600110003900712110100
    210001234560011000390
    5086001007250407121110001234560011000390
    60860020000150000 044115126189175247210 11000206
    408600360171800000003        0000150000000000000000   testtesttesttest
    7086007007250407121100100001500000
    80860080072504071211000100001500009    015000    015000
    9000001
    If any confusion in text file give ur mail id i will send you the file with explanation.
    Regards
    Balaji

  • Invoice clearing in Lock Box - FIFO basis

    hi experts,
    My client wants that for specific customer, all those outstanding invoices  be cleared with one payments received via check, that were received first, automatically. In other words, the stream of incoming payments will keep  clearing a sequence of all previous (date-wise)  outstanding invoices automatically.
      It seems we need to do some configuration changes in lock box process. Can any one give some insight in this regard as  how to make it possible?
    Thanks

    No, standard lockbox cofiguration doesn't provide this facility.
    There are 5 standard Lockbox program that do clearing based on either Reference (XBLNR) or Document number (BELNR) or both.
    You may have to customization.
    1. Use some custom re-processing program before Lockbox or
    2. See if you can change clearing rulses in one of the 2 available Lockbox user exits or

  • Lock box facility

    hi experts,i want to know about:what is lock box facility?can any body tell me the configation steps for that

    hi
    Using of lock box
    Lockbox is a process provided by a bank where the customer remits his payment to a PO Box at your bank, the bank deposits the check in your account and enters the remittance data from the customer. Then the bank sends the data to you electronically for you to import and apply in SAP-AR.
    The structure that the bank uses is usually one of two formats. BAI will provide you the customer information and the check amount but no invoice remittance data. Usually cheaper and works well for a business where customers are paying only one invoice at a time.
    BAI-2 offers remittance data but the bank charges more for the service because they have to enter more info.
    Look at structures FLB** to see the transfer data. 
    When the bank sends the customer payment data you use Treasury function FLB2 to import and then process the payments. This process attempts to determine where to apply the payment and will post directly against an invoice, an account to a customer or if it can't even determine the customer it posts into a clearing account (configured) to be resolved.
    for furthur notes
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/06/992a88b22c11d289c70000e8215862/frameset.htm
    nagesh

  • Lock box procedure

    sapians,
    Please Explain the LOCK BOX PROCESS?
    Business scenario..?
    Legacy system of lOCK BOX PROCESS?
    Regards,
    sap

    hi
    Lockbox is a process provided by a bank where the customer remits his payment to a PO Box at your bank, the bank deposits the check in your account and enters the remittance data from the customer. Then the bank sends the data to you electronically for you to import and apply in SAP-AR.
    The structure that the bank uses is usually one of two formats. BAI will provide you the customer information and the check amount but no invoice remittance data. Usually cheaper and works well for a business where customers are paying only one invoice at a time.
    BAI-2 offers remittance data but the bank charges more for the service because they have to enter more info.
    Look at structures FLB** to see the transfer data. 
    When the bank sends the customer payment data you use Treasury function FLB2 to import and then process the payments. This process attempts to determine where to apply the payment and will post directly against an invoice, an account to a customer or if it can't even determine the customer it posts into a clearing account (configured) to be resolved.
    nag

  • Lock Box - FLB2

    Hi All
    I tried to import data in TC FLB2, but i am getting the error that 'Customer Doesnt Exist' Error F5 102
    my Qs is, after setting up all config for Lock box, is there any other place where i need to maintain some MICR number or anything else for the customer on the master data etc
    thank you
    Rukshana

    The customer exists in a different company code than the lockbox and requires cross-company posting in post-processing.
    If the customer exists in both companies, the check should at least be put u201COn Accountu201D in the main company (the main company is the one that gets the cash, the one the lockbox is pointed to via transaction OBAX).  Then, when you u201Cpostu201D the check from FLB1, you will get the open items for the main company. Here you would use the Edit-> Select More function, and specify your other company.  Then select the open items and post.
    Alternatively a carefully designed user exit can be designed to look across company codes.
    You may consider a modest user-exit for cross company code cash application.  Such a user exit would check for open items across all company codes, despite the company code into which the payment was received (by lockbox definition in IMG).

  • About LOCK BOX account

    Hi experts,
    I have a doubt on lock box account.
    1.  when we open lock box account in bank it is used for payment collection from customers is it correct.
    2. Then how that payment information sent to R/3 systems, where we get that bank files & which area it is actually storage.
    3. How we can download that files is there any T.code for that downloading.
    4. what is different between BAI & BAI2,  EDI 820 & EDI823.
    Thanks & Regards,
    vinod.
    Moderator: Multuiple questions are not allowed in one thread. Also, please avoid asking basic questions

    Dear
    Please check the thread Item category 04000 not allowed
    Regards

  • How to improve lock box performance

    Hi
    I am working on lock box process. Currently they have lock box processing in 4.6c and now  upgrading to ECC 6.0. Client is not satisfied with the lock box hit rate and want to improve the hit rate by improving matching rate.
    Can any body tell me, what all are the aspects we can take a look and improve it.
    Thanks in advance
    Deepa

    Hi,
    Are you using BAI or BAI2 version of lockbox file? If you are using BAI version, then move to BAI2 version and this will improve the hit rate of Lockbox postings.
    Secondly, while executing the transaction FLB2, in processing parameters - Invoice numbers select the option of 3 or 4. This will enhance the hit rate as the system will look at document number as well as reference field. This will be helpful if Customer gives the number entered in reference field in payment advice.
    Thirdly, you can do a clean up of MICR and Bank Account numbers in Customer Master data. Maintain the correct data, if the data is not updated regularly based on Lockbox data.
    Fourthly, if multiple payer accounts are maintained for Customers, maintain worklist for such customers. Worklist can be maintained in transaction code OB55.
    Thanks
    Murali.

Maybe you are looking for