Korisnički alati

Site alati


brix:en:invoices

| Documents |
eInvoices
Invoices | service | Garage | Membership Fees | Webshop | pausalni_obrti | studentservice

Invoices

The form is used to issue outgoing invoices to customers — entry, approval, fiscalisation, sending of eInvoices and voiding. Postings to the journal entry and the VAT books are created automatically from the invoice, and payments against an invoice are linked to the till and bank statements.

Toolbar

  • — Opens the print dialog for the Account card; the print is sent, downloaded or previewed as described in Print language.
  • — Opens the menu of invoice reports.
  • — Shows and hides the list filter.
  • — Opens this help page in a new window.

How to...

List

The filter, the search box, the {Search} box and the list columns are described on the List page.

Statuses

Invoices go through the statuses described in Document statuses. Which invoices are shown in the list is chosen by status in the list filter.

  • Ordered — Shown to companies integrated with a webshop.
  • Draft
  • Approved

A voided invoice keeps the status Approved. It is shown in the list together with its void by choosing Void in the filter.

The fiscalisation status of an invoice is shown in the Status, F1 and F2 columns of the invoice list. An invoice sent as an eInvoice has one of the eInvoice statuses:

  • Delivered
  • Accepted
  • Rejected
  • Paid in full
  • Partially
  • Registered
  • Mediator error

For an invoice fiscalised under the F2.0 protocol, the invoice dialog shows the {eInvoice ID} field with the identifier the eInvoice received when sent for fiscalisation. Companies that fiscalise under the F1 protocol see the fiscalisation data on the ~ FISCAL DATA ~ tab.

Buttons

Next to the list:

  • in the bottom right corner — Opens the dialog for a new invoice.
  • in the bottom right corner — Starts a manual import of items and orders from the webshop; shown only to companies integrated with a webshop (see Importing orders from WooCommerce).

The icons in the invoice dialog header start printing:

  • — Prints declarations.
  • — Prints the address label.
  • — Prints labels; shown only on approved invoices.
  • — Prints the delivery note.
  • — Prints the invoice, as described in print.

In the invoice dialog:

The other dialog buttons, including the round F1 button, are described on the ~ BASIC ~ tab.

Data tabs

Invoice data is arranged in the following data tabs:

  • ~ FISCAL DATA ~
    Issuer's protection code (ZKI), unique invoice identifier (JIR) and the XML files exchanged with the Tax Administration. Shown only in companies with F1 fiscalisation and only for an invoice fiscalised under the F1 protocol.
  • ~ TILL ~
    Till receipts and payments linked to the invoice. Shown to companies with the Tills module enabled.
  • ~ JOURNAL ENTRY ~
    Accounting postings created by approving the invoice.
  • ~ VAT ~
    VAT postings created from the invoice.
  • ~ WOO ~
    Download of the invoice JSON data received from the WooCommerce webshop, for troubleshooting the integration. Shown to companies integrated with a webshop.
  • ~ DMS ~
    Adding, viewing and updating documents related to the invoice, e.g. a warranty card, a technical description of the product and the like.
    • The tab is shown to companies subscribed to the Document Management System (DMS) module.
    • All documents in the invoice attachments at the moment of approval are sent as attachments with the eInvoice. Check the tab before approving.
  • ~ AUDIT TRAIL ~
    Chronology of actions on the invoice and responses of the fiscalisation system.

Limitations

  • Voiding only after fiscalisation — Before voiding in Brix, wait for the information intermediary to successfully fiscalise the credit note. The system automatically links the original document and the void on the Tax Administration side, so if the document has not yet been received in the Tax Administration database, it reports the error “No fiscalisation of the eInvoice is recorded.” If the system refuses the void, check the status of the document with your information intermediary and try again once you receive confirmation of successful fiscalisation.
  • Customer credit limit — The customer's credit limit is checked when an invoice is approved (see limit).
  • Closed VAT periods — Voiding restrictions in closed VAT periods are described in Void an invoice.

Fiscalisation and eInvoice

Invoice types

The invoice type is selected in the {Type} field of the ~ BASIC ~ tab.

  • RAOT - Regular
    Regular invoice.
  • RAMP - Retail
    Retail invoice to consumers and temporary customers; also created from members' subscription plans.
  • rarn
    Service or job card invoice; created from the job card, and entered directly only in a department that does not keep stock.
  • rapp
    Invoice for an advance payment received and its link to the final invoice.
  • RAFO - Delivery Note
    Invoice based on a delivery note; created from the delivery note.
  • odot
    Credit note to a customer.
  • UGSS - From contract - student service
    Invoice created from a student service contract.
Types RAFO and UGSS are not entered manually — invoices of these types are created from a delivery note or a contract respectively. Type RARN is entered manually only in a department that does not keep stock.

VAT and taxes

  • vat_exemption
    VAT exemption basis and its correction on an invoice.
  • non_taxable
    Non-taxable amounts in invoice items.
  • vies
    Automatic check of an EU customer's VAT ID and storage of the confirmation in the DMS.
  • fta
    Exporter's declaration for countries with an FTA (EORI/REX).
  • ppmv
    Special tax on motor vehicles in invoice items.
  • ppom
    Consumption tax (HiP) in invoice items.

Payments and voiding

Printing and reports

  • print
    Signature, liquidator and responsible person on the print.
  • Reports
    Financial report, list of documents, to be delivered, CSV export.

Examples

The collection of examples is kept in one place — praksa.

brix/en/invoices.txt · Zadnja izmjena: od Zoran Spoja

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki