Format spec
Parking ticket receipt template
Entry and exit stamps, a duration, the rate row that was applied, and the code the exit gate scans.
This is a generic industry format — the printing convention, not any company’s trade dress. You supply your own business identity; Get Receipt supplies the grid it prints on.
Physical spec
- Paper
- 58 mm thermal roll
- Roll or sheet width
- 57.5 mm
- Printable width
- 48 mm
- Horizontal dots
- 384
- Head density
- 203 dpi (8 dots/mm)
- Characters per line
- 32 (ESC/POS Font A)
The character grid is the printer’s, not an approximation: at 203 dpi a Font A cell is 12 × 24 dots, so 384 dots of printable width is exactly 32 characters. Anything you render has to land on integer dot multiples or the edges blur.
Ordered field list
Top of the document to the bottom. This is the order a reader expects and the order a scanner, a bookkeeper or a returns desk looks for.
- 1.Facility name and address
- 2.Lot, level or space number
- 3.Entry timestamp
- 4.Exit timestamp
- 5.Duration
- 6.Rate row applied
- 7.Subtotal
- 8.Parking or occupancy tax
- 9.Total
- 10.Tender
- 11.Plate
- 12.Display or retain instruction
- 13.Gate code
Alignment
Label-and-value pairs, values right-flush.
Tax convention
A separately named local parking or occupancy tax at its own rate, not a general sales-tax line.
Tender
Card or cash at a pay station or the exit gate.
Machine-readable code
Code 128 or a QR the gate scans. Card-sized tickets often use Aztec, which stays readable at small sizes.
How to recognise it
- Entry and exit timestamp pair
- Duration line
- Rate row shown explicitly
- DISPLAY ON DASHBOARD or RETAIN FOR EXIT instruction
Get Receipt renders this as Parking garage receipt
Exit-machine slip: entry and exit stamps, rate band, and the exit barcode the driver scans on the way out. Every total is recomputed by the engine from the line items, so the printed lines always sum to the printed total — the one thing generated receipts most often get wrong.