NetSuite allows almost any field to be made mandatory, including custom fields. If a field is required in NetSuite but not supported by the Re-Leased integration, Re-Leased cannot populate it and the sync will fail. This article explains how to prevent those failures.
Quick Safeguards
Ensure mandatory fields in NetSuite are also fields Re-Leased sends (see mapping tables below).
Avoid making non-standard or custom fields mandatory on forms used by Re-Leased transactions (e.g. vendor bills, customers, invoices).
Ask your NetSuite administrator to set default values for non-critical mandatory fields where needed.
Set Default Values for Unsupported Mandatory Fields
When a mandatory field isn't supported by the integration, add a default value at the NetSuite form or field level so the transaction is accepted without Re-Leased needing to supply it.
Use a Dedicated NetSuite Form for Re-Leased Transactions
If you need certain fields to remain mandatory for internal workflows but they're not needed for Re-Leased-generated invoices, create a separate form that skips those rules:
Open your usual form in NetSuite and click Save As to create a copy.
In the copy, mark the relevant fields as non-mandatory.
Go to the Roles tab and set this form as the preferred form for the Re-Leased Integration Role.
Save the form.
Note: Do not try to set this via the Role setup — the Re-Leased Integration Role is not editable.
After saving, Re-Leased uses this form for synced transactions. Internal NetSuite users continue using the standard form.
Field Mapping: Invoice
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.
Field Mapping: Bill
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.
Field Mapping: Customer Credit / Vendor Credit
Customer Credit: Identifier, Customer/Vendor, Transaction Identifier, Reference, Transaction Date, Item Lines — all mapping to corresponding Re-Leased fields. Vendor Credit additionally includes Sales Order Identifier, Item Lines, and Expense Lines.
Field Mapping: Item Lines and Expense Lines
Item Lines: Description → Description, Item → Account, Tax Code → Tax Type, Quantity → Quantity, Rate → Unit Amount, Location → Location, Classification → Classification, Department → Department.
Expense Lines: Description → Description, Account → Account, Amount → Quantity × Unit Amount, Location → Location, Classification → Classification, Department → Department.
Field Mapping: Customer and Vendor Records
Both map: Entity Identifier → Display Name, Company Name → Correspondence Name, Subsidiary → External Customer ID, First Name, Last Name, Email Address, Fax, Mobile Phone, Phone → corresponding Re-Leased contact fields.