ERP Log & Forensic Audit Report
ERP Log & Forensic Audit - User Guide
1. Introduction ๐ก๏ธ๐
Trust is built on transparency. The ERP Log Report is the ultimate security layer of ERPCrystal/MFG. It maintains an unalterable, chronological record of every significant action performed within the software. Whether a purchase bill was edited, a customer profile was deleted, or an AI agent was consulted for sales predictions, this module captures the “Who, What, and When” of your organizational data.
โน๏ธ
Purpose of this Report:
- Forensic Auditing: Investigate data discrepancies by viewing the exact history of modifications made to any record.
- Security & Compliance: Meet statutory audit requirements (SOX, ISO) by proving that all financial and operational changes are logged.
- IT Performance Monitoring: Track the health of automated background tasks (Schedulers) and AI agent utilization.
- User Accountability: Review the activity levels of different departments and individual users to ensure productivity and data integrity.
This report is essential for Internal Auditors, IT Administrators, and Business Owners.
2. Log Categories ๐
A. ERP Log (The Activity Trail)
- Operational History: Records every “Insert,” “Edit,” and “Delete” across all ERP modules.
- Modification Notes: Shows the internal data state before and after a change, allowing you to “Digital Trace” any clerical error back to its source.
- Activity Summary: Provides a high-level view of which users are the most active and which modules (Sales, Inventory, Finance) are being updated most frequently.
B. Scheduler Log (The Background Health)
- Automation Monitoring: Monitors the “invisible” parts of the ERPโthe automated scripts that run in the background. Use this to verify that daily backups, automated ledger updates, and scheduled email reports were completed successfully.
C. AI Interaction Log (Agent Audit)
- Smart Usage Tracking: If your organization uses the integrated AI agents, this log tracks the prompts given to the AI and the category of assistance requested.
- Cost Control: Links AI usage to your organizationโs “Credit Balance,” providing a clear view of which departments are utilizing AI resources.
3. Key Forensic Indicators ๐ ๏ธ
- Operation Code: Identifies if a record was Created (C), Modified (M), or Deleted (D).
- Timestamp Precision: Logs the exact second an action occurred, which is critical for resolving disputes about “When” a particular order was processed.
- Doc ID Reference: Every log entry is permanently linked to the specific Record ID in the database, ensuring 100% traceability.
4. Understanding Data Columns ๐
- Date & Time: The precise moment of the action.
- User Name: The unique login ID of the person who performed the action.
- Module (DocType): The area of the ERP where the action took place (e.g., Invoice, GRN, Voucher).
- Operation: The nature of the change (Edit, Delete, etc.).
- Audit Notes: The specific details of the change (e.g., “Changed Rate from 100 to 110”).
- AI Credit Use: For AI logs, shows the resource cost of the interaction.
5. Source Transactions ๐
The reporting engine synthesizes data from:
- ERP One Log: The master security table that serializes all system operations.
- AI System Logs: The central database tracking agent interactions and credit consumption.
- Physical Scheduler Logs: Automated text files generated by background processing units.
6. Best Practices / Tips ๐ก
- The Monthly Security Review: On the first of every month, run a Log Summary for the “Delete” operation across all modules. Investigate why records are being deleted rather than being “Cancelled” or “Reversed” (Reversing is a better accounting practice).
- AI “Prompt” Analysis: Periodically review the AI Log to identify “Best Practices.” If a specific team is getting great results from the AI agent, share their prompt strategies with other departments.
- Ledger Integrity: If a financial balance doesn’t match your expectations, filter the log by the specific Voucher Number. This will show you if any user edited the voucher values after the original entry was made.
- SOX/Statutory Compliance: Always keep a PDF export of a monthโs ERP Log in your “Audit Folder” for external auditors. This proves that you maintain a robust environmental control over your data.