Know who holds every asset. Prove it to your auditor.
Vouchline for Assets asks every owner in Assets to confirm what they hold, flags assets left on accounts of people who have left, and settles returns when someone leaves. Every decision is sealed in a hash-chained log your auditor can verify without trusting us.
Built on Atlassian Forge · read-only · no data leaves your Atlassian site
$ node verify-package.mjs "Evidence package - 28 Oct 2026.json" Vouchline evidence package — independent verification review Asset confirmation campaign 2026-10-28 [ OK ] chain 5 links, each hash recomputed [ OK ] order numbered without a gap; closing link is last [ OK ] items 3 decided items match their last link [ OK ] closing closing totals equal the decisions before it [ OK ] seal snapshot header matches the seal final chain hash a372e280a0dc6ac8…c924c78eb61a7 RESULT: every check passed
From inventory to evidence in four steps
Inside Jira, on the Assets data you already have.
Scan
Pick a schema and an AQL scope. The app reads the assets every night, including owners kept on a person record, and flags assets without an owner or held by accounts that were deactivated.
Confirm
A campaign, started by hand or every quarter, asks each owner to confirm their assets in one place, or say an asset is not theirs, missing or retired, with a reason.
Settle leavers
When someone leaves, list everything they hold and record for each asset whether it was returned, transferred or written off.
Prove
Download the campaign report or the leaver certificate, with the files behind them and an offline verifier.
Why it holds up in an audit
A tool that says about itself “the data is consistent” is not evidence. Vouchline for Assets is built so that you do not have to take its word for it.
Your auditor can check it without us
Every decision is a link in a SHA-256 hash chain. The downloaded package holds each link in full, and a short script that shares no code with the app recomputes the whole chain.
Owners answer, and say why
Anything other than “confirmed” needs a written reason. A changed answer does not erase the earlier one: it becomes a new link.
Closing is final
After a campaign or a leaver settlement is closed, nobody can change it. Assets without an answer are reported as such, not hidden.
Mapped to ISO/IEC 27001:2022, DORA and NIS2
Four hygiene rules run on every scan; each one names the requirement it supports.
| Rule | What it reports | Requirements |
|---|---|---|
| AS1 | Asset without an owner | ISO 27001 A.5.9 |
| AS2 | Owner account deactivated | ISO 27001 A.5.9 |
| AS3 | Asset held by a deactivated account (possible non-return) | ISO 27001 A.5.11 |
| AS4 | Asset not confirmed within the confirmation period | ISO 27001 A.5.9 · DORA art. 8 |
The mapping is an aid, not a certificate. The app supports the evidence for these requirements; it does not make an organisation compliant with them. Which requirements apply to you is decided by your auditor.
What the app reads — and what it never touches
It reads
- Assets schemas, object types and attribute definitions
- The objects in the scope you choose, with their owner fields
- Whether an owner's Jira account is active
It does not
- Change anything in Assets or Jira — every scope is read-only
- Read work items, requests, comments or attachments
- Send data outside your Atlassian site — no servers of ours, no telemetry
- Store names of people or assets — identifiers and hashes only
Pricing
Bought and billed through the Atlassian Marketplace, like other Jira apps. Free for up to 10 Jira users, with a 30-day free trial for larger sites. Quotes, invoices, taxes and resellers are handled by Atlassian.
Current prices on the Atlassian Marketplace ↗ · How billing works →
Questions people ask first
Does it change our Assets data?
No. The app only reads. Corrections that come out of a campaign — a new owner, a missing asset — are listed in a CSV file you can import into Assets yourself.
Our laptops point to a person record, not to a user. Does that work?
Yes. The owner can be a user field on the asset or a reference to a person record whose user field holds the account — the layout of Atlassian's own IT asset template.
How do owners know they have something to confirm?
The app sends no email, because nothing leaves your Atlassian site. Owners see their assets on the “My assets to confirm” page in Jira; announce the campaign in your usual channel.
Which plans does it need?
Jira Service Management with Assets: Standard, Premium or Enterprise.
Make the next asset audit the last one you rebuild by hand.
Questions before you try it? Write to support@retek.app.
More from RETEK for Jira
Audits under NIS2 and ISO/IEC 27001 also look at who has access to your systems and how you report incidents.