Blog ·
Jira for finance: requests, the close, and the recurring calendar
Jira for finance teams works best as three things in one place: an intake for requests from the rest of the company, a project for the planned work such as budgets and purchases, and a calendar of recurring tasks that never depends on somebody remembering. The first two are what Atlassian's finance templates are built for. The third is where finance teams feel the most pain, because the month-end close, the quarterly review and the annual filing come back on a fixed date and nobody files a request for them. This guide sets up the first two quickly, then spends its time on the third.
Statements about Jira's built-in features and templates are as of October 2026, from Atlassian's own pages.
Why finance ends up in Jira #
Usually because the rest of the company is already there. Engineering and operations track work in Jira, so finance gets asked for approvals, purchase orders and budget numbers in the same tool, or in an email that links to a Jira ticket. Bringing finance in gives the team a queue it can see, a record of who asked for what, and a way to show workload.
Jira suits finance work that is:
- request driven, such as purchase approvals, expense questions and vendor setup;
- made of steps with owners, such as request, approve, order and receive;
- tied to the calendar, such as the close, payroll checks and quarterly filings;
- visible to the business at the level of status, while the numbers stay in the ledger.
It is a weaker fit for the ledger itself, for invoicing, and for anything that must be a system of record for money. Keep those in your accounting software and link to them from the ticket.
Start from Atlassian's finance templates #
Atlassian publishes a set of finance templates for Jira. As of October 2026 its finance template page lists five:
| Template | What Atlassian says it is for |
|---|---|
| Procurement | "Track all purchases from request to receipt." |
| Budget creation | "Align teams during the budget creation process." |
| RFP process | "Select the right vendor and improve the RFP process." |
| Finance service management | "Manage and track budget, spend, and other finance requests." |
| Month-end close | "Simplify the messy month-end close process." |
For most teams the finance service management template is the right first project. It gives you one place for incoming requests, which you can then shape to your own stages. Procurement suits a team that runs a steady flow of purchase requests. The month-end close template gives you a checklist of steps for one close.
Treat any template as a starting point. Rename the statuses to the words your team uses, remove fields nobody fills in, and add the one or two that matter to you, such as the cost centre or the amount band.
Set up the request queue #
The queue is how the rest of the company reaches you. A few choices make it work:
- Give each request type its own work type or label: purchase approval, expense query, new vendor, budget change. Reporting by type shows where the team's time goes.
- Ask for the essentials up front: the amount, the cost centre, and a link to the quote or the invoice. A request with no quote is a conversation, and it can wait for one.
- Assign on intake, even if only to a triage owner. An unassigned request is one everybody assumes somebody else has.
- Keep sensitive matters in a separate project. Payroll, salary and acquisition work should not sit in a queue the whole company can browse.
That fourth point depends on your plan. Atlassian's page on the Free plan says permissions and roles are not customisable there, so a finance team that needs restricted projects should plan on a paid plan.
A workflow for approvals #
Purchase and expense approvals move through the same stages every time, which makes them a good fit for a Jira workflow:
| Status | Who acts | Leaves the status when |
|---|---|---|
| Requested | Requester | The amount, cost centre and quote are attached |
| In review | Finance | The request is checked against budget |
| Approval | Budget owner | The approver signs off |
| Ordered | Finance or procurement | The purchase order is raised |
| Received | Requester | The goods or service are confirmed |
| Done | Nobody | The invoice is matched and filed |
Keep the approval in a status, not in a comment. A status can be filtered, counted and audited. "Approved in the thread" cannot.
The recurring calendar nobody files a request for #
Requests come from people. The recurring tasks come from the calendar, and nobody sends a request for them. Here is a typical finance routine:
| Task | Typical cadence | What goes wrong without a ticket |
|---|---|---|
| Month-end close checklist | Monthly, from the last working day | Steps are done in a different order each month, and one is missed |
| Bank and account reconciliations | Monthly | A difference is found in quarter-end week instead of in week one |
| Accruals and prepayments review | Monthly | Cost lands in the wrong period |
| Expense and card statement chase | Monthly | Receipts arrive after the books are closed |
| Payroll input check | Every pay cycle | A change from HR never reaches payroll |
| Vendor and contract renewal review | Quarterly | An auto-renewing contract renews on old terms |
| Budget versus actual review | Quarterly | Variances are noticed only at year end |
| Tax and statutory filing prep | Per filing date | The work starts under deadline pressure |
| Access review for the finance system | Quarterly | Leavers keep approval rights |
Each of these is small, and that is why they slip. A routine with a ticket has an owner, a due date and a record that it was done. A routine without one has a hope.
The record matters when an auditor asks. "Show me that the bank reconciliation was reviewed every month last year" is answered by a filter: twelve resolved tickets, each with a date, an assignee and notes. If you need a pattern for the checklist inside each ticket, our Jira checklist template guide covers where the steps should live.
Three ways to make the calendar create tickets #
| Create by hand | Jira Automation scheduled rule | Recurring Work Items for Jira | |
|---|---|---|---|
| Effort | Every ticket, every cycle | One rule per task, written once | One rule per task, chosen from a form |
| Schedule | Whoever remembers | Fixed rate or cron expression | Daily, weekly, or monthly on a day or a weekday, every N months |
| "Last working day of the month" | Whoever counts | Awkward in cron | A setting on the rule |
| Lives in | Somebody's calendar | The automation rules list | The finance project itself |
| When it misses | Nobody knows | Check the rule's audit log | Run history with the reason |
By hand #
Fine for a handful of tasks. One person creates the month's tickets on the first working day, ideally by cloning last month's. Our Jira task template guide makes those clones quick. The risk is the one above: the calendar has one owner, and the close does not wait for them to return from leave.
Jira Automation #
Jira's own automation can create a work item on a schedule. Atlassian's trigger reference describes running a rule at a fixed rate or with a cron expression for more complex schedules. That covers a lot of finance routines. The friction is the date: finance runs on "the last working day" and "three days before the filing date", and cron has no word for a working day. Our Jira cron expression guide covers the gaps, and each run counts toward your plan's automation usage, which Jira Automation pricing explains.
A scheduling app #
Recurring Work Items for Jira is built for this job. Its rules are scoped to one project, so the finance team's calendar lives inside the finance project rather than in a site-wide rules list that other admins edit. A project administrator turns it on for the project, and a rule made there creates work only there.
Set up the finance calendar with Recurring Work Items #
- Open the finance project and turn the app on for it.
- Create one rule per task. A quarterly review is a monthly rule repeating every 3 months; a yearly filing prep repeats every 12.
- Pick the day. "The 1st" or "the last Friday of the month" are both choices in the form.
- Set your working days and holidays. When a rule lands on a day off, you choose whether it moves to the next working day, moves back to the last working day before it, or is skipped. Moving back is the one finance usually wants, for work that must be finished before a deadline.
- Write the title with tokens so each cycle's ticket is distinct, for example
Month-end close {{now.monthName}} {{now.year}}. - Fill in the template: the owner, a due date a set number of days after the run, labels, and a description that links the close checklist.
- Add subtasks where the task has steps, such as reconcile bank, post accruals, review variances, sign off.
Create the ticket early. For a filing due on the 20th, schedule the prep ticket a week or two before, and put the real deadline in the due date. The ticket's job is to start the work, not to mark the last possible day.
A rule can be given an end, either a date or a number of runs. That suits work that stops: a project-based reconciliation that runs until a system migration is complete, for instance.
Every run is recorded in the rule's history as created, skipped or failed, with the reason. When an auditor asks whether March's review was raised, the history and the ticket together answer it.
Report on the finance workload #
A finance team in Jira can show its workload instead of describing it. A few saved filters do most of it:
- open requests by type, to show where the time goes;
- requests waiting on an approver for more than a few days, to spot what is stuck;
- this month's close tickets and their status, for the controller.
Our Jira weekly report guide shows how to turn a filter into an emailed summary, which is often all the business needs from finance each week.
When the manual way is enough #
A recurring schedule earns its keep once the calendar is bigger than one person's memory. You probably do not need one if:
- you are a team of one or two with a short list of dates you already track reliably;
- your accounting or close-management software already schedules the tasks and reminds the right people;
- almost all your work is reactive, so the request queue is the whole job.
Once the routine runs to dozens of tasks, or the person who holds the calendar is away for a month, a missed date costs more than the setup.
FAQ #
Is there a Jira template for finance teams? Yes. As of October 2026 Atlassian lists five: procurement, budget creation, RFP process, finance service management and month-end close.
Can Jira run the month-end close? It can hold the checklist, the owners and the due dates for each close. The numbers themselves stay in your accounting system.
Should finance use Jira or Jira Service Management? Jira works for an internal team that takes requests from colleagues. A team that wants a request portal for the whole company, with forms and queues, may prefer Jira Service Management.
Can Jira create the close ticket for me each month? Not on its own from a date. You need a scheduled rule, either in Jira Automation or in an app such as Recurring Work Items for Jira, that creates the ticket ahead of the close.