[GH-ISSUE #161] [Feature] XML documents #125

New issue

Closed

opened 2026-02-25 21:31:15 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 21:31:15 +03:00

Owner

Originally created by @francescocarzaniga on GitHub (Oct 11, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/161

Originally assigned to: @ciur on GitHub.

XML is sometimes used for invoices (e.g. Italy) or other static documents. It would be extremely useful (and a major selling point in places where such documents are mandatory) to be able to add them to Papermerge and view them in the Web UI using a stylesheet. Each document could be associated to a stylesheet either directly or automated per-folder or with a tag. Moreover no OCR is needed.
A user story could be setting up an autoforward for XML invoices to the Papermerge email, which would then process it, tag it, and associate a stylesheet for viewing, making the whole invoice intake incredibly smooth.

Originally created by @francescocarzaniga on GitHub (Oct 11, 2020). Original GitHub issue: https://github.com/ciur/papermerge/issues/161 Originally assigned to: @ciur on GitHub. XML is sometimes used for invoices (e.g. Italy) or other static documents. It would be extremely useful (and a major selling point in places where such documents are mandatory) to be able to add them to Papermerge and view them in the Web UI using a stylesheet. Each document could be associated to a stylesheet either directly or automated per-folder or with a tag. Moreover no OCR is needed. A user story could be setting up an autoforward for XML invoices to the Papermerge email, which would then process it, tag it, and associate a stylesheet for viewing, making the whole invoice intake incredibly smooth.

kerem

2026-02-25 21:31:15 +03:00

closed this issue
added the
enhancement

feature request
labels

kerem commented

2026-02-25 21:31:16 +03:00

Author

Owner

@ciur commented on GitHub (Oct 12, 2020):

@francescocarzaniga, Papermerge is limited only for scanned documents. XML invoices (well, XML, TXT, office documents etc) are out of scope.
Papermerge is a niche DMS. It specializes for scanned documents - that's the whole point :)

@ciur commented on GitHub (Oct 12, 2020): @francescocarzaniga, Papermerge is limited only for scanned documents. XML invoices (well, XML, TXT, office documents etc) are out of scope. Papermerge is a niche DMS. It specializes for scanned documents - that's the whole point :)

kerem commented

2026-02-25 21:31:16 +03:00

Author

Owner

@francescocarzaniga commented on GitHub (Oct 12, 2020):

@ciur It would be nice to have documentation on how to create plugins (you mention them in the README so I guess they are possible). This way people might choose to extend Papermerge's scope without interfering with the main concept.

@francescocarzaniga commented on GitHub (Oct 12, 2020): @ciur It would be nice to have documentation on how to create plugins (you mention them in the README so I guess they are possible). This way people might choose to extend Papermerge's scope without interfering with the main concept.

kerem commented

2026-02-25 21:31:16 +03:00

Author

Owner

@ciur commented on GitHub (Oct 12, 2020):

@francescocarzaniga, my plans are to make Papermerge "plugin" oriented (plugin=apps).

This way people might choose to extend Papermerge's scope without interfering with the main concept.

I absolutely agree!

@ciur commented on GitHub (Oct 12, 2020): @francescocarzaniga, my plans are to make Papermerge "plugin" oriented (plugin=apps). > This way people might choose to extend Papermerge's scope without interfering with the main concept. I absolutely agree!