Integrations
Connect Dawmly to your Odoo database and post payroll journal entries to it.
Available from the Growth plan.
What this screen is for
Integrations connects Dawmly to other systems. Today it connects to Odoo: once you connect a database and map your accounts, you can post an approved payroll run to Odoo as a journal entry with one click. The page appears in the side menu only for Growth plan and above, and only for company administrators.
At a glance
- Connectors & Connections lists the systems you can connect and the connections you have made.
- Sync Log lists every job Dawmly ran against a connection, with its status and attempts.
How to connect Odoo
- Open Integrations and, on the Odoo card, click Connect.
- Fill in Odoo URL, Database, Username and API Key, then save. Create the API key in Odoo under your user's account security settings.
- Open the connection's Settings and click Test Connection. Dawmly never shows the API key again after you save it.
- Open Mappings and choose the Odoo account for each payroll part, and the Odoo journal the entry goes into.
How to post a payroll run to Odoo
- Open Payroll and open an Approved or Paid run.
- Click Post to Odoo. Dawmly builds one journal entry for the run, totalled per account and cost centre, and queues it.
- Follow it in Sync Log. The entry lands in Odoo as a draft: review it in Odoo and post it there.
- Clicking Post to Odoo again for the same run does not create a second entry; Dawmly shows Already posted to Odoo.
Notes and limits
- Only company administrators can connect, map and post. The Odoo server must be reachable from the internet; private and local addresses are refused.
- Posting is one way, from Dawmly to Odoo, and manual per run. Nothing is posted when a run is approved.
- A failed post is retried automatically; open it in Sync Log to read the reason and retry it by hand.
- A run with a missing account mapping tells you which payroll parts to map first.
- If the combined entry is too large to send, Dawmly drops the cost-centre split and tells you; if it is still too large, use the CSV or Excel journal export instead.