Overview
UniBee lets you define invoice company information per payment gateway. This means invoices generated through one gateway can display a different issuing entity from invoices generated through another gateway. Use gateway-level invoice configuration when invoices generated through different payment gateways must display different legal entity details, such as company name, address, registration number, VAT number, and logo. This configuration is designed for businesses that manage multiple legal entities, regional invoice issuers, or separate billing identities within the same UniBee environment.At a glance
| Item | Details |
|---|---|
| Applies to | Configuration → Payment Gateways |
| Audience | Finance admins, operations teams, billing owners, and implementation teams |
| Use this when | Your business operates multiple legal entities or invoice issuers |
What this setting controls The payment gateway determines not only how a payment is processed, but also which invoice company details are shown on invoices generated through that gateway.
Before you begin
- Make sure the payment gateway has already been created (or is ready to be configured).
- Prepare the legal entity details you want to display on invoices.
- Confirm which gateway should be associated with which invoice issuer before you enable the configuration in production.
How it works
A gateway record in UniBee can include invoice entity information. When UniBee generates an invoice through that gateway, the configured entity details are used on the invoice output. Figure 1. Gateway-level invoice entity configuration flow. Key behavior: If your business uses multiple gateways, each gateway can carry a different invoice identity. Gateways do not share this configuration.Configure invoice entity settings
- Go to Configuration → Payment Gateways.
- Select an existing gateway, or create a new gateway configuration.
- Open the gateway setup dialog.
- In the Essentials step, find the Invoice Configuration section.
- Enter the company information that should appear on invoices generated through this gateway.
- Upload the company logo if needed.
- Review the remaining gateway settings, such as keys, webhook information, and exchange rate options.
- Click Save.
Field reference
Invoice Configuration (invoice entity)
The gateway-level invoice entity configuration is stored ascompanyIssuer in the gateway configuration (schema: GatewayCompanyIssuer).
| Field (UI) | API / model field | Description |
|---|---|---|
| Issue Company Name | issueCompanyName | The legal company name that appears on invoices generated through this gateway. |
| Issue Address | issueAddress | The company address printed on the invoice. |
| Registration Number | issueRegNumber | The business registration number for the invoice issuer. |
| VAT Number | issueVatNumber | The VAT registration number for the invoice issuer. |
| Company Logo | issueLogo | The logo displayed on invoices generated through this gateway. |
Related gateway settings (same setup dialog)
These gateway fields are commonly configured alongside invoice entity settings:| Field | Purpose |
|---|---|
| Display Name | The gateway display name shown in UniBee. |
| Gateway Icons | Gateway branding icons used to identify the gateway in the admin UI. |
| Exchange Rate | If applicable, configure exchange settings as part of the same gateway setup. |
What happens after you save
- Invoices generated through the gateway use the configured company details.
- The configured invoice entity remains associated with that gateway until it is updated.
- If your business uses multiple gateways, each gateway can carry a different invoice identity.
Example
Suppose your organization operates two legal entities:- UniBee US Inc.
- UniBee Singapore Pte. Ltd.
Operational notes
⚠️ Review entity mapping carefully
Before using this configuration in production, verify that each gateway is mapped to the correct legal entity and that downstream accounting, tax, and compliance workflows expect that mapping.
- Update gateway invoice settings whenever legal company details change.
- Review invoice templates and downstream accounting exports after introducing a new entity.
- Validate production behavior before routing live traffic through a newly configured gateway.
Related topics
- Payment gateway credentials
- Webhook configuration
- Currency exchange configuration
- Multi-currency support