{"section":"known-issues","requestedLocale":"en","requestedSlug":"native-split-with-asymmetric-financial-charge-across-suborders-settles-less-than-the-invoiced-amount","locale":"en","slug":"native-split-with-asymmetric-financial-charge-across-suborders-settles-less-than-the-invoiced-amount","path":"docs/en/known-issues/Order Management/native-split-with-asymmetric-financial-charge-across-suborders-settles-less-than-the-invoiced-amount.md","branch":"main","content":"## Summary\n\nIn natively split orders (multiple suborders sharing a single payment transaction) paid in installments with a financial charge (interest), the charge can be applied through separate ChangeOrderV2 operations, one per suborder. When the resulting charge is **asymmetric** between suborders, the amount settled when the first suborder is invoiced can be **lower than the invoiced amount**. The remaining balance of the transaction may then fail to auto-settle repeatedly, leaving the transaction in `Settling`.\n\nThe settlement value is calculated by the Sales Order System (SOS), not by the payment provider. The calculation is expected to be correct only when the charge is symmetric across suborders.\n\nEngineering confirmed this is a bug. The fix requires a significant refactor of the proportional-value calculation, and there is no ETA at the moment.\n\n## Simulation\n\nThere's no easy way to reproduce the scenario.\n\n## Workaround\n\nThere is no workaround available."}