Skip to content

Appendix A — UJP codebooks

← Back to contents


This appendix contains a reference overview of all codebooks (cb_* tables) that eFakturaWin uses to align with the UJP e-Invoice system. The codebooks are read-only — they are populated on the first start of the application and used in drop-down lists across the forms. The snapshot below is from UJP Phase 2 (3 May 2026).

A.0. How the codebooks are updated

On the first start of the application, the Db_Codebooks.prg::PopulateCodebookSeeds() function fills all cb_* tables from baked-in seed data. That seed data was taken from UJP at build time.

Each row in the codebook tables has a last_synced column — reserved for a future Service → Refresh codebooks function, which will fetch the latest lists directly from the UJP API.

🚧 Automatic refresh from UJP is not yet implemented. Until then, the codebooks remain "frozen" in the state at installation time; this appendix documents that state. If UJP adds a new code in the meantime (e.g. a new rejection reason), an upgrade of eFakturaWin is needed for that code to be available in the application.

💡 The local cb_* tables can always be inspected directly in the SQLite eFakturaWin.db database with any SQLite client. They are the source of truth for what is available in your installation.


A.1. Countries

ISO-3166 alpha-2 two-letter country codes. Used in the "Country" field of a partner to distinguish residents (MK) from non-residents (foreign EDB + country code).

Where it appears in the application: Codebooks → Partners → Add/Edit → Country field.

UJP endpoint: GET /api/v1/countries

Codes (selection of the most common in MK trade):

Code Name
MK North Macedonia
AL Albania
AT Austria
BG Bulgaria
CH Switzerland
DE Germany
ES Spain
FR France
GB United Kingdom
GR Greece
IT Italy
NL Netherlands
RS Serbia
TR Turkey
US United States of America

The full list contains ~200 countries. For a code not listed here, see the UJP source: countries.json or directly GET /api/v1/countries.

Captured from UJP Phase 2 snapshot, 2026-05-03.


A.2. Currencies

Currency codes. The UJP codebook contains two formats in parallel: three-letter ISO-4217 code (EUR, USD, MKD…) and three-digit ISO-numeric code (978, 840…). eFakturaWin uses the three-letter codes as the primary form.

Where it appears in the application: Invoice → Header → Currency field.

UJP endpoint: GET /api/v1/currency

Codes (selection of the most common):

Code Name
MKD Macedonian denar
EUR Euro
USD US dollar
GBP Pound sterling
CHF Swiss franc
CAD Canadian dollar
AUD Australian dollar
JPY Japanese yen
BGN Bulgarian lev
156 Chinese yuan (CNY)
643 Russian ruble (RUB)
941 Serbian dinar (RSD)
949 Turkish lira (TRY)

The full list contains ~44 codes (including three-letter and numeric variants). For a currency not listed here, see the UJP source or directly GET /api/v1/currency.

Captured from UJP Phase 2 snapshot, 2026-05-03.


A.3. Tax groups (VAT type)

Base VAT rates. From Phase 2 (May 2026) UJP renamed the old codes (A018, B005, V010, G000) to DDV-A / DDV-B / DDV-V / DDV-G.

Where it appears in the application: Invoice → Items → VAT Type column.

UJP endpoint: GET /api/v1/tax-groups

Codes:

Code Name Rate Description
DDV-A VAT 18% 18% Standard rate – 18%
DDV-B VAT 5% 5% Reduced tax rate – 5%
DDV-V VAT 10% 10% Reduced tax rate – 10%
DDV-G VAT 0% 0% Zero tax rate – 0%

Captured from UJP Phase 2 snapshot, 2026-05-03.


A.4. VAT indicator

More detailed classification of the VAT treatment of each item — standard taxation, exempt, reverse charge, out of scope, etc. Each indicator is linked to exactly one tax group (taxGroupCode).

Where it appears in the application: Invoice → Items → VAT Indicator column.

UJP endpoint: GET /api/v1/tax-indicators

Codes:

Code Tax group Name VAT impact
DDV-A DDV-A Standard taxation at the general tax rate of 18% STANDARD
DDV-B DDV-B Standard taxation at the reduced tax rate of 5% STANDARD
DDV-V DDV-V Standard taxation at the reduced tax rate of 10% STANDARD
DDV-G DDV-G Not a VAT payer NULA
DDV-7-I DDV-G Export – supply exempt from VAT with the right to deduct input tax OSLOBODEN
DDV-8 DDV-G Supply exempt from VAT with the right to deduct input tax OSLOBODEN
DDV-9 DDV-G Supply exempt from VAT without the right to deduct input tax OSLOBODEN
DDV-10-13 DDV-G Supply of goods that is not subject to taxation in the country OSLOBODEN
DDV-10-14 DDV-G Supply of services that is not subject to taxation in the country OSLOBODEN
DDV-11-A DDV-A Supply in the country for which the tax is calculated by the recipient at the general tax rate of 18% (reverse charge under Article 32-a of the VAT Law) PRENESEN
DDV-11-V DDV-V Supply in the country for which the tax is calculated by the recipient at the reduced tax rate of 10% (reverse charge under Article 32-a of the VAT Law) PRENESEN
DDV-11-B DDV-B Supply in the country for which the tax is calculated by the recipient at the reduced tax rate of 5% (reverse charge under Article 32-a of the VAT Law) PRENESEN

💡 VAT impact (vatImpact): STANDARD = regular VAT is calculated; NULA = not a VAT payer; OSLOBODEN = exempt from VAT; PRENESEN = reverse charge (Article 32-a).

Captured from UJP Phase 2 snapshot, 2026-05-03.


A.5. Payment type

Codebook of payment types. Used for informational purposes on the e-invoice.

Where it appears in the application: Invoice → Header → Payment type field.

UJP endpoint: GET /api/v1/payment-types

Codes:

Code Description
P10 Cash payment
P11 Card payment
P12 Bank transfer payment
P13 Instalment payment
P14 Online banking payment
P15 Mobile application payment
P16 Free-of-charge supply
P17 Compensation/offset
P18 Payment with a value voucher
P19 Other payment instruments

Captured from UJP Phase 2 snapshot, 2026-05-03.


A.6. Document type

Codebook of document types that can be submitted via the UJP API. At the moment only the regular invoice is active.

Where it appears in the application: Invoice → Header → Document type field.

UJP endpoint: GET /api/v1/document-types

Codes:

Code Name Requires signature Has items Has reference
100 Invoice yes yes no

Captured from UJP Phase 2 snapshot, 2026-05-03.


Codebook of document types that an invoice may refer to (order, customs declaration, pro-forma invoice, etc.). Used in the "Related doc." field in the invoice header.

Where it appears in the application: Invoice → Header → Related doc. field.

UJP endpoint: GET /api/v1/ref-document-types

Codes:

Code Name Description
SYS From system Delivery note and return note, justifications for them, weighbridge note — refers to the ID number of a related document issued through the e-invoice system
JN Public procurement document —
C_D Customs declaration —
C_R Decision of the Customs Administration —
GRD Construction documents —
TRN Transport documents e.g. CMR, bill of lading, accompanying note for uncleared goods
KUP Buyer reference Reference by types of preferential buyers
NAR Order Document used to place an official order for goods or services
FIS Fiscal receipt Used in the case of ambulant sales when payment is in cash and a fiscal receipt and a Cash invoice are issued
PRO Pro-forma invoice Document issued before the sale is realised
PON Offer Offer submitted to a buyer
DOC Other documents —

Captured from UJP Phase 2 snapshot, 2026-05-03.


A.8. Void reason

Official UJP reasons used when voiding a submitted invoice. Chosen in the "Void" window before confirmation.

Where it appears in the application: Invoice list → right click → Void → Reason drop-down. 🚧 (Activates with S1 — the void function is under development.)

UJP endpoint: GET /api/v1/void-reasons

Codes:

Code Reason
S-1 Wrong buyer
S-2 Contract cancellation
S-3 Goods returned in full
S-4 Double invoicing of the same supply
S-5 Other

Captured from UJP Phase 2 snapshot, 2026-05-03.


A.9. Rejection reason

Official UJP reasons for rejecting an inbound invoice. Chosen in the "Reject inbound invoice" window before confirmation.

Where it appears in the application: Inbound invoices → Reject → Rejection reason drop-down. (See also §9.9 Rejecting.)

UJP endpoint: GET /api/v1/reject-reasons

Codes:

Code Reason
O-1 Incorrectly calculated VAT (inadequate tax base, VAT rate, incorrect tax indicator, etc.)
O-2 Error in the order (quantity, price, description of the supply, etc.)
O-3 Wrong buyer data (EDB, name, address, etc.)
O-4 The supply was not performed
O-5 Duplicate invoice
O-6 Wrong date (issue/supply)
O-7 Other

Captured from UJP Phase 2 snapshot, 2026-05-03.


← Back to contents | Previous: FAQ ←