Every customer payment applied in Cash Receipts Entry

It is applied at zero and named on the draft as unverified, rather than having cash applied to it. The same holds for the payer: a tax identifier that matches no customer leaves the draft with no customer selected and a record that the lookup ran and found nothing. Processing stops before any write when the customer, the deposit bank account or the amount is missing.

In Cash Receipts Entry, as a receipt with one line per invoice applied, inside a cash group. Fluent populates the customer and the currency through Epicor's own entry calls, the way the Kinetic screen does, so the amounts and the exchange rate are Epicor's rather than ours. The group is created but left unposted: posting stays inside Epicor, with a person.

Both directions are handled. Each invoice takes the smaller of what the document asked for, the balance Epicor still shows open, and what is left of the payment, so a short payment closes what it covers and leaves the remainder open. Whatever is left after the last invoice stays on account and is shown on the draft as unapplied, rather than being forced onto an invoice that never asked for it.

No. Every run ends in a draft carrying what it could not settle: a payer whose tax ID matched no customer, an invoice Epicor reported as missing or already closed, a check matched on amount alone, a deposit account nobody has chosen yet. A person edits the draft and presses Process, and only then does anything reach Epicor.

The currency printed on the payment wins over the customer's default in Epicor, and only document-currency fields are written, with the rate group on the header so Epicor derives the base-currency amounts itself. There is no exchange-rate arithmetic on Fluent's side. Withholdings are kept as their own lines and close invoices alongside the cash instead of counting as cash.