SAP BOX

'26/11/18 UPDATE

FI-AR / FIELD NOTES

When a payment falls short, a partial payment and a residual item leave the same balance. What differs?

A partial payment leaves the invoice open, while a residual item clears it and creates a new item. Using a fictional payment of KRW 600,000, this note compares open lines, dates, dunning and discount, and looks at how one reason code can turn money still owed into an expense, based on the S/4HANA 2025 documentation.

A KRW 1,000,000 invoice receives a payment of only KRW 600,000. The accountant can post a partial payment or a residual item. Either way the customer balance is KRW 400,000, so it is easy to reach for whichever is habit. The Help documentation, however, separates the two: the balance effect is the same and the effect on the line items is not. After reading this note you can explain what differs before you choose, and avoid the case where one reason code makes money still owed disappear from the account.

The sources are the SAP Help Portal documentation for SAP S/4HANA 2025 FPS02 and the public SAP Learning course "Customizing Core Settings in Financial Accounting in SAP S/4HANA". The company code, customer, document numbers, amounts and reason codes are all invented. Nothing here was run on an SAP system: the documented rules are applied to a fictional example. All amounts are in Korean won (KRW), and tax and cash discount are left out of the example.

Where this choice comes up

With a small difference there is nothing to choose. Inside the tolerance limits, the system adjusts the cash discount or writes the difference off to a separate account and clears. If both an employee tolerance group and a customer or vendor tolerance group apply, the lower limit counts. Above the limits the accountant has to act, and that is where partial payment and residual item appear as options. Writing the difference off to a separate G/L account, or posting the payment on account, are also possible.

Fictional example: one payment, two postings

In company code 1000, invoice 1800000101 to customer 300100 is KRW 1,000,000, with baseline date October 1, 2026 and net 30 terms, so the net due date is October 31. On November 16 a payment of KRW 600,000 arrives, and the KRW 400,000 difference is assumed to be above the customer tolerance limit, so it does not clear automatically, but within the accountant's employee tolerance group. You enter the payment in transaction F-28 (Accounting > Financial Accounting > Accounts Receivable > Document Entry > Incoming Payments) and go on to process open items. Here are the two results first.

Two cards. Partial payment: invoice 1800000101 for KRW 1,000,000 and payment 1400000111 for KRW 600,000 both stay open, balance KRW 400,000. Residual item: the invoice for KRW 1,000,000 and the payment of KRW 600,000 are cleared, only new item 1400000222 for KRW 400,000 is open, balance KRW 400,000.
The customer account after the posting in the text. The balances in the last lines match. Look at which lines remain open.

Partial payment: the invoice stays open

On the Partial pmt tab, enter 600,000 in the Payment amount column. The whole payment is assigned to this invoice, so nothing is left unassigned, and a reason code is optional. On posting, no item is cleared, and the payment is posted to the customer account as an open item. The account shows two lines, +1,000,000 and −600,000, with a balance of KRW 400,000. The Payment for field on the payment line records which invoice item it belongs to: document number, fiscal year and item. Other Help pages describe the same link as the Invoice reference field. When the remaining KRW 400,000 arrives and is posted, the invoice and the partial payment are cleared together.

Example SAP GUI F-28 process open items screen, Partial pmt tab. Invoice 1800000101, amount KRW 1,000,000, payment amount KRW 600,000, reason code empty, marker 1. Below, amount entered KRW 600,000 and not assigned KRW 0, marker 2.
Example of the Partial pmt tab in F-28. Marker 1 links to the sentence about entering the amount paid, and marker 2 to the sentence saying nothing is left unassigned. Tab and column names are shortened from the SAP Help Portal documentation for S/4HANA 2025 FPS02, and the total fields are drawn for explanation. All values are invented.

The Help documentation records one more detail. The system calculates the invoice's net due date and writes it to the payment line's Baseline date field, and the payment joins the dunning program and cash management at that date. In the example, the payment line's baseline date becomes October 31 rather than November 16, the day the money arrived. In the standard system the posting key for customer partial payments is 15.

Residual item: the invoice is cleared and a new item appears

On the Res. items tab, enter 400,000 in the Residual items column. An editing option can set this column to take the payment amount instead of the remaining amount. This time the invoice and payment are cleared, and the customer account holds a single new open item of KRW 400,000. The Residual for field on the new item records the original invoice, so the link remains, but invoice 1800000101 itself becomes a cleared item. SAP Learning says the new document number references the original documents. In the example the new item is 1400000222. To tell which invoice a line with this number belongs to, read the Residual for field.

Example SAP GUI F-28 process open items screen, Res. items tab. Invoice 1800000101, amount KRW 1,000,000, residual items KRW 400,000, reason code Z01, marker 1. A note line below says Z01 has Charge Off not set and Z02 has Charge Off set, marker 2.
Example of the Res. items tab in F-28. Marker 1 links to entering the residual amount, and marker 2 to the section on reason codes. Tab and column names are shortened from the SAP Help Portal documentation for S/4HANA 2025 FPS02, and the note line at marker 2 is drawn for explanation and may not exist on a real screen. All values are invented.

The terms of the new item come from the customer or vendor tolerance group. Payment terms are either taken from the original invoice or set by a predefined terms of payment key. How the new item's baseline date is set, however, was not found in the documents checked for this note. The example therefore gives no due date for the residual item, and this needs checking on a system. Cash discount can be set up to be granted only on the portion paid, with the rest granted only if the balance is paid in full within the discount deadline. The Help documentation recommends this setting when the invoice's terms are used. No cash discount rule for partial payments was found in the documents checked. A dunning key can cap the dunning level, so a residual item can, for example, be kept out of legal dunning or shown separately in the dunning notice.

One reason code can turn money owed into an expense

The field to watch most on the residual item screen is the reason code. If the code has the Charge Off indicator set, the difference does not become a new open item and goes to a separate G/L account instead. On the same Res. items tab with the same KRW 400,000, the customer balance can be KRW 400,000 or KRW 0 depending on the code. In the example, say the invented code Z01 has no indicator and Z02 has it. Under Z02, that KRW 400,000 is still owed, yet it has been written off as an expense. The partial payment description carries the same warning. The Help documentation says a difference posting must stay within the accountant's employee tolerance group.

Two cards. With Charge Off not set, a new open item for KRW 400,000 stays on the customer account, balance KRW 400,000. With Charge Off set, the invoice is cleared and KRW 400,000 goes to a separate G/L account as an expense, customer balance KRW 0.
The two outcomes of the Charge Off indicator on a reason code. The customer balance of KRW 0 in the red card is the case from the text, where money still owed disappears from the account.

The documents word it differently on whether a reason code is mandatory. "Partial Payments Versus Residual Items" says you must give a reason for a residual item, "Reason Codes" says you can enter your own text or use a predefined code, and "Reason Code" says a new open item results even when no code is entered. How this is enforced could not be confirmed, so check it on your system. A reason code can also decide the type of payment notice and whether an item is left out of the credit limit check.

Side by side

Collected point by point, the differences look like this.

Four cards. Original invoice: stays open with a partial payment, cleared with a residual item. Dates: with a partial payment the invoice's net due date goes into the payment's baseline date; a residual item takes terms from the invoice or a predefined key. Dunning: a partial payment joins dunning at that date; a dunning key can cap the level of a residual item. Cash discount: a setting grants residual items discount only on the paid portion, and no rule was found for partial payments.
The differences between the two methods, point by point. Compare the two lines in each card. The settings on the residual item side are in the customer or vendor tolerance group.

The documents checked for this note do not recommend either method. That a partial payment suits tracking by the original invoice number and keeping the existing due date, and a residual item suits new terms or a dunning limit on the rest, is this note's judgement drawn from the differences above. If your company has a collection rule, that comes first.

If you chose the wrong one, and other cases

To undo a residual item, use Document > Reset cleared items in the receivables, payables or G/L menu with the clearing document number. The line items lose their clearing data, and the change is logged in the change documents. You can decide whether to reverse the clearing document; if you do not, it also stays as an open item to be cleared with the others. In some cases (clearing in a third currency, clearing with exchange rate differences, documents posted with the net procedure) the system reverses it. This applies a procedure that Help describes for clearing documents in general to a residual item. What happens to the new item after the reset, and the order to follow if it has meanwhile been cleared by another payment, were not found in the documents, so check them on your system. A partial payment clears nothing, so this note's reading is that this menu does not apply to it. Help's Document Reversal page lists conditions for reversing a document, among them that it contains no cleared items. Reversing the payment document is therefore worth a look, but that page does not discuss partial payments directly, so check it on your system.

When the payment is in a currency other than the invoice's, there is a separate path. Residual Item Posting in Invoice Currency posts the residual item again in the currency of the original invoice, and it requires EA-FIN to be activated and a document type to be defined. In S/4HANA, the apps Post Incoming Payments, Clear Incoming Payments and Reprocess Bank Statement Items also support both methods, and Manage Customer Line Items (F0711) shows the open items. The Help examples say that selecting Use Invoice Ref. in the Edit Options for Journal Entries app links the partial payment to the original item, so check this option if you work in the apps. On the vendor side, F-53 is the entry path, and the residual item description mentions the vendor tolerance group. Help's comparison examples are customer-based, though, so confirm before carrying the above over to vendors unchanged.

When a payment falls short, check two things before the balance: should the original invoice stay open, and does the reason code you chose have Charge Off set? The first answer settles the open lines and dates. The second settles whether the KRW 400,000 stays on the customer account.

THE END
RSS feedBack to the library
COMMENTS BOX

Add your perspective.

Share a question, another approach, or something you have tried.

Newest first

Checking sign-in…

Loading comments…