E-Document References Now Supported on Invoices and Credit Memos

What changed

A new Document Reference mechanism has been added to invoices and credit memos to satisfy e-document formats that require cross-referencing between transactions. Typical use cases include:

• A corrective invoice referencing the original invoice.
• A final invoice referencing a prepayment invoice.

The feature surfaces on the Invoice Configuration subtab of the invoice or credit memo record. Clicking New Document Reference exposes two fields:

• Reference Transaction — a filtered list showing only invoices and credit memos that share the same subsidiary and customer as the parent transaction.
• Link Transaction Relationship Type — classifies the nature of the link (e.g., corrective, prepayment). The exact enum values are not documented in this source; inspect the field in the UI or via N/record to enumerate available options.

Multiple document references can be added to a single parent transaction.

Technical notes

The source does not specify the internal sublist ID, field IDs, or whether this sublist is scriptable via SuiteScript. If you need to automate document-reference creation (for example, during bulk e-invoice generation), verify the following:

• Whether the sublist is exposed on the record object returned by record.load({ type: record.Type.INVOICE }) or record.Type.CREDIT_MEMO.
• The internal IDs of the Reference Transaction and Link Transaction Relationship Type fields — use the record browser or record.getSublistFields() against the Invoice Configuration subtab.
• Whether the sublist supports insertLine/setSublistValue in standard and dynamic mode.

The subsidiary-and-customer constraint is enforced at the UI level; it is unclear whether the same validation fires server-side on record.save(). Test accordingly if scripting references.

What to do

1. E-document users: If your country-specific e-invoicing format (e.g., PEPPOL, FatturaPA, UBL) requires references between documents, use this feature instead of custom fields or workarounds. Review whether your existing SuiteApp or bundle already populates these references automatically.
2. Script developers: Open an invoice in the record browser (or call record.getSublistFields) to discover the sublist and field IDs. Confirm scriptability before building automation.
3. Admins: No migration needed. The feature is additive. If roles accessing invoices or credit memos have restricted sublists, verify that the Invoice Configuration subtab and the new Document Reference sublist are visible in relevant custom roles.