Price follows volume. Start with one use case. No big-bang cutover project.
OXS.eco does not sell off-the-shelf packages. We put your quote together individually after the initial call and a requirements review. It is driven by three factors: Number of users, Document volume and intake channels, plus modules and interfaces. The model scales from a small team to a large mid-sized company.
What determines your price: users, volume and intake channels
OXS.eco has no one-size-fits-all package. Three factors shape your custom quote. The number of users and your document volume drive the running costs, the number of intake channels drives the one-off rollout effort.
Number of users
How many people work in OXS.eco day to day, for approvals, case files, search or archiving? The number of users scales with your team size: a mid-sized company with 10 users pays differently than a company with 500.
Document volume
How many documents do you process per month: invoices, vouchers, scans, e-invoices? Volume is billed in blocks of 1,000 documents, and your quote states the rate for each document type.
Intake channels
How many routes do documents take to reach you: email inboxes, scan, upload or SFTP? Each intake channel is configured and tested individually during the rollout. The number of channels drives the one-off rollout effort, not your running costs.
What sets OXS.eco apart from typical enterprise DMS suites
Large DMS vendors offer powerful platforms, but often at project costs and rollout timelines that are out of proportion for a mid-sized company. OXS.eco is built for the German mid-market and scales from a small team to a large mid-sized company: the functional depth that document-heavy core processes need, at a price-performance ratio that fits mid-market budgets.
How you get your quote
No tender process, no requirements catalogue before the first conversation. You move step by step from that initial call to a live process, starting with your most important use case.
Initial call in 15 minutes
We clarify departments, volumes and systems and discuss where OXS.eco fits. The demo on sample data follows in a separate session.
Requirements & scope
Modules, integrations, number of users, document volume, intake channels: out of that comes a concrete written quote.
A start tailored to you
Once you place the order, the timeline depends on your intake channels, your approval workflows and any data migration. How a rollout works →
Common questions about pricing & models
Monthly: user licenses by role, document volume, storage per terabyte and flat fees for interfaces. One-off: the rollout billed by effort, above all the configuration of your intake channels and interfaces. Your written quote lists both separately.
The demo costs nothing: sample documents, a demo system, no obligation. If you want the proof on your own process, you start with a single intake channel as a compact first quote. You pay only for that manageable entry step and extend once it convinces you.
Yes, and that is our preferred approach. Start with accounts payable or e-invoicing, for example, and extend to digital case files, the mailroom or document dispatch once the first use case is established.
That depends on the number of your intake channels, your approval workflows and any data migration. So we do not quote a blanket duration: the first use case goes live, further modules follow in stages.
When OXS.eco is a good fit and when it is not
Four profiles where we typically see strong effects, and two where we advise against it.
CFO of a mid-sized company with a growing document volume
Profile: From 50 to 500 employees, several sites, more than 300 incoming invoices a month, manual Excel lists for tracking early payment discounts.
Why it fits: Pricing scales with volume; Diamant is connected in production, further accounting systems on a project basis on request; early payment discount deadlines are visible, with reminders.
IT management under integration pressure
Profile: An existing system landscape (ERP, CRM, specialist systems), a new requirement from the e-invoicing obligation and PEPPOL receipt, hosting required in Germany.
Why it fits: REST API and a test integration environment after the order, e-invoice receipt by e-mail, upload, SFTP or PEPPOL, hosting in Frankfurt.
Accounting under early payment discount pressure
Profile: Fewer than 50 % of early payment discounts taken, approvals take 5 to 10 working days, plenty of queries asking "where is that invoice?".
Why it fits: Multi-stage approval workflows, notes on anomalies, status per invoice, reminders before early payment discount deadlines expire.
Insurance or freight forwarding with a case-file-driven business
Profile: Claim, contract, order or route case files at the core. High intake volumes from broker mail, e-mail intake or scan.
Why it fits: The case file model is configurable, roles are separated per case file type, broker mail can be processed in a structured way.
A group with its own ECM standard
Profile: An existing group-wide DMS (SharePoint Enterprise, OpenText, Documentum) with a global standardisation requirement.
Why not: OXS.eco does not slot into a mandated group ECM standard. It only makes sense as a departmental solution alongside the group standard.
A micro business with fewer than 10 employees
Profile: Few documents a month, simple bookkeeping, no need for workflows or case file logic.
Why not: OXS.eco is built for mid-sized companies with process complexity. For very small firms the implementation effort and the monthly cost are out of proportion. Our suggestion: lean accounting tools.
Hélène TinetInitial call, demo & onboarding
Quote within three working days.
Book a demo or a process call, describe your process, receive a written quote. You talk to a person from the MAAS team.
Before the quote