The salesperson scans the products, scans the buyer's IDNO, the system confirms the company details from SFS and generates the invoice: draft → sign → post → status tracking — all in roughly 5 seconds. You never open the SFS portal again. The certificate stays yours; we are only the technical channel that automates the process, and on a connection error the system retries on its own until SFS responds. Unlimited on the Standard / Extra packages, with no per-document cost.
Five steps, all automated. The operator confirms only at the start and at the end — everything else happens in the background.
You add the lines from the POS, from online orders, or manually. The system validates the buyer's IDNO against the SFS database — autocomplete for name, address, tax code. It automatically calculates TVA by rate (8% / 12% / 20% / 0% / no TVA) depending on the product, and validates incremental numbering with no gaps in the series.
The invoice is sent to the e-Factura SFS portal via API, authenticated with your dedicated user-api credentials for the module (generated separately in the e-Factura SFS portal, not a USB token). Signing remains the operator's responsibility according to SFS procedure — we only facilitate the submission.
Within a few seconds you get: OK with a unique SFS RID, or a validation error with a clear message about the problematic field (correct → resubmit). If the SFS API is temporarily unresponsive, the invoice stays in draft — the operator resubmits it when SFS is back online.
After submission the invoice enters one of the states: Pending acceptance (awaiting the buyer), Accepted (confirmed, becomes final), Rejected (refused with a reason). Status updates with SFS are semi-automatic — the operator presses the sync button in the platform and the dashboard refreshes.
On a goods return or an error caught late: the cancellation or reversal request follows the SFS procedure and is semi-automatically trackable in the platform — the system shows you the status at every step, the decision remains the operator's. Full audit: who, when, reason.
If SFS refused on validation (rare — meta-validations), the system tells you the exact problematic field. You correct it and press Resubmit → the flow resumes from the submission step. No manual duplication of data.
The daily scenario in a network of 4 stores and a central warehouse, as it runs today.
A corporate customer asks for an invoice for 50 footballs. The salesperson scans the products, scans the IDNO, the system confirms the company details from SFS and generates the invoice: draft → sign → post → status tracking. If SFS rejects (rare), you immediately get the exact wrong field and the resubmit button.
Unlimited on any package, within the included traffic. We do not charge per e-Factura — metering is on traffic and storage, included in the base package. Fast issuance even for chains with 50,000 invoices per year — performance does not degrade.
If the buyer's IDNO does not appear in the SFS database, we receive a restriction from SFS and the invoice cannot be issued to that buyer. The fix: the buyer registers with SFS, or you choose another method (a plain fiscal receipt, without e-Factura).
We do not generate a periodic export file. The accountant can pull invoices via the ERP API — with a custom setup we build on request the periodic extraction logic in the format preferred by their accounting software (1C, SAGA, BAS, InfoCont, etc.). Individual quote after evaluation.
The flow is only legal if your signature remains yours. Here is how we keep the technical pace without touching the signatory's responsibility.
These are not generic SFS credentials, and we do not use a USB token for the API — authentication is via user-api e-Factura per the official standard. Setting it up in the platform is paid support effort, on request, priced in hours after evaluation.
The cache of invoices processed through the platform is stored on servers with role-based access and an immutable audit log, TLS communication and off-site backups with restricted access. The official source of truth remains SFS (the e-Factura system).
Every call to the SFS API runs over HTTPS with certificate validation. Access to the module is restricted through permissions with point-of-sale scoping, configured at onboarding based on the roles in your team.
You. We do not issue on your behalf. We use your dedicated user-api credentials for the e-Factura module (generated separately in the SFS portal, not a USB token). Signing remains the operator's responsibility according to SFS procedure — we only facilitate submission and status tracking.
A few seconds — from scanning the products and confirming the IDNO, all the way to the response with the official SFS RID, under normal conditions. If the SFS API is temporarily unresponsive, the invoice stays in draft — you resubmit it when SFS is back online.
No. Unlimited on any package, within the included traffic (an internal technical rate-limit is configurable per account to respect SFS quotas). We do not charge per document — metering is on traffic and storage, included in the package. Chains with 50,000 invoices per year issue with no performance degradation.
The status update with SFS is semi-automatic — the operator presses the sync button in the platform and the system updates the Pending acceptance / Accepted / Rejected states in the dashboard. On reject you get the reason and decide: correction + resubmit or cancellation.
Yes, semi-automatically. Cancellation and reversal follow the SFS procedure and are semi-automatically trackable in the platform — operator action is required at each step. An important note: deleting the leftover draft on the SFS portal is done manually by the operator directly in the e-Factura portal (we do not do it from the platform). The audit remains complete: who, when, reason.
We do not generate a periodic export file. The accountant can pull invoices via the ERP API — with a custom setup we build on request the periodic extraction logic in the format preferred by their accounting software (1C, SAGA, BAS, InfoCont, etc.), priced individually after evaluation. Your data stays accessible self-service via export at any time.
We configure the roles at onboarding. Access to the e-Factura module is restricted via permissions with point-of-sale scoping — an operator from Store 2 cannot issue for Store 4 without an explicit right. All actions (issuance, cancellation, resubmission) go into an immutable audit log.
B2B sales + full e-Factura is included in both Standard and Extra for Large Retail, plus the certified fiscal register and B2C e-Factura. The exact comparison of the packages, with what Extra adds (multi-warehouse, multi-provider e-commerce, higher ceilings) — on the Decision-maker page.
The structures above reflect our standard offer, but every customer is discussed individually. We adjust scope (activated modules, accounting integrations, per-point-of-sale setups), onboarding timelines and specific configurations depending on your business. The final binding offer is the one in the written quote + signed contract. For custom cases (integration with an internal ERP, an unlisted accounting format, migration from another system) we quote in support hours after evaluation, not at a fixed price.
20 minutes on the phone and we walk you through exactly what issuing, signing, posting and tracking a B2B e-Factura looks like for your profile (number of locations, estimated volume, accounting format used). Setting up the user-api credentials, mapping the TVA rates, integrating with the fiscal register and the export to the accountant all happen at onboarding — we configure them for you.
We spend 20 minutes together looking at your chain — number of locations, monthly B2B invoice volume, accounting format used, existing integrations. The initial consultation is free.
SGAPPS LABS SRL · Chișinău, Moldova · Continuously in production since 2018 · POS · ERP · MEV fiscal register · B2B / B2C e-Factura