Naming dictionary

One accounting breakdown line of a document. In the QUiCK Public API this is the assignment: it ties an amount to an expense or revenue type, a VAT category and — with advanced accounting — a ledger number.

The flag in the company-info response indicating that accounting identifiers are in use.

A bookkeeping note attached to the document. Only applied when advanced accounting is enabled.

The last day of the accounting (fulfilment) period for continuous services.

The first day of the accounting (fulfilment) period for continuous services, in ISO 8601 format.

The bookkeeping processing state of the document. This is the field to mirror in your own system during incremental sync.

The flag in the GET /2/company-info/ response indicating that advanced accounting is enabled for the company. Only then do the ledger and detailed VAT fields on assignments take effect.

The amount on salary and tax items. Distinct from the financial fields of documents (net / VAT / gross).

Indicates whether the expense has been approved. Set in bulk through /1/expenses/approve/ and /1/expenses/unapprove/.

The endpoint producing the XML export used for tax authority and audit reporting.

The mandatory header on every call, prefixed with Token. A token is bound to exactly one company. A missing or invalid token returns 401; a lack of permission returns 403.

The bank account number of the partner or the cash account. On documents it also appears denormalised as partner_account_number.

The file content of the uploaded document, Base64-encoded. A single call accepts at most 5 items.

Per-item error messages from a bulk operation. On create operations the id field of the error object is the zero-based position in the submitted array — not a record identifier.

A cash register or bank account — the API calls it a paid-through. Its current balance also appears in the pulse summary.

The direction of a VAT category: cost — expense (incoming invoice), revenue — income (outgoing invoice).

The identifier of the company-specific VAT category on an assignment line. Name, code, percentage and VAT territory are populated automatically from the master record.

An optional header that selects the target company explicitly. If you omit it, the company is inferred from the token — the usual case. If the value is not the token's company, the response is 403.

The tax number of your own company in the company-info response. Do not confuse it with the partner's tax_number field.

A partial amendment of an earlier invoice — for example correcting a wrong quantity or amount. The document type is indicated by invoice_class; the correction invoice has the value 4.

The time the document entered the system. For incremental sync this is the field to filter on, combining date_field=created with from_date.

A free-text source marker you can pass in the POST /2/expenses/create/ request. It defaults to public_api; a custom label can identify your own integration.

The identifier of the document's currency (an integer, not an ISO code). If it differs from the company default, an exchange rate is attached as well.

The current balance of a cash account or bank account, as a decimal string. Returned by the pulse summary.

Indicates whether the partner acts as a customer. One partner can be both a customer and a vendor.

Selects which date field the period filter applies to — for example created, fulfilled_at or due_at. Essential for incremental sync.

The default currency of the company. A document in a different currency also carries an exchange rate.

The partner data stored on the document (partner_name, partner_tax_number, partner_city, partner_zip_code, partner_address, partner_country, partner_account_number). Listing therefore needs no separate partner lookup.

An uploaded file (PDF or image) that can be attached to an expense or an income. Handling: GET /1/documents/, attach via /1/documents/attach/, detach via /1/documents/detach/.

The image or PDF attachment belonging to an expense or income. Its presence is signalled by has_artifact; read them from /1/artifacts/expense/ and /1/artifacts/income/.

An email address belonging to the company; files sent here enter the system as documents.

The type of the document as an integer code: 0 — invoice, 1 — storno invoice, 2 — advance invoice, 3 — final invoice, 4 — correction invoice.

The type classification of documents (contract, bank statement, …). Its master data is read from /2/document-types/, and it can also filter the document list.

The Community VAT number used for intra-EU trade, with a country prefix (for example HU12345678). The VAT territory of a document is indicated by the vat_area field: HU, EU or 3RD.

Every error response from the API returns this single text field. There is no error code and no per-field error list — branch your code on the HTTP status code.

The conversion rate applied when the currency differs from HUF, as a decimal string.

The date of the exchange rate used for the conversion (ISO 8601, YYYY-MM-DD).

The document is deliberately excluded from bookkeeping (for example a mistaken submission or a non-deductible item).

An invoice received from an external vendor, waiting to be booked. In the QUiCK Public API this is the expense resource: it is created by uploading the document, after which the system extracts its data.

An email address belonging to the company: incoming invoices sent here appear automatically as expenses. An alternative to uploading through the API.

The cost category (cost centre) on an assignment. Its catalogue is managed under /2/expense-types/ and can be synchronised with an external ERP.

Indicates whether the item has already been included in an accounting export. Set through the /1/expenses/export/ endpoint.

A field for storing an identifier from an external system — use it to link a QUiCK record to a record in your own system.

The identifiers of the items the bulk operation could not process. The detailed reason is in the errors array.

The number of items that errored during a bulk operation.

Limits which fields the response returns. On large lists it reduces the amount of data transferred.

The file name of the uploaded document; a required field alongside the Base64 content.

The time the document was filed. Together with the filing number it belongs to document management.

The filing number assigned by the system, identifying the document in document management.

The date the economic event actually took place, which determines when VAT becomes chargeable. In the API this is the fulfilled_at field; it can also be used for filtering via date_field=fulfilled_at.

The amount including VAT, in the currency of the document. The API returns it as a decimal string, alongside the net and VAT amounts.

Indicates whether an image or PDF attachment belongs to the item. Without one, bookkeeping usually cannot be completed.

The unique integer identifier of every resource. There is no type prefix, and identifiers of different resource types are independent of each other.

The input of bulk operations: the identifiers of the affected records (for example approval, deletion, export).

A sales invoice issued by the business. In the QUiCK Public API this is the income resource, available through the list and update endpoints.

Marks a document with incomplete data — typically recognition could not fill every field and human completion is needed.

Indicates how the document entered the system: upload — file upload, public_api — public API, email — email intake, quick_browser_addon — browser add-on.

The date the invoice was issued according to the document (ISO 8601). Keep it distinct from the fulfilment date and the payment due date.

The invoice number as printed on the document by the issuer. It can also be used to filter lists.

The title of salary and tax items. On salary items it may be a date, marking the posting period.

The identifier of the ledger number on an assignment line. Name and code are filled in automatically from the master record. Only applied when advanced accounting is enabled.

A monthly salary summary. Read with GET /1/monthly-salaries/ or GET /2/monthly-salaries/.

A monthly tax summary used for tax returns. Read with GET /1/monthly-taxes/ or GET /2/monthly-taxes/.

Marks an item that requires accountant review. Only meaningful when advanced accounting is enabled.

The amount excluding VAT, in the currency of the document. The API returns it as a decimal string to avoid floating-point rounding errors.

The full URL of the next page, or null when there are no more items. Following it is the most reliable way to walk a whole list.

Orders results by a field; a - prefix means descending order (for example -created).

The number of the requested page in paginated lists (starting at 1). QUiCK uses page-number pagination, not cursor-based pagination.

The number of items returned per page. A larger value means fewer requests but a slower response; 50–200 is usually optimal.

The opaque pointer used by /2/ pagination, carried in the response's next / previous link. Follow it verbatim: the value is not meant to be constructed or decoded, and nothing should depend on its internal structure.

A customer or a vendor of the business. One partner can be both at the same time — the is_customer and is_vendor fields indicate which. Partner records can be reconciled by tax number (tax_number).

The identifier of the partner master record. When sending a document it takes precedence over inline partner data.

A financial transaction that always belongs to a cash account or bank account, and can be linked to documents through its transactions.

The day by which the invoice must be settled. In the API this is the due_at field; payment state is tracked separately in paid_status (1 — unpaid, 2 — paid, 3 — instalment).

How the document is settled: transfer — bank transfer, cash — cash, card — bank card, cod — cash on delivery.

The identifier of the cash account or bank account the document was settled from.

The settlement state of the document as an integer code: 1 — unpaid, 2 — paid, 3 — instalment.

The end date of the period filter, applied to the date field selected by date_field.

The start date of the period filter. date_field decides which date field it applies to. When syncing, use a small overlap so boundary items are not missed.

The day settlement is planned for — the basis of liquidity planning. It may differ from the legally binding payment due date.

The full URL of the previous page in a paginated response, or null when you are on the first page.

Indicates whether processing of the document has finished. Usable as a list filter.

In the POST /2/expenses/create/ response, the identifiers of the expenses accepted for processing.

A lightweight summary endpoint returning the balances of the company's cash and bank accounts. An ideal first call to verify the token and the connection.

The field holding the data of a paginated response; together with next / previous it forms the pagination envelope. On /1/ endpoints it is an array and comes with a count; on /2/ endpoints it is also an array but without count (cursor pagination). The one exception is GET /2/expenses/, where results is an object: the invoices live under expenses, alongside the reference lists needed to resolve them.

The revenue category (cost centre) on an assignment. Its catalogue is managed under /2/revenue-types/.

Marks the income as reviewed when updating it. Applied with advanced accounting enabled.

A salary item in the company's payroll posting. Managed through /1/salaries/create/, /1/salaries/update/ and /1/salaries/delete/, and the same operations in v2.

Free-text search across lists. The search_fields parameter narrows down which fields are searched.

An additional external reference identifier for cross-system lookups (for example an ERP document number).

The time a user first opened the document. Useful for filtering out new, not yet reviewed items.

A list of text-only tag identifiers on the document. When sent, the list replaces the existing set.

The complete voiding of an earlier invoice. The document type is indicated by the invoice_class field; the storno invoice has the value 1.

The number of successful items in a bulk operation. Its counterpart is failure_count; on a partial success both can be greater than zero.

The identifiers of the items the bulk operation processed successfully.

A freely defined tag on documents and accounting assignments. Managed under /2/tags/; lists can be filtered with with_tag_ids and without_tag_ids.

Master data of the tax codes used for tax returns.

The Hungarian tax number of the partner in xxxxxxxx-y-zz format. It is the partner's tax_number field; on expenses and incomes it also appears denormalised as partner_tax_number.

The number of all items matching the filter — not just those on the current page. Use it to calculate the number of pages. Present only in the /1/ pagination envelope; the cursor pagination of /2/ endpoints returns no total.

The VAT content of a document or assignment, as a decimal string. Together with the net and gross amounts it forms a consistent triple.

The identifier of the VAT category applied to an assignment. The categories (code, percentage, VAT territory) are read from /2/accounting/vat-categories/.

The identifier of the ledger number for the VAT content of an assignment line. Also only applied with advanced accounting enabled.

The percentage rate of a VAT category in the master data. Documents carry the category identifier, not this value.

The flag indicating that VAT period handling is enabled for the company. It determines whether the accounting period fields are meaningful.

The VAT rate applied to a line. On an assignment the vat field holds the VAT category identifier; the categories (code, percentage, VAT territory) are read from /2/accounting/vat-categories/.

The VAT territorial classification of the document: HU — domestic, EU — intra-Community, 3RD — third country.

Indicates whether the partner acts as a vendor. A required field on the partner record.