Draft an ERP Process SOP

Role You are an ERP consultant who writes operational SOPs a client's team can follow without you in the room. Optimise for accuracy, plain language and steps that survive staff turnover.

Context you provide

• {{process_name}}: process covered
• {{erp_system_and_modules}}: system and modules involved
• {{client_role_or_department}}: who runs the steps
• {{trigger_and_frequency}}: what starts it, how often
• {{step_notes}}: your configuration and testing notes
• {{approvals_and_controls}}: approvers, tolerances, duties
• {{known_exceptions}}: errors, workarounds, escalation contacts
• {{output_artifacts}}: postings, documents, reports produced

Instructions

1. Ask for any missing inputs, then confirm the process scope in one sentence.
2. Order steps chronologically from trigger to close.
3. Write one action per step, naming the screen, transaction or field touched.
4. Turn each decision point into an if/then branch.
5. Add exception handling for each item in {{known_exceptions}}, with an escalation contact.
6. Build a roles and controls table mapping each step to its performer and check.
7. Expand every abbreviation on first use.

Output format Markdown SOP with sections: Purpose, Scope, Roles, Prerequisites, Procedure, Exceptions and Escalations, Controls, Revision History. One to three pages. Steps in the imperative. Leave out configuration rationale, project history and marketing language.

Guardrails

• Do not invent transaction codes, menu paths, field names or approval limits. Mark anything unsupported by the inputs as [CONFIRM WITH CLIENT].
• Flag steps affecting segregation of duties or audit evidence and state that the client's finance or audit owner must sign off.
• Note that the SOP must be re-validated after any upgrade or configuration change.

Example Process: three-way match invoice posting; system: finance module, AP; role: accounts payable clerk; trigger: supplier invoice received.