Ledgerman for Jira Cloud
For PMOs and finance controllers who keep project budgets in a spreadsheet next to Jira. Ledgerman tracks each project's budget, the contracts that commit it and the certificates that prove delivery, by month and by calendar year.
Free for sites with up to 10 users. Runs on Atlassian: your financial data stays in your Atlassian site.
| Budgetapproved, phased by month | 1,200,000.00 | |
|---|---|---|
| Committedcontracts, this year's allocation | 900,000.00 | 75% |
| Actualsacceptance certificates | 540,000.00 | 45% |
| Uncommitted budget | 300,000.00 | |
| Open commitment | 360,000.00 |
Budget → Committed → Actuals
Most budget apps for Jira turn logged hours into cost. Ledgerman works from the documents your finance team already signs.
Layer 1
Each project's approved budget for a calendar year, phased by month. Break it down by category, such as Licences or Services, if you need to.
Layer 2
Contracts with vendors. Each contract's value is phased across the years it runs, so it counts against the right year's budget. A contract can be a Jira issue.
Layer 3
Acceptance certificates: dated amounts of delivered work, each posted against one contract. They are your actuals.
Annual phasing
Budgets are approved per calendar year. Contracts don't follow the calendar. In Ledgerman each contract carries an annual phasing that must add up to its value, and each year's budget is measured against that year's allocation, whatever the signing date.
Certificates fall into a year and month by their date, so you always see what was delivered against what was allocated.
Five checks
Ledgerman records the documents as they are entered and points out where they disagree with each other or with the budget. It never corrects them silently.
Close the books. Set the month your books are closed through, and its budget amounts and certificates are locked. Only people with the "Change closed periods" permission can change them, and every change goes into the audit log.
Who it's for
Every month you rebuild the portfolio picture from a workbook and a pile of certificates.
You need to know what is already committed, not only what has been spent.
You want your project's money in Jira, without asking the PMO for the spreadsheet.
Excel in, Excel out
Upload your budget workbook. A preview shows what will be created, updated or left unchanged, and the rows to fix first, with sheet, row and column. Import never deletes, and running it again is safe.
A project, a portfolio year or all your data to Excel. The acceptance register and the audit log to CSV. Contract statements and a dashboard snapshot to PDF. The full export imports back unchanged.
Free template · Excel · 50 KB
The workbook layout Ledgerman imports, filled with a sample portfolio of five projects. It has monthly budgets per calendar year, contracts with their annual phasing, acceptance certificates, a yearly summary and a monthly budget against actuals. Two contracts carry deliberate errors, so you can see what Ledgerman flags.
Use it in Excel on its own, or import it: replace the Jira keys on the Projects sheet with your own projects' keys, then go to Apps → Ledgerman → Import & Export → Import from Excel.
Inside Jira
Access follows Jira permission schemes. Ledgerman adds its own permissions to Jira: view project financials, edit the budget, edit contracts, record acceptance certificates and change closed periods, plus view portfolio, manage vendors and manage categories across the site.
Security and data
Ledgerman runs on Atlassian. It has no servers of its own, and Sideshore doesn't see your budgets, contracts or certificates in normal operation.
All Ledgerman data is kept in Forge SQL, Atlassian-hosted storage tied to your Jira site. It follows your site's data residency and moves with it.
Ledgerman calls Jira as the person using it, so Jira's own permissions apply. It can't read or change anything that person couldn't.
The only personal data Ledgerman records is the Atlassian account ID of whoever made a change. Names are looked up when the audit log is shown.
Export everything to Excel first if you want a copy. Atlassian keeps the app's data for 28 days after uninstalling, then deletes it.
| Scope | What Ledgerman does with it |
|---|---|
read:jira-work | Checks your permissions before showing or changing anything; lists projects and issue types for setup; reads the contract, certificate and vendor issues it links to, to show their status. |
write:jira-work | Creates a Jira issue for a new contract, certificate or vendor when an administrator has chosen a project for them, and marks linked issues so they show the Ledgerman tab. It doesn't edit or delete your issues. |
write:project.property:jira | Marks a project as tracked so it gets the Financials tab. Used instead of a broader scope that could change project settings. |
delete:project.property:jira | Removes that mark when a project is no longer tracked. Its financial data is kept. |
read:jira-user | Shows people's display names on the Audit tab. |
Before you install
If your costs are mainly people's time, a timesheet-based app will suit you better. Ledgerman is for money that moves through contracts.
Pricing
$0 up to 10 users
Larger sites pay per user per month through the Atlassian Marketplace, which bills for every user on the Jira site. The price per user falls as the site grows: about $1,000 a year at 100 users.
| Users on the site | Per user |
|---|---|
| 1–10 | free |
| 11–100 | $1.00 |
| 101–250 | $0.50 |
| 251–1,000 | $0.20 |
| 1,001–2,500 | $0.10 |
| Above 2,500 | from $0.06 down to $0.02 |
Annual subscriptions cost ten times the monthly price. The Marketplace listing shows the current price for your site.
Support
Public guides for users and Jira administrators, from setup to the Excel layout.
Open the documentation30 minutes on Google Meet: Ledgerman with a sample portfolio, or with your own workbook. Pick a time that suits you.
Book a demoImport your workbook, see its problems, and check this year's numbers in Jira.
Ledgerman