Build Paperless runs the job and Odoo keeps the ledger. Invoices, bills, purchase orders and payments sync with Odoo, and each project maps to an Odoo analytic account so your Odoo reports can be read job by job.
You connect one accounting system per organisation.
Two-way where it makes sense, one-way where Odoo should stay the source of truth.
Both ways
Odoo partners that are customers or suppliers import as Build Paperless customers and suppliers. Internal partners are skipped. A contact Odoo does not have yet is created when you push a document for them.
Both ways
Invoices you issue push to Odoo as customer invoices. Customer invoices and credit notes from Odoo import back in. Journal entries are never imported.
Both ways
Bills you record push to Odoo as vendor bills, and vendor bills from Odoo import back in.
Both ways
Payments you record push to Odoo. From Odoo, Build Paperless reads the payment status of documents it created.
Both ways
Purchase orders sync both ways, with the project carried on each line.
Out to your accounting system
Each project maps to an Odoo analytic account, and invoice and bill lines carry it, so Odoo reports by job.
Into Build Paperless
Build Paperless reads your Odoo chart of accounts to resolve default income and expense accounts. Nothing is written back to it.
Out to your accounting system
Approved time entries post to Odoo as analytic lines on the project, so labour lands on the same job as the rest of its costs. Workers must be mapped first.
Build Paperless detects the Odoo server version when it connects and handles the differences between Odoo 17 and Odoo 18.
No. Each active project is matched to an Odoo analytic account for you, so lines in Odoo carry the project.
No. Only customer invoices, credit notes, vendor bills, payments and customer or supplier contacts are read. Journal entries are excluded.
No. An organisation connects to one accounting system at a time. Disconnect the current one in Settings before connecting Odoo.
Your Odoo credentials are encrypted before they are stored.