Login Book a Demo
Bill Tracker / Invoice intake

Bring every incoming invoice into one controlled queue.

Vendor invoices arrive through email, text, paper, and portals. Crux brings them into one queue and gives each item project context, ownership, and status, so it is ready to route, approve, and hand to QuickBooks®, which stays the accounting system of record.

The Crux bill queue showing invoices waiting for approval with vendor, assignment, and amount, plus pending bills by vendor.
An invoice in Crux with its vendor, amount, line-item context, assigned approver, and status.
Product interface shown with illustrative data.
By role

Why intake quality matters to every role.

The controller runs intake day to day. Clean intake changes what the project manager and the owner can rely on.

Controller / Office Manager

One place to see every incoming invoice.

Crux surfaces the whole intake queue, what is complete, and what still needs context.

  • Acts on missing information before it stalls approval.
  • Sees readiness for approval and the QuickBooks handoff.
  • Result: less chasing and less duplicate entry.
See the approval workflow
A controller's intake queue in Crux showing invoices waiting by vendor and owner.
Intake queue.
Project Manager

Only the invoices that belong to my job.

Crux surfaces project-specific items with cost and scope context, and a simple way to answer a question.

  • Acts on the items that need a project answer.
  • Sees cost code and scope context on each one.
  • Result: clarity about what actually requires action.
Experience Crux
A project invoice in Crux with vendor, line-item context, and the assigned approver.
Project invoice.
Owner / President

Confidence that the supporting context stays attached to the Crux record.

Crux surfaces the backlog and where items are stuck, so unmanaged cost activity is visible earlier.

  • Acts on bottlenecks before they slow the books.
  • Sees a more reliable project financial picture.
  • Result: fewer surprises from bills that were never tracked.
See what this has produced
A Crux project financial summary showing estimate, cost to date, and an over/under budget figure that reliable intake helps keep accurate.
Project budget.
The intake problem

Invoices arrive from everywhere, with pieces missing.

A vendor invoice can reach a contractor through any of these channels. When it does, the project, the cost code, and the backup often arrive separately, or not at all.

EmailInboxes across the office and field.
Text messageA photo from a phone on site.
PaperHanded over or left in a truck.
Vendor portalsDownloaded and forwarded on.
Field staffReceived at the jobsite.
Office staffReceived at the office.

These are the channels invoices arrive through today. Crux is the one controlled queue those items enter. How each source reaches Crux, submitted in Crux or brought in by your team, is set up for the way you work.

What still arrives incomplete.

Missing project assignment

The bill is not tied to the job it belongs to.

Missing cost code or backup

The line has no code, or the supporting document is elsewhere.

Duplicate entry

The same figures get keyed more than once on the way to accounting.

Unclear ownership

No one is clearly responsible for the next step.

Approval delays

Items wait because no one can see where they sit.

Weak visibility into what is pending

The backlog is hard to see until it becomes a problem.

How intake works

One controlled path from received to ready.

Each incoming invoice moves through the same intake steps in Crux. Each step adds the context the next step needs.

Stage 01

Receive

What the user sees
A new item in the intake queue.
What the user does
Brings the invoice into Crux and opens it.
What Crux records
The item, the date received, and where it came in.
Ready for the next step
An item that exists in one place, not an inbox.
Status: received
Stage 02

Identify project and vendor

What the user sees
The invoice next to the project and vendor fields.
What the user does
Confirms the vendor and assigns the project.
What Crux records
The vendor and the project the bill belongs to.
Ready for the next step
An item tied to the job it affects.
Status: in intake
Stage 03

Add cost and document context

What the user sees
Line items, cost codes, and a place for backup.
What the user does
Codes the lines and attaches supporting documents.
What Crux records
Cost coding and the attachments kept with the item.
Ready for the next step
An item with the financial context an approver needs.
Status: in intake
Stage 04

Flag missing information

What the user sees
What is still required before the item can move.
What the user does
Completes the missing context or asks the right person.
What Crux records
That the item is not yet ready, and why.
Ready for the next step
A complete item, or a clear reason it is waiting.
Status: needs context
Stage 05

Assign or route

What the user sees
Who should review or approve the item.
What the user does
Assigns the responsible approver.
What Crux records
The owner of the next decision.
Ready for the next step
An owned item, with someone accountable.
Status: assigned
Stage 06

Move into approval

What the user sees
A complete, owned item ready for a decision.
What the user does
Submits it into the approval workflow.
What Crux records
That intake is complete and approval is next.
Ready for the next step
Approval decides whether it moves forward.
Status: ready for approval
Product proof

The queue, and one item inside it.

Product interface shown with illustrative data. Together these screens show a controlled queue and one invoice with its context, not a set of unrelated widgets.

The Crux bill queue: invoices waiting for approval with vendor, assignment, and amount, and pending bills grouped by vendor.
See the whole intake queue What is pending, by vendor and by owner.
One invoice in Crux with vendor, amount, line-item context, the assigned approver, and its status, ready for a decision.
Open one item with full context Vendor, amount, cost code, approver, and status together.
What Crux captures

A structured record, not a scanned pile.

Each item carries the fields the workflow needs. Structured intake is what makes routing, approval, job cost, and the QuickBooks handoff reliable.

Invoice recordIllustrative data
VendorKeystone Structural Steel
Invoice numberDEMO-CEDAR-005
Invoice date07/04/2026
Amount$16,996.83
ProjectCedar Ridge
Cost code05 12 00 Structural steel
Commitment / POLinked when present
Supporting documentsAttachments kept with the item
Assigned approverDaniel Mercer
StatusReady for approval

Fields shown here reflect the structured intake record. Only fields the product supports are shown; the exact set is confirmed for your configuration.

Exceptions

Incomplete items stay visible, not buried.

When an item is not ready to approve, Crux keeps it visible with the reason, so the team can resolve it instead of losing it in an inbox.

Missing project

The item has no job assigned, so it shows as needs context until one is set.

Missing backup

No supporting document is attached yet, so the item is not marked ready.

Unclear cost code

A line has no code, so the cost cannot land in the right place until it is set.

Possible duplicate

Because the queue is visible by vendor and reference, the team can catch a possible repeat before it is approved.

Amount to confirm

The amount sits next to the line items and any commitment, so a mismatch is easy to question.

No approval owner

Until an approver is assigned, the item cannot move into approval.

These are the kinds of exceptions Crux keeps visible until they are resolved. This is an illustrative reference of exception types, not a live queue.

What happens next

Intake ends where approval begins.

Bill Tracker creates a complete, owned financial item. Approval then decides whether it moves forward. Once approved, the activity can affect job-cost visibility and reach QuickBooks. The intake work is what makes each of those steps reliable.

QuickBooks boundary

Intake prepares the bill. QuickBooks keeps the books.

  • Bill Tracker controls how invoices enter and how they are prepared.
  • QuickBooks remains the accounting system of record.
  • Approved bills, not every incomplete incoming document, proceed into the accounting workflow.

QuickBooks is a registered trademark of Intuit Inc. Crux is independent and not affiliated with, endorsed by, sponsored by, or certified by Intuit.

See how your invoices move today.

Bring your current intake. A working session maps how invoices reach you now and where a controlled queue would help most. It is a conversation about your process, not a production setup or a data import.

Book a Demo A working session, not a hard sell.