Designed scope
- separate generator per form
- durable submission queue
- final result and corrections
Planned product · enquiries only
RDCopilot Declarations
Declarations treated individually, not as one generic compliance checkbox.
01 / Workflow
From intent to a verifiable trail
Each of D300, D390, D394, D100, D101 and D406 covers generation, validation, signing, submission and final result.
Every operation retains company identity, actor, and source linkage.
Acceptance requires tests against the actual authorized version, integration, and data.
02 / Scope
Capabilities and boundaries
Not yet validated
- None of the six workflows is accepted as release-ready.
- XML export alone does not prove automatic submission.
03 / API
Controlled integrations
Connections use authenticated APIs and durable events. Single sign-on does not replace data synchronization, and each service retains its declared authority.
- ANAF DUKIntegrator
- Accounting API
- e-Factura
04 / Docs
Public integration notes
Working contract
Commands require an idempotency key, legal company, actor, source, and timestamp. Corrections use linked reversals and never silently rewrite history.
Access and availability
There is no validated application entry yet. The /app route does not redirect until origin, path, license, and release evidence are approved.
Price and inclusions
No price is published. Commercial, tax, refund, and support policies are unapproved; this page supports enquiries only.
05 / FAQ
Factual answers
Is the product available now?
No. Its status is planned and the offer is enquiry-only.
Can I purchase online?
No. There is no approved price or checkout.
What does this page prove?
It describes planned public scope and its boundaries; it does not prove production availability, certification, or acceptance.