Skip to content

Mixed A/P Account Rule

The Mixed A/P Account rule flags vendor payments that apply to documents posting to more than one Accounts Payable (A/P) account. NetSuite doesn't allow this — a VendorPayment supports a single header A/P account — so a mixed-A/P vendor payment will fail on push.

The push error

If a mixed-A/P vendor payment reaches a push attempt, the push fails with an error like this on the vendor-payment record in SuiteMigration:

Push Error banner shown on a vendor-payment record in SuiteMigration

In NetSuite a VendorPayment has one header A/P account, and it can only apply to bills and journal entries that post to that same A/P account. That single header field is set on NetSuite's Make Payment screen:

NetSuite Make Payment screen with the A/P Account field highlighted

A concrete example

Here's what a flagged vendor payment looks like in SuiteMigration. The Related Transactions section on the record lists the two applied documents, each posting to a different A/P account:

Related Transactions on a vendor-payment record showing two applied documents with different A/P accounts

Because the vendor payment applies to both documents, and each posts to a different A/P account, NetSuite rejects the push with the "applies documents posting to multiple A/P accounts…" error shown above.

How to fix a flagged vendor payment

The fix has to happen in the source system. Split the mixed vendor payment into separate vendor payments in QBO — one per A/P account.

  1. On the flagged vendor-payment record in SuiteMigration, click Open in QuickBooks Online.

    Open in QuickBooks Online button on the vendor-payment record

  2. In QBO, delete the existing bill payment.

    Delete the existing bill payment in QBO

  3. Create a new Bill Payment in QBO applying only the documents that share the first A/P account.

    First replacement Bill Payment in QBO — single A/P account

  4. Create a second Bill Payment in QBO for the remaining document(s) that share the second A/P account.

    Second replacement Bill Payment in QBO — the other A/P account

  5. In SuiteMigration, open the source connection and click Resync Data. This triggers a full sync so the deleted payment drops off and the two new vendor payments land.

    Resync Data button on the source connection page in SuiteMigration

  6. Re-run the Migration Readiness Audit. The rule should now show Passed for these payments.

    Migration Readiness Audit run showing the rule Passed

  7. Push again. The two new vendor payments should now succeed.

The customer-payment side of this same story is the Mixed A/R Account Rule. It uses the same logic against A/R accounts (invoice/credit-memo headers plus A/R lines on JEs, checks, cash expenses, and credit card charges/refunds) — with one extra requirement: the Default A/R Account project setting has to be set before the rule can run.