Optional automation

Feature summary

Automated Features can file Jira tickets for you. Every job on this page is off until you accept it and save. None of them email a customer, none of them spend Rovo credits, and none of them send an invoice to QuickBooks or Xero. That send is a button on the saved invoice, after the books are connected.

When to use it

Turn a job on only after the required setup is done and you have watched one invoice go through by hand. The ops space from setup is required for tickets that are not filed in the accounting space.

How to use it

  1. Open Settings, then Automated Features.

  2. Confirm the ops project key is still the space you created in setup.

  3. Invoice drafts — accept this if LedgerLine should save a draft for each of a client's projects when the month closes, then file one review ticket for that client. The LL Manager still reviews the draft and sends it. Nothing is emailed.

  4. Unfinished work — accept this if you want a ticket when hours in the period are still unfinished.

  5. Payment check — accept this if, some days after an invoice is marked sent, LedgerLine should open a ticket asking whether the payment arrived. Set the days from 1 to 90. The default is 14. The ticket is filed in the accounting space when that key is set, and it is unassigned. If the accounting space is blank, the ticket goes to the ops space, or to the client's first linked project when ticket home is the client, and it is assigned to that client's LL Manager. Finishing the ticket does not mark the invoice paid. A person still chooses Paid.

  6. Choose Save changes.

Related

The accounting handoff itself is not this page. It is the Send to Account Invoicing button, documented in Invoices. Sending a saved invoice to QuickBooks or Xero is also a button, documented in Connect QuickBooks or Xero.