The roster brings together every role Humetry's AI workers can take on, across three service areas: build, run and operate. For each role: what the worker owns, and the decisions and approvals your policies reserve for your team. Where a role needs judgement, our consultants take it on.
The marked roles are our first assignments, each with a full profile of its scope, the evidence it leaves and how it is measured. The others open once their work has been demonstrated in a client environment, and the roster grows wherever work can be clearly defined, performed consistently and measured against agreed standards.
Process discovery from documents, tickets and workshops: the process as is and to be, requirements and user stories written to acceptance criteria, the impact on other processes and systems traced.
The priorities and the order of the backlog, the scope of each change, sign-off of the requirement.
A business requirement turned into a functional specification: the process as is and to be, the data and the rules, the screens and the reports, the test cases that prove it, the open questions put to the owner and closed.
Approval of the specification, the priority, the business decision behind it.
The technical design across systems: integration patterns, data flows, fit to the standard and the gaps, the non-functional requirements, the design document every build follows.
Decisions that change the estate, technology choices, exceptions to the client's standards.
A functional specification turned into a change in SAP (ABAP, RAP, Fiori), Oracle (Fusion extensions, PL/SQL) or Dynamics 365 (X++): the technical design, the code, the unit tests and their results, the authorisation and performance checks, the documentation, the transport imported clean to QA.
Code review sign-off, release to QA, the transport to production.
Release testing against approved expectations: test cases from the specification, the run, defects raised with their evidence, regression suites maintained.
User acceptance, the go or no-go for a release.
Automated tests written and kept working (Tricentis Tosca, Selenium, Playwright, the platform's own tools), the suite run on every release, unstable tests found and fixed.
Which processes must be covered before a release, the test data that may be used.
Transport and deployment packages assembled, dependencies checked, change-board packs prepared, release notes written, rollback plans tested.
Change-board approval, the release window, the move to production.
Changes on Salesforce (Apex, Lightning, flows), ServiceNow (scripts, flows, catalogue items) and Workday (integrations, reports, calculated fields), built in a sandbox and moved with the platform's own tools.
Promotion to production, licences and permission sets, anything that changes who can see which data.
Features and fixes in the client's own applications (Java, .NET, Python, JavaScript): the code with its tests, a pull request to the client's repository, the review notes answered.
Merge approval, the release decision, production credentials.
Interfaces built and changed on SAP Integration Suite (CPI and PI/PO), MuleSoft, APIs and EDI: the mappings, the error handling, the monitoring hooks, the interface specification kept current.
New connections to outside parties, certificates and keys, partner agreements.
Reports, data models and pipelines (SQL, SAP BW and Datasphere, Power BI, Tableau): the extract, the transformation and the report, every figure reconciled to its source.
Which data may be combined or shared, access to personal data, the definition of a measure the business reports on.
Tickets triaged and resolved from runbooks, access requests processed within policy, incidents investigated with the evidence assembled.
Change approval, security exceptions.
Joiner, mover and leaver access provisioned to the approved role design, requests checked against segregation of duties, periodic access reviews prepared with the evidence.
Approval of access, exceptions to segregation of duties, privileged and emergency access.
Incidents on business applications diagnosed from logs, dumps and data; workarounds applied within authority; problems traced to their root cause and the fix routed into the build chain.
Data corrections above the delegated limit, emergency changes, what the business is told during an outage.
Job chains and interfaces watched through the day: failures investigated, IDocs and messages reprocessed within policy, the next run protected, the overnight report written.
Rerunning a job that would post financial data twice, changes to schedules, manual postings.
SAP Basis and its equivalents: system health checks, transports imported to non-production systems, technical users and roles maintained, housekeeping jobs, system copies prepared.
Imports to production, kernel and release upgrades, emergency access.
Alerts read and correlated across the client's tools, known events resolved from runbooks, the rest routed to the right team with the evidence attached.
Declaring a major incident, changes to production systems, contact with the client's vendors.
Patch cycles prepared from vendor releases, applied within agreed windows, verified afterwards, every exception recorded with its reason.
Patching business-critical production systems, deferring a critical vulnerability, the maintenance windows.
Provisioning requests carried out from approved templates, backups checked and restores tested, cost and usage reports, idle resources flagged.
New spend above the agreed limit, changes to networks and security groups, deleting data.
First-line security alerts investigated across the client's tools, false positives closed with the reasoning recorded, real ones escalated with the evidence and a timeline.
Containment, declaring a security incident, notifying regulators and customers.
Requisition to purchase order, price and lead-time checks against contracts, confirmations chased, delivery follow-up, supplier queries answered.
Supplier selection, contract award, negotiated terms.
Supplier creations and changes validated against documents and registries, duplicates found, bank details checked through the call-back procedure, the record kept clean.
Approval of a new supplier, bank-detail changes under dual control, blocking a supplier.
Invoice intake, duplicate investigation, two- and three-way matching, variance resolution, supplier follow-up until closed, release within authority, the payment run end to end: proposal, exceptions, run, payment medium, transmission to the bank.
Whatever your policy reserves today: approval of the payment proposal, release at the bank as signatory, supplier bank-detail changes under dual control.
Customer creations and changes validated, tax and credit data checked against their sources, duplicates merged within the rules, hierarchies kept current.
Credit limits, payment terms outside policy, blocking a customer.
Orders captured from email, EDI and portals, validated against pricing, credit and availability, confirmed to the customer, changes managed to delivery.
Pricing exceptions, credit releases.
Order, delivery and invoice queries answered from the systems, returns and claims initiated, escalations routed with the case assembled.
Goodwill, commercial concessions.
Invoice accuracy checks before issue, statements, dunning sequences by policy, promise-to-pay follow-up, account reconciliation with the customer.
Credit limits and holds, negotiated settlements.
Bank, lockbox and remittance intake; receipts matched exact, partial, multi-invoice and on-account; unidentified cash found and cleared; deductions identified and coded.
Write-offs above tolerance, credit decisions, refunds.
A dispute owned from claim to close: evidence assembled, validity judged against contract and policy, the decision obtained, the credit or denial executed, the customer told.
Claims above threshold, settlements, legal escalation.
Asset master proposals, capitalisation from purchase and receipt, depreciation runs checked, transfers and retirements prepared, the register reconciled to the ledger.
Capitalisation policy, impairment decisions.
Contract and order data turned into revenue schedules, allocation proposals, deferrals and releases, period-end revenue entries prepared with their support.
Accounting-policy judgments, material estimates, sign-off.
Account reconciliations, journal preparation and permitted posting, supporting schedules, close-checklist execution, investigation of balance differences.
Accounting policy, estimates, final sign-off of the close.
Recurring reports assembled, movements investigated, every figure traced to source, commentary prepared with the evidence behind it.
Validating explanations, deciding what action to take.
Forecasts consolidated, models updated, scenarios compared, budget packs prepared, assumptions tracked to their owners.
Setting assumptions, negotiating budgets, recommendations.
Control tests executed to the programme, samples pulled and traced, walkthrough evidence assembled, exceptions documented, follow-ups tracked to closure.
Scoping, the opinion, reporting to the committee.
Material and product records created and extended across plants and sales organisations, units, classifications and valuation data checked, obsolete records flagged.
New product introductions, valuation and costing decisions, deleting records.
History cleansed, statistical baseline produced, consensus pack prepared, bias and accuracy tracked, promotion and event adjustments proposed.
The final forecast, commercial assumptions.
Exception messages worked daily, reschedule proposals, shortage investigation, planned orders converted within rules, master-data gaps flagged to their owners.
Planning parameters, expedite spend.
Cycle counts scheduled and reconciled, discrepancies investigated, slow and obsolete stock flagged, transfers prepared, write-off proposals with evidence.
Write-off approval, safety-stock policy.
Production reporting, work-order administration, shortage investigation, downtime analysis, maintenance coordination.
Physical operations, safety, supervisory judgment.
Requisitions opened, interviews scheduled, offer letters prepared from approved templates, background checks tracked, new joiners handed to HR operations.
Hiring decisions, offers outside the approved range, the interviews themselves.
Joiner, mover and leaver transactions, employee data changes verified, benefits administration, letters and documents prepared, policy queries answered.
Hiring, compensation, disciplinary decisions.
Time and absence data validated, inputs reconciled to HR changes, gross-to-net checked against the prior run, exceptions investigated, filings and payment files prepared.
Approval of the run, pay changes, disputes with employees.
A desk belongs on the roster when its work is defined, recurring and measurable, and when the decisions your policy reserves can be written down. Tell us the desk; we come back with the remit, the boundary and what it would take to prove.