What Dijit.app is

Dijit.app is a document management platform built on generative AI and OCR for purchase-to-pay and accounting. It reads invoices, delivery notes, receipts and business paperwork; it extracts and checks the data on them, from the supplier and the line items to the taxes, the totals and the nominal account; and it hands the result to your ERP or accounting software. It also covers the work that comes next: matching delivery notes against invoices, auditing prices, raising purchase orders, costing recipes, flagging payments that are about to fall due, running approvals and keeping a searchable archive with a full audit trail.

What the product covers

Dijit.app works across the purchase-to-pay cycle and input VAT. Its job is to take away the typing, and the checking that always comes with it: confirming that what you were invoiced for is what you actually received, that the prices are the ones you agreed, and that every document ends up against the right nominal account.

What happens to a document

Every document goes through the same sequence, whichever way it arrived:

1. It arrives. Uploaded through the web application on a desktop or a phone, sent in by email, dropped into a connected Dropbox folder, or pushed in through the API.
2. It is read. OCR picks up the content and the generative AI models work out what each value means. This takes under three seconds a page.
3. The data is pulled out. Header data first, meaning the issuer, the recipient, the dates, the numbers, the net amounts, the taxes and the totals, then the line items with item, quantity, price and discounts.
4. It is checked. The system tests the document against itself: that the lines add up to the totals, that the taxes are consistent, and that this is not a document you have already had.
5. It is coded. Nominal accounts are filled in from your own history and from the rules you have set.
6. It gets a status. The document appears in its list with a status that either says the checks passed or points at the one thing that needs a look.
7. You approve it, on its own or in a batch.
8. It goes out. The data is posted to your ERP through a connector, or written to a file in the format your accounting software accepts.

What it does

Purchasing

• A complete view of what you buy, line by line, from both delivery notes and invoices.
• Automatic matching of delivery notes to their invoice, item by item.
• Price auditing: anything that has moved since the last delivery is flagged.
• Purchase orders built from what you ordered on previous delivery notes.
• Recipe costings, with the cost of every recipe updated as prices change.
• Alerts for supplier payments about to fall due.

Accounting

• VAT, withholding tax, the Spanish equivalence surcharge and net amounts read off the document whatever its layout.
• Nominal accounts filled in automatically, learning from how your company has coded things before.
• Duplicate invoices caught before they are posted.
• Input and output VAT, on both purchases and sales.
• Every kind of invoice: intra-community, exempt, simplified, VAT-inclusive, import documents, credit notes and invoices with tax withheld.
• Users by role: the finance team, clients who only upload, and clients who manage their own paperwork.

Internal paperwork

• Job sheets and production records digitised, handwriting included.
• Approval routes by amount, by supplier or by category.
• A digital archive of everything processed, searchable and fully traceable.

Set up around how you work

The system is fitted to each customer's way of working with no development needed at your end:

• Your own extraction and validation rules, per company and per supplier.
• Training for documents and fields that are not covered as standard.
• Export formats built to order, whether an Excel layout or an ERP file.
• Nominal accounts, document series and accounting criteria configured per company.
• New connectors on request for software that is not on the list.

Documents it reads

Purchase invoices, simplified invoices, import documents, till receipts, goods-received and sales delivery notes, transport invoices, purchase orders, production sheets, job sheets, payslips, payment documents and transport manifests.

Which of these you have depends on how your account is set up.

Ways documents come in

The routes work side by side: one account can take most of its invoices by email while several people upload by hand at the same time. Where each document came from is recorded and shown in the list.

Where the data goes

There are two ways out:

• Posted straight in through a connector: SAP Business One and SAP S/4HANA, Microsoft Dynamics 365 Business Central, Sage X3, Holded, ICG Manager, Ágora POS, Monitor Informática and Diagram.
• Written to a file for your accounting software to import: a3 (a3ASESOR eco/con, a3ERP, a3innuva), Contasol, Cegid DIEZ, Aplifisa, ContaPlus, Alba IBS, Factusol, Xero and QuickBooks.

On top of that there is Excel export with a layout of your own and a REST API for anything else. Connectors that are not on the list are built on request.

Performance, security and compliance

The security architecture and the compliance detail are set out in Security and compliance.

What it deliberately does not do

• It is not a sales invoicing package. It reads and processes sales invoices; it does not raise them.
• It does not replace your ERP or your accounting software. It feeds them.
• It does not file tax returns and it does not produce them.
• Approval stays with you. The system checks and flags; sign-off comes from a person or from the approval route you have set up.
• It does not invent missing data. If a value is not on the document, or cannot be read, the field is left empty and the document is flagged for a look.

Documentation index

↑ Back to top

Last reviewed: 11 September 2026 · The Dijit.app team