Odoo Documents: a shared drive, OCR digitization, and e-sign in one workspace

What is Odoo Documents?

Odoo Documents is the centralized document management application in Odoo's Productivity category. Per the official Odoo 19 documentation, it lets you store, view, and manage files within Odoo — and is described in the docs as behaving like a shared drive inside the system.

Files and folders are organized into left-rail sections: All (everything you can access), Company (shared across the company, governed by per-folder access rights), My Drive (your personal workspace for files you own or uploaded), Shared with me, Recent, and Trash. You can add folders under Company or My Drive, and nest sub-folders under a parent for deeper structure.

For an SME replacing a patchwork of network drives, shared mailboxes, and scattered attachments, Documents gives every team a single place to find contracts, bills, payslips, and signed agreements — attached to the records they relate to inside Odoo.

Odoo Documents features at a glance

Before the deep dives, here is the full feature set in one view. The capabilities are grouped by what they do — storage and organization, collaboration, finance workflows, and integrations — and each is documented in the official Odoo 19 Documents user guide or the product's features page.

A few notes on what is and isn't bundled: the Documents app itself requires an Odoo Enterprise subscription on Odoo Online/Odoo.sh; the per-folder Automations need Odoo Studio; AI Auto-sort needs the Odoo AI app; e-signatures need the separate Odoo Sign app; and vendor-bill digitization is an In-App Purchase (IAP) cloud service that consumes prepaid credits.

Workspace and folder configuration

Folders in Odoo Documents are more than storage containers. Each folder can carry configuration that determines what happens to files placed inside it:

Actions on Select — custom server-action buttons shown for files inside that folder, so a button like Send for Digitization or Sign appears only where it is relevant.

Automations (requires Odoo Studio) — server actions that run automatically when files are added or edited.

AI Auto-sort (requires Odoo AI) — a custom prompt that organizes files into the folder, tags them, moves them, or creates records such as invoices and bills.

Tags, email aliases, and linked records — files can be tagged on upload and linked to an Odoo record via the Linked to field.

Access is controlled per folder and per file using Viewer and Editor rights, and the Add star action is a per-user favorite that does not change anyone else's workspace. This is a meaningful step up from a flat shared drive where everyone sees everything.

Requesting files from employees, customers, and vendors

One of the most useful day-to-day features is Requesting files. Instead of emailing a PDF back and forth to collect a signed contract, a payslip, or a bank form, you create a request inside Odoo:

Click New > Request, set a Document Name, choose who you are requesting it from (Request To), optionally add a Due Date, pick the target Folder, add Tags, and write a Message. Click Request.

A placeholder appears in the target folder. When the recipient clicks it, they upload the file directly into Odoo — no account on their side, no email attachment gymnastics.

Requests are tracked in the Documents Activity view under a Requested Document column, where you can upload, edit, cancel, or send a reminder email individually, or send a bulk reminder to all outstanding requests.

For an SME onboarding a new hire, collecting vendor W-9s, or pulling in customer credit references, this removes an entire class of email churn.

Built-in PDF tools: split, merge, versions, lock, shortcut

Documents ships with PDF manipulation tools so most file handling never leaves Odoo:

Split PDF — open a PDF, click Actions > Split PDF, click the scissors icon between pages to remove a split, then confirm.

Merge PDFs — multi-select files in a folder (Ctrl-click), click Actions > Merge PDFs, optionally add files from your computer, then confirm. The Odoo 19 documentation explicitly notes that the original PDFs are replaced by the merged version, so merge is a destructive operation on the source files.

File management also includes Duplicate, Move, Rename, Manage versions, Lock (to prevent edits while a file is being reviewed), and Create shortcut (to surface the same file in multiple folders without copying it).

These are small features individually, but together they eliminate the need to bounce files out to a desktop PDF tool just to combine two invoices or pull a page out of a contract.

Embedded spreadsheets: real-time collaboration on live Odoo data

Documents isn't only a file store — it hosts Odoo Spreadsheets natively. New > Spreadsheet creates a sheet that lives inside a folder just like any other file, and per the Odoo 19 documentation it supports permission-based sharing, version history, and discussions through both cell-level comments and the file's chatter thread.

Collaboration uses three roles inherited from the folder or set on the file: Owner (full control, can reassign ownership), Editor (edit, share, comment, download), and Viewer (view and copy a link only). Multiple people can edit simultaneously, and the sheet keeps a version history so changes are traceable — a real step up from emailing a spreadsheet around.

Where it gets powerful is dynamic data. A spreadsheet becomes 'dynamic' the moment it contains a formula that pulls live data from an Odoo model — for example, a pivot table of sales or a list of vendor bills. According to the Odoo 19 documentation, an internal user opening that sheet only sees the rows their own access rights permit, so a sales manager's team-wide sheet automatically narrows to a rep's own deals for that rep. This makes spreadsheets a lightweight BI layer on top of the ERP, not just a calculator.

The one sharp edge to know: dynamic spreadsheets cannot be shared with external (portal) users — the live Odoo formulas have to be removed first. To share outside the company you use File > Share > Freeze and share, which converts every Odoo formula to its current value and strips menu links, producing a static, read-only copy. Downloading as .xlsx does the same freezing. For a finance team that wants to send a vendor a current statement, freeze-and-share is the safe path; for internal review of live figures, dynamic sharing is the faster one.

File centralization: attachments that route themselves

File centralization (Documents > Configuration > Settings) is the connective tissue between Documents and the rest of Odoo. It automatically routes attachments created in other apps into dedicated folders, with tags applied.

It is enabled by default when you install an app, and you can change the target folder or tags per app. The Odoo 19 documentation calls out two important special cases:

File centralization cannot be disabled for Accounting documents. A sub-folder is created automatically for each journal type (Sales, Purchase, Bank, and so on), and the journal name is added as a tag on each document. For Human Resources files, a sub-folder is automatically created for each employee, tagged by document type (Contracts, Payslips, etc.).

Changing the folder or tags only affects new files — existing files are left where they are. And when file centralization is enabled for an app, deleting the related record in that app moves its attachments to Trash rather than deleting them outright.

The practical effect: when a vendor emails a bill to a journal's alias, or a sales rep attaches a spec sheet to a quote, the file lands in the right folder automatically, tagged and linked to its record.

Finance-folder OCR: vendor bills, invoices, and credit notes

Files in the Documents Finance folder can be turned into draft Accounting records. Select the file, click Create Vendor Bill, Create Customer Invoice, or Create Customer Credit Note, then click Send for Digitization.

Odoo's Extract service (an In-App Purchase cloud service) runs OCR and AI on PDFs and images, populates the draft record with fields such as Vendor, Bill Reference, Bill Date, Payment Reference, Recipient Bank, Due Date, Currency, and per-line Product, Quantity, Unit Price, and Taxes, and presents confidence scores so a human can verify before posting.

Digitization is configured under Accounting > Configuration > Settings > Digitization, where you choose Digitize automatically or Digitize on demand per document type. Vendors can be set to Auto-post bills (Always / Ask after 3 validations without edits / Never) when auto-digitization is on.

Pricing is usage-based: per the Odoo 19 documentation, digitizing one document uses one credit. Electronic vendor bills with embedded structured data (such as UBL, factur-x, or country-specific XML e-invoices) are imported directly without OCR and do not consume credits, which matters for businesses in jurisdictions that mandate structured e-invoicing.

The full accounts-payable cycle a bill travels through is best thought of as five stages, each of which Odoo touches: capture the supplier document (email alias, upload, or scanner gateway); create a draft bill via digitization or via PO Auto-complete; connect the bill to its purchase order and receipt history; review the lines, taxes, and references that still need human judgment; then resolve any exceptions before posting. Recognition is not the same as validation — a draft can carry the right vendor and total yet still need line-level review where descriptions merged or a quantity break did not map cleanly. Treating OCR as a way to cut first-pass data entry, not as proof the bill is ready to post, is the realistic operating posture.

Two matching mechanisms complement digitization. PO Auto-complete starts from the purchasing record rather than the invoice: it pulls expected bill lines from a confirmed purchase order, often using received quantities, which is the safer source of truth when the PO already defines the transaction. Three-way matching validates that a bill corresponds to goods both ordered and physically received, flagging discrepancies in quantity or price. It is a verification step, not an approval — it answers 'does this match?' rather than 'is this authorized to pay?' — and the Purchase matching smart button surfaces it right after digitization.

This end-to-end flow is what distinguishes Documents from a generic shared drive: a PDF dropped into a folder becomes a reconcilable accounting record with a couple of clicks, with the document and the accounting entry staying attached to each other for audit.

Odoo Sign integration

Odoo Sign (a separate Productivity app) handles electronic signatures and is tightly wired into Documents:

Start a signature request from any Odoo record via Actions > Request Signature — the related contact is typically added as a signer automatically, and once fully signed, the completed document and certificate of completion are attached to the record's chatter.

Sign can pull PDFs from Documents via Actions > Import from Documents, and a Documents folder can be configured (Actions > Actions on Select > Sign) so PDFs in that folder show a Sign button for direct signing or sending without pre-added fields.

Sign templates can specify a target Documents folder and tags, so fully signed files are saved back into Documents automatically — closing the loop from request to signed, filed copy.

On legal validity, Odoo's documentation states that documents signed with Sign are considered valid electronic signatures in the European Union (under the eIDAS regulation, as simple electronic signatures) and in the United States (under the ESIGN Act and UETA), and meet the requirements in most countries. Odoo positions these as simple (not qualified) electronic signatures — sufficient for most common business documents, but for high-stakes or cross-border contracts treat that as vendor positioning and confirm with local counsel rather than as independent legal advice.

Employee expense receipts and HR files that file themselves

File centralization makes expense reports and HR documents genuinely low-friction, because the filing happens automatically rather than by hand.

Take employee expenses. In the Odoo Expenses app, a rep logs a receipt, submits an expense report, a manager approves it, and accounting posts and reimburses it. Every receipt attached along the way — the photo of the restaurant bill, the hotel folio, the mileage log — is an attachment on an HR-related record. Because file centralization is on for Human Resources, the Odoo 19 documentation confirms that a sub-folder is automatically created for each employee, and files are tagged by document type (Contracts, Payslips, and so on). So a submitted receipt does not sit orphaned in a chatter; it lands in that employee's HR sub-folder, tagged and linked to its expense line, where finance can find it at reimbursement or audit time.

The same routing applies to the rest of the employee file. Contracts, signed offer letters (captured through Odoo Sign), payslips, certifications, and ID documents each flow into the per-employee folder under their type tag. You can even add custom Employee Subfolders by name (comma-separated) so a specific onboarding packet has a predictable home.

For shared company knowledge — process SOPs, policy manuals, training material — Odoo's Knowledge app is the better fit than Documents. Knowledge is a collaborative article library, and per the Odoo 19 documentation its articles are reachable from the form views of various apps, so a helpdesk agent can pull up a troubleshooting article without leaving the ticket. Documents and Knowledge complement each other: Knowledge holds the living, editable text; Documents holds the fixed files (scanned certificates, signed PDFs, exported reports) that those articles reference.

The Dynamics 365 equivalent (and where it differs)

Microsoft splits document management across products because Dynamics 365 is not a single stack. The right comparison depends on which D365 product you run.

Business Central (SME-focused): attachments live in a FactBox on records and support any file type, with in-browser PDF preview. An Attach as PDF action snapshots the current document. By default, files are stored in the BC database, but an External File Storage framework can offload them to Azure Blob Storage, Azure File Share, or SharePoint document libraries to reduce database size. There is no native OCR digitization equivalent to Odoo Documents inside the attachment layer — automation is handled separately via Incoming Documents, e-documents, and Power Automate.

Dynamics 365 Finance (F&O): configurable Document Management uses Document Types (File, Image, Note, URL). Per Microsoft Learn, each document type's storage Location can be set to options including Azure (default external option), SharePoint, Archive (database), or Temp database — with a configurable max file size and a file-type allow-list. This is a per-document-type attachment store, not a workspace-style document manager.

Dataverse / Customer Engagement (Sales, Customer Service): attachments are Notes (Annotation, base64-encoded), modern File columns, or email attachments, all counting against Dataverse file storage. Server-based SharePoint integration is the collaborative layer — enabling it for an entity (Account, Opportunity, Quote, Case, Lead) creates a SharePoint library named after the entity, and per-record folders resolve through SharePointDocumentLocation records. Users get versioning, check-in/out, and direct SharePoint access.

Nearest-equivalent mapping: the shared-drive/workspace concept in Odoo Documents is closest to D365 Customer Engagement plus SharePoint integration. Business Central and Finance offer per-record attachments rather than a workspace. Vendor-bill OCR digitization has no direct D365 equivalent inside the document layer — that gap is filled by Power Automate, AI Builder, or ISV solutions rather than a built-in finance-folder workflow. E-sign has no native D365 equivalent; SharePoint plus Power Automate plus a third-party e-sign tool is the usual path.

Note these capabilities are version- and license-dependent: SharePoint integration in F&O requires the Microsoft-managed cloud (not on-prem SharePoint), and Dataverse SharePoint integration requires tenant licensing and Entra consent. Do not assume universal availability — check your specific D365 edition before scoping a rollout.

Is Odoo Documents good? Where it shines, and its honest limits

Evaluation-stage buyers (a recurring intent in community threads) want a straight answer on where the module earns its place and where it runs thin. Here is the net-useful view, sourced rather than promotional.

Where it shines: as an integrated workspace for an SME already on Odoo, Documents replaces a patchwork of network drives, shared mailboxes, and scattered attachments with one searchable place where files live next to the records they relate to. The vendor-bill-to-draft workflow, per-employee HR sub-folders that file themselves, real-time spreadsheets on live ERP data, and Odoo Sign integration are genuinely differentiating — you would otherwise stitch together three or four tools to get the same coverage.

Limitation 1 — vendor-bill approval is not a native workflow. Odoo does not include a dedicated multi-step vendor bill approval process out of the box. The native controls are partial: Purchase Order approval thresholds (which only govern bills that originate from a confirmed PO), binary posting rights, and period-end Lock Dates. There is no conditional routing by amount, vendor, or department, and no multi-approver chain without configuration. If you need threshold-based or multi-level bill approval, you reach for Odoo Studio approval rules (which lack threshold routing out of the box) or a third-party App Store module — and third-party modules can break on each annual Odoo version upgrade. This is the single most common gap AP teams hit.

Limitation 2 — OCR is recognition, not validation. Digitization reduces first-pass data entry, but a draft bill can still carry the right header and total while needing line-level review where descriptions merged or a quantity break did not map cleanly. Noisy inputs — low-quality scans, phone photos, multi-PO invoices, partial receipts — generate exceptions that a human must triage. Clean, recurring supplier PDFs work well; a messy, high-variability inbox does not.

Limitation 3 — dynamic spreadsheets can't be shared externally. Sheets that pull live Odoo data must be frozen (formulas converted to static values) before an outside contact can see them, and external sharing otherwise errors out. For internal collaboration this is fine; for sending a vendor a live statement you freeze-and-share first.

Limitation 4 — a per-file size cap on Odoo Online. Per the Odoo 19 documentation, each uploaded file on Odoo Online must not exceed 64 MB, which matters if you handle large engineering drawings, video, or scanned batches. (Odoo.sh and on-premise have their own infrastructure-driven limits.)

Limitation 5 — it is a document workspace, not a digital asset management (DAM) system. There is no in-app editing of native Microsoft Office formats, no creative-asset versioning workflows, and no rich media transformation. For marketing/creative asset libraries or deep engineering PLM, pair Documents with a dedicated tool (Odoo PLM covers manufacturing drawings and engineering change orders inside the same system).

Net judgment: for an Odoo-running SME whose pain is 'files are everywhere and bills get keyed in by hand,' Documents is a strong, integrated fit — provided you plan for the vendor-bill approval gap up front. For organizations that need heavy approval routing, enterprise-grade DAM, or a stack that stays inside Microsoft 365, scope those needs deliberately before committing.

Choosing for an SME: integrated vs. modular

The decision is less about which platform is better and more about the operating model you want.

Pick Odoo Documents if you want one integrated workspace — shared drive, OCR digitization, e-sign, file requests, and per-folder automations inside a single system, with accounting attachments that turn into draft bills automatically. The tradeoff is that everything lives inside Odoo.

Pick Dynamics 365 if your organization is already invested in the Microsoft stack — Microsoft 365, SharePoint, Entra ID, Power Platform — and you want document management to flow through those services. Business Central attachments cover day-to-day SME needs; SharePoint integration gives Customer Engagement teams the collaborative layer; Finance document types give F&O teams controlled, per-type storage. The tradeoff is that OCR digitization and e-sign require additional Microsoft or third-party tooling.

As a dual-platform implementation partner, Flectic helps SMEs in Canada, the UK, and the USA choose the right fit and then implement it — with an AI-accelerated delivery model designed to deliver up to 3x faster than a traditional ERP rollout. Book an ERP Readiness Call if you want help scoping either path.

Frequently asked questions