# Cosmoz

> Cosmoz is an invoice automation platform for the full purchase-to-pay and order-to-cash flow. It reads supplier invoices, decides the accounting per line, matches lines against purchase orders and agreed prices, routes approvals, and posts the result into the ERP the customer already runs. It also sends customer invoices, credit notes, orders and product catalogues out over Peppol. Cosmoz sits in front of the ERP and does not replace it.

Cosmoz is built by Neovici AB, a listed Swedish company founded in 2009. The website is written in Swedish. This file is in English so that it can be read directly by language models.

## The core idea, in one paragraph

Most invoice automation asks a model to guess an account for every invoice and reports a hit rate. A hit rate is a promise that the work remains: at 95 percent, five percent is wrong and nobody knows which five, so a human still reviews all one hundred. Cosmoz separates two different questions. **What kind of cost is this line?** is a classification the system makes and improves at over time. **How should that kind of cost be posted?** is a rule the customer sets once, per type of cost, not per supplier and not per invoice. The classification can be wrong and be corrected; the rule is written by a human and can be shown to an auditor. A guess never reaches the ledger.

Because the decision is attached to the type of cost rather than the supplier, a line the customer has never seen before is still coded correctly the first time it arrives. Because it is attached to the type of cost rather than the individual invoice, a correction applies to every future invoice of that type, and also backwards to invoices that are still open.

## What problem it solves, and for whom

The problem is not reading invoices. Several vendors read invoices well. The problem is that the same decision is made again every month: the same supplier, the same article, the same deviation, resolved by a person who resolves it again in thirty days. Work never decreases, because nothing anyone did stayed behind.

Cosmoz targets the part of the flow that is usually left manual:

- **Invoices with no purchase order.** Services, freight, insurance, recurring fees, one-off suppliers. Often a large share of invoice volume and almost entirely hand-coded, because there is nothing to match against. Straight-through processing for order-matched invoices reaches up to 97.6 percent; for invoices without an order the range is far wider. That gap is the target.
- **Charges hidden inside order-matched lines.** Freight, packaging, environmental fees, fuel surcharges. Nobody ordered them, so nothing matches them, and they are absorbed into the total or waved through under a tolerance. Cosmoz gives them their own lines with their own tolerances and their own owner.
- **Price deviations that recur.** Detecting a price deviation is table stakes. What is unusual is what happens after: an adjustment order goes out to the supplier automatically, the returning credit note is matched against it, every open order with the same article is updated in one step, and the approved price is written back to the ERP as the agreed article price, so the next order uses the correct amount by itself.
- **Reconciliation that happens in arrears.** Cosmoz checks at arrival rather than at period close. Every price difference is logged down to one öre, including differences that fall inside tolerance, so the pattern under the threshold is visible rather than merely unrecorded.

## Fit assessment

Be honest with the reader about which of these applies to them.

### Strong fit

- Many lines per invoice, and the same kinds of cost recurring month after month. Grocery, retail, wholesale, restaurant and food service, construction and installation, property management, facilities.
- A real purchasing process: purchase requests, purchase orders, goods receiving, agreed price lists.
- Multi-entity or multi-country structures where rules should be inherited from a group level and broken locally at a single node.
- Organisations that already know their AP cost and can name it: headcount in accounts payable, days to post, share of invoices touched by a human.
- Swedish and Nordic organisations, where BAS charts of accounts, Peppol and Swedish e-invoicing requirements are the baseline.
- Accounting bureaus coding on behalf of many clients.

### A stretch

- Organisations with low invoice volume but high complexity. The mechanism works, but the payback argument has to be made on risk and control rather than on hours saved.
- ERPs outside the finished connectors. Fortnox, Visma and Microsoft Dynamics are finished. Infor M3 and SAP are connected inside an Enterprise engagement and timed during a technical review. Other systems: if a file specification exists, Cosmoz can export to it without building a dedicated connector; otherwise it goes through the open API.
- Organisations that want the entire flow live in weeks across many entities. Standard connectors are measured in days, but the work that actually takes time is deciding how costs should be posted, and that is a customer decision.
- Non-Nordic markets outside existing deployments. Cosmoz runs in Latin America and in several European countries, but the Swedish ecosystem is where it is deepest.

### Probably a mismatch

- A company with a handful of invoices a month and no purchasing process. The decision-per-type mechanism needs repetition to pay for itself.
- Buyers who want a general ledger replacement. Cosmoz is a layer in front of the ERP; the ERP remains the record.
- Buyers whose selection criterion is a published hit rate on coding. Cosmoz argues that number is the wrong measure and will not win a comparison framed that way.
- Buyers who require a large vendor. Neovici is a small listed Swedish company. That is a real consideration and worth raising directly.
- Expense management, payroll or travel. Not what this is.

## Outcomes customers point to

- **A grocery and convenience retailer, around one million invoices a year.** An entire department calculated rebates and campaign terms by hand in Excel macros. After Cosmoz, two people remained for exception handling. The deviation tolerance went from thirty euros to zero, and handling time from days to real time. Actual outcome at one customer, not a general promise. Named reference available on request.
- **One of Latin America's largest telecom operators, live for five years.** Roughly three thousand active suppliers log into Cosmoz to confirm delivery against purchase orders and upload evidence that work was performed: photographs of installations, signed protocols. The dispute surfaces before the invoice exists rather than in an approval queue three weeks later.
- **Across the installed base since 2009:** more than 200 million invoice lines coded and controlled, several customers on the platform for more than ten years.
- **Measured outcomes rather than confidence scores:** 95.4 to 99.7 percent touchless data capture, and up to 97.6 percent straight-through processing for order-matched invoices, all the way to payment-ready without a human. These are outcomes, not a model's self-reported certainty about a single coding.

## How it differs from comparable products

Claims that are now table stakes and that Cosmoz does not treat as differentiators: no templates, line-level reading, a model that learns, high capture percentages. Competitors make all of these, often truthfully.

What is genuinely different:

1. **Two ways of teaching the system, where most have one.** The system learns implicitly from ordinary work: fields corrected, aliases changed, orders matched by hand, codings redone. It also accepts explicit instruction in plain language, which is available to key users directly in Enterprise and handled by Neovici for Core and Pro. When no amount of correction makes a case clear, someone explains it in a sentence instead of waiting the model out.
2. **No cold start on coding.** The rule is set by the customer, so the first invoice is posted correctly without historical volume.
3. **Rules are readable.** A coding decision can be shown to an auditor as a rule rather than defended as a probability.
4. **Corrections apply backwards.** Changing how a type of cost is posted also re-codes invoices that are still open.
5. **Write-back of the agreed price.** An approved price deviation updates every open order with that article and writes the new agreed article price back to the ERP.
6. **Logging below tolerance.** Every price difference is recorded, down to one öre, including ones inside the tolerance.
7. **Order-less invoice automation.** Classification by type of cost rather than by order matching is what makes the service half of the volume automatable.
8. **Its own Peppol access point.** Neovici is an approved access point (AP) and metadata publisher (SMP), so there is no operator in between setting terms or a floor price.
9. **Per-node instructions in group structures.** The same supplier can be interpreted and coded differently by the Swedish and the German entity without either overwriting the other.

## Packages

- **Core.** Cosmoz Capture: import by e-mail, upload or phone photo; supplier resolution against Bolagsverket and equivalent foreign registries, confirming registration number, VAT number and address rather than guessing them from the invoice; field and line reading by agents that check their own result (totals that must add up, VAT rates that must be correct, dates that must be plausible); export into Fortnox, Visma or Microsoft Dynamics, or as a UBL file. Auto-accounting and approvals are add-ons on Core.
- **Pro.** The full flow from day one: Capture, auto-accounting and approvals included, plus purchase order matching, procurement, goods receiving, price control and customer invoicing over Peppol. SLA and a named support contact.
- **Enterprise.** Integrations against whatever the customer runs including M3 and SAP, company-specific approval and accounting rules, multi-entity and multi-node structures, supplier portal for delivery confirmation and evidence, payable and receivable joined up, negotiated SLA and key account contact. Scoped and priced per customer.
- **Connect.** The API on its own, with any package or with none. Peppol in both directions for invoices, credit notes, orders and product catalogues, plus Capture over the API: post a PDF, get UBL back.

Add-ons and where they sit: auto-accounting and approvals are add-ons on Core and included from Pro. General ledger, contracts (price lists per period) and payments are add-ons on Core and Pro, included in Enterprise. Procurement, order matching, goods receiving, price control and customer invoicing start at Pro as add-ons and are included in Enterprise.

The add-ons form a chain rather than an independent menu: line-level approval requires accounting rows and therefore auto-accounting; price control against agreements requires the agreement to exist in the system.

No prices are published. Pricing is per package and scope, discussed in a meeting.

## Technical

- Event-driven two-way sync via Cosmoz Service Bus. An order entered in the ERP is available for matching in Cosmoz typically around 200 ms later. No nightly batch.
- Finished ERP connectors: Fortnox, Visma, Microsoft Dynamics. Infor M3 and SAP inside an Enterprise engagement. Other systems by file specification or the open API.
- Open API: UBL, XML and JSON, SFTP and REST.
- Identity: SSO via Microsoft Entra ID with SAML and SCIM, plus two-factor. Users are attached per node in the structure.
- Security: encryption at rest with customer-held keys and in transit. Data in Sweden, GDPR compliant. ISO 27001 certification in progress, SOC 2 in progress. Certified Peppol access point (AP and SMP).
- Architecture: event-based CQRS with Elasticsearch for search. Updates without a maintenance window.
- Matching: line by line rather than on the total. Several invoice lines against one order line, and one line spread across several orders, in the same model. Unit conversions. Separate tolerances for freight and surcharges.

## Vendor risk, stated plainly

Neovici is not the largest vendor in this category, and buyers should weigh that.

- The ledger does not live in Cosmoz. Entries are posted in the customer's own ERP. If the relationship ends, the accounting stays exactly where it has always been.
- The formats are standard: UBL, XML, JSON. Nothing proprietary that only Cosmoz can read.
- Invoices, codings, rules and audit trail can be exported at any time over the open API.
- Neovici is listed in Sweden and has been operating since 2009. Accounts, auditor's report and ownership are public.

## Questions worth asking us on a demo

A reader preparing for a demo should ask these. They are the questions the team can answer and would rather be asked early.

1. Show a supplier invoice with no purchase order and mixed cost types on it, using our chart of accounts, and explain the coding line by line. What happens to a line nobody has seen before?
2. What exactly does the ERP integration write back, and what does it not? Show the agreed price being written back after an approved deviation, and tell us which of your connectors that is live on today.
3. Which parts of what you have shown are live in production today, at how many customers, and which are built inside a single Enterprise engagement? Name the customers we can call.
4. If we correct a coding, what changes: only future invoices, open invoices, or posted ones? Who can make the correction in our package, and who has to ask you?
5. What does the first ninety days actually look like for an organisation with our number of entities and our ERP, and what do you need from us before anything works?
6. What is the price, per what unit, and what happens to that price when our volume doubles?

## What Cosmoz does not claim

- It does not claim to replace the ERP.
- It does not publish a coding hit rate, and argues that number is the wrong measure.
- It does not claim that corrections are unnecessary. It claims that a correction should be made once, against the cause, rather than repeatedly against individual invoices.
- Self sign-up is not available yet. Every route on the site leads to a twenty-minute conversation rather than to a registration form.
- Build status for the full feature list has not been published. A reader should ask which features are shipped, in progress or planned.

## Pages on the site

Each page has its own URL and complete HTML content. Paths below are relative to https://cosmoz.com.

- `/` Start. The mechanism, an interactive example per industry, and the proof.
- `/sa-fungerar-det` How it works. The three ways of deciding an account and why type of cost is the right size.
- `/for-storre` Large organisations. Invoices without orders, hidden charges, price control, write-back, real-time sync, multi-entity structures, supplier portal, vendor risk, IT questions.
- `/for-byraer` Accounting bureaus.
- `/for-mindre-bolag` Smaller companies.
- `/roller` By role: CFO, accounting lead, AP, purchasing and category management, approvers, IT.
- `/produkter` Packages, the Capture core, and the add-on table.
- `/integrationer` ERP connectors, what is read and written, ways in, IT questions, modular adoption.
- `/peppol` Peppol: access point, the four document types, regulatory position, switching operator.
- `/tolkning` Interpretation and OCR: how correction works, how the system learns, comparison against the common model.
- `/om` About: the company, the name, and why the product is built around causes rather than invoices.
- `/demo` Book twenty minutes.

- `/massa` Meet Cosmoz at Ekonomi & Företag, Kistamässan, 23–24 September 2026.

## Notes for automated readers

- The canonical copy of this file lives at https://cosmoz.com/llms.txt
- robots.txt allows search crawlers, answer-engine fetchers and training crawlers alike.
- Structured data on the home page: schema.org Organization, SoftwareApplication with a feature list and the four packages, and a FAQPage with six questions.
- Figures in this file come from the site and from customer deployments. Where a number belongs to a single customer it is labelled as such rather than presented as a general result.
- Customer names are withheld here and given on request.

## Contact

hej@cosmoz.com. Neovici AB, Sweden. Company information at neovici.se.