Skip to content

Guides · JoFotara registration

Link your device on the JoFotara portal before the first submit

JoFotara device linking and API credentials. Link your device on the JoFotara portal before the first submit: without a Client-Id and Secret-Key issued by the official portal, submission will not authenticate, and no software connector can invent those values.

Registration is taxpayer work on the JoFotara portal, not a marketing step. After sign-in you create an identity for the device or billing system, and the portal issues the two authorization values. Those values go into a secret store, then into runtime configuration, then a single invoice is submitted with the response stored. BarmajTek can build the connector and train the operator; we do not sign in as the taxpayer to create the account.

Copy reviewed on 2026-08-26.

In operations

Four rules that show up on day one

  • Portal first

    Do not start coding submission before the accountant has an account and knows where the linking control is.

  • Secrets stay off screen

    The Secret-Key is not a field on the customer invoice and not a screenshot in a support chat.

  • Test rejection before the rush

    The first data error should appear in a calm rehearsal, not at peak till time.

  • Rotate on leak

    If a key appears in a repository or mailbox, revoke the portal profile and create a new one.

Visible steps

Follow the sequence as written

  1. Confirm the taxpayer account on the Department portal

    Use the official channels: the Department site and the JoFotara portal. The account is the taxpayer’s or their fiscal representative’s, not the software vendor’s.

  2. Open device and system linking

    From the portal menu open device and system linking. That is where the sending system’s identity is created, not on the daily invoice screen.

  3. Register a profile for the device or billing server

    Name the profile so your team can recognise it later: a till, a billing server, or an internal trial environment if the Department offers one on your account.

  4. Copy the Client-Id and Secret-Key into a secret store

    After registration the portal shows two values that normally persist. Store them in a secret vault or encrypted configuration. Do not put them in a repository or a public support ticket.

  5. Bind the values in the billing system without printing them

    The system must read the values from runtime configuration, not from a file on an accountant’s desktop. Record who may change them, and rotate the profile if a key leaks.

  6. Submit a trial invoice and store the full response

    Do not stop at an on-screen success toast. Persist status, identifier, and any rejection reason. If no trial environment is available, use the smallest lawful document the accountant approves.

  7. Train the operator on the rejection screen

    Before go-live, a staff member should reproduce a rejection, correct the source, and resubmit. If only a developer can fix it, the till will stop at the first data error.

  8. Review daily reconciliation with accounting

    Match accepted invoices to the till before the gap grows. A technical connector does not replace an exception list with an owner.

Why a step page separate from the technical guide

A search for “JoFotara registration” or “device linking” is a different intent from a developer looking for the invoice document. Mixing them under one title weakens both. This page is for the party that owns the tax account. The technical guide is for the developer who will parse the response. The commercial service is for teams that want BarmajTek to build the connector.

What can change in the portal without freezing a screenshot

Menu labels can change. The principle does not: taxpayer account, device link, two authorization values, secret storage, a trial submit. If the label differs, use portal help or Department channels, not an old blog screenshot. We do not attach interface pictures that can be wrong within a week.

Who should not hold the key

Till staff, a UI contractor, a hardware vendor, and a shared mailbox are not places for the Secret-Key. Limit access to whoever runs the server or the secret vault. When a software contract ends, rotate the key so access does not outlive delivery.

A clinic is not exempt from these steps

Clinic Tek submits invoices after the establishment has linked its account. The clinic JoFotara page explains the consult day; this page explains how credentials were born. Do not mix them, and do not buy a subscription expecting “accreditation to arrive with the software”.

After the steps are done

Read the developer guide if you are building the connector, the service page if you want a team to implement it, or the correction guide if the worry is after acceptance rather than before the first submit.

No. The account is in the taxpayer’s name. We coach the steps and build the connector after the portal issues the values.

Once linking is done, build the connector

The steps above are taxpayer work. Engineering comes after, on the current billing system or inside Clinic Tek.