This element id deprecated. As a single expense can contain entries with different company-cards. See expense-entry-readable for its actual company-card value. Value here is unspecified if multiple company-cards in expense. Main currency type for the company, ie the accounting currency type. Vat code used for this transaction. Vat code used for this transaction, or null if none. If at least one transaction in the voucher has this element, all transactions will be vat coded according to the given definition. If no transactions have this element, vat codes will be assigned automatically based on account number. Optional dimension information for this transaction. Usage of project-element is deprecated, please use dimensions instead. Optional currency information for this transaction. One of the elements should be used. Currency that amount on transaction is specified in. The actual accounting amount will then be automatically determined using the exchange rate on the voucher's date. Explicit currency amount information for this transaction. Amount on transaction is implicitely assumed to be in the accounting currency. The serie that this voucher belongs to. The voucher's number in its given serie. Two vouchers in the same serie can not have the same number within the same accounting year. The description of the voucher The voucher's transaction date The transactions associated with this voucher. The account number for this transaction. Vat code used for this transaction. The internal identification used for this transaction The accounting amount for this transaction. The set of references associated with this transaction, always at least one. On a reference, further detailed information will be found, such as currency amount and any dimension entries. The type of this reference, e.g. where does this reference point? No specific reference, the transaction itself is the reference. This is the default case. The internal identification used for this transaction reference The accounting amount for this reference. The sum of all reference amounts is guranteed to be equal to the transaction's amount. The date from which the tax percentage is valid. Required when tax-percentage is set. If omitted, defaults to January 1st of the current year. The date until which the tax percentage is valid. Required when tax-percentage is set. If omitted, defaults to December 31st of the current year. The date from which the specified monthly-salary is valid from. If omitted, default start date is start of current month. The date from which the specified hourly-salary is valid from. If omitted, default start date is start of current month. Setting this element to true will automatically fetch an EDI-recipient for the given client and apply it if its identities matches strictly. If multiple recipients were found, no EDI-recipient will be set. Optional template to use as default when creating new client invoices with the client. When reading, this value is always set, where "null" means "use a reasonable default template". When writing, omitting this value will set it to "null" when creating, and leave it unchanged with updating. Optional approver to use as default when creating new client invoices with the client. When writing, omitting this value will set it to "none" when creating, and leave it unchanged with updating. When updating, set to null to explicitely clear any previously set value. Omitting this element will leave dimension-entries unchanged when updating Omitting this element will leave client-brokers unchanged when updating Value, if set, must be unique. Value, if set, must be unique within its dimension The dimension entry denoting this user. In other words, to create a dimension reference to this user, use this entry. Non-writable The last date, if any, that this invoice had a payment registered. Unique identifier for this row, read only value. Can be safely ignored when creating or updating client invoices. Unique identifier for reinvocing Id of the supplier invoice the reinvoicing is related to Id of the expense entry the reinvoicing is related to The amount in the invoice's currency that this payment represents. If the invoice's currency is the same as the company's accounting currency, this amount and accounting amount must always be equal. The accounting amount that this payment represents. If the invoice's currency is the same as the company's accounting currency, thus amount and invoice amount must be equal. Used when updating an existing revenue. Provide a <revenue-create> as when creating, together with a message with the reason for this update. If this revenue represents a credit for a prior created revenue, it must be referenced here. Negative revenues can not be created without referencing a debit. A unique identifier for this revenue. If given, the exact accounting amounts that should be used. If not given, final values will be determined using the exchange rate for the given currency on the transaction date. If not set, transaction date will be used. At least one file must be given, to use as basis for the accounting. A unique identifier for this revenue. The bank account that should be used as debtor for this supplier invoice. If none is given, a suitable bank account will automatically be chosen. This is an optional field only relevant if payments are performed from different bank accounts. If unsure, please leave empty. Select bank account associated with the given bankgiro. Select bank account with the given identifier. Vat code used for this account. If omitted, default vat code from account will be used. If null this account will not have vat code. Unique identifier for this account, read only value. Can be safely ignored when creating or updating supplier invoices. Optional when creating/updating. Default value will be used if not set Deprecated and no longer used Optional when creating/updating. Default value will be used if not set Vat percentage used for domestic sales using this product. Optional when creating/updating. Default value will be used if not set Deprecated, se will still be used to set account-nr, if it is not set. For backwards compatibility. When reading all elements will have value of account-nr. Optional when creating/updating. Default values will be used if not set. This field is deprecated and is no longer used. When creating or updating an agreement, this field is ignored. When reading an agreement, its value will always be identical to start-invoice-date. Optional when creating/updating. Empty value will be used if not set Set when reading agreements. Ignored when creating/updating Set when reading agreements. Ignored when creating/updating If activity id is absent, it is the users internal hourly cost for all unspecified activities If activity id is absent, it is the users internal hourly cost for all unspecified activities If price is absent, use activity default price Can be used to approve or deny the invoice, with optional comment. The type of approval can either be "APPROVAL" "DENIAL" or "TIMEOUT". The key (UUID) of the user who last updated the project. Non-writable. The date and time when the project was last updated. Non-writable. Can only be set when creating new project Optional client to use as client instead of "normal" client when creating new client invoices from the project. Omitting this value will set it to default when creating, and leave it unchanged when updating. Setting to null explicitely clears the value. Can only be set when creating new project Can only be set when creating new project Will not set status of project to closed, doing so is another operation. Omitting this element will leave dimension-entries unchanged when updating The offset into the full result that this page represents, 0-indexed. The size that this page was limited to. May have been automatically adjusted compared to user input. This value also always represents the number of returned rows. The total size of all rows. May be used to calculate number of calls required to fetch full result. A bank validate request is used to validate account information according to our internal logic. Select what you want to validate. Validate a BIC and IBAN Validate an account as it would be entered when creating a supplier invoice. Did the validation pass? Please note that a passing validation does not guarantee that the specific account actually exists, it merely means that it passed all passive validation rules such as check digits etc. Used when validation fails to supply a human-readable failure message. Always an empty string when validation passes. If set to true, the following validations are performed: * Bank transaction's full amount must be accounted for * All references revenues must be fully consolidated Recommended to always set this to true for use cases when it is expected that a bank transaction only represents revenues that are paid in full. Information about a revenue and a currency that should be consolidated. If a revenue was created with many different currencies, this element may be repeated. Reference to the revenue to be consolidated. Amount from the bank transaction that this revenue represents, as given in the bank account's currency. For example, if the bank account under consideration is in USD, the amount should be given in the same currency. The amount to consolidate as given in a currency used by the revenue. If more than one currency needs to be consolidated for a single revenue, the revenue can be repeated. If the used currency is fully consolidated with respect to the revenue's remaining amount, currency win/loss will be automatically performed. At least one file must be given, to use as basis for the accounting. Its format must be PDF. The general contract of this construction is that all the given bank transactions and revenues will be fully consolidated. Reference to a revenue to be consolidated. Reference to a bank transaction to be consolidated. If amounts from a previous ledger is known it can be specified here along with a desired account number to be credited. An optional currency win/loss amount that is used for sanity check the final result. At least one file must be given, to use as basis for the accounting. Its format must be PDF. Revenue transaction fees. If there is VAT associated with the fees given in the amount field, use this field to specify. This VAT represents an amount that is assumed to have already been subtracted from bank-transaction-amount. Number of consolidated bank transactions. Number of consolidated revenues. Total accounting amount of consolidated bank transactions. Total accounting amount of consolidated revenues. Reference to the client invoice. Reference to the revenue. Reference to the supplier invoice. The native amount given in a currency used by the distribution.