English 
French 
FAQ: Digital Mailroom and IDP (Vault Review)
A Digital Mailroom with IDP collects inbound documents from multiple channels, classifies them, extracts structured data, validates extraction results, and routes documents and data to the right workflow, with a full audit trail from first receipt.
This FAQ covers the technical, governance and compliance dimensions of digital mailroom and IDP, and how it connects to secure intake and long-term preservation
For the solution overview, see digital mailroom automation. For structured external submission before processing, see secure document collection.
Foundational Questions
What is a digital mailroom?
A digital mailroom is the governed inbound processing layer for an organisation’s document intake. Docbyte delivers this through Vault Review, the IDP and document review module in Docbyte Vault. It collects documents from all channels (physical mail, email, portals, APIs, scanners), identifies what they are, captures and validates key data, and routes documents and extracted data to the right team or system, with a traceable audit trail from first receipt.
What is IDP (Intelligent Document Processing)?
IDP is the set of capabilities used to classify documents, extract structured data (including tables and line items), validate extraction results, and improve automation accuracy over time. In practice, IDP combines configurable rules, layout analysis, OCR, ML-based extraction, and human-in-the-loop review for exceptions. The goal is reliable structured output, not just automation for its own sake.
What is the difference between a digital mailroom and an archive?
The Digital Mailroom solution (Vault Review module) focuses on inbound processing and routing: classification, extraction, validation, and workflow. The Docbyte Vault archive focuses on long-term preservation and governance: retention schedules, legal holds, integrity evidence, and defensible deletion. These are complementary capabilities within the same platform. Vault Review processes and routes inbound content; the Docbyte Vault archive preserves the resulting records with their processing evidence for long-term defensibility.
What is the difference between a digital mailroom and Secure Document Collection?
Secure Document Collection (Vault Collect module) is the governed intake channel for external parties (customers, suppliers, CROs, counterparties) submitting documents through a structured portal with completeness enforcement. The Digital Mailroom (Vault Review module) handles the broader inbound processing flow: classifying, extracting and routing what arrives across all channels. Secure collection is typically the entry point for structured external submissions; Vault Review handles the full inbound volume including physical mail, email, and integrations.
Technical Questions
Which channels can a digital mailroom handle?
Physical mail scanning, email and attachments, web portal uploads, mobile capture, API and EDI feeds, shared folders, and batch ingestion from legacy systems. Channel design should match security requirements, submission volumes, and governance level. Not every channel is appropriate for every document type.
How does document classification work?
Classification uses a combination of content analysis (text, structure, keywords), sender/source metadata, configurable rules, and ML-based models. Each classification produces a confidence score; items below the configured threshold go to a human review queue rather than being silently misclassified. Classification taxonomies are configurable per use case and can handle multi-label documents (e.g., an invoice with an attached purchase order).
Can you extract table and line-item data, not just header fields?
Yes. Layout analysis identifies table structures within documents. Line-item extraction captures each row as a discrete record, maps extracted values to a configurable schema, and flags discrepancies (missing fields, arithmetic inconsistencies, out-of-range values). This is essential for invoices (line items against PO), claims schedules, contract annexes, and regulatory submission tables
How do you handle exceptions and low-confidence extraction?
Low-confidence classifications and extractions are routed to a structured human review queue. Items are never silently accepted. Reviewers see the document alongside the extracted values, can correct and confirm, and all corrections are logged with timestamps and user identity. Correction data can feed back to improve future model accuracy. The audit trail of every exception and correction is preserved.
How do you validate extracted data against master data?
Field-level validation rules can check extracted values against master data sources: supplier registries, policy databases, case management systems, ERP master data. Mismatches trigger exception handling. Cross-field checks (e.g., invoice total equals sum of line items, date logic) provide additional validation without master data lookups.
Compliance and Auditability Questions
Do you keep an audit trail of what happened to each document?
Yes. Every significant event is logged automatically and immutably: intake time, channel, classification outcome and confidence, extraction results, validation decisions, user corrections, approval actions, routing decisions, and access events. This creates a complete, traceable processing history for every document, supporting operational control, internal audit, and regulatory compliance.
How does this support invoice processing and financial compliance?
Invoice processing benefits from classification (invoice vs. non-invoice, credit note, reminder), structured extraction (supplier, invoice number, amounts, line items, PO references), validation against supplier master data and POs, routing to AP approval workflows, and preservation of invoices in Docbyte Vault with their processing evidence for statutory retention periods and VAT audit requirements.
How does this support claims handling?
Claims intake involves classifying document types within a submission (claim form, supporting evidence, correspondence), extracting key fields (policy number, claimant identity, incident details, amounts), routing to handlers based on claim type and complexity, and creating an auditable case record with the full processing history. For settled claims, the record and its evidence can be archived in Docbyte Vault for long-term retention.
What about GDPR and data privacy for sensitive content?
Mailroom designs enforce least privilege, role-based access controls, and purpose limitation. Sensitive content (HR documents, medical information, financial data) requires explicit access segregation and data handling controls. GDPR-aligned processing includes defining the lawful basis for processing, respecting data subject rights, and ensuring records flow into governed archives where retention and deletion are controlled.
How does the Digital Mailroom relate to eIDAS when inbound records carry electronic signatures?
When inbound documents carry electronic signatures or electronic seals (e.g., signed contracts, signed invoices, regulatory submissions), eIDAS considerations apply to downstream preservation. The mailroom captures these records with their metadata and provenance; downstream preservation should align with Qualified Electronic Archiving (QeA) requirements to keep the signatures legally defensible over the full retention period.
Integration and Lifecycle Questions
How do mailroom outputs connect to long-term archiving and QeA?
For records with long statutory retention periods, the Digital Mailroom is the intake layer of a preservation lifecycle. The final record, together with its extracted metadata, validation outcomes, and processing evidence, flows into Docbyte Vault, aligned with OAIS principles. Where records carry electronic signatures or seals, downstream archiving aligns with Qualified Electronic Archiving (QeA) under eIDAS, ensuring the evidence needed for future validation is preserved alongside the record.
What is the strategic value of a governed Digital Mailroom?
A governed Digital Mailroom is not just an efficiency tool. It is the foundation of information quality for everything downstream: more accurate IDP because intake data is structured, more reliable automation because validation catches errors early, more defensible archives because the chain of custody is unbroken from first receipt, and lower-cost audit response because processing evidence is captured systematically. The mailroom is where information quality is created, not where it is hoped for.
How do we integrate the Digital Mailroom with our ERP, case management or DMS?
Integration is via REST API, message queues, or dedicated connectors for common platforms. Docbyte delivers extracted data, classification outcomes and routing decisions as structured outputs consumed directly by downstream systems, eliminating manual rekeying. Integration scope (which systems receive which data, how status is updated, how master data is referenced) is defined per workflow.
What is a sensible implementation approach?
Start with the highest-volume, most standardised document type (often invoices). Define the taxonomy, extraction fields, validation rules and exception handling for that type. Go live with a limited scope and channel set. Measure accuracy and exception rates, improve the model, then expand to additional document types and channels. Align with long-term archiving requirements from the start. Retrofitting governance is far more expensive than building it in.
Next step
If you want to evaluate a Digital Mailroom and IDP flow, especially for invoices, claims, case files, or contract-related inbound. Request a short session. We can map your channels, document types, extraction requirements, exception handling, and downstream path to processing and preservation.