Reason code in automatic payment

Hi
Please advice how to add the reason code in change line item while editing the proposal in automatic payment run.
Thank you

Hi,
the reason code is normally used for payments with differences to the invoice amount. In the payment run the invoice would normally be paid fully except you have made some further reduction postings to that invoice so you would pay a reduced amount by selecting the invoice and the credit memos relating to it.
But there is no option to choose this in F110.
If you want to pay a reduced amount and have a reason code consider using the manual payment functions (F-53 / F-58).
Hope this helps
Hein

Similar Messages

Error: Reason codes with automatic charge-off are not permitted here(F-28)

Hi All
I creted a reason code in obxl t-code and assigned a gl code in OBXL transaction code, But when I am trying to clear a payment with reason code in F-28, System is throwing the following error..Can some one tell me why i am getting this error?
Reason codes with automatic charge-off are not permitted here
Message no. F5605
Diagnosis
The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose. Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
System Response
The reason code entered is not accepted.
Procedure
You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.

Hi Venkata,
It seems while entering the payment (partial payment / residual items) ... you are clearing multiple items with differences. (e.g. if the difference amount is $30, then may the difference consists of two invoices underpaid by $15 each). In this scenario, F-28 doesn't know which additional account assignment fields should be picked up ... hence the error.
First of all, to validate that this indeed is the case, try clearing a payment with the same reason code where difference can be attributed to a single invoice. If you still get an error, then there is some other problem.
Then, to take care of a the business scenario where the difference can indeed be due to multiple documents, select "charge off difference" option and create an entry to post the difference as necessary.
HTH,
Manish Patel
Sr. SAP Solutions Consultant

Reason code for short payment received from Customers

Hello
We are on ECC 6.0 without application of any enhancement package.
Requirement is to capture reasons of short payment received from customer and generate a report based on such reason codes.
Reasons of short payment received could be - Adhoc payment; Excess billed; Tax deducted at source (TDS) on freight / service charges and Bank charges etc.
Let me know relevant configuration required.
Would reason codes be captured during incoming payment entry or customer account clearing?
Thanks.
Vimal, India

Hi Vimal
Following is the configuration for Reason code for customer payments. It can be short payment, over payment or discount not allowed.
First step is to define reason code. You do this in Financial Accounting (New >Accounts Receivable and Accounts Payable>Incoming Payments>Incoming Payments Global Settings>Overpayment/Underpayment>Define Reason Codes
Define reason code , short text, long text and assign it to correspondence type. (please note correspondence type settings needs to be done first). There is a column c which is Indicator: Charge off difference via separate account set this if you want to post the difference to seperate account during clearing customer open item.
The second step is to define accounts for payment difference.
Financial Accounting (New >Accounts Receivable and Accounts Payable>Incoming Payments>Incoming Payments Global Settings>Overpayment/Underpayment>Define Accounts for Payment Differences
Assign G/L accounts against reason codes.
The third step is Define Reason Code Conversion Version
Financial Accounting (New >Accounts Receivable and Accounts Payable>Incoming Payments>Incoming Payments Global Settings>Overpayment/Underpayment>Define Reason Code Conversion Version
In this step, you make the default settings you need for the manual incoming payment processing via payment advice notes. If differences between the payment advice item and the total of the allocated open items occur after selecting the open items, you can enter a reason code in the payment advice item. This represents the reason for the reduction of the payment amount specified by the paying person.
Create version 001 and name for it.
For correspondence type create or assign relevant form and print program in global settings> correspondence
Once you have these settings you can insert appropriate reason code while clearing customer open item .
You can print correspondence via T-ode F.62 on a monthly basis or wekly basis.
Hope this helps.
Thanks
Sanjeev

How to put default section code in Automatic payment program(F110)

Hi,
Is it possible to put default section code(BSEG-SECCO) in transaction code F110 for down payment transactions through Automatic payment program.
in our company section code is required field for vendor transactions, if i am doing the transaction F-48 or F-53 or F-58 , i can able to give the input for section code, But when i am executing the auto payment against payment request system showing the error message 'Please Enter 1001 As Section Code" based on my validation rule for section code for posting key 29 with account type K
How to overcome the above section code issue in auto payment without deactivation of validation.

Hi,
Just confirm how many section codes you are having.
If you are having only one section code for your company code then you can achieve this by developing a substitution rule.
T.code GGB1
Prerequisite
BSEG-BUKRS = 1000(give your company code)
Substitution
BSEG-SECCO=1001(give your section code)
Here take constant and give section code manually
If you are using business area then you need to give business area in prerequisite and respective section code in substitution.
After you define the substitution you need to activate for your company code through T.code OBBH.
Revert if you have any queries.
Regards,
Sankar
Edited by: Durgasankar.Innamuri on Jul 30, 2010 12:11 PM

Incoming payment by F-28: Reason code error while posting

Hello everyone,
I want to post Incoing Payment using F-28 net of TDS. I want the separate GL account to be picked up automatically for the difference when I enter the Reason Code 003.
I did the following customization for the same.
1. Financial Accounting> Accounts Receivable and Accounts Payable> Business Transactions>Incoimng Payments> Incoming Payments Global Settings>Overpayment/Underpayment> Define Reason Codes:- Here I selected the Indicator 'C' for reason code 003 which is for "Indicator: Charge off difference via separate account". The reason code 003 is for TDS Netted
2. Below the Define Reason Code node, I selected the node 'Define Accounts for Payment Differences' . Selected the key ' Rules' and selected the checkbox 'Reason Code'. Then clicked on 'Accounts' and enetered the desired GL account against the reason code '003'.
After doing the above customization I posted the Incoming payment using T code F-28. I entered the difference in the field 'Difference Posting'. Then entered reason code '003' which is for 'TDS netted' in the field 'Reason Code'. Now, I am getting the follwoing error.
Reason codes with automatic charge-off are not permitted here
Message no. F5605
Diagnosis
The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose. Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
System Response
The reason code entered is not accepted.
Procedure
You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.
How can I proceed ahead?
Thanks and Regards,
Pradnya

Hi Saulo,
Thanks for ur reply.
I had alreay done the config in OBXL and OBBE. Only thing I wanted to know is while posting Incoming Payment by F-28, how to use this reason code.
Ur reply was a gr8 help for me.
Regards,
Pradnya

Reason code and payment terms

Hi Gurus,
Is there any link between reason codes and payment terms ?
When I am posting a document or creating any residual and assign a reason code, it automatically assign a payment term and which i am unable to change.
any advice, suggestion would be appreciated.
Thanks.

Hi,
There is no direct link between Reason Code and Payment terms.
Reason code is the key actually specify the reason for payment difference it can be any reason like DISPUTE - TAX, DISPUTE - IN PRICE, DISPUTE EX - QTY and so on and those we can define.
Where as Payment Term are used to define
1. Base line date for due date calculation
2. Cash discount periods
3. Cash discount percentage rated
And the Payment Term which is coming by default while posting the document is the same one which has been defined in your master data for that customer. So I would suggest you check the master for that customer and surely you will find the same payment term updated there as well.
But it not means that you can not changed Payment term while creating or posting document, you change it and it will supersede you master data payment term.
Hope this will answer your query.
Regards,
Abhinav Sharma

Where to configure the reason code for payment differene

Dear Experts,
I did the settings in obxl with reason code option and changed the screen layout for the postings keys for payment difference as mandatory. while doing the account assignment in obxl system asking the reason code for payment difference. Where to configure the reason code any t.code is there, please guide me.
J.francis

Just Go SPRO>IMG>Financial Accounting (New) >Accounts Receivable and Accounts Payable > Business Transactions > Outgoing Payments > Manual Outgoing Payments > Overpayment/Underpayment > Define Reason Codes (Manual Outgoing Payments)
There you have to create Reason Code
Now go SPRO>IMG>Financial Accounting (New) >Accounts Receivable and Accounts Payable > Business Transactions > Outgoing Payments > Manual Outgoing Payments > Overpayment/Underpayment >Define Accounts for Payment Differences (Manual Outgoing Payment)
Here assign GL
Best Of Luck
Tanmoy

Error while configuring the automatic payment

Hi
I configured for the over and under payment. However whenever i try to to use the reason code i get an error . reason code with automatic charge off is not permitted here.I was using the Tcode F-28
The diagnosis says that the automatic posting requires adtional specifications.and since the difference is not from one open item this method can not be used.
Need help on this.
Thanks in advance

Thank you All,
i tried connecting using AD Browser from Microsoft, and it went in properly. then i found out that the AD Team here were giving a Wrong Credentials to connect, they Gave me HYP_OID which infact turned out to be a Principal name instead of a 'cn'.
after searching in the AD Browser i found the correct cn which is "Hyperion OID", then it went to the second Screen where now i am trying to search for the Users based on thier Job Nature.
Thank you for all the Support Guys, you both "Celvin" and "John" are the Top Guys under my Search list for any technical Assistance.
Thank you once again Friends....
Regards,
Sunil...
Shantan....

How to check F110 - automatic payment transaction

Dear gurus,
I had to execute the T-code F110 ("automatic payment transaction).
I'd like to check/verify if I have correctly entering the datas.
Is there a mean to check?
After throwing the proposal and the payment I have the following message : "Posting orders: 2 generated, 2 completed".
What does it mean?
How can I check/verify the recision of my enteries? Is there a transaction that I can execute to verify?
Thanks,
Regards,
gul

Hi
For the 'Red' Line item in F110, check the proposal log & the payment log for the details of the error message.
The error may be due to these common problems:
- Bank data not maintained properly
- Vendor master not updated for payment method or house bank
- house bank settings & FBZP configuration improper (go thro the FBZP settings fully for that payment code - house bank combination)
For the other open items in FBL1N which are not processed in F110, it may be due to the foll reasons:
- Either they are not due as on the date mentioned in F110
- Parameters enetered in F110 don't fufil those documents (like house bank, payment method, etc).
Regards
Srini

How to generate checks when executing Automatic Payment Program (F110)

Is it possible to generate checks automatically when I execute the automatic payment program? Will reward points to any suggestion. Thanks!

hi patrick
try this.....ur problem may solve.....
Create Automatic Payment Transactions (F110)
Purpose
Use this procedure to generate checks proposals or ACH proposals and then subsequently issue checks or set up ACH files to be transmitted to the bank.
Trigger
Perform this procedure when through either an ACH or a check, a creditor of the University needs to be paid.
Prerequisites
Open invoices with reached due dates have to be present in the SAP system.
Menu Path
Use the following menu path to begin this transaction:
·         Select Accounting Financial Accounting Accounts Payable Periodic processing Payments to go to the Automatic Payment Transactions: Status screen.
Transaction Code
F110
Business Process Information
The automatic payment process will be centrally managed in the Accounts Payable Office. The automatic payment program will be executed each day for all open invoices (across vendors) in the system. There will be separate payment run execution corresponding to each payment method category:
Check payments: clears the open invoices and issues a check output
ACH payments: clears the open invoices and issues an ACH file output
Foreign currency payments: clears open invoices but no output is issued
State/Grant payments: clears open invoices but no output is issued
The process steps executed during the automatic payment program are:
Enter Payment Parameters
Edit/review Payment Proposal
Post Payments
Generate Payment Medium (print checks or create ACH payment file)
Generate Positive Payment File
The payment parameters are entered in order to limit the open invoices and credits selected for payment. It is important to note that the payment terms that are defined on the invoice will drive whether a invoice is due for payment during the current payment run. During the payment program execution, the invoices that are due for payment will be presented to the user on a payment proposal list.
The payment proposal is a list of expected payments grouped by vendor account. Invoices that are due for payment but cannot be paid due to some kind of accounting or system error are listed as exceptions. Examples of typical exceptions are missing banking information (for ACH payments) and blocked invoices. Some payment exceptions will be resolved at the Accounts Payable Office. However the Department must resolve some exceptions. When these types of exceptions appear on the payment proposals, the Accounts Payable Office will inform the Department of the blocked payment in order to get a resolution. Key personnel in the Accounts Payable Office will be the only resources to have access to the editing function of the payment proposal processing. Typically, there is no business reason the edit or change a payment proposal. Editing options for a payment proposal includes: changing the default disbursing bank account information or changing the payment method.
After the payment proposals have been reviewed and edited, the proposals are posted as payments. It is important to note that any open credit on the vendor's account is also taken in consideration when creating the vendor's payment. The payment method supplement defined on the invoice will drive the check sorting.
In addition to the printed check output, the payment program run produces an ACH file and a Positive Pay file. Both files are sent to the bank for further processing. The ACH file contains the vendor's payment and banking data. The Positive Pay file contains the check data (check processed, voided, etc) and is used for confirmation of payments.
Helpful Hints
·         The R/O/C column in the field description tables below defines whether the field is required (R), optional (O), or conditional (C).
·         On certain screens you may have to scroll to view some data entry fields.
·         Click the tab to view the current overall status of the payment process by viewing the informational messages.
Procedure
1. Start the transaction using the menu path or transaction code.
    Automatic Payment Transactions: Status
2. As required, complete the following fields:
·         Run date
·         Identification
3. Click the tab.
The payment program parameters are used to limit the program's selection of open invoices and credits.
    Automatic Payment Transactions: Parameters
4. As required, complete/review the following fields:
·         Posting date
·         Docs entered up to
·         Company codes
·         Pmt meths
·         Next p/date
·         Vendor
5. Click the tab.
Free selection criteria are extended parameter selection criteria used to limit the open invoices and credits selected in the payment run.
    Automatic Payment Transactions: Free Selection
6. Perform any of the following:
If You Want To
Then
Select data by a particular field value; use the match code on the Field Name field to obtain the required field
Enter the required field value to be considered in the payment program selection of open items. The field value is entered in the Values field
Payment selection can be based on fields on the invoice or credit memo document or fields on the vendor master.
Example: A (AP payment block)
Exclude the open items that match your field value
Select to the left of Exclude values.
Include only those open items that match your field value
Deselect to the left of Exclude values.
7. Click the tab.
This information is used to expand the information that is automatically recorded in the payment run log. The payment run log is used to diagnose any program errors during the payment run.
    Automatic Payment Transactions: Additional Log
8. Perform the following:
If You Want the Payment Program Log to Record
Then
Information on due date check
Select to the left of Due date check.
Activate this option.
Any payment method selection data
Select to the left of Payment method selection in all cases.
Activate this option.
Line item information the payment documents generated upon posting the payment proposal
Select to the left of Line items of the payment documents.
Activate this option.
9. As required, complete/review the following fields:
·         Vendors (from)
·         Vendors (to)
Enter the same vendor account number range for Accounts required section of the transaction.
10. Click the tab.
The specifications defined in this section of the transaction inform the payment program the correct form to use for check printing and the correct payment file format to use for ACH payments.
    Automatic Payment Transactions: Printout and DME
11. As required, complete the following fields:
·         RFFOAVIS
·         RFFOUS_C
12. Click the tab.
    Exit editing
13. Click to save the data.
If you want to delete the payment program parameters entered, select Edit Parameters Delete.
    Automatic Payment Transactions: Status (2)
The system displays the message, "Details have been saved for the run on XX/XX/XX XXXX."
14. Click .
If you want to refresh the screen in order to view the current status (processing step) of the payment program click at any time.
    Schedule Proposal
15. Perform one of the following:
If You Want To
Then
Execute the payment program (i.e. process the payment parameters entered and create a payment proposal) immediately
Select to the left of Start immediately.
Activate this option.
Designate a target computer
Enter the name in the Target computer field.
16. Click to process the payment parameters and create a payment proposal.
While the payment program is selecting and processing data, the status will display the message, "Proposal is running." When the payment proposal has completed and is ready for review/edit, the system will display the message, "Payment proposal has been created."
    Automatic Payment Transactions: Status (3)
The system displays the message, "Proposal run has been scheduled."
17. Click .
    Automatic Payment Transactions: Status (4)
The system updates the status, "Payment proposal has been created."
18. Perform one of the following:
If You Want To
Then
Go To
Execute the payment run
Click .
Step 19
Edit the payment proposal
Click .
Step 43
Display the payment proposal
Click .
Step 54
Display the payment proposal run log
Click .
Step 57
Delete the proposal
Select Edit Proposal Delete.
Step 60
Display the proposal list in a printer friendly format
Select Edit Proposal Proposal List....
Step 62
Display only the exception (error) invoices or credits
Select Edit Proposal Exception List....
Step 67
Exit this transaction
Step 72
    Schedule Payment
19. Perform the following:
If You Want To
Then
Execute the payment program (i.e. process the payment parameters entered and create a payment proposal) immediately
Select to the left of Start immediately.
Activate this option.
Designate a target computer
Enter the name in the Target computer field.
20. Click to process the payment proposal and post the payment documents.
While the payment program is selecting and processing data, the status will display 'Payment is running'. When the payment proposal posted the status will display 'Payment run has been carried out. Posting orders X generated, X completed. (X will represent the total number of checks produced).
    Automatic Payment Transactions: Status (5)
The system displays the message, "Payment run has been scheduled."
21. Click .
    Automatic Payment Transactions: Status (6)
The system updates the status, "Payment run has been carried out." If you click after seeing the status update, "Payment run has been carried out", the system will display an update to the status, "Posting orders: XXXX generated, XXXX completed."
22. Perform one of the following:
If You Want To
Then
Go To
Review the payments posted
Click .
Step 23
Display the payment proposal
Click .
Step 26
Display the payment proposal run log
Click .
Step 29
Display the payment list in a printer friendly format
Select Edit Payments Payment List.
Step 32
Display only the exception (error) invoices or credits
Select Edit Payments Exception List.
Step 36
Print the payment run information
Click .
Step 40
Exit this transaction
Step 72
    Job Log Entries for F110-XXXX-XXXX / XXXX
23. Review the displayed information.
24. Click .
25. Return to Step 22.
    Display Payment Proposal: Payments
26. Review the displayed information.
27. Click .
28. Return to Step 22.
    Job Log Entries for F110-XXXX-XXXX-X / XXXX (2)
29. Review the displayed information.
30. Click .
31. Return to Step 22.
    List Variant
32. Click .
    Payment list
33. Review the displayed information.
34. Click .
35. Return to Step 22.
    List Variant (2)
36. Click .
    Payment list (2)
37. Review the displayed information.
38. Click .
39. Return to Step 22.
    Schedule Print
40. As required, complete/review the following fields:
·         Start date
·         Start immediately
·         Start time
·         Target computer
·         Job name
41. Click .
42. Return to Step 22.
    Accounting clerk
43. Click .
    Edit Payment Proposal: Payments
44. Review the displayed information.
45. Perform one of the following:
If You Want To
Then
Go To
Continue with the payment process
Click .
Step 18
Review/edit invoice information for the payment (invoice numbers, discounts, payment amounts, etc).
1. Click on the line you want to select.
2. Click .
Step 46
Change the key payment information (payment method, house bank, payee name and address, etc.)
1. Click on the line you want to select.
2. Click .
This option does not work for lines that have exceptions.
Step 51
    Edit Payment Proposal: Open Items
46. Double-click on the line you want to choose.
    Change Line Items
47. As required, complete/review the following fields:
·         Payment block
·         Discount amount
·         Cash discount %
48. Click .
49. Click .
50. Return to Step 45.
    Change Payment
51. As required, complete/review the following fields:
·         Payment method
·         Pmt meth.supl.
·         Due date
52. Click .
53. Return to Step 45.
    Display Payment Proposal: Payments
54. Review the displayed information.
55. Click .
56. Return to Step 18.
    Job Log Entries for F110-XXXX-XXXX-X / XXXX (3)
57. Review the displayed information.
58. Click .
59. Return to Step 18.
    Delete proposal
60. Click .
    Automatic Payment Transactions: Status (7)
The system displays the message, "Data and log deleted."
61. Go to Step 72.
    List Variant (3)
62. As required, complete the following field:
·         Variant
63. Click .
    Payment list (3)
64. Review the displayed information.
65. Click .
66. Return to Step 18.
    List Variant (4)
67. As required, complete the following field:
·         Variant
68. Click .
    Payment list (4)
69. Review the displayed information.
70. Click .
71. Return to Step 18.
72. Click until you return to the SAP Easy Access screen.
73. You have completed this transaction.
Result
You have executed a payment proposal, executed and posted a payment run and printed checks.
reward me points.......dont forget

Cheque print from F110 (Automatic Payment Transaction)

Hello Friends,
I have a requirement to print the cheque from t.code F110 (Automatic Payment Transactions).
Normally when run Auto payment from F110 it will give A4 size print out at top having Address details and then item details, and finally Cheque data will print.
But our requirement is only Cheque print, we dont want to print total page.
For this Script is F110_PRENUM_CHCK and print program is RFFOUS_C.
can any one suggest me how to solve this issue.
Regards,

HI,
carry out the following changes with the help of the functinal guy around.
In F110 goto the Printout/data medium tab, there click on the Variant name against pgm - RFFOUS_C, say it is Z_VAR1, now click on the 'Maintain Variants' (pushbutton on tool bar)
This will take you to the Variant screen of this pgm,
Under the 'Print control' block deselect the 'Print payment summary'
Under the 'Output control' block change the value of 'Number of Sample printouts' to 1.
Hope this helps.

Check posing date on F110 Automatic payment

Hi Guru
I have some problem on transaction code F110 (Automatic payment program) . Can the program selection check posting date of invoice document not more than field "Docs entered up to" ?

Yes, the system checks that the invoices selecte should not have posting date greater than "Docs entered up to"
Regards,
SDNer

Incoming Payment with Underpayment/Overpayment in F-28 with reason code

Hi All,
While making a incoming payment with overpayment / underpayment in F-28, I am getting an error u2018Reason codes with automatic charge-off are not permitted here u2018. The reason code is defined with charge off checked and the account for differences is defined for the same.
Please advice
Thanks

Please check "Indicator: Charge off difference via separate account" in reason code settings (TCode OBBE). If this indicator is set against the reason code that you are using, you will getting the error.
What you can do is either use different reason code or in residual items tab you can specify the reason code with residual items.
Thanks,
Sukhbold
Edited by: Sukhbold Altanbat on Oct 13, 2011 7:47 AM

Customer Payment using Reason codes

Hi Freinds,
I have checked many SDN replies on this, but i didnt find the right solution.
I have assigned GL account for Reason code 055 for ZDI (Payment differences by reason) in OBBE. In F-28 i want to post some difference amount to this account automatically. when i selected 055 on Residual tab and simulated, the difference amount again going to Customer a/c.
Please tell me the possible reasons and please explain me briefly how to use the Reason codes in F-28 step by step
Appreciate your help.
Thanks in advance.
Kanna.

Hi,
Please check the settings for 'Reason code: 55' through 't.code: OBBE'.
Though you asign a GL account for reason code, if the reason code is not activated for Charge off difference via separate account, system will not charge-off the difference to a GL account.
Thanks,
Vinod

Clearing Payment to a G/L account set up in Reason Code

I am having a problem posting an overpayment/underpayment to a G/L account using a reason code. What I am attempting to do is, using F-28, have the remainder of an underpayment post to a G/L account attached to the reason codes. What I need to have work is that in F-28 I do not want to have to enter any data on what the residual amount is, it should just take whatever is not paid and apply it to the G/L account tied to the reason code. I have set 3 new reason codes in OBBE to test different possibilities with the checkboxes in that transaction, and have attached each of the reason codes to accounts using OBXL. What is happening now is that when I enter a short pay amount for an invoice and I enter a reason code in the RCd field in the residual tab - I hit save and it seems to try to attach the remaining amount to an account that is currently tied to a blank reason code in our setup in OBXL. I would think that since I am placing a code in the RCD field, that it would use the account tied to that. I have also tried to use the reason code field below, but encounter the same results or, with one of my codes that has the "charge off difference via separate account" checkbox checked, it will not allow that code in that field below.
There must be a way to take the shortpay amoun,t and without entering the residual amount anywhere, use the G/L account tied to the reason code to post the remainder to. Can anybody help on what I may need to do to get this to work?
Thanks -
PS. This is not a tolerance issue as I have set the tolerances for both the customer and the user high enough to allow under/overpayments.

No... this is SAP standard.... if you are treating them as residual payment and the GL is seperate than the small diff GL we have to enter the amount there..... as system cannot understand whats the differnece when we dont put the amount there......
we can always see the field NOT ASSIGNED in the bootom.. it is just the matter of copy paste for the user.... it has to come thro user discipline.... i dont see a standard sap way of doing it,....

Reason code in automatic payment

Similar Messages

Maybe you are looking for