Ürün ayrıntıları İngilizce olarak görüntülenir. Çeviriler yakında gelecek.
Kısa bilgiler
- Fiyat
- $499.00 USD
- ERPNext versiyonları
- —
- Kurulum süresi
- 30 dk.
- Lisans
- Bir kerelik kalıcı
- Diller
- 11 language
Tek Seferlik Satın Alma
ERPNext Germany Localization (GoBD/DATEV)
A build-to-order German accounting localization for ERPNext that ships an SKR03/SKR04 chart of accounts, a GoBD-compliant immutable ledger, DATEV-format export and ELSTER-ready VAT (USt) advance return data. ECOSIRE scopes, builds, installs and supports it for your specific Frappe/ERPNext deployment.
$499.00USD
Şimdi ödeme yok. Bu, ekibimize bir teklif talebi gönderir — fiyat ve sonraki adımlarla e-posta ile dönüş yapacağız.
Temel Özellikler
SKR03 and SKR04 charts of accounts delivered as importable ERPNext Chart of Accounts templates with correct account numbers and tax-account links
DATEV Buchungsstapel export (EXTF format CSV: Umsatz, Soll/Haben-Kennzeichen, Gegenkonto, BU-Schlüssel, Belegdatum, Belegfeld 1, Buchungstext) via a dedicated DATEV Export DocType
GoBD-compliant immutable ledger: hooks.py on_submit / on_cancel doc events lock submitted GL and Journal Entries; cancellations post reversing entries instead of deleting originals
German USt tax templates: 19% Regelsteuersatz, 7% ermäßigter Satz, 0%, reverse-charge (§13b) and innergemeinschaftlicher Erwerb, each mapped to the correct SKR tax accounts
ELSTER-ready USt-Voranmeldung data model mapping bookings to Kennzahlen (81, 86, 35, 66, 61, 89) for the monthly/quarterly VAT advance return
Sequential document numbering (Belegnummer / fortlaufende Nummerierung) with gap detection to satisfy GoBD Nachvollziehbarkeit
Fibu period-lock DocType that blocks postings into closed accounting periods with a permission-gated unlock
Whitelisted @frappe.whitelist() server method exposing DATEV export over the Frappe REST API for programmatic and scheduled retrieval
Scheduler events (frappe scheduler_events) that pre-stage monthly USt figures and validate posting-period integrity
Role profiles and permission rules for Buchhalter, Steuerberater (read-only export) and Finanzleiter, so export and period locking are access-controlled
Configurable DATEV header parameters (Berater-Nr, Mandanten-Nr, Wirtschaftsjahr-Beginn, Konten-Länge) stored in a Single settings DocType
Client scripts adding German-specific validation and quick DATEV-export actions on Sales Invoice, Purchase Invoice and Journal Entry
Frappe version history + dedicated audit-log DocType capturing who changed what and when, supporting the Verfahrensdokumentation
Packaged as a standard installable Frappe app that survives bench update and pins compatibility to ERPNext v15 (validated for v16)
Bu Ürün Hakkında
German Mittelstand finance teams run into a wall the moment their Steuerberater asks for a DATEV export. ERPNext core ships a generic accounting engine, but it has no SKR03/SKR04 account structure, no DATEV Buchungsstapel format, no GoBD-grade immutability guarantees, and no USt advance-return (Umsatzsteuervoranmeldung) mapping that ELSTER expects. Bookkeepers end up hand-keying journals into DATEV, exporting spreadsheets that fail GoBD's Unveränderbarkeit (non-alterability) principle, and reconciling VAT codes manually every month. That is exactly where ERPNext native runs out of road for a German entity.
Neden ERPNext Germany Localization (GoBD/DATEV)
SKR03 and SKR04 charts of accounts delivered as importable ERPNext Chart of Accounts templates with correct account numbers and tax-account links
DATEV Buchungsstapel export (EXTF format CSV: Umsatz, Soll/Haben-Kennzeichen, Gegenkonto, BU-Schlüssel, Belegdatum, Belegfeld 1, Buchungstext) via a dedicated DATEV Export DocType
GoBD-compliant immutable ledger: hooks.py on_submit / on_cancel doc events lock submitted GL and Journal Entries; cancellations post reversing entries instead of deleting originals
German USt tax templates: 19% Regelsteuersatz, 7% ermäßigter Satz, 0%, reverse-charge (§13b) and innergemeinschaftlicher Erwerb, each mapped to the correct SKR tax accounts
ELSTER-ready USt-Voranmeldung data model mapping bookings to Kennzahlen (81, 86, 35, 66, 61, 89) for the monthly/quarterly VAT advance return
Sequential document numbering (Belegnummer / fortlaufende Nummerierung) with gap detection to satisfy GoBD Nachvollziehbarkeit
ECOSIRE builds a proper Frappe app — for example erpnext_de_localization — that installs cleanly onto your bench alongside ERPNext, rather than a pile of manual customizations that break on the next bench update. The app ships the SKR03 and SKR04 charts as importable Chart of Accounts templates with the correct account numbers and tax-account mappings, plus German USt tax templates (19% Regelsteuersatz, 7% ermäßigt, 0%/reverse-charge, innergemeinschaftlicher Erwerb). Bookings flow through ERPNext normally; a custom DATEV Export DocType and a whitelisted server method assemble the DATEV Buchungsstapel (EXTF header + booking lines with Umsatz, BU-Schlüssel, Gegenkonto, Belegdatum, Belegfeld) as a DATEV-format CSV your tax advisor imports directly.
GoBD compliance is enforced in code, not in policy. We wire hooks.py doc events (on_submit, on_trash, on_cancel) so that submitted GL Entries and Journal Entries become immutable, with cancellation posting a reversing entry rather than deleting the original — preserving the audit trail (Verfahrensdokumentation-ready, with sequential document numbering / Belegnummer continuity). A Fibu Period Lock guard blocks postings into closed periods, and every change is captured through Frappe's version history and a dedicated audit log DocType. Role profiles (Buchhalter, Steuerberater read-only export, Finanzleiter) are provisioned so DATEV export and period locking are permission-gated. Scheduler events can pre-stage the monthly USt advance return figures (Kennzahlen 81/86/35/66 etc.) so the ELSTER submission data is ready on schedule, and the Frappe REST API / whitelisted methods let your existing tooling pull the same export programmatically. Everything targets Frappe/ERPNext v15 and is validated for the v16 line.
Because this is build-to-order, nothing is a blind download. We start with a scoping call to confirm your SKR variant, tax scenarios, DATEV berater/mandant numbers and ERPNext version, then build against your requirements, test on a staging clone, run UAT with your bookkeeper and Steuerberater, and hand over installable source plus the git repository. Typical delivery is 2–4 weeks from confirmed scope, followed by a post-go-live support window. You get a maintainable Frappe app you own — not a one-off consultant hack.
Ne elde edeceksin
- Installable Frappe app source code for your ERPNext version (v15 or v16), pinned to your bench
- Guided installation and configuration on your environment: SKR variant selection, USt templates, DATEV Berater/Mandant numbers and role profiles
- Technical documentation: DocType reference, hooks.py doc-event map, whitelisted API endpoints and the DATEV field mapping
- German user guide (Buchhalter-oriented) plus a live training session for your finance team and Steuerberater
- UAT on a staging clone with a signed-off test plan and a documented rollback procedure
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with full commit history so you own and can extend the codebase
- Verfahrensdokumentation starter template describing the GoBD controls the app enforces
Bu kimin için
Mittelstand bookkeeper (Buchhalter/in)
Runs day-to-day Finanzbuchhaltung in ERPNext and needs a one-click DATEV Buchungsstapel their Steuerberater can import without hand-keying, plus USt figures that reconcile to ELSTER every month.
Finance lead / Finanzleiter
Owns period close and audit readiness. Needs a GoBD-compliant immutable ledger, period locking, sequential document numbering and an audit trail that stands up in a Betriebsprüfung.
Steuerberater / tax advisor
Receives the client's data in DATEV format. Wants a clean, correctly-mapped Buchungsstapel (correct BU-Schlüssel and Gegenkonto) and read-only export access rather than raw spreadsheet dumps.
ERPNext implementation partner / IT lead
Responsible for keeping the bench maintainable. Wants German localization delivered as a proper versioned Frappe app that survives bench update, not as fragile ad-hoc customizations.
Kuruluma genel bakış
ECOSIRE'dan indirin
Lisansı ecosire.com adresinden satın alın ve hesap kontrol panelinizden ERPNext Germany Localization (GoBD/DATEV) uygulamasının ZIP dosyasını indirin.
Uygulamayı bankınıza ekleyin
ZIP dosyasını tezgahınızın uygulamalar klasörüne çıkarın veya çıkarılan uygulamanın yolunu içeren "bench get-app" komutunu çalıştırın.
Sitenize yükleyin
ERPNext Germany Localization (GoBD/DATEV) yüklemek ve şemasını uygulamak için `bench --site SITE_NAME install-app APP_NAME` komutunu ve ardından `bench move'u çalıştırın.
Lisansınızı etkinleştirin
Sitenizdeki ECOSIRE Lisans ayarlarını açın ve lisans anahtarınızı etkinleştirin. Ücretsiz ecosire_connect ve ecosire_license_client uygulamalarını gerektirir.
ERPNext Germany Localization (GoBD/DATEV) Nasıl Karşılaştırılır
| Kriter | ECOSIRE | Özel Yapı | Rakip | Odoo Yerlisi |
|---|---|---|---|---|
| SKR03/SKR04 chart of accounts | Delivered as importable templates with correct tax-account mappings | Built by hand per project; accuracy depends on the developer | Sometimes bundled, often only one SKR variant, rarely mapped to your entity | |
| DATEV Buchungsstapel export | EXTF-format export validated with your Steuerberater during UAT | Possible but you specify and test the format yourself | Basic CSV export, may not match current DATEV field spec | |
| GoBD immutability | Enforced via hooks.py doc events, reversing entries and period locks | Only if explicitly scoped and correctly implemented | Rarely covered; usually export-only | |
| USt / ELSTER return data | Kennzahlen mapping for the USt-Voranmeldung, pre-staged by scheduler | Hand-built mapping, maintained by you | Tax templates maybe; ELSTER mapping usually absent | |
| Maintainability on upgrade | Proper versioned Frappe app that survives bench update | Ad-hoc customizations that often break on updates | Packaged app, but fit and update cadence vary | |
| Fit to your entity | Scoped to your SKR variant, tax cases and DATEV numbers | Fully bespoke but slow and expensive to get right | One-size-fits-all; you adapt to it | |
| Support and ownership | Post-go-live support window plus full git repo handover | Tied to the individual developer's availability | Vendor support tiers; you rarely get the source | |
| Time to value | 2–4 weeks from confirmed scope, tested on staging | Often months, with iteration risk | Fast to install but slow to make actually compliant |
ERPNext Germany Localization (GoBD/DATEV) hakkında Sıkça Sorulan Sorular
+Is this an existing app I can download and install right now?
No. This is a build-to-order engagement. ECOSIRE builds the German localization against your specific ERPNext version, SKR variant, tax scenarios and DATEV configuration, then installs and supports it. There is no instant download — you receive tested, installable source plus the git repository at handover.
+How long does delivery take?
Typical delivery is 2–4 weeks from confirmed scope. The clock starts once we have agreed your SKR03/SKR04 choice, USt scenarios, DATEV Berater/Mandant numbers, ERPNext version and any custom mappings on the scoping call. More complex tax or multi-entity requirements can extend the timeline, which we confirm in writing before we start.
+Does the DATEV export actually import into my Steuerberater's DATEV system?
Yes. We generate the DATEV Buchungsstapel in EXTF format with the correct header (Berater-Nr, Mandanten-Nr, Wirtschaftsjahr) and booking lines (Umsatz, Soll/Haben, Gegenkonto, BU-Schlüssel, Belegdatum, Belegfeld, Buchungstext). We validate a sample import with your tax advisor during UAT before go-live so there are no format surprises.
+How is GoBD compliance actually enforced?
In code, not policy. hooks.py doc events make submitted GL and Journal Entries immutable; cancellations post reversing entries instead of deleting originals; period locks block postings into closed periods; document numbering is sequential with gap detection; and Frappe version history plus a dedicated audit-log DocType record every change. Together these satisfy GoBD's Unveränderbarkeit and Nachvollziehbarkeit requirements.
+Which ERPNext and Frappe versions are supported?
We target Frappe/ERPNext v15 and validate the app for the v16 line. Tell us your exact bench version on the scoping call and we build and test against it, packaged as a standard Frappe app so it survives bench update rather than breaking on the next upgrade.
+What happens after go-live for support and updates?
The engagement includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full git repository, your team or ours can extend it later. Ongoing maintenance — for example adapting to a future DATEV format revision or a new ERPNext major version — can be arranged as a separate support agreement.
+Can I pull the DATEV export programmatically instead of clicking a button?
Yes. The export is exposed through a whitelisted @frappe.whitelist() method over the Frappe REST API, and scheduler events can pre-stage monthly figures. That lets external tooling or automated jobs retrieve the Buchungsstapel and USt data on a schedule, with the same permission gating as the UI.
Teklif isteyin
ERPNext Germany Localization (GoBD/DATEV)
A build-to-order German accounting localization for ERPNext that ships an SKR03/SKR04 chart of accounts, a GoBD-compliant immutable ledger, DATEV-format export and ELSTER-ready VAT (USt) advance return data. ECOSIRE scopes, builds, installs and supports it for your specific Frappe/ERPNext deployment.
- SKR03 and SKR04 charts of accounts delivered as importable ERPNext Chart of Accounts templates with correct account numbers and tax-account links
- DATEV Buchungsstapel export (EXTF format CSV: Umsatz, Soll/Haben-Kennzeichen, Gegenkonto, BU-Schlüssel, Belegdatum, Belegfeld 1, Buchungstext) via a dedicated DATEV Export DocType
- GoBD-compliant immutable ledger: hooks.py on_submit / on_cancel doc events lock submitted GL and Journal Entries; cancellations post reversing entries instead of deleting originals
- German USt tax templates: 19% Regelsteuersatz, 7% ermäßigter Satz, 0%, reverse-charge (§13b) and innergemeinschaftlicher Erwerb, each mapped to the correct SKR tax accounts