Norway TVINN Import VAT Reconciliation for AP

Norway TVINN import VAT reconciliation is a three-document control. A Norwegian importer needs to tie the foreign supplier invoice, the forwarder or freight invoice, and the TVINN customs declaration to the same import before the VAT return can be prepared with confidence.

The supplier invoice does not control the import VAT amount by itself. AP teams should reconcile the customs declaration summary against the underlying invoices, check the VAT basis built from statistical value plus customs duties and other taxes, and report the import under the VAT-return period tied to the shipping date on the customs declaration. That is why a clean import-VAT file usually looks less like a normal purchase ledger report and more like a customs workpaper.

TVINN is Norwegian Customs' electronic system for customs declarations. For AP, the important point is not the system architecture. It is the declaration evidence TVINN produces: declaration reference, declared values, tariff number, country of origin, duties or other taxes, and the date that drives the import-VAT reporting period.

Each of the three documents answers a different question:

• Foreign supplier invoice: what was bought, from whom, in which currency, on which commercial terms, and at what invoice value.
• Forwarder or freight invoice: what freight, handling, customs clearance, duty, and possible disbursement charges were billed around the shipment.
• TVINN declaration: what was declared to Tolletaten, which importer or recipient was recorded, which tariff and origin data were used, and what statistical value and duties feed the VAT basis.

The reconciliation fails when one of those documents is treated as if it explains all three. A supplier invoice can be correct while the customs value differs because freight, insurance, exchange-rate handling, or duty has been added. A forwarder invoice can include service VAT, disbursed duty, and freight on the same page. A TVINN declaration can be present in the monthly declaration overview even though AP has not yet received the matching supplier invoice.

VOEC is a different path. It is relevant to certain low-value consumer sales where a foreign seller collects Norwegian VAT at checkout. Ordinary B2B imports handled by an AP team are normally TVINN imports, with the Norwegian importer or its representative declaring the goods and preserving the customs evidence for the accounts.

What each document contributes to the import-VAT row

The supplier invoice is the commercial starting point. Capture the invoice number, supplier name, invoice date, currency, invoice value, line items, Incoterms, shipment reference, and any supplier-stated tariff or origin information. If the invoice is in euros, US dollars, sterling, or another foreign currency, preserve both the original currency amount and the NOK amount posted in the accounting system. The customs declaration may use a different exchange-rate basis, so overwriting the original invoice value too early makes later review harder.

The forwarder invoice explains the movement and clearance costs around the shipment. It may include freight, insurance, a customs clearance fee, storage, handling, duty, excise duty, and sometimes a recharge of amounts the forwarder has paid on the importer's behalf. Treat those lines separately. A freight service charge is not the same thing as import VAT, and a disbursement line needs to be reconciled to the declaration rather than booked as an ordinary supplier tax line by habit.

The TVINN declaration is the customs evidence. AP should capture the declaration number, shipping or clearance date, importer or recipient identifier, statistical value, tariff number or HS code, country of origin, customs duties and other taxes, and the declaration status. Tolletaten's declaration overview is useful because it is based on TVINN and gives the business a monthly view of declarations connected to its customer number.

The current official rule is stricter than "book the invoice and move on." For Norwegian VAT-registered enterprises, import VAT on goods is calculated and entered in the VAT return, and purchases from abroad should be reported only when they are present in the accounts and reconciled against the customs declaration summary, according to Skatteetaten's import VAT reconciliation guidance.

That is the practical reason for a reconciliation row. The supplier invoice proves the purchase, the forwarder invoice explains clearance and freight charges, and the TVINN declaration supplies the customs basis. If one source is missing, the row should stay open rather than being forced into the VAT return.

Customs broker paperwork deserves particular care because the broker's document pack may contain a fee invoice, a declaration copy, and backup for duty or tax disbursements. Teams that process these in volume should keep their broker controls separate from ordinary AP invoice entry; the same principle sits behind customs broker invoice processing and document automation, where the document type determines which fields matter.

Norwegian bookkeeping rules do not require the incoming goods invoice itself to refer to the customs declaration. That means the AP workpaper becomes the evidence bridge. It should show which supplier invoice, forwarder invoice, and TVINN declaration were reviewed together, who reviewed them, and what remains unresolved.

How varegrunnlag is built, and why it rarely equals the invoice total

The varegrunnlag is the basis used to calculate import VAT. In AP terms, it is the VAT basis for the import, and it should be taken from the customs declaration logic rather than copied blindly from the supplier invoice.

For ordinary VAT-registered importers, the import VAT basis normally corresponds to the statistical value plus customs duties and other taxes. The statistical value is shown on the customs declaration in Norwegian kroner. Duty and certain other taxes are shown separately. There are exceptions for special procedure codes and certain goods categories, so unusual re-imports, repairs, artworks, dental work, or other special cases should not be treated as routine imports without checking the declaration and advice behind them.

For a normal goods import, the operational calculation looks like this:

Item	Amount
Supplier invoice value converted for customs purposes	NOK 120,000
Freight and insurance included in statistical value	NOK 8,000
Statistical value on the customs declaration	NOK 128,000
Customs duty and other taxes	NOK 6,400
VAT basis	NOK 134,400
Import VAT at 25 percent	NOK 33,600

The supplier invoice in that example might show only the original foreign-currency purchase price. The TVINN declaration may show a higher NOK statistical value because freight and insurance have been included, and the VAT basis is higher again once duty or other taxes are added. If AP compares only invoice total to import VAT, the numbers appear inconsistent. If AP compares invoice, freight, statistical value, duty, and VAT basis, the movement is explainable.

Exchange rates are another common source of mismatch. The supplier invoice may be posted using the accounting system's rate for the invoice date. The customs declaration uses customs declaration values in NOK. Both numbers can be legitimate for their own purpose, but they should not be forced to match.

Freight terms matter as well. Under CIF, freight and insurance are already part of the commercial arrangement in a different way than under FOB. Under DAP or DDP, the forwarder or supplier may present costs that AP must inspect carefully before deciding whether they are purchase cost, freight service, duty, or a disbursement. Incoterms do not replace the declaration, but they help explain why the supplier invoice and the customs basis differ.

When the workpaper shows a mismatch, the first question should be whether the declaration values can be reconstructed from the source documents. If not, AP should preserve the declaration, supplier invoice, and forwarder invoice, then ask the forwarder, customs representative, or advisor for correction or explanation before the import VAT is treated as clean.

Mapping the declaration to the MVA-meldingen period and import codes

Norwegian import VAT has two dates that AP should not collapse into one. The invoice date determines the accounting period for posting the purchase. The shipping date on the customs declaration determines the period in which the import should be declared in the VAT return.

That split matters when goods arrive after the supplier invoice has been posted. A December supplier invoice might sit in December purchase accounts while the import belongs in the January MVA-meldingen because the customs declaration shipping date falls in January. The reconciliation row should therefore carry both dates: invoice date for purchase posting, shipping date for import VAT reporting.

For VAT-return coding, use the current import-goods codes in the accounting or MVA-meldingen workflow:

Code	Use
81	Deductible goods from abroad, high rate
82	Goods from abroad without deduction entitlement, high rate
83	Deductible goods from abroad, medium rate
84	Goods from abroad without deduction entitlement, medium rate
85	Goods from abroad where VAT is not to be calculated, zero-rate cases

Older guides, ERP mappings, and internal checklists may still refer to legacy VAT-return posts or older code labels. Treat those as translation clues, not current filing instructions. The workpaper should show the current code used for the return period being filed and retain enough evidence to explain any historical label in the accounting system.

Input VAT recovery also depends on who the importer is. The Norwegian VAT-registered entity claiming the deduction should be the entity documented by the customs declaration and should have deduction entitlement for the purchase. If another entity appears as importer or recipient, the AP team should not assume the VAT is recoverable just because the cost ultimately relates to the Norwegian business.

For audit purposes, one import row should document the basis and VAT per rate for each customs declaration. That discipline also supports adjacent Norwegian compliance records, including Norway SAF-T requirements for audit-ready records, because a reviewer can trace from ledger posting to customs evidence without rebuilding the import file from email attachments.

The clean row is the one where the purchase posting, import VAT code, importer evidence, and declaration period all agree. If one of those is unresolved, the row needs a review status rather than a forced deduction.

Forwarder clearance, self-clearance, and the double-claim risk

In a self-clearance setup, the importer controls the TVINN declaration and pays any duties or taxes directly through the customs process. AP still needs the same three-way file, but the source of customs evidence is closer to the business: supplier invoice, internal declaration record, Tolletaten overview, and any direct payment evidence.

In a forwarder clearance setup, the freight agent or customs broker handles the declaration on the importer's behalf. The document pack is usually messier. One forwarder invoice may include freight, a customs clearance fee, domestic service VAT on the forwarder's own services, duty paid on behalf of the importer, and other pass-through amounts. Some lines are costs of moving the goods. Some are customs amounts. Some are ordinary supplier invoice lines from the forwarder.

The double-claim risk appears when AP treats every tax-looking amount on the forwarder invoice as recoverable VAT and also calculates import VAT from the customs declaration. Import VAT recovery should be tied to the declaration and the VAT-return calculation. Forwarder service VAT, if charged on the forwarder's own Norwegian services, is a separate domestic input VAT question. Disbursed duty is not VAT. A recharge of import VAT should be reconciled to the declaration before any deduction is booked.

The opposite risk is missing VAT recovery because the forwarder invoice was booked as freight and the declaration was never matched. If the declaration overview shows an import but AP has no matching supplier invoice or freight backup, the file is incomplete. The right response is not to ignore the declaration; it is to mark the import as open and query the missing document owner.

A practical query workflow separates the problem by source:

• Supplier query: missing invoice, wrong currency, unclear Incoterms, missing shipment reference, or inconsistent supplier origin data.
• Forwarder query: missing declaration copy, unclear duty or disbursement lines, unexplained freight allocation, or mismatch between invoice reference and declaration number.
• Customs or advisor query: wrong tariff number, wrong quantity, wrong rate, incorrect importer, or declaration values that cannot be reconciled from the backup.

The workpaper should not ask AP staff to decide customs law from scratch. It should make exceptions visible early enough that the right party can correct the declaration, provide the missing backup, or explain why the amount belongs in a different period or code.

---

Apparel imports need a separate HS, origin, and preference check

Apparel wholesalers have a specific reconciliation problem because tariff number, origin, and preference evidence can change duty, and duty changes the VAT basis. AP does not need to classify garments from first principles, but it should not treat HS and origin fields as decorative customs data.

Many apparel imports sit around HS chapters 61 and 62: knitted or crocheted apparel in chapter 61, and non-knitted apparel in chapter 62. The declaration's tariff number should be visible in the workpaper, especially when the supplier invoice contains product descriptions, style codes, or commodity information that can be compared against the declaration at a reasonableness level.

Country of origin is not the same as country of shipment. A Norwegian wholesaler might buy from a supplier in one country, ship from a warehouse in another, and import goods manufactured somewhere else. If preferential origin is claimed under an applicable trade agreement, the evidence matters. A missing EUR.1 certificate or qualifying invoice declaration can lead to duty that the buyer did not expect, and that duty increases the import VAT basis.

This is where country-of-origin reconciliation from supplier invoices becomes part of the import-VAT control rather than a pure logistics exercise. If the supplier invoice says one origin, the packing documents imply another, and the TVINN declaration records a third, AP should not silently book the result as clean. The issue may affect duty, cost of goods, and recoverable VAT documentation.

For apparel, add these fields to the row even if they are not used for every shipment:

• HS_Code
• CountryOfOrigin
• OriginProof
• PreferenceClaimed
• Duty_NOK
• OriginReviewStatus

The review status is useful because origin evidence often arrives outside the normal invoice flow. A shipment can be physically received and invoiced while the certificate or invoice declaration is still missing. Until that evidence is present, the workpaper should show whether duty was accepted as declared, whether preference proof is being chased, or whether the declaration may need correction.

Keep the scope narrow. AP's job is to preserve the link between the supplier invoice, origin evidence, declaration values, and duty included in the VAT basis. Specialist classification questions belong with customs, logistics, or a trade advisor, but the finance file should make clear when classification or origin has changed the amount being reported.

Build the monthly Excel reconciliation with one row per import

The monthly workpaper should have one row per import, not one row per document. A single import may have a supplier invoice, one or more forwarder invoices, a TVINN declaration, an origin certificate, and internal review notes. The row is clean when those records support the same VAT-return treatment.

A practical Excel layout can start with these columns:

Column	Purpose
ImportRef	Internal reference for the import row
SupplierInvoiceNumber	Foreign supplier invoice number
SupplierName	Supplier legal or trading name
Currency	Original invoice currency
SupplierInvoiceValue	Original invoice value
Incoterms	Commercial terms shown or inferred from documents
ForwarderInvoiceNumber	Freight or customs broker invoice reference
FreightCost_NOK	Freight, insurance, or handling costs identified for review
TVINN_DeclarationNumber	Customs declaration reference
ShippingDate	Date controlling the VAT-return period
StatisticalValue_NOK	Statistical value from the declaration
DutyAndTaxes_NOK	Customs duty and other taxes added to the VAT basis
VATBasis_NOK	Statistical value plus relevant duties and taxes
ImportMVA_NOK	Calculated import VAT
MVACode	Current import VAT code used in the return
HS_Code	Tariff number or HS code
CountryOfOrigin	Origin recorded or evidenced
OriginProof	EUR.1, invoice declaration, none, or other evidence
ImporterOfRecord	Entity shown on the customs documentation
SourceFiles	Supplier, forwarder, and customs files reviewed
ReviewStatus	Open, Matched, Query supplier, Query forwarder, or Adjusted

The control logic is simple enough to audit: every row ties a supplier purchase, any freight or customs broker charges, and one TVINN declaration to one MVA-meldingen treatment. The row should also show exceptions clearly. "Open" means the file is not ready. "Matched" means the source documents support the VAT basis and code. "Query supplier" and "Query forwarder" identify the document owner. "Adjusted" should be reserved for rows where a correction, late document, or reviewed treatment changed the original booking.

This is the point in the process where invoice data extraction is most useful. Invoice Data Extraction converts invoices and financial documents into structured Excel, CSV, or JSON. A team can upload supplier invoices, forwarder invoices, and relevant document packs, then prompt the system for the fields needed in the workpaper. The output includes source file and page references, which helps the reviewer jump back from the Excel row to the underlying document.

A prompt for this workflow can be direct:

Create one import-level reconciliation table. Group supplier invoices, forwarder invoices, and customs references by shipment reference, customs declaration number, or other shared import reference where possible. Output one row per import with supplier invoice number, supplier name, invoice date, currency, net amount, shipment reference, Incoterms if present, forwarder invoice number, freight charges, duty or disbursement lines, customs declaration number if present, HS code if present, country of origin if present, source file and page number, and a ReviewStatus column for unmatched or uncertain rows. Format dates as YYYY-MM-DD and currency amounts with two decimals.

That extraction step does not replace the TVINN reconciliation. It gives AP a structured starting file instead of a folder of PDFs. The reviewer still needs to compare the extracted invoice and forwarder data against the declaration overview and the customs declaration values.

Norway's broader document environment is also changing, especially around Norway's B2B e-invoicing and EHF requirements. Import paperwork from non-Norwegian suppliers will still leave AP with customs evidence, forwarder documents, and exceptions that do not behave like a clean domestic invoice. The workpaper is the control that keeps those documents connected.

The file is ready when every import has one complete row, every VAT basis can be traced to declaration values and duty, every recoverable amount has importer evidence, and every exception has an owner or status.