This feature is only available to customers on the Elite subscription plan. To request to upgrade to this plan, please reach out to your Recurly account manager or [email protected] for more details.
By setting up your business entities on one Recurly site, you can guarantee that all of your customers receive the appropriate invoice treatments. Origin tax is calculated based on your precise business address, so ensuring each of your entities’ unique business addresses are configured for transaction tax calculation ensures greater tax precision and compliance. This setup not only makes scaling your business more efficient but also simplifies maintenance. You can create as many entities on your Recurly site as needed, updating, removing, and adding entities as your business needs change.
● Each entity receives accurate tax treatment based on its specific business address.
● Seamless integration of business entities with customer accounts, facilitating automatic tax calculation.
● Flexibility to add, remove, and update business entities as your business evolves.
● Automated assignment of tax entities based on customers' billing addresses.
● Transparency in transactions and subscriptions to identify which entity is associated with a transaction.
● Ability to file taxes by each unique business entity for merchants with a direct integration to Avalara
Automatic assignment is the default method of entity application to invoices for all customers at the time of their next subscription transaction. This assignment is based on the billing address of the customer's account at the time the transaction takes place. If a customer has manual billing set up, or if your site is configured to use the account address for all invoices, then the account address will be used as the "BILL TO" address on the invoice.
The logic behind the automatic assignment of entities from the "BILL TO" address of a customer is based on the entity's configured subscriber locations. These locations are an optional configuration setting on alternate business entities. You can add specific countries to the entity to create rules for automatic assignment. Each unique country can only be added to a single Subscriber Location/entity at a time. You can adjust the countries within your Subscriber Locations at any time, but changes will reconfigure the entity assigned on any transaction if a customer's country location matches a country that has been moved to a new entity.
If you choose not to add any regions to any or all of your alternate entities' Subscriber Locations, all customers will be "automatically" assigned to the Site Default Entity, which serves as the site's fallback entity for assignment.
For example, if you create an entity called "Acme Inc. Western Europe" and add Germany, Italy, France, Spain, Ireland, and England to its Subscriber Locations, customers whose "BILL TO" address is in one of those countries will receive the "Acme Inc. Western Europe" entity's invoice address settings and origin tax address.
If you set up another entity called "Acme Inc. Eastern Europe" with Poland and Hungary in its Subscriber Locations, customers with a billing address in these two countries will automatically have the "Acme Inc. Eastern Europe" entity applied to their invoices.
If your headquarters serves customers globally, you can set it up as your Site Default Business Entity on Recurly, which will serve as the fallback entity for customers who are not covered by a subscriber location within another entity.
You can view this information on the "Subscriptions" page under the "Customers" section or on a customer's account. This view will display the corresponding entity on each transaction associated with their billing address at a given point in time. You can also use an API query on the Invoice object to identify which entity was associated with a specific invoice.
If you prefer static assignments at the ACCOUNT level over the dynamic approach at the SUBSCRIPTION level for customer accounts, you can opt to apply an overriding entity to a customer's account(s).
Tip: If you are integrated with NetSuite, Recurly recommends applying entities at the ACCOUNT level rather than relying on automatic assignment. This approach ensures that entity mapping for customer accounts remains consistent between Recurly and NetSuite, as entities are mapped at the time a customer is created on NetSuite.
You can apply an overriding entity at the ACCOUNT level either via the admin console or API V2/V3. If you apply an overriding entity to an account, you can do an API call to see what entity an account is assigned to. Accounts using automatic assignment will have entities applied at the subscription level, making the detection of entities used for transactions a bit more complex.
To apply an overriding entity via the Recurly user interface, navigate to a specific customer account, go to the Edit Account Information page, and select an "Overriding Business Entity" from the dropdown menu provided in the field.
Once you save the changes made to the selected customer account with an overriding business entity, all future transactions of that account will be assigned to the corresponding business entity. This assignment persists until you either change the overriding entity or revert that account back to automatic assignment logic applied at the subscription level. Remember, the assigned overriding business entity will be applied at the start of the next billing cycle once your changes have been applied to the account. You cannot switch a customer’s business entity mid-billing period.
You can see the business entity assigned at the account level for customers with an overriding business entity applied directly on their account page, under "Account Information". You can also do an API query on the Account object to identify which entity is associated with an account, or, for accounts using automatic assignment, an API query on the Invoice object to see which entity was applied to a specific invoice.
If you have customers with a parent/child account hierarchy, the application of business entities for transactions depends on the billing preferences of the parent/child relationship.
● If the "Bill all charges to Child Account" option is selected for an account, each child account in a given hierarchy will receive its own invoices. They will thus follow the same entity assignment behavior explained above—either automatic assignment based on Subscriber Location at the subscription level, or an account-level overriding entity applied so all transactions for that customer occur under the overriding entity.
● If the "Bill all charges to Parent Account" option is selected for an account, invoices from a child account's charges sent to the given parent account will be assigned to whatever entity is assigned to the parent at the account level if an overriding entity is set, or will assume the entity from automatic assignment based on the parent account's "BILL TO" address.
Refunds are inevitable. Whether a customer's entity is assigned at the subscription level using automatic assignment, or at the account level with an applied entity override, refunds work the same way.
When a customer makes a purchase, the entity assigned at the time of the transaction is considered the original entity. If a customer requests a refund and the entity assigned to their transactions or account has changed since the original purchase, the refund invoice will use the original entity's invoice display information and tax address. This process ensures the correct tax calculation for the refund and maintains invoice consistency with the original entity name and address.
You cannot delete your Site Default Entity from your Recurly site. The Site Default Entity is critical in communicating your company's customer-facing information during the invoicing process. While the SDE cannot be deleted, it can be edited.
However, you can delete any alternate entity set up on your site at any time. You can delete an alternate entity from the main list page when hovering over the ellipses for the entity of choice and selecting “Delete”, or by selecting "Delete Entity" from the "Entity Actions" dropdown on the view-page of a specific alternate entity.
When confirming to delete an alternate entity, you will be prompted to enter the entity code of the one you are attempting to delete. Once you enter the code successfully, that entity will be permanently deleted from your site. However, if a return is initiated, the refund invoice will still leverage the display and tax address information from the original transaction.
Once you delete an alternate entity, all customers previously assigned to that specific entity as an overriding entity on their account will have their invoices assigned to the Site Default Entity moving forward, unless:
● The customer's "BILL TO" address is changed to match a country included within the Subscriber Location on another alternate entity.
● The countries included in the deleted entity's Subscriber Locations are added to another alternate entity.
● The customer is manually reassigned to a specific entity at the account level (overriding business entity).
Tax ID Numbers (TINs) are entity-specific and used to display a business's tax registration number on invoices sent to customers. When a Default TIN/VAT number is entered on an entity, that number will appear as the last line in the merchant information shown on the invoice.
Country-specific TINs replace the Default TIN/VAT number on the invoice when a customer's BILL TO address is located within a country that has a country-specific TIN configured on the given entity.
For example, if a merchant has a Default VAT number set on an entity and also has a country-specific VAT number configured for Portugal on that entity, then all customers with BILL TO addresses in Portugal will see the French merchant VAT number on their invoices instead of the merchant’s Default VAT number. Alternatively, if there are no other country-specific VAT numbers added to that entity, all customers leveraging that entity with BILL TO addresses in any country OTHER than Portugal will see the merchant’s Default VAT number on their invoices.
TIN/VAT numbers will not automatically be applied across entities on Recurly. If you use the same TIN/VAT numbers across multiple entities, you need to ensure that you fill out those fields with the appropriate tax registration numbers for each entity.
If you have an integration to a direct Avalara account, you can map each of your entities from Recurly to your direct AvaTax account to report and file taxes independently for each unique entity. While Recurly only supports one unique Avalara account on a single Recurly site at a time, we provide multi-entity tax support by allowing you to map your Recurly Site Default Entity to your Avalara main company, and each alternate entity on Recurly to the corresponding sub-entities configured on your single Avalara account.
On your Avalara site, from your home page, you will see the list of companies/sub-companies within your account. Copy the unique Company Code exactly as it appears on your Avalara site, and paste it into the appropriate Company Code field in the Recurly App on the "Avalara AvaTax Settings" page to create a direct mapping for each Recurly entity to each Avalara company you manage.
If you delete an entity on Recurly, that mapping will no longer exist for the corresponding sub-company in Avalara. Maintain the mapping relationship between the two sites to ensure entity mappings are up-to-date if your entities change.
If a customer's subscription is paused, resuming the subscription or an immediate change made to the subscription will trigger a new billing period. The subscription will no longer be paused, and the next invoice will be assigned to the entity assigned to the customer's account if an overriding entity has been applied. Otherwise, the invoice will receive the entity based on the subscriber location or the Site Default Entity if using automatic assignment logic.
If you started on a Recurly Elite plan and then decide to move to a Recurly Starter or Professional plan, you will lose the ability to maintain multiple business entities on your site once your downgrade takes effect. Historic invoices leveraging various entities will remain unchanged, and refunds for invoices leveraging previously maintained alternate entities will still reflect the original entities applied. However, all invoices and transactions moving forward will be assigned to your Site Default Entity. All renewal, manual, immediate change, and one-time-charge invoices moving forward will receive the SDE assignment and treatments.
Should you decide to re-upgrade to an Elite plan at a future date, you will need to recreate alternate entities.
Q: Can other Recurly objects, such as plans, coupons, and email templates, be entity-specific?
A: Not at this time. However, we are continually exploring additional areas where we can enhance multiple business entity support and success and are always eager to hear your feedback!
Q: Can purchases made from a given entity be routed to a specific payment gateway?
A: This is not available through the UI. However, you can set a specific payment gateway at both the Subscription and Account levels, and thus route a given subscription to the preferred gateway.
Q: Can I file my taxes within Avalara by the specific entity I have set up on my Recurly site?
A: Yes, this is possible for merchants with a direct Avalara account set up. You will need to configure the integration within your Recurly site to ensure entity/company codes are mapped appropriately, allowing for entity-specific filing in the Avalara system.
Q: Does this feature work with Recurly revenue recognition?
A: Yes, the multi-entity feature is compatible with Recurly revenue recognition. Please note that if you enable Recurly revenue recognition on your site after you've created entities, you will need to create 2 GL codes for each entity on your site.
Q: Can I conduct entity-specific analytics within Recurly?
A: The Entity Code will be included within the Admin UI for the Invoices - Accounts Receivable, Adjustments, Adjustments - Taxes, and Invoices - Summary exports. At this time, analytics dashboards will account for the performance of all subscriptions across your site and will not provide entity-specific information. If this is a feature you are interested in, please let your CSM or customer support representative know as we are always looking to enhance our analytics experience.
Updated 22 days ago