<aside> 💡 If you want to bill the parent customer in a parent-child hierarchy, see Parent + Child invoice schedules instead.

</aside>

<aside> 🧩 This feature requires custom mappings. Please contact our Data Solutions team if your billing process requires this workflow.

</aside>

There are situations when you have your contracts (transactions) agreed with your customers, but for tax, legal or other reasons the invoices need to be sent to a separate entity, that is not your customer and it’s not represented in your parent-child hierarchy in Subscript or in your CRM. One example is a legal entity created to develop a project, for instance.

Subscript allows you to do that, with specific custom configurations. Please contact our Data Solutions team to help configure this properly to you. If you already have this configuration set up, this is how you’ll bill this separate entity:

1. Create a customer record with the exact same name as the entity you want to bill, and with all the information you need to show in your invoice: bill-to email, entity name, address, and tax ID. This customer record won’t count as a customer for any purposes in Subscript, it’s just a placeholder for the bill-to information mentioned above.

2. In the transactions that you need to bill to this entity, add this entity name in the field customized for you for that. Usually it’s called Bill-to customer, Bill-to entity, or something similar.

Metadata field in the transaction pointing to the entity to be billed. This does not impact your metrics or accounting reports.

1. When you start to create the invoicing schedule, you’ll see the entity will be pulled as a customer, instead of the customer for that transaction. The email address in the invoice will also be from this entity.

<aside> ⚠️ Note: the names between the metadata field and the customer record for the entity must be an exact match.

</aside>

What this configuration impacts:

• Your invoices for these transactions in Subscript will be associated with the entity, not with the actual customer
• If you use a General Ledger (Quickbooks, Xero, Netsuite), the invoices will be pushed to this entity as it was the customer
• The bill-to section in the invoices will use the entity name, address and other details
• The invoices will be sent to the email configured for the entity
• All revenue reports will take into account the actual transaction customer
• The accounting reports will list the actual transaction customer, and will take into account the invoices created