AI in receipt processing

Incoming invoices and expense receipts arrive as PDF scans, phone photos, email attachments, or structured e-invoices. Someone still has to create a record, pick the supplier, choose a booking account, enter amounts and dates, and check for duplicates. That work scales with every supplier and every month-end.

Automation helps most when the file already carries machine-readable data. When it does not, models can propose fields from a scan. Neither path removes the need for a person who knows your chart of accounts and your tax advisor's expectations. Software speeds capture. It does not replace bookkeeping judgment.

This article explains how Jupiter ERP splits structured extraction from AI suggestions, what you should check before you confirm, and where the Jupiter AI assistant fits beside receipt recognition. It is orientation for SMB workflows, not tax or GoBD advice for your case.

Structured e-invoices that follow EN 16931 (for example ZUGFeRD hybrid PDFs or XRechnung XML) are parsed from the XML. Amounts, parties, dates, and line items come from the dataset, not from a language model guessing at pixels. That is faster and more predictable than OCR alone.

AI comes in when the file is a scan or photo, or when fields such as booking category or contact still need a suggestion after the structured part is read. The AI module then proposes contact, booking account, cost center, amounts, date, and line items after upload. The panel shows those values as suggestions you can edit.

Duplicate checks during capture reduce the risk of posting the same supplier invoice twice. Suggestions still need a human eye: similar supplier names, split invoices, and unusual VAT rates are common traps.

Treat every AI-filled field as a draft. Compare supplier name and VAT ID to your contact master. Check net, tax, and gross against the visible document. Confirm the document date and the period you want for reporting. Assign the booking account and cost center your advisor expects.

For structured e-invoices, still verify that the parsed party matches the right contact and that line items map cleanly. Automatic XML reading reduces typing. It does not decide your chart of accounts for you.

After confirmation, expense receipts can flow into accounting reports and, on Business and above, into DATEV export for your tax firm. Locking and period close remain separate steps. AI does not auto-lock periods or invent postings you never approved.

Receipt recognition runs when you capture an expense receipt: it fills or suggests fields on that document. The Jupiter AI assistant is the sidebar you open from the sparkle icon on almost every panel page. It knows the current form and can answer questions such as which booking account fits, without you leaving the page.

AI chat is the longer conversation mode with access to your company data and advisor-style roles. All three sit in the same AI module. There is no separate licence for the Jupiter AI assistant. See the pricing page for how the AI module is included from Basic.

The assistant and receipt recognition stay tenant-scoped and read-only with respect to other accounts. They do not see data from other customers on the platform. You remain responsible for what you save and export.

Blurry photos, handwritten notes, multi-page scans with mixed documents, and unusual layouts reduce suggestion quality. Foreign-language supplier invoices may need more manual correction. AI can misread a total or propose the wrong contact when names are similar.

Jupiter ERP does not claim that every receipt posts itself without review. Structured e-invoices are the reliable path when suppliers send EN 16931 data. For scans, plan a short review step into your process, especially before period lock or DATEV handover.

GoBD and proper bookkeeping still depend on your organisation: who may approve receipts, how fast you capture them, and how you retain evidence. Use change logs, roles, and period rules with your tax advisor. Software supports those controls. It does not certify your overall compliance alone.