Confirmation Declaration Schema

decHfr_confirm_v3_restrict.xsd

1. Overview

This XML Schema Definition (XSD) defines the structure for confirmation notifications pursuant to Article 8(4) and Article 9(4) of Regulation No. H-5 of 29 September 2023 on the terms and procedure for exercising fiscal control over the movement of goods with high fiscal risk within the territory of the Republic of Bulgaria.

1.1 Purpose

The confirmation schema is used to notify the National Revenue Agency (NRA) when goods have been received or dispatched. This serves two purposes:

1.2 Version Information

2. Root Element: decHfrConfirm

The root element contains all confirmation notification data. It consists of one main section (part1) that includes information about the declarant and the transport being confirmed.

Documentation: Notification pursuant to Article 8(4) and Article 9(4) of Regulation No. H-5 of 29 September 2023 on the terms and procedure for exercising fiscal control over the movement of goods with high fiscal risk within the territory of the Republic of Bulgaria

3. Main Declaration Section (part1)

The part1 section contains all elements of the confirmation notification. Elements use the <xs:all> compositor, meaning they can appear in any order.

3.1 Identification Number (ident)

MANDATORY. Identifies the person submitting the confirmation.

Field Type Required Description
ident bulstat (9-13 digits) Yes Personal Identification Number (PIN)/Identification Number for foreigner/Bulstat/Service number NRA (National Revenue Agency)

Restrictions:

3.2 Identification Type (identtype)

MANDATORY. Specifies the type of identification number provided.

Field Type Required Description
identtype identtype enum Yes Identification number type:
1 - BULSTAT
2 - PIN
3 - FPN/PN
5 - service number NRA (National Revenue Agency)

3.3 Receipt Confirmation (isreceived)

OPTIONAL. Boolean flag confirming receipt of goods.

Field Type Required Description
isreceived boolean No I hereby confirm receipt of the goods

3.4 Received Transport Number (uinreceived)

OPTIONAL. The unique transport number under which goods were received.

Note: This schema is used to confirm the receipt and/or dispatch of goods by referencing the UIN (Unique Identification Number) from the original declaration. The recipient confirms receipt using isreceived/uinreceived, and the sender confirms dispatch using issent/uinsent.

Field Type Required Description
uinreceived string (max 13 chars) No Unique transport number under which the goods were received

3.5 Dispatch Confirmation (issent)

OPTIONAL. Boolean flag confirming dispatch of goods.

Field Type Required Description
issent boolean No I hereby confirm that I have dispatched the goods

3.6 Sent Transport Number (uinsent)

OPTIONAL. The unique transport number for dispatched goods.

Field Type Required Description
uinsent string (max 13 chars) No Unique number for transportation the dispatched goods

3.7 Declaration Confirmation (iscorrect)

MANDATORY. Boolean flag confirming the accuracy of the information.

Field Type Required Description
iscorrect boolean Yes Flag - I declare that the information provided in this form is true and accurate. I acknowledge that providing false information is subject to liability under Article 313 of the Criminal Code

Legal Note: By setting iscorrect to true, the declarator acknowledges criminal liability under Article 313 of the Bulgarian Criminal Code for providing false information.

4. Simple Data Types Reference

This section defines the custom simple types used in the schema.

Type Name Base Type Constraints Description
bulstat string minLength: 9, maxLength: 13 Base type for identification numbers
identtype integer Enum: 1, 2, 3, 5 1=BULSTAT, 2=PIN, 3=FPN/PN, 5=NRA Service Number

5. Usage Guidelines

5.1 When to Use This Schema

This schema should be used when:

5.2 Typical Use Cases

Receipt Confirmation: Set isreceived to true and provide uinreceived with the transport number.

Dispatch Confirmation: Set issent to true and provide uinsent with the transport number.

Combined Confirmation: Both receipt and dispatch can be confirmed in a single submission if applicable.

6. XML Examples

6.1 Minimal Example (Required Fields Only)

<?xml version="1.0" encoding="WINDOWS-1251"?>
<decHfrConfirm>
  <part1>
    <ident>123456789</ident>
    <identtype>1</identtype>
    <iscorrect>true</iscorrect>
  </part1>
</decHfrConfirm>

6.2 Receipt Confirmation

<?xml version="1.0" encoding="WINDOWS-1251"?>
<decHfrConfirm>
  <part1>
    <ident>123456789</ident>
    <identtype>1</identtype>
    <isreceived>true</isreceived>
    <uinreceived>2501170000001</uinreceived>
    <iscorrect>true</iscorrect>
  </part1>
</decHfrConfirm>

6.3 Dispatch Confirmation

<?xml version="1.0" encoding="WINDOWS-1251"?>
<decHfrConfirm>
  <part1>
    <ident>987654321</ident>
    <identtype>1</identtype>
    <issent>true</issent>
    <uinsent>2501170000002</uinsent>
    <iscorrect>true</iscorrect>
  </part1>
</decHfrConfirm>

7. Schema Information

End of Documentation