What's on the Receipt PDF
Understand every section of the receipt MonuDesk generates when you log a payment, including the per-payment billing snapshot and totals.
Written By Dennis Rodin
Last updated 17 days ago
MonuDesk automatically generates a receipt each time you log a payment. Find it in the order's Files section under the Financial Document category, or generate one anytime from Document Generation → Generate Receipt.
Empty fields: If you skipped optional fields when creating the order (cemetery, color, finish, size), the PDF renders Not specified in those positions instead of leaving blank space. Fill in the missing fields from Edit Order and regenerate the PDF to update it.
Header information
The top left shows:
Order Number, Issue Date (the date this payment was received, not the date the order was created),
Payment Terms (the deposit split you selected, for example "30% down, 70% before installation"),
Sales Rep (the team member who created the order),
Timeframe (the scheduling selection from Step 2, for example "June - August"),
Order Type (the monument type, such as "Upright" or "Bevel Marker"),
Cemetery, Section, and Lot / Space added from Step 2 of the "+ New quote" window.
The top right shows:
From with your company name, address, and phone number (pulled from Settings → Company Profile).
Bill To with the billing name, address, phone, and email. See "Why this receipt's billing can differ" below for how this is filled in.
Why this receipt's billing can differ
Each receipt carries a per-payment billing snapshot. The Bill To block prefers the billing details captured on this specific payment (for example, what the customer typed when paying through the Customer Portal) and only falls back to the live client record when no snapshot exists.
That means if a customer edits their billing name or address while making one portal payment, the change appears on that one receipt only. It never updates the client record or any other payment's receipt. Each receipt reflects the billing details as they were at the moment that payment was made.
Item lines
A table showing each component of the order, with the same columns as the invoice:
Die shows the granite color, dimensions, finish, and quantity. For orders with multiple stones, finishes are labeled per stone (for example "Finishes: Stone A, P5 Polish").
Base shows the same details for the base.
Vase, Porcelain, and Etching show the selected options. Custom accessories display their description.
Each line shows the Quantity and Amount. When a finish isn't a recognizable short code (P1–P5 / S1–S5), it shows as Custom Finish; empty values show as Not specified.
Totals
Below the items, the receipt shows the totals for this specific payment:
Total Amount: the full order total.
Payment Received: the amount of the payment you just logged.
Total Received: everything paid on the order so far, across all payments.
Balance Due (bold): what's still owed after this payment.
This is the key difference from the invoice: the receipt is tied to one payment. Instead of a deposit-due schedule, it shows how much that single payment covered and what remains on the order.
Order Details
A structured box (titled Order Details) summarizes the monument's finishes and inscription under a Lettering sub-header. For each decedent it shows a Decedent N header with these fields:
Given Names
Surname (with " (both sides)" appended when the surname appears on both sides)
Dates (shown as birth – death)
Additional Text
Facing
When there are two or more decedents, the box lays them out in two columns. Finishes for each stone are listed here as well. Sizes already shown in the item table above are not repeated in this box.
Receipt notes
If you added a note when logging the payment (the optional Receipt Note field in the Record Payment modal), it appears here. This is specific to the individual payment, not the order's general notes.
Page footer
Every page ends with your company name in bold above Powered by MonuDesk, centered at the bottom, with page numbers in the bottom-right corner (for example 1/2, 2/2).
Related articles: