如何在Quickbooks Web Connector中添加未核销付款？

Got it, I’ve run into this exact issue before—creating unlinked customer prepayments works seamlessly in the QuickBooks desktop client, but the Web Connector throws fits if you don’t nail the QBXML request structure. Let’s walk through the solutions step by step:

1. Use the Correct QBXML PaymentAdd Request (No Linked Transactions) #

The key mistake most people make is either including auto-apply logic or accidentally linking the payment to an existing transaction. Here’s the exact request you need:

• Set <IsAutoApply>false</IsAutoApply> to prevent QuickBooks from auto-matching the payment to open invoices.
• Do NOT include any <AppliedToTxnAdd> nodes—these are what link the payment to specific transactions.

Example QBXML:

<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="13.0"?>
<QBXML>
  <QBXMLMsgsRq onError="stopOnError">
    <PaymentAddRq requestID="1">
      <PaymentAdd>
        <CustomerRef>
          <FullName>Acme Corp</FullName>
        </CustomerRef>
        <TxnDate>2024-05-20</TxnDate>
        <TotalAmount>1500.00</TotalAmount>
        <PaymentMethodRef>
          <FullName>Wire Transfer</FullName>
        </PaymentMethodRef>
        <IsAutoApply>false</IsAutoApply>
        <!-- Critical: No <AppliedToTxnAdd> sections here -->
      </PaymentAdd>
    </PaymentAddRq>
  </QBXMLMsgsRq>
</QBXML>

2. Verify QBXML Version & Web Connector Permissions #

• QBXML Version Check: The <IsAutoApply> node was introduced in QBXML version 13.0 (QuickBooks 2019 and later). If you’re using an older version, you’ll need to omit this node entirely and just avoid adding any <AppliedToTxnAdd> entries.
• Web Connector Permissions: Make sure your Web Connector application has been granted full access to create customer payments (check the authorization settings in QuickBooks under Edit > Preferences > Integrated Applications).

3. Troubleshoot with Web Connector Logs #

If the sync still fails, pull up the Web Connector logs (click View Log in the Web Connector interface) to see the exact error message. Common issues include:

• Invalid customer name in <CustomerRef> (QuickBooks is case-sensitive here)
• Accidental inclusion of <AppliedToTxnAdd> nodes
• QBXML version mismatch causing unrecognized nodes

4. Alternative: Use CustomerDeposit for Prepayments #

If you’re still having trouble with PaymentAdd, consider using the CustomerDepositAdd request instead. This is explicitly designed for unlinked prepayments and avoids any auto-apply logic by default:

Example QBXML:

<?xml version="1.0" encoding="utf-8"?>
<?qbxml version="13.0"?>
<QBXML>
  <QBXMLMsgsRq onError="stopOnError">
    <CustomerDepositAddRq requestID="2">
      <CustomerDepositAdd>
        <CustomerRef>
          <FullName>Acme Corp</FullName>
        </CustomerRef>
        <TxnDate>2024-05-20</TxnDate>
        <TotalAmount>1500.00</TotalAmount>
        <PaymentMethodRef>
          <FullName>Wire Transfer</FullName>
        </PaymentMethodRef>
      </CustomerDepositAdd>
    </CustomerDepositAddRq>
  </QBXMLMsgsRq>
</QBXML>

This will create a prepayment that sits in the customer’s account as an unapplied credit, just like the manual client operation.

内容的提问来源于stack exchange，提问作者Scottie