Combined payments, accounting and refunds

Invoice ownership and allocation

Invoices remain attached to the resident payer's billing account. One combined provider charge does not create a new billing account and does not move an invoice to a different user.

Journal entries and audit

Settlement is atomic. Either every component records its canonical mutation, balanced source-linked journal entry, and exactly-once audit, or none of those writes commit. Invoice, amenity, and event histories remain independently legible.

The provider processing fee posts once for the aggregate charge. It is not duplicated in each component JE.

Refunds

Refund the invoice, amenity, or event component through its normal domain workflow. Kore targets the exact component allocation, enforces its remaining principal cap, and preserves the other components.

Combined-payment refunds return component principal only. They do not return the resident card surcharge or reverse the provider's processing cost merely because one component is refunded.

A refund taken outside URBI

If a refund is issued against a combined payment somewhere other than URBI, the payment is left needing attention and an alert is raised for a person to pick up. It used to sit unnoticed.

No journal entry is posted for it automatically, and this is deliberate. A combined payment covers two or more obligations, and which one the refund applies to is a judgement, not a calculation. Open the payment, decide which component the money came back against, and refund that component through its normal workflow so the ledger records what actually happened.

Never create a compensating manual entry or charge the resident again while a captured bundle is processing.