Fintura
Fintura logoPaySpace logo
Data pulled in

Fintura PaySpace integration

Authorise the connection once and the EMP201 fills itself from the closed payroll run, with no key passed between systems and no figures retyped.

What is the Fintura PaySpace integration?

The Fintura PaySpace integration is an authorised, read-only link between PaySpace and Fintura's tax module. You approve Fintura from within PaySpace rather than issuing it a key, and from then on any EMP201 can be filled from the period's closed payroll run instead of typed up from a report.

Because the connection is authorised rather than key-based, there is nothing to copy between systems, nothing sitting in a password manager, and nothing to rotate when somebody leaves. Access is revoked from PaySpace whenever you choose.

What syncs, and in which direction

Every row is what the PaySpace connection does today.

What syncs between Fintura and PaySpace, in which direction, when it happens, and what happens.
DataDirectionWhenWhat happens
PAYE, UIF and SDL amountsPaySpace to FinturaOn Import from payroll, per periodThe period's totals land on the EMP201 for the client and payroll company you mapped together.
The ETI blockPaySpace to FinturaOn Import from payrollBrought forward, utilised and carried forward arrive with the month's amount, so the incentive reconciles rather than appearing as a single figure.
ETI compliance warningPaySpace to FinturaOn import, where PaySpace raises oneThe warning travels with the import and sits on the result, so it is read before submission rather than after it.
PAYE and UIF reference numbersPaySpace to FinturaOn import, only where Fintura holds noneAn empty reference is filled in; one you have already captured is left exactly as it is.
The authorised connectionIn FinturaOn approval, and until you revoke itApproving Fintura from PaySpace establishes the link. Revoking it in PaySpace ends Fintura's access without anyone editing settings on this side.
Client to payroll company mappingIn FinturaOn setup, and whenever you change itEach Fintura client points at the payroll company holding its figures, which is what an import follows to find them.
The return totalIn FinturaOn import, and on every editFintura adds the imported figures up itself rather than accepting a total, which is what leaves penalty and interest editable afterwards.

How you would use it

  1. Authorise Fintura from PaySpace

    Tax, then Integrations, then Payroll Connections, then Connect PaySpace. You are sent to PaySpace to approve the access and returned to Fintura with the connection live. Nothing is copied by hand.

  2. Point each client at its payroll company

    On the Client Payroll Mapping tab, tell Fintura which payroll company holds each client's figures. An unmapped client has nowhere to import from.

  3. Fill the EMP201 from the closed run

    Open the client's EMP201 for that period and choose Import from payroll. PAYE, UIF, SDL and the ETI block populate, and any compliance warning PaySpace raised comes with them.

  4. Check it against the payroll report, then submit

    Compare the figures, add penalty or interest if the period calls for it, and submit. The total is worked out by Fintura, so your edits carry through.

What it does not do

  • Never writes to PaySpace. The authorisation is read-only, so no Fintura action can reach a payroll run.
  • Does not run payroll. PaySpace remains your payroll system and Fintura replaces none of it.
  • Does not pull employees, payslips or leave. Only the figures an EMP201 needs come across.
  • Does not import on a schedule. Somebody opens the return and asks for the period.
  • Does not return the SDL reference number. Capture it once on the client's tax configuration screen.
  • Does not return the ETI employee count.
  • Does not populate EMP501 reconciliations.
  • Does not import several periods at once.
  • Does not overwrite a PAYE or UIF reference you have already captured.

Three steps to connect PaySpace

  1. 1

    Start the connection in Fintura

    Go to Tax, then Integrations, then Payroll Connections, and choose Connect PaySpace.

  2. 2

    Approve the access in PaySpace

    You are handed to PaySpace to sign in and approve Fintura. There is no key to generate, paste or store, and you can withdraw the approval from PaySpace at any time.

  3. 3

    Point each client at its payroll company

    On the Client Payroll Mapping tab, link every Fintura client to the payroll company its figures sit in.

FAQ

Frequently asked questions.

What South African firms ask about PaySpace in Fintura.

By approving it in PaySpace. Fintura sends you across to sign in and authorise the access, then returns you with the connection live, so there is no API key to generate, paste between systems or keep in a password manager. You can withdraw the approval from PaySpace whenever you want, and Fintura loses access at that point without anyone changing settings on our side.

Only what an EMP201 needs: the period's PAYE, UIF and SDL amounts, the ETI block with brought forward, utilised and carried forward, and the PAYE and UIF reference numbers where Fintura is not already holding them. Any ETI compliance warning PaySpace raises travels with the import. Employees, payslips and leave are never read, and the connection is read-only, so nothing Fintura does can alter a payroll run.

Yes. Authorise each account and label it, then map every client to the payroll company its figures actually sit in. An import follows that mapping, so a firm splitting clients across several payroll accounts does not have to keep track of which is which at the point of filing.

No, and that is deliberate. Nothing is scheduled and nothing streams in. Once the payroll run is closed you open the client's EMP201 for that period and ask for the import, which keeps the person filing in control of which figures land on which return. Earlier periods are brought in the same way, one at a time.

Interactive demo