A corporate gift in Latvia is not one decision. It is a chain of employment, tax, privacy, procurement, and delivery decisions that must be owned before anyone places an order. A US parent cannot safely import its domestic fringe-benefit assumptions, and a campaign manager cannot treat a parcel marked “gift” as exempt from Latvian import rules. The practical answer is to classify the recipient, purpose, payer, item, data flow, and route; give each unresolved question to the Latvian owner; and release fulfillment only when the evidence is complete.
This guide is an operating framework, not Latvian tax or legal advice. It reflects official pages live-checked on 21 October 2026. It deliberately avoids inventing a universal employee-gift exemption or VAT deduction. Material conclusions belong to the Latvian employer, its tax advisers, privacy lead, and customs specialist.
Start with six facts that change the answer
Begin with an intake record, not a catalogue. Record the paying legal entity, recipient category, business purpose, item and fair value, origin and delivery route, and personal data required. Those facts determine which specialist must act and whether a domestic alternative is safer.
Recipient category matters first. An employee recognition parcel can be remuneration or another employment benefit question. A client thank-you may be a business expense with VAT and policy consequences. A prospect gift can create influence risk. A public-sector recipient may be prohibited by the recipient’s rules even when the item is inexpensive. A contractor should not be silently treated as either an employee or a customer.
Purpose must be specific enough to review. “Relationship building” does not explain why a person was selected, why this value is proportionate, or whether the timing could influence a decision. “Non-cash anniversary recognition under the Latvian employer’s approved policy” is reviewable. “Thank-you parcel after the contract was signed and all commercial decisions closed” is materially different from a parcel offered during a tender.
Use a single stable campaign key. Attach the request, approver, invoice, employee or customer classification, data notice, import evidence, delivery outcome, exception, and reconciliation to that key. This prevents the cheerful front end of a gifting program from becoming detached from the records that justify it.
| Decision fact | Primary owner | Evidence before release | Stop condition |
|---|---|---|---|
| Employee or other recipient | HR or relationship owner | Recipient class and purpose | Role is ambiguous |
| Employment treatment | Latvian payroll and tax | Written treatment and reporting route | No local conclusion |
| Purchase and VAT | Finance or VAT owner | Invoice, supply chain, VAT decision | Invoice or use is unclear |
| Recipient data | Privacy owner | Purpose, basis, notice, fields, retention | Unnecessary or undisclosed data |
| Import route | Trade compliance or broker | Origin, commodity, value, importer, charges | Importer or classification unknown |
| Release | Campaign owner | All approvals linked to campaign key | Any gate remains open |
Keep the employee-benefit decision with the Latvian employer
The first question for an employee gift is not “Is it under our US limit?” It is “How will the Latvian employer classify this specific benefit?” The official State Revenue Service personal income tax page explains Latvia’s personal income tax system, but a general landing page does not prove that every recognition item is exempt. The employer’s payroll or tax owner should document the applicable rule, the facts that satisfy it, and any reporting or withholding treatment.
Give payroll the actual facts rather than a marketing description. Include the item, market value, whether it is cash or cash-like, the reason for the award, whether eligibility is broad or discretionary, whether performance determines the benefit, who purchases it, and what the same employee has received during the relevant period. A flexible-value card, a physical item, and a reimbursed purchase are not automatically equivalent.
Separate fairness from tax. Even if payroll confirms a treatment, HR still needs a consistent eligibility rule. A program that rewards only employees visible to one manager can create employment and culture problems. Define the milestone, eligible population, exclusions, equivalent choices, refusal path, and treatment of leave, remote work, or termination before the campaign begins.
The US parent should not “gross up” or suppress reporting without the Latvian employer’s decision. Nor should it ask a gifting platform to decide whether the item is wages. The platform can execute an approved invitation and delivery flow; the employer remains responsible for the classification.
Use four outcomes in the decision record: approved as designed; approved with payroll treatment; approved after changing the form, value, or eligibility; or not approved. “Low value” is not a fifth outcome. If the local basis cannot be confirmed, recover by replacing the item with a documented domestic alternative, postponing the send, or recognizing the employee in a non-monetary way that HR has approved.
Acceptance evidence is concrete: policy version, recipient group, item description, fair value and currency, payroll reviewer, written treatment, reporting step, decision date, and recheck trigger. The trigger could be a different item form, higher value, new recipient class, new paying entity, or legal change.
Separate VAT from payroll and expense treatment
Latvia’s standard VAT rate is 21 percent according to the official State Revenue Service VAT page. That fact does not answer whether input VAT on a particular gift purchase is deductible, whether a self-supply or adjustment applies, or how the expense should be treated. Those questions depend on the transaction, the taxable person, the item’s use, and current Latvian law.
Finance should examine the supply chain at three points. At purchase, identify the supplier, customer on the invoice, place of supply, VAT charged, and paying entity. At distribution, document whether the item is provided to an employee, customer, prospect, intermediary, or public-sector recipient and for what business purpose. At reconciliation, match approved quantities, actual recipients, failed deliveries, replacements, and unused stock to the accounting record.
Do not collapse the employee tax conclusion into the VAT conclusion. An item’s employment treatment does not prove input VAT recovery. A valid invoice does not make a personal or promotional use deductible. Corporate income tax or expense deductibility is another distinct question. Give each conclusion its own field, source, owner, and date.
For an intra-EU route, do not call the parcel an import merely because it crossed a national border. Determine where the goods are located, which entity buys them, how the vendor invoices, and whether distance-sale, intra-Community acquisition, or other VAT rules are relevant. For goods entering from outside the EU, import VAT and customs evidence become part of the same accounting file, but they still do not automatically establish deductibility.
The safe operational metric is not “percentage of gifts with VAT recovered.” It is “percentage of released orders with a documented VAT decision by the responsible owner.” A zero-recovery decision can be correct. An aggressive recovery rate without reproducible reasoning is a control failure.
Design privacy before collecting an address
A name, work email, home address, telephone number, preference, delivery instruction, and order history can all be personal data. Latvia’s Data State Inspectorate is the independent supervisory authority for personal data processing in Latvia under the General Data Protection Regulation. The sponsor must determine its purpose, legal basis, roles, notices, access, transfers, retention, and rights handling before recipient data moves to a vendor or carrier.
The European Commission’s business guidance on the GDPR distinguishes lawful grounds and organizational obligations. Consent is not automatically the best or only basis, particularly in an employment relationship where power is unequal. The privacy owner should select and document the basis for each purpose. A lawful basis for employee recognition does not automatically cover later marketing or profiling.
Apply data minimization field by field. HR may need an employee identifier to establish eligibility but the gift vendor may need only an invitation token. The recipient can often provide a delivery address after choosing to participate. A carrier may need a telephone number in one route but not another. A customs broker may require specific identity data only after an import condition is known. Do not upload full HR or customer lists “just in case.”
Keep four boundaries visible:
-
Eligibility data determines who may receive an invitation.
-
Choice data records participation, refusal, and selected item.
-
Fulfillment data supports delivery and customs.
-
Evidence data supports finance, support, rights requests, and required retention.
For each field, record its purpose, source, recipient, access role, storage location, deletion trigger, and exception. If a vendor uses subprocessors or transfers data outside the European Economic Area, privacy and procurement should examine the contractual and transfer safeguards rather than relying on a generic “global” claim.
Design refusal as a normal outcome. The recipient should be able to decline without being forced to provide an address. After refusal or expiry, stop new collection and remove unnecessary working data. For an in-flight parcel, separate data needed to complete, cancel, defend, or reconcile the order from data that can already be deleted. For a deeper control review, use the live corporate gifting vendor security checklist and the address-minimizing invitation guide.
Privacy acceptance evidence includes the purpose and basis, versioned notice, approved fields, controller and processor roles, processor terms, access list, transfer review where relevant, retention schedule, deletion test, and a rights-request lookup test. Delivery success alone is not privacy acceptance.
Treat non-EU corporate parcels as commercial until proven otherwise
The dangerous shortcut is to label a company parcel “gift” and assume the private-gift exemption applies. The Latvian State Revenue Service’s non-commercial gift guidance describes a narrow relief for an occasional, non-commercial consignment sent free of charge by one natural person outside the EU to another natural person in the EU, subject to the conditions and a EUR 45 value ceiling. A company-to-employee or company-to-client parcel does not become person-to-person simply because no recipient payment is collected.
For corporate shipments, use the commercial route unless a customs specialist documents a different legal classification. Record the seller or sender, buyer, recipient, importer, country of dispatch, country of origin, commodity description, quantity, value, currency, freight and insurance, Incoterm where used, and supporting invoice. Screen restrictions, excise goods, food, alcohol, plants, batteries, cosmetics, and other regulated categories before selection.
The official postal consignments page states that VAT and a EUR 3 customs duty per item apply from 1 July 2026 to goods purchased by individuals from non-EU online stores or platforms, with the precise route depending on the consignment. The campaign’s trade owner must confirm how current rules apply to the company’s transaction; do not copy a consumer example into a corporate file.
Choose the importer before dispatch. The importer must be able to provide the declaration data, receive assessments and broker questions, and pay or account for charges. Decide whether duties and taxes are prepaid, billed to the sender, or collected from the recipient. A recognition gift that surprises an employee or client with fees is an operational failure even when the customs calculation is technically correct.
If the route remains uncertain, recover by sourcing in Latvia or elsewhere within the EU, choosing a less regulated item, appointing a qualified broker, or delaying the campaign. Do not lower the declared value, describe a commercial item as a sample without basis, or split a shipment to avoid controls.
Keep 1 November 2026 changes in a future-effective panel
Future-effective import change: do not apply before 1 November 2026
The State Revenue Service page on changes from 1 July and 1 November 2026 says that, for goods in consignments with a value not exceeding EUR 150, a EUR 3 customs duty per item applies from 1 July 2026 and an additional Union handling fee of EUR 2 per item applies from 1 November 2026. It also says the relief for qualifying non-commercial natural-person-to-natural-person gifts up to EUR 45 continues. The corporate sender must not borrow that private relief.
On this article’s verification date, 21 October 2026, the November fee was future-effective. Planning models may show the expected post-1-November landed cost, but invoices, recipient messages, and accounting should apply the rule effective on the legally relevant date. Trade compliance should confirm the event that determines applicability, the number of chargeable items, any updated implementation detail, and the broker’s treatment before release.
Use two dated cost scenarios for campaigns that may straddle the change. The first reflects the rules in force through 31 October 2026. The second reflects the announced 1 November regime. Show product value, freight, customs duty, handling fee, VAT base, broker or postal fee, and who bears each amount. Mark unresolved amounts as unknown rather than zero.
Add a recheck 48 hours before dispatch and again when the declaration is created. If an order is delayed across the effective date, reopen the cost and recipient-experience approval. If the additional cost changes the approved budget or would be charged to the recipient, pause and choose a local/EU alternative or obtain new approval.
Worked decision A: Riga employee recognition bought locally
This hypothetical example illustrates a process, not a customer result. A US parent wants to recognize 40 employees of its Riga subsidiary after a team milestone. The proposed item is a non-cash home-office accessory purchased from a Latvian supplier and delivered to employees who opt in.
The campaign owner first identifies the Latvian subsidiary as employer and the US parent as funder. HR defines a consistent eligibility rule tied to the completed team milestone, provides an equivalent refusal path, and removes managers’ discretion to add favorites. Procurement obtains the Latvian supplier’s quote and confirms item, warranty, delivery, and invoice fields.
Latvian payroll receives the actual item, market value, funding flow, eligibility rule, timing, and previous benefits. It does not receive a vague request to “approve a tax-free gift.” Payroll documents whether and how the benefit enters payroll or another reporting process. Finance separately decides VAT and expense treatment from the supplier invoice and planned use.
Privacy chooses an invitation flow. HR sends tokens to eligible work emails. Employees who accept enter their preferred delivery point; the vendor does not receive the whole HR file. The notice identifies the sponsor, fulfillment providers, purposes, fields, support channel, and retention approach. Home delivery remains optional if an approved office collection route is available.
The initial design fails one control: the supplier’s invoice would name the US parent, while the Latvian subsidiary would distribute the benefits and keep the employee record. Finance pauses the order. Procurement obtains a revised contracting and invoice route that matches the approved tax and accounting design. The campaign is released only after payroll, finance, privacy, and procurement attach their dated decisions.
Acceptance is not “40 boxes delivered.” It is: all 40 recipients meet the rule; every released item maps to an invitation and decision; payroll treatment is posted where required; the invoice matches the purchasing entity; refused and expired invitations stop; addresses are accessible only to the necessary roles; failed parcels are resolved; unused stock is reconciled; and the owner signs closure.
Worked decision B: client parcel arriving from outside the EU
This second hypothetical example is not evidence of Giftpack or any customer performance. A regional account team proposes a thank-you parcel for six Latvian client contacts after a project closes. The item would ship from a non-EU supplier. No recipient pays for the item.
The relationship owner records the completed project, recipient roles, business purpose, value, timing, and each client’s gift policy. One contact works for a municipal company. Compliance removes that recipient from the automatic route and requires written specialist clearance; a small price does not neutralize a public-sector concern.
Trade compliance rejects the request form’s “personal gift under EUR 45” selection. The sender is a company, so the team cannot assume the natural-person-to-natural-person relief. The broker requests a commercial invoice, accurate commodity descriptions, country of origin, quantities, values, and a named importer. Procurement asks the supplier to confirm product composition and packaging so restrictions and classifications can be checked.
Privacy also changes the flow. Instead of emailing the supplier a spreadsheet of home addresses, the campaign sends a notice and claim link. Accepting recipients provide only the fields required for the approved route. Customs-specific information is collected by the party that needs it, at the stage when the need exists. Declining contacts receive no parcel and their unneeded delivery record is removed.
The first broker quote would bill import charges to recipients. The team treats that as a failed recipient experience and pauses. It compares three recovery options: sender-paid import with a qualified broker; a Latvian or EU-sourced substitute; or a digital/non-physical alternative approved by compliance. The local substitute has a higher item price but lower customs uncertainty and no surprise collection. Finance selects it after comparing total landed cost and support burden, not purchase price alone.
Acceptance evidence includes the relationship purpose, recipient policy check, public-sector exception outcome, invoice, VAT decision, route and origin, broker or domestic supplier evidence, privacy notice, consent or other basis decision, delivery result, exception resolution, and final reconciliation. If any one of those remains unknown, the program is not complete.
Run a release checklist with named owners
The operating checklist should be short enough to use and strict enough to stop an unsafe send. Assign one accountable role to each line; “team” is not an owner.
-
Campaign owner: defines recipient group, purpose, value, timing, item, and success criteria.
-
Latvian HR and payroll: classify employee benefits and reporting; approve eligibility and fairness.
-
Finance and VAT owner: approve invoice, purchasing entity, VAT, expense, and reconciliation treatment.
-
Legal or compliance: review client policy, sensitive timing, public-sector roles, conflicts, and no-send cases.
-
Privacy owner: approve purpose, basis, notice, fields, access, processor terms, transfers, retention, and rights handling.
-
Procurement: verify supplier, product, contract, service responsibilities, incident and exit terms.
-
Trade compliance or broker: confirm commodity, origin, value, importer, declaration, restrictions, charges, and effective date.
-
Operations: execute only approved records, monitor delivery exceptions, and preserve evidence.
Test the process with five records before a large launch: one employee, one ordinary client, one sensitive recipient, one refusal, and one delivery failure. Confirm that each route reaches the correct owner, the parcel cannot release early, data access is limited, and the finance record reconciles. A pilot that tests only a successful delivery misses the controls most likely to fail.
Use the corporate gifting risk register when several countries or business units share the program. Keep the Latvia decision record attached rather than replacing local conclusions with a global score.
Measure evidence and recovery, not only delivery
A delivery rate says whether parcels arrived. It does not say whether the program was correctly classified, fairly approved, lawfully operated, or reconciled. Use measures that reveal control quality: released orders with documented payroll and VAT decisions; recipient records limited to approved fields; notices delivered before collection; unknown importers at release; recipient-paid surprise fees; exceptions unresolved past their owner’s deadline; and deletion tasks completed with evidence.
Every failure needs a defined recovery. If payroll cannot classify the item, pause and change the form or obtain local advice. If the invoice is wrong, correct it before posting. If the privacy basis or notice is missing, stop collection. If the importer is unknown, do not dispatch. If a parcel returns, restrict the data to support and reconciliation, resolve replacement or cancellation under policy, and close the record. If a law or authority page changes, reopen only the decisions that depend on it.
Record source verification separately from decision approval. This article verified the named official pages on 21 October 2026. A campaign owner should recheck them at approval and before a material launch. Save the page title, URL, relevant rule, jurisdiction, effective date, verifier, and unresolved gap. A screenshot without the effective date is weak evidence.
The final program file should let a reviewer reproduce the decision without searching private messages. It contains the intake, local conclusions, approvals, notice, supplier and processor terms, invoice, import documents, fulfillment events, exceptions, reconciliation, deletion or retention evidence, and closure signature. That file is the real reusable asset.
Conclusion: make the Latvian decision boundary travel with the gift
The safest Latvia program does not search for one convenient gift limit. It separates the employee-benefit, VAT, privacy, and import questions; assigns them to the Latvian owners who can decide them; and prevents fulfillment until the evidence is linked. It also distinguishes rules already in force on 21 October 2026 from the announced 1 November customs handling fee. That discipline protects the recipient experience as much as it protects the company.
For an approved program, Giftpack can be evaluated as an execution layer for recipient choice, controlled address collection, fulfillment, and global operations. Giftpack does not replace the employer, payroll, tax, legal, privacy, procurement, or customs decisions described in this guide. The commercial platform belongs after the decision boundary, not in place of it.