NRA reporting

# NRA reporting

Install the NRA app from the App Shop and open it from your store. An owner or administrator configures the applicable markets and payment flows. Before each change, the app checks with Storeloom that your role still allows it; if you opened it more than 15 minutes ago, it asks you to open it again from Apps. The app asks for company/payment configuration access and separate access to keep financial records and prepare documents/reports. It never asks for payment keys. An existing installation needs to consent to the additional financial-record scope.

This development version has a working local financial workflow. It has not been released or validated through the NRA portal. It does not submit files with your qualified electronic signature.

Configure and publish

Save the seller details, starting document number, effective date and registration profiles. The seller’s EIK must be the company number in Settings › Company; set it there first. Until a policy has been live, the EIK can still be corrected. Choose the applicable profile or explicit exclusion for each market. Inheritance lets a market use the main store’s rules. Saving these drafts does not activate issuance. Changed or removed markets/methods need review.

For each method, confirm its contractual treatment: card, bank transfer, postal money order, fiscal receipt or another supported flow. Cash on delivery needs the actual courier arrangement. The provider’s name alone does not establish treatment. A provider can offer several channels: map them individually or explicitly confirm that the same rule covers every channel it offers. Unreviewed channels stay held. Use the Annex 38 payment code, processor identifiers and VPOS details actually applicable to that contract.

Open Finance to map VAT rates to NRA tax groups. Missing historical tax rates need an explicit reviewed rate; the app does not infer them from the provider. A tip the customer added at checkout is its own line, Бакшиш / Tip, with its VAT: in your 20 % group, as Bulgarian law taxes a tip like any other sale. A tip with no VAT (a customer you exempted from tax) goes in your group for 0 %; without one, that order stays held and says the tip’s line needs a tax group. Confirm the applicable legal eligibility, numbering, QR and archive arrangements, then publish the chosen policy version. Start with Test order mode: it uses separate numbers and clearly marked test documents. Other methods may remain unconfirmed during testing; their actual transactions stay held rather than being omitted from a test report. Test mode creates no payment or refund. Publishing a live policy is not a statement of NRA approval.

Review transactions and documents

The register keeps committed order, payment, adjustment and delivery facts. It shows a stable sequence of records, processing holds and confirmation history. Verified source payments support card documents; a manually marked paid order needs an actual payment confirmation. Refund requests do not count as returned money until their settlement, date and payment method are confirmed.

A confirmation names an existing source and asks for a reference, time in UTC and note. It confirms the source values at that time. If those amounts or delivery lines change, record a reviewed correction; an older confirmation will no longer cover them. The amount comes from that source. Saving a correction appends another version; it does not erase the earlier confirmation. Physical delivery is derived from parcel quantities/history; a source-bound delivery confirmation is available where evidence needs to be entered by the merchant.

Documents keep their issued contents and number. Repeated processing returns the same document. HTML is available immediately after supported issuance; the PDF link appears after background rendering succeeds. Customers use their existing protected order-status document links. Other payment flows get separately numbered information documents, which do not replace a courier’s or fiscal device’s receipt.

Prepare a month

Choose a registration profile and a closed month. The app checks money, tax groups, complete delivery, confirmed refunds, coverage and the official XSD before creating a versioned XML file. Download the retained version from the report archive. Test files keep a TEST filename. An unchanged input returns the existing version; later facts or confirmed corrections can produce another version.

A hold explains that the data needs review. The app never exports a partial set as a complete report. Empty/refund-only months and mixed non-card periods remain held until the published XSD/document-field interpretation is resolved and accepted. Split tender/delivery across months, unsupported payment fees, non-EUR conversion, changed paid orders and historical external-document imports also need further work. No zero sales or invented document numbers are inserted to bypass a check.

Uninstall stops new issuance and records the interruption. Existing financial archives and numbering stay in core; a reinstall does not reset them. Once a store has issued a live document, its company number stays with that store, also after an uninstall: another store cannot issue for the same company, because it would start the document numbers again. A month with a recording gap cannot be presented as a complete live month. Removing app drafts through the privacy workflow does not erase the retained financial archive.

A real launch still needs the merchant’s contracts/registration and the pilot’s accepted payment, document delivery, QR and NRA import checks. Keep the qualified signature filing step with the merchant or authorized accountant.