# Process invoices and receipts

Source: https://dropdigital.de/en/leistungen/rechnungsverarbeitung
Language: en
Site: DropD., https://dropdigital.de

## Process invoices and receipts

Receipts pile up, amounts are retyped, the tax office asks the same things every month. We pre-capture, you approve.

Staff retype supplier, date and amount, and at some point the coding no longer matches. Expense reports take weeks because receipts are missing or unreadable. The tax advisor gets the same pile as last month, only later. Read the receipt PDF, photo, mail attachment. Supplier, date, amount, tax rate, receipt number. What is unambiguous becomes a record. What is unclear stays unclear and goes to review, not into the books. Pre-capture against your account logic The mapping follows your existing scheme, DATEV, sevDesk or lexoffice, not a generic table from the internet. New suppliers land in a queue, not on a guessed account. Approval, then handover A person sees the proposal next to the receipt image and signs off. Only then does the record enter the accounting system. An automation that books silently will not hold under GoBD. Capture Read fields and map them to the account logic Quietly correct values that do not match Booking Pre-capture and submit for approval Book without a person having looked Unreadable receipts Stop and send to review with a guess attached Guess and file the receipt as done Payments Prepare a payment proposal Trigger transfers Is this GoBD-compliant? GoBD require traceable, immutable bookings. That is why the system does not book itself: it pre-captures, a person approves, the booking is created afterwards in the existing system. The original receipt is kept, the processing is logged. Whether your tax advisor signs off on the flow is settled before the build, not after. Does this work with DATEV, sevDesk or lexoffice? Yes, those are the three we hand over to most often. The receipt stays where it is, the record moves. Switching accounting systems is its own project and rarely the answer to a pile of receipts. What if the receipt is unreadable? Then it goes into the review queue, with what was readable and the part that is missing. A system that invents the amount in doubt creates exactly the discrepancies the tax advisor later has to hunt. How is this different from document processing? Invoices have a fixed shape: supplier, amount, tax, account. Contracts and delivery notes do not. That is why they are two pages. In practice receipts often arrive by mail, and the chain into accounting is workflow automation. Pre-capture in minutes instead of the morning Tax firm, 11 staff, Münsterland. Receipts pre-coded, approval in the existing DATEV chain. Unclear receipts stay put, instead of going through wrong.

Link: https://dropdigital.de/en/leistungen/rechnungsverarbeitung
Id: usecase-rechnungsverarbeitung