{"id":3508,"date":"2026-01-10T22:23:09","date_gmt":"2026-01-10T20:23:09","guid":{"rendered":"http:\/\/xampp.local\/optimus\/?page_id=3508"},"modified":"2026-01-10T22:23:09","modified_gmt":"2026-01-10T20:23:09","slug":"quota-models-explained-simply","status":"publish","type":"page","link":"https:\/\/optimussoftware.de\/en\/quota-models-explained-simply","title":{"rendered":"Quota Models Explained Simply"},"content":{"rendered":"

\n
\n\n\t

Quota Models Explained Simply<\/h1>\n<\/div>\n<\/div><\/div><\/div><\/div><\/section>
<\/div><\/div>
\n
\n\n\t

Quota Models Explained Simply<\/h3>\n<\/div>\n
<\/p>\n

To help you choose the right license, we distinguish between two types of quotas: the master data quota and the transaction quota.
Both models are intentionally kept simple; they differ only in what is being counted.
The offered quota models provide maximum flexibility, allowing you as a customer to choose exactly the model that best matches your individual verification behavior.<\/p>\n

\n<\/div>

<\/div>\n
\n\n\t

Master Data Quota<\/h2>\n<\/div>\n
<\/p>\n

With the master data quota, it does not matter how often you check a VAT ID number, but how many different VAT identification numbers (VAT IDs) you check for the first time within a usage period.<\/p>\n

In short<\/strong>
\u2022 You have a limit per period (e.g. per month) for new, unique VAT IDs.
\u2022 Each VAT ID is counted as \u201cnew\u201d only once within that period.
\u2022 After that, you can recheck the same VAT ID as often as you like without consuming additional quota.<\/p>\n

Simple example<\/strong>
Assume your master data quota is 100 VAT IDs per month:
\u2022 In January, you check 80 different VAT IDs \u2192 everything is within the limit.
\u2022 You recheck one of these VAT IDs 20, 30, or 50 times (e.g. for monitoring purposes) \u2192 it is still counted only once and does not consume additional quota.
\u2022 As soon as you check 100 new VAT IDs for the first time within the same month, the quota is reached.
\u2022 Additional new VAT IDs can only be checked for the first time again in the next usage period (reset).
\u2022 However, you can continue to check all 100 existing VAT ID numbers as often as you like.<\/p>\n

When is this useful?<\/strong>
The master data model is ideal if you:
\u2022 regularly monitor or verify existing customers or suppliers,
\u2022 have few new but many recurring checks,
\u2022 work with a stable master data base (low fluctuation),
\u2022 perform automated and regular checks (e.g. monthly),
\u2022 want to use it in combination with our master data email monitoring.<\/p>\n

Typical use cases: accounting, accounts receivable\/payable management, ERP master data maintenance, continuous compliance checks.<\/p>\n

\n<\/div>

<\/div>\n
\n\n\t

Transaction Quota<\/h2>\n<\/div>\n
<\/p>\n

With the transaction quota, each individual check counts as a separate transaction.<\/p>\n

In short<\/strong>
\u2022 Each executed check consumes one transaction.
\u2022 It does not matter whether it is always the same VAT ID or a different one each time.
\u2022 Every execution counts.<\/p>\n

Simple example<\/strong>
\u2022 You check the same VAT ID 50 times \u2192 50 transactions.
\u2022 You check 50 different VAT IDs once each \u2192 also 50 transactions.<\/p>\n

The decisive factor is solely the number of executed checks or transactions.<\/p>\n

When is this useful?<\/strong>
The transaction model is ideal if you:
\u2022 check many new or different VAT IDs (high fluctuation),
\u2022 mainly perform one-time or occasional checks,
\u2022 prefer a usage-based model where each check is counted individually.<\/p>\n

Typical use cases: new customer verification, project-based or one-time business, lead checks, onboarding processes.<\/p>\n

\n<\/div>

<\/div>\n
\n\n\t

Which option fits your daily work better?<\/h2>\n<\/div>\n
<\/p>\n

\u2022 You frequently check the same VAT IDs?
\u2192 The master data quota is usually more economical, as repeated checks do not count additionally.
\u2022 You constantly check new VAT IDs?
\u2192 The transaction quota is usually better suited, as each check is counted.<\/p>\n

Rule of thumb:<\/strong>
Master data quota counts new VAT IDs per period.
Transaction quota counts each individual check.<\/p>\n

\n<\/div>

<\/div>\n
\n\n\t

Frequently Asked Questions (FAQ)<\/h2>\n<\/div>\n
<\/p>\n

Does merely creating or storing a VAT ID already count toward the quota?
No. Only the actual verification of a VAT ID is relevant for the quota.<\/p>\n

What happens if my quota is exhausted?
Once the quota is reached, further checks cannot be executed, depending on the model, until:
\u2022 the next usage period begins (reset), or
\u2022 additional quota is booked (if available).<\/p>\n

How does the reset work?
At the start of a new usage period, the quota is reset to the booked amount.<\/p>\n

Is a VAT ID really checkable without limits in the master data model?
Yes, within the same usage period. After the first check, each further repetition is not counted again.<\/p>\n

Does every repetition count in the transaction model?
Yes. Each check consumes one transaction, even if it is the same VAT ID.<\/p>\n

Where can I see my current quota status?
After logging in to your customer account under:
Settings \u2192 Billing & Quotas<\/p>\n

\n<\/div><\/div><\/div>

<\/div><\/div><\/div><\/div><\/section><\/p>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-3508","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/optimussoftware.de\/en\/wp-json\/wp\/v2\/pages\/3508","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/optimussoftware.de\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/optimussoftware.de\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/optimussoftware.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/optimussoftware.de\/en\/wp-json\/wp\/v2\/comments?post=3508"}],"version-history":[{"count":1,"href":"https:\/\/optimussoftware.de\/en\/wp-json\/wp\/v2\/pages\/3508\/revisions"}],"predecessor-version":[{"id":3731,"href":"https:\/\/optimussoftware.de\/en\/wp-json\/wp\/v2\/pages\/3508\/revisions\/3731"}],"wp:attachment":[{"href":"https:\/\/optimussoftware.de\/en\/wp-json\/wp\/v2\/media?parent=3508"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}