Small and medium business | Business Central, N...

Unapplying Payments

(4) Share

Report

Posted on by rcboiler

1,290

The standard unapply feature in BC unapplies all records from a payment. Not an issue when it is 1:1 but sometimes the client just wants to unapply one invoice and leave the rest applied. not an option. we have a client that does enough of these (and with large number of applied invoices) that the standard BC process will be super time consuming and open to errors. Is there a workaround (or an extension) that allows this single unapply actions in these situations?

Categories:

Dynamics 365 Business Central

All responses (5)

Answers (0)

Sort by

Suggested answer

YUN ZHU 103,085 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

As far as I know, this cannot be done using standard functionality; you can submit this idea to Microsoft.
Missing a feature? Post or vote for ideas on: aka.ms/BCIdeas

Thanks.
ZHU
Suggested answer

AndrewThomas81 2,717 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Applications have to be completely unapplied as standard, I'd investigate why entries are being unapplied regularly and fix the root cause if possible

Kind Regards

Andrew Thomas FCCA MCP
YouTube - Use Business Central
LinkedIn
Suggested answer

OussamaSabbouh 19,350 Super User 2026 Season 2 on at

Like (1)

Report
Copy link

Link copied!

Hello rcboiler,
This is essentially a standard Business Central limitation: if one payment was applied to multiple invoices in the same application posting, Unapply reverses that application as a whole, so you cannot simply select one invoice from that group and leave the others applied; you can check Customer Ledger Entries → Detailed Ledger Entries → select the relevant application entry → Unapply Entries, which can help when the payment has been applied through separate application postings, but Microsoft also states that the latest application must be unapplied first. For your current scenario, the standard approach is therefore to unapply the payment and reapply it to the invoices that should remain matched; for future transactions where this happens frequently, applying/posting invoices in smaller separate application groups can make corrections easier. If the volume makes this impractical, an extension is reasonable, but it should use BC's standard application/unapplication posting logic rather than modifying Customer/Detailed Customer Ledger Entries directly.
Regards,
Oussama Sabbouh
Suggested answer

Grigorios Mavrogeorgis 3,363 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Hi, it's all or nothing, and it goes by the application transaction, not the payment. So whatever was applied in one posting comes off together, discounts and currency gains included.
Easier fix is upstream. If they apply invoices one at a time from the ledger entries instead of ticking twenty at once, each one is its own transaction and you can unapply just that one later. For the old ones already applied together there's nothing, unapply and reapply.
Custom code for this I'd avoid, too easy to break the ledger.
Glad to help - follow up if anything is unclear.
► If this solved it, marking it verified helps others too.
Regards,
Grigorios Mavrogeorgis
Business Central Consultant & AL Developer
Work: Gmsoft Limited
Blog: insidebusinesscentral
LinkedIn: linkedin.com/in/gregorymavrogeorgis
Suggested answer

Simon Kimani 174 on at

Like (0)

Report
Copy link

Link copied!

@rcboiler
This is not possible in standard Business Central. Transactions with the same transaction number can only be unapplied together. The alternative is to use a customization, and Acumens Receivables and Collections Management provides this capability. You can select the specific entries to unapply, and only those selected applications are unapplied, leaving the other records intact.
Check it here: https://acumens.com/Blog/acumens-receivables-collections-business-central/#partial-unapply