At a glance

• Vendor bills and credit notes, polled from DocuWare on a configurable schedule.
• Header and line-table mapping configured entirely in the UI — no Python.
• Resolve partners, accounts, taxes and currencies by VAT, code, external ID, name or email.
• Optional auto-post and index-field writeback (status, ODOO_REF, error message) to DocuWare.
• Per-document audit trail with redacted error messages — failed docs become an error inbox.
• Dry-run wizard validates filters before going live; one connection per cabinet/dialog flow.

Key features

Multiple import connections

One Accounting Import Connection per (DocuWare connection, file cabinet, dialog) tuple. A single tenant can feed several import flows with different filters, mappings and writeback policies — for example, one connection per document type or per legal entity.

Header mapping with flexible resolvers

Bind any DocuWare index field to any account.move field via the UI. Many2one targets resolve by VAT, code, external ID, name or email, with optional transforms (strip, upper, lower, parse decimal, parse ISO date) and a fallback when no match is found. Required-field validation runs before the move is created.

Table-based booking lines

Each booking’s lines come from a DocuWare Index Table field on the document. Every row in the table becomes one account.move.line, with per-column mapping to account, tax, quantity, price and analytic distribution. Same resolver and transform options as the header.

Round-trip status writeback

After every import attempt — success or error — user-configured rules update DocuWare index fields. Triggers: success, error or always. Value sources: literal string (e.g. STATUS = imported-to-odoo), Odoo move field path (e.g. name, partner_id.vat), connection field, or the redacted error message. DocuWare and Odoo stay in lockstep without a separate sync.

Dedupe + per-document audit

A per-(connection, DocuWare document) link record prevents double imports and surfaces failed documents as the operator’s error inbox. Every event lands in the shared DocuWare log with redacted payloads, capped error messages, and a deep link back to the original DocuWare document.

Auto-post and PDF attach

Optional auto-post posts valid bills the moment they are imported; validation errors flip the link to error state and fire error-triggered writeback. The original PDF is downloaded and attached to the move, with a deep-link URL back to the DocuWare Web Client on the bill form.

Dry-run wizard

Before going live, the Dry run button on each connection runs the same search as the cron without creating anything in Odoo — it returns the matching document count and a preview of the first hits, so you can validate filters and the status field choice in seconds.

The DocuWare connector family

Three modules from codebar Solutions AG, designed to layer. You are looking at the inbound half — turning DocuWare-indexed documents into Odoo bookings.

Module	Direction	Role
DW Authentication	Foundation	OAuth, REST client, audit log, shared schema cache.
DW Master Data	Odoo → DocuWare	Push contacts, accounts, taxes & any Odoo model as indexed records.
DW Accounting Import — you are here	DocuWare → Odoo	Create vendor bills & credit notes from DocuWare documents.

Why DW Master Data is strongly recommended: this module’s VAT, code and email resolvers match DocuWare values against existing Odoo records. Pushing Odoo’s contacts, chart of accounts and taxes into DocuWare via Master Data ensures the values that arrive on inbound documents match cleanly — without it, every missing master is an import error.

Frequently asked questions

Does this module OCR my invoices?

No. OCR happens upstream in DocuWare. This module reads DocuWare index fields and Index Tables that DocuWare’s capture workflow has already populated, and turns them into Odoo bookings. If a value isn’t indexed in DocuWare, it isn’t available for mapping.

Will it auto-create vendors or accounts I don’t have yet?

No. The relational resolvers (VAT, code, external ID, name, email) match DocuWare values against existing Odoo records. Missing masters become import errors that surface in the connection’s error inbox. Install DW Master Data to push Odoo’s contacts, chart of accounts and taxes into DocuWare so the values that arrive on inbound documents are the same ones Odoo expects.

Can it import customer invoices or sales documents?

No. Only vendor bills (in_invoice) and vendor credit notes (in_refund). Customer invoices, sales orders, purchase orders and receipts are out of scope and not on the roadmap — the mapping model and writeback semantics are tuned for accounts-payable inbound.

Permissions

• docuware_accounting.group_docuware_accounting — read access on connections, links and imported moves; sees the menu but cannot edit configuration.
• docuware_accounting.group_docuware_accounting_manager — full CRUD on connections, mappings and writeback rules. Implies account.group_account_manager so managers can also work with imported bills.
• All DocuWare credentials remain on the dw.connection record (gated to base.group_system); this module adds no secret-bearing fields.

Setup walkthrough

Configure a DocuWare connection, create an import connection, map header and line fields, add optional writeback, dry-run, then enable polling.

1. Connect DocuWare. Authorize a connection under DocuWare → Connections via DW Authentication, and click Sync to cache cabinets and dialogs.
2. Create an import connection. Open DocuWare → Accounting Imports and add one entry per (cabinet, document type) flow. Choose the DocuWare connection, file cabinet and search dialog.
3. Pick the trigger. Set the status field on the cabinet and the value that flags a document as ready-to-import (e.g. STATUS = ready-to-import-at-odoo). Add additional AND-combined filters as needed.
4. Map the header. Bind DocuWare index fields to account.move fields. For Many2one targets (partner, journal, account, currency), pick a resolver: VAT, code, external ID, name or email. Add transforms and fallbacks where needed.
5. Map the lines. Pick the DocuWare Index Table field that holds the booking lines. For each column, bind it to an account.move.line field with the appropriate resolver.
6. Add writeback rules. Optional: configure rules that fire on success, error or always — e.g. flip the DocuWare status to imported-to-odoo on success, write the Odoo move name into ODOO_REF, write the redacted error message on failure.
7. Dry-run. Click Dry run to execute the same search the cron will run, without creating any moves. Review the matching count and the preview to validate filters and the status value.
8. Enable polling. Activate the connection and let the cron pick it up (default every 15 minutes, editable in Settings → Technical → Scheduled Actions). Or click Run now for a one-shot poll.
9. Review. Imported bills appear in Accounting with the original PDF attached and a deep link back to DocuWare. Errors surface on the connection’s link list and in DocuWare → Sync Log.

Annotated screenshots will follow in a future release.