Explain cost per tonne
Bring fuel, spares, contractor, and labour costs together against production quantities.
Mining & quarrying
Mining and quarry operations need to know what was extracted, hauled, crushed, stockpiled, and dispatched, and what it cost. Map production, equipment, fuel, spares, and dispatch records around your site so operations and finance work from one set of numbers.

Built around your business
A mine or quarry produces the same product every day, yet the numbers that matter, tonnes produced, tonnes hauled, fuel burned, and tonnes invoiced, often live with different people. Bringing production, equipment, contractor, and dispatch records into one system lets the site explain cost per tonne and reconcile what left the gate with what was billed.
Bring fuel, spares, contractor, and labour costs together against production quantities.
Compare stockpile movements, weighbridge tickets, and customer invoices.
Keep the quantities and references needed for royalty, licence, and environmental returns.
Solution capabilities to scope
Build the scope around the records your team uses, the decisions it makes, and the exceptions it needs to manage.
01 / SOLUTION AREA
Record extraction, crushing or processing output, and stockpile balances by product and grade, with the weighbridge or survey references your site uses.
02 / SOLUTION AREA
Track fuel issues, maintenance, tyres, and spare parts against each machine so equipment cost per tonne can be reviewed.
03 / SOLUTION AREA
Capture contractor trips, tonnes hauled, and agreed rates, and reconcile contractor bills against recorded work.
04 / SOLUTION AREA
Link dispatch quantities to customer invoices and keep the references needed for royalty, licence, and environmental reporting in your country.
Recommended starting point
SAP Business One covers purchasing, inventory, fixed assets, and finance; production quantities, equipment costing, and royalty reporting are scoped as configuration or add-on work during discovery.
Explore the solution approach ↗An example operational workflow
Follow a typical transaction through the business. We adapt the sequence, approvals, and handovers to your operation during discovery.
Capture extraction and crushing or processing output by product and grade, using shift reports, weighbridge tickets, or survey figures.
Key record
Daily production record
Record fuel, lubricants, and spare parts issued to each machine and contractor, with the stock balance updated at the site store.
Key record
Equipment cost record
Record contractor trips, tonnes moved, and rates so contractor bills can be checked against recorded work.
Key record
Contractor work log
Load customer orders, record the weighbridge quantity, and issue the delivery document with the references your regulator expects.
Key record
Weighed dispatch document
Invoice from dispatch quantities, reconcile stockpiles, and review cost per tonne and royalty liabilities for the period.
Key record
Period reconciliation and invoice
Reporting priorities
Agree report definitions, date ranges, ownership, and source transactions before implementation. Use these industry-specific views as a starting point for your reporting scope.
Implementation approach
Agree the scope and acceptance criteria first, then prepare the data and people who will run the process.
Walk through a real transaction with your operations and accounts teams. Agree the priorities, exceptions, and reports.
Confirm product fit, responsibilities, approvals, and data fields. Scope any add-ons, custom workflows, and integrations.
Clean and map master records, opening stock, balances, and active transactions. Reconcile the data before migration.
Run representative transactions and exceptions with your users. Verify calculations, reports, access, and operating procedures.
Agree the cutover plan and support arrangements. Review early transactions and resolve issues with the responsible team.
Before you decide
Usually, if the equipment exports data or has an interface. Review sample weighbridge and fuel-system output first, then agree the validation rules and how exceptions are handled before scoping the integration.
The scope depends on your users, locations, opening data, approvals, reporting, and integrations. We review a representative workflow and agree what uses standard functionality, what needs configuration, and what needs additional development before preparing the proposal.