Government integrations: SARS, CIPC and LOGIS procurement integration
Government integrations connect your systems to the state platforms you report to: SARS and CIPC in South Africa and, for national and provincial departments, LOGIS procurement integration around National Treasury's transversal systems. Arke Technologies, in Johannesburg, builds these interfaces and their controls within each authority's permitted channels.
What government integration covers
Organisations deal with state systems in two directions: they submit returns and filings, and they check what the state holds, such as a supplier's registration or tax status. Integration replaces re-keying between your systems and those platforms, and records what was submitted, when and by whom. It is part of our systems integration service.
Each authority decides which channels are open, to whom and in what format, and changes them over time. So every project starts by establishing the channel your organisation may use and the current specification. Where no permitted machine interface exists, we automate the preparation, checks and records around a filing a person still submits.
LOGIS procurement integration for national and provincial departments
LOGIS, the Logistical Information System, is one of National Treasury's transversal systems. Many national and provincial departments use it for procurement and provisioning: requisitions, orders, stores and asset records. Payments typically run through BAS, the Basic Accounting System, and personnel through PERSAL.
LOGIS procurement integration is therefore not an open API project. National Treasury manages the transversal systems and decides which interfaces exist and who may use them, so most of the work happens around LOGIS rather than inside it:
- Reconciliation. Matching LOGIS orders to supplier invoices, goods-received records and BAS payments, with exception reports for unmatched or late items.
- Payment monitoring. Tracking invoices against the Treasury Regulations' 30-day payment rule, so accounting officers see what is at risk before it becomes an audit finding.
- Supplier and contract registers. Keeping contract, commitment and supplier records consistent with each supplier's record on the Central Supplier Database, where suppliers to government must be registered; see our CSD registration guide.
- Reporting. Dashboards and audit-ready packs built from the extracts and reports your department is authorised to take.
Where your department runs its own systems beside LOGIS, such as a requisition portal, we connect them to the extracts or interfaces you are permitted to use. For how departments buy technology, see SITA and government IT and PFMA, MFMA and ICT procurement.
Risks, and how we prevent them
Shared logins. Named users with their own rights on each portal, never a shared password, so every submission is traceable to a person.- Unpermitted automation. We do not script a government portal in ways its terms prohibit; we use the channels each authority provides.
- Format changes near deadlines. Specifications are tracked, and changes are tested before filing season.
- Wrong entity or period. Validation of registration and tax numbers, and a human approval before anything is filed.
- Confidentiality. Taxpayer information is confidential under the Tax Administration Act, and personal information is protected under POPIA, so access is limited, encrypted and logged, and credentials sit in a secrets store, never in code.
Governance, compliance, procurement and continuity
- Governance and reporting. A named integration lead, change control, a filing log, and an integration health report in each monthly service review.
- Compliance. Integrations for departments and public entities keep the records PFMA audits test, and for municipalities the records MFMA audits test; boards get King IV Principle 12 reporting on the technology risks involved. Controls are aligned with ISO/IEC 27001, and we act as an operator under POPIA where we process personal information for you. For the wider public-sector picture, see IT services for government and the public sector.
- Procurement. Level 1 B-BBEE contributor (sworn affidavit available on request), giving 135% procurement recognition. Company documents, CSD supplier number and tax compliance status are available on request, and we complete SBD forms when a bid requires them. Departments and entities buy through a request for quotation, a proposal and purchase order, or a tender response; see procurement and compliance. We do not hold SITA accreditation or a transversal contract; SITA and government IT explains when departments may buy IT outside SITA.
- Continuity. Credentials and portal rights stay registered to your organisation. You own your data and documentation, and at handover or exit we transfer the mappings and runbooks.