Approvals, period locking and tasks
Approve reports, batches and certificates through defined steps, lock reported periods against change, and track follow-up work as projects and tasks.
A defensible month-end needs more than correct figures: it needs to show who checked them, who approved them, and that they did not change afterwards. In a spreadsheet those controls can end up in email threads and people’s memories. MAX builds them into the records themselves.
Approving reports
Every period report starts as a Draft while data arrives and corrections are made. When it is ready, an authorised user approves it, and MAX records who approved it and when in the report’s log. An approved report keeps the values it was approved with, and if a correction is needed it is reverted to draft, changed and approved again, leaving a trail of what happened.
Reports can be issued as Preliminary and Final versions, each with its own watermark and distribution list. That suits a month-end where preliminary figures are needed before the last assays and surveys are in, and final figures follow once they arrive. AMIRA P754 asks for exactly this kind of control over replacing provisional data with final data.
Approving product and certificates
Bullion pours, product batches and loadings are pending approval until someone checks them, and are then approved or rejected. Certificates of analysis are drafted, approved and, if necessary, voided, so only approved certificates leave site. See bullion, concentrate and product tracking.
Locking what has been reported
Once a period has been reported, its figures should not move. Administrators set a lock date, and values on or before it cannot be edited until the period is deliberately unlocked. Period-end reconciliations are locked too once their figures are final. Locking turns “please don’t change last month” into a control that the system enforces.
Controlled state changes
Where equipment or locations move between states, such as running, standby or breakdown, state workflows define which changes are allowed from each state, so the record of what happened follows the rules your site has set. See downtime and delay accounting.
Projects and tasks
Improvement work and investigations need following up, and the AMIRA P754 code expects investigations into metal accounting problems to be documented and their actions signed off. MAX includes projects made up of tasks, each with a status (to do, in progress, done), a priority, a due date, an assignee and comments. Users see their own work in a My Tasks view, can assign a task to themselves, and mark it done, which records when it was completed.
Projects can hold the same custom fields as the rest of MAX, so an investigation can carry the figures, files and notes behind it alongside the actions taken.
More MAX4METS features
Ready to elevate your metallurgical accounting?
Book a demonstration and see how MAX fits your plant, your data sources and your reporting cycle.