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?

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.

Table information is available to you in the Information Center > Resources > File Layouts and Program Information.  Choose File Layouts under Contents.  Choose the table name and the table information will display.  You posted "I wish I new what the AP_TransactionPaymentHistory CheckType letters meant", that is answered in the file layout.

Under NO circumstances should you attempt to import into that file to mark invoices as paid. You would be in for a world of hurt.  You should use some type of transaction entry such as manual check entry and then post. This insures that ALL tables that are effected when an invoice is paid are written out to correctly.

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) 

Thank you.  I overlooked this information.

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.

So if I import payments into AP_ManualCheckHeader, I should then be able to use  Manual Check Entry to post the payments?

Or are you saying I should NOT import payments at all?

(Thank you guys for you help BTW).

Yes, you do post that way.  Imports should replace manual data entry, not bypass programmed business object processes. 

Importing to the data entry tables is normal activity.  If you don't know what data entry table is appropriate, just ask, explaining the business problem you want to solve. 

Start with a technical question, and you may be lead further in the wrong direction.

When I try to import my AP_ManualCheckHeader I keep getting an error that the header record is not in an editable state.

All of the fields pass.  Should I create a Sage case?

Create a transaction manually and look at all the fields with values (some of which are auto-filled... like Payment Type).  Make sure every required field is part of your import job.