A build-to-order SAP Business One add-on that produces RO e-Factura XML from your A/R Invoices,
uploads it to ANAF, polls the returned upload index and records the per-invoice outcome against the marketing document.
Sur commande
A build-to-order SAP Business One add-on that produces RO e-Factura XML from your A/R Invoices, uploads it to ANAF, polls the returned upload index and records the per-invoice outcome against the marketing document. Built to order by ECOSIRE for SAP Business One (build-to-order) — indicative price from $1499.00 USD; request a quote for a scoped proposal.
Romania's RO e-Factura mandate covers B2B and B2G invoicing, and it is not a print job. Each invoice has to be rendered in the required XML structure, uploaded to ANAF, and then followed — because the upload returns an index, not a verdict. The verdict arrives later, and it can be an acceptance, a validation rejection, or nothing at all if the upload never landed.
SAP Business One has no concept of any of this. It posts the A/R Invoice and the Journal Entry correctly and stops there. Which means somebody in finance ends up owning a spreadsheet of upload indexes, polling a portal by hand, and trying to reconcile which of last week's 200 invoices actually cleared. The failure mode is quiet: an invoice looks fine in SAP B1, sits in the aging report, gets chased for payment — and was rejected by ANAF eleven days ago for a missing buyer tax code that nobody looked at.
That asynchronous gap between uploaded and accepted is the entire problem, and it is exactly what native SAP B1 cannot express.
We build a per-tenant SAP Business One add-on that generates, uploads, polls and reconciles RO e-Factura submissions, using SAP's supported extensibility surfaces only.
A/R Invoices and A/R Credit Memos are read through the Service Layer (Invoices, CreditNotes) and mapped to the RO e-Factura XML structure. The mapping is explicit and delivered as a written specification you can audit: Business Partner identification (CUI/CIF, registration data, addresses), header fields, line-level item codes and unit of measure, quantities, net amounts, discount treatment, and the VAT breakdown built from the document's SAP B1 tax codes so the XML totals reconcile to the posted Journal Entry. Fields with no native home get a UDF on the correct object — OINV, ORIN, OCRD — driven by a formatted search or validated value list rather than free text.
Upload is handled by the add-on service. The returned upload index is immediately persisted to a UDO submission record alongside the source document key, the generated payload, the timestamp and the current state. Nothing is transient; if the process is killed mid-run, the index is already durable and the poller will pick it up.
A scheduled poller walks every submission that is not yet in a terminal state, queries ANAF for the outcome against its stored index, and transitions the record. On acceptance, the returned identifier and the signed response are written back to locked UDFs on the source invoice and archived on the submission record. On rejection, the validation errors are parsed into readable reasons and the invoice is flagged for correction. Polling is idempotent and rate-aware — the same index is never double-claimed, and a document already in a terminal state is never re-uploaded by accident.
A Crystal Report shows, for any date range: invoices posted, invoices uploaded, uploads accepted, uploads rejected with reason, and — the important one — invoices posted but never uploaded. That last bucket is where compliance gaps hide, and it is the first thing a finance manager should be able to see. Drill-through takes you straight to the offending A/R Invoice.
Pre-upload validation runs the same rules as the schema: Business Partner tax identification present and well-formed, every line carrying a tax code, currency and rounding consistency, numbering series integrity, and the B2G-specific fields where the recipient is a public institution. Failures surface before upload rather than as a rejection days later. Where you want a human gate, the add-on hooks into standard approval procedures so flagged invoices need sign-off before transmission.
A/R Credit Memos are generated and uploaded in the same flow, with the reference to the corrected invoice resolved from the SAP B1 base-document link so nobody types an identifier by hand.
Companies running SAP Business One with a Romanian legal entity issuing B2B or B2G invoices — distributors, manufacturers, construction and services businesses, and any supplier to Romanian public institutions. It also fits multi-country groups where the Romanian company is one database among several and the group wants Romania handled inside SAP B1 rather than in a parallel tool.
If you issue a handful of invoices a month and are content to upload them manually, this will not pay for itself. The value is in volume, in the polling loop, and in never again discovering a silent rejection at month end.
Built as a SAP Business One add-on and integration layer on the Service Layer (REST) for document read and UDF write-back, the DI API where a transaction demands it, and UDO/UDF/UDT for the submission ledger, poller state and configuration. Compatible with SAP Business One 10.0 on Microsoft SQL Server and on SAP HANA, on-premise or cloud-hosted. Endpoints, credential references, in-scope numbering series, polling interval and approval thresholds live in a setup UDT, so moving between test and production is a configuration change rather than a rebuild.
Nothing is pre-built and there is no instant download. Each deployment is built for your company database and your document flow.
1. Scoping call. We walk your invoice types, numbering series, tax codes, Business Partner master data quality, B2G exposure and correction process, and we identify what is missing for the schema before quoting. 2. Fixed quote. Written scope, fixed price, no hourly drift. 3. Build. Typical lead time is one working week from signed scope, depending on document types in scope and master-data remediation. 4. Install into your test company. Installed into the test database first and exercised with your own real documents end to end — including a deliberate rejection and a credit memo — so you see the failure path, not just the happy path. 5. Install into production. After test sign-off, installed into the production company database with a supervised first upload and polling window. 6. Support. A support window follows go-live for defect fixes and adjustments arising from real use.
You own the deployment. Source is delivered with it, documented, and maintainable by your own team or your SAP B1 partner.
A short call to confirm the workflow, your platform version and where the integration boundaries sit.
You receive a written scope and a fixed price. Nothing is built until you approve it.
We develop against a copy of your configuration and test it there. Typically two to four weeks.
Nous installons sur votre instance, vous remettons le code source et incluons deux semaines d'assistance après la mise en production. Les défauts du code que nous livrons sont corrigés gratuitement.
Is accountable for whether every issued invoice actually reached ANAF and cleared, and today has no way to prove it from inside SAP Business One. Gets a reconciliation report that explicitly surfaces invoices posted but never uploaded, which is the gap that otherwise goes unnoticed until an audit.
Has to deliver e-Factura compliance without a second system running beside SAP B1 and without unsupported database modifications. Gets a Service Layer and UDO based add-on with source code, a documented object inventory and configuration held in a UDT rather than hardcoded.
Runs a team that currently tracks upload indexes in a spreadsheet and checks the portal by hand. Gets an automatic poller that closes each submission out on its own and a work queue of only the invoices that genuinely need human attention.
| Critère | ÉCOSIRE | Construction personnalisée | Concurrent | Natif SAP Business One |
|---|---|---|---|---|
| Generates RO e-Factura XML from SAP B1 marketing documents | Inclus | Prise en charge partielle | Inclus | Non inclus |
| Asynchronous status polling against the stored upload index | Inclus | Non inclus | Prise en charge partielle | Non inclus |
| Per-invoice ANAF outcome written back onto the source document | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Report surfacing invoices posted but never uploaded | Inclus | Non inclus | Non inclus | Non inclus |
| B2G-specific field handling driven from Business Partner classification | Inclus | Prise en charge partielle | Prise en charge partielle | Non inclus |
| Source code delivered and owned by the customer | Inclus | Inclus | Non inclus | Non inclus |
| Built on Service Layer and UDO extensibility with no base-table writes | Inclus | Prise en charge partielle | Prise en charge partielle | Inclus |
| Fixed-price scope agreed before build starts | Inclus | Non inclus | Prise en charge partielle | Non inclus |
A build-to-order SAP Business One toolkit that maps, validates and imports QuickBooks chart of accounts, master data, open items and history — with reconciliation proof at every step, before go-live.
A build-to-order SAP Business One add-on that adds rule-based product configuration, guided selling, live costing and margin approval to B1 quotations. Built for your product rules after a fixed quote.
Transmits SAP Business One A/R Invoices and Credit Memos over the Peppol network as InvoiceNow documents, with inbound receipt into A/P. Built to order for your company database.
A build-to-order SAP Business One integration that turns Stripe charges, refunds, fees, disputes and payouts into Incoming Payments and Journal Entries. Built and installed for your tenant.