Transaction data enrichments are optional metadata layers you can apply to your transactions for more detailed reporting, classification, and record-keeping.
Jaz offers four types of enrichments, each operating at a different level:
Tracking Tags — hashtags applied at the transaction level for advanced reporting.
Nano Classifiers — classification applied at the line item level for granular analysis.
Capsules — containers that group related transactions together for a specific accounting workflow.
Custom Fields — additional data fields on transactions for record-keeping.
Tracking tags work like hashtags on your transactions. They are a data enrichment tool for advanced reporting.
Tags are applied at the transaction level only (not to individual line items).
You can create tags to categorize transactions by project, department, region, or any dimension meaningful to your business.
In reports, you can filter by tracking tags. Tags do not support grouping.
Go to Settings > Configurations > Tags.
Click + New Tag and enter a name.
Tags can be edited or deleted. Deleted tags are removed from future transactions but remain in historical records.
When creating or editing a transaction (invoice, bill, journal, credit note, or cash entry), select the tag field and choose one or more tags.
You can also apply tags in bulk using the Quick Fix function on selected transactions.
Keyboard shortcut: Press T while editing a transaction to open the tracking tags selector.
Yes. When a tracking tag is set on a scheduler, every recurring entry the scheduler generates will automatically inherit the same tag.
Nano classifiers are a data enrichment tool with a classification intent. They allow you to group line items into named classes within a classifier for more granular reporting.
Classifiers are applied at the line item level only (not to the transaction header).
Example: A classifier called "Department" with classes "Engineering," "Sales," and "Finance" lets you break down expenses by department across any transaction.
Go to Settings > Configurations > Nano Classifiers.
Click + New Classifier to add a new classifier.
Fill in the name for the classifier (e.g., "Department").
Add classes under the classifier (e.g., "Engineering," "Sales," "Finance").
Nano classifiers can be added to line items in:
Invoices
Bills
Customer credit notes (CCNs)
Supplier credit notes (SCNs)
Manual journals (MJs)
Direct cash-in / cash-out
Bank reconciliation adjustments
Fixed assets
Schedulers (invoice, bill, and ledger schedulers)
Yes. When nano classifiers are set on a scheduler's line items, every recurring entry the scheduler generates will automatically inherit the same classifiers.
Yes. Nano classifiers can be displayed on PDF line items, so your customers or suppliers can see the classification directly on printed or emailed documents.
Yes. Assigning nano classifiers to items ensures they are automatically applied to line items in transactions, removing the need for manual assignment each time.
Nano classifiers are supported as filters in reports. You can use them to refine data and drill down into specific classes across your transactions.
Capsules are containers that group related transactions together for complex, multi-step accounting scenarios.
Unlike tracking tags and nano classifiers which are classification tools, capsules represent a specific accounting workflow — they tie together the full set of transactions that make up a single business event over time.
A capsule contains three parts:
Basic details: capsule name, type, and description.
Transactions: invoices, bills, journals, or any mix of entries tied to the capsule.
Schedulers: recurring transactions from any linked schedulers.
Capsules can be used for any complex or multi-step transaction that requires multiple linked entries. Common use cases include:
Prepaid expenses: Annual insurance or subscriptions paid upfront with monthly amortization journals.
Deferred revenue: Upfront customer payments with monthly revenue recognition entries.
Accrued expenses: Month-end accrual journals, reversals, and the supplier bill once received.
Security deposits: Deposit payment, reclassification entries, and refund or offset.
Intercompany transactions: Reimbursements, allocations, and adjustments across related entities.
Fixed asset acquisitions: Recording equipment purchases together with installation, delivery, or setup costs.
Construction-in-progress (CIP): Progress billings, accumulated costs during construction, and final capitalization into a fixed asset.
Renovations or improvements: Contractor bills, capitalization journals, and depreciation after improvements.
Asset disposals: Derecognition entries, accumulated depreciation write-off, and gain or loss on disposal journals.
Adjustments or corrections: Reversal entries and correcting journals grouped for audit clarity.
If a scheduler has a capsule selected, every recurring entry it generates will automatically be created under the same capsule.
This is the key mechanism for scenarios like prepaid expenses and deferred revenue: the initial transaction and all future amortization or recognition entries stay grouped in one place.
In the General Ledger, you can group entries by Capsule — this lets you see the complete lifecycle of a multi-step transaction in one view.
Capsules are the only enrichment that supports group-by in reports. Tracking tags, nano classifiers, and custom fields can only be used as filters or have no reporting impact.
Capsule types are labels that help categorize your capsules (e.g., "Prepaid Expenses," "Deferred Revenue," "Intercompany").
Your organization starts with default types, and you can add, edit, or rename types to match your accounting needs.
Custom fields let you capture additional information on transactions beyond the standard fields.
They are applied at the transaction level and are purely for record-keeping — they do not affect reporting, filtering, or grouping.
Custom fields support multiple data types: text, number, date, and dropdown.
They can be applied to invoices, bills, journals, and contacts.
Yes. Custom fields can optionally be displayed on transaction PDFs, so additional information like PO numbers, reference codes, or internal notes are visible on printed or emailed documents.
Yes. You can configure a custom field as mandatory, which means the transaction cannot be saved without filling it in. This is useful for enforcing data collection policies (e.g., requiring a PO number on every bill).
Q21. How do the four enrichments compare?
Tracking Tags | Nano Classifiers | Capsules | Custom Fields | |
What it is | Hashtags for advanced reporting | Classification for granular analysis | Workflow container for multi-step accounting | Additional record-keeping fields |
Applied to | Transaction level only | Line item level only | Group of related transactions | Transaction level |
Reporting | Filter | Filter | Filter + Group by | No reporting impact |
Shown on PDF | No | Yes (line items) | No | Yes |
Scheduler support | Yes — inherited by generated entries | Yes — inherited by generated entries | Yes — all generated entries land in the capsule | No |
Multiple per record | Yes (multiple tags) | Yes (multiple classifiers) | One capsule per transaction | Yes (multiple fields) |
Can be mandatory | No | No | No | Yes |
Use case | "Tag all marketing expenses" | "Break down by department per line item" | "Group all entries for FY2025 insurance prepaid" | "Record PO number on every bill" |
Yes. A transaction can have tracking tags on its header, nano classifiers on its line items, belong to a capsule, and have custom fields filled in — all at the same time. Each enrichment serves a different purpose and they complement each other.
Tracking tags, nano classifiers, and capsules can all be set on schedulers. Every entry the scheduler generates will inherit them automatically. Custom fields are not available on schedulers.
Here is an example showing how the enrichments work together for a $12,000 annual insurance premium:
Create a capsule — "FY2025 Office Insurance" with type "Prepaid Expenses."
Record the initial bill — $12,000 bill to the insurance supplier. Assign the capsule, add the tag "Insurance," classify the line item as "Operations" using a Department nano classifier, and fill in the custom field "Policy Number" with the insurer's reference.
Create a scheduler — Monthly amortization journal entry ($1,000/month) moving the expense from Prepaid to Insurance Expense. Assign the same capsule, tag, and nano classifier.
Over 12 months — The scheduler generates 12 journal entries. Each one automatically inherits the capsule, the "Insurance" tag, and the "Operations" classification.
Reporting:
Group the General Ledger by Capsule to see all 13 entries (1 bill + 12 journals) together as one workflow.
Filter by the "Insurance" tag to find all insurance-related transactions across the organization.
Filter by the "Operations" nano classifier to see all line items attributed to the operations department.
The Policy Number custom field is visible on the bill PDF sent to the insurer.
