Donor Statement Personalisations

These personalisations are available to both Donor and Income Statements, with some exclusions identified below.

Date personalisations

{date}

Today's date

Date Format

Output the date using the format you specify

There are options available with the personalisation "date":

{date}
This will output using your default date format setup in Administration / System / Date and Time

{datelong}
This will output using the format based on the addition of format characters. The format character options are:

You can use any of the available formats from this list.

Examples:
{date F Y} will output January 2018
{periodstart d F} will output 1 January
{periodend M Y} will output Jan 2019

{periodstart}

First date of the specified reporting period

{periodend}

Last date of the specified reporting period

{enddate} and {end date}

Last date of the specified reporting period. This is the same value as {periodend}, so use whichever reads better in your template. Write it with or without the space: {enddate} and {end date} both work.

The format characters described above apply to these as well, for example {enddate F Y} will output March 2027.

Statement Items

{all items}

List a line of text which describes all the available pledges. The information on the line is customisable. by including words from the following list.

Note that the GST(or VAT) percentage is taken from the administration / system / finance / "Current GST Rate" field.

This personalisation also supports font tags (see details in this section)

This personalisation also supports conditional tags (see details in this section)

{totals}

{totals} has a number of options available:

It can be helpful to combined these totals. You can combine the statement or the lifetime values.

{openingbalance} and {closingbalance}

This displays the opening and closing balance for the transaction period. This balance is calculated when the process of printing the statement is started. This balance is updated during the process of producing the statement depending on what is shown on the statement.

The matching {closingbalance} is calculated by taking the {openingbalance} and adding items from the following personalisations:

• all pledge items when {paidamount} is used
• tax item list grouped when {amount} is used
• track1 group list when {amount} is used
• track2 group list when {amount} is used
• all items when {amount} is used
• income when {amount} is used

{income}

For those people who are connected to a tracking category (Xero users only), as a Recipient who receives money. This personalisation allows you to list the transactions received as income.

This personalisation also supports font tags (see details in this section)

{pledges}

List a line of text which describes all the available pledges. The information on the line is customisable by including words from the following list.

Example usage:

To show the amount the the frequency of all pledges, include the following text.

{pledges amount frequency}

If no words are included then the following is the default:

 {pledges amount frequency start [end]to end}

Note that other words and letters of your choosing can be included in this text For example, Date range:

{pledges amount - frequency. Date range: start [end]to end}

{all pledge items}

This outputs a table of information related to pledges. Each column is evenly spaced across the page. One row is shown for each pledge item. For instance, if you have a monthly pledge for 12 months there will be 12 rows shown.

This personalisation also supports font tags (see details in this section)

Example usage:
Just output the list of pledge dates, payments required.

{all pledge items date pledgeamount} 

If no keywords are included then the following is used:

{all pledge items date pledgeamount paidamount pledgepaidbalance}

{pledgesummary}

This is only available to Donor Statements

This outputs one table covering all of the person's pledges, with a single row for each pledge. Where {all pledge items} gives a row for every payment, {pledgesummary} gives a row for every pledge, so a donor with two pledges gets two rows. Rows are grouped by pledge drive, drive name from Z to A, and then by pledge start date within each drive. Pledges that are not on a pledge drive come last.

Example usage:

To show just the campaign, the frequency and the three amounts:

{pledgesummary campaign frequency totalpledge paid topaywithdate}

The columns appear in the order you list them. If no keywords are included then the following is used:

{pledgesummary pledgedrive campaign formid frequency totalpledge paid topaywithdate}

Note that the keyword for the amount received is paid. The pledge detail page tables use totalpaid for the same figure, so check which of the two you are writing for.

You can rename any of these headings using the | option described in this section, for example paid|Received_so_far gives the column the heading Received so far. The combined heading and width form shown in that section has no effect on this table: column widths are shared evenly across the columns you include.

What the amounts cover

Total , Paid and Amount Left To Pay all cover the statement period, not the whole life of the pledge. A 50.00 monthly pledge shows a Total $ of 600.00 on a twelve month statement and 300.00 on a six month statement covering the same pledge.

Paid and Amount Left To Pay also reflect the Transactions up to date on the statement run, which is why the last heading carries that date. That field arrives filled in with the end of your current financial year, and it keeps whatever date it was given, so it does not follow the statement period when you change the period dates. Set it to the date you want before you generate. Bringing the date back holds later payments out of Paid and raises Amount Left To Pay by the same amount. Total $ stays as it is.

Clear Transactions up to and the heading is just Amount Left To Pay, with every payment in the period counting towards Paid $.

A pledge with no fixed end date shows its Total $ prefixed with >. More payments are still to be scheduled, so the figure is a running minimum rather than a final total.

When the person has no pledges in the period, the table prints its headings with No records found across the row. Keep that in mind if you are adding this tag to a template you use for every donor.

{balance of statement}

By default this will output a total value for all pledged and paid items that would have been listed under the {all pledge items} personalisation.

You can tailor it to only count pledges, or only count paid for items thus:

{balance of statement pledge}
{balance of statement paid}

{tax item list grouped}

These will output the list of tax rebatable items

{track1 group list}

{track2 group list}

These will output the list of items connected to the tracking categories

{supportlist}

This is only available to Donor Statements

This personalisation also supports font tags (see details in this section)

{supportkpis}

This personalisation also supports font tags (see details below)

Personalisation

{organisation name}

The name recorded on the donor's household, for example Riverside Community Trust. This is the same value as {household name}, so use whichever reads better in your template. A donor with no household leaves this blank.

Unlike the statement item tags, this one works on both Donor and Income Statements, and on a pledge detail page.

Font tags

Some of the above personalisations appear in tables. Simply using the editor to change the font of the personalisation does not affect tables, therefore an additional tag is needed to tell infoodle to use the font within the table.

The format is font[dejavusans/12pt]

This has 4 parts

• font[ : the keyword, must be lower case and preceded by a space

• dejavusans : this is the font to use. dejavusans is a good one to use, alternatives are shown in the drop down choice of fonts in the edit

• 12pt : this is the font size to use. Again, use the same values that are available in the drop down list in the editor

• ] : Closing the keyword. There is also a space after this (or the closing } of the personalisation.

Conditional Tags

This feature allows for the scenario when a column needs to contain one of several values, depending on where that value is. This is typically used when trying to output the purpose a transaction was used for. In most cases "description" is sufficient. In curtain circumstances you may want to output the Tracking category Decode if its there, and use the description if its not.

To achieve this use the ^ between the field tags. For example:

tc1decode^tc2decode^description

This outputs Tracking Category 1 decode if it has a value - otherwise it outputs Tracking Category 2 decode if that has a value - otherwise it uses the description.

Widths

Some personalisations output in tables - e.g. {all items}. You may need to control the column widths for these. This is possible by adding the letter > then a number of pixels you want to expand the column by beyond the current setting - i.e. this number is added to the current default value. e.g.

description>50

Renaming columns headings

Some personalisations output in tables - e.g. {all items}. You may need to control the heading word each column. This is possible by adding the letter | then the heading you want to use. e.g.

description|Information

If you want a space in the name - use the _ character:

description|Item_Information

If you want to change the column heading and the width:

description|Item_Information>50

Formatting issues