Financial systems. Software testing. The foundations of reliable engineering.
Learnership → Software Development Intern → IT Consultant
C#MSSQLQAPayment gatewaysHTML
Conceptual reconstruction / architecture study
Reconstructed to explain the work. Not an original system screenshot.
Interactive concept / invented demo records
Reconciliation workbench
Explore the distinction between matched transactions and records requiring investigation.
CONCEPT INTERFACE NO PRODUCTION DATA
3 demo records
Conceptual reconstruction with invented sample data; not an original employer interface.
Demo reference
Gateway
Ledger
State
SAMPLE-001
R 250.00
R 250.00
Matched
SAMPLE-002
R 480.00
R 450.00
Investigate
SAMPLE-003
R 120.00
R 120.00
Matched
Matching values is one useful check. Missing records, timing differences and duplicates also require attention; this simplified example does not implement a payment system.
CASE STUDY / 01
Payment gateway & reconciliation
Worked on Siyakhokha payment gateway support, daily, monthly and yearly reconciliations, and financial reports from MSSQL.
My contribution
Compared transaction and accounting data, supported user queries, and helped identify missing data for financial year-end audit reporting.
Methods & tools
C# • MSSQL • Excel
Conceptual reconstruction
Payment gateway & reconciliation
An illustrative transaction lifecycle: payment records enter a reconciliation process, matched records progress to reporting, and exceptions require investigation. This does not reproduce a client database or payment integration.
Conceptual reconstruction / architecture study
Reconstructed to explain the work. Not an original system screenshot.
This model uses public career descriptions. It contains no proprietary screenshots, customer records or credentials.
CASE STUDY / 02
Internal helpdesk development
Led development of an internal helpdesk across the front end, back end, database design and documentation.
My contribution
Connected application development with technical support needs; also contributed to Strategy, Bio Time and Credit Control interfaces.
Methods & tools
Application development • Database design • Documentation
Conceptual reconstruction
Internal helpdesk development
A conceptual request lifecycle: a user submits an issue, a service layer records it, a support queue assigns ownership, and resolution is documented. No real customer tickets are shown.
Conceptual reconstruction / architecture study
Reconstructed to explain the work. Not an original system screenshot.
This model uses public career descriptions. It contains no proprietary screenshots, customer records or credentials.
CASE STUDY / 03
Testing & technical communication
Started with black-box testing, front-end documentation and comparing datasets in Excel; learned white-box testing methodologies.
My contribution
Created technical user manuals and process walkthroughs, and tested a WhatsApp chatbot during the development internship.
Methods & tools
QA • HTML • User documentation
Conceptual reconstruction
Testing & technical communication
A reconstructed QA workflow: define expected behaviour, exercise inputs, document actual behaviour, raise defects, and retest fixes. It describes practice, not a proprietary test suite.
Conceptual reconstruction / architecture study
Reconstructed to explain the work. Not an original system screenshot.
This model uses public career descriptions. It contains no proprietary screenshots, customer records or credentials.
Check the details
Reconciliation and QA built a habit of inspecting the evidence.
Explain the system
Manuals and walkthroughs made technical workflows usable.
Own the full loop
Helpdesk work connected interface, back end and database.
Employment history and contributions verified against the supplied CV. System models are illustrative reconstructions, not original proprietary screenshots. Each page is an independent portfolio interpretation; its palette is not presented as an official employer colour specification.