Supported Document Types
Six kinds of paper come out of REDA Financials' PDF engine — five transaction documents plus the statement of account. Each carries your entity's branding and a layout tuned to its purpose. Here's the catalogue.
Access you'll need. Anyone who can open a posted record can generate its PDF. Configuring the layouts — PDF Templates — requires the Accounting Admin v2 or Accounting Controller v2 permission set; the Accounts Payable v2, Accounts Receivable v2, and Read Only v2 sets can view templates but not change them.
| Source | Printed title | Layout notes |
|---|---|---|
| Sales Invoice | INVOICE | Line table (Description, Qty, Unit Price, Amount — plus Discount and Tax columns where relevant), totals block, and a Tax Breakdown table summarizing each tax applied — the section your customer's accountant looks for. |
| Credit Memo | CREDIT MEMO | Same anatomy as the invoice, unmistakably titled — and it can carry its own template (a different tagline, e.g.), separate from invoices. |
| Cash Receipt | RECEIPT | Compact: parties, date, amount, payment method — proof of payment, not a bill. |
| Cash Disbursement | PAYMENT VOUCHER | Includes a Remittance Detail table — one row per invoice the payment settles (invoice #, date, amount, applied, discount) — so your vendor's AR team can match the money without emailing you. |
| Purchase Order | PURCHASE ORDER | Addressed to the Vendor; shows quantities and prices with estimated totals — a commitment document, not a tax document, so no tax breakdown. |
| Account Ledger | Statement of Account | Generated from the Account Ledger screen's Export PDF: opening balance, every charge and payment, running to a closing balance, honoring your current entity/date filters. Print-oriented — it opens for printing/saving rather than attaching to a record. |
A closer look at each layout
Invoices and credit memos carry the fullest anatomy. Take Meridian's MSI001021 — NovaTech's $9,800 invoice: under the letterhead and the big INVOICE title sit the Bill To block, the line table (#, Description, Qty, Unit Price, Amount — with Discount and Tax columns when they apply), then the totals: Subtotal, any Discount, Tax, Total. Beneath that, the Tax Breakdown table lists each tax by name with its taxable amount, rate, and tax amount, adding up to a Total Tax row — the section a customer's accountant reads first. A Ship To card appears only when the customer account actually has a shipping address, and a Notes section prints whatever is in the document's Description field. A credit memo is the same anatomy under a CREDIT MEMO title, dressed by its own Credit-Memo-type template.
Receipts and payment vouchers have no line table — a payment is one amount, not a list of items — so their body is the parties, the amount, and the detail rows your administrator configures (payment method, check number, bank account…). The payment voucher adds the Remittance Detail table: one row per invoice the payment settles — Invoice #, Invoice Date, Invoice Amount, Applied, Discount — in the order the applications were made (earliest application date first), so the vendor's AR team can match the money line by line.
The purchase order swaps Bill To for a Vendor heading (the paper goes to the vendor), drops the tax column from its lines, and totals as Subtotal, Tax, and Total — the tax and total being estimates until the vendor's real invoice arrives.
The statement of account reads like a bank statement for one customer: the account card, the Period, a "Filtered By" line echoing your ledger filters, four position figures — Total Outstanding, Unapplied Payments, Unapplied Memos, Net Outstanding — then an Opening Balance, every transaction with its Charges and Payments columns, and the Closing Balance. It also prints a small generated-on timestamp, so the reader knows exactly when this snapshot was taken.
What they all share
- Entity letterhead — logo, company name, address, tax identifier — from entity branding.
- Bill To details, including the customer's tax registration where configured — essential in GST/VAT jurisdictions.
- Template-driven styling — colors, fonts, page size, footer, terms — from the resolved template, with a clean built-in default when none exists.
- Extra detail rows your administrator adds per document type — see Admin-Configurable PDF Columns.
Where to go next
- Generating PDFs — the three generation paths.
- PDF Template Configuration — one template per document type, per entity.
- Sales Invoice PDF — the invoice flow end-to-end.
Frequently asked questions
No — journals are internal bookkeeping, not customer-facing paper. The six types above are the documents that leave your organization.
By design — a receipt proves an amount arrived on a date by a method. If you want more (bank account, applied invoices), your administrator can add fields to the receipt's PDF detail rows in minutes: Admin-Configurable PDF Columns.
The statement renders for printing/saving in your browser rather than attaching to the account record — statements are point-in-time answers, regenerated fresh from the ledger whenever needed.
From the document's Description field — whatever your team wrote there prints as Notes. Blank description, no Notes section; the layout never prints empty boxes.
The Ship To card prints only when the customer account has a shipping address on file. For service businesses (like Meridian's rent invoices) that's usually nothing to fix — there's nothing to ship.
A purchase order is a commitment, not a tax document — the binding tax figures arrive with the vendor's invoice. The PO prints its estimated tax and total so both sides know the expected spend, and leaves the tax detail to the paper that legally carries it.
Was this article helpful?