Protected presentation workspace

Confirming Owner access…

Talus Cost Intelligence is isolated from production finance and operational records.

C
Talus Cost IntelligenceOperational cost evidence for ChundR
Concept PreviewHow it worksTalus+ projects
From receipt to field intelligence

Know what the work actually costs.

Talus connects approved expense evidence to the ChundR project, machine, truck or tool that created the cost—then combines it with hours, miles and production for better future decisions.

Demonstration dataNo BILL connectionRead-only conceptNo payment controls
Protected data path
1
Approved receiptBILL remains the financial source of truth.
2
Exact project matchChundR IDs prevent name-based guessing.
3
Human allocationConfirm category and asset; split when needed.
4
Operational metricJoin cost with hours, miles and completed feet.
Total operational cost—Approved receipts + loaded labor
Cost per completed foot——
Receipt-backed spend—Immutable source amounts
Loaded labor—ChundR hours × protected rate

Where the money went

Only verified allocations for this project are included.

Traceable
Talus observation
Calculating operational signal…

    Presentation logic only. Talus may explain and flag; it cannot alter the imported amount, approve an expense or initiate payment.
    Manage labor rates & approve time

    Live work time evidence

    Team Lead and Crew sessions from ChundR · last 30 days. Hours are separate from the demonstration costs above.

    Unpriced hours
    Checking recorded work time…
    Project time is attributed to its project. Shop, travel, maintenance, training, meetings and other work remain overhead until a manager sets allocation rules. No wage rate, payroll amount or BILL receipt is inferred from these sessions.

    Receipt reconciliation

    What would cross from BILL—and what would stay out.

    1 needs review

    Exact-match rule

    A receipt enters project metrics only after its immutable source amount balances and every allocation has a valid ChundR project ID. Unmatched records remain outside totals.

    Split allocation

    One fuel purchase can be allocated across a machine and truck while the original BILL amount remains unchanged and auditable.

    Why this compounds over time

    Every verified cost strengthens estimating, maintenance planning and replacement decisions.

    Future metric
    Machine cost per hour

    Fuel, parts and maintenance divided by approved ChundR machine hours.

    Truck cost per mile

    Fuel and maintenance divided by captured project mileage.

    Asset lifetime cost

    All linked costs across projects without changing the original receipt evidence.

    Future bid intelligence

    Use comparable terrain, production and asset histories to strengthen estimates.

    BILL
    Financial source evidence

    Merchant, date, immutable amount, receipt reference and approval state.

    ChundR
    Operational denominator

    Project, labor hours, machine hours, truck miles, assets and completed footage.

    Human review
    Accountable allocation

    Finance confirms project, category, asset and any split before metrics change.

    Talus
    Explainable intelligence

    Calculates rates, finds outliers and shows the evidence behind every observation.

    Approval boundary for a future integration
    • No bank or payment credentials in ChundR
    • No payments initiated from this module
    • No name-based project matching
    • No unbalanced receipt allocations
    • No employee payroll inferred from receipts
    • No edits to BILL source amounts
    • Owner and future Finance authorization
    • Talus GIS role remains GIS-only
    • Maps 2.0 and ArcGIS geometry unchanged
    • Webhook events rechecked against BILL API

    Integration decision

    This foundation demonstrates the workflow and calculations. Connecting a BILL sandbox, approving the data contract and defining Finance permissions would be a separate controlled phase.

    Approval required