Metadata
Tariff metadata attaches extra codes to a tariff so that, when the tariff becomes an invoice line, that line carries the right information for another system — most often a bookkeeping package. It's how a fee ends up with the correct ledger account or article code when the invoice is exported.
You add it on the Tariff metadata tab of a tariff's business logic card. Each entry has three parts:
- Target (required) — the system the metadata is for (the meta target), chosen from the available services, for example a bookkeeping connection.
- Key (required) — which piece of information you're setting (the meta key), such as an article code or ledger account.
- Value (required) — the value for that key.
Bookkeeping targets
When the target is a bookkeeping service (for example SnelStart), the Key becomes a dropdown of that system's known fields, such as:
- Article code
- Ledger account
- Cost centre
- VAT type
…and the Value is then picked from that system's own list (so you select a real ledger account rather than typing a number). For other targets, Key and Value are free-text.
Why it matters
Without metadata, an exported invoice line may be missing the codes the receiving system needs, and the export can fail or land in the wrong account. Setting it once on the tariff means every line produced from that tariff is tagged correctly, automatically.
The available targets and their keys depend on which integrations your organisation has set up. If a bookkeeping target you expect isn't listed, check with your administrator. For how invoices are actually sent to those systems, see Content distribution.