Skip to main content

How to Manage Billing Contacts

Audience: HUB Super Admins Related feature: Flexible Invoice Management

What is a billing contact?

A billing contact is a record that holds all the invoicing details for a specific legal entity in your organization. Each billing contact includes:

  • Entity name (e.g., SkyWatch Space Applications)

  • Full billing address (street, city, zip, country)

  • Billing contact name (the A/P contact at the entity)

  • Billing email(s) — up to 6 addresses; invoices are sent to every address listed

  • Tax / VAT / other ID

  • Invoice-specific wording (required in some countries for an invoice to be legally payable)

Billing contacts are created and managed entirely by your organization's Super Admin.

Note: Once a billing contact is linked to a billing method, it overrides any billing contact listed on individual HUB order forms tied to that method. The billing contact record is always the source of truth for where invoices are sent.


Adding a billing contact

  1. Sign in to HUB as a Super Admin.

  2. Go to your organization's Billing settings (Organization -> Billing).

  3. Select Add Billing Contact.

  4. Fill in the required fields:

    • Entity name

    • Billing address

    • Billing contact name

    • Billing email(s) — you can add up to 6

    • Tax / VAT / other ID (if applicable)

    • Any invoice-specific wording required for your country (if applicable)

  5. Save the record.

Once saved, the billing contact is available to associate with a billing method, or with individual projects if you're using Invoice per Project.


Editing a billing contact

  1. Go to your organization's Billing settings.

  2. Locate the billing contact you want to update and select Edit.

  3. Update any of the fields (address, billing emails, tax ID, etc.).

  4. Save your changes.

Edits take effect immediately for any future invoices routed to that billing contact. If your invoices are going to the wrong recipient, this is usually the fix — check the billing email(s) on the relevant billing contact record first, since that overrides any email on file elsewhere.


Removing a billing contact

  1. Go to your organization's Billing settings.

  2. Locate the billing contact and select Remove (or Delete).

  3. If the billing contact is currently attached to a billing method or one or more projects, HUB will prompt you to:

    • Disconnect it from each attached billing method/project, and

    • Assign a replacement billing contact to each one.

  4. Once every attachment has a replacement assigned, HUB allows the deletion to complete.

Important: HUB will not let you delete a billing contact that's still in use without a replacement in place. This prevents a billing method or project from being left without valid invoicing details.


How do billing contacts interact with invoice structure?

If your organization uses multi-level invoicing, keep in mind:

Invoice mode

Billing Contact Requirement

One org-level billing contact covers everything

Each billing method needs its own billing contact

Every project must have its own billing contact assigned

If you're on Invoice per Project and can't save your billing configuration, it's almost always because one or more projects is missing an assigned billing contact. Add or assign a billing contact to each project and the save will go through.


FAQ

My invoices are going to the wrong email — what should I check first? Check the billing contact tied to that billing method. If a billing contact is configured, its billing email(s) are where invoices go — this can be different from the email on your organization profile or order form.

I removed a billing contact but it's still attached somewhere — is that possible? No — HUB won't complete the deletion until you've reassigned every billing method or project that depended on it to a different billing contact.

Can I add more than one billing email to a contact? Yes, up to 6. Invoices are sent to all listed addresses.


Have questions not covered here? Reach out to our SkyWatch support team.

Did this answer your question?