Os detalhes do produto são exibidos em inglês. Traduções em breve.
Fatos rápidos
- Preço
- $499.00 USD
- Versões ERPNext
- —
- Tempo de configuração
- 30 min
- Licença
- Uma vez perpétua
- Idiomas
- 11 idiomas
Compra Única
UAE VAT & E-Invoicing for POS (Peppol/FTA)
FTA-compliant UAE tax invoices and Peppol/PINT-AE-ready e-invoices emitted directly from the ERPNext POS, with bilingual Arabic/English receipts, TRN validation, and 5% VAT plus exemption handling. Built, installed, and supported by ECOSIRE on your ERPNext v15/v16 instance.
$499.00USD
Sem pagamento agora. Isto envia um pedido de orçamento à nossa equipe — responderemos por e-mail com preços e próximos passos.
Recursos Principais
Dedicated Frappe app packaged as its own module, installed on your bench via `bench get-app`/`bench install-app` — no monkey-patched core files
FTA-compliant UAE tax invoice DocType (or extension of `POS Invoice`/`Sales Invoice`) with seller/buyer TRN, invoice type code, and credit-note reference chain
Peppol / PINT-AE UBL XML e-invoice generation produced on `on_submit` via a `doc_events` hook in `hooks.py`
TRN format and checksum validation on both seller and customer, enforced in the DocType `validate` hook and surfaced as a POS client script prompt
Per-item tax category handling — standard-rated 5%, zero-rated, exempt, and out-of-scope — with FTA-conformant line and total rounding
Bilingual Arabic/English tax-invoice print format with correct RTL layout for the customer receipt
Whitelisted `@frappe.whitelist()` methods plus Frappe REST API endpoints for e-invoice submission and status retrieval
Access Point / FTA channel transmission with clearance reference, acceptance status, and error payload stored back on the record
`scheduler_events` background jobs for automatic retry of failed transmissions and periodic reconciliation of pending invoices
POS-side client scripts for cashier TRN capture, live validation, and inline VAT breakdown without slowing the checkout flow
Role profiles and DocType permissions restricting who can void, re-issue, or resubmit a compliant invoice, with an auditable trail
Credit note / return handling that emits a compliant corrective e-invoice linked to the original document
Configurable seller identity, VAT registration, and Peppol participant ID stored in a single settings DocType rather than hardcoded
Built and tested against Frappe/ERPNext v15 and v16 on a staging clone before any production change
Sobre este Produto
UAE retailers and restaurants running high-volume checkout on ERPNext hit a wall the moment the FTA's e-invoicing mandate and Peppol interoperability enter the picture. Stock ERPNext POS issues a simplified sales receipt and a generic print format — it does not produce a legally structured UAE tax invoice with mandatory TRN, bilingual Arabic/English fields, correct rounding, and a machine-readable Peppol/PINT-AE payload. Restaurants layering service charges, mixed 5%-VAT and zero-rated/exempt items, and split payments on a single ticket make this worse: the native tax templates and print formats simply were not designed for the FTA layout or for emitting a UBL-based e-invoice to an Access Point. Bolting this on with ad-hoc client scripts leaves you with fragile, unauditable receipts.
Por Que Escolher UAE VAT & E-Invoicing for POS (Peppol/FTA)
Dedicated Frappe app packaged as its own module, installed on your bench via `bench get-app`/`bench install-app` — no monkey-patched core files
FTA-compliant UAE tax invoice DocType (or extension of `POS Invoice`/`Sales Invoice`) with seller/buyer TRN, invoice type code, and credit-note reference chain
Peppol / PINT-AE UBL XML e-invoice generation produced on `on_submit` via a `doc_events` hook in `hooks.py`
TRN format and checksum validation on both seller and customer, enforced in the DocType `validate` hook and surfaced as a POS client script prompt
Per-item tax category handling — standard-rated 5%, zero-rated, exempt, and out-of-scope — with FTA-conformant line and total rounding
Bilingual Arabic/English tax-invoice print format with correct RTL layout for the customer receipt
ECOSIRE builds a proper Frappe app — its own module with versioned DocTypes, hooks.py doc events, server scripts, whitelisted API methods, and print formats — installed on your bench alongside ERPNext. We model an E-Invoice (or extend POS Invoice / Sales Invoice) with the fields the FTA requires: seller and buyer TRN, invoice type code, line-level tax categories, and the reference chain for credit notes. A validate and on_submit hook wired through doc_events runs TRN format/checksum validation, computes 5% VAT against per-item tax categories (standard-rated, zero-rated, exempt, out-of-scope), applies FTA-conformant rounding, and generates the Peppol/PINT-AE UBL XML. The bilingual tax-invoice print format renders Arabic and English side by side for the customer receipt, and the POS flow is kept fast so cashiers see no lag at the till.
On the interoperability side, a whitelisted method (@frappe.whitelist()) and the Frappe REST API expose e-invoice submission and status, so the generated document can be transmitted to your chosen Peppol Access Point / FTA channel and the response (acceptance, clearance reference, errors) is stored back on the record and shown in the POS. Scheduler events (scheduler_events in hooks.py) handle ret/retry of failed transmissions and periodic reconciliation, and everything is guarded by ERPNext role profiles and permissions so only authorized roles can re-issue or void a compliant invoice. Client scripts add the cashier-facing TRN capture and validation prompts inside the POS UI. The app targets Frappe/ERPNext v15 and v16.
Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, confirm your exact FTA/Peppol channel, item tax structure, receipt language rules, and POS profiles, then build against a staging copy of your instance. You get UAT on staging with a rollback plan, installable source in a Git repo we hand over, install and configuration on your production bench, technical and user documentation, a training session, and a post-go-live support window. Typical delivery is 2-4 weeks from confirmed scope.
O que você ganha
- Installable source code for your version of the app, delivered as a proper Frappe app
- Installation and configuration on your ERPNext production bench (POS profiles, tax categories, settings DocType, Peppol/FTA channel)
- Technical documentation covering DocType schema, hooks, whitelisted methods, and scheduler jobs
- End-user guide for cashiers and finance staff plus a live training session
- Post-go-live support window for defect fixes and configuration adjustments
- UAT on a staging clone with a documented test plan and a rollback plan
- Handover of the full Git repository with commit history and README
Para quem é isso
UAE Retail Operations Manager
Runs multi-branch retail on ERPNext POS and needs every till to issue an FTA-compliant, bilingual tax invoice and a Peppol-ready e-invoice without slowing cashiers or creating reconciliation gaps.
Restaurant / F&B Owner
Handles mixed 5%-VAT, zero-rated, and exempt items, service charges, and split payments on a single ticket, and needs each receipt to be legally structured and transmittable to the FTA channel.
Finance & Tax Manager
Owns VAT filing and audit readiness; wants TRN validation, correct rounding, per-item tax categories, and a full audit trail of issued, cleared, and voided e-invoices inside ERPNext.
ERPNext System Administrator
Maintains the bench and needs a clean, versioned Frappe app with documented DocTypes, hooks, and permissions that installs on v15/v16 and can be upgraded without breaking core ERPNext.
Visão geral da instalação
Baixe do ECOSIRE
Compre a licença em ecosire.com e baixe o ZIP do aplicativo UAE VAT & E-Invoicing for POS (Peppol/FTA) no painel da sua conta.
Adicione o aplicativo à sua bancada
Extraia o ZIP na pasta de aplicativos do seu banco ou execute `bench get-app` com o caminho para o aplicativo extraído.
Instale no seu site
Execute `bench --site SITE_NAME install-app APP_NAME` seguido de `bench Migra` para instalar UAE VAT & E-Invoicing for POS (Peppol/FTA) e aplicar seu esquema.
Ative sua licença
Abra as configurações de licença ECOSIRE em seu site e ative sua chave de licença. Requer os aplicativos gratuitos ecosire_connect e ecosire_license_client.
Como UAE VAT & E-Invoicing for POS (Peppol/FTA) se compara
| Critério | ECOSIRE | Construção personalizada | Concorrente | Odoo nativo |
|---|---|---|---|---|
| UAE FTA tax invoice layout | Purpose-built compliant bilingual print format | Buildable but you design it from scratch | Generic template, often KSA/EU-focused | |
| Peppol / PINT-AE e-invoice | UBL XML generated and transmitted | Feasible with significant dev effort | Sometimes, rarely UAE PINT-AE profile | |
| TRN validation | Format + checksum, enforced at POS | Depends on developer scope | Basic field capture if present | |
| 5% VAT + exemption handling | Per-item categories with FTA rounding | Manual tax templates to configure | Standard-rate focused, limited exemptions | |
| Bilingual Arabic/English receipt | Side-by-side RTL layout included | Custom print format work required | English-first, partial Arabic | |
| ERPNext v15/v16 fit | Built and tested for your bench | Depends on the team's ERPNext depth | May lag core versions | |
| Source code ownership | Full Git repo handed over | You own what you pay to build | Licensed, usually closed | |
| Support and go-live | UAT, rollback plan, support window | Whatever you contract separately | Vendor ticket queue |
Perguntas frequentes sobre UAE VAT & E-Invoicing for POS (Peppol/FTA)
+Is this an existing app I can download and install right now?
No. This is a build-to-order engagement — ECOSIRE builds, installs, and supports the app for your specific FTA/Peppol channel, item tax structure, and POS profiles. There is no instant download. We scope it with you first, then build against a staging copy of your instance.
+How long does delivery take?
Typical delivery is 2-4 weeks from confirmed scope. The timeline starts once we have agreed the exact requirements on the scoping call — your Peppol Access Point / FTA channel, receipt language rules, tax categories, and POS profiles — and depends on the complexity of your setup and how quickly staging access and test data are available.
+How are updates and support handled after go-live?
Every engagement includes a post-go-live support window for defect fixes and configuration adjustments. Because you receive the full Git repository, your team can maintain it, or ECOSIRE can provide ongoing support and version upgrades under a separate arrangement. The app is built cleanly against v15/v16 so ERPNext upgrades don't force a rewrite.
+Which ERPNext versions are supported?
The app is built and tested against Frappe/ERPNext v15 and v16. We confirm your exact bench version during scoping and target it specifically. It installs as a standard Frappe app via `bench get-app` and `bench install-app` — no core files are patched.
+How does the Peppol / FTA e-invoice actually get transmitted?
On submit, a `doc_events` hook generates the Peppol/PINT-AE UBL XML. A whitelisted method transmits it to your chosen Access Point or FTA channel, and the response — clearance reference, acceptance status, or error payload — is stored back on the record and shown in the POS. Failed transmissions are retried automatically via a scheduler job.
+Will it slow down my POS at the till?
No. The heavy work — UBL generation and transmission — runs on submit and through background scheduler jobs, not on every keystroke. The cashier-facing pieces are lightweight client scripts for TRN capture and validation, so checkout stays fast even at peak.
+Do you handle credit notes and returns?
Yes. Returns and corrections emit a compliant corrective e-invoice linked back to the original document, preserving the reference chain the FTA requires. Void and re-issue actions are permission-gated by role profile and fully audit-logged inside ERPNext.
Solicitar orçamento
UAE VAT & E-Invoicing for POS (Peppol/FTA)
FTA-compliant UAE tax invoices and Peppol/PINT-AE-ready e-invoices emitted directly from the ERPNext POS, with bilingual Arabic/English receipts, TRN validation, and 5% VAT plus exemption handling. Built, installed, and supported by ECOSIRE on your ERPNext v15/v16 instance.
- Dedicated Frappe app packaged as its own module, installed on your bench via `bench get-app`/`bench install-app` — no monkey-patched core files
- FTA-compliant UAE tax invoice DocType (or extension of `POS Invoice`/`Sales Invoice`) with seller/buyer TRN, invoice type code, and credit-note reference chain
- Peppol / PINT-AE UBL XML e-invoice generation produced on `on_submit` via a `doc_events` hook in `hooks.py`
- TRN format and checksum validation on both seller and customer, enforced in the DocType `validate` hook and surfaced as a POS client script prompt