AP_TransactionPaymentHistory     would be a good place to start      

Thank you, yes I do see payments in AP_TransactionPaymentHistory with TransactionType = P

Odd that ApplytoInvoice is null yet I see the payment applied.

It must be applied based on merely the fact that the Invoice numbers between Type=I and Type=P are the same.

Working on my Sage Visual Integrator job to mark these invoices as paid.

I guess I will start trying to import payments into AP_TransactionPaymentHistory.

I wish I new what the AP_TransactionPaymentHistory CheckType letters meant.   

Is there any schema or table structure documentation for VI import jobs that you know of, or trial and error?

If you are trying to record in Sage 100, payments processed outside of Sage100, you probably want to do your import to AP_ManualCheckHeader.  Then post normally.

If you are trying to record in Sage 100, payments processed outside of Sage100, you probably want to do your import to AP_ManualCheckHeader.  Then post normally.

Yes trying to import outside invoices/payments into Sage 100.  (Payments from our credit card vendor export.)  I can import the credit card transactions as invoices and tie them to the correct vendor no problem with this little Access Database I made to match them.

Thanks!  I will try importing with the Visual Integrator to the AP_ManualCheckHeader table instead. 

(I have been having difficulty getting the payment to apply when sending it to AP_TransactionPaymentHistory) 

As BigLouie stated, don't ever try to bypass Sage 100 business objects and edit data through back end methods (like importing directly into AP_TransactionPaymentHistory).  Only import into a data entry function (like manual check entry), and use normal processing for things to be posted properly.