The Challenge
The finance team noticed that certain main accounts had their “Do not allow manual entry” setting modified. However, they could not identify who made the changes or when they happened because database logging was not enabled for this table.
This created risks:
- Lack of accountability for critical financial master data.
- Difficulty in tracing unapproved configuration changes.
- Gaps in audit readiness.
The Solution: Enabling Database Logs
The resolution was straightforward but impactful. By enabling the Database Log feature in D365 F&O, we ensured all updates to sensitive financial tables would be tracked.
Here’s how we did it:
1. Navigate to Database Log Setup
Go to: System Administration > Setup > Database > Database Log Setup.
2. Enable Logging for Specific Tables
Select the following tables:
- Main Account
- Dimension Code
Mark them for Update monitoring.
3. Save and Activate the Setup
Once enabled, D365 starts capturing all modifications for the selected fields.
4. View the Logs
Navigate to: System Administration > Inquiries > Database > Database Log.
Here, the finance team can now track:
- Who made the change
- What was changed
- When it was changed
The Outcome
After implementing this setup:
- All changes to main account settings are now logged and visible.
- Finance and audit teams have greater transparency and control.
- The customer can confidently manage compliance and prevent unauthorized updates.
Key Takeaway
Database logging in D365 F&O is a powerful but often underutilized feature. For sensitive master data like Main Accounts and Dimensions, enabling logging provides an additional layer of governance and auditability.
At MindCurve, we always recommend enabling database logs for critical tables to strengthen internal controls and support financial compliance.
Pro Tip: Review your organization’s setup to ensure database logs are enabled for high-risk tables. A small configuration step can prevent major audit headaches later.
Frequently Asked Questions
Why are database logs important in D365 Finance & Operations? +
They ensure accountability by tracking who made changes to critical financial data. At MindCurve, we’ve seen this significantly reduce audit risks.
Can enabling database logs slow down the system? +
When applied selectively (only to high-risk tables like Main Accounts), performance is not impacted. We recommend a balanced approach.
Which tables should always have database logs enabled? +
Tables like Main Account, Dimension Codes, and other sensitive master data tables. We help clients identify the right ones based on risk.
How do database logs support audit readiness? +
They provide a traceable history of changes — who, what, and when. This eliminates blind spots during internal and external audits.
Is this a one-time setup or does it require ongoing monitoring? +
Setup is one-time, but ongoing review is crucial. At MindCurve, we train finance and IT teams to monitor logs regularly for compliance.