Skip to content

Global workflow

Make the workspace and customer documents fit their audience

Invoice Crowd separates interface locale from business and customer-facing choices. Available languages come from the installed language catalog, while currency, tax, date and document settings stay attached to the relevant business workflow.

  • Installed language catalog
  • Business and customer context
  • Currency and tax remain explicit

Last updated:

Invoice Crowd localization illustration showing fictional language, locale, currency and tax choices for an international invoice workflow.

How it works

Localization has more than one audience

The signed-in workspace, business defaults and document recipient can need different settings. The product keeps those decisions visible instead of treating translation as automatic accounting advice.

Set the workspace

The top-level locale changes supported interface text for the signed-in user.

Invoice Crowd localization illustration for set the workspace using fictional data.

Choose an available interface language

The locale selector reads the installed, active language records. English remains the fallback where a translated value is not available.

  • Catalog-backed choices
  • Signed-in locale switch
  • English fallback

Keep theme and language separate

Light or dark theme and language are independent preferences, so a visual change does not rewrite locale data or business records.

  • Independent theme toggle
  • Locale-specific interface text
  • No record conversion

Prepare customer documents

Business and recipient context controls how a document is presented and sent.

Invoice Crowd localization illustration for prepare customer documents using fictional data.

Customer-facing language

Supported send composers can select a language for customer-facing communication while preserving the underlying document facts.

  • Visible language selection
  • Document facts preserved
  • Email wording can differ

Editable document labels

Invoice and proposal editors expose label text so a business can adapt presentation without changing stored quantities, rates, taxes or totals.

  • Presentation labels
  • Amounts remain numeric facts
  • Reusable business defaults

Preserve regional meaning

A language switch does not decide the correct currency, tax or legal treatment.

Invoice Crowd localization illustration for preserve regional meaning using fictional data.

Currency, tax and dates

Choose document currency, exchange-rate context, tax rules and date presentation explicitly for the business and transaction.

  • Currency selected per workflow
  • Taxes configured deliberately
  • Date meaning stays visible

Regional payment availability

Gateway and payment-method availability depends on the provider, market, account and implementation. Translation alone does not make a method available.

  • Provider market limits
  • Account eligibility
  • Configuration still required

Capability map

Regional controls that stay explicit

Language is one part of localization; currency, taxes, dates, numbering and gateway availability retain their own rules.

  • Interface locale

    Switch among active languages available in the installed catalog.

  • English fallback

    Preserve usable interface text when a translated value is unavailable.

  • Customer communication

    Select supported language context in document send flows.

  • Document labels

    Adapt visible labels without rewriting financial facts.

  • Business defaults

    Keep reusable regional settings attached to the relevant profile.

  • Document currency

    Select the currency and retain its transaction context.

  • Exchange rate

    Make the selected rate context visible for foreign-currency documents.

  • Tax settings

    Configure taxes deliberately instead of inferring them from language.

  • Date presentation

    Use regional presentation while preserving the underlying date.

  • Number formatting

    Present amounts in a readable locale-aware format where supported.

  • Payment markets

    Respect provider and account availability by region.

  • No automatic advice

    Localization does not determine legal, tax or accounting treatment.

Questions

Localization, answered

Which languages does Invoice Crowd support?

The current choices come from the installed and active language catalog, so the available list can change by deployment. The locale selector is the authoritative list for your account, with English used as a fallback.

Does changing language convert currencies?

No. Interface language and document currency are separate choices. Foreign-currency documents retain an explicit currency and exchange-rate context.

Can customer documents use a different language?

Supported invoice, proposal and report send flows can carry customer-facing language context. Exact labels and translations should be reviewed before sending.

Does Invoice Crowd choose my tax rules from my locale?

No. Taxes must be configured for the business and transaction. Locale is presentation context, not tax or legal advice.

Will every payment gateway work in every country?

No. Availability depends on the provider, market, account, currency and the current Invoice Crowd integration. Review the relevant provider guide and provider terms.

Can administrators edit translations?

A protected language-management surface exists for installed language records. It is an administrative capability, not a normal team-member translation workflow.

Test the exact customer-facing document

Choose the language, currency, taxes and dates, then preview a representative invoice or proposal before making that configuration the team default.

  • No card required to start
  • Configuration stays visible
  • Current product boundaries stated