Propagating Custom Field Values to Sales Invoices

Introduction

When you create a sales invoice from a sales order, custom field values should carry over automatically where the documents are mapped correctly. If a customer custom field is not appearing on the invoice, the issue is usually related to field mapping, document setup, or the source document chain used during invoice creation.

Issue description

This guide explains how to make sure custom field values from the Customer entity are propagated to Sales Invoices when the invoice is created from a Sales Order. It also covers related document setup for Quotes and Orders, plus email recipient handling for invoices that need to be sent to multiple contacts.

Signs

• A custom field appears on the Customer record but not on the Sales Invoice.
• The field is populated on some documents but disappears when the invoice is created from a sales order.
• Invoices sent by email do not reach all intended recipients.
• Custom values appear inconsistently across Quotes, Orders, and Invoices.

Basic troubleshooting steps

1. Confirm that the custom field exists on both the Customer entity and the Sales Invoice entity.
2. Check whether the Sales Order is created from a document that already contains the custom field value.
3. Verify that the field is included on related documents such as Quotes and Orders if your workflow uses them as source documents.
4. Review the document mapping or field propagation settings for the invoice creation flow.
5. Test the process with a new Sales Order to rule out legacy data or incomplete records.

Step-by-step instructions

Step 1: Add the custom field to all related documents

Make sure the custom field is available on every document in the workflow that needs to carry the value forward. In most cases, this includes Customer, Quote, Order, and Sales Invoice.

Step 2: Verify the source document used to create the invoice

If the invoice is created from a Sales Order, confirm that the Sales Order contains the expected custom field value. If your process starts from a Quote, ensure the Quote also includes the field so it can flow through the chain.

Step 3: Check field mapping or defaulting rules

Review the configuration that controls how values are copied from one document to another. If the field is not mapped, the invoice may be created without the customer value even though the field exists on the source record.

Step 4: Test invoice creation again

Create a new Sales Order and generate a Sales Invoice from it. Confirm that the custom field value appears on the invoice as expected.

Step 5: Configure multiple invoice recipients

For invoices that must be sent to more than one recipient, add the email addresses directly to the contact record or use the Copy to field in the email template. This helps ensure the invoice email reaches all required recipients.

Tips and best practices

• Keep custom fields consistent across all documents in the order lifecycle.
• Use clear field names so administrators can identify the correct mapping quickly.
• Test changes in a controlled environment before applying them to production workflows.
• If email delivery is part of the workflow, validate both recipient addresses and template settings.

Next steps

If the custom field still does not propagate after checking the document setup, review your workflow configuration, integration rules, or API mapping logic. You can also contact support with examples of the Customer, Sales Order, and Sales Invoice records involved.

Additional information

If your implementation uses custom automation, middleware, or ERP integrations, confirm that those systems are not overwriting the field during invoice creation. For complex workflows, document the expected field behavior for each step in the order-to-cash process.

Disclaimer

Configuration options may vary depending on your workflow, integrations, and product setup. If you are unsure which document mapping or email settings apply to your account, contact your administrator or support team for assistance.