Use cases

Bill a client from Jira time

Scenario

A consultancy logs delivery time in the client's Jira project. Finance needs a monthly invoice without retyping hours.

Problem

Hours live in Jira. Prices live in a spreadsheet. The invoice is assembled by hand, and nobody can see which hours were already billed.

Solution

  1. Link the Jira project to the client and set labor categories.
  2. Finish the project as Client and billable.
  3. Each month, build the invoice from that period, save the draft, and send it to the accounting space.
  4. When accounting finishes the ticket, the invoice is Sent. When the cash arrives, mark it Paid.

Outcome

The invoice lines are the Jira hours times the contract rate. Accounting gets a Jira ticket and a PDF. The same hours are not billed twice unless someone voids the invoice.

Screenshot needed: a client invoice preview whose lines match Jira hours.

Charge another department

Scenario

IT does work for HR. Nobody outside the company is billed, but IT still needs to show the cost or the internal charge.

Problem

The time sits in a Jira project that looks the same as client work, so it gets mixed into client invoices or ignored.

Solution

  1. Add the internal "client" (the department) and link the Jira project.
  2. On Projects, set billing mode to Internal.
  3. Leave time billable on if you want an internal charge amount, or off if you only want cost.
  4. Read the result on the dashboard for that period. Do not send a customer invoice unless you truly intend to.

Outcome

Internal work stays in the money picture and out of an external client's invoice.

Screenshot needed: a project dialog with Billing mode set to Internal.

Hand the month to accounting without emailing the customer

Scenario

The engagement manager prepares the invoice. Accounting issues it from their own Jira space and their own tools.

Problem

Emailing a PDF from the manager's inbox skips accounting, and the books do not know the invoice left draft.

Solution

  1. Set Account invoicing to accounting's Jira project.
  2. The manager saves the draft and chooses Send to Account Invoicing.
  3. Accounting works the ticket. Moving it to Done marks the invoice Sent in LedgerLine.
  4. Accounting, or anyone with Ship invoices, marks it Paid when the payment is confirmed.

Outcome

The manager does not need an email integration. The status in LedgerLine matches where the invoice actually is: still a draft, with accounting, sent, or paid.

Screenshot needed: the accounting Jira ticket with the invoice PDF attached.