Navigating the 230-Series Tech & Software Codes

Intro

Every modern South African business runs on a global technology stack. Whether you are outsourcing development to a tech agency in Eastern Europe, migrating your infrastructure to Amazon Web Services (AWS), or simply paying for your team’s monthly Microsoft 365 subscriptions, that capital is crossing borders.

Under the South African Reserve Bank (SARB) framework, these payments fall into the 230-series of Balance of Payments (BoP) codes. Unlike standard physical imports, the regulatory distinction here hinges on two critical factors: how the tech is delivered (physical media vs. electronic) and how it is billed (ongoing subscription vs. outright purchase).

To keep your tech stack compliant and your payments flowing, here is a breakdown of the four most vital tech-related BoP codes and the documents you need to support them.

Code 231: Computer-Related Services (Maintenance, Repair, and Consultancy)

The Scenario: This code is entirely about paying for human expertise and time, rather than a software product itself. You utilise this code when paying a foreign entity for outsourced IT support, offshore software development, database administration, network repairs, or technical consulting.

Required Supporting Documents:

• Commercial Invoice: Must clearly detail the hours worked, the specific nature of the IT services rendered, and the billing period.
• Service Level Agreement (SLA) or Contract: For high-value invoices or ongoing monthly retainers, your Authorised Dealer will almost certainly request a copy of the underlying contract to verify the commercial reality of the service fees.

Code 235: Electronic Software with a Periodic License (SaaS & Cloud)

The Scenario: Meet the undisputed heavyweight champion of the modern digital economy. You use this code for non-customised software that is downloaded or accessed online, and paid for on a recurring basis (monthly or annually). This covers almost all modern Software-as-a-Service (SaaS) and cloud computing bills: AWS, Google Workspace, Adobe Creative Cloud, Salesforce, and Zoom.

Required Supporting Documents:

• Commercial Invoice / Billing Statement: Since many of these providers operate on automated credit card billing or digital invoicing, you must provide the official digital receipt or monthly billing statement from the platform showing the subscription period and amount.

Code 233: Physical Media Software with a Periodic License

The Scenario: This is a legacy code that is increasingly rare, but still vital for certain specialised industries. You use this when the software is physically shipped to you on a hard drive, USB drive, or disc, but you do not own it outright—you pay a recurring annual or monthly fee to maintain the license to use it.

Required Supporting Documents:

• Commercial Invoice: Detailing the licensing period and the physical delivery.
• Customs Documentation (SAD 500): Because the software arrived on a physical medium that crossed the South African border, customs documentation proving the physical import is often required to tie the physical entry to the capital exit.
• Licensing Agreement: Proving the recurring nature of the fee.

Code 234: Physical Media Software with a Perpetual License

The Scenario: Similar to 233, the software is delivered on a physical medium (USB, server rack, disc). However, the key difference is the license type: perpetual. You are paying a once-off fee to buy the software outright. You own that specific version forever, with no recurring monthly licensing fees required to keep it active.

Required Supporting Documents:

• Commercial Invoice: Clearly stating it is a once-off, perpetual purchase.
• Customs Documentation (SAD 500): Just like Code 233, the physical medium requires customs clearance, and your Authorised Dealer will need the Movement Reference Number (MRN) from the SAD 500 to acquit the payment.

The Hidden Trap: Withholding Tax on Royalties

When dealing with the 230-series (especially software licenses under 233, 234, and 235), businesses often face a nasty surprise from SARS. South African tax law frequently categorises cross-border payments for the use of software rights as “Royalties.” Depending on the Double Taxation Agreement (DTA) with the supplier’s country, you may be legally required to withhold a percentage of the payment (often up to 15%) and pay it directly to SARS. Always consult your tax practitioner before executing large offshore software license payments.

Future-Proofing Your Tech Payments

When executing these payments through a digital portal, ensuring that your accounts payable team understands the difference between a service (231) and a subscription (235) eliminates 90% of FinSurv compliance delays. Ensure your payment platform allows for the seamless upload of both the invoice and the underlying SLA, keeping your tech infrastructure online and fully compliant.

SME Forex is specifically designed to help businesses make overseas payments with ease at the best possible exchange rate. With direct integration to Investec Bank, your cross-border payments are no longer an administration nightmare.