Export and submission
Understand export, submission, receipt, and acceptance
Keep product artifacts and external authority outcomes distinct and preserve evidence for each step.
Who should read this
Anyone responsible for delivering an artifact or recording an authority outcome.
The four distinct events
- Export: SolvencyBridge generates an artifact from an approved snapshot.
- Submission: an authorized person or supported transport sends that exact artifact through the required external channel.
- Receipt: the authority channel acknowledges that it received or registered something.
- Acceptance: external evidence reports an accepted terminal outcome under the authority’s process.
Before submission
Confirm the artifact identity and checksum, destination, portal account, deadline, required accompanying documents, and approved procedure. Never infer the destination from a filename alone.
Steps
- Generate and verify the approved artifact.
- Submit it through the authority’s current approved channel outside the product unless an explicitly supported transport says otherwise.
- Capture the external reference, timestamp, status, and evidence.
- Where the filing exposes a dedicated receipt or status control, record the evidence there. NBS ESAS guidance and field labels follow the active interface language, but the status choices retain the exact authority-native codes and Slovak labels:
ROZPRACOVANA(Rozpracovaná),SPRACOVAVANA(Spracovávaná),SKONTROLOVANA(Skontrolovaná),ODMIETNUTA(Odmietnutá),NA_PODPIS(Na podpis), andPRIJATA(Prijatá). Do not translate or reinterpret those evidence values. - Correlate every response to the exact submission and artifact.
- Continue follow-up until your approved process identifies a terminal result.
Expected result
The filing history distinguishes internal export from externally evidenced submission, receipt, rejection, correction, or acceptance.
How to verify
Compare artifact checksum or identity, portal reference, entity, period, submission time, and returned evidence. A portal login or upload screen alone is not acceptance evidence.
Common problems
Queued, processed, received, valid, accepted, rejected, and correction-required can have profile-specific meanings. Use the product’s exact profile guidance and the authority’s current instructions.
Consequences and limitations
Recording an outcome without correlated evidence can misstate filing status. SolvencyBridge never labels a generated export as authority accepted merely because generation succeeded.