Prevent NetSuite sync failures caused by mandatory custom fields
NetSuite lets you make almost any field mandatory, including custom fields. That flexibility is great for your internal process, but it creates a challenge for the Re-Leased sync. When NetSuite requires fields that Re-Leased doesn’t send, the sync fails.
Understand the limitation and remove blockers
Re-Leased supports a defined set of standard NetSuite fields. It does not have visibility into your unique customisations or form-level rules. If a field is mandatory in NetSuite but not supported by the Re-Leased integration, Re-Leased cannot populate it and the sync will fail.
Important: This applies especially to fields made mandatory on specific forms and to fully custom fields.
Apply immediate safeguards to avoid failures
Use these quick checks to keep your sync stable and predictable:
- Ensure mandatory fields in NetSuite are also supported fields in Re-Leased.
- Avoid making non-standard or custom fields mandatory on forms used by Re-Leased transactions (for example, vendor bills, customers, invoices).
- Ask your NetSuite administrator to set default values for non-critical mandatory fields where needed.
If NetSuite requires a mandatory field that Re-Leased does not send, the sync will fail.
Set default values for unsupported mandatory fields
When a mandatory field is not supported by the integration, add a default value so NetSuite accepts the transaction without user input from Re-Leased. This lets the sync proceed cleanly.
Set the default at the NetSuite form level or field level so the required value is always present.
Use a dedicated NetSuite form for Re-Leased transactions
If you need certain fields to remain mandatory for internal workflows—but they are not necessary for invoices generated from Re-Leased—set up a separate form that Re-Leased uses. This form skips those mandatory rules.
- Open your usual form in NetSuite.
- Click Save As to create a copy of the form.
- In the copied form, mark the specific fields as non-mandatory.
- While editing the form, go to the Roles tab and set this version as the preferred form for the Re-Leased Integration Role.
- Save the form.
Note: Do not try to set this directly through the Role setup—the Re-Leased Integration Role is not editable.
After you save, Re-Leased will use this dedicated form for synced transactions. Your internal NetSuite users can continue using the main form without changes.
Identify supported fields for a successful outgoing sync
Use the mappings below to confirm which fields Re-Leased sends to NetSuite. Refer to these tables when reviewing your mandatory settings or creating default values.
Review invoice field mapping
Use this table to verify how invoice data maps from Re-Leased to NetSuite.
| NetSuite Field | Re-Leased Field |
| Identifier | External Entity Identifier |
| Customer | Contact |
| Transaction Identifier | Reference |
| Reference | Reference |
| Due Date | Due Date |
| Transaction Date | Issue Date |
| Sales Order Identifier | Sales Order Identifier |
| Item Lines | Line Items |
Review bill field mapping
Use this table to verify how bill data maps from Re-Leased to NetSuite.
| NetSuite Field | Re-Leased Field |
| Identifier | External Entity Identifier |
| Vendor | Contact |
| Transaction Identifier | Reference |
| Due Date | Due Date |
| Transaction Date | Issue Date |
| Sales Order Identifier | Sales Order Identifier |
| Item Lines | Line Items |
| Expense Lines | Line Items |
Review customer credit field mapping
Use this table to verify how customer credit data maps from Re-Leased to NetSuite.
| NetSuite Field | Re-Leased Field |
| Identifier | External Entity Identifier |
| Customer / Vendor | Contact |
| Transaction Identifier | Reference |
| Reference | Reference |
| Transaction Date | Issue Date |
| Item Lines | Line Items |
Review vendor credit field mapping
Use this table to verify how vendor credit data maps from Re-Leased to NetSuite.
| NetSuite Field | Re-Leased Field |
| Identifier | External Entity Identifier |
| Vendor | Contact |
| Transaction Identifier | Reference |
| Transaction Date | Issue Date |
| Sales Order Identifier | Sales Order Identifier |
| Item Lines | Line Items |
| Expense Lines | Line Items |
Review item line mapping
Use this table to confirm how item line details map between systems.
| NetSuite Field | Re-Leased Field |
| Description | Description |
| Item | Account |
| Tax Code | Tax Type |
| Quantity | Quantity |
| Rate | Unit Amount |
| Location | Location |
| Classification | Classification |
| Department | Department |
Review expense line mapping
Use this table to confirm how expense line details map between systems.
| NetSuite Field | Re-Leased Field |
| Description | Description |
| Account | Account |
| Amount | Quantity * Unit Amount |
| Location | Location |
| Classification | Classification |
| Department | Department |
Review customer record mapping
Use this table to confirm how customer records map from Re-Leased to NetSuite.
| NetSuite Field | Re-Leased Field |
| Entity Identifier | Display Name |
| Company Name | Correspondence Name |
| Subsididiary | External Customer ID |
| First Name | First Name |
| Last Name | Last Name |
| Email Address | Email Address |
| Fax | Fax Phone |
| Mobile Phone | Mobile Phone |
| Phone | Default Phone |
Review vendor record mapping
Use this table to confirm how vendor records map from Re-Leased to NetSuite.
| NetSuite Field | Re-Leased Field |
| Entity Identifier | Display Name |
| Company Name | Correspondence Name |
| Subsididiary | External Customer ID |
| First Name | First Name |
| Last Name | Last Name |
| Email Address | Email Address |
| Fax | Fax Phone |
| Mobile Phone | Mobile Phone |
| Phone | Default Phone |
Regional Terminology Note: You’ll see Tax used in the tables above to match NetSuite field names. In many APAC/EMEA regions, you may refer to this as VAT or GST. We use APAC/EMEA terminology for consistency, while keeping NetSuite’s field labels where required. For a full list of regional variations, check the Regional Terminology Guide.