Stores the payee's compliance-entity source preference. Omit to leave the stored value unchanged. PayerProvided requires the linked payer Account to have a ComplianceEntity and PayeeProvided requires payeeSuppliedComplianceEntityId; otherwise 422 payments.PinnedComplianceEntityMissing.

Client-administered policy naming which side's collection funding configuration is authoritative after the Payer links. While unlinked, the Client-supplied configuration is authoritative. AlwaysPayeeAccountSupplied and AlwaysPayerAccountSupplied consult only the named side; PreferPayerAccountSupplied consults the Payer-supplied configuration first and falls back to the Client-supplied configuration when absent. The fallback unit is the indivisible funding-authorization pair, never a per-field merge, and revoked authorization is invalid under every value. This selector does not enable invoice auto-pay. While unlinked, collection uses Payer.isAutomaticInvoiceCollectionEnabled; linked-payer auto-pay uses Payee defaults or PayeeEngagement overrides. Changes apply to new collections only; in-flight reservations keep their snapshotted pair.

Bind a payee-owned ComplianceEntity whose subject is exactly {type: Payer, id: <this Payer id>}.

The AccountingCustomer.id from listAccountingCustomers to map this Payer to. Empty string clears; omitted leaves unchanged. This is a Wingspan normalized reference id, not the QuickBooks-native id.

The AccountingItem.id from listAccountingItems to use as the default line-item mapping for invoices to this Payer. Empty string clears; omitted leaves unchanged. This is a Wingspan normalized reference id, not the QuickBooks-native id.

Optional idempotency token for authenticated POST and PATCH requests. Reusing the same key and body returns the cached response for 24 hours, except credential operations that explicitly document a 409 because one-time secret material is never cached; reusing it with a different body returns 409 IdempotencyKeyConflict. Use 1-255 printable ASCII characters.

Select the Account for an Account-scoped operation. A direct ServiceAccount API key MUST supply this header, and the target must be within the ServiceAccount owner's or Authorization grant's Account boundary. A Person bearer may select an Account on which it has an active Stakeholder, and an Account session may select its bound Account (or a descendant only when the session explicitly includes descendants).

Generated from available response content types