NetSuite Invoice and Payment Sync Troubleshooting Guide

Overview

This troubleshooting guide helps you identify and resolve issues when specific invoices and associated payments fail to sync to NetSuite. It outlines common causes, verification procedures, and resolution steps to ensure your billing data flows seamlessly between Recurly Subscriptions and NetSuite. This guide applies to merchants managing active NetSuite billing integrations.

Issue Description

You may occasionally find that certain invoices or payments fail to sync, sync only partially, or remain stuck in a pending or failed state when sending data to NetSuite. This discrepancy can affect individual customer accounts or specific records, even when your other invoices and payments sync without any disruption.

Signs

• A specific invoice does not appear in NetSuite.

• An associated payment fails to sync or is missing from the invoice record in NetSuite.

• The sync log shows an error message for one record but not others.

• The invoice syncs perfectly, but the payment remains unsynced.

• Records remain stuck in a pending, queued, or failed status.

Basic Troubleshooting Steps

Before diving into deep configuration changes, review this initial checklist to eliminate common data oversight issues:

• Confirm that the invoice and payment meet the transaction rules required to be eligible for sync.

• Verify that the customer account, general ledger account, and payment method are mapped correctly in NetSuite.

• Check whether the invoice has already been synced under a different internal ID or external reference to prevent duplication.

• Review the sync status and specific error details for the affected records.

• Make sure all required data fields are fully completed on both the invoice and payment records.

• Confirm that the payment is linked to the correct invoice.

Diagnostic Tools and Resources

Use the following built-in integration utilities to pinpoint the root cause of the sync failure:

• Sync logs

• Integration error details

• NetSuite record search

• Field mapping configuration

Advanced Troubleshooting Steps

Step 1: Verify the invoice record in NetSuite

Search for the invoice in NetSuite using the invoice number, external ID, or customer reference. If the invoice already exists in NetSuite, confirm that it matches your source record precisely. Check that it is not closed, voided, or manually adjusted in a way that blocks incoming payment syncs.

Step 2: Verify the payment record and its relationship to the invoice

Check whether the payment is properly applied to the correct invoice and that the payment amount, currency, and date are valid for your active integration. If the payment is unapplied or linked to the wrong invoice, correct the source data in your billing dashboard and retrigger the sync.

Step 3: Review field mappings and required settings

Confirm that all required invoice and payment fields are mapped correctly between Recurly Subscriptions and NetSuite. Pay close attention to customer identifiers, subsidiary settings, account references, tax fields, and payment method mappings.

Step 4: Reprocess the failed sync

After correcting any data fields or configuration issues, re-run the sync for the affected invoice and payment. If your current integration setup supports manual reprocessing, use that option to send only the specific failed records.

Step 5: Check for duplicate or conflicting records

Look for duplicate invoices, duplicate payments, or records created manually in NetSuite that might conflict with the integration. Remove or reconcile these duplicates completely before attempting another sync.

Contact Support

If the issue continues after completing these steps, contact our support team. To help speed up our investigation, please provide the invoice number, payment reference, sync timestamp, and the exact error messages found in your sync logs.

Conclusion

Most invoice and payment sync issues can be resolved quickly by confirming record eligibility, verifying mappings, and checking for data conflicts in NetSuite. Use this guide as your primary reference whenever a specific transaction fails to sync.

Disclaimer

This guide is intended for general troubleshooting purposes only. Your specific implementation may include custom workflows or tailored settings that require additional review by a qualified system administrator.