Login and permissions
- Confirm account status, assigned roles and applicable MFA requirements.
- Check whether a permission applies to the page, action and underlying record.
- Escalate access requests instead of sharing credentials.
CORE1ERP RESOURCES / KNOWLEDGE BASE
Solve common ERP questions systematically.
Troubleshooting guidance organised by symptom, cause and safe resolution.
PRACTICAL FIELD GUIDE
What matters in knowledge base
Use the guidance below to frame the right questions, set clear responsibilities and move from discussion to a practical next step. Adapt each recommendation to your organisation's policies, regulatory obligations and current systems.
Transactions and balances
- Check document status, posting date, currency and filters.
- Trace source documents and approvals before correcting a balance.
- Use approved reversal or adjustment workflows rather than direct database edits.
Performance and integrations
- Capture the time, action, error message and affected user role.
- Check whether failures are isolated or repeat across a workflow.
- Escalate with reproducible steps while excluding passwords and sensitive records.
DEEPER PRACTICAL GUIDANCE
Diagnose issues systematically
Use the following steps to turn this topic into an actionable internal discussion. Adapt them to your organisation’s size, industry, controls and existing systems.
Capture the symptom
Record the exact page, time, role, expected result and observed result without exposing passwords or sensitive records.
Check scope
Determine whether the issue affects one user, one branch, a specific module or all users.
Review recent changes
Note configuration updates, permission changes, data imports and integrations that may explain the behaviour.
Escalate with evidence
Provide reproducible steps, relevant reference IDs and sanitised logs to the authorised support team.
What your team should produce
Do not repeatedly submit financial or inventory transactions when the first attempt may have succeeded; verify their status before retrying.
QUESTIONS ANSWERED
Frequently asked questions
Why does a report not match a transaction list?
Different filters, posting dates, currencies or document states may explain the difference; reconcile the criteria first.
Should users change database records to fix an error?
No. Use approved application controls and administrator escalation procedures.
FROM INSIGHT TO ACTION
Explore how Core1ERP fits your workflows.
Bring your requirements, approval rules and reporting needs to a focused discussion.