On this page
Database Structure – Entity Relationship Diagram
Updated 31 October 2026
Aedon.Accounting is built on the Salesforce database, a cloud-based relational database. The managed package has almost 200 objects and more than 20 types of transaction that create ledger entries, so the diagram below is simplified, using the Sales Invoice as an example transaction. It reads from left to right.
Transaction model
Every transaction is a master-detail pair: a header object, such as Sales Invoice, and a transaction object for its lines. When the transaction is posted, its lines create ledger entries.
Master data model
Master data objects hold information that changes less often, such as companies, accounts, products, nominal codes, tax codes, currencies and exchange rates.
Reporting model
- Source data: most reports use the ledger entries. The exceptions are Accounts Receivable and Accounts Payable, which use the Sales Ledger and Purchase Ledger, and the VAT reports, which use the accrual and prorated cash transactions.
- Junction objects: link the transaction objects to the reporting objects, holding the data needed for reports such as aged balances.
- Presentation layer: Aedon’s report types let administrators build their own reports with the standard Salesforce report builder. See Ledger Entries Explained.
Benefits of the Salesforce platform
- Scalability: grows with your data volumes.
- Security: Salesforce’s security and encryption protect your data.
- Customisation: you can add your own fields, objects and relationships.
- Integration: connects with other Salesforce products and external systems.
- Automation: flows and other tools can automate routine tasks.
- Analytics: report on all your data with Salesforce reports and dashboards.
