Turn invoices and other business documents into validated digital transactions.
Products / SPICE Digital Document Service™
SPICE Digital Document Service™
SPICE Digital Document Service™ (SPICE DDS™) ingests business documents, most often invoices, sent as emails, PDFs and spreadsheets, extracts and validates their data, and converts it into a structured digital message that enters the same P2P or O2C process as EDI, API and portal transactions.
How SPICE Digital Document Service™ turns documents into validated transactions
SPICE Digital Document Service™ (SPICE DDS™) receives PDFs, emailed documents, spreadsheets and other files from trading partners that don't use EDI. It extracts the data, validates it against your masters, the original order and your business rules, transforms it into the format your systems need, and routes anything that needs review through a governed resolution process. The result is validated, ERP-ready transactions for procure-to-pay, order-to-cash and logistics.
- PDF : purchase orders, confirmations and invoices sent as PDF files.
- Email : documents that arrive in an email body or attachment.
- Spreadsheet : orders and updates sent as spreadsheets or CSV files.
- Other documents : scans, images and other files received by email or SFTP.
SPICE Digital Document Service™
- ExtractIdentifies each document and turns its contents into structured transaction data.
- ValidateChecks the data against your masters, the original order and your business rules.
- TransformConverts it to EDI, XML, IDoc, JSON or the structure your ERP needs.
- GovernRoutes anything that needs correction or review through a controlled resolution process.
The problem
Document-extraction tools may capture fields but often stop before business validation, trading partner context, exception resolution and conversion into a transaction the enterprise can process.
SPICE DDS™ is built for AP, procurement and customer order teams whose trading partners use PDFs, email or spreadsheets.
What it does
- Email, PDF and spreadsheet document ingestion
- Context-aware data extraction
- Business-rule validation
- Structured digital message creation
- Exception review workflows
- Native middleware and ERP integration
How SPICE DDS™ works
- Ingest document Identify the trading partner and receive a PDF invoice or customer order from an email or supported upload.
- Extract data Extract line items and references with document and trading partner context.
- Validate Check against master data, order references and configured business rules.
- Create message A reviewer resolves an unmatched item or quantity before the validated data becomes a structured digital message.
- Continue process SPICE™ native middleware transforms the approved transaction for the ERP. SPICE Insight™ tracks status; SPICE Web OMS™ or SPICE Trade™ can continue collaboration.
An explanation of the workflow using representative data; implementation reflects the enterprise rules and integration scope.
For the enterprise and the trading partner
For the enterprise: more consistent execution. Reduce manual entry and carry document-based transactions into the same governed order lifecycle as EDI.
For the trading partner: a clearer way to participate. Keep a familiar starting channel and continue digitally through SPICE Web OMS™ or SPICE Trade™ where appropriate.
Why this approach
Address the process around the technology. OCR and cloud document AI extract fields. SPICE DDS™ adds trading partner context, transaction validation, exception review, transformation and continued collaboration across P2P and O2C.
Its role in the SPICE™ platform
The document-to-transaction channel for email, PDF and spreadsheet activity, working with SPICE Web OMS™, SPICE Trade™, SPICE™ native middleware and SPICE Insight™ rather than creating a separate manual process.
The SPICE™ platform
Where SPICE Digital Document Service™ fits
The highlighted parts run this process. Every other part runs on the same platform. Select any part to explore it.
FAQ
Frequently asked questions
Who is SPICE DDS™ for?
AP, procurement and customer order teams whose trading partners use PDFs, email or spreadsheets.
How does it connect to our existing systems?
The solution is designed around supported enterprise interfaces and the transaction scope. SPICE™ native middleware transforms each approved transaction for your ERP and translates X12, EDIFACT, IDoc and JSON, so trading partners don't change format. SPICE Connect™ can provide connectivity and operational ownership. Your ERP stays the system of record.
Can we start with one process or trading partner group?
Yes. Scope a priority process or trading partner group first, then extend the relevant shared integration, visibility and support services as requirements change.
How long does implementation take?
Timing depends on interfaces, document scope, business rules, deployment needs and trading partner readiness. SPICE™ establishes a rollout plan after discovery; there is no universal go-live promise.
Where does SpicY™ fit?
SpicY™ is built into the SPICE™ platform; it isn't a separate purchase. Embedded SpicY™ assistance is available in applicable SPICE™ workflows for status, explanation, reporting and defined work. Its scope and controls are confirmed in solution design.
Talk to a platform specialist
Turn the invoices you receive into validated transactions
Bring sample invoices, orders and other documents your trading partners send today, and see SPICE DDS™ in your operating model.