Skip to main content
Lynka is not documented as if every customer operates in one country. A business in Ghana, Nigeria, Kenya, Lebanon, the UAE, Saudi Arabia, France, Germany, or the UK can share the same core workflow while using different currencies, taxes, timezones, privacy rules, and commercial habits. The product should keep those local differences configurable without changing what a Lead, Deal, Quote, Invoice, Purchase Order, or Ticket means.

Set the workspace finance context first

If the business uses Accounting or posted invoices, confirm the workspace base currency and related finance settings before real posting begins. The base currency is important because reporting can normalize supported transaction values into the workspace’s reporting currency when valid FX information exists. Do not change the base currency casually after real financial history exists.

Keep transaction currency separate from display preference

A document can use a transaction currency that differs from the workspace base currency where the workflow supports it. That is different from simply changing which currency symbol a user prefers to look at. Currency and FX explains the distinction.

Configure tax for the business, not the documentation example

Lynka supports tax configuration and mappings, but the documentation does not assume one country’s VAT or sales tax regime. Your company is responsible for configuring rates and treatment that match its obligations and professional advice. Tax across regions explains what Lynka controls and what remains a legal or accounting decision.

Use the correct timezone

Timezone affects what “today” means, when activities are due, how schedules run, and which period a time-sensitive report includes. A team working between Accra, Beirut, Dubai, and Europe should not assume the browser’s local time and the workspace reporting boundary are always the same thing.

Treat privacy and prospecting rules as regional business requirements

European privacy obligations can be especially relevant when handling personal data, but every region can have its own rules for communications, retention, and customer information. LeadGen does not convert generated data into automatic permission to contact somebody.

Mobile is a first-class working environment

For many small businesses, important customer and operational work happens away from a desk. Lynka has dedicated mobile navigation, cards, filters, and full-screen flows instead of simply shrinking desktop tables. Use the mobile guidance in each feature when the interaction differs.

Currency and FX

Understand base currency, transaction currency, and reporting conversion.

Tax configuration

Keep product settings separate from country-specific legal advice.

Timezone and dates

Avoid confusion around due dates, activities, reports, and schedules.

Privacy and data

Use Lynka responsibly across markets, especially when personal data is involved.

Currency, base currency, and FX in Lynka

Understand workspace base currency, document currency, exchange rates, reporting normalization, and missing FX behavior in Lynka.

Configure tax without assuming one country

Use Lynka tax settings, mappings, document tax lines, and accounting controls while keeping country-specific VAT and tax obligations separate from product documentation.

Timezone, dates, due dates, and reporting periods

Understand how timezone and date boundaries affect activities, invoice due dates, automations, dashboard periods, and reports in an international Lynka workspace.

Privacy, customer data, and regional responsibility

Understand Lynka data controls and the responsibilities a business keeps when handling customer, prospect, employee, and financial data across Africa, Europe, and the Middle East.
Last modified on September 7, 2026