The linkages between QuickBooks objects are typically complex. Following explains one of those scenarios.
The objects are:
Vendor Credit (termed as “Bill Credit” in QuickBooks)
For testing purposes, a vendor named “New Vendor” is created in QuickBooks. Bill (99119911 of amount $1000) and Vendor Credit (11991199 for amount $400) are created for this vendor. Then a payment is made for this bill vendor based on the vendor credit.
This is how it looks it QuickBooks.
Now, let us see what is returned from the QuickBooks SDK for this data for each of the object calls.
The above XML is a part of the response that is received for the Bill request. It has the Vendor Credit and the BillPaymentCheck information.
2. Vendor Credit
This XML is a part of the Vendor Credit information received from the QuickBooks. It has the information about the bill with which it is linked and the affected amount.
This is the original BillPaymentCheck information that shows the bill, bill’s reference number and the check amount.
This object behaves exactly like BillPaymentCheck. As there is not Credit card payment made now, this is not shown.
Bill behaves as the master object that has all the information pertaining to the bill and its applied transactions.
Following can be inferred:
Bill has Vendor Credit and BillPaymentCheck Information.
Vendor Credit has the related bill information.
BillPaymentCheck has only the Bill Payment information.