Summary
Names, statuses, and settings as they appear in the product. Use this when a step says "open Invoicing" and you need the field, or when a status word does not match what you expected.
Required setup, in order
| Step |
Where |
Done when |
| 1. LL Administrator |
Settings → Permissions |
At least one person is an LL Administrator |
| 2. Approvers |
Settings → Permissions → Approvers |
At least one budget or expense approver is saved |
| 3. Hourly Company Rates |
Settings → Permissions, then Settings → Rates |
An owner is named, or a person cost is already stored |
| 4. LL Manager |
Settings → Permissions |
At least one LL Manager is assigned |
| 5. Ops space |
Settings → Automated Features |
An ops project key is saved |
| 6. Client |
Clients |
At least one client exists and a Jira project is linked |
| 7. Contract rates |
Clients → Client rates |
Every client has a labor category or other bill rate |
| 8. Projects |
Projects |
At least one project exists and none say Needs setup |
| 9. Company setup |
Settings → Company setup |
Display currency is set, and burn basis is confirmed |
Roles
| Role |
What they are for |
| LL Administrator |
Full access, including permissions and company settings. Does not have to be a Jira site admin. |
| LL Manager |
Clients, linked projects, bill rates, and the invoices their capabilities allow. Not wages, unless you also make them a rate owner. |
| LL Executive |
Company views such as profitability and client risk when the edition includes them, and reports. |
| LL Report Generator |
Runs reports. |
| Jira site admin |
Can open permissions before any LL Administrator exists, and can manage permissions after that. |
A capability on the manager policy applies to every LL Manager. The person must reload LedgerLine before a newly checked button appears.
| Capability |
What it allows |
| Create budgets |
Draft and edit project budgets on the client |
| Approve budgets |
Approve those drafts. Separate from create. |
| Create invoices |
Build and save drafts, including credit notes, and send to accounting |
| Approve invoices |
Mark an invoice approved. LedgerLine does not block sending until you turn a separate approval rule on. That rule is not part of the current product. |
| Ship invoices |
Mark an invoice paid. Also allowed to mark sent. |
| Approve expenses |
Approve expenses, on editions that include them |
| Edit client / project bill rates |
The price you charge |
| Edit team member cost rates |
Wages on Settings → Rates |
| Manage clients |
Create and edit clients |
Invoice status
| Status |
How it gets there |
What it means |
| Draft |
Save draft |
Saved. Not with accounting yet. |
| In accounting |
Send to Account Invoicing |
A Jira ticket exists in the accounting space and the PDF is attached. |
| Sent |
Accounting moves that ticket to Done, or someone uses Mark sent only |
Issued. Reopening the ticket does not undo this. |
| Paid |
Paid, by someone with Ship invoices |
Payment recorded by hand. |
| Void |
Void |
Out of receivables. Its worklogs can be billed again. |
There is no bank feed. A payment-check ticket does not set Paid.
Settings map
| Page |
What belongs there |
| First time setup |
The ordered checklist. Buttons jump to the right screen. |
| Company setup |
Display currency, budget burn basis, Confluence archive. One save. |
| Invoicing |
Arrears lock, tax regions, and the accounting project key. |
| Invoice Branding |
Letterheads. An invoice uses the layout and header saved on the letterhead you pick for the project. |
| Rates |
Org defaults, person cost, and, on Advanced, dated rate cards. |
| Automated Features |
Ops space, invoice drafts, unfinished work, payment check. |
| Permissions |
Roles and capabilities. |
| Financial intake |
Advanced. Map JSON from an outside system onto clients and projects. |
| Financial glossary |
Definitions LedgerLine uses for bill, cost, margin, burn, and invoices. |
Editions
Standard includes the dashboard, clients, projects, invoices, credit notes, reports, rates, budgets, and the Confluence archive.
Advanced adds multi-currency conversion, profitability, budget-burn alerts, a cost ledger, client risk, a delivery calendar, expense approvals, and dated rate cards. Those menu items show a lock when the edition is not on.
Optional fields worth setting before the first real invoice
| Field |
Where |
Why |
| Accounting project key |
Settings → Invoicing → Account invoicing |
Without it, Send to Account Invoicing is a cover letter you copy, not a ticket. |
| Tax region |
Settings → Invoicing, then the project |
Applied when that project is billed. |
| Letterhead |
Settings → Invoice Branding, then the project |
Name, address, and logo on the PDF. |
| Project team |
Projects → the project → Team |
The people you choose. Not everyone in the Jira role. |