Trade Register filing assistant (Chrome)

Optional beta — may fill some non-sensitive fields and shows an attachment checklist; it does not replace the in-app step-by-step guide or your checks in EPZEU.

Official filing happens in the Registry Agency portal (EPZEU). Firmify gives you a signed document pack and a guide; the extension is extra help for EOOD only, and only when filing assist is enabled for your account.

1. Install the extension (Chrome)

  1. Open chrome://extensions, enable Developer mode, click Load unpacked, and select the dist folder for Firmify TR Filing Assistant (from a cloned repo: at the monorepo root run pnpm --filter filing-extension build:dist, then pick apps/filing-extension/dist). Do not load a folder that contains underscore-prefixed directory names — Chrome will refuse.
  2. Pin the extension icon to the toolbar (puzzle icon → pin) for quick access to the popup.
  3. If you use staging/local APIs, set the correct API base in the popup instead of the production URL.

Beta; Chrome Web Store distribution when available. If API calls fail, your administrator must enable filing assist and add your chrome-extension:// origin for CORS.

If you point the popup to an API host not listed in the extension manifest (e.g. staging or local), add that HTTPS origin under host_permissions in manifest.json and reload the extension in chrome://extensions — otherwise Chrome blocks the fetch before CORS even applies.

2. Token from Firmify

Sign in and open your organization with a signed pack (EOOD). On the Submit to Trade Register page, create a token for the extension and copy the full string — a short-lived JWT bound to the organization.

Go to dashboard

3. EPZEU portal

Open electronic application A4 in a new tab, sign in with a qualified electronic signature, and move through the sections following the Firmify guide.

4. Extension popup

  1. Keep the EPZEU tab active where you will apply data (active tab in the window).
  2. Paste the token and click save / fetch / apply.
  3. Review diagnostics (section, applied keys); if mapper versions differ between API and the extension bundle, verify fields manually.
  4. Cross-check every value against your signed articles before paying and signing in EPZEU.

Logging out of Firmify does not clear the extension token — use Clear saved token in the popup before handing off the device.

5. Attachments (PDFs)

The extension does not upload files. The ordered list in the popup (TR slot → filename) helps you match the Firmify ZIP to upload fields; mark Original where required.

When the assistant is unavailable or applies nothing

  • EOOD with signed pack only; OOD and other flows use the in-app guide only.
  • Applicant / identity and sensitive identifiers are filled manually in EPZEU.
  • If EPZEU changes its UI, autofill may match zero fields — use the copy cards from the guide.
  • Filing, payment, and signing remain your responsibility in the portal.
Important: The token grants access to a filing payload projection for your organization — do not share it.

Security and privacy

  • Tokens expire; create a new one after organization changes.
  • Do not store the token in shared notes or screenshots.
  • The extension sends the token only to your configured Firmify API and passes data to the active EPZEU tab — not to third parties.
  • If anything looks wrong, stop and reconcile with the signed pack and EPZEU before submitting.
Chrome assistant for A4 filing (EPZEU) | Firmify | Firmify