Structuring Contracts for Tax Compliance: Invoicing Foreign Clients to Guarantee Foreign-Source Income Status

TL;DR

• Under Georgian tax law, income classification is determined by the contract and invoice documentation, not solely by the client's country of incorporation or the founder's intention.

• For Virtual Zone companies, the contract must establish that the client is a foreign entity, the service is IT in character, and the service is delivered and received outside Georgia.

• Vague or generic invoices, "consulting fee," "monthly services," "project work", create an evidentiary gap that the Revenue Service can exploit to reclassify income.

• The contract structure and invoice description are the two primary documents the Revenue Service examines when assessing whether VZS income qualifies for the 0% rate.

• Payment routing matters: foreign client payments should flow directly into the Georgian corporate bank account, not through personal accounts or intermediate foreign accounts.

• Mixed-revenue contracts, where qualifying and non-qualifying income are bundled under one fee, must be unbundled with separate line items for each income type.

• Individual entrepreneurs under SBS do not face the same VZS export rule, but maintaining clear documentation of foreign-source income supports banking, residency, and treaty claims.

The 0% corporate income tax rate under Virtual Zone status is not protected by the contract the Revenue Service signed when it granted VZS status. It is protected, or lost, by the contracts you sign with your clients.

Income classification in Georgia is a factual question. The Revenue Service Georgia determines whether income qualifies as VZS IT export income, and therefore attracts 0% CIT, based on the documentation supporting the transaction. That documentation is the client contract and the invoice. If the contract does not establish the key qualifying elements, and if the invoice does not describe what was delivered, the income classification defaults to whichever rate is most conservative.

This guide covers exactly what contracts and invoices must say to protect foreign-source income status, how to handle mixed-revenue situations, and how payment routing and documentation practices affect the sustainability of the 0% rate.

Why contract structure determines income classification

Georgian tax law determines the source of income based on substance, where the service was performed and received, who the parties are, and what was delivered. The Revenue Service does not take the taxpayer's self-declaration of income classification at face value when the documentation does not support it.

For VZS income to qualify at the 0% rate, the Revenue Service must be able to verify, from the documentation, that three qualifying conditions are met: the income is from an IT service, the client is foreign, and the service is delivered outside Georgia. If any of these conditions cannot be verified from the contract and invoice, the income is at risk of reclassification.

A founder who knows their client is foreign, knows the service is IT, and knows the service was delivered outside Georgia, but whose contract and invoices say none of these things, has a compliance problem. The Revenue Service does not read minds. It reads documents.

The burden of proof lies with the company, not with the Revenue Service. If the Revenue Service questions an income classification, the company must produce documentation showing the qualifying conditions are met. A contract that is silent on client tax residency or place of service delivery does not meet that burden.

The five essential elements of a VZS-compliant client contract

Every client contract generating income that a Georgian VZS LLC intends to declare as qualifying IT export income should contain the following five elements explicitly.

1. Identification of the client as a non-Georgian entity

The contract should identify the client as a company incorporated outside Georgia, operating outside Georgia, and not tax resident in Georgia. For individual clients, the contract should identify the client as a non-Georgian tax resident. This does not need to be a legal declaration, a clear description of the client (name, registered address, country of incorporation) is sufficient to establish the factual starting point.

2. Description of the IT service

The contract should describe the service being rendered in specific IT terms. Not "services", "software development services," "SaaS platform access and maintenance," "API integration and technical support for [product name]," "cloud infrastructure management." The description must make clear that this is an IT service, a technology activity performed by the Georgian entity.

3. Confirmation of remote delivery outside Georgia

The contract should state explicitly that the services are delivered remotely by the Georgian entity and received by the client outside Georgia. A simple clause is sufficient: "All services shall be provided remotely from Georgia. The client acknowledges that the services are received and used at the client's principal place of business in [country]."

4. Currency and payment terms

The contract should specify the invoicing currency (USD, EUR, GBP) and the payment method. Most VZS companies invoice in foreign currency, this is standard and creates no tax issue. Payments should be routed to the Georgian LLC's Georgian bank account. Specifying this in the contract removes ambiguity about where the payment obligation is discharged.

5. Contracting entity identification

The contract should clearly identify the Georgian VZS LLC as the contracting party on the Georgian side, with its full legal name, Georgian registration number, and, where relevant, its Virtual Zone certificate number. This connects the contract to the entity that holds VZS status and is filing VZS declarations. For how to register a company in Georgia, including getting the registration extract that confirms the company's details, see the Gegidze company registration guide.

Invoice requirements: what generic invoices miss

Contracts establish the framework. Invoices are the transaction-level evidence. A perfect contract paired with a generic invoice creates a gap, the contract says what should have been delivered, but the invoice does not confirm what actually was.

What a compliant VZS invoice contains

Every invoice issued by a VZS LLC to a foreign client for qualifying IT income should include:

• The Georgian LLC's full legal name and Georgian company registration number.

• The client's full legal name, country, and address.

• A specific description of the IT service delivered in the billing period, not "services" but "SaaS platform subscription, [product name], [period: month/year]" or "Software maintenance and technical support, [product name], [billing period]."

• The invoice amount in the agreed foreign currency.

• Payment instructions referencing the Georgian corporate bank account.

• Invoice date and due date.

What generic invoices miss

Generic invoice line items, "Consulting," "Monthly fee," "Project," "Services," "Technical work", do not describe the qualifying IT activity. They describe nothing. In an audit, the Revenue Service assessor examines the invoice to determine whether the income matches the VZS declaration. A line item that could describe anything is not evidence that the underlying income qualifies as IT export income.

The additional risk: if the company also serves Georgian clients, generic invoices make income segregation difficult to defend. The Revenue Service cannot distinguish VZS-qualifying invoices from non-qualifying invoices if both say "monthly fee."

Invoice Description	VZS Compliance Risk	Recommendation
"Monthly fee", no further detail	High, cannot establish IT service character	Replace with specific product/service description
"Consulting services"	High, consulting may not qualify as IT	Replace with "IT consulting: [specific activity]"
"SaaS platform access, [Product], March 2026"	Low, specific, IT in character, period clear	Compliant, no change needed
"Software development, [Project name], Milestone 2"	Low, development work clearly IT	Compliant, no change needed
"Technical support and maintenance, [Product], Q1 2026"	Low, product-linked, IT in character	Compliant, no change needed
"Project X, Phase 1"	Medium, ambiguous without further description	Add IT service description and project scope

Handling mixed-revenue contracts

Many client engagements generate multiple types of income, some qualifying for VZS, some not. The most common example is a SaaS company that bills a foreign client for: a software subscription (qualifying), an onboarding / implementation fee (qualifying if IT in character), and a training or advisory fee (potentially non-qualifying).

The rule is simple: every income type needs its own line item, with its own description, on the same invoice or on separate invoices. Bundling qualifying and non-qualifying fees under a single line item, or under a single total amount, creates an apportionment problem that the Revenue Service resolves in the most conservative way.

Separate line items

A single invoice can contain multiple line items representing different income types, qualifying and non-qualifying, provided each line item is clearly described and separately amounts. This allows the company to declare the VZS-qualifying income separately in its monthly declarations while including the full invoice amount in the accounting records.

Separate invoices

Alternatively, qualifying and non-qualifying revenue can be billed on separate invoices. This is cleaner from an accounting perspective but requires the client to receive two invoices per billing cycle, a commercial consideration that should be discussed with clients where relevant.

Never bundle a VZS-qualifying fee and a non-qualifying fee under a single line item "for simplicity." The Revenue Service will apply the most conservative classification to the entire bundled amount. Separate line items take two minutes to add to an invoice template and protect the 0% rate on the qualifying portion.

Payment routing: keeping the evidence clean

The payment flow from client to the Georgian LLC creates an evidence trail. That trail should be consistent with the contract: a foreign client paying a Georgian entity for IT services should result in a payment from a foreign bank account to the Georgian LLC's Georgian corporate bank account.

Correct routing

Foreign client pays directly to the Georgian LLC's Georgian corporate bank account. The bank statement shows an incoming foreign-currency transfer from the client's name or entity. This is clean, consistent with the contract, and creates no ambiguity about who paid, what entity received payment, and where the payment landed. For opening a Georgian corporate account in multiple currencies, see open a multi-currency bank account in Georgia.

Problematic routing patterns

The following payment patterns create documentation problems:

• Client pays to the founder's personal account, who then transfers to the company. The payment is received personally, not by the Georgian LLC, creating a factual gap between the contract (which shows the LLC as the payee) and the payment evidence.

• Client pays to a foreign entity (a holding company or subsidiary), which then transfers to the Georgian LLC. This creates an intermediary transaction that must be explained and may raise related-party transaction questions.

• The founder instructs the client to pay in GEL via a Georgian consumer account, rather than in foreign currency to a corporate account. This is factually inconsistent with a foreign-client transaction.

None of these patterns are automatically fatal to VZS income qualification. But they each require additional explanation and documentation to overcome the evidentiary gap they create. Clean routing eliminates the problem entirely.

SBS individual entrepreneurs and foreign-source income

Individual entrepreneurs under Small Business Status do not face the VZS export rule, there is no 0%/15% split based on client location. The 1% SBS rate applies to all qualifying gross turnover, regardless of whether clients are Georgian or foreign.

But foreign-source income documentation matters for SBS IEs in three other contexts.

Banking and KYC

Georgian banks, and international banks dealing with Georgian IEs, conduct KYC on income sources. An IE with primarily foreign-source income that cannot produce clear contracts and invoices documenting that income may face difficulties maintaining or opening accounts. See opening a bank account in Georgia for what banks typically require.

Tax residency and treaty claims

If an IE is also seeking a georgia tax residency certificate, to prove fiscal domicile to a foreign tax authority or to claim treaty benefits, the Revenue Service may examine the income sources. An IE earning primarily foreign-source income has a stronger case for georgia tax residency than one earning only Georgian-source income. Clear documentation of foreign-source income supports the certificate application. See the guide on Georgia tax residency requirements for how income sources factor into the application.

Home-country tax authority queries

An IE who has relocated to georgia country and is seeking to terminate home-country tax residency may need to demonstrate to their home tax authority that their income is genuinely from foreign sources (if the home country has exit rules based on income source). Clear contracts and invoices showing IT services delivered by the IE to foreign clients outside Georgia are the relevant documentation.

Documentation retention requirements

The Revenue Service Georgia can audit a company for up to six years after the relevant tax period. All documentation supporting income classification, contracts, invoices, bank records, correspondence, should be retained for at least six years.

Practical retention requirements:

• Signed client contracts, retain original signed copies or digital originals with electronic signatures.

• All invoices issued, retain in PDF or equivalent format with invoice number, date, and payment reference.

• Bank statements confirming receipt of client payments, retain monthly statements showing the incoming transfer details.

• Any correspondence with clients that establishes the nature or location of the services, retain email threads, project documentation, and service confirmations.

• The company's VZS certificate and annual compliance documents, retain all versions.

Cloud storage with regular backup, a consistent naming convention, and folder organisation by year and client is sufficient. The Revenue Service accepts digital copies in audit situations.

Red flags that attract Revenue Service scrutiny

The Revenue Service Georgia has patterns of audit trigger based on known compliance failure modes. The following signals attract scrutiny:

Revenue significantly above declarations

If a VZS company's bank account shows substantially more incoming funds than its monthly VZS declarations report, the Revenue Service will investigate the discrepancy. The company must be able to account for every GEL in the bank with a corresponding declaration entry.

Generic invoices paired with large payments

A company issuing invoices reading "monthly services, EUR 50,000" to what appears to be a related party in a low-tax jurisdiction is a pattern the Revenue Service recognises. Large payments on generic invoices attract proportionally more scrutiny.

Payments routed through personal accounts

As noted above, payments received to personal accounts and then transferred to the company create an evidential gap that the Revenue Service can use to question whether the income was genuinely earned by the Georgian LLC or by the individual.

Related-party foreign clients

Transactions between the VZS LLC and entities controlled by the same shareholder, a UAE holding company, a spouse's UK business, are treated with heightened scrutiny under Georgian transfer pricing rules. These are not prohibited, but they require arm's-length pricing and commercial documentation. For how transfer pricing rules interact with VZS, Gegidze recommends professional review for any related-party transactions. See tax optimisation strategies in Georgia for the boundaries of legitimate structuring.

How Gegidze helps

Gegidze reviews, prepares, and manages client contract and invoice compliance for Georgian VZS LLCs and SBS individual entrepreneurs.

• Contract template preparation: We prepare client contract templates that include all five VZS-qualifying elements, tailored to the company's specific service model (SaaS, development, consulting, maintenance).

• Invoice template review: We review existing invoice templates and line-item descriptions, flagging generic language and replacing it with VZS-compliant service descriptions.

• Mixed-revenue unbundling: For companies with multiple revenue streams, we structure invoice templates to separate qualifying and non-qualifying income on separate line items with appropriate descriptions.

• Payment routing advice: We advise on corporate bank account setup in multiple currencies to ensure payment routing is consistent with contract structure. For account opening, see open a corporate bank account in Georgia.

• Documentation review prior to Revenue Service interaction: When clients are subject to Revenue Service review or audit, we compile and review the contract, invoice, and banking documentation package before submission.

• SBS income documentation: For individual entrepreneurs, we advise on contract and invoice structures that support banking, residency, and treaty claims involving foreign-source income.

Final thoughts

Contract structure and invoice description are not administrative tasks that come after the real work of building and selling a product. They are the documentation that determines whether the real work generates 0% CIT or 15% CIT.

The georgia virtual zone gives Georgian IT companies one of the most competitive tax environments in the world. That environment is protected by documentation. A well-structured contract and a specific, accurate invoice are the two cheapest compliance tools available, they cost nothing to prepare correctly and potentially millions in reclassified tax liabilities if prepared carelessly.

Build the habit from the first client. Review the contract template before it is signed. Approve the invoice description before it is sent. Check that the payment lands in the correct account. These are not burdensome steps for a company operating at scale, they are the foundation of sustainable 0% rate compliance.

If you want Gegidze to review your existing contracts and invoices for VZS compliance, or to prepare new templates from scratch, book a free consultation with Gegidze and we will assess your current documentation in a single session.

Frequently asked questions (FAQs)

Does the contract need to be in Georgian, or can it be in English?

Contracts can be in any language agreed by the parties. There is no legal requirement for client contracts to be in Georgian. However, if a contract is submitted to the Revenue Service during an audit, and it is in English, German, or another foreign language, the company may be required to provide a certified Georgian translation. Gegidze recommends having a Georgian translation of the standard client contract template available, even if the signed version with the client is in English.

Can the contract be signed electronically?

Yes. Electronic signatures are legally recognised in Georgia. A contract signed via DocuSign, HelloSign, or equivalent electronic signature platform is legally valid. The signed electronic document, with its audit trail, should be retained in the company's documentation archive. For clients who require wet signatures, physical signing is also acceptable. The choice of signing method does not affect the contract's function as VZS income documentation.

What if my client refuses to include specific clauses about Georgian VZS status?

Client contracts are commercial documents, and most commercial clients will not agree to include references to your Georgian tax structure in their contracts. This is not a problem, the contract does not need to reference VZS status explicitly. What matters is that the contract describes: what IT service is being delivered, who the client is (foreign entity or individual), and that the service is delivered remotely. A standard service agreement that establishes these facts, without mentioning VZS, is sufficient for income classification purposes.

How detailed does the invoice service description need to be?

It needs to be specific enough that an independent assessor, a Revenue Service official who has never heard of your company, can determine from the invoice description alone that the income is from an IT service delivered to a foreign client. "Software development services for [Client Name], Phase 2 backend build, February 2026" is sufficient. "Services rendered" is not. A rule of thumb: if the description could also describe a laundry service, a consulting engagement, or a trading transaction, it is not specific enough.

Do we need a new contract for each project, or can a master agreement cover multiple engagements?

A master services agreement, covering the general terms of the relationship, the qualifying elements, and the nature of the services, can serve as the framework for multiple engagements. Individual projects or billing periods can be covered by statements of work or order forms attached to the master agreement, each describing the specific services for that engagement. This is a common and efficient structure for ongoing client relationships. The master agreement must contain the five essential elements; the statement of work provides the engagement-specific detail.

What if we need to invoice in GEL rather than foreign currency?

Invoicing in GEL is possible but unusual for VZS export income. Most foreign clients pay in their home currency, USD, EUR, GBP. An invoice to a foreign client in GEL is not disqualifying for VZS purposes, but it creates a practical question: why is a foreign client paying in Georgian Lari? If the client is a Georgian entity, the answer is obvious. If the client is genuinely foreign, the GEL invoicing requires explanation. Gegidze recommends invoicing foreign clients in their functional currency and maintaining a Georgian corporate account that accepts the relevant foreign currencies.

How do we handle refunds or credit notes under VZS? Does this affect the income classification?

Refunds and credit notes reduce the gross income declared for VZS purposes in the period they are issued. A refund to a foreign client on qualifying VZS income reduces the qualifying income total, it does not create a new non-qualifying income item. The refund or credit note should be documented with the same specificity as the original invoice: the client's identity, the service the refund relates to, and the period. Monthly declarations should reflect the net income after refunds in the relevant period.