In 15 minutes you will see whether OXS.eco fits your process.
A genuine advisory format: you speak with a dedicated contact from the MAAS team who walks through your current process (intake, approval, archive) together with you and shows you exactly where OXS.eco makes a difference.
Take three minutes, most fields are optional. We will get back to you with proposed times for an initial call.
What mid-sized teams ask us about this topic
Answers specific to this section, no marketing phrases, just what we discuss in real projects.
How does the initial call work?
We listen first: your current document types, volumes, bottlenecks and existing systems. Then we show OXS.eco on a use case close to your situation. The initial call takes 15 to 20 minutes, free of charge and online; a deeper demo is arranged in a separate session.
Who should join the initial call?
At least one person from the department (accounting / case handling / the specialist team) and one person from IT. Management is helpful for setting the goal, but not essential.
What happens after the initial call?
You receive a written quote with a module proposal and an effort estimate. No pressure to sign: you get back to us once you have decided.
Do you know our industry?
Our experience is above all in insurance, retail, logistics and freight forwarding, and in aviation, including very large document volumes. Tell us your sector and we will show a comparable process example in the call.
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.