Bring purchasing into Jira and JSM.
Keep Finance in control.

Raley Procurement is an Atlassian Marketplace app that turns Jira and JSM into your procurement system. Your business teams raise purchase requests from the JSM customer portal they already use. Those requests route through approval tiers in Jira (by department, budget, product, and spend threshold), become purchase orders sent to suppliers as branded PDFs, and get tracked through goods receipt. Finance sees committed spend in real time on Jira dashboards. POs export to CSV or pull through a REST API to feed your existing ERP, AP, or accounting system. Everything happens inside the Jira instance your teams already log into.

From your Jira project you can: configure your own budgets and watch committed spend track against them in real time; build approval workflows by department, budget, product, and spend threshold (up to three tiers); manage your supplier and product catalog with bulk CSV import (up to 1,000 products); generate branded PDF purchase orders for suppliers; record goods receipt with partial deliveries per order line; see live PO data on Jira dashboard widgets; set Finance, Approval, and Viewer roles so each user sees only what they should; configure multi currency, tax rates (VAT and sales tax), per order delivery addresses, and up to five custom fields per order line; export everything as CSV or pull through the REST API into your ERP, AP, or accounting system.

Yes. Raley Procurement includes a Sales Quotes module alongside Purchase Orders. From inside your Jira project you can create customer facing quotes, set quote numbers and currency, deliver branded PDF quotes by email (works with Raley Email Notifications if installed), and track quote status through Draft, Sent, Accepted, Declined, and Expired. PDF layout, logo, columns, and footer are all customisable. Sales and finance teams work in the same Jira project as your procurement, so the buying side and the selling side of the business live in one place.

Raley uses role based access on top of your Jira project permissions. You assign Finance, Approval, or Viewer roles to users or groups. Business users raise purchase requests from the JSM customer portal (no Jira license required to submit a request). Approvers see what they need to approve. Finance sees the full picture, including committed and actual spend across departments and suppliers. Atlassian admins control configuration. Every action is logged in the Jira issue activity feed for full audit traceability.

Yes. Purchase requests are raised from the JSM customer portal, then approved as POs in Jira. Approvers and admins work in Jira; requesters work in the JSM portal they already know.

Raley is the intake and approval layer. POs and order data export cleanly as CSV, or you can pull data through the REST API to feed your ERP, AP, or accounting system. Your ERP stays the system of record.

Yes. Approval tiers are configured by department, budget, product type, and spend threshold, with up to three approval stages. The underlying Jira workflow is yours to customise too.

Yes. Raley Procurement carries Atlassian’s Cloud Fortified trust mark and participates in the Marketplace Security Bug Bounty Program. The app runs as an Atlassian Connect cloud add on, with no direct database access. Communication is over SSL with JWT authentication. Data is hosted on AWS in Amsterdam and the USA, retained for 60 days after uninstall, then permanently deleted.

Generic approval apps move tickets; Raley generates and tracks the purchase orders themselves, with budgets, suppliers, multi currency, and committed spend dashboards as first class entities. A DIY workflow gives you the issue transitions but none of the procurement data model.