Payment Profile Codes in South Africa | Interpretation Guide
Interpret payment profile codes used in South African bureau reports, identify repayment patterns, and turn account history into actionable risk signals.
Payment profile strings are the month-by-month record of how a consumer has paid each credit account, represented as numeric codes on South African credit bureau reports. For debt counsellors, credit brokers, and credit providers, they are one of the most informative parts of the report—yet in PDF form they are often underused because they appear as dense strings of digits without context or structure. Understanding what these codes mean, how to read them, and what patterns to look for is essential for thorough affordability and risk assessment. This guide explains the standard coding convention used in South Africa, how to interpret payment profile strings across bureaux, why they matter for credit assessment and NCA compliance, and how structuring this data turns it into actionable risk signals instead of static text on a page.
What Payment Profile Strings Are
A payment profile string is a sequence of characters—usually digits—where each character represents the payment status of an account in a given month. One position corresponds to one month; the full string therefore gives a chronological view of whether the consumer was up to date, one month in arrears, two months in arrears, or in some other status (e.g. write-off, legal action, debt review) in each of those months. Bureaux receive payment data from credit providers and display it in this compact form so that assessors can see behaviour over time without reading lengthy narrative. For credit professionals, the string answers a critical question: not only “what is the balance today?” but “how has this account been paid over the last 24 or 36 months?” That behavioural view is central to credit scoring, to spotting early signs of over-indebtedness, and to understanding whether a consumer is improving, stable, or deteriorating before formal adverse listings appear.
The Standard Coding Convention in South Africa
South African credit bureaux generally follow a common convention for payment profile codes, though the exact symbols and labels can vary slightly by bureau and product. The core logic is:
Numeric arrears: 0 = up to date (current), 1 = one month in arrears, 2 = two months in arrears, 3 = three months, and so on. Higher numbers indicate more severe delinquency for that month.
Special codes: Beyond simple arrears counts, bureaux use additional codes for write-offs, legal action, debt review, settlement, and similar statuses. For example, an account that has been written off may be shown with a distinct code (e.g. “W” or a specific digit); accounts under legal action or in debt review may have their own markers. These codes are important because they indicate not just late payment but a formal change in the account status—and they often precede or accompany adverse listings on the report.
Practitioners should confirm the legend for each bureau report they use. Experian, TransUnion, and Datanamix each publish or provide key-to-code explanations; using the wrong legend can lead to misreading. Once the convention is known, the same logic applies across accounts and clients—which is why standardising the interpretation in policy and in systems reduces errors when many reports are processed.
How to Read a Payment Profile String
Reading a payment profile string requires knowing two things: the direction of time (which end is oldest, which is most recent) and the length of the string.
Chronology: Depending on the bureau and the report layout, the string may read left-to-right (oldest month on the left, most recent on the right) or right-to-left (oldest on the right, most recent on the left). Misreading the direction reverses the story: what looks like recent improvement may be old history, or vice versa. Always check the bureau’s layout or legend before drawing conclusions about “recent” behaviour.
Length: Strings typically represent 24 or 36 months of history, sometimes 12. The length may be fixed (e.g. always 24 characters) or variable; shorter strings may mean the account is newer or that the bureau only received data for a limited period. Knowing the length helps you interpret how much history you are actually seeing and whether a run of zeros at one end means “current for the last X months” or “no data for that period.”
Once direction and length are clear, you can walk through the string month by month and note where arrears appear, how long they last, and whether there are recovery phases (e.g. 2, 2, 1, 0, 0) or deterioration (e.g. 0, 0, 1, 2, 3).
What Patterns to Look For
Payment profile strings reveal behaviour patterns that a single “current” or “in arrears” flag cannot.
Consecutive arrears (deteriorating behaviour): A run of increasing numbers—e.g. 0, 1, 2, 2, 3—shows the account slipping from current into deeper arrears. This is a strong signal of stress and often an early warning before formal default or over-indebtedness is declared. Multiple accounts with similar deterioration across a consumer’s file compound the concern.
Recovery patterns (improvement): A sequence such as 3, 2, 1, 0, 0 shows the consumer bringing the account back to current. That can support a more favourable view of recent behaviour and willingness to correct, even if the account had been in difficulty earlier.
Seasonal patterns: Some consumers show repeated arrears in certain months (e.g. after December or school fees) and then recovery. Recognising seasonality helps avoid over-penalising a single bad month when the overall trend is stable.
Sudden changes: A long run of zeros followed by a sudden 2 or 3 may indicate a life event, loss of income, or over-commitment. It warrants attention when assessing new credit or reviewing existing exposure.
Identifying these patterns manually across many accounts and clients is time-consuming. When the same logic is encoded in rules and applied to structured data, flags can be raised automatically—e.g. “any account with three or more consecutive months in arrears in the last 12 months”—so that assessors focus on exceptions rather than re-reading every string.
How Different Bureaux Present Payment Profiles
Experian, TransUnion, and Datanamix all provide payment history, but the format and presentation differ.
Experian reports typically show payment profile strings in the trade-line section for each account, with a key or legend elsewhere on the report. The convention (0 = current, 1 = 1 month, etc.) is consistent with the industry norm, but the exact layout and any special codes should be confirmed from the report or Experian’s documentation.
TransUnion uses a similar numeric convention for payment history on its South African reports. The Empirica score and other risk indicators are partly driven by this payment data; understanding the underlying strings helps practitioners see why a score may be high or low and apply their own rules on top.
Datanamix (including Compuscan) also presents payment profiles in a comparable way. Because Datanamix is often used alongside affordability-focused workflows, payment behaviour on each trade line is especially relevant for debt counsellors and lenders who need to prioritise accounts or explain risk to clients.
The underlying data concept is the same across bureaux; the difference is in layout, labelling, and any bureau-specific codes. For firms that pull from multiple bureaux, normalising payment profile data into a common structure allows the same pattern rules and flags to be applied regardless of which bureau supplied the report.
Why Payment Profiles Matter for Credit Assessment
Payment profiles matter for three main reasons.
They reveal behaviour beyond the current balance. A consumer may be “current” today but have a history of repeated late payments; another may have been in arrears recently but has cleared and stayed current for several months. The profile string captures that history and supports a more nuanced view than a single status field.
They predict future risk. Persistent or worsening payment behaviour is associated with higher default risk; clean or improving profiles support lower risk. Bureaux use this data in credit scoring models, and credit professionals can use it in their own policies—e.g. declining or conditioning credit when recent profiles show a defined pattern of deterioration.
They support NCA compliance. Under the NCA, credit providers must take reasonable steps to assess the consumer’s debt repayment history and financial means before granting credit. Payment profiles are direct evidence of repayment history. Using them in a consistent, documented way helps demonstrate that the assessment was thorough and that the decision was based on available data—reducing reckless lending and over-indebtedness risk.
The Problem with Reading Payment Profiles from PDFs
In a PDF credit report, payment profile strings appear as strings of numbers (and sometimes letters) next to or under each account. There is no semantic structure: the system does not “know” that position 7 is “March 2024” or that the value “2” means two months in arrears. The assessor must read each string, recall the convention, and mentally apply pattern rules. Across dozens of accounts and hundreds of reports, that approach does not scale. It is hard to answer questions such as “which of this client’s accounts have had more than two consecutive months in arrears in the last year?” or “how many of our recent applications showed a deteriorating profile on any account?” without opening each PDF and checking manually. Consistency suffers when different analysts interpret the same string differently or when policy rules (“flag if 3+ consecutive arrears”) are applied only when someone remembers to look. There is no built-in way to filter, query, or compare payment profiles across accounts or across clients—so the data remains locked in the document.
How Structured Data Turns Payment Profiles Into Actionable Risk Signals
When payment profile data is extracted from bureau reports and stored in a structured form—each position parsed, each code mapped to a standard meaning, and each account linked to the consumer and the report—it becomes possible to apply rules consistently and at scale. Automated flagging can surface accounts (or consumers) that meet defined criteria: for example, any account with three or more consecutive months in arrears in the trailing 12 months, or any consumer with two or more accounts showing a deteriorating pattern. Trend analysis can compare the same account across report dates to see whether behaviour is improving or worsening. Consistent rules can be applied across all cases, so that the same policy is enforced for every application or debt review file. And because the logic is explicit and the data is traceable, the assessment is auditable: an auditor or the NCR can see which data was used, which rules were applied, and how the outcome was reached. That is the practical value of structuring payment profiles—not a single “score” replacement, but the same bureau data turned into comparable, rule-driven, decision-ready signals that support faster, more consistent, and defensible credit assessment.
Payment profile strings and codes are central to understanding how South African consumers have paid their credit accounts over time. Interpreting them correctly—using the right convention, direction, and length—and looking for deterioration, recovery, and other patterns helps credit professionals assess risk and meet NCA expectations. When that data remains in PDFs, it is underused; when it is structured, it can drive automated flagging, trend analysis, and consistent rules across all cases. Get in touch to turn payment profiles into actionable risk signals and see how structured bureau data supports consistent, auditable assessments.