Short answer
Yes, it can, and that’s called a hallucination. The model writes an answer that sounds believable because it’s built to produce convincing text, not to admit it’s missing a fact. No system is right every time, so what matters is how it fails. "I don’t know, let me get a person" is acceptable; inventing a billing figure is not.
In detail
Why it happens
A language model doesn’t distinguish between what it knows and what it’s filling in. Ask it about a feature that doesn’t exist, with nothing written about it, and the most likely output is a plausible description of that feature. It isn’t lying. It’s doing what it always does, writing the most likely text.
What reduces it
Answers that come from your sources instead of the model’s memory, instructions on what to do when a fact is missing, and documentation of what your product doesn’t do. Almost nobody writes that last part, and it prevents the most hallucinations. An article that says "XML export isn’t available" closes that door.
The test before you buy
Ask it about a feature your product doesn’t have and see what it says. A well-built system says it doesn’t exist or that it will check with someone. A badly built one describes the feature in detail, and it will do the same to a customer.
What isn’t enough
Asking in the instructions and stopping there. "Don’t make up prices" is a request, and a model can ignore it in a strange enough conversation. The limit has to live in the system. The fact comes from a lookup in your systems, or it doesn’t come at all.