New Hire ERP Checklist and AI Tool Rollout

0%

0 of 35 items complete

12 critical items still open - these are the highest-risk gaps.

Download checklist:

New hire: ERP access and role

Written request from the hiring manager naming job role and siteCRITICALRole mapped to a standard ERP role, not copied from another personCRITICALSegregation of duties check done, for example no create-vendor plus pay-vendorCRITICALUser account created with unique ID, no shared loginsCRITICALApproval limits set for purchasing, expenses or journalsDefault site, warehouse, cost center and printer setMulti-factor or single sign-on enabled where supported

New hire: training and first week

Training sandbox or test company login given before production accessFive core transactions for the role practised with a buddyWhere to find reports, saved searches and dashboards shownHow to raise an ERP support request explainedData entry standards covered: naming, units of measure, item codes30 day check that access still matches actual duties

New hire: AI assistant use

Acceptable use rules for AI tools signed or acknowledgedCRITICALTold which data may never go into public AI tools, such as drawings, pricing and customer dataCRITICALAccess to the approved internal AI assistant, if one exists, granted by roleShown how to check an AI answer against ERP records before acting

Design the AI tool

One specific task chosen with a measurable result, for example quote drafting timeCRITICALData sources listed, with an owner for eachCRITICALRead-only access to ERP agreed first; any write-back requires human approvalCRITICALRoles and permissions of the ERP carried through to the AI toolWhere the model runs decided: cloud API, private cloud or on-premSensitive and export-controlled data classified before design

Build and test the AI tool

Test set of at least 50 real questions with known correct answersCRITICALAnswers cite the ERP records or documents they usedWrong or unsupported answers are measured, not guessedPrompt, model and data version recorded for each test runLogging of questions and answers with user ID enabledLatency and cost per request measured on realistic volume

Roll out

Pilot with five to ten users in one department firstCRITICALUsers told what the tool cannot do and when to ignore itFeedback button or channel for wrong answersOwner named for monitoring accuracy and cost monthlyCRITICALRollback plan if answers prove unreliableReview at 30 and 90 days against the original measure

Aim for every critical item ticked before production access or pilot launch. Open critical items in the access groups are audit findings in waiting; open critical items in the AI groups are the usual cause of tools that nobody trusts.

Review your AI rollout plan

Optional: an expert reads your AI tool design and flags gaps in access, testing and rollout.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Use the first three groups on the day a new employee is hired and the last three when your team starts an AI project. Tick each item as it is done and treat items marked critical as gates. Export the result to PDF to keep as the onboarding record, or to Excel to assign owners and dates. If you onboard many people, copy the groups into your HR workflow so ERP access is part of the standard hire process rather than an afterthought.

ERP onboarding: access is the risk

The common ERP onboarding failure is not training but access. New hires get a copy of a colleague's access, which brings every permission that colleague accumulated. Map the job to a defined role, check segregation of duties, and set approval limits explicitly. In SAP this means roles and authorization objects, in Infor SyteLine user groups and form permissions, in NetSuite roles, and in Oracle Fusion job roles and data security contexts. Review access again after 30 days, since real duties usually differ from the request.

Never share a login between two people
Remove access promptly when someone changes role, not only when they leave
Keep the approval for each access grant on file for audits

Designing AI tools that people use

Efficient AI tools start with one narrow task and a measure, not a general chatbot. Decide what data the tool reads, who owns it, and whether the tool may write anything back. Read-only first is the safe default; if the tool proposes changes, a person approves them. Carry the ERP's role permissions into the tool so a clerk cannot ask for payroll or cost data they cannot see in the ERP itself. Decide early whether the model runs in a cloud API or inside your network, because that choice affects confidentiality, cost and what data you can include.

Testing and rolling out

Build a test set of real questions with known answers before you show the tool to users, and measure wrong and unsupported answers explicitly. Require citations to ERP records so users can verify. Pilot with a small group, give them an easy way to report wrong answers, and name one owner who reviews accuracy and cost monthly. Compare results at 30 and 90 days with the measure you chose at design time. If the tool is not clearly better than the existing report or search, simplify it or stop.

Frequently Asked Questions

What should an ERP new hire checklist include?

A written access request, a defined role instead of a copied profile, a segregation of duties check, a unique login, approval limits, training in a sandbox, and a review of access at 30 days. Add data handling rules for AI tools.

How do I give a new user the right ERP access?

Map the job to a standard role, grant only that role, check for conflicting duties, and set approval limits. Avoid copying another user, since that carries over unneeded permissions that auditors will question.

What is a checklist for building an AI tool?

Choose one task and a measure, list data sources and owners, start read-only, keep ERP permissions, test on real questions with known answers, log usage, pilot with a small group, and review results at 30 and 90 days.

Can an AI tool write back to the ERP?

It can, but only with care. Treat any write as a proposal that a person approves, log it, and restrict it to low risk transactions first. Read-only is the safe starting point for most teams.

Netray builds private AI tools on ERP data with read-only access, role checks and logged answers. If you want a second pair of eyes on your design or rollout plan, we can review it.

Talk to an Expert Explore More Free Tools

Related Tools

On-Prem AI

More AI Agents & Automation tools

See all

New Hire Checklist for ERP and AI: Onboard Users, Build and Roll Out AI Tools