Great! Thanks! I have been told it wasn't :-)

When you request a signature from the web client, it embeds information in the envelope about the source document. When the receiver component gets a signed document back from DocuSign, it will look for that identifying information, and if it's there it will update the source document. But the receiver was designed to also be able to handle documents that did not originate in the repository. The configuration page lets you indicate how properties from the DocuSign envelope should be mapped to field data, and where in the repository the document should be saved.

Thanks Brian, I have been reviewing the documentation you shared, and we'll go that way. Your last comment clarifies our use case!