Placeholders

Placeholders are tokens in your template that get replaced with live data when you generate a document (Word or PDF). They use the ${PLACEHOLDER_NAME} syntax.

Viewing available placeholders

On the Templates page, click the Available Placeholders button to open a reference panel. Placeholders are grouped by:

1. Data source (e.g., QuickBooks Online) — with connection status
2. Entity type (e.g., Invoice, Estimate, Purchase Order) — collapsible sections
3. Field group (e.g., Invoice, Customer, Line Items) — organized by category

QuickBooks Online — Invoice

Invoice

Customer

Line Items — Auto Table

Line Items — Row Placeholders

Your Company

Box Labels

QuickBooks Online — Estimate

Estimate

Customer

Line Items — Auto Table

Line Items — Row Placeholders

Your Company

Box Labels

QuickBooks Online — Purchase Order

Purchase Order

Vendor

Line Items — Auto Table

Line Items — Row Placeholders

Your Company

Box Labels

Purchase orders support both item-based and account-based line items. Account-based lines use the account name as the product/service name.

QuickBooks Online — Bill Payment

A bill payment produces a remittance advice: the document you send a vendor confirming a payment and itemizing the bills it covers.

In the US edition of QuickBooks Online there is no way to send one for a payment you made yourself — pay by ACH from your own bank, by wire, by card, or by plain check and your vendor gets nothing. Payments run through QuickBooks Bill Pay do trigger an automatic notification, but it does not list the bills the payment covers, which is the part your vendor actually needs.

The UK and Canadian editions have a built-in Send remittance option on bill payments. If you're on one of those, use this when you want the document on your own letterhead, in your own format, or with details QuickBooks doesn't include.

Bill payment fields

QuickBooks stores the check number in the same field as the payment number, so ${CHECK_NUMBER} is only filled in on check payments. On a credit card payment it is blank while ${PAYMENT_NUMBER} still has a value.

${PRINT_STATUS} is blank on any payment QuickBooks was never asked to print — which is most of them, including every payment made by ACH, card or wire. It only fills in once a check has been queued for printing or printed.

${PAY_TYPE} is worth using with care. QuickBooks records only two payment methods on a bill payment — it has no value for ACH, EFT or wire — so a payment drafted from your bank account arrives as "Check". A template that prints "Payment method: ${PAY_TYPE}" will tell a vendor you sent a check when you sent an ACH. If your remittance advice needs to name the method, write it into the template itself, or put it in the payment's Ref no. or Memo field in QuickBooks.

QuickBooks pre-fills Ref no. with a counter that runs per account rather than per company, so every credit card payment in your company can arrive as 1. Ref no. is editable on the payment in QuickBooks — if you want a reference your vendor can quote back to you, such as an ACH trace number or your own payment-run reference, type it there and it flows straight through to ${PAYMENT_NUMBER}. To see what a particular payment will produce, view it in the app before building your template: each placeholder is listed with its current value.

Ref no. is also how bill payments are listed and searched in the app, so what you see in the Doc # filter is what ${PAYMENT_NUMBER} will print. Where two payments share a Ref no., tell them apart by the vendor, date and amount shown alongside. A payment with no Ref no. at all is listed by its QuickBooks id instead, so the entry is never blank.

Vendor fields

A bill payment carries no address of its own, so every address placeholder is filled from the vendor record in QuickBooks.

${VENDOR_ACCOUNT_NUMBER} is worth putting on a remittance advice. It comes from the Account no. field on the vendor in QuickBooks — the number that vendor uses to identify your company — and it is how their accounts receivable clerk finds you before they even look at your bill numbers. It's blank unless somebody filled that field in on the vendor record.

Line item fields

On a remittance advice, each line is a bill the payment settles rather than a product sold.

Auto table

Row placeholders

Note that ${LINE_BILL_BALANCE} is the bill's balance as it stands today, not as it stood on the payment date — a fully paid bill shows 0.00. QuickBooks does not keep historical balances, and for the same reason this column is left out of the ${LINE_ITEMS} table. Use ${LINE_PAYMENT_AMOUNT} for the figure this payment contributed.

Your company

These fill in your own company's name and contact details, from your QuickBooks company settings.

Your remittance advice is only as good as your Bill no.

${LINE_BILL_NUMBER} comes from the Bill no. field on the bill in QuickBooks. That field is where you record the vendor's own invoice number, and it is the column that makes a remittance advice work — it's what lets your vendor match your payment to their invoices without calling you.

QuickBooks does not fill it in for you. Unlike an invoice, a bill is not auto-numbered: if nobody typed a Bill no. when the bill was entered, QuickBooks stores nothing, and ${LINE_BILL_NUMBER} comes out blank on your document. The rest of the row — dates, totals, amount paid — still fills in, so the remittance advice remains usable, but your vendor has more work to do.

If your remittance advice has blank bill numbers, the fix is in QuickBooks, not here: open the bill and enter the vendor's invoice number in Bill no., then generate the document again. Before building your template, view a bill payment in the app — every placeholder is listed with its current value, so you can see straight away whether your bills carry numbers.

Payments that apply a vendor credit

A payment can also apply a vendor credit or a deposit, and those get a row of their own. On such a row:

• ${LINE_BILL_NUMBER} and ${LINE_BILL_DATE} hold the credit's number and date, so the deduction names itself.
• ${LINE_PAYMENT_AMOUNT} is negative, because the credit reduces what you actually paid.
• ${LINE_TXN_TYPE} reads Vendor Credit or Deposit rather than Bill.
• ${LINE_BILL_DUE_DATE}, ${LINE_BILL_TOTAL} and ${LINE_BILL_BALANCE} are blank — a credit has no due date, bill total or outstanding balance.

Each bill row shows the amount the payment settles that bill for in full, including anything the credit covered, and the credit is then deducted on its own row. So the ${LINE_PAYMENT_AMOUNT} column adds up to ${TOTAL_AMOUNT}, the cash that actually left your account:

This is what a vendor expects to see: both bills confirmed as settled, the credit shown as the deduction that explains why the payment is smaller than their total.

When the rows don't add up

The rows are a claim that they explain the total at the bottom, and that is the first thing your vendor will check. Occasionally they won't: QuickBooks holds an overpayment as a credit rather than as a line, so a payment can be larger than everything it visibly settles.

When that happens the app tells you before you build the document. View the bill payment and you'll see a warning naming both figures — what the rows come to, and what the payment actually was. Open the payment in QuickBooks and confirm what it settles before sending anything to your vendor.

You may occasionally see a different warning saying a transaction could not be read from QuickBooks. That one is not about your data: the amount paid is still right, but the bill number, dates and totals will be blank on those rows because the records behind them didn't come back. Generate the document again in a moment — it usually clears.

QuickBooks Online — Credit Memo

A credit memo is the document you send a customer when you owe them money back — a return, a billing correction, or a goodwill credit.

QuickBooks Online has no custom form style for one. Under Custom form styles you can build a style for an invoice, estimate, sales receipt, sales order or purchase order, but not for a credit memo, and there is no way to import your own. So a business that has carefully branded its invoices still sends a stock QuickBooks credit note alongside them. Use these placeholders to issue the credit on the same letterhead as the invoice it corrects.

Credit Memo

Customer

Line Items — Auto Table

Line Items — Row Placeholders

Your Company

Box Labels

${REMAINING_CREDIT} is how much of the credit the customer has not yet used, as it stands today — not as it stood on the credit memo's date. A credit that has since been applied in full reads 0.00, even on a document dated before it was applied. Use ${TOTAL_AMOUNT} for the value of the credit itself.

A credit memo carries no due date, because there is nothing to pay. ${PAYMENT_TERMS} exists and QuickBooks will copy it across from the customer record, but it rarely means anything on a credit — leave it off unless you know you want it.

QuickBooks Online — Customer Statement

A statement is a summary of what a customer owes you — the document you send at the end of the month so somebody in their accounts department knows what to pay.

QuickBooks Online will produce one, but gives you no say in how it looks. Custom form styles does not offer a statement at all, custom fields are unavailable on them, and the columns are fixed. Most visibly, a statement will not show a purchase order number against each invoice.

QuickBooks Online has no P.O. number field on an invoice either, so companies that need one add a custom field and record it there. Those custom fields are available on a statement as row placeholders: a field named P.O. Number becomes ${LINE_CUSTOM_PO_NUMBER}, which puts it in a column of its own. Use the name you gave your own field.

Statements come in two kinds. An open item statement lists every invoice still carrying a balance, whenever it was raised. A balance forward statement opens with what was owed before the period, lists everything that happened during it, and carries a running balance down the page.

Statement

Aging

Customer

Transaction Rows — Auto Table

Transaction Rows — Row Placeholders

Your Company

The aging placeholders total what is unpaid into the usual receivables buckets, measured as at the statement date from each transaction's due date — or from its own date where it has none, which is how QuickBooks ages receivables. They are the figures a collections call is made from.

Each row of the statement is one transaction, and every transaction posted to accounts receivable is there — journal entries, deposits, and refunds as well as invoices, payments, and credits. ${LINE_TYPE} names it the way QuickBooks does. On an open item statement ${LINE_AMOUNT} is the transaction total and ${LINE_OPEN_AMOUNT} is what remains unpaid on it. On a balance forward statement ${LINE_OPEN_AMOUNT} is the running balance after that transaction, and payments and credits appear as negative amounts.

These fill in your own company's name and contact details, from your QuickBooks company settings.

QuickBooks Online — Sales Register

A sales register lists every invoice, sales receipt and credit memo in a period, one row each. Credit memos are negative, so the totals are what you actually sold. Amounts are in your home currency; ${LINE_CURRENCY} and ${LINE_DOCUMENT_TOTAL} give each document's own currency and total. See Sales Register.

Custom fields work on each row too. A field on your sales prints as ${LINE_CUSTOM_…}, and a field on the customer as ${LINE_CUSTOMER_CUSTOM_…}, so a customer field named TIN becomes ${LINE_CUSTOMER_CUSTOM_TIN}.

Register

Register Rows — Auto Table

Register Rows — Row Placeholders

Your Company

Custom fields

If you have custom fields on your QuickBooks invoices, estimates, purchase orders, and credit memos, they are automatically available as placeholders. This includes all custom field types: text, number, date, and dropdown lists.

QuickBooks offers no transaction custom fields on bill payments, customer statements, and sales registers, but vendor and customer custom fields are still available on them.

How custom field placeholders are named

All custom field placeholders are prefixed with CUSTOM_ to clearly distinguish them from built-in fields. The rest of the name is converted to UPPER_CASE with underscores replacing spaces, and special characters (periods, commas, etc.) are removed.

Examples:

Dropdown fields

Dropdown (list) custom fields are fully supported. When you use a dropdown custom field in QuickBooks, the placeholder is populated with the selected option's display text — not the internal ID. For example, if your "Delivery Status" dropdown has options "Customer Arranged" and "Inclusive", the placeholder will contain the text "Customer Arranged", not a number.

Viewing your custom fields

You can see the exact placeholder name and current value for each custom field by opening any entity detail page in the app. Custom fields appear in their own "Custom Fields" section with a copy button so you can paste placeholder names directly into your template.

If you've recently added or changed custom fields in QuickBooks and they aren't appearing correctly, click the refresh button on the Custom Fields section to update.

Adding new custom fields

Any custom field you add in QuickBooks will automatically be available as a placeholder — no configuration needed. Custom fields work on your invoices, estimates, purchase orders, and credit memos.

Customer and vendor custom fields

Custom fields on customer and vendor records in QuickBooks are also supported. These are extracted automatically when generating a document and use the same CUSTOM_ prefix. For example, if you add a "VAT Number" custom field to a customer in QuickBooks, it will be available as ${CUSTOM_VAT_NUMBER} in your template.

Customer custom fields appear in their own "Customer Custom Fields" section on the entity detail page. When viewing your purchase orders and bill payments, vendor custom fields appear in a "Vendor Custom Fields" section instead.

Shorthands

If a placeholder name is too long for your template layout — especially in narrow table columns — you can create a shorthand. A shorthand is a shorter name that maps to a standard placeholder, so you can use either one in your template.

For example, you could create the shorthand POS for CUSTOM_PLACE_OF_SUPPLY, then use ${POS} in your template instead of ${CUSTOM_PLACE_OF_SUPPLY}. Both will produce the same result.

Creating a shorthand

1. Browse to any entity detail page (e.g., view an invoice)
2. Find the placeholder you want to shorten
3. Click the + button next to it
4. Enter your shorthand name and click Save

Shorthands must use uppercase letters, numbers, and underscores, and cannot conflict with existing placeholder names. They are saved per connection and entity type, so you can define different shorthands for invoices and estimates if needed.

You can add filters after a shorthand, just as after any placeholder: ${POS|upper}.

Editing or removing a shorthand

On the entity detail page, shorthands appear as a green-tinted chip next to the standard placeholder. Click the pencil icon to edit or remove it.

Your company tax ID

${COMPANY_TAX_ID} is the one company placeholder that doesn't come from QuickBooks. QuickBooks doesn't share your company's tax number with apps, so you enter it once under Team > Settings > Tax ID.

Date formatting

All date placeholders (including ${LINE_SERVICE_DATE}) respect your team's date format setting. To change the format, go to Team > Settings and select your preferred format from the dropdown.

Filters

A filter changes how one placeholder prints. Add it after the placeholder name with a |:

• ${TOTAL_AMOUNT|plain} prints 1234.50 instead of 1,234.50
• ${CUSTOMER_NAME|upper} prints ACME TRADING
• ${INVOICE_DATE|date:Ymd} prints 20261001

You can chain filters. They run left to right, so ${TOTAL_AMOUNT|abs|plain} prints 1234.50 for a credit of -1,234.50.

You don't have to type filters by hand. In the placeholder lists, open a placeholder's menu and choose Format…. Choose the formatting you want, check the preview, and copy the result into your template. On a record's page, the preview uses that record's real value.

Some filters take a setting after a colon, like |round:0. Don't put quotes around settings: write |default:N/A, not |default:"N/A". Filter names can be upper or lower case.

Available filters

Filters work in table rows too: ${LINE_AMOUNT|abs} fills every row.

Amounts in words

words spells out an amount. On its own it uses the style printed on US checks. Add a currency code for that currency's wording: USD, LKR, INR, GBP or AUD.

A negative amount starts with "Minus". To spell a credit as a positive amount, put abs first: ${TOTAL_AMOUNT|abs|words:GBP}.

Dates

date takes the same letters PHP uses for dates. The most useful are d (day, 01), j (day, 1), m (month, 10), F (October), M (Oct), Y (year, 2026) and y (26).

The fiscal filters take the month your fiscal year starts, from 1 to 12. A fiscal year is named by the calendar year it starts in. For a year starting in April, ${INVOICE_DATE|fiscal_year:4,2}${INVOICE_DATE|quarter:4} prints 263 for an invoice dated October 2026.

Mistakes

When you upload a template, we check its filters. A misspelled filter, a missing setting, or a filter that doesn't suit its placeholder (like words on a customer name) shows as a warning. Until you fix it, that placeholder prints without the filter.