Financial Code Lookup 3695 codes

VAT exemption reason codes

VATEX is the code list for the EN 16931 VAT exemption reason (BT-121): it states in a coded, machine-readable way why an invoice line carries no VAT — an EU VAT Directive article, a scheme such as reverse charge or intra-Community supply, or a national exemption.

VAT category codes (duty, tax or fee category)

UNCL 5305 is the code list for the EN 16931 VAT category (BT-118 at document level, BT-151 per line): a single letter stating how VAT applies to an amount — standard (S), zero-rated (Z), exempt (E), reverse charge (AE), intra-Community (K), export (G), out of scope (O) or the regional Spanish/Italian regimes (L, M, B).

Document type codes (invoice & credit note, EN 16931 BT-3)

UNTDID 1001 is the document type code (EN 16931 BT-3): the code that says what a document is — a commercial invoice (380), a corrected invoice (384), a self-billed invoice (389), a credit note (381) and so on. This page covers the invoice and credit-note codes that EN 16931 and Peppol BIS 3.0 allow; the full UN/EDIFACT list has ~200 document name codes.

SEPA payment status reason codes (ISO 20022)

When a SEPA credit transfer (pain.001) or direct debit (pain.008) is rejected, the bank returns a pain.002 status report carrying a reason code such as AC04 (closed account), AM04 (insufficient funds) or MD01 (no valid mandate). This list decodes each code into what it means and whether the payment can be fixed and resubmitted or is final.

German business transaction codes (Geschäftsvorfallcodes)

A camt.053 statement from a German bank carries a three-digit GVC (Geschäftsvorfallcode) in BkTxCd/Prtry/Cd that says what each booking is — a SEPA credit transfer, a direct debit, a return, a fee, interest. Without it a German statement is a list of amounts with no meaning. This list maps each code to its official German label and usual booking direction.

VAT date code (date/time period qualifier)

UNTDID 2005 is the VAT date code (EN 16931 BT-8): when only present without an explicit VAT point date, it states which event fixes the tax point — the invoice issue date (3), the actual delivery date (35) or the payment date (432).

Currency codes

ISO 4217 is the standard for currency codes: a three-letter code (EUR, USD, GBP), a numeric code and the number of minor units (decimal places) for every active currency in the world. EN 16931 uses it for the invoice currency (BT-5); ISO 20022 uses it on every amount.

Reference code qualifier

UNTDID 1153 is the reference code qualifier: it says what a reference number actually is — a contract (CT), a buyer’s order (ON), a despatch advice (AAK). EN 16931 uses it as the scheme of the invoiced object identifier (BT-18-1, rule BR-CL-07); UN/EDIFACT uses it on every RFF segment.

Item type identification code

UNTDID 7143 is the item type identification code: it says which catalogue an item code comes from — a GS1 GTIN (SRV), the Harmonised System customs nomenclature (HS), a UPC (UP), or the buyer’s or seller’s own numbering. EN 16931 uses it as the scheme of the item classification identifier (BT-158-1, rule BR-CL-13).

Purpose of the payment (ISO 20022)

ExternalPurpose1Code is the ISO 20022 purpose of the payment: the 4-letter code that says what a payment actually is — a salary (SALA), a supplier payment (SUPP), taxes (TAXS), a pension (PENS). It travels in the Purp element of a pain.001 or pain.008 and is passed on to the creditor.

Category purpose of the payment (ISO 20022)

ExternalCategoryPurpose1Code is the ISO 20022 category purpose: the code placed in CtgyPurp to tell the debtor’s bank how to process a payment or a batch — payroll (SALA), tax (TAXS), treasury (TREA), an urgent transfer (URGP), a SEPA credit transfer (SEPA).

Payment rejection and status reason codes (ISO 20022)

ExternalStatusReason1Code is the complete ISO 20022 list of reasons a payment is rejected, returned or held — all 302 of them, from AC04 (account closed) to MD01 (no mandate). It is the code your bank puts in a pain.002 status report to say why a payment did not go through.

Bank Transaction Code (camt)

The Bank Transaction Code (BTC) is how an ISO 20022 bank statement says what each entry actually is. It is a three-level hierarchy — Domain / Family / SubFamily — so a SEPA credit transfer you received reads PMNT/RCDT/ESCT, and the same transfer you issued reads PMNT/ICDT/ESCT. 1563 sub-families across 11 domains.

ACH Notification of Change codes

A Notification of Change (NOC) is how a US bank says "I posted your ACH payment, but your data is wrong — fix it for next time". It is not a rejection: the money moved. The zero-dollar COR entry carries a change code (C01 for a wrong account number, C02 for a wrong routing number…) together with the corrected value, and the Originator must apply it within six banking days or before the next entry to that account, whichever comes later.

ACH Standard Entry Class codes

The Standard Entry Class (SEC) code is the three letters in an ACH batch header that say what kind of entry this is: PPD for a consumer payroll or preauthorized debit, CCD for a business payment, CTX when that business payment carries EDI remittance data, WEB for a debit authorized online, TEL over the phone. There are 23 of them, and the choice is not cosmetic — it decides what authorization you must hold and how long the receiver has to return the entry.