01
Contractor invoices by project and site
Read contractor and supplier invoices, prepare project and cost-code allocations, and route differences to the named reviewer before posting.
Capability: Accounts payable →For infrastructure
Across projects, assets, and sites. Keep the recurring work moving.
Configure finance and operations workflows around contractor invoices, project records, asset documentation, and reporting. Lieutenant prepares the work and routes exceptions; your project, operations, and finance teams keep approvals.
Sample project · Contractor invoices
- Contractor invoiceProject and cost codeMatched
- Rate differs from contractProject managerFlagged
- Prepared invoice entryFinance approvalWaits for a person
Illustrative example with sample data. Not a customer result or product screen.
For infrastructure owners, operators, and service companies. Systems, data availability, and each workflow are agreed during scoping. Engineering judgments, safety decisions, and regulatory sign-offs remain with your qualified team.
Workflows
The recurring work Lieutenant takes on.
Each workflow links to the platform capability underneath it.
02
Contract terms and supporting records
Extract agreed rates, billing terms, and approval requirements from supplied contracts. Attach the source clauses when a charge needs review.
Capability: Document capture →03
Project spend and commitments
Prepare budget-to-actual and commitment summaries from the records in scope. Surface missing approvals and cost variances for project owners.
Capability: Forecasting and planning →04
Asset and site documentation
Link service agreements, invoices, and supplied maintenance records to the relevant asset and site. Route missing documents to operations.
Capability: Facilities and assets →05
Entity close and reporting
Prepare reconciliations and recurring reporting by entity, site, or project, with exceptions and supporting evidence for finance review.
Capability: Month-end close →06
Leases and renewal dates
Abstract site and equipment lease terms and prepare obligation and notice-date schedules. Your team reviews interpretations and decides next steps.
Capability: Lease abstraction →How it runs
Inputs, work, your review, outputs.
Source systems are confirmed during scoping, not assumed.
01 · Connected inputs
- Contractor invoices
- Contracts and project budgets
- Asset and site records
- Entity ledgers
02 · Lieutenant does the work
- Code by project and site
- Check contract terms
- Prepare spend summaries
- Organize asset evidence
03 · A person reviews
- Invoice exceptions
- Budget changes
- Payment release
04 · You get
- Coded invoice drafts
- Spend summaries
- Evidence and review queue
Illustrative flow. Which systems connect and who reviews is agreed in scope for each engagement.
What you get
- Project- and site-coded invoice drafts
- Contract exceptions with source references
- Project spend and commitment summaries
- Asset and site document registers
- Entity reporting and review queues
Waits for a person · sample scope
| Contractor invoice exceptions | Project manager and finance |
| Budget changes and commitments | Budget owner |
| Asset record exceptions | Operations lead |
| Posting and payment release | Your finance approver |
Illustrative. Signatures, payment release, and vendor decisions always stay with your team.
Related
Pair it with your role or your own process.
Questions
What people ask before a walkthrough.
Which infrastructure businesses is this for?
We scope recurring finance and operations work for infrastructure owners, operators, and service companies around their specific projects, sites, and assets. We confirm the process and available records before agreeing a workflow.
Will we need to replace our project or asset system?
Not by default. We confirm the systems, exports, access, and refresh schedules available to the agreed workflow. We do not assume every project, asset, or accounting system has a native connector.
Does Lieutenant make engineering or safety decisions?
No. These workflows support administrative and financial work. Engineering decisions, safety approvals, and regulatory sign-offs stay with your qualified people.
What gets agreed before we start?
Staffing, source connections, access, reporting cadence, and timing are scoped with you before any work begins. Your team keeps signatures, payment release, and vendor decisions.
Is this a different platform from the other solutions?
No. It is the same platform and review model, configured around the workflows that matter most for your business. Custom workflows are available when yours differ.
Start with the workflow that costs you most.
We'll scope systems, access, reviewers, and timing before anything runs.