Skip to main content

Glossary

Written by Jèsel Broekema

This glossary explains what the most important terms in Zenvoices mean. You come across these terms in the portal, in help articles and in conversations with support.
​

The terms are grouped by theme and listed alphabetically within each theme. Use the shortcut Ctrl+F (Windows) or Cmd+F (Mac) to find a term directly, or use the themes below to jump to the right section.
​


Structure and setup

Accounting system connection: The connection between a Zenvoices company and your accounting or ERP system. Through this connection, Zenvoices retrieves master data and exports transactions.
​

Additional module: An extension that you can switch on or off per company. The following modules are available:

  • Authorisation management: offers a clear workflow for approving invoices digitally.

  • Automatic document splitting: module that splits documents consisting of multiple invoices or receipts into separate documents.

  • Document management: for storing documents that do not need to be booked, such as reminders and payment specifications.

  • Payment discounts: makes it possible to automatically settle payment discounts in the transaction.

  • Payments batches: makes it possible to pay invoices from Zenvoices.

  • Purchase to pay: makes it possible to automatically match and check purchase invoices against orders/purchase orders and goods receipts from your accounting or ERP system.

  • Uploading & Importing document categories: you can set up that submitters must select a category when they submit documents.

Which modules you can activate depends on your subscription.
​

API: Connections with various accounting systems have been built to exchange master data and export transactions. This data exchange takes place via APIs. Besides these standard connections, you can also exchange data via our Public API and build your own connection, for example with Multi ERP or other applications.
​

Bulk action: An action you perform on multiple selected rows at once, for example editing multiple companies, deleting multiple documents, importing multiple transactions again, editing multiple users or assigning a tag to multiple accounts.


​Business classification code: The sector code of a company, for example the SBI or NACE code. AI booking uses this code to apply the right VAT rules, for example for a hospitality business. Organisation booking rules can also filter on this code. You set the code via Manage / Organisation / Company / pencil icon / Properties.


​Channel: An automatic connection with an external system from which Zenvoices retrieves invoices and receipts. Available channels are Dropbox, email via POP3/IMAP and JoinData. Documents are retrieved every half hour. If this fails five times in a row, the channel is set to inactive. The submission email address is also seen as a channel, emails are received in real time.


​Company: The accounts of one business within your Zenvoices organisation, connected to one company in your accounting system. You always book within a company.
​

Company level: A setting or rule that only applies within one company.
​

Company tag: A label you use to group companies, for example per employee or per type of processing. You use company tags to grant access, to filter in the dashboard and to apply automation to a group of companies or not.

Column chooser: The feature that lets you decide which columns are visible in a data overview.
​

Dashboard: The overview screen with the status and performance of your processing. Here you can filter by company and by company tags. There is a status dashboard with the number of transactions to process and to authorise, and a performance dashboard with, among other things, the percentage of automatically booked transactions.
​​

Fiscal year: The financial year in which a transaction falls. New fiscal years are copied into Zenvoices as soon as they are created in the accounting system.
​

Inactive company: A company that you have set to inactive. It is not visible in the company overview on the dashboard, you cannot book in it and no documents are retrieved from channels. Peppol invoices still come in. The data is kept, including the full archive, and the regular costs continue.
​

Master data: The basic data that Zenvoices retrieves from your accounting system and synchronises: companies, journals, periods, creditors, debtors, currencies, payment conditions, VAT codes, ledger accounts and, when available, cost centers, cost units and projects. You can also create creditors and debtors in Zenvoices, these are then synchronised to the accounting system. You manage the other master data in your accounting system.
​

Multi ERP: The option to connect multiple accounting or ERP systems to one Zenvoices company. Items, orders and commitments then come via the API from a different system than the one you keep your financial accounts in. Only available in the Complete subscription.
​

On-premise connection: A connection with an accounting system that runs locally at the customer instead of in the cloud. Separate installation guides apply.
​

Organisation: The highest level in Zenvoices: all your companies, users, roles and organisation-wide settings together. One organisation can contain multiple companies.
​

Organisation level: A setting or rule that you set up centrally once and that applies to all (or a selection of) companies in your organisation, instead of per company. Available for automation rules, financial transaction templates, tags and custom recognition fields, among others.
​

Portal: The Zenvoices web environment you work in. You can personalise the portal with your own logo and colours.
​

Subscription: Zenvoices offers the subscriptions Basic, Pro, Complete and ‘Pay per use’*. Basic, Pro and Complete can be combined with Vast & Zeker. Your subscription determines which features and modules are available.
*This subscription has not been offered since 2020. Existing users can continue to use it, but new features are only added to the new subscriptions.
​

Tag: A label you use to group master data. Tags are available for companies, payment conditions, VAT codes, VAT scenarios, ledger accounts, cost units, cost centers, accounts and currencies. You create them at company level or at organisation level.
​

Zenvoices Lite: A product being phased out that automatically converts documents to UBL in real time, for accounting systems that can import UBL invoices.
​

Submitting and importing

Blocked list: A list of senders or file names that are automatically deleted and moved to the recycle bin. This prevents costs for documents you do not need to import. The blocked list is executed before automation rules and does not involve any costs.
​

Destination: The place a submitted document goes to: a journal (for a transaction) or Document management (for storage without a transaction). Can be automated with the assign destination rule.
​

Document management categories: Categories for storing documents that do not need to be booked, such as received reminders and payment specifications. Can be automated with the assign destination rule. Can be created at both company and organisation level. Part of the Document management module.
​

Document type: The type of document determined by AI, for example invoice, receipt, packing slip, payslip, insurance policy or payment reminder. E-invoices always get the type ‘Invoice’. You can set up automation based on the document type.
​

E-invoicing connections: Here you can view all e-invoicing connections, such as Peppol.
​

Import: The step in which Zenvoices processes a submitted document into a transaction proposal. To import a document, its journal must be known. Can be automated with the import rule.
​

JoinData: A platform through which you can receive invoices in Zenvoices, set up as a channel.
​

Origin: The way a document came into Zenvoices, for example email, upload, mobile app or channel.
​

Peppol: The international network for exchanging e-invoices. Invoices that come in via Peppol also arrive in an inactive company. Zenvoices can also send Peppol response messages when the document is received and/or when it has been approved or rejected in the authorisation process.

Remark: A note you add to a document or a transaction. Comments can also be sent along by email and can be used as a condition in automation rules and authorisation schemes. You can add and view comments in Uploading & Importing, Transactions, Authorisation and the Archive. You can tag users with ‘@user’.

Split and arrange: The feature you use to divide a document consisting of multiple invoices or receipts into separate documents and put the pages in the right order. The Automatic document splitting module creates a split proposal for this automatically.
​

Split proposal: An automatically generated proposal to split a PDF with multiple invoices or receipts into separate documents.
​

Submitter: A free user role with only the permission to submit documents. If a submitter gets more permissions, they are seen as a full, paid user. By default, this user role has no company access, this can be set per user.
​

Submitting: Sending invoices, receipts and documents to Zenvoices. You can do this by email, by uploading in the portal, with the mobile app, via a channel, via Peppol, via API or via JoinData.
​

Trusted list: A list of senders whose documents are imported automatically. The trusted list is executed before automation rules.
​

Uploading & Importing: The screen that shows all submitted documents before they become a transaction. Here you upload, split, move, delete and import documents. Among other things, you can see the origin, the subject and the assigned destination here.
​

Uploading & Importing document categories: Categories that submitters choose when they submit a document, for example parking costs or restaurant receipts. This category can be selected via the mobile app or when uploading manually in the portal, so you can set up automation and authorisation based on that choice. Part of the Uploading & Importing document categories module. Can be created at both company and organisation level.
​

@to-zenvoices.com email address: The email address per company to which submitters can email documents. You can set a preferred journal for this in the company settings.
​

Recognition

Account recognition method: The way Zenvoices has determined the account for a document, for example an automatic match on CoC number, VAT number, IBAN, name or debtor number, or via an account assignment rule. You can see how an account match was made in the transaction screen, below the field of the recognised account.
​

Advanced mode: Setup method for a custom recognition field in which you use a prompt to describe what needs to be recognised. Suitable when the field name does not appear literally on the invoice or when you want a calculation to be performed.
​

Automatic invoice recognition: The feature that extracts relevant transaction data from documents and automatically turns it into a transaction proposal. Also called ‘scan & recognition’.
​

Confidence scores: The percentage that shows how confident Zenvoices is about a transaction. The score combines the confidence of the recognition and the confidence of the transaction proposal. There is a score per transaction and a score per field. The lowest score counts: if one field is uncertain, this score is shown.

You use the score to determine from which confidence level a transaction proposal may be approved automatically. This used to be called the recognition score.
​

Cost type: A cost category assigned by AI, for example Fuel costs, Software/SaaS costs or Restaurant costs. Can be used as a condition in rules and authorisation schemes.
​

Custom recognition field: A field you create yourself to have information recognised on an invoice that is not recognised by default, for example a licence plate, project number or usage period. You set it up with a field name (simple mode) or with a prompt in natural language (advanced mode) and use the recognised value as a variable in your transaction or financial transaction template. Available in Pro and Complete; setup at organisation level only in Complete.
​

Document summary: A short description of the document generated by AI, for example ‘Business insurance package (various coverages)’. Can be used as a variable in booking rules, automation and authorisation schemes.
​

E-invoice: An invoice in an electronic, machine-readable format. This can be in UBL or XML format. Scan & recognition is not used for e-invoices: the data is read directly and the confidence score is always 100 percent.
​

Generative AI: The AI component that recognises the cost type, document summary, document type and custom recognition fields. It is switched on by default and can be switched off at organisation or company level.
​

Header level: Level of a custom recognition field that applies to the whole document, as opposed to line level.
​

Line item recognition: The feature that recognises the invoice lines in addition to the header fields. Zenvoices reads tables on the invoice and copies, for example, item numbers, descriptions, amounts, VAT amounts and VAT percentages into transaction lines. Line item recognition can be performed on both e-invoices and other invoices (such as PDF).
​

Line level: Level of a custom recognition field or setting that applies per invoice line, as opposed to header level.
​

Prompt: The question in natural language that you use in a custom recognition field to describe what needs to be recognised, for example: ‘Which customer reference is stated on the first page?’. A maximum of 1000 characters, with room for a maximum of five calculations per prompt. Additional costs apply.
​

Recognised data: The overview in the transaction screen with everything Zenvoices has extracted from the document, including the confidence score per field and the recognised custom recognition fields.
​

Scan & recognition: The collective name for the automatic invoice recognition of Zenvoices. Real-time recognition based on machine learning, on average 3 seconds per document and approximately 90 percent accurate. Supported languages: Dutch, English, German, French, Polish and Spanish.
​

Self-learning invoice recognition: The principle that Zenvoices learns from your corrections. After a transaction is exported, Zenvoices compares the booked data with the data recognised earlier and learns from the differences. Transactions that are exported via approval rules without a check do not train the software.
​

Simple mode: Setup method for a custom recognition field in which you only fill in the name of the field to recognise, for example ‘Licence plate’. Suitable when the field name appears literally on the invoice.
​

UBL: Universal Business Language, the standard for exchanging business documents such as invoices and purchase orders electronically. A UBL invoice uses XML and therefore always has the extension .xml. In the Netherlands, the EN 16931 standard is usually used. UBL invoice and e-invoice are often used as synonyms.
​

XML: Extensible Markup Language, a general standard for defining the structure of documents. XML is overarching: UBL is one of the standards that uses it.
​

Processing transactions

AI: AI booking: a proposal strategy in which Zenvoices itself determines how an invoice can best be booked. AI booking looks at the document, the history of the account, the legislation of the company’s country and your instructions. You switch on AI booking via Manage / Organisation / Companies / Bulk action / Enable AI booking.
​

Archive: The overview where you find completed transactions and the related documents. With the Document management module, documents without a transaction are also stored here. Deleting a transaction from the archive does not remove it from your accounting system. Besides the archive for transactions, there is also an archive in Uploading & Importing, where all received files are stored.
​

Audit report: A report that you can add to a transaction document and download together with the source document. It records the processing history of the transaction (including comments and authorisation history).
​

Deferred transaction: A transaction in which costs or revenue are spread over multiple periods. Also known as deferred expenses, deferred revenue, spread transaction or accrual. Only available for accounting systems that support this.
​

Draft: A transaction proposal that you have not fully completed yet and have saved in the meantime from ‘Incomplete’ or ‘To review’.
​

Entry number: The number under which the transaction is recorded in your accounting system. You can search for it in the archive and use it to open the transaction. An entry number is always generated by the accounting system.
​

Exporting: Sending an approved transaction to your accounting system. After exporting, the self-learning recognition is trained.
​

Financial transaction (transaction type): A transaction that is processed as a journal entry in your accounting system. This is the default transaction type.
​

Financial transaction template: A blueprint for future transactions that you create once. You use a transaction template to simplify complex transactions, for example when one VAT rate must be divided over multiple ledger accounts or cost centers, or when a transaction must automatically be booked as deferred. Transaction templates exist at company level and at organisation level.
​

Header description: The description at header level of the transaction, as opposed to the line description per transaction line.
​

Header field and line field: Fields at the level of the whole transaction and at the level of a transaction line respectively. Per journal and account, you can set which header and line fields are copied from the last transaction.
​

Incomplete: Transactions end up in ‘Incomplete’ when Zenvoices cannot yet create a complete transaction proposal. This usually happens because one or more required details are missing or cannot be determined automatically. A document with a high confidence score can still end up in ‘Incomplete’ (for example because the creditor does not exist yet).
​

Line type: The type of transaction line in a financial transaction template. Possible line types: fixed amount, percentage, remainder, VAT base, line item recognition and recognised amount.
​

Mark as payable: Also called release for payment (see ‘Release for payment’ in the Payments theme). Transactions can be marked as payable automatically after authorisation.
​

Proposal strategy: The way Zenvoices builds a transaction proposal. The following proposal strategies are available:

  • Master data: based on the master data of the account in your accounting system.

  • Last transaction (VAT recognition): based on the recognised VAT rate and the last transaction of the account. This is the default proposal strategy.

  • Last transaction (line item recognition): based on the recognised invoice line descriptions and the last transaction.

  • Financial transaction template: based on the default transaction template of the account in that journal.

  • AI: AI booking creates the proposal based on the document, the history of the account, the legislation and your instructions. Available in a closed beta.

If there is no match, Zenvoices falls back on ‘Master data’. If AI booking is switched on for the company, AI booking creates the proposal.
​

Purchase invoice (transaction type): A transaction that consists of lines with items and references to order lines, instead of a journal entry. Only available with the Purchase to pay module.
​

Timeline: The overview of everything that has happened to a transaction, available per transaction. On the timeline, you can also see whether AI booking was applied.
​

To approve: Transactions end up in ‘To approve’ when Zenvoices can create a complete transaction proposal; all required fields of the transaction are filled in. A document with a low confidence score can still end up in ‘To approve’ (for example because the recognised date field gets a low confidence score, even though it was recognised).
​

Transaction: The processed invoice or receipt as it ends up in your accounts. Consists of a header and one or more transaction lines.
​

Transaction document: The document, the invoice or receipt, that is linked to a transaction.
​

Transaction line: One line within a transaction, with a ledger account, VAT code, amount and description, among other things. With line item recognition, transaction lines are created from the recognised invoice lines.
​

Transaction proposal: The draft that Zenvoices creates automatically after a document has been imported. You check and approve it, after which it is exported to your accounting system. A transaction proposal is therefore the preliminary stage of a transaction.
​

Transaction screen: The screen in which you check, complete and approve a transaction proposal. Here you find the ‘Recognised data’ and ‘Line item recognition’ buttons and a calculator function, among other things.
​

Transaction type: In the Purchase to pay module: the choice between a financial transaction and a purchase invoice. A financial transaction is booked directly to the general ledger, a purchase invoice is booked to an order or goods receipt.
​

Variable: A placeholder between curly brackets that you use in descriptions and payment references, for example {accountname}, {invoicenumber} or {linedescription}. Zenvoices fills in the variable with the right value for each transaction, so you do not have to adjust descriptions manually.
​

Zero line: A transaction line with an amount of zero. It can be deleted automatically when saving.
​

Automation

Account assignment rule: Automation rule that automatically assigns an account to a document, for example to book all fuel receipts to one account or to assign an account to invoices from suppliers outside the EU. These rules are executed before the regular account recognition takes place.
​

Approval rule: Automation rule that automatically approves a transaction proposal. Intended for transactions with a high confidence score. Only transactions without warnings can be approved automatically.
​

Assign destination rule: Automation rule in ‘Uploading & Importing’ that assigns a journal or document management category to a document.
​

Assign proposal strategy rule: Automation rule for transactions that assigns a proposal strategy, for example a specific transaction template based on text on the invoice. In an assign proposal strategy rule, you can also add instructions for AI booking. These only apply to the transactions the rule applies to.
​

Automation rule: An IF-THEN rule that determines whether an action must be performed automatically for a document or transaction. By default, you can create a maximum of 250 per company. Rules are executed from low to high priority value.
​

Catch-all: A rule without conditions. As a result, it applies to all documents.
​

Condition: The IF part of an automation rule: the field, the operation (contains, starts with, equals and so on) and the value. You separate multiple values with a semicolon without spaces. Operations on text fields are not case sensitive.
​

Delete rule: Automation rule in ‘Uploading & Importing’ that deletes a document automatically.
​

Import rule: Automation rule in ‘Uploading & Importing’ that imports a document automatically. For documents linked to a journal, a transaction proposal is generated. Documents linked to a document management category are placed in the archive.
​

Move rule: Automation rule in ‘Uploading & Importing’ that moves a document to another company. Moving to inactive companies is not performed.
​

Note: Free text field at the bottom of an automation rule or transaction template, in which you record why the rule exists. Visible in the overview of rules or templates.
​

Organisation booking rules: Booking rules based on VAT recognition that you set up at organisation level and that apply to multiple companies.
​

Priority: The value that determines the order in which automation rules are executed: from low to high. Applies to rules at both company and organisation level. A rule with priority 1 is executed before a rule with priority 100, regardless of whether it was created at company or organisation level.
​

Purchase invoice assessment rule: Automation rule that assesses a purchase invoice line as correct. Only with the Purchase to pay module.
​

Purchase invoice transaction lines (rule): Automation rule that automatically adds transaction lines to a purchase invoice. Only with the Purchase to pay module. For example to add transport costs to the transaction that are on the invoice, but not in the order.
​

RGS: The Referentie Grootboek Schema (Dutch reference chart of accounts), a standardised chart of accounts. You can link ledger accounts via RGS codes and use transaction templates at organisation level across multiple companies.
​

Authorisation

Authorisation management: The module for approving invoices and transactions digitally. Supports both simple approval processes and variants with multiple levels and conditions.
​

Authorisation manager: User role that may assign and manage authorisation schemes, process rejected transactions and edit authorised transactions. Has no access to companies by default.
​

Authorisation overview: The personal overview of transactions waiting for your authorisation. You can set when authorisation overview emails are sent.
​

Authorisation scheme: The record of which authorisers must approve a transaction and in which order. You set the order with levels.
​

Authoriser: User role of someone who approves or rejects transactions. Only users with the permission ‘Authorise transactions’ and the right company access can be added to an authorisation scheme. Has no access to companies by default.
​

Catch-all authoriser: An authoriser who only needs to approve if no other authoriser needs to approve. You set this up with the conditions ‘No authorisers on the previous level’ or ‘No authorisers on higher levels’. Works as a safety net in your scheme.
​

Conditional authorisation: Authorisation scheme in which authorisers are linked to conditions, so the right people are automatically assigned to an invoice. Also called authorisation rules or approval rules. An authoriser without conditions must always authorise.
​

Level (authorisation scheme): The step in the approval order. Authorisation starts at level 1 and moves to the next level as soon as all non-optional authorisers have approved. Multiple authorisers on the same level receive the transaction at the same time.
​

Optional authorisation: Setting per authoriser that means their approval is not required to move to the next level. If all authorisers on a level are optional, the approval of one of them is required.
​

Rejected transaction: A transaction that an authoriser has rejected. This stops the authorisation process and the transaction must be processed again.
​

Payments

G-account: A blocked account for paying payroll taxes and VAT in case of hired staff or subcontracting. In Zenvoices, you can enter a G-account amount per transaction or template. The availability of this field in the transaction screen can be switched on or off (switched off by default).
​

Outstanding and overdue invoices: Overviews within the Payments batches module: invoices that still need to be paid and invoices whose due date has passed.
​

Payment batch: A collection of invoices to be paid that you create in Zenvoices and export as a payment file. Per transaction, you use ‘Include in Zenvoices payments batches’ to set whether the invoice is included.
​

Payment condition: The agreed payment term or payment method for an account. Comes from your master data and is suggested in the transaction proposal.
​

Payment discount: Discount for early payment. With the Payment discounts module, this is applied automatically based on a percentage in the master data of the creditor or based on manual input.
​

Payment file: The SEPA bulk payment file (pain.001.001.03 or 001.001.09) that Zenvoices exports and that you import at your bank.
​

Payment reference: The reference sent along with the payment, for example a Belgian structured communication or an ISO payment reference according to ISO 11649. You can have it filled in automatically with variables. The availability of this field in the transaction screen can be switched on or off (switched off by default).
​

Payments batches (module): The module you use to pay invoices from Zenvoices via a SEPA payment file.
​

Release for payment: Also called mark as payable (see ‘Mark as payable’ in the Processing transactions theme). Lifting the block on a transaction, so it can be included in a payment batch. Transactions can be blocked for payment and released automatically after authorisation.
​

Purchase to pay

Commitment: A recorded future payment obligation in AFAS or Exact Online Bouw, which you can reconcile in Zenvoices against an incoming invoice.
​

Direct purchase invoice: A purchase invoice of which one or more lines are not linked to an order. Can be used as a condition in authorisation schemes and automation rules. Only available in combination with Exact Online.
​

Goods receipt: The recorded receipt of goods. Used in the automatic check of purchase invoices against orders.
​

Matching: Linking purchase invoice lines and order lines to each other at line level, so a complete transaction proposal can be generated, even if there are differences in quantity or price.
​

Order or purchase order: The order in your accounting or ERP system that a purchase invoice is matched with. For each order line, you can see how much has been ordered, received and already invoiced.
​

Purchase invoice assessment: The assessment of a purchase invoice after the check against orders: correct, correct (manual) or incorrect. This assessment is switched off by default and can be switched on at journal level for both purchase invoices and financial transactions. You can have incorrect purchase invoices rejected automatically.
​

Purchase to pay: The module that automatically matches orders and purchase orders from your accounting or ERP system with purchase invoices. Available for Complete and ‘Pay per use’ and not for every accounting system.
​

Reconciling: Linking an open order or commitment to an incoming invoice, so it is clear which part of the order has been invoiced.
​

Users and permissions

Administrator: Fixed user role with all user permissions except authorisation management permissions, with access to all companies.
​

App permissions: Permissions that determine which actions a user may perform, written as a path with pipes, for example Pages | Manage | Organisation | Companies.
​

Company permissions: Permissions that determine which companies within your organisation a user has access to. You can also grant access via company tags.
​

Delegated access: The option to authorise someone to log in and act on your behalf, for example during a longer absence.
​

Paid user: A user for whom monthly costs are charged. In the user overview, the ‘Paid user’ column shows whether paid permissions have been assigned.
​

Single Sign On (SSO): Logging in to Zenvoices via your organisation’s identity provider, for example Okta, Entra or Microsoft.
​

Two-step verification: Extra security when logging in, with a second verification step. Also called MFA. Verification codes can be sent via SMS, email and Google Authenticator.
​

User: Fixed user role with all user permissions except certain management permissions, with access to all companies. Also the general term for someone with an account in your organisation.
​

User role: A group of permissions. If a user gets a role, they get all permissions of that role. The fixed roles are Administrator, User, Submitter, Authoriser and Authorisation manager. You cannot delete fixed roles. You can create additional user roles manually.
​

Accounting terms as used in Zenvoices

Account: The collective name for creditors and debtors in Zenvoices. Many settings, such as the preferred proposal strategy and the default transaction template, are set at account level.
​

Cost center: Dimension that shows where in the organisation a cost item belongs. Available if the accounting system supports it.
​

Cost unit: Dimension that shows what a cost item was incurred for. Available if the accounting system supports it.
​

Creditor: A supplier: an account you receive invoices from, booked in the purchase journal.
​

Debtor: A customer: an account you invoice, booked in the sales journal.
​

Dimension axis: An extra dimension on which you can book in AFAS and Microsoft Dynamics, referred to as dimension axis 1 to 5.
​

Item: A product or service from your accounting or ERP system. You can book on items and use item numbers in line item recognition and transaction templates.
​

Journal: The administrative category in your accounting system in which a transaction is recorded, for example a purchase journal or sales journal. The journal must be known when importing. Multiple purchase and sales journals can be linked to one company.
​

Ledger account: The account on which an amount is recorded in the accounts. Comes from your master data and can be grouped via tags or RGS codes.
​

Non-deductible VAT and private use: Percentages you use at line level to record which part of the VAT is not deductible or which part concerns private use. Only available in combination with Exact Online Belgium.
​

Project: Dimension on which you can book costs. In combination with AFAS Profit, project item, project phase and recharging are also available.
​

VAT charged: Situation in which the VAT is paid by the customer instead of the supplier (reverse charge). Can be set as true or false in rules and templates, and can be viewed in the recognised data.
​

VAT code: The code in your accounting system that defines a VAT rate and VAT treatment. Zenvoices looks up the matching VAT code based on the recognised VAT rate. Per journal, you can set a preferred VAT code per VAT rate. Without a preference, VAT codes of the type excluding VAT get priority.
​

VAT scenario: A setting in your accounting system that determines how VAT is processed, for example domestic, EU or outside the EU (only in certain accounting systems such as Software Gemak and Accountancy Gemak).


Keywords: glossary, definitions, terminology, word list, terms

Did this answer your question?