Depending on where you found this statement, there may be specific reasons why it is true in the context.
However, the usual reason for the '+k' is simply that it takes O(k) extra operations to insert each of the matches you found in the result list returned to the user. This is not necessarily the case when an inverted file is used instead of a suffix tree, because then the inverted list (aka postings list) found in the index is already the final results list (at least if we assume that (a) the query consists of a single token only, and (b) the inverted list is stored uncompressed).
But a suffix tree usually (unless it is specially prepared) does not contain such match lists. Hence during matching you identify a path through the tree, ending at some internal node. From there, you must follow all paths in the subtree of that internal node to identify the leaf nodes that tell you the actual positions of the matches (one leaf node per match), and insert the match positions in the results list that you return to the user. This final step is what takes O(k) time.
Also note that following all paths in the subtree of the internal node you found can take significant extra time, in which the total complexity is even higher than O(n+k). That depends on whether or not there are any direct pointers from internal nodes to the leaf nodes in their subtrees.