EngLedger documentation
Set up EngLedger, understand how your numbers are made and resolve common issues.
Get startedFrom a fresh account to your first report.Start Connect your toolsGitHub, Bitbucket, Jira, Asana and AI metering.Browse setup guides The complete setupAll three pillars configured end to end.Follow the guide
Browse by topic
Setup
Concepts
Guides
- Complete setup: all three pillars from zero
- Scenario: a SaaS team on GitHub and Jira
- Scenario: a Bitbucket and Jira shop
- Scenario: R&D capitalisation end to end
- Reading the period close report
- Reading the ledger reports
- Scenario: rolling out AI spend visibility
- AI spend budgets, limits and enforcement
- The AI governance report suite
- Scenario: running an AI governance review
- Writing ticket and commit classification rules
- Rules cookbook: common setups
- Best practices: getting the most out of EngLedger
Billing
Popular guides
EngLedger gives engineering leaders three connected views of where their engineering money goes:
- AI Spend: meter every AI request, tie the spend to the tickets it shipped and report it beside the labour cost it belongs with. See the AI Spend overview.
- AI Governance: ranked exceptions with dollars attached, honest correlational reporting and a full audit trail. See the AI Governance overview.
- The Ledger: worklogs, commits and pull requests become a classified, reconciled effort ledger for cost, capitalisation and period close. See the ledger overview.
All three stand on your integrations, your people and the identity mapping that attributes work to people. Already up and running? The best practices guide covers the working habits that keep your delivery healthy and the numbers accurate.