Journal, open items and bank statement arrive as CSV. vorerfasst shows what is missing, lets a person review it and puts the same lines into DATEV, BMD, RZL, Lexware, Sage 50 or SAP Business One. The mapping stays behind the scenes.
Accounting firms. Finance teams. Tax advisers.
Try it without risk: 14 days, no credit card, data in the EU
The journal brings the customers and vendors with it: personal account, name and the assignment already booked. Open items hang on those accounts, so a name is never a guess. What is unclear stays open instead of being quietly filled with a tax rate.
08:15 in Vienna: the first stamp of the day is already there.
Journal, open items and bank statement. You map the columns once, after that vorerfasst remembers the mapping, even when the next file comes from another program.
A missing tax rate, a missing contra account, a possible duplicate. What is complete is skipped while you review the rest.
Time and person come from the server, not from a text field. The approval matrix sets who approves up to which amount. If the invoice changes afterwards, the old stamp stays visible and no longer applies.
The same lines leave as an EXTF batch for DATEV, as Satzart 0 for BMD, as a euro file for RZL or as a DTW file for SAP Business One. An empty tax rate arrives empty.
Overdue customers become a reminder letter. Overdue vendors become a SEPA file, once a person has approved the payment. For everyday collections, not for the courtroom.
Useful lives come from the German table, calculated with the Austrian monthly rule. The years stay editable and the acquisition sits next to them.
Without a chart of your own, vorerfasst proposes the Austrian EKR. After that it learns from what was booked for each vendor.
Import, approval and export land in the audit log. The approval itself is its own list and is never overwritten, not even by us.
The same journal lines leave as a file, and the import happens in DATEV, Lexware, Sage, BMD, RZL or SAP Business One. No direct access, no standing connection to the books.
DATEVEXTF posting batch: the firm imports the file.
LexwareThe same DATEV file, read through the DATEV import.
Sage 50The same DATEV file for Sage 50 and 50cloud.
BMDFIBU postings as Satzart 0, as a file.
RZLeuro file with semicolons, imported into RZL.
SAP Business OneDTW file with an OJDT header and JDT1 lines.BMD and RZL, DATEV, Lexware, Sage and SAP Business One read the file in their own import. You check it there with the trial run, as before.
Time and person come from the server. A later change to the invoice invalidates the approval but does not delete it, so the old stamp stays visible.
Password and authenticator, the recovery codes once. Only then are clients and documents visible, for every person, including management.
Access, role and audit log apply per client. The intended storage location is Frankfurt.
The intended location is a server in Frankfurt. Clients, documents and archive stay in the EU and with that client.
vorerfasst processes the bookkeeping on behalf of the firm, under Art. 28 GDPR. Responsibility for the books stays with the firm.
The bookkeeper prepares, the financial accountant reviews, C-level approves. Without that approval no bank file is created.
Login only with password and authenticator. Recovery codes are issued once, and only then are clients and documents visible.
Import, approval and export record person and time. The approval stays as its own list and is not overwritten.
The password is stored only as a hash. The session is signed and ends after twelve hours.
No direct access to someone else's books, no guessed tax rates, no interface that quietly pulls data. Four things carry this.
Developed and operated in Austria, under Austrian and European law. Support in German and English, by the people who wrote the code.
Clients, documents and archive stay in the EU. Every file stays attached to its client, including in the archive.
EXTF for DATEV, Satzart 0 for BMD, a euro file for RZL, the same DATEV file for Lexware and Sage 50, DTW for SAP Business One.
Every approval carries person and server time. Every archive entry carries its SHA-256. Import, approval and export sit in the audit log.
One price per plan, every target format included. No setup fee, no price per document, no surcharge per client.
Double-entry bookkeeping as the base: a debit and credit journal, monthly and annual reports, export to all six target formats.
Preparatory bookkeeping, not tax or legal advice.
Accounting with documents: upload the paperwork, have it read and attach it to the matching line.
Preparatory bookkeeping, not tax or legal advice.
For trade and large document volumes: more room for documents, journal lines without a fixed limit (fair use).
Preparatory bookkeeping, not tax or legal advice.
Store the originals, import the lists, hand out the same records as a target file: no live interface.
Originals, documents and exports stay attached to the client: seven years, in the EU.
Documents, minutes and an hourly rate of 60 €. The minutes with vorerfasst are your assumption, not ours.
The minutes with vorerfasst are your assumption. The hourly rate in the calculation is 60 €.
The archive costs €199.99 per year, which is €16.67 per month. The switch costs €1,499.99 once.
An indicative calculation from your numbers: it does not say how much time really falls away in your firm.
Three CSV lists: journal, open items and bank statement. The personal accounts from the journal are your customer and vendor master data, and the bank posting takes its account from the journal.
One posting batch. DATEV, Lexware and Sage 50 read the same EXTF file. BMD gets Satzart 0, RZL the euro file, SAP Business One the DTW file.
No. If none is in the line, the field stays empty. An amount with a tax rate counts as gross.
Every approval writes a new line with person and server time, in Vienna, and the history is never overwritten. The matrix sets how many people approve up to which amount. Reminder, payment and the export of open items wait for a valid stamp.
No. You download the CSV and import it into DATEV, Lexware, Sage, BMD, RZL or SAP Business One. The trial run happens in the target program first.
On the server of this installation, intended for Frankfurt in the EU. The files of a client stay attached to that client, and login requires password and authenticator.
vorerfasst does, on behalf of the firm, under Art. 28 GDPR. Responsibility for the books stays with the firm.
Three roles are open. Anyone who has produced a DATEV file knows why that is a role of its own.
Set up the office, switch on the second factor and load a CSV. The rest shows up on the first run.
Start for free