Hi, 

I will explain how the NA Credit card interface solution works.   

When we have a credit card customer order, at delivery (or invoice depending on options) IFS sends a message to the credit card partner (processor) and if the CC was good IFS creates a customer check record and a payment on account. At that moment a customer order invoice is unpaid. A background job is run that creates an offset that essentially moves the payment on account to be a payment on that customer order invoice.  At that time, the invoice should be paid (typically).  At this time the customer check is still not cashed. 

At some future point in time (when cash is deposited) some user option cashes the checks.  IMO the best way to cash the checks is the check cashing proposal.  The check cashing proposal simply sets the checks as cashed it has no connection with the invoice / payment on the invoice. 

What you describe is different from my experience with the NA credit card interface. Have not tested IFS Cloud 24R1, but if you're talking about the exact same functionality, something is clearly different. 

You may want to double check. 

Anyway, the check cashing proposal had always been a user activity with user selections and had no effect on invoice payment status.   Check the background jobs for the offset. If the offset fails, the invoice will not flow to paid. 

Best regards, 

Thomas