Receipts in expense reports

When Dolibarr produces an expense report PDF, the module appends the receipts after it, in a fixed order:

1. the files attached to the lines, in line order. A file attached to several lines appears only once;
2. as an option, enabled by default, the other files in the “Linked files” tab, except documents produced by Dolibarr.

Photos and PDFs

An image wider than it is tall is placed on a landscape page. In the PDF, photos are re-saved as JPEG and limited to 2,400 pixels on the longest side. The uploaded file itself is not changed.

Other formats — iPhone HEIC photos, Word documents… — are not converted: they are listed as not included. Straightening and support for PNG and GIF require the PHP GD extension; without it, only JPEGs are included, as they are.

The marker on each page

At the top of each receipt page, one line says where it comes from (here in French):

Justificatif — ER2610-0001 — ligne 1 · 07/10/2026 · 68,00 € — billet_train.pdf

Report reference, line number, date and amount including tax of the line, file name. In English, the line reads “Receipt — … — line 1 …”. A file not attached to any line carries the mention “not attached to a line”. The marker can be switched off in the setup page.

A receipt never blocks the expense report

Each file is checked before it is read: empty file, maximum size, format, complete PDF, non-encrypted PDF. A rejected file does not prevent the report from being produced. It is listed on a last page, “Receipts not included in this document”, with the reason, and a message reports it on screen.

On Dolibarr 19 to 23, the core PDF library can stop PHP on some damaged PDFs: the user gets a blank page. The module protects against this. The faulty file is set aside, and a page explains what happened and leads back to the expense report. On the next generation, the PDF is produced normally and the file appears in it as not included.

The module does not check that each line has a receipt: a line with no attached file is not reported.

The screenshot shows the result: four pages of the same PDF, side by side.

The first one is expense report ER2610-0001 as Dolibarr produces it: three lines — a train from Strasbourg to Paris at 68.00, one hotel night at 102.65, a client lunch at 40.50 — for a total of 211.15 including tax.

Then come the three receipts, in line order: the train ticket and the hotel invoice, two PDFs, then the photo of the restaurant receipt. Each page carries its marker, whose date and amount match the report line. There is no “Receipts not included in this document” page: all three files were included.

SetupModules/ApplicationsReceipts in expense reports:

Below the settings, the list of receipts set aside after a read error. A file set aside is recognised by its content: it stays left out until the list has been cleared with the “Clear the list” button.

Settings are specific to each entity in multi-company.

• The original PDF is never damaged. Merging is written to a separate file; the PDF produced by Dolibarr is only replaced if it succeeds.
• Check before reading each receipt: size, format, complete PDF, non-encrypted PDF. An image of more than 60 million pixels is left out.
• Files confined to the expense report’s folder: a file attached to a line is only read if it really sits in that folder.
• No new permission. Receipts are appended for anyone who can already generate the expense report PDF.
• Setup page restricted to administrators, and its two actions — save, clear the list — require the session’s anti-CSRF token.

• The dolixjustif folder, in readable source, under GPL v3 or later: descriptor, two classes (the end-of-PDF-generation hook and the merge), setup page, icons.
• The translations present in langs/: French (fr_FR), English (en_US) and German (de_DE).
• A README.md and a ChangeLog.md.

The module needs the Expense Reports module. The descriptor requires Dolibarr 19.0 and PHP 7.4 minimum; the test scenarios were run on 19.0.4, 20.0.4, 21, 22, 23.0.4 and 24.0.1.

• No table created. The module contains no sql/ directory.
• It changes neither the lines, nor the amounts, nor the uploaded files. It reads the list of files of the expense report; the only write is the produced PDF, completed.
• On activation, three settings are stored in Dolibarr’s constants.
• If a damaged PDF is set aside, a record is kept in a small file, documents/dolixjustif/quarantaine_<entity>.json, not in the database.
• No outgoing connection: nothing is sent anywhere.
• On deactivation, PDFs generated afterwards are Dolibarr’s own again. PDFs already generated keep their receipts until they are generated again. The three settings and the list of files set aside remain; you can delete them yourself.