Payment Sync keeps Bill payment status aligned between Procurify and NetSuite. It has two modes, and you can only use one at a time:
Push mode (default). When a Payment is recorded in Procurify, it is pushed to NetSuite and applied to the related Bill or Bills.
Pull mode. When a Bill is marked paid in NetSuite, Procurify reads the paid status on an hourly schedule and marks the Bill as paid in Procurify.
Push mode fits teams that make Payments from Procurify. Pull mode fits teams that continue to record Payments in NetSuite and just want Procurify to reflect the outcome.
Looking for setup? See NetSuite AP Integration Overview and Set Up for the initial connection. You can switch between Push and Pull mode from Settings → Integrations → NetSuite Request to AP under payments.
Prerequisite: Bills must be synced first
Payment Sync only works for Bills that have already synced to NetSuite through Bill Sync, regardless of which mode you are using. If a Payment refers to a Bill that has not yet synced, the Payment will fail. Check that every related Bill shows a successful sync status before troubleshooting the Payment.
Push mode: Procurify to NetSuite
When a Payment is pushed to NetSuite, Procurify sends the following:
Vendor from the Payment record in Procurify
Subsidiary for the Payment
Payment date
Payment account, taken from the GL Code on the Payment Method in Procurify. This is matched against the Number field on the corresponding account in NetSuite's Chart of Accounts.
Currency and total amount
Applied amount per Bill, so NetSuite records how the Payment is distributed across one or more Bills
The Payment appears in NetSuite as a standard Vendor Payment linked to the Bills it is applied to.
Paying multiple Bills with one Payment
If a single Payment in Procurify pays off more than one Bill, all of those Bills must already be synced to NetSuite. The Payment push includes the amount applied per Bill, so NetSuite records the split correctly.
Pull mode: NetSuite to Procurify
In Pull mode, Procurify checks NetSuite on an hourly schedule for Bills that have been marked paid. When a match is found, the Bill's status in Procurify updates to reflect the payment.
A few things to know about Pull mode:
Only matches Bills Procurify knows about. Bills created directly in NetSuite and never synced from Procurify are ignored.
Works across legacy and new integrations. If your Procurify instance was previously on the legacy NetSuite Bill Sync, Bills that were originally pushed through the legacy integration are still recognized when their paid status comes back from NetSuite.
No Payment record is created in Procurify. Pull mode only updates the Bill status. The actual Payment record lives in NetSuite.
Switching modes
You can switch between Push and Pull mode from the integration page. A couple of things to keep in mind:
Both modes cannot be active at the same time. Push mode creates the Payment record in NetSuite; Pull mode assumes the Payment record already exists there. Using both at once would either double-record or conflict.
Existing Payments are not migrated. If you switch modes, Payments that were already synced under the previous mode stay as they were. Only new activity uses the new mode.
Most teams pick a mode once during setup and stay on it.
What happens if a Payment fails to sync
When a Payment sync fails, the error appears on the Payment in Procurify. Procurify handles different kinds of failures differently:
Temporary issues, for example NetSuite briefly rate-limiting requests, are retried automatically with delays between attempts. You do not need to do anything.
Data issues, for example a related Bill that has not yet synced, are surfaced immediately without retry. These need to be corrected before the Payment can sync.
If you manually re-sync a Payment, avoid clicking Sync repeatedly in quick succession. Procurify treats rapid re-clicks within about 2 minutes as the same request to prevent duplicate Payments in NetSuite. Wait a couple of minutes between manual retries, or correct the underlying issue first.
Common errors and what they mean
If a Payment fails to sync, the error appears on the Payment in Procurify. The most common causes are:
Bill not synced. The Bill (or one of the Bills) the Payment is applied to has not been pushed to NetSuite yet, or failed to sync. Confirm every related Bill shows a successful sync status in Procurify, then re-sync the Payment.
Payment account not found. The GL Code on the Payment Method in Procurify does not match any active account Number in NetSuite's Chart of Accounts. Check the GL Code on the Payment Method and confirm the matching NetSuite account is active and has a Number set.
Sync could not complete. A generic push failure that usually means a related record (the Bill or its vendor) is missing its link to NetSuite. Re-syncing the related Bill first often clears this, after which the Payment can be re-synced.
Once the underlying issue is corrected, re-sync the Payment from the Payments page.