<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://pubgizmo.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=PubGizmoSysop</id>
	<title>PubGizmo Help - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://pubgizmo.com/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=PubGizmoSysop"/>
	<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php/Special:Contributions/PubGizmoSysop"/>
	<updated>2026-11-17T23:10:43Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.46.2</generator>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Main_Page&amp;diff=241</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Main_Page&amp;diff=241"/>
		<updated>2026-11-11T21:52:27Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages contain manuals for using [https://pubgizmo.com PubGizmo], software that helps publishers manage their presses.&lt;br /&gt;
&lt;br /&gt;
We are constantly building pages to provide help; look for more to be added her soon!&lt;br /&gt;
&lt;br /&gt;
Please [mailto:queries@pubgizmo.com click] to email us help questions.&lt;br /&gt;
&lt;br /&gt;
== Getting Started with PubGizmo ==&lt;br /&gt;
&lt;br /&gt;
# [[How to Get Your Press Aboard PubGizmo]]&lt;br /&gt;
# Options for Funding Your Subscription:&lt;br /&gt;
#* [[Funding Options for Canadian Presses|Canadian Presses]]&lt;br /&gt;
#* [[Funding Options for US Presses|US Presses]]&lt;br /&gt;
# [[Onboarding Import: Introduction]]&lt;br /&gt;
#* [[Onboarding Import: Titles]]&lt;br /&gt;
#* [[Onboarding Import: Editions]]&lt;br /&gt;
#* [[Onboarding Import: Organizations]]&lt;br /&gt;
#* [[Onboarding Import: Contacts]]&lt;br /&gt;
#* [[Onboarding Import: Contracts]]&lt;br /&gt;
&lt;br /&gt;
== Using PubGizmo ==&lt;br /&gt;
# [[How to Use PubGizmo]] – conventions, tips, and tricks&lt;br /&gt;
# [[How to Access Your Solution]] – setting up your computer to use PubGizmo&lt;br /&gt;
# [[QuickDex Helps with Finds]] – secrets for finding data fast&lt;br /&gt;
# [[Tags &amp;amp; Snapshots]] – working with selected sets of records&lt;br /&gt;
&lt;br /&gt;
== Titles ==&lt;br /&gt;
# [[New vs. Existing Titles]]&lt;br /&gt;
# [[Keywords]]&lt;br /&gt;
&lt;br /&gt;
== Contracts ==&lt;br /&gt;
[[Configuring, Recording, and Disbursing Subsidiary Rights]]&lt;br /&gt;
&lt;br /&gt;
== Royalties ==&lt;br /&gt;
# [[Sales Data Needed to Compute Royalties]]&lt;br /&gt;
# [[Importing Sales Data]]&lt;br /&gt;
# [[Running Royalties]]&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
[[Handling Slow Access and Crashes]]&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Main_Page&amp;diff=240</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Main_Page&amp;diff=240"/>
		<updated>2026-11-11T21:51:55Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages contain manuals for using [https://pubgizmo.com PubGizmo], software that helps publishers manage their presses.&lt;br /&gt;
&lt;br /&gt;
We are constantly building pages to provide help; look for more to be added her soon!&lt;br /&gt;
&lt;br /&gt;
Please [mailto:queries@pubgizmo.com click] to email us help questions.&lt;br /&gt;
&lt;br /&gt;
== Getting Started with PubGizmo ==&lt;br /&gt;
&lt;br /&gt;
# [[How to Get Your Press Aboard PubGizmo]]&lt;br /&gt;
# Options for Funding Setup, Subscription, and Users&lt;br /&gt;
#* [[Funding Options for Canadian Presses|For Canadian Presses]]&lt;br /&gt;
#* [[Funding Options for US Presses|For US Presses]]&lt;br /&gt;
# [[Onboarding Import: Introduction]]&lt;br /&gt;
#* [[Onboarding Import: Titles]]&lt;br /&gt;
#* [[Onboarding Import: Editions]]&lt;br /&gt;
#* [[Onboarding Import: Organizations]]&lt;br /&gt;
#* [[Onboarding Import: Contacts]]&lt;br /&gt;
#* [[Onboarding Import: Contracts]]&lt;br /&gt;
&lt;br /&gt;
== Using PubGizmo ==&lt;br /&gt;
# [[How to Use PubGizmo]] – conventions, tips, and tricks&lt;br /&gt;
# [[How to Access Your Solution]] – setting up your computer to use PubGizmo&lt;br /&gt;
# [[QuickDex Helps with Finds]] – secrets for finding data fast&lt;br /&gt;
# [[Tags &amp;amp; Snapshots]] – working with selected sets of records&lt;br /&gt;
&lt;br /&gt;
== Titles ==&lt;br /&gt;
# [[New vs. Existing Titles]]&lt;br /&gt;
# [[Keywords]]&lt;br /&gt;
&lt;br /&gt;
== Contracts ==&lt;br /&gt;
[[Configuring, Recording, and Disbursing Subsidiary Rights]]&lt;br /&gt;
&lt;br /&gt;
== Royalties ==&lt;br /&gt;
# [[Sales Data Needed to Compute Royalties]]&lt;br /&gt;
# [[Importing Sales Data]]&lt;br /&gt;
# [[Running Royalties]]&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
[[Handling Slow Access and Crashes]]&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Funding_Options_for_US_Presses&amp;diff=239</id>
		<title>Funding Options for US Presses</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Funding_Options_for_US_Presses&amp;diff=239"/>
		<updated>2026-11-11T21:43:54Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: Created page with &amp;quot;Are you a US press thinking about moving to PubGizmo, and wondering whether anyone will help pay for it? The honest answer is: maybe, depending on what kind of press you are.  The United States has no equivalent of the Canada Book Fund, and very little government money goes to publishers for technology. What does exist comes mostly from private foundations, and nearly all of it is reserved for &amp;#039;&amp;#039;&amp;#039;nonprofit literary presses&amp;#039;&amp;#039;&amp;#039; (501(c)(3) organizations, or presses working...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Are you a US press thinking about moving to PubGizmo, and wondering whether anyone will help pay for it? The honest answer is: maybe, depending on what kind of press you are.&lt;br /&gt;
&lt;br /&gt;
The United States has no equivalent of the Canada Book Fund, and very little government money goes to publishers for technology. What does exist comes mostly from private foundations, and nearly all of it is reserved for &#039;&#039;&#039;nonprofit literary presses&#039;&#039;&#039; (501(c)(3) organizations, or presses working under a nonprofit fiscal sponsor). If that describes you, there are real options, including one new fund that pays for exactly the kind of infrastructure change a move to PubGizmo represents. If you are a for-profit trade, educational, or scholarly press, the options are thin, and we say so below.&lt;br /&gt;
&lt;br /&gt;
For Canadian presses, see [[Funding Options for Canadian Presses]].&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Last checked: November 11, 2026.&#039;&#039;&#039; Funders change their programs often. Always read the current guidelines before you apply. We are not grant writers or funding officers, and nothing here is a promise that a funder will accept PubGizmo as an eligible expense.&lt;br /&gt;
&lt;br /&gt;
== Before You Start ==&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Check your status first.&#039;&#039;&#039; Almost every program on this page requires nonprofit status, either your own 501(c)(3) or a fiscal sponsor&#039;s. (NEA is the exception: it won&#039;t accept applications through fiscal sponsors.) Most also require that the majority of what you publish be literary work: fiction, poetry, creative nonfiction, drama, or literary criticism.&lt;br /&gt;
# &#039;&#039;&#039;Apply before you spend.&#039;&#039;&#039; Most funders won&#039;t pay for costs you incurred before the grant period starts. If you plan to fund your move to PubGizmo with a grant, apply first, then subscribe.&lt;br /&gt;
# &#039;&#039;&#039;Know which kind of fund you&#039;re applying to.&#039;&#039;&#039; There are two kinds on this page:&lt;br /&gt;
## &#039;&#039;&#039;Project and capacity-building grants&#039;&#039;&#039; fund a specific change, such as replacing spreadsheets with a royalty and title management system. These are the best fit.&lt;br /&gt;
## &#039;&#039;&#039;General operating grants&#039;&#039;&#039; are unrestricted. You can spend them on your ordinary running costs, and a software subscription is an ordinary running cost.&lt;br /&gt;
# &#039;&#039;&#039;Ask us for paperwork.&#039;&#039;&#039; Funders want real numbers. We are happy to give you a written quote showing your setup fee, your annual or monthly subscription, and any additional users. See [[How to Get Your Press Aboard PubGizmo]] for how our pricing works.&lt;br /&gt;
&lt;br /&gt;
== At a Glance ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!Program&lt;br /&gt;
!Who it&#039;s for&lt;br /&gt;
!Type&lt;br /&gt;
!Amount&lt;br /&gt;
!Most recent / next deadline&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for US Presses#Literary Arts Fund: Innovation Project Grants|Literary Arts Fund: Innovation Project Grants]]&lt;br /&gt;
|Nonprofit literary presses, nationwide&lt;br /&gt;
|Infrastructure / capacity project&lt;br /&gt;
|$25,000 to $100,000&lt;br /&gt;
|Aug. 17, 2026; next expected summer 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for US Presses#Literary Arts Fund: General Operating Grants|Literary Arts Fund: General Operating Grants]]&lt;br /&gt;
|Nonprofit literary presses, nationwide&lt;br /&gt;
|Operating (unrestricted, 5 years)&lt;br /&gt;
|2026 awards: $40,000 to $500,000&lt;br /&gt;
|Dec. 19, 2025; next open call expected January 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for US Presses#CLMP: NYSCA NYTAP Regrant Program|CLMP: NYSCA NYTAP Regrant Program]]&lt;br /&gt;
|Nonprofit literary presses in New York State&lt;br /&gt;
|Capacity building (software named)&lt;br /&gt;
|$2,500, $5,000, or $7,500&lt;br /&gt;
|&#039;&#039;&#039;Jan. 11, 2027&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for US Presses#CLMP: Professional Development Consulting Program|CLMP: Professional Development Consulting Program]]&lt;br /&gt;
|Literary presses, nationwide&lt;br /&gt;
|Paid consultant hours&lt;br /&gt;
|10 to 20 hours of consulting&lt;br /&gt;
|&#039;&#039;&#039;Jan. 11, 2027&#039;&#039;&#039;&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for US Presses#National Endowment for the Arts: Grants for Arts Projects (Literary Publishing)|NEA: Grants for Arts Projects]]&lt;br /&gt;
|Nonprofit literary presses, 5+ years&lt;br /&gt;
|Publishing project (1:1 match)&lt;br /&gt;
|$10,000 to $100,000&lt;br /&gt;
|Feb. 2026; next expected February 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for US Presses#Poetry Foundation: General Operating Support|Poetry Foundation: General Operating Support]]&lt;br /&gt;
|Nonprofit poetry presses&lt;br /&gt;
|Operating (unrestricted)&lt;br /&gt;
|$10,000 to $75,000&lt;br /&gt;
|July 15 annually&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for US Presses#Amazon Literary Partnership|Amazon Literary Partnership]]&lt;br /&gt;
|Nonprofit literary organizations, including publishers&lt;br /&gt;
|Project or general support&lt;br /&gt;
|$5,000 to $20,000&lt;br /&gt;
|May 1, 2026; next expected spring 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for US Presses#Your State Arts Agency|Your state arts agency]]&lt;br /&gt;
|Varies by state&lt;br /&gt;
|Usually operating or project&lt;br /&gt;
|Varies&lt;br /&gt;
|Varies&lt;br /&gt;
|}&lt;br /&gt;
Deadlines marked &amp;quot;expected&amp;quot; are our guess based on last year&#039;s cycle. The funder hasn&#039;t announced them yet. Two deadlines are coming up soon: both CLMP programs close on &#039;&#039;&#039;January 11, 2027&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
== National Programs ==&lt;br /&gt;
&lt;br /&gt;
=== Literary Arts Fund: Innovation Project Grants ===&lt;br /&gt;
The Literary Arts Fund is new. It is a collaborative of major foundations (including Mellon, Ford, MacArthur, Lannan, Hawthornden, and the Poetry Foundation), and it plans to give at least $50 million to nonprofit literary organizations over five years, through 2031. Its innovation grants are the best US match we found for a move to PubGizmo.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; $25,000 to $100,000 per project. The 2026 round awarded $1 million in total.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# An independent nonprofit (or fiscally sponsored) literary arts organization, press, or publication, based and active in the US.&lt;br /&gt;
# Your primary mission must directly support adult creative writers, and publishing their work counts.&lt;br /&gt;
# Established for at least three years (by incorporation date, or by the date of your fiscal sponsorship contract).&lt;br /&gt;
# An executive director who has been in the role for at least 12 consecutive months.&lt;br /&gt;
# An annual operating budget of at least $50,000, not counting in-kind contributions. If you are fiscally sponsored, your press must meet this on its own, not your sponsor.&lt;br /&gt;
# &#039;&#039;&#039;Not eligible:&#039;&#039;&#039; presses that are part of, or fiscally sponsored by, a college or university; presses focused on young writers; and several other groups (drama, storytelling, arts therapy, literacy, libraries, and service organizations).&lt;br /&gt;
# If you received a Literary Arts Fund general operating grant, you can&#039;t apply on your own for an innovation grant until 12 months after that award. You can still take part in a collaborative application.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; the grants pay for new, one-time projects that address structural or infrastructure challenges at a literary nonprofit. Outside summaries of the 2026 guidelines list organizational infrastructure and &amp;quot;new systems and processes&amp;quot; among the kinds of projects that qualify. Replacing hand-built royalty spreadsheets and scattered contract records with a single system is an infrastructure project. Applications can also be collaborative, so several small presses could apply together, led by one nonprofit, to move to PubGizmo as a group. Read the full guidelines when the next round opens to confirm what costs are allowed.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Complete the eligibility quiz, then apply through the Literary Arts Fund&#039;s [https://literaryartsfund.submittable.com/submit Submittable portal].&lt;br /&gt;
# The 2026 round opened June 8, 2026, closed &#039;&#039;&#039;August 17, 2026&#039;&#039;&#039;, and decisions are due by December 31, 2026. The fund plans to run this program every year, so expect a similar summer window in 2027.&lt;br /&gt;
# Questions: grants@literaryartsfund.org.&lt;br /&gt;
&lt;br /&gt;
=== Literary Arts Fund: General Operating Grants ===&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; the first round, announced in June 2026, gave $7.7 million to 40 organizations and publishers, in grants of $40,000 to $500,000. Each grant is paid as a single payment meant to cover five years.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies:&#039;&#039;&#039; the same eligibility rules as the Innovation Project Grants, above.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; these grants are unrestricted. They support a press&#039;s mission, activities, and administrative needs, which includes the systems you use to run the press.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when:&#039;&#039;&#039; the first open call ran from November 10 to December 19, 2025. The open call for 2027 grants is expected to start in &#039;&#039;&#039;January 2027&#039;&#039;&#039; (date not yet confirmed). Apply through the same [https://literaryartsfund.submittable.com/submit Submittable portal].&lt;br /&gt;
&lt;br /&gt;
=== CLMP: NYSCA NYTAP Regrant Program ===&lt;br /&gt;
This program is for New York State presses only, but it is the only one we found that names &#039;&#039;&#039;software upgrades&#039;&#039;&#039; as an example of an eligible project. The Community of Literary Magazines and Presses (CLMP) runs it with funding from the New York State Council on the Arts.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; one-year grants of $2,500, $5,000, or $7,500. You can&#039;t request more than 50% of your operating budget from your most recently completed fiscal year.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# A literary press or magazine based in New York State.&lt;br /&gt;
# Nonprofit, or with a fiscal sponsor that is also in New York.&lt;br /&gt;
# At least one title or issue published in the past 18 months.&lt;br /&gt;
# More than 50% of your published work is literary (fiction, poetry, creative nonfiction, drama, or literary reviews).&lt;br /&gt;
# &#039;&#039;&#039;Not eligible:&#039;&#039;&#039; presses that publish mainly children&#039;s literature, hybrid publishers, self-publishers, and publishers that received NYSCA funding for 2027.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; projects must build capacity rather than pay the routine costs of publishing. The guidelines give software upgrades as an example, and consultant fees can be included in the budget.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Download the application preview and budget template from the [https://www.clmp.org/funding-for-publishers/nysca-nytap-regrant-program/ program page], then apply through Submittable.&lt;br /&gt;
# The portal opened November 9, 2026, and closes &#039;&#039;&#039;January 11, 2027, at 11:59 p.m. ET&#039;&#039;&#039;. Grants are announced in March 2027, and projects must be completed by November 30, 2027.&lt;br /&gt;
# Questions: ckern@clmp.org.&lt;br /&gt;
&lt;br /&gt;
=== CLMP: Professional Development Consulting Program ===&lt;br /&gt;
This program doesn&#039;t pay for software, but it can pay for an expert to help you plan and carry out the change.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;What it pays:&#039;&#039;&#039; 10 to 20 hours of work with a professional consultant. The money goes directly to the consultant.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# A US-based literary press or magazine that has published at least one title or issue in the past 18 months.&lt;br /&gt;
# More than 50% of your published work is literary.&lt;br /&gt;
# &#039;&#039;&#039;Not eligible:&#039;&#039;&#039; hybrid publishers, self-publishers, presses that publish mainly children&#039;s literature, and New York State publishers that received 2027 NYSCA funding.&lt;br /&gt;
# You must have a consultant confirmed &#039;&#039;&#039;before&#039;&#039;&#039; you apply.&lt;br /&gt;
# The guidelines don&#039;t say whether for-profit presses can apply. An earlier CLMP information session said both nonprofit and for-profit publishers were eligible, so for-profit presses should ask CLMP directly.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; eligible areas include &amp;quot;overall operations.&amp;quot; A consultant could help you audit your contracts and royalty data, clean it up before [[Onboarding Import: Introduction|import into PubGizmo]], and redesign your royalty workflow. Ask CLMP whether a consultant tied to a software vendor would be acceptable before you choose one.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Download the application preview from the [https://www.clmp.org/funding-for-publishers/professional-development-consulting-program/ program page], then apply through Submittable.&lt;br /&gt;
# The portal opened November 9, 2026, and closes &#039;&#039;&#039;January 11, 2027, at 11:59 p.m. ET&#039;&#039;&#039;. Grants are announced in March 2027, and consulting runs March to November 2027.&lt;br /&gt;
&lt;br /&gt;
=== National Endowment for the Arts: Grants for Arts Projects (Literary Publishing) ===&lt;br /&gt;
The NEA is the main federal arts funder. It doesn&#039;t fund general operating costs, but it does allow technology costs inside a publishing project.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; $10,000 to $100,000. Every grant needs a &#039;&#039;&#039;1:1 cost share&#039;&#039;&#039;: you match the NEA&#039;s money dollar for dollar, with cash or in-kind contributions.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# A US 501(c)(3) nonprofit. Literary journals, independent presses, and university presses can apply under Literary Publishing.&lt;br /&gt;
# At least five years of arts programming before the deadline, and at least $20,000 in operating expenses in your most recent fiscal year.&lt;br /&gt;
# &#039;&#039;&#039;Not eligible:&#039;&#039;&#039; for-profit presses, applications through a fiscal sponsor, and individuals. Generally one application per year.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; Literary Publishing projects publish, distribute, or promote contemporary literary work, and they may include new technology and efforts to advance literary publishing. The NEA&#039;s FAQ says costs for updated technology, including hardware and software, can be included as long as they fit the proposed project. PubGizmo wouldn&#039;t be the project itself, but its cost could be part of the budget for a publishing project. For example, the project could cover a season of titles, with PubGizmo managing their contracts, metadata, and royalties.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Literary Publishing uses the NEA&#039;s &#039;&#039;&#039;February&#039;&#039;&#039; deadline. In the most recent cycle, Part 1 (on Grants.gov) was due February 12, 2026, and Part 2 (the NEA Applicant Portal) was due February 25, 2026. Register with Grants.gov and SAM.gov well ahead of time.&lt;br /&gt;
# The NEA expects to publish new guidelines by late December 2026. Check the [https://www.arts.gov/grants/grants-for-arts-projects Grants for Arts Projects page] for the 2027 dates.&lt;br /&gt;
&lt;br /&gt;
=== Poetry Foundation: General Operating Support ===&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; $10,000 to $75,000, for 12 months, unrestricted.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Nonprofit poetry presses and publications based in the US or a US territory. Presses without 501(c)(3) status can apply through a fiscal sponsor.&lt;br /&gt;
# A minimum operating budget of $20,000 (in-kind revenue counts).&lt;br /&gt;
# Presses whose mission is publishing underrepresented poets, with content that is at least 50% poetry, are considered case by case.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; this is unrestricted money for your core operations, so it can cover a subscription.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Request access to the Poetry Foundation&#039;s grants portal through its [https://poetryfoundation.org/grants/general-operating-support General Operating Support page].&lt;br /&gt;
# The deadline is &#039;&#039;&#039;July 15&#039;&#039;&#039; each year (the following Monday if it falls on a weekend).&lt;br /&gt;
&lt;br /&gt;
=== Amazon Literary Partnership ===&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; $5,000 to $20,000.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies:&#039;&#039;&#039; US nonprofit literary organizations that develop and support writers. Past recipients include independent publishers of fiction, nonfiction, and poetry.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; a modest grant that could cover part of your setup fee and first year&#039;s subscription, if you can tie the request clearly to your mission of publishing writers. Amazon doesn&#039;t give guidance on individual applications.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when:&#039;&#039;&#039; the 2026 window closed &#039;&#039;&#039;May 1, 2026&#039;&#039;&#039;, and recipients were announced in July. Watch for the 2027 call, and apply through the [https://apply.amazonliterarypartnership.com/submit Amazon Literary Partnership portal].&lt;br /&gt;
&lt;br /&gt;
=== Your State Arts Agency ===&lt;br /&gt;
Every state has an arts agency, and many give operating or project grants to nonprofit literary organizations, including presses. Amounts, eligibility, and deadlines vary widely, so look up your own state&#039;s agency. Some states also fund regrant programs for literary publishers (the CLMP New York program above is one example). Your regional arts organization (such as South Arts or Mid-America Arts Alliance) may also have literary programs.&lt;br /&gt;
&lt;br /&gt;
== If You&#039;re a For-Profit Press ==&lt;br /&gt;
We looked hard, and found almost nothing. Every grant on this page, apart from possibly the CLMP consulting program, requires nonprofit status or a fiscal sponsor. The NEA specifically excludes commercial enterprises. Your realistic options are:&lt;br /&gt;
&lt;br /&gt;
# Ask CLMP whether you can apply to the Professional Development Consulting Program.&lt;br /&gt;
# Check your state or city economic development office for small business grants. These change often and are rarely specific to publishing.&lt;br /&gt;
# Look at small business loans. Unlike a grant, a loan has to be repaid, but it can spread the cost of setup over time.&lt;br /&gt;
&lt;br /&gt;
If your press publishes literary work and has a mission beyond profit, it may be worth talking to a lawyer or accountant about fiscal sponsorship, which some small presses use to become eligible for foundation grants.&lt;br /&gt;
&lt;br /&gt;
== Programs That Don&#039;t Fit (and Why) ==&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;NEH Infrastructure and Capacity Building Challenge Grants:&#039;&#039;&#039; discontinued. The final deadline was May 17, 2023.&lt;br /&gt;
# &#039;&#039;&#039;CLMP Capacity-Building Grant Program&#039;&#039;&#039; (funded by the Hawthornden Foundation): offered grants of $5,000 or $10,000, but the most recent cycle we found was 2024. Watch CLMP&#039;s site in case it returns.&lt;br /&gt;
# &#039;&#039;&#039;CLMP Small Press Future Fund:&#039;&#039;&#039; a one-time program for presses that had been distributed by Small Press Distribution when it closed.&lt;br /&gt;
# &#039;&#039;&#039;CLMP Literary Magazine Fund:&#039;&#039;&#039; for literary magazines only, not presses.&lt;br /&gt;
# &#039;&#039;&#039;SBIR and STTR:&#039;&#039;&#039; federal research-and-development grants for businesses building new technology, not for buying or adopting existing software.&lt;br /&gt;
&lt;br /&gt;
== Some Wording You Can Adapt ==&lt;br /&gt;
Funders want to know what problem you are solving and what will change. Here are a few phrases you might adapt for your own application. Change them to describe your press honestly.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describing the problem&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&amp;quot;Our royalty statements are currently prepared by hand in spreadsheets, which takes approximately [X] staff days each royalty period and has led to errors and late statements to our authors.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describing the project&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&amp;quot;We will move our title, contract, rights, and royalty records into PubGizmo, a publisher-specific management system. The project includes cleaning and importing our existing data, training [X] staff, and running our first royalty period in the new system.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describing the results&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&amp;quot;We expect to reduce the time spent on royalty preparation by [X]%, send accurate statements on time to all [X] of our authors, and maintain complete, consistent metadata for our [X] active titles, so that more of our small staff&#039;s time goes to editing and promoting our writers&#039; work.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Budget line&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&amp;quot;PubGizmo setup fee (one-time): $[X]. PubGizmo annual subscription, [X] users: $[X]. (Quote attached.)&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Need Help? ==&lt;br /&gt;
We can&#039;t write your application for you, but we can answer questions about what PubGizmo does, give you a written quote, and describe the onboarding timeline so your project plan is realistic. Email us (see [[How to Get Your Press Aboard PubGizmo]]). We are patient and kind – honest!&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Funding_Options_for_Canadian_Presses&amp;diff=238</id>
		<title>Funding Options for Canadian Presses</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Funding_Options_for_Canadian_Presses&amp;diff=238"/>
		<updated>2026-11-11T21:14:19Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: Created page with &amp;quot;Are you thinking about moving to PubGizmo but wondering how to pay for it? You&amp;#039;re not alone. Many Canadian presses run on tight budgets, and a new system can be a hard thing to justify. The good news: several federal and provincial funders will help pay for technology that makes a press more efficient, and a PubGizmo subscription fits into a number of their programs.  This page lists the grants we know of that a Canadian press moving to PubGizmo could reasonably apply to...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Are you thinking about moving to PubGizmo but wondering how to pay for it? You&#039;re not alone. Many Canadian presses run on tight budgets, and a new system can be a hard thing to justify. The good news: several federal and provincial funders will help pay for technology that makes a press more efficient, and a PubGizmo subscription fits into a number of their programs.&lt;br /&gt;
&lt;br /&gt;
This page lists the grants we know of that a Canadian press moving to PubGizmo could reasonably apply to. For each one, we explain how much is available, who qualifies, how to apply, and when. We have left out programs that don&#039;t apply (and we tell you which ones, and why, near the bottom of the page).&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Last checked: November 11, 2026.&#039;&#039;&#039; Funders change their programs every year, sometimes with little notice. Always read the current guidelines and talk to the program officer before you apply. We are not grant writers or funding officers, and nothing here is a promise that a funder will accept PubGizmo as an eligible expense.&lt;br /&gt;
&lt;br /&gt;
== Before You Start ==&lt;br /&gt;
A few things are true of almost every program on this page:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Apply before you spend.&#039;&#039;&#039; Most funders will not pay for costs you incurred before the application deadline, or before you sign their agreement. If you plan to fund your move to PubGizmo with a grant, apply first, then subscribe.&lt;br /&gt;
# &#039;&#039;&#039;Grants rarely cover everything.&#039;&#039;&#039; Most programs pay a share of your costs, commonly 50% to 75%. You will need to cover the rest from your own funds or another source. Some funders also cap the total of all government help on a project.&lt;br /&gt;
# &#039;&#039;&#039;Know which kind of fund you&#039;re applying to.&#039;&#039;&#039; There are two kinds on this page:&lt;br /&gt;
## &#039;&#039;&#039;Technology and business-development programs&#039;&#039;&#039; fund a specific project, such as replacing your royalty and title management system. These are the best fit.&lt;br /&gt;
## &#039;&#039;&#039;Operating programs&#039;&#039;&#039; give you money for your general costs of running the press. A software subscription is normally an ordinary operating expense, so it can usually come out of an operating grant, but the grant itself isn&#039;t aimed at technology.&lt;br /&gt;
# &#039;&#039;&#039;Ask us for paperwork.&#039;&#039;&#039; Funders want quotes. We are happy to give you a written quote showing your setup fee, your annual or monthly subscription, and any additional users, so you can put real numbers in your budget. See [[How to Get Your Press Aboard PubGizmo]] for how our pricing works.&lt;br /&gt;
&lt;br /&gt;
== At a Glance ==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!Program&lt;br /&gt;
!Where&lt;br /&gt;
!Type&lt;br /&gt;
!Amount&lt;br /&gt;
!Most recent / next deadline&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for Canadian Presses#Canada Book Fund: Business Development|Canada Book Fund: Business Development]]&lt;br /&gt;
|Canada&lt;br /&gt;
|Technology / business planning&lt;br /&gt;
|Up to $50,000 (business planning); up to $30,000 or $45,000 (technology internship)&lt;br /&gt;
|Feb. 2, 2026; next expected early 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for Canadian Presses#Canada Book Fund: Publishing Support|Canada Book Fund: Publishing Support]]&lt;br /&gt;
|Canada&lt;br /&gt;
|Operating (formula)&lt;br /&gt;
|Formula-based; no fixed maximum&lt;br /&gt;
|April 1, 2026; next expected spring 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for Canadian Presses#Canada Council for the Arts: Literary Publishers|Canada Council: Literary Publishers]]&lt;br /&gt;
|Canada&lt;br /&gt;
|Operating (core, multi-year)&lt;br /&gt;
|Up to $250,000/year (books)&lt;br /&gt;
|Spring 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for Canadian Presses#Canada Council for the Arts: Sector Support, Innovation and Development|Canada Council: Sector Support, Innovation and Development]]&lt;br /&gt;
|Canada&lt;br /&gt;
|Capacity / innovation&lt;br /&gt;
|Up to $100,000&lt;br /&gt;
|Not yet open&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for Canadian Presses#British Columbia: BC Arts Council Operating Assistance|BC Arts Council: Operating Assistance]]&lt;br /&gt;
|BC&lt;br /&gt;
|Operating&lt;br /&gt;
|$20,000 minimum for new applicants&lt;br /&gt;
|Oct. 8, 2026; next expected fall 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for Canadian Presses#Alberta: Book Publishers Operating Grant|Alberta: Book Publishers Operating Grant]]&lt;br /&gt;
|AB&lt;br /&gt;
|Operating and business development&lt;br /&gt;
|$5,000 to $125,000&lt;br /&gt;
|June 1 annually&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for Canadian Presses#Saskatchewan: Business Improvement Grant|Creative Saskatchewan: Business Improvement Grant]]&lt;br /&gt;
|SK&lt;br /&gt;
|Technology&lt;br /&gt;
|Up to 50%, max $15,000/year&lt;br /&gt;
|June 10, 2026; next expected spring 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for Canadian Presses#Manitoba: Looking Forward|Manitoba Arts Council: Looking Forward]]&lt;br /&gt;
|MB&lt;br /&gt;
|Business models / sustainability&lt;br /&gt;
|Up to $15,000 (exploration) or $35,000 (implementation)&lt;br /&gt;
|Nov. 15, 2026; then July 15, 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for Canadian Presses#Ontario: Ontario Creates Enterprise Fund|Ontario Creates: Enterprise Fund]]&lt;br /&gt;
|ON&lt;br /&gt;
|Business innovation / efficiency&lt;br /&gt;
|Up to 75%, max $80,000&lt;br /&gt;
|Aug. 27, 2026; next expected summer 2027&lt;br /&gt;
|-&lt;br /&gt;
|[[Funding Options for Canadian Presses#Ontario: Ontario Arts Operating Fund|Ontario Arts Council: Ontario Arts Operating Fund]]&lt;br /&gt;
|ON&lt;br /&gt;
|Operating&lt;br /&gt;
|Varies&lt;br /&gt;
|March 2026; next expected early 2027&lt;br /&gt;
|}&lt;br /&gt;
Deadlines marked &amp;quot;expected&amp;quot; are our guess based on last year&#039;s cycle. The funder hasn&#039;t announced them yet.&lt;br /&gt;
&lt;br /&gt;
== Federal Programs ==&lt;br /&gt;
&lt;br /&gt;
=== Canada Book Fund: Business Development ===&lt;br /&gt;
This is the federal program most directly aimed at the kind of change a move to PubGizmo represents. It&#039;s run by Canadian Heritage, and it has three project types. Two of them are useful here.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Amounts&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Business planning:&#039;&#039;&#039; up to 50% of eligible costs, to a maximum of $50,000. Indigenous, racialized-owned, and official-language minority publishers can get up to 75%, still to a maximum of $50,000.&lt;br /&gt;
# &#039;&#039;&#039;Technology internship:&#039;&#039;&#039; up to 50% of costs, to a maximum of $30,000 (or 75%, to a maximum of $45,000, for the same designated groups, or for Indigenous or racialized interns).&lt;br /&gt;
&lt;br /&gt;
Total government help on the project can&#039;t be more than 75% of its cost (90% for designated groups and small literary publishers, 100% for not-for-profits). Projects can last up to 12 months.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Business planning:&#039;&#039;&#039; presses that received Canada Book Fund Publishing Support in 2025–26, or that received a grant in the most recent cycle of the Canada Council&#039;s Literary Publishers program.&lt;br /&gt;
# &#039;&#039;&#039;Technology internship:&#039;&#039;&#039; presses that received Canada Book Fund Publishing Support in 2025–26.&lt;br /&gt;
# You can send only one Business Development application per fiscal year, across all project types.&lt;br /&gt;
&lt;br /&gt;
In short: if you already get Canada Book Fund or Canada Council core funding, you can probably apply. If you don&#039;t, you can&#039;t apply to this one yet.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Business planning projects that put &amp;quot;a significant emphasis&amp;quot; on new technology strategies for production, marketing, or &#039;&#039;&#039;information management&#039;&#039;&#039; get funding priority. A plan to replace spreadsheets or an old royalty system with PubGizmo, including your rights, contracts, royalties, and title metadata, is an information-management project.&lt;br /&gt;
&lt;br /&gt;
Eligible costs are third-party fees (consultants, research and analysis, preparing the plan), executive training related to the plan, and administration fees up to 15%. Salaries of owners and staff are not eligible. The guidelines don&#039;t mention software subscriptions, so ask the program officer whether your PubGizmo setup fee and first year&#039;s subscription can be included, or whether you should limit the budget to consulting and data-preparation costs.&lt;br /&gt;
&lt;br /&gt;
A &#039;&#039;&#039;technology internship&#039;&#039;&#039; could pay for an intern who prepares and cleans your data for [[Onboarding Import: Introduction|import into PubGizmo]], then helps your staff adopt the new system.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Read the [https://www.canada.ca/en/canadian-heritage/services/funding/book-fund/business-development/application-guidelines.html application guidelines].&lt;br /&gt;
# Apply through the [https://pch-financement-funding.canada.ca/en-CA/ Canadian Heritage Funding Portal]. You&#039;ll need the application form, a project plan, and (for an internship) the intern&#039;s résumé. Incomplete applications are rejected.&lt;br /&gt;
# The last deadline was &#039;&#039;&#039;February 2, 2026, at 4 p.m. ET&#039;&#039;&#039;, for projects starting between April 1, 2026, and March 31, 2027. Expect the next deadline around early February 2027, so now is a good time to start planning.&lt;br /&gt;
# Questions: flc-sae-cbf-sfp@pch.gc.ca, or 1-866-811-0055 (toll-free).&lt;br /&gt;
&lt;br /&gt;
=== Canada Book Fund: Publishing Support ===&lt;br /&gt;
This is Canadian Heritage&#039;s main annual funding for Canadian-owned book publishers. It isn&#039;t a technology program, but the money is flexible.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Amount&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Funding is calculated by formula from your eligible sales, so there is no fixed minimum or maximum. Affiliated groups are capped at $850,000 in base funding. Total government help can&#039;t be more than 75% of your book publishing expenses (90% for designated groups and small literary publishers).&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# At least 75% Canadian-owned and controlled, with your head office and at least 75% of employees in Canada.&lt;br /&gt;
# At least 12 months operating as a book publisher, and financially viable.&lt;br /&gt;
# Up to date on author royalty payments.&lt;br /&gt;
# &#039;&#039;&#039;Titles:&#039;&#039;&#039; in general, at least 10 eligible titles since you started and 6 over the last three financial years. Trade-only publishers need 15 and 12. In the reference year you must also publish at least one new Canadian-authored title and at least one digital title or edition. Some publisher groups can count new editions toward these numbers.&lt;br /&gt;
# &#039;&#039;&#039;Sales:&#039;&#039;&#039; at least $50,000 in eligible net sales of your own titles in the reference year ($20,000 for official-language minority, Indigenous, and racialized-owned publishers).&lt;br /&gt;
# At least 65% of your net revenue must come from book publishing and sales (40% for designated groups).&lt;br /&gt;
# A book counts as Canadian-authored if at least one author is a Canadian citizen or permanent resident.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Eligible uses of the funds include &#039;&#039;&#039;managing bibliographical data&#039;&#039;&#039;, author royalties, capital expenses, and overhead such as administrative costs. PubGizmo handles your title metadata (including ONIX), your contracts, and your royalty calculations, so its cost falls naturally under bibliographic data management and administrative overhead.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Read the [https://www.canada.ca/en/canadian-heritage/services/funding/book-fund/publishing-support/application-guidelines.html application guidelines].&lt;br /&gt;
# Apply through the Canadian Heritage Funding Portal. You&#039;ll need financial statements, a production report, a business plan, an author payment certification, and cover and copyright pages of your books.&lt;br /&gt;
# The 2026–27 deadline was &#039;&#039;&#039;April 1, 2026, at 4 p.m. ET&#039;&#039;&#039;. Expect the next one in spring 2027.&lt;br /&gt;
# Questions: info@pch.gc.ca, or 1-866-811-0055.&lt;br /&gt;
&lt;br /&gt;
Receiving Publishing Support also makes you eligible for Business Development (above), so it&#039;s worth applying to both.&lt;br /&gt;
&lt;br /&gt;
=== Canada Council for the Arts: Literary Publishers ===&lt;br /&gt;
This is the Canada Council&#039;s multi-year core (operating) grant for literary publishers.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; up to $250,000 a year for book publishers ($300,000 for publishers of both books and magazines).&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Canadian literary book publishers (and creative-writing magazine publishers), with a validated profile in the Canada Council portal.&lt;br /&gt;
# Either you already receive core support from this component, &#039;&#039;&#039;or&#039;&#039;&#039; you have received at least two Literary Publishing Projects grants in the last three years and had more than $30,000 in revenue in each of those years.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; this is general operating support. A subscription is an ordinary running cost of your press, but confirm with your program officer how to present it in your budget.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when:&#039;&#039;&#039; the next intake is &#039;&#039;&#039;spring 2027&#039;&#039;&#039;. Apply through the [https://canadacouncil.ca/funding/grants/supporting-artistic-practice/literary-publishers Canada Council portal].&lt;br /&gt;
&lt;br /&gt;
=== Canada Council for the Arts: Sector Support, Innovation and Development ===&lt;br /&gt;
This is a new Canada Council component that isn&#039;t open yet. We list it because it looks promising.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; up to $100,000 per application.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Why it&#039;s worth watching:&#039;&#039;&#039; it can fund work that makes an organization more stable and sustainable, including building &#039;&#039;&#039;digital capacity&#039;&#039;&#039;. It is open to organizations as well as individuals. The Canada Council doesn&#039;t yet say whether it covers an organization&#039;s own systems or only projects that benefit the wider arts sector, so check with them once it opens.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;When:&#039;&#039;&#039; it will open after the Canada Council launches its updated portal. No date has been announced. See the [https://canadacouncil.ca/funding/grants/upcoming-funding-opportunities/sector-support-innovation-and-development program preview].&lt;br /&gt;
&lt;br /&gt;
== Provincial Programs ==&lt;br /&gt;
&lt;br /&gt;
=== British Columbia: BC Arts Council Operating Assistance ===&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; new applicants receive at least $20,000. There is no stated maximum. (For comparison, BC book publishers received roughly $25,000 to $70,000 each in 2025–26.)&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# BC-based and Canadian-owned. Companies must be at least 75% owned, and managed and financially controlled, by BC residents. Non-profits must be registered in BC for at least a year.&lt;br /&gt;
# Book publishing is your primary business, with your head office, editorial office, and management in BC for at least one fiscal year.&lt;br /&gt;
# At least 4 eligible titles in print, at least 2 published in the previous year, and an ongoing publishing program.&lt;br /&gt;
# Each eligible book must have at least 50% Canadian-authored or illustrated content.&lt;br /&gt;
# &#039;&#039;&#039;New applicants&#039;&#039;&#039; must have received at least three BC Arts Council grants since April 1, 2022, including at least one Operating Assistance or Project Assistance: Literary Arts grant.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; this grant supports your general operations, and a subscription is an operating cost. Note that capital expenses, including equipment purchases over $2,500, aren&#039;t eligible. A subscription isn&#039;t a capital purchase.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Read the [https://www.bcartscouncil.ca/program/book-publishers/ program guidelines].&lt;br /&gt;
# Apply through the BC Arts Council&#039;s online grant system, with financial and statistical forms completed in CADAC. New applicants must confirm their intent with the Program Advisor about two weeks before the deadline so they can be set up in CADAC.&lt;br /&gt;
# The 2026–27 intake ran from July 22 to &#039;&#039;&#039;October 8, 2026&#039;&#039;&#039;. Results are expected in late February 2027. Expect the next intake in summer–fall 2027.&lt;br /&gt;
# Questions: Michelle Benjamin, Program Advisor (Literary Arts), 236-478-2582, Michelle.Benjamin@gov.bc.ca.&lt;br /&gt;
&lt;br /&gt;
=== Alberta: Book Publishers Operating Grant ===&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; $5,000 to $125,000, calculated from your eligible sales and the number of eligible titles you published in the 12 months before the deadline.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Alberta-based book or ebook publishers whose primary activity is publishing.&lt;br /&gt;
# Majority Alberta ownership (at least 51%), with editorial control held by Alberta residents.&lt;br /&gt;
# You must publish authors other than your owners and board, and titles by principals can&#039;t be more than 25% of your output.&lt;br /&gt;
# You must have published a minimum number of eligible titles. Check the current [https://open.alberta.ca/publications/cultural-industry-book-publishers-operating-grant-guidelines program guidelines] for the exact threshold and sales rules.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; the grant covers &amp;quot;operating and business development related expenses&amp;quot; for book publishers. Both describe a PubGizmo subscription well.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Read the guidelines, then request access to set up an online profile (new applicants).&lt;br /&gt;
# The deadline is &#039;&#039;&#039;June 1 each year, at 11:59 p.m.&#039;&#039;&#039;&lt;br /&gt;
# Questions: Cultural Industry Grants, 780-422-8584 (dial 310-0000 first for toll-free in Alberta). See the [https://www.alberta.ca/book-publishers-operating-grant program page].&lt;br /&gt;
&lt;br /&gt;
=== Saskatchewan: Business Improvement Grant ===&lt;br /&gt;
Creative Saskatchewan&#039;s Business Improvement Grant is the provincial program that most clearly names software.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; up to 50% of your approved project budget, to a maximum of $15,000 per applicant per fiscal year.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Saskatchewan creative businesses, including book publishers, that meet Creative Saskatchewan&#039;s [https://www.creativesask.ca/general-program-guidelines/ General Program Guidelines].&lt;br /&gt;
# Technology expenses are limited to Saskatchewan residents and operations.&lt;br /&gt;
# If ineligible expenses make up more than 50% of your project budget, the whole application is ineligible.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; the grant supports &amp;quot;technology infrastructure updates,&amp;quot; including &#039;&#039;&#039;hardware and software that improves business or production efficiencies&#039;&#039;&#039;, plus staff training that goes with the new technology. Software subscriptions aren&#039;t mentioned specifically, so confirm with Creative Saskatchewan that a subscription (rather than a one-time purchase) qualifies.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Read the [https://www.creativesask.ca/our-support/business-improvement/ Business Improvement Grant guidelines].&lt;br /&gt;
# Apply through Creative Saskatchewan&#039;s online Grant Management System, using their budget template.&lt;br /&gt;
# In 2026–27, the program opened April 22, 2026, and the book publishing deadline was &#039;&#039;&#039;June 10, 2026, at 4 p.m. SK time&#039;&#039;&#039;. Expect a similar spring window in 2027. Funding is limited, so apply early.&lt;br /&gt;
# Questions: office@creativesask.ca, 306-798-9800.&lt;br /&gt;
&lt;br /&gt;
=== Manitoba: Looking Forward ===&lt;br /&gt;
The Manitoba Arts Council runs Looking Forward with The Winnipeg Foundation. It funds research into, and adoption of, new business models and ways of operating.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; exploration grants up to $15,000. Implementation grants up to $35,000.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Manitoba-based arts and culture organizations, in continuous operation for at least three years.&lt;br /&gt;
# Registered charities and non-profits are eligible. &#039;&#039;&#039;For-profit companies are eligible only if they are book or periodical publishers.&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; the program supports new business models, organizational sustainability, and new ways of working. Eligible costs include consultant and specialist fees, some staff time (capped at 15% of the request for regular full-time staff), and overhead (capped at 15%). Software isn&#039;t listed either way, so book a consultation before you build your budget.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Apply online through Manipogo. Register your profile 5 to 10 business days before you apply.&lt;br /&gt;
# The fall 2026 deadline is &#039;&#039;&#039;November 15, 2026&#039;&#039;&#039; (results in mid-January 2027). The next deadline is &#039;&#039;&#039;July 15, 2027&#039;&#039;&#039;.&lt;br /&gt;
# You can book a free, confidential consultation with strategic advisor Judy Murphy before applying. See the [https://artscouncil.mb.ca/?p=46048 program page].&lt;br /&gt;
&lt;br /&gt;
=== Ontario: Ontario Creates Enterprise Fund ===&lt;br /&gt;
&#039;&#039;&#039;Amount:&#039;&#039;&#039; up to 75% of your approved budget, to a maximum of $80,000 (or $150,000 for partnership applications).&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Who qualifies&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# For-profit, Canadian-owned and controlled, incorporated in Canada, and Ontario-based.&lt;br /&gt;
# You must have received Ontario Creates publishing (or screen) funding in the last five years.&lt;br /&gt;
# Two years of financial statements, sound finances, and good standing with Ontario Creates.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How it fits PubGizmo:&#039;&#039;&#039; the fund supports innovative projects that relate to your core business and are distinct from your regular operations. &amp;quot;Strategic business efficiencies&amp;quot; are named as an example, and technology or systems that improve efficiency count toward the Relevance and Innovation score. Hardware and software are eligible capital costs, but are limited to 50% of their cost (or straight-line amortization over 12 months). A strong application would present your move to PubGizmo as a larger efficiency project, for example: data cleanup, system migration, staff training, and new royalty and metadata workflows, with measurable goals.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Conditions to note:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# The remaining 25% of the budget must come from you or other sources, and at least 10% must be cash from a source other than Ontario Creates.&lt;br /&gt;
# Outside services need quotes and a reason for choosing the provider. We can supply a quote.&lt;br /&gt;
# You must set at least one financial goal with dollar-value KPIs.&lt;br /&gt;
# Projects run 6 to 20 months, and payment comes in three stages (60% on signing, 25% after the interim report, 15% after the final report).&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;How to apply and when&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
# Read the [https://www.ontariocreates.ca/uploads/Industry_Initiatives/ENG/Industry-Development-Program/Enterprise-Fund-Guidelines.pdf Enterprise Fund guidelines].&lt;br /&gt;
# Apply at [https://apply.ontariocreates.ca/ apply.ontariocreates.ca], using the Excel budget template.&lt;br /&gt;
# The 2026–27 deadline was &#039;&#039;&#039;August 27, 2026, at 5 p.m. ET&#039;&#039;&#039;. Decisions come within 16 weeks. Expect the next deadline around late summer 2027.&lt;br /&gt;
# Questions: Gillian Fizet, gfizet@ontariocreates.ca, 416-642-6627.&lt;br /&gt;
&lt;br /&gt;
=== Ontario: Ontario Arts Operating Fund ===&lt;br /&gt;
As of 2026, the Ontario Arts Council has a single operating program, the Ontario Arts Operating Fund. It supports Ontario-based non-profits and &#039;&#039;&#039;for-profit book and magazine publishers&#039;&#039;&#039;. Like other operating grants, it isn&#039;t aimed at technology, but it can help with your general costs, including a subscription.&lt;br /&gt;
&lt;br /&gt;
The 2026 deadlines for Literature Organizations were in March 2026. 2025–26 recipients of OAC operating grants were invited to apply automatically. See the [https://www.arts.on.ca/grants/ontario-arts-operating-fund program page] for eligibility, and contact the program officer, Barbara Gilbert (bgilbert@arts.on.ca, 416-969-7427), to ask about entry for new applicants.&lt;br /&gt;
&lt;br /&gt;
== Programs That Don&#039;t Fit (and Why) ==&lt;br /&gt;
We looked at these, so you don&#039;t have to:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Quebec, SODEC Programme d&#039;aide aux éditeurs de livres:&#039;&#039;&#039; the 2026–27 program has no technology component, and its promotion aid specifically excludes software subscriptions and licences.&lt;br /&gt;
# &#039;&#039;&#039;New Brunswick, Book and Periodical Publishers Operational Support Program:&#039;&#039;&#039; the 2026–29 recipients have already been selected. Watch for the next cycle.&lt;br /&gt;
# &#039;&#039;&#039;Nova Scotia:&#039;&#039;&#039; the Publishers Assistance Fund was cut in the 2026–27 budget. The Creative Industries Fund is focused on reaching markets outside the province, not internal systems.&lt;br /&gt;
# &#039;&#039;&#039;Newfoundland and Labrador, Publishers Assistance Program:&#039;&#039;&#039; covers editing, design, marketing, and professional development, not technology.&lt;br /&gt;
# &#039;&#039;&#039;Prince Edward Island, Publishing Assistance:&#039;&#039;&#039; covers acquisition, production, and distribution costs of books.&lt;br /&gt;
# &#039;&#039;&#039;Ontario Creates Publishing Marketing &amp;amp; Discoverability Fund:&#039;&#039;&#039; ongoing operational costs are ineligible, and software is capped at 15% of a marketing project.&lt;br /&gt;
# &#039;&#039;&#039;BC Arts Council Project Assistance: Literary Arts:&#039;&#039;&#039; funds specific books, not operating or systems costs.&lt;br /&gt;
# &#039;&#039;&#039;Canada Digital Adoption Program (CDAP):&#039;&#039;&#039; this federal technology program is closed to new applicants.&lt;br /&gt;
# &#039;&#039;&#039;Canada Book Fund Support for Organizations:&#039;&#039;&#039; open to associations and collective projects, not individual presses.&lt;br /&gt;
# &#039;&#039;&#039;Territories:&#039;&#039;&#039; we found no program for publishers in Yukon, the Northwest Territories, or Nunavut that covers technology.&lt;br /&gt;
&lt;br /&gt;
We have also left out tax credits and loans. Provincial book publishing tax credits exist in several provinces, but they reward publishing activity in general rather than funding a system change.&lt;br /&gt;
&lt;br /&gt;
== Some Wording You Can Adapt ==&lt;br /&gt;
Funders want to know what problem you are solving and what will change. Here are a few phrases you might adapt for your own application. Change them to describe your press honestly.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describing the problem&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&amp;quot;Our royalty statements are currently prepared by hand in spreadsheets, which takes approximately [X] staff days each royalty period and has led to errors and late statements to authors.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describing the project&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&amp;quot;We will move our title, contract, rights, and royalty records into PubGizmo, a Canadian, publisher-specific management system. The project includes cleaning and importing our existing data, training [X] staff, and running our first royalty period in the new system.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Describing the results&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&amp;quot;We expect to reduce the time spent on royalty preparation by [X]%, issue accurate statements on time to all [X] authors, and maintain complete, consistent metadata for our [X] active titles.&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Budget line&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
: &#039;&#039;&amp;quot;PubGizmo setup fee (one-time): $[X]. PubGizmo annual subscription, [X] users: $[X]. (Quote attached.)&amp;quot;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Need Help? ==&lt;br /&gt;
We can&#039;t write your application for you, but we can answer questions about what PubGizmo does, give you a written quote, and describe the onboarding timeline so your project plan is realistic. Email us (see [[How to Get Your Press Aboard PubGizmo]]). We are patient and kind – honest!&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=237</id>
		<title>Optimizing PubGizmo Speed</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=237"/>
		<updated>2026-10-14T14:32:29Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: /* Distance From Servers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To interact with PubGizmo, data must travel through the internet between your computer and our servers, and then your computer must process that data.&lt;br /&gt;
&lt;br /&gt;
Here are steps to ensure you&#039;ve done everything you can to optimize your experience.&lt;br /&gt;
&lt;br /&gt;
== Test Your Speed ==&lt;br /&gt;
[[File:Screenshot 2026-10-12 at 11.28.25.png|thumb|150x150px|Click to retest]]&lt;br /&gt;
First, test! You can do this by visiting the Home screen and clicking the About PubGizmo tab. At the bottom of the screen you&#039;ll see &#039;&#039;&#039;Connection Speed&#039;&#039;&#039; and a coloured button.&lt;br /&gt;
&lt;br /&gt;
* green: great speed, things will be smooth and quick&lt;br /&gt;
* amber: okay speed&lt;br /&gt;
* red: poor speed, working will be suboptimal&lt;br /&gt;
&lt;br /&gt;
Speed is tested when you login, but you can do an instant test by clicking the indicator. This allows you to change your circumstances and re-test to determine if that had an effect.&lt;br /&gt;
&lt;br /&gt;
If you hover your mouse over the button, you&#039;ll see a value; this is a raw number that indicates latency.&lt;br /&gt;
&lt;br /&gt;
== Causes and Potential Fixes ==&lt;br /&gt;
&lt;br /&gt;
=== Poor Network Connection ===&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connectioncan impede network traffic. And &amp;quot;ping&amp;quot; matters too; a high ping number (30+) indicates high latency.&lt;br /&gt;
&lt;br /&gt;
Things that may internet speed:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Get closer to the WiFi:&#039;&#039;&#039; This one&#039;s pretty easy: if your WiFi unit sits in the basement and you&#039;re on the third floor, get closer! The further your WiFi signal has to travel, the more walls and floors it must penetrate, the more devices (phones, other computers, TVs, microwave ovens, etc., which introduce radio interference), between your computer and the WiFi, the slower your connection. Remember to test as you make changes to your environment by clicking the coloured test button; you may be able to find the sweet spot where speed is optimal.&lt;br /&gt;
# &#039;&#039;&#039;Wire up:&#039;&#039;&#039; If you have the option of connecting directly to your network using an ethernet cable, do it; cable is the fastest connection.&lt;br /&gt;
# &#039;&#039;&#039;Talk to your internet supplier:&#039;&#039;&#039; If your speed is nowhere near what you are paying for (e.g., you pay for 1GB speed and you are only getting 10% of that), there may be a problem with your internet. They can help troubleshoot and ensure you&#039;re getting what you pay for.&lt;br /&gt;
&lt;br /&gt;
=== Slow Computer ===&lt;br /&gt;
Is your computer generally slow at other tasks? If yes, then an issue lies with your computer, either the hardware or your operating system. A number of factors can impede computer speed:&lt;br /&gt;
&lt;br /&gt;
==== Software/Operating System ====&lt;br /&gt;
Issues with your operating system (Windows or macOS) can slow down your computer. This kind of issue accrues over time as your computer receives updates and as you install and remove programs. Windows is especially prone to this, more so than macOS. The best bet is a complete wipe and reinstall of your OS; it&#039;s not a trivial task, but it can yield significant improvements (some say it&#039;s like getting a new computer), not just in terms of speed, but also stability.&lt;br /&gt;
&lt;br /&gt;
You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
==== Computer ====&lt;br /&gt;
&lt;br /&gt;
===== Bad Hardware =====&lt;br /&gt;
If your problems survive a wipe/reinstall, there could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== New Computer =====&lt;br /&gt;
We recognize that a new computer represents significant expense, but it can really help if your current hardware is old and slow.&lt;br /&gt;
&lt;br /&gt;
====== What Kind of Computer Should I Get? ======&lt;br /&gt;
While PubGizmo works fine on both PCs and Macs, it runs best on Macs. Not only are Macs faster than PCs, they are also much more reliable in terms of operating system integrity (see above) and hardware quality, and require less support – we do tech support too, and this is empirically true, whatever your cranky uncle tells you. They may cost more, but they are more rugged and last longer than PCs.&lt;br /&gt;
&lt;br /&gt;
FileMaker Pro, the software that runs PubGizmo, also performs better on Macs. We&#039;re not sure why. Even a base model [https://www.apple.com/ca/macbook-neo/ MacBook Neo] handles PubGizmo well (provided your internet speed is good too).&lt;br /&gt;
&lt;br /&gt;
=== Distance From Servers ===&lt;br /&gt;
This one is harder to fix: your distance from one of PubGizmo&#039;s two servers will be a factor in your access speed – it&#039;s the physics of network latency. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re visiting Frankfurt or Hong Kong and accessing PG, it will take longer for data to travel between your location and the server.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=236</id>
		<title>Optimizing PubGizmo Speed</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=236"/>
		<updated>2026-10-14T01:18:12Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To interact with PubGizmo, data must travel through the internet between your computer and our servers, and then your computer must process that data.&lt;br /&gt;
&lt;br /&gt;
Here are steps to ensure you&#039;ve done everything you can to optimize your experience.&lt;br /&gt;
&lt;br /&gt;
== Test Your Speed ==&lt;br /&gt;
[[File:Screenshot 2026-10-12 at 11.28.25.png|thumb|150x150px|Click to retest]]&lt;br /&gt;
First, test! You can do this by visiting the Home screen and clicking the About PubGizmo tab. At the bottom of the screen you&#039;ll see &#039;&#039;&#039;Connection Speed&#039;&#039;&#039; and a coloured button.&lt;br /&gt;
&lt;br /&gt;
* green: great speed, things will be smooth and quick&lt;br /&gt;
* amber: okay speed&lt;br /&gt;
* red: poor speed, working will be suboptimal&lt;br /&gt;
&lt;br /&gt;
Speed is tested when you login, but you can do an instant test by clicking the indicator. This allows you to change your circumstances and re-test to determine if that had an effect.&lt;br /&gt;
&lt;br /&gt;
If you hover your mouse over the button, you&#039;ll see a value; this is a raw number that indicates latency.&lt;br /&gt;
&lt;br /&gt;
== Causes and Potential Fixes ==&lt;br /&gt;
&lt;br /&gt;
=== Poor Network Connection ===&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connectioncan impede network traffic. And &amp;quot;ping&amp;quot; matters too; a high ping number (30+) indicates high latency.&lt;br /&gt;
&lt;br /&gt;
Things that may internet speed:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Get closer to the WiFi:&#039;&#039;&#039; This one&#039;s pretty easy: if your WiFi unit sits in the basement and you&#039;re on the third floor, get closer! The further your WiFi signal has to travel, the more walls and floors it must penetrate, the more devices (phones, other computers, TVs, microwave ovens, etc., which introduce radio interference), between your computer and the WiFi, the slower your connection. Remember to test as you make changes to your environment by clicking the coloured test button; you may be able to find the sweet spot where speed is optimal.&lt;br /&gt;
# &#039;&#039;&#039;Wire up:&#039;&#039;&#039; If you have the option of connecting directly to your network using an ethernet cable, do it; cable is the fastest connection.&lt;br /&gt;
# &#039;&#039;&#039;Talk to your internet supplier:&#039;&#039;&#039; If your speed is nowhere near what you are paying for (e.g., you pay for 1GB speed and you are only getting 10% of that), there may be a problem with your internet. They can help troubleshoot and ensure you&#039;re getting what you pay for.&lt;br /&gt;
&lt;br /&gt;
=== Slow Computer ===&lt;br /&gt;
Is your computer generally slow at other tasks? If yes, then an issue lies with your computer, either the hardware or your operating system. A number of factors can impede computer speed:&lt;br /&gt;
&lt;br /&gt;
==== Software/Operating System ====&lt;br /&gt;
Issues with your operating system (Windows or macOS) can slow down your computer. This kind of issue accrues over time as your computer receives updates and as you install and remove programs. Windows is especially prone to this, more so than macOS. The best bet is a complete wipe and reinstall of your OS; it&#039;s not a trivial task, but it can yield significant improvements (some say it&#039;s like getting a new computer), not just in terms of speed, but also stability.&lt;br /&gt;
&lt;br /&gt;
You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
==== Computer ====&lt;br /&gt;
&lt;br /&gt;
===== Bad Hardware =====&lt;br /&gt;
If your problems survive a wipe/reinstall, there could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== New Computer =====&lt;br /&gt;
We recognize that a new computer represents significant expense, but it can really help if your current hardware is old and slow.&lt;br /&gt;
&lt;br /&gt;
====== What Kind of Computer Should I Get? ======&lt;br /&gt;
While PubGizmo works fine on both PCs and Macs, it runs best on Macs. Not only are Macs faster than PCs, they are also much more reliable in terms of operating system integrity (see above) and hardware quality, and require less support – we do tech support too, and this is empirically true, whatever your cranky uncle tells you. They may cost more, but they are more rugged and last longer than PCs.&lt;br /&gt;
&lt;br /&gt;
FileMaker Pro, the software that runs PubGizmo, also performs better on Macs. We&#039;re not sure why. Even a base model [https://www.apple.com/ca/macbook-neo/ MacBook Neo] handles PubGizmo well (provided your internet speed is good too).&lt;br /&gt;
&lt;br /&gt;
=== Distance From Servers ===&lt;br /&gt;
This one is harder to fix: your distance from one of PubGizmo&#039;s two servers will be a factor in your access speed – it&#039;s the physics of network latency. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re visiting Frankfurt, it will take longer for data to travel between your location and the server.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Main_Page&amp;diff=235</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Main_Page&amp;diff=235"/>
		<updated>2026-10-14T00:41:48Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages contain manuals for using [https://pubgizmo.com PubGizmo], software that helps publishers manage their presses.&lt;br /&gt;
&lt;br /&gt;
We are constantly building pages to provide help; look for more to be added her soon!&lt;br /&gt;
&lt;br /&gt;
Please [mailto:queries@pubgizmo.com click] to email us help questions.&lt;br /&gt;
&lt;br /&gt;
== Getting Started with PubGizmo ==&lt;br /&gt;
&lt;br /&gt;
# [[How to Get Your Press Aboard PubGizmo]]&lt;br /&gt;
# [[Onboarding Import: Introduction]]&lt;br /&gt;
#* [[Onboarding Import: Titles]]&lt;br /&gt;
#* [[Onboarding Import: Editions]]&lt;br /&gt;
#* [[Onboarding Import: Organizations]]&lt;br /&gt;
#* [[Onboarding Import: Contacts]]&lt;br /&gt;
#* [[Onboarding Import: Contracts]]&lt;br /&gt;
&lt;br /&gt;
== Using PubGizmo ==&lt;br /&gt;
# [[How to Use PubGizmo]] – conventions, tips, and tricks&lt;br /&gt;
# [[How to Access Your Solution]] – setting up your computer to use PubGizmo&lt;br /&gt;
# [[QuickDex Helps with Finds]] – secrets for finding data fast&lt;br /&gt;
# [[Tags &amp;amp; Snapshots]] – working with selected sets of records&lt;br /&gt;
&lt;br /&gt;
== Titles ==&lt;br /&gt;
# [[New vs. Existing Titles]]&lt;br /&gt;
# [[Keywords]]&lt;br /&gt;
&lt;br /&gt;
== Contracts ==&lt;br /&gt;
[[Configuring, Recording, and Disbursing Subsidiary Rights]]&lt;br /&gt;
&lt;br /&gt;
== Royalties ==&lt;br /&gt;
# [[Sales Data Needed to Compute Royalties]]&lt;br /&gt;
# [[Importing Sales Data]]&lt;br /&gt;
# [[Running Royalties]]&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
[[Handling Slow Access and Crashes]]&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=234</id>
		<title>Optimizing PubGizmo Speed</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=234"/>
		<updated>2026-10-12T18:34:34Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To interact with PubGizmo, data must travel through the internet between your computer and our servers, and then your computer must process that data.&lt;br /&gt;
&lt;br /&gt;
Here are steps to ensure you&#039;ve done everything you can to optimize your experience.&lt;br /&gt;
&lt;br /&gt;
== Test Your Speed ==&lt;br /&gt;
[[File:Screenshot 2026-10-12 at 11.28.25.png|thumb|150x150px|Click to retest]]&lt;br /&gt;
First, test! You can do this by visiting the Home screen and clicking the About PubGizmo tab. At the bottom of the screen you&#039;ll see &#039;&#039;&#039;Connection Speed&#039;&#039;&#039; and a coloured button.&lt;br /&gt;
&lt;br /&gt;
* green: great speed, things will be smooth and quick&lt;br /&gt;
* amber: okay speed&lt;br /&gt;
* red: poor speed, working will be suboptimal&lt;br /&gt;
&lt;br /&gt;
Speed is tested when you login, but you can do an instant test by clicking the indicator. This allows you to change your circumstances and re-test to determine if that had an effect.&lt;br /&gt;
&lt;br /&gt;
If you hover your mouse over the button, you&#039;ll see a value; this is a raw number that indicates latency.&lt;br /&gt;
&lt;br /&gt;
== Causes and Potential Fixes ==&lt;br /&gt;
&lt;br /&gt;
=== Poor Network Connection ===&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connectioncan impede network traffic. And &amp;quot;ping&amp;quot; matters too; a high ping number (30+) indicates high latency.&lt;br /&gt;
&lt;br /&gt;
Things that may internet speed:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Get closer to the WiFi:&#039;&#039;&#039; This one&#039;s pretty easy: if your WiFi unit sits in the basement and you&#039;re on the third floor, get closer! The further your WiFi signal has to travel, the more walls and floors it must penetrate, the more devices (phones, other computers, TVs, microwave ovens, etc., which introduce radio interference), between your computer and the WiFi, the slower your connection. Remember to test as you make changes to your environment by clicking the coloured test button; you may be able to find the sweet spot where speed is optimal.&lt;br /&gt;
# &#039;&#039;&#039;Wire up:&#039;&#039;&#039; If you have the option of connecting directly to your network using an ethernet cable, do it; cable is the fastest connection.&lt;br /&gt;
# &#039;&#039;&#039;Talk to your internet supplier:&#039;&#039;&#039; If your speed is nowhere near what you are paying for (e.g., you pay for 1GB speed and you are only getting 10% of that), there may be a problem with your internet. They can help troubleshoot and ensure you&#039;re getting what you pay for.&lt;br /&gt;
&lt;br /&gt;
=== Slow Computer ===&lt;br /&gt;
Is your computer generally slow at other tasks? If yes, then an issue lies with your computer, either the hardware or your operating system. A number of factors can impede computer speed:&lt;br /&gt;
&lt;br /&gt;
==== Software/Operating System ====&lt;br /&gt;
Issues with your operating system (Windows or macOS) can slow down your computer. This kind of issue accrues over time as your computer receives updates and as you install and remove programs. Windows is especially prone to this, more so than macOS. The best bet is a complete wipe and reinstall of your OS; it&#039;s not a trivial task, but it can yield significant improvements (some say it&#039;s like getting a new computer), not just in terms of speed, but also stability.&lt;br /&gt;
&lt;br /&gt;
You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
==== Computer ====&lt;br /&gt;
&lt;br /&gt;
===== Bad Hardware =====&lt;br /&gt;
If your problems survive a wipe/reinstall, there could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== New Computer =====&lt;br /&gt;
We recognize that a new computer represents significant expense, but it can really help if your current hardware is old and slow.&lt;br /&gt;
&lt;br /&gt;
====== What Kind of Computer Should I Get? ======&lt;br /&gt;
While PubGizmo works fine on both PCs and Macs, it runs best on Macs. Not only are Macs faster than PCs, they are also much more reliable in terms of operating system integrity (see above) and hardware quality, and require less support – we do tech support too, and this is empirically true, whatever your cranky uncle tells you. They may cost more, but they are more rugged and last longer than PCs.&lt;br /&gt;
&lt;br /&gt;
FileMaker Pro, the software that runs PubGizmo, also performs better on Macs. We&#039;re not sure why. Even a base model [https://www.apple.com/ca/macbook-neo/ MacBook Neo] handles PubGizmo well (provided your internet speed is good too).&lt;br /&gt;
&lt;br /&gt;
== Are You Far Away? ==&lt;br /&gt;
Wait, are you away, connecting from somewhere other than your press&#039;s location? Your speed issue may be due to network latency caused by distance. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re in Frankfurt, you are far away, and it takes longer for data to travel between your location and the server.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=233</id>
		<title>Optimizing PubGizmo Speed</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=233"/>
		<updated>2026-10-12T18:31:25Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: /* Test Your Speed */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To interact with PubGizmo, data must travel through the internet between your computer and our servers, and then your computer must process that data.&lt;br /&gt;
&lt;br /&gt;
Here are steps to ensure you&#039;ve done everything you can to optimize your experience.&lt;br /&gt;
&lt;br /&gt;
== Test Your Speed ==&lt;br /&gt;
[[File:Screenshot 2026-10-12 at 11.28.25.png|thumb|150x150px|Click to retest]]&lt;br /&gt;
First, test! You can do this by visiting the Home screen and clicking the About PubGizmo tab. At the bottom of the screen you&#039;ll see &#039;&#039;&#039;Connection Speed&#039;&#039;&#039; and a coloured button.&lt;br /&gt;
&lt;br /&gt;
* green: great speed, things will be smooth and quick&lt;br /&gt;
* amber: okay speed&lt;br /&gt;
* red: poor speed, working will be suboptimal&lt;br /&gt;
&lt;br /&gt;
Speed is tested when you login, but you can do an instant test by clicking the indicator. This allows you to change your circumstances and re-test to determine if that had an effect.&lt;br /&gt;
&lt;br /&gt;
If you hover your mouse over the button, you&#039;ll see a value; this is a raw number that indicates latency.&lt;br /&gt;
&lt;br /&gt;
== Causes and Potential Fixes ==&lt;br /&gt;
&lt;br /&gt;
=== Poor Network Connection ===&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connectioncan impede network traffic. And &amp;quot;ping&amp;quot; matters too; a high ping number (30+) indicates high latency.&lt;br /&gt;
&lt;br /&gt;
Things that may internet speed:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Get closer to the WiFi:&#039;&#039;&#039; This one&#039;s pretty easy: if your WiFi unit sits in the basement and you&#039;re on the third floor, get closer! The further your WiFi signal has to travel, the more walls and floors it must penetrate, the more devices (phones, other computers, TVs, microwave ovens, etc., which introduce radio interference), between your computer and the WiFi, the slower your connection. Remember to test as you make changes to your environment by clicking the coloured test button; you may be able to find the sweet spot where speed is optimal.&lt;br /&gt;
# &#039;&#039;&#039;Wire up:&#039;&#039;&#039; If you have the option of connecting directly to your network using an ethernet cable, do it; cable is the fastest connection.&lt;br /&gt;
# &#039;&#039;&#039;Talk to your internet supplier:&#039;&#039;&#039; If your speed is nowhere near what you are paying for (e.g., you pay for 1GB speed and you are only getting 10% of that), there may be a problem with your internet. They can help troubleshoot and ensure you&#039;re getting what you pay for.&lt;br /&gt;
&lt;br /&gt;
=== Slow Computer ===&lt;br /&gt;
Is your computer generally slow at other tasks? If yes, then an issue lies with your computer, either the hardware or your operating system. A number of factors can impede computer speed:&lt;br /&gt;
&lt;br /&gt;
==== Software/Operating System ====&lt;br /&gt;
Issues with your operating system (Windows or macOS) can slow down your computer. This kind of issue accrues over time as your computer receives updates and as you install and remove programs. Windows is especially prone to this, more so than macOS. The best bet with either is a complete wipe and reinstall of your computer; it&#039;s not a trivial task, but it can yield significant improvements (some say it&#039;s like getting a new computer), not just in terms of speed, but also stability.&lt;br /&gt;
&lt;br /&gt;
You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
==== Computer ====&lt;br /&gt;
&lt;br /&gt;
===== Bad Hardware =====&lt;br /&gt;
If your problems survive a wipe/reinstall, there could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== New Computer =====&lt;br /&gt;
We recognize that a new computer represents significant expense, but it can really help if your current hardware is old and slow.&lt;br /&gt;
&lt;br /&gt;
====== What Kind of Computer Should I Get? ======&lt;br /&gt;
While PubGizmo works fine on both PCs and Macs, it runs best on Macs. Not only are newer Macs faster in terms of price/performance than PCs, they are also much more reliable in terms of operating system integrity (see above) and hardware quality, and require less support – we do tech support too, and this is empirically true, whatever your cranky uncle says. They may cost more, but they are more rugged and last longer than PCs.&lt;br /&gt;
&lt;br /&gt;
FileMaker Pro, the software that runs PubGizmo, also performs better on Macs. We&#039;re not sure why. Even a base model [https://www.apple.com/ca/macbook-neo/ MacBook Neo] handles PubGizmo well (provided your internet speed is good too).&lt;br /&gt;
&lt;br /&gt;
== Are You Far Away? ==&lt;br /&gt;
Wait, are you away, connecting from somewhere other than your press&#039;s location? Your speed issue may be due to network latency caused by distance. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re in Frankfurt, you are far away, and it takes longer for data to travel between your location and the server.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=232</id>
		<title>Optimizing PubGizmo Speed</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=232"/>
		<updated>2026-10-12T18:30:39Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: /* What Kind of Computer Should I Get? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To interact with PubGizmo, data must travel through the internet between your computer and our servers, and then your computer must process that data.&lt;br /&gt;
&lt;br /&gt;
Here are steps to ensure you&#039;ve done everything you can to optimize your experience.&lt;br /&gt;
&lt;br /&gt;
== Test Your Speed ==&lt;br /&gt;
[[File:Screenshot 2026-10-12 at 11.28.25.png|thumb|150x150px|Click to retest]]&lt;br /&gt;
First, test! You can do this by visiting the Home screen and clicking the About PubGizmo tab. At the bottom of the screen you&#039;ll see &#039;&#039;&#039;Connection Speed&#039;&#039;&#039; and a coloured button.&lt;br /&gt;
&lt;br /&gt;
* green: great speed, things will be smooth and quick&lt;br /&gt;
* amber: okay speed, could be better&lt;br /&gt;
* red: poor speed, working will be suboptimal&lt;br /&gt;
&lt;br /&gt;
Speed is tested when you login, but you can do an instant test by clicking the indicator. This allows you to change your circumstances and re-test to determine if that had an effect.&lt;br /&gt;
&lt;br /&gt;
If you hover your mouse over the button, you&#039;ll see a value; this is a raw number that indicates latency.&lt;br /&gt;
&lt;br /&gt;
== Causes and Potential Fixes ==&lt;br /&gt;
&lt;br /&gt;
=== Poor Network Connection ===&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connectioncan impede network traffic. And &amp;quot;ping&amp;quot; matters too; a high ping number (30+) indicates high latency.&lt;br /&gt;
&lt;br /&gt;
Things that may internet speed:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Get closer to the WiFi:&#039;&#039;&#039; This one&#039;s pretty easy: if your WiFi unit sits in the basement and you&#039;re on the third floor, get closer! The further your WiFi signal has to travel, the more walls and floors it must penetrate, the more devices (phones, other computers, TVs, microwave ovens, etc., which introduce radio interference), between your computer and the WiFi, the slower your connection. Remember to test as you make changes to your environment by clicking the coloured test button; you may be able to find the sweet spot where speed is optimal.&lt;br /&gt;
# &#039;&#039;&#039;Wire up:&#039;&#039;&#039; If you have the option of connecting directly to your network using an ethernet cable, do it; cable is the fastest connection.&lt;br /&gt;
# &#039;&#039;&#039;Talk to your internet supplier:&#039;&#039;&#039; If your speed is nowhere near what you are paying for (e.g., you pay for 1GB speed and you are only getting 10% of that), there may be a problem with your internet. They can help troubleshoot and ensure you&#039;re getting what you pay for.&lt;br /&gt;
&lt;br /&gt;
=== Slow Computer ===&lt;br /&gt;
Is your computer generally slow at other tasks? If yes, then an issue lies with your computer, either the hardware or your operating system. A number of factors can impede computer speed:&lt;br /&gt;
&lt;br /&gt;
==== Software/Operating System ====&lt;br /&gt;
Issues with your operating system (Windows or macOS) can slow down your computer. This kind of issue accrues over time as your computer receives updates and as you install and remove programs. Windows is especially prone to this, more so than macOS. The best bet with either is a complete wipe and reinstall of your computer; it&#039;s not a trivial task, but it can yield significant improvements (some say it&#039;s like getting a new computer), not just in terms of speed, but also stability.&lt;br /&gt;
&lt;br /&gt;
You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
==== Computer ====&lt;br /&gt;
&lt;br /&gt;
===== Bad Hardware =====&lt;br /&gt;
If your problems survive a wipe/reinstall, there could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== New Computer =====&lt;br /&gt;
We recognize that a new computer represents significant expense, but it can really help if your current hardware is old and slow.&lt;br /&gt;
&lt;br /&gt;
====== What Kind of Computer Should I Get? ======&lt;br /&gt;
While PubGizmo works fine on both PCs and Macs, it runs best on Macs. Not only are newer Macs faster in terms of price/performance than PCs, they are also much more reliable in terms of operating system integrity (see above) and hardware quality, and require less support – we do tech support too, and this is empirically true, whatever your cranky uncle says. They may cost more, but they are more rugged and last longer than PCs.&lt;br /&gt;
&lt;br /&gt;
FileMaker Pro, the software that runs PubGizmo, also performs better on Macs. We&#039;re not sure why. Even a base model [https://www.apple.com/ca/macbook-neo/ MacBook Neo] handles PubGizmo well (provided your internet speed is good too).&lt;br /&gt;
&lt;br /&gt;
== Are You Far Away? ==&lt;br /&gt;
Wait, are you away, connecting from somewhere other than your press&#039;s location? Your speed issue may be due to network latency caused by distance. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re in Frankfurt, you are far away, and it takes longer for data to travel between your location and the server.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=File:Screenshot_2026-10-12_at_11.28.25.png&amp;diff=231</id>
		<title>File:Screenshot 2026-10-12 at 11.28.25.png</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=File:Screenshot_2026-10-12_at_11.28.25.png&amp;diff=231"/>
		<updated>2026-10-12T18:28:52Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Connection Speed button&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=230</id>
		<title>Optimizing PubGizmo Speed</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=230"/>
		<updated>2026-10-12T18:24:40Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;To interact with PubGizmo, data must travel through the internet between your computer and our servers, and then your computer must process that data.&lt;br /&gt;
&lt;br /&gt;
Here are steps to ensure you&#039;ve done everything you can to optimize your experience.&lt;br /&gt;
&lt;br /&gt;
== Test Your Speed ==&lt;br /&gt;
First, test! You can do this by visiting the Home screen and clicking the About PubGizmo tab. At the bottom of the screen you&#039;ll see &#039;&#039;&#039;Connection Speed&#039;&#039;&#039; and a coloured button.&lt;br /&gt;
&lt;br /&gt;
* green: great speed, things will be smooth and quick&lt;br /&gt;
* amber: okay speed, could be better&lt;br /&gt;
* red: poor speed, working will be suboptimal&lt;br /&gt;
&lt;br /&gt;
Speed is tested when you login, but you can do an instant test by clicking the indicator. This allows you to change your circumstances and re-test to determine if that had an effect.&lt;br /&gt;
&lt;br /&gt;
If you hover your mouse over the button, you&#039;ll see a value; this is a raw number that indicates latency.&lt;br /&gt;
&lt;br /&gt;
== Causes and Potential Fixes ==&lt;br /&gt;
&lt;br /&gt;
=== Poor Network Connection ===&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connectioncan impede network traffic. And &amp;quot;ping&amp;quot; matters too; a high ping number (30+) indicates high latency.&lt;br /&gt;
&lt;br /&gt;
Things that may internet speed:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Get closer to the WiFi:&#039;&#039;&#039; This one&#039;s pretty easy: if your WiFi unit sits in the basement and you&#039;re on the third floor, get closer! The further your WiFi signal has to travel, the more walls and floors it must penetrate, the more devices (phones, other computers, TVs, microwave ovens, etc., which introduce radio interference), between your computer and the WiFi, the slower your connection. Remember to test as you make changes to your environment by clicking the coloured test button; you may be able to find the sweet spot where speed is optimal.&lt;br /&gt;
# &#039;&#039;&#039;Wire up:&#039;&#039;&#039; If you have the option of connecting directly to your network using an ethernet cable, do it; cable is the fastest connection.&lt;br /&gt;
# &#039;&#039;&#039;Talk to your internet supplier:&#039;&#039;&#039; If your speed is nowhere near what you are paying for (e.g., you pay for 1GB speed and you are only getting 10% of that), there may be a problem with your internet. They can help troubleshoot and ensure you&#039;re getting what you pay for.&lt;br /&gt;
&lt;br /&gt;
=== Slow Computer ===&lt;br /&gt;
Is your computer generally slow at other tasks? If yes, then an issue lies with your computer, either the hardware or your operating system. A number of factors can impede computer speed:&lt;br /&gt;
&lt;br /&gt;
==== Software/Operating System ====&lt;br /&gt;
Issues with your operating system (Windows or macOS) can slow down your computer. This kind of issue accrues over time as your computer receives updates and as you install and remove programs. Windows is especially prone to this, more so than macOS. The best bet with either is a complete wipe and reinstall of your computer; it&#039;s not a trivial task, but it can yield significant improvements (some say it&#039;s like getting a new computer), not just in terms of speed, but also stability.&lt;br /&gt;
&lt;br /&gt;
You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
==== Computer ====&lt;br /&gt;
&lt;br /&gt;
===== Bad Hardware =====&lt;br /&gt;
If your problems survive a wipe/reinstall, there could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== New Computer =====&lt;br /&gt;
We recognize that a new computer represents significant expense, but it can really help if your current hardware is old and slow.&lt;br /&gt;
&lt;br /&gt;
====== What Kind of Computer Should I Get? ======&lt;br /&gt;
While PubGizmo works fine on both PCs and Macs, it runs best on Macs. Not only are newer Macs faster in terms of price/performance than PCs, they are also much more reliable in terms of operating system integrity (see above) and hardware quality, as they require less support. They may cost more, but they are more rugged and last longer than PCs.&lt;br /&gt;
&lt;br /&gt;
FileMaker Pro, the software that runs PubGizmo, also performs better on Macs. We&#039;re not sure why. Even a base model [https://www.apple.com/ca/macbook-neo/ MacBook Neo] handles PubGizmo well (provided your internet speed is good too).&lt;br /&gt;
&lt;br /&gt;
== Are You Far Away? ==&lt;br /&gt;
Wait, are you away, connecting from somewhere other than your press&#039;s location? Your speed/freeze issue may be due to network latency caused by distance. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re in Frankfurt, you are far away, and it takes longer for data to travel between your location and the server.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=229</id>
		<title>Optimizing PubGizmo Speed</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=229"/>
		<updated>2026-10-12T18:10:44Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: /* Poor Network Connection */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Speed issues working in on PubGizmo can be frustrating, we want to help.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
and these can be broken down into three distinct areas:&lt;br /&gt;
&lt;br /&gt;
== Your Computer and Internet Connection Speeds ==&lt;br /&gt;
To interact with PubGizmo, data must travel through the internet between your computer and our servers, and then your computer must process that data.&lt;br /&gt;
&lt;br /&gt;
Both these factors have an enormous impact on the quality of your experience, and they are fully under your control and purview – only you can take steps to improve them. Here are steps to ensure you&#039;ve done everything you can to optimize your experience.&lt;br /&gt;
&lt;br /&gt;
=== Test Your Speed ===&lt;br /&gt;
The first step to determine if your setup is responsible for poor performance is to test it. You can do this by visiting the Home screen and clicking the About PubGizmo tab. At the bottom of the screen you&#039;ll see &#039;&#039;&#039;Connection Speed&#039;&#039;&#039; and a coloured indicator.&lt;br /&gt;
&lt;br /&gt;
* green: great speed, things will be smooth and quick&lt;br /&gt;
* amber: okay speed, could be better&lt;br /&gt;
* red: poor speed, working will be less than optimal&lt;br /&gt;
&lt;br /&gt;
Speed is tested when you login, but you can do an instant test by clicking the indicator. This allows you to change your circumstances and re-test to determine if that had an effect.&lt;br /&gt;
&lt;br /&gt;
=== Causes and Potential Fixes ===&lt;br /&gt;
&lt;br /&gt;
===== Poor Network Connection =====&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connectioncan impede network traffic. And &amp;quot;ping&amp;quot; matters too; a high ping number (30+) indicates high latency.&lt;br /&gt;
&lt;br /&gt;
Things to try to improve internet speed:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Get closer to the WiFi:&#039;&#039;&#039; This one&#039;s pretty easy: if your WiFi unit sits in the basement and you&#039;re on the third floor, get closer! The further your WiFi signal has to travel, the more walls and floors it must penetrate, the more devices (phones, other computers, TVs, microwave ovens, etc., which introduce radio wave interference), between your computer and the WiFi, the slower your connection.&lt;br /&gt;
# &#039;&#039;&#039;Wire up:&#039;&#039;&#039; If you have the option of connecting directly to your network using an ethernet cable, use that; cable is always going to be the fastest connection.&lt;br /&gt;
# &#039;&#039;&#039;Talk to your internet supplier:&#039;&#039;&#039; If your speed is no where near what you are paying for (e.g., you pay for 1GB speed and you are only getting 10% of that), there may be a problem with your internet. They can help troubleshoot.&lt;br /&gt;
&lt;br /&gt;
===== Slow Computer =====&lt;br /&gt;
Is your computer generally slow at other tasks? If yes, then one issue lies with your computer, either the hardware or your operating system. A number of factors can impede computer speed:&lt;br /&gt;
&lt;br /&gt;
===== Software/Operating System =====&lt;br /&gt;
Issues with your operating system (Windows or macOS) can slow down your computer. This kind of issue accrues over time as your computer receives updates and as you install and remove programs. Windows is especially prone to this kind of issue, more so than macOS. The best bet with either is a complete wipe and reinstall of your computer; it&#039;s not a trivial task, but it can yield significant improvements (some say it&#039;s like getting a new computer), not just in terms of speed, but also stability.&lt;br /&gt;
&lt;br /&gt;
You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
===== Hardware =====&lt;br /&gt;
If your problems survive a wipe/reinstall, it could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
And of course an old computer can be slow too.&lt;br /&gt;
&lt;br /&gt;
====== New Computer ======&lt;br /&gt;
We recognize that a new computer represents significant expense, but it can really help if your current hardware is old and slow.&lt;br /&gt;
&lt;br /&gt;
==== What Kind of Computer Should I Get? ====&lt;br /&gt;
While PubGizmo works fine on both PCs and Macs, it runs best on Macs. Not only are newer Macs faster in terms of price/performance than PCs, they are also much more reliable in terms of operating system integrity (see above) and hardware quality. They may cost more, but they are more rugged and last longer than PCs.&lt;br /&gt;
&lt;br /&gt;
FileMaker Pro, the software that runs PubGizmo, also performs better on Macs. We&#039;re not sure why. Even a base model MacBook Neo handles PubGizmo well (provided your internet speed is good too).&lt;br /&gt;
&lt;br /&gt;
== Complexities in the PubGizmo&#039;s Programming ==&lt;br /&gt;
&lt;br /&gt;
== The Internet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Computer Problem =====&lt;br /&gt;
Do other programs also crash? If yes, then the problem lies with your computer, either the hardware or your operating system. Windows is more prone to this kind of issue that macOS. The best bet with either is a complete wipe and reinstall of your computer; it&#039;s not a trivial task, but it can yield significant improvements, not just in terms of stability, but also computer performance. You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
If your problems survive a wipe/reinstall, it could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== FileMaker Pro Application Problem =====&lt;br /&gt;
If only FileMaker crashes, uninstall it, and reinstall. This will ensure that your installation of FileMaker is not corrupt.&lt;br /&gt;
&lt;br /&gt;
=== Freezes ===&lt;br /&gt;
&lt;br /&gt;
==== All Records, Operations ====&lt;br /&gt;
If you experience freezes (PubGizmo eventually responds), and it doesn&#039;t seem to matter what you&#039;re looking at (e.g., just a basic Contact record), something is impeding the exchange of information between your computer and the data on the server. This could be:&lt;br /&gt;
&lt;br /&gt;
===== Poor Network Connection =====&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connection (e.g., on WiFi, but weak signal – get closer to the WiFi router!) can impede network traffic. If you rectify these issues, things may improve.&lt;br /&gt;
&lt;br /&gt;
====== Are You Far Away? ======&lt;br /&gt;
Wait, are you away, connecting from somewhere other than your press&#039;s location? Your speed/freeze issue may be due to network latency caused by distance. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re in Frankfurt, you are far away, and it takes longer for data to travel between your location and the server.&lt;br /&gt;
&lt;br /&gt;
===== Slow Computer =====&lt;br /&gt;
An old computer or a computer problem (corrupt OS, see above under &amp;quot;Computer Problem&amp;quot;) can impede access to PubGizmo.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=228</id>
		<title>Optimizing PubGizmo Speed</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=228"/>
		<updated>2026-10-12T17:38:48Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Speed issues working in on PubGizmo can be frustrating, we want to help.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
and these can be broken down into three distinct areas:&lt;br /&gt;
&lt;br /&gt;
== Your Computer and Internet Connection Speeds ==&lt;br /&gt;
To interact with PubGizmo, data must travel through the internet between your computer and our servers, and then your computer must process that data.&lt;br /&gt;
&lt;br /&gt;
Both these factors have an enormous impact on the quality of your experience, and they are fully under your control and purview – only you can take steps to improve them. Here are steps to ensure you&#039;ve done everything you can to optimize your experience.&lt;br /&gt;
&lt;br /&gt;
=== Test Your Speed ===&lt;br /&gt;
The first step to determine if your setup is responsible for poor performance is to test it. You can do this by visiting the Home screen and clicking the About PubGizmo tab. At the bottom of the screen you&#039;ll see &#039;&#039;&#039;Connection Speed&#039;&#039;&#039; and a coloured indicator.&lt;br /&gt;
&lt;br /&gt;
* green: great speed, things will be smooth and quick&lt;br /&gt;
* amber: okay speed, could be better&lt;br /&gt;
* red: poor speed, working will be less than optimal&lt;br /&gt;
&lt;br /&gt;
Speed is tested when you login, but you can do an instant test by clicking the indicator. This allows you to change your circumstances and re-test to determine if that had an effect.&lt;br /&gt;
&lt;br /&gt;
=== Causes and Potential Fixes ===&lt;br /&gt;
&lt;br /&gt;
===== Poor Network Connection =====&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connectioncan impede network traffic.&lt;br /&gt;
&lt;br /&gt;
Here are things to try to improve internet speed:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;Get closer to the WiFi:&#039;&#039;&#039; This one&#039;s pretty easy: if your WiFi unit sits in the basement and you&#039;re on the third floor, get closer! The further your WiFi signal has to travel, the more walls and floors it must penetrate, the more devices (phones, other computers, TVs, microwave ovens, etc.), between your computer and the WiFi, the slower your connection.&lt;br /&gt;
# &#039;&#039;&#039;Wire up:&#039;&#039;&#039; If you have the option of connecting directly to your network using an ethernet cable, use that; cable is always going to be the fastest connection.&lt;br /&gt;
# &#039;&#039;&#039;Talk to your internet supplier:&#039;&#039;&#039; If your speed is no where near what you are paying for (e.g., you pay for 1GB speed and you are only getting 10% of that), there may be a problem with your internet. They can help troubleshoot.&lt;br /&gt;
&lt;br /&gt;
===== Slow Computer =====&lt;br /&gt;
A slow computer can harm your PubGizmo experience too.&lt;br /&gt;
&lt;br /&gt;
Software/Operating System&lt;br /&gt;
&lt;br /&gt;
Is your computer generally slow at other tasks? If yes, then the issue lies with your computer, either the hardware or your operating system. Windows is especially prone to this kind of issue, less so than macOS. The best bet with either is a complete wipe and reinstall of your computer; it&#039;s not a trivial task, but it can yield significant improvements, not just in terms of stability, but also computer performance. You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
If your problems survive a wipe/reinstall, it could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
== Complexities in the PubGizmo&#039;s Programming ==&lt;br /&gt;
&lt;br /&gt;
== The Internet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Computer Problem =====&lt;br /&gt;
Do other programs also crash? If yes, then the problem lies with your computer, either the hardware or your operating system. Windows is more prone to this kind of issue that macOS. The best bet with either is a complete wipe and reinstall of your computer; it&#039;s not a trivial task, but it can yield significant improvements, not just in terms of stability, but also computer performance. You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
If your problems survive a wipe/reinstall, it could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== FileMaker Pro Application Problem =====&lt;br /&gt;
If only FileMaker crashes, uninstall it, and reinstall. This will ensure that your installation of FileMaker is not corrupt.&lt;br /&gt;
&lt;br /&gt;
=== Freezes ===&lt;br /&gt;
&lt;br /&gt;
==== All Records, Operations ====&lt;br /&gt;
If you experience freezes (PubGizmo eventually responds), and it doesn&#039;t seem to matter what you&#039;re looking at (e.g., just a basic Contact record), something is impeding the exchange of information between your computer and the data on the server. This could be:&lt;br /&gt;
&lt;br /&gt;
===== Poor Network Connection =====&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connection (e.g., on WiFi, but weak signal – get closer to the WiFi router!) can impede network traffic. If you rectify these issues, things may improve.&lt;br /&gt;
&lt;br /&gt;
====== Are You Far Away? ======&lt;br /&gt;
Wait, are you away, connecting from somewhere other than your press&#039;s location? Your speed/freeze issue may be due to network latency caused by distance. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re in Frankfurt, you are far away, and it takes longer for data to travel between your location and the server.&lt;br /&gt;
&lt;br /&gt;
===== Slow Computer =====&lt;br /&gt;
An old computer or a computer problem (corrupt OS, see above under &amp;quot;Computer Problem&amp;quot;) can impede access to PubGizmo.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=227</id>
		<title>Optimizing PubGizmo Speed</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Optimizing_PubGizmo_Speed&amp;diff=227"/>
		<updated>2026-10-12T17:26:21Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: Created page with &amp;quot;Speed issues working in on PubGizmo can be frustrating, we want to help.    and these can be broken down into three distinct areas:  == Your Computer and Internet Connection Speeds == To interact with PubGizmo, data must travel through the internet between your computer and our servers, and then your computer must process that data.  Both these factors have an enormous impact on the quality of your experience, and they are fully under your control and purview – only yo...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Speed issues working in on PubGizmo can be frustrating, we want to help.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
and these can be broken down into three distinct areas:&lt;br /&gt;
&lt;br /&gt;
== Your Computer and Internet Connection Speeds ==&lt;br /&gt;
To interact with PubGizmo, data must travel through the internet between your computer and our servers, and then your computer must process that data.&lt;br /&gt;
&lt;br /&gt;
Both these factors have an enormous impact on the quality of your experience, and they are fully under your control and purview – only you can take steps to improve them. Here are steps to ensure you&#039;ve done everything you can to optimize your experience.&lt;br /&gt;
&lt;br /&gt;
=== Test Your Speed ===&lt;br /&gt;
The first step to determine if your setup is responsible for poor performance is to test it. You can do this by visiting the Home screen and clicking the About PubGizmo tab. At the bottom of the screen you&#039;ll see &#039;&#039;&#039;Connection Speed&#039;&#039;&#039; and a coloured indicator.&lt;br /&gt;
&lt;br /&gt;
* green: great speed, things will be smooth and quick&lt;br /&gt;
* amber: okay speed, could be better&lt;br /&gt;
* red: poor speed, working will be less than optimal&lt;br /&gt;
&lt;br /&gt;
Speed is tested when you login, but you can do an instant test by clicking the indicator. This allows you to change your circumstances (e.g., move closer to the WiFi router) and test to determine if that had an effect.&lt;br /&gt;
&lt;br /&gt;
== Complexities in the PubGizmo&#039;s Programming ==&lt;br /&gt;
&lt;br /&gt;
== The Internet ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===== Computer Problem =====&lt;br /&gt;
Do other programs also crash? If yes, then the problem lies with your computer, either the hardware or your operating system. Windows is more prone to this kind of issue that macOS. The best bet with either is a complete wipe and reinstall of your computer; it&#039;s not a trivial task, but it can yield significant improvements, not just in terms of stability, but also computer performance. You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
If your problems survive a wipe/reinstall, it could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== FileMaker Pro Application Problem =====&lt;br /&gt;
If only FileMaker crashes, uninstall it, and reinstall. This will ensure that your installation of FileMaker is not corrupt.&lt;br /&gt;
&lt;br /&gt;
=== Freezes ===&lt;br /&gt;
&lt;br /&gt;
==== All Records, Operations ====&lt;br /&gt;
If you experience freezes (PubGizmo eventually responds), and it doesn&#039;t seem to matter what you&#039;re looking at (e.g., just a basic Contact record), something is impeding the exchange of information between your computer and the data on the server. This could be:&lt;br /&gt;
&lt;br /&gt;
===== Poor Network Connection =====&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net/ speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connection (e.g., on WiFi, but weak signal – get closer to the WiFi router!) can impede network traffic. If you rectify these issues, things may improve.&lt;br /&gt;
&lt;br /&gt;
====== Are You Far Away? ======&lt;br /&gt;
Wait, are you away, connecting from somewhere other than your press&#039;s location? Your speed/freeze issue may be due to network latency caused by distance. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re in Frankfurt, you are far away, and it takes longer for data to travel between your location and the server.&lt;br /&gt;
&lt;br /&gt;
===== Slow Computer =====&lt;br /&gt;
An old computer or a computer problem (corrupt OS, see above under &amp;quot;Computer Problem&amp;quot;) can impede access to PubGizmo.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Handling_Slow_Access_and_Crashes&amp;diff=226</id>
		<title>Handling Slow Access and Crashes</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Handling_Slow_Access_and_Crashes&amp;diff=226"/>
		<updated>2026-10-12T17:03:09Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Help! PubGizmo/FileMaker Pro is Slow/Crashing! ==&lt;br /&gt;
Both slowness and crashing are frustrating occurrences, and we are sorry for these experiences. There can be a variety of causes, some of which are us, some of which are you, and some to chalk up to the vagaries of computers and networks.&lt;br /&gt;
&lt;br /&gt;
== Background: How PubGizmo Works ==&lt;br /&gt;
As a sidebar, it helps to isolate your issue if you understand how PubGizmo operates. This is somewhat technical, so you can skip it if you just want suggestions to help with your problem.&lt;br /&gt;
&lt;br /&gt;
=== PubGizmo Runs Within FileMaker Pro ===&lt;br /&gt;
PubGizmo runs under FileMaker Pro in somewhat the same way a Word document runs under Microsoft Word, except that PubGizmo&#039;s data is located on a server (computer) in the cloud (connected to the internet), which in a way makes it more like a Google Sheet (which is why multiple users can use PubGizmo at the same time).&lt;br /&gt;
&lt;br /&gt;
=== Getting Data and Making Changes ===&lt;br /&gt;
You use FileMaker Pro on your computer to access it on the server where it is hosted, and data moves back and forth between your computer and the server. For example, when you open a Title record, PubGizmo tells FileMaker Pro to communicate to FileMaker Server in the cloud to fetch all the Title data, and display it for you. When you make a change, e.g., you add a subtitle or keyword, the data gets sent back to the server and written to the record. Changes are immediate.&lt;br /&gt;
&lt;br /&gt;
==== Moving Data Takes Time ====&lt;br /&gt;
It&#039;s important to understand that moving data takes time. The more data you&#039;re moving, the longer it takes.&lt;br /&gt;
&lt;br /&gt;
==== Computation Adds Complexity ====&lt;br /&gt;
If the data requires computation, like calculating royalty amounts, that increases the time required, especially if you are running a complex calculation, such as escalation.&lt;br /&gt;
&lt;br /&gt;
==== &amp;quot;Expense&amp;quot; ====&lt;br /&gt;
We talk about the factors of data volume and computational strain in terms of &amp;quot;expense.&amp;quot; It is &#039;&#039;expensive&#039;&#039;, in terms of computational power and data mobility, to run a hard calc on a ton of data.&lt;br /&gt;
&lt;br /&gt;
Imagine a briskly selling book, with many sales records. Each record is a piece of data, and when you open a Royalty Statement, all that data has to be collated, and then the royalty calculations must be run. A book with a 1000 sales involves 10 times more data than one with 100 sales.&lt;br /&gt;
&lt;br /&gt;
Add a complex calculation, specifically escalation, and it&#039;s a recipe for slow access, so slow, in fact, that it may appear to be a crash (when really it&#039;s a freeze, which will respond, given time – see below).&lt;br /&gt;
&lt;br /&gt;
=== Factors That Affect Speed ===&lt;br /&gt;
Many factors affect the speed of your PubGizmo experience, some of which are controllable, and some which are not:&lt;br /&gt;
&lt;br /&gt;
* volume of data being accessed and moved&lt;br /&gt;
* complexity of calculations&lt;br /&gt;
* your internet speed (provider, and also your connection to your router – bad WiFi can slow you down)&lt;br /&gt;
* your distance from the server (i.e., distance from either Toronto or Vancouver, depending on which server your solution is hosted)&lt;br /&gt;
* your computer&#039;s speed (physically, and depending on the state of its operating system) &lt;br /&gt;
* PubGizmo programming efficiency – how PG is built to handle data. We are making frequent improvements by running calculations on the server (which is quicker, since data need not transit between the server and your computer; an example is import processing – we run this on the server, which is what is happening when you see that an import is &amp;quot;PENDING&amp;quot;), and by caching and pre-calculating data.&lt;br /&gt;
&lt;br /&gt;
== Is it a Crash or a Freeze? ==&lt;br /&gt;
We should distinguish between a crash and a freeze. These are different events, and require different handling.&lt;br /&gt;
&lt;br /&gt;
=== Crash ===&lt;br /&gt;
A crash means FileMaker Pro has quit. All windows have disappeared from the screen. There&#039;s no spinning beachball, no hourglass.&lt;br /&gt;
&lt;br /&gt;
On a Mac, you&#039;ll usually receive a dialogue that tells you FileMaker Pro has crashed, with a few options: re-open, report the problem to Apple, or cancel. If you look at the [https://support.apple.com/en-ca/guide/mac-help/mh35859/mac Dock], the icon is gone, or, if you keep the icon in the Dock, there&#039;s no black dot below the icon to indicate it&#039;s running.&lt;br /&gt;
&lt;br /&gt;
On Windows, it no longer appears on the [https://support.microsoft.com/en-us/windows/how-to-use-the-taskbar-in-windows-0657a50f-0cc7-dbfd-ae6b-05020b195b07#:~:text=Typically%2C%20the%20taskbar%20is%20at,the%20top%20of%20the%20desktop. Taskbar]. If you look at the [[wikihow:Open-Windows-Task-Manager#:~:text=Press%20Ctrl%20%2B%20Shift%20%2B%20Esc%20to,and%20select%20%22Task%20Manager.%22|Task Manager]], FileMaker does not appear. Note that a message indicating FileMaker has stopped responding could be crash, but it could also be a freeze, per below.&lt;br /&gt;
&lt;br /&gt;
=== Freeze ===&lt;br /&gt;
If FileMaker Pro is still running but unresponsive, it has frozen or stalled. There&#039;s a good chance it&#039;s still alive, but it has stalled, or is hesitating, possibly because it is:&lt;br /&gt;
&lt;br /&gt;
# running a complex calculation&lt;br /&gt;
# attempting to fetch a large volume of data from the server to display, or to calculate&lt;br /&gt;
# struggling to negotiate a bad network connection&lt;br /&gt;
# impeded by your computer&#039;s speed&lt;br /&gt;
# struggling with a heavy server load (unlikely)&lt;br /&gt;
&lt;br /&gt;
==== Wait it Out ====&lt;br /&gt;
In this situation, you may just have to wait for PG to yield data and update – give it a chance to complete its processes, and your results will appear. It can take many seconds, or even many minutes, in extreme cases, to respond. Take a breath, take a break, make a cup of tea.&lt;br /&gt;
&lt;br /&gt;
===== Data Volume and/or Complexity =====&lt;br /&gt;
Frequently, the nature of the operation you are trying to perform, or the volume or complexity of data you are trying to access, will help you understand why the freeze is happening. &lt;br /&gt;
&lt;br /&gt;
For reference, these operations will be slow: &lt;br /&gt;
&lt;br /&gt;
* Opening royalty statements with escalation and/or lots of sales records&lt;br /&gt;
* Using the Reporter with many of record selected, or covering a large span of time&lt;br /&gt;
* Viewing records in List View, especially Royalties if the amount column is toggled on (PG must calculate royalties for all the statements in the view, which invokes hundreds or even thousands of calculations).&lt;br /&gt;
If some records are predictably quick, and others are predictably slow, e.g., &amp;quot;I know when I open this Royalty Statement it always takes a while,&amp;quot; you know that things are operating normally (even if waiting sucks), because there&#039;s a consistency to the slowness.&lt;br /&gt;
&lt;br /&gt;
== What to Do ==&lt;br /&gt;
&lt;br /&gt;
=== Crashes ===&lt;br /&gt;
&lt;br /&gt;
==== Isolated ====&lt;br /&gt;
An isolated crash can be dismissed as a one-off. Computers crash, software crashes – we don&#039;t always know why. Just re-open FileMaker, connect to PubGizmo, and continue where you left off.&lt;br /&gt;
&lt;br /&gt;
==== Chronic ====&lt;br /&gt;
If you are suffering chronic, not infrequent crashes, something more serious is going on. There are a host of possible causes, and solutions:&lt;br /&gt;
&lt;br /&gt;
===== Computer Problem =====&lt;br /&gt;
Do other programs also crash? If yes, then the problem lies with your computer, either the hardware or your operating system. Windows is more prone to this kind of issue that macOS. The best bet with either is a complete wipe and reinstall of your computer; it&#039;s not a trivial task, but it can yield significant improvements, not just in terms of stability, but also computer performance. You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
If your problems survive a wipe/reinstall, it could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== FileMaker Pro Application Problem =====&lt;br /&gt;
If only FileMaker crashes, uninstall it, and reinstall. This will ensure that your installation of FileMaker is not corrupt.&lt;br /&gt;
&lt;br /&gt;
=== Freezes ===&lt;br /&gt;
&lt;br /&gt;
==== All Records, Operations ====&lt;br /&gt;
If you experience freezes (PubGizmo eventually responds), and it doesn&#039;t seem to matter what you&#039;re looking at (e.g., just a basic Contact record), something is impeding the exchange of information between your computer and the data on the server. This could be:&lt;br /&gt;
&lt;br /&gt;
===== Poor Network Connection =====&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connection (e.g., on WiFi, but weak signal – get closer to the WiFi router!) can impede network traffic. If you rectify these issues, things may improve.&lt;br /&gt;
&lt;br /&gt;
====== Are You Far Away? ======&lt;br /&gt;
Wait, are you away, connecting from somewhere other than your press&#039;s location? Your speed/freeze issue may be due to network latency caused by distance. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re in Frankfurt, you are far away, and it takes longer for data to travel between your location and the server.&lt;br /&gt;
&lt;br /&gt;
===== Slow Computer =====&lt;br /&gt;
An old computer or a computer problem (corrupt OS, see above under &amp;quot;Computer Problem&amp;quot;) can impede access to PubGizmo.&lt;br /&gt;
&lt;br /&gt;
==== Some Records or Reports ====&lt;br /&gt;
Big sellers, or contracts with complicated clauses (escalation), or, worse-still, combinations of the two, will be slow to render. Try to limit your access to these records.&lt;br /&gt;
&lt;br /&gt;
== Improvements Coming ==&lt;br /&gt;
We have in our PubGizmo development plan a big update in the works that will cache sales data, instead of reading each sales record individually. This will yield a major performance improvement. Stay turned for updates.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=225</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=225"/>
		<updated>2026-10-12T16:58:39Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. Running royalties is a multi-step process:&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Ensure the last period&#039;s Payment records were generated, and create them if not.&lt;br /&gt;
# Set your Minimum Royalty Payment (payout threshold) in Admin.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages: one for contractees and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statements attached.&lt;br /&gt;
# Personalize those messages as you like and send them.&lt;br /&gt;
# Generate Payment records to lock in the amounts for the next period.&lt;br /&gt;
# Optionally, generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
The following details each of the steps above.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts Are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means importing all your sales sheets, as well as manually entering any sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sales sheet containing sales from a royalty period that is imported after that period&#039;s royalty run is complete will never be counted, even in the next period, because PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contracts/Statements Are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you to flag active contracts, to determine whether they are computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for the selected period (see below), the status of the Calc Royalty flag persists through all royalty runs; that is, contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
* on the Contract itself, at the upper right;&lt;br /&gt;
* in Royalty form view;&lt;br /&gt;
* in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can list statements by their Calc Royalty status by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Ensure Payment Records from Last Period Have Been Generated ==&lt;br /&gt;
If this is not your first PubGizmo royalty run, make sure you have generated Payment records for the last period. These are necessary to bring forward important values such as Advance Remaining, reserve on returns, and carry-forward amounts for statements you chose not to pay.&lt;br /&gt;
&lt;br /&gt;
If you forgot to do it last time, you can do so now:&lt;br /&gt;
&lt;br /&gt;
# Select the previous royalty period.&lt;br /&gt;
# Open the Bulk Royalty Actions popover.&lt;br /&gt;
# Click Create Payment Records.&lt;br /&gt;
&lt;br /&gt;
After that, set your current royalty period and proceed.&lt;br /&gt;
&lt;br /&gt;
== Flag Statements to Pay This Period ==&lt;br /&gt;
For each royalty period, you determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where those values will be added to (or subtracted from) those statements. Unlike the Calc Royalty checkbox, which persists until you change it, the statements you will actually pay vary each period and must be set each period. By default, when you start a new period, none of the statements are flagged to pay out. You decide which ones get paid and which ones will have their values carried forward to the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]&lt;br /&gt;
You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header above the right-hand column. That toggles the display of the amounts. This setting is off by default because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, described below under Bulk Royalty Actions.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure that you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set Your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments to contractees owed less than a specific amount. For example, you can hold payments until the next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value to $0 and use the bulk process described below, all Calc Royalty statements will be set to pay out.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
* one for the contractee (author, translator, editor, etc.);&lt;br /&gt;
* one for the literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is composed. The subject and body text of these messages are set in Admin &amp;gt; Bulk Mail Templates tab. The templates include a number of merge tags, each enclosed in angle brackets (&amp;amp;#x3C; and &amp;amp;#x3E;), into which relevant data is substituted when the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;Year&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; The royalty year, if your press uses the calendar year as its statement period; otherwise, the start and end dates of the royalty period.&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;Title&amp;gt;&amp;lt;/code&amp;gt; The book&#039;s title, or titles if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;GreetingName&amp;gt;&amp;lt;/code&amp;gt; The value in the Correspondence Name field on the recipient&#039;s Contact record (defaults to the Contact&#039;s first name but can be edited). For Organization contractees, the system will attempt to use the name of the Organization&#039;s representative, if defined on the Contract; otherwise, it will use the Organization&#039;s name.&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;Artist&amp;gt;&amp;lt;/code&amp;gt; The contractee&#039;s first and last name. Note: in the agent email, this is replaced with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;Address&amp;gt;&amp;lt;/code&amp;gt; The recipient&#039;s mailing address on one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents with Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements (that is, gathers all relevant statements into a single PDF) and attaches them to one email message under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* the author/contractee has multiple active contracts (a summary page of all statements is included);&lt;br /&gt;
* the literary agent is the agent of record on multiple active contracts.&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk: processes that might have taken days or weeks can be accomplished in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
Bulk actions are executed in a popover accessed with the royalties button (a crown – get it?) in the list view of the Royalties module.[[File:Screenshot_2026-10-01_at_16.31.08.png|none|thumb|631x631px]]Actions are performed for the current royalty period on the Found Set (the records currently showing in the list), and only on those records in the Found Set that have Calc Royalty checked. Statistics at the upper right of the popover describe the composition of your total and current Found Set of records and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure the Found Set that the royalty buttons will run against:&lt;br /&gt;
&lt;br /&gt;
* click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements;&lt;br /&gt;
* load a Snapshot of Royalty records you created previously (see Tags &amp;amp; Snapshots for how to create Snapshots);&lt;br /&gt;
* close the Bulk Royalty Actions popover and use the Find box with criteria to generate a Found Set of the records you want to process;&lt;br /&gt;
* close the Bulk Royalty Actions popover, tag the records, and show only the tagged records you want to process (see Tags &amp;amp; Snapshots for how to tag records and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
The processes are typically run in order. However, you can choose to perform the actions on a subset of records, then move on to another set and start again from the beginning of the process. This is handy if you are working with a large volume of statements and/or working as a team where different users handle different sets of records.&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The Flag Eligible for Payout button automatically flags statements for payout in the selected period when both of the following are true:&lt;br /&gt;
&lt;br /&gt;
* Calc Royalty is checked;&lt;br /&gt;
* the total amount payable across all contracts for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
==== Payment Total Is for All Statements ====&lt;br /&gt;
Because the purpose of the payout threshold is to avoid making payments to contractees below a specified amount – no one wants to write and mail a cheque for $1.87 – PubGizmo considers &#039;&#039;all statements for each contractee&#039;&#039; when computing whether the total exceeds the threshold.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* The Minimum Royalty Payment is set to $25.&lt;br /&gt;
* An author has three statements with the following amounts owing: $10, $12, and $5.&lt;br /&gt;
&lt;br /&gt;
In this case, although no single statement reaches $25 by itself, the bulk process will flag all three statements because the total amount to pay that author is $27, which is greater than your $25 threshold. You will send those three statements (which, when sent in bulk, will be bundled into one PDF with a summary page), along with a payment of $27.&lt;br /&gt;
&lt;br /&gt;
=== 2. PDF of Royalty Statements ===&lt;br /&gt;
Most presses have found that the best way to proofread statements before sending them is to generate a PDF, or a series of PDFs, containing the statements and to work from those.&lt;br /&gt;
&lt;br /&gt;
Click this button to generate a PDF on your Desktop containing the Calc Royalty statements in the Found Set.&lt;br /&gt;
&lt;br /&gt;
=== 3. Email Royalty Statements ===&lt;br /&gt;
Click this button to have PubGizmo generate draft email messages in your default email software. Your default email program must be Apple Mail (Mail) if you are on macOS, or Outlook if you use Windows (let us know if you use something else). You can customize each email message as you like and send each one individually.&lt;br /&gt;
&lt;br /&gt;
Every Contact, whether they have their own individual contract or share a single contract for a Title, will receive an email with the relevant statement(s) attached. This includes contractees who are the only signatory to a contract, as well as contractees who share a contract with other contractees. In the latter case, each statement will show the full earnings for the contract, plus the contractee&#039;s own share as a percentage and an amount, as specified in their contract.&lt;br /&gt;
&lt;br /&gt;
Contractees, whether they are Contacts or Organizations, will receive the following in their PDF:&lt;br /&gt;
&lt;br /&gt;
==== Contacts ====&lt;br /&gt;
&lt;br /&gt;
* all their own Calc Royalty statements in the current Found Set;&lt;br /&gt;
* a summary page of all their Calc Royalty statements (including those not in the Found Set), if the contractee has more than one Calc Royalty statement.&lt;br /&gt;
&lt;br /&gt;
==== Organizations ====&lt;br /&gt;
&lt;br /&gt;
* all relevant Calc Royalty statements in the current Found Set;&lt;br /&gt;
* a summary page of statements (including those not in the Found Set), if the contractee has more than one Calc Royalty statement.&lt;br /&gt;
&lt;br /&gt;
==== Literary Agents ====&lt;br /&gt;
The process also generates draft emails to the agent of record on each statement, with the relevant statements attached.&lt;br /&gt;
&lt;br /&gt;
=== 4. Create Payment Records ===&lt;br /&gt;
This essential step &amp;quot;locks in&amp;quot; amounts, such as Advance Remaining and carry-forward values, which inform the calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important notes:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* All of the steps above must be complete (all sales records imported, appropriate records set to calculate and pay out, statements fully proofed) before you perform this step. If you change anything for the current period, you will have to create the Payment records again, although a single changed statement can receive a new Payment record by opening the statement and clicking the &amp;quot;$&amp;quot; button.&lt;br /&gt;
* This step is performed on all Calc Royalty records, regardless of the Found Set. Save it for the very end of your royalty process to ensure the values are final.&lt;br /&gt;
* You must complete this step for each royalty period before running the next one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period&#039;s results will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
* If you have previously created Payment records and try to do so again, PubGizmo will warn you that records already exist and will be deleted and replaced. This is fine: the new Payment records will be created using the latest royalty data.&lt;br /&gt;
&lt;br /&gt;
=== 5. CSV Export ===&lt;br /&gt;
Click this button to generate a CSV file (a spreadsheet you can open in Excel) on your Desktop that summarizes the statements. You can give this file to your accountant.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; this export is generic and may or may not be suitable for import into your accounting software. If there is a format that works better for you, let us know and we can discuss building it. Be sure to tell us which software you use, and provide a sample CSV or Excel file showing what a useful import would look like.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=224</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=224"/>
		<updated>2026-10-11T18:56:49Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: After Claude edit&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. Running royalties is a multi-step process:&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Ensure the last period&#039;s Payment records were generated, and create them if not.&lt;br /&gt;
# Set your Minimum Royalty Payment (payout threshold) in Admin.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages: one for contractees and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statements attached.&lt;br /&gt;
# Personalize those messages as you like and send them.&lt;br /&gt;
# Generate Payment records to lock in the amounts for the next period.&lt;br /&gt;
# Optionally, generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts Are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means importing all your sales sheets, as well as manually entering any sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sales sheet containing sales from a royalty period that is imported after that period&#039;s royalty run is complete will never be counted, even in the next period, because PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contracts/Statements Are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you to flag active contracts, to determine whether they are computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for the selected period (see below), the status of the Calc Royalty flag persists through all royalty runs; that is, contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
* on the Contract itself, at the upper right;&lt;br /&gt;
* in Royalty form view;&lt;br /&gt;
* in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can list statements by their Calc Royalty status by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Ensure Payment Records from Last Period Have Been Generated ==&lt;br /&gt;
If this is not your first PubGizmo royalty run, make sure you have generated Payment records for the last period. These are necessary to bring forward important values such as Advance Remaining, reserve on returns, and carry-forward amounts for statements you chose not to pay.&lt;br /&gt;
&lt;br /&gt;
If you forgot to do it last time, you can do so now:&lt;br /&gt;
&lt;br /&gt;
# Select the previous royalty period.&lt;br /&gt;
# Open the Bulk Royalty Actions popover.&lt;br /&gt;
# Click Create Payment Records.&lt;br /&gt;
&lt;br /&gt;
After that, set your current royalty period and proceed.&lt;br /&gt;
&lt;br /&gt;
== Flag Statements to Pay This Period ==&lt;br /&gt;
For each royalty period, you determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where those values will be added to (or subtracted from) those statements. Unlike the Calc Royalty checkbox, which persists until you change it, the statements you will actually pay vary each period and must be set each period. By default, when you start a new period, none of the statements are flagged to pay out. You decide which ones get paid and which ones will have their values carried forward to the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]&lt;br /&gt;
You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header above the right-hand column. That toggles the display of the amounts. This setting is off by default because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, described below under Bulk Royalty Actions.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure that you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set Your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments to contractees owed less than a specific amount. For example, you can hold payments until the next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value to $0 and use the bulk process described below, all Calc Royalty statements will be set to pay out.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
* one for the contractee (author, translator, editor, etc.);&lt;br /&gt;
* one for the literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is composed. The subject and body text of these messages are set in Admin &amp;gt; Bulk Mail Templates tab. The templates include a number of merge tags, each enclosed in angle brackets (&amp;amp;#x3C; and &amp;amp;#x3E;), into which relevant data is substituted when the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;Year&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; The royalty year, if your press uses the calendar year as its statement period; otherwise, the start and end dates of the royalty period.&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;Title&amp;gt;&amp;lt;/code&amp;gt; The book&#039;s title, or titles if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;GreetingName&amp;gt;&amp;lt;/code&amp;gt; The value in the Correspondence Name field on the recipient&#039;s Contact record (defaults to the Contact&#039;s first name but can be edited). For Organization contractees, the system will attempt to use the name of the Organization&#039;s representative, if defined on the Contract; otherwise, it will use the Organization&#039;s name.&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;Artist&amp;gt;&amp;lt;/code&amp;gt; The contractee&#039;s first and last name. Note: in the agent email, this is replaced with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;Address&amp;gt;&amp;lt;/code&amp;gt; The recipient&#039;s mailing address on one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents with Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements (that is, gathers all relevant statements into a single PDF) and attaches them to one email message under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* the author/contractee has multiple active contracts (a summary page of all statements is included);&lt;br /&gt;
* the literary agent is the agent of record on multiple active contracts.&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk: processes that might have taken days or weeks can be accomplished in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
Bulk actions are executed in a popover accessed with the royalties button (a crown – get it?) in the list view of the Royalties module.[[File:Screenshot_2026-10-01_at_16.31.08.png|none|thumb|631x631px]]Actions are performed for the current royalty period on the Found Set (the records currently showing in the list), and only on those records in the Found Set that have Calc Royalty checked. Statistics at the upper right of the popover describe the composition of your total and current Found Set of records and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure the Found Set that the royalty buttons will run against:&lt;br /&gt;
&lt;br /&gt;
* click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements;&lt;br /&gt;
* load a Snapshot of Royalty records you created previously (see Tags &amp;amp; Snapshots for how to create Snapshots);&lt;br /&gt;
* close the Bulk Royalty Actions popover and use the Find box with criteria to generate a Found Set of the records you want to process;&lt;br /&gt;
* close the Bulk Royalty Actions popover, tag the records, and show only the tagged records you want to process (see Tags &amp;amp; Snapshots for how to tag records and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
The processes are typically run in order. However, you can choose to perform the actions on a subset of records, then move on to another set and start again from the beginning of the process. This is handy if you are working with a large volume of statements and/or working as a team where different users handle different sets of records.&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The Flag Eligible for Payout button automatically flags statements for payout in the selected period when both of the following are true:&lt;br /&gt;
&lt;br /&gt;
* Calc Royalty is checked;&lt;br /&gt;
* the total amount payable across all contracts for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
==== Payment Total Is for All Statements ====&lt;br /&gt;
Because the purpose of the payout threshold is to avoid making payments to contractees below a specified amount – no one wants to write and mail a cheque for $1.87 – PubGizmo considers &#039;&#039;all statements for each contractee&#039;&#039; when computing whether the total exceeds the threshold.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* The Minimum Royalty Payment is set to $25.&lt;br /&gt;
* An author has three statements with the following amounts owing: $10, $12, and $5.&lt;br /&gt;
&lt;br /&gt;
In this case, although no single statement reaches $25 by itself, the bulk process will flag all three statements because the total amount to pay that author is $27, which is greater than your $25 threshold. You will send those three statements (which, when sent in bulk, will be bundled into one PDF with a summary page), along with a payment of $27.&lt;br /&gt;
&lt;br /&gt;
=== 2. PDF of Royalty Statements ===&lt;br /&gt;
Most presses have found that the best way to proofread statements before sending them is to generate a PDF, or a series of PDFs, containing the statements and to work from those.&lt;br /&gt;
&lt;br /&gt;
Click this button to generate a PDF on your Desktop containing the Calc Royalty statements in the Found Set.&lt;br /&gt;
&lt;br /&gt;
=== 3. Email Royalty Statements ===&lt;br /&gt;
Click this button to have PubGizmo generate draft email messages in your default email software. Your default email program must be Apple Mail (Mail) if you are on macOS, or Outlook if you use Windows (let us know if you use something else). You can customize each email message as you like and send each one individually.&lt;br /&gt;
&lt;br /&gt;
Every Contact, whether they have their own individual contract or share a single contract for a Title, will receive an email with the relevant statement(s) attached. This includes contractees who are the only signatory to a contract, as well as contractees who share a contract with other contractees. In the latter case, each statement will show the full earnings for the contract, plus the contractee&#039;s own share as a percentage and an amount, as specified in their contract.&lt;br /&gt;
&lt;br /&gt;
Contractees, whether they are Contacts or Organizations, will receive the following in their PDF:&lt;br /&gt;
&lt;br /&gt;
==== Contacts ====&lt;br /&gt;
&lt;br /&gt;
* all their own Calc Royalty statements in the current Found Set;&lt;br /&gt;
* a summary page of all their Calc Royalty statements (including those not in the Found Set), if the contractee has more than one Calc Royalty statement.&lt;br /&gt;
&lt;br /&gt;
==== Organizations ====&lt;br /&gt;
&lt;br /&gt;
* all relevant Calc Royalty statements in the current Found Set;&lt;br /&gt;
* a summary page of statements (including those not in the Found Set), if the contractee has more than one Calc Royalty statement.&lt;br /&gt;
&lt;br /&gt;
==== Literary Agents ====&lt;br /&gt;
The process also generates draft emails to the agent of record on each statement, with the relevant statements attached.&lt;br /&gt;
&lt;br /&gt;
=== 4. Create Payment Records ===&lt;br /&gt;
This essential step &amp;quot;locks in&amp;quot; amounts, such as Advance Remaining and carry-forward values, which inform the calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important notes:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* All of the steps above must be complete (all sales records imported, appropriate records set to calculate and pay out, statements fully proofed) before you perform this step. If you change anything for the current period, you will have to create the Payment records again, although a single changed statement can receive a new Payment record by opening the statement and clicking the &amp;quot;$&amp;quot; button.&lt;br /&gt;
* This step is performed on all Calc Royalty records, regardless of the Found Set. Save it for the very end of your royalty process to ensure the values are final.&lt;br /&gt;
* You must complete this step for each royalty period before running the next one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period&#039;s results will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
* If you have previously created Payment records and try to do so again, PubGizmo will warn you that records already exist and will be deleted and replaced. This is fine: the new Payment records will be created using the latest royalty data.&lt;br /&gt;
&lt;br /&gt;
=== 5. CSV Export ===&lt;br /&gt;
Click this button to generate a CSV file (a spreadsheet you can open in Excel) on your Desktop that summarizes the statements. You can give this file to your accountant.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; this export is generic and may or may not be suitable for import into your accounting software. If there is a format that works better for you, let us know and we can discuss building it. Be sure to tell us which software you use, and provide a sample CSV or Excel file showing what a useful import would look like.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=223</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=223"/>
		<updated>2026-10-11T18:47:49Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. Running royalties is a multi-step process:&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Ensure the last period&#039;s Payment records were generated, and create them if not.&lt;br /&gt;
# Set your Minimum Royalty Payment (payout threshold) in Admin.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages: one for contractees and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statements attached.&lt;br /&gt;
# Personalize those messages as you like and send them.&lt;br /&gt;
# Generate Payment records to lock in the amounts for the next period.&lt;br /&gt;
# Optionally, generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts Are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means importing all your sales sheets, as well as manually entering any sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sales sheet containing sales from a royalty period that is imported after that period&#039;s royalty run is complete will never be counted, even in the next period, because PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contracts/Statements Are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you to flag active contracts, to determine whether they are computed and included in your royalty run, by checking the Calc Royalty checkbox. Unlike flagging statements to pay out for the selected period (see below), the status of the Calc Royalty flag persists through all royalty runs; that is, contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
* on the Contract itself, at the upper right;&lt;br /&gt;
* in Royalty form view;&lt;br /&gt;
* in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can list statements by their Calc Royalty status by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Ensure Payment Records from Last Period Have Been Generated ==&lt;br /&gt;
If this is not your first PubGizmo royalty run, make sure you have generated Payment records for the last period. These are necessary to bring forward important values such as Advance Remaining, reserve on returns, and carry-forward amounts for statements you chose not to pay.&lt;br /&gt;
&lt;br /&gt;
If you forgot to do it last time, you can do so now:&lt;br /&gt;
&lt;br /&gt;
# Select the previous royalty period.&lt;br /&gt;
# Open the Bulk Royalty Actions popover.&lt;br /&gt;
# Click Create Payment Records.&lt;br /&gt;
&lt;br /&gt;
After that, set your current royalty period and proceed with the process.&lt;br /&gt;
&lt;br /&gt;
== Flag Statements to Pay This Period ==&lt;br /&gt;
For each royalty period, you determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where those values will be added to (or subtracted from) those statements. Unlike the Calc Royalty checkbox, which persists until you change it, the statements you will actually pay vary each period and must be set each period. By default, when you start a new period, none of the statements are flagged to pay out. You decide which ones get paid and which ones will have their values carried forward to the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]&lt;br /&gt;
You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header above the right-hand column. That toggles the display of the amounts. This setting is off by default because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, described below under Bulk Royalty Actions.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure that you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set Your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments to contractees owed less than a specific amount. For example, you can hold payments until the next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value to $0 and use the bulk process described below, all Calc Royalty statements will be set to pay out.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
* one for the contractee (author, translator, editor, etc.);&lt;br /&gt;
* one for the literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is composed. The subject and body text of these messages are set in Admin &amp;gt; Bulk Mail Templates tab. The templates include a number of merge tags, each enclosed in angle brackets (&amp;amp;#x3C; and &amp;amp;#x3E;), into which relevant data is substituted when the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;&amp;lt;Year&amp;gt;&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; The royalty year, if your press uses the calendar year as its statement period; otherwise, the start and end dates of the royalty period.&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;Title&amp;gt;&amp;lt;/code&amp;gt; The book&#039;s title, or titles if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;GreetingName&amp;gt;&amp;lt;/code&amp;gt; The value in the Correspondence Name field on the recipient&#039;s Contact record (defaults to the Contact&#039;s first name but can be edited). For Organization contractees, the system will attempt to use the name of the Organization&#039;s representative, if defined on the Contract; otherwise, it will use the Organization&#039;s name.&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;Artist&amp;gt;&amp;lt;/code&amp;gt; The contractee&#039;s first and last name. Note: in the agent email, this is replaced with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;Address&amp;gt;&amp;lt;/code&amp;gt; The recipient&#039;s mailing address on one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents with Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements (that is, gathers all relevant statements into a single PDF) and attaches them to one email message under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* the author/contractee has multiple active contracts (a summary page of all statements is included);&lt;br /&gt;
* the literary agent is the agent of record on multiple active contracts.&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk: processes that might have taken days or weeks can be accomplished in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
Bulk actions are executed in a popover accessed with the royalties button (a crown – get it?) in the list view of the Royalties module.[[File:Screenshot_2026-10-01_at_16.31.08.png|none|thumb|631x631px]]Actions are performed for the current royalty period on the Found Set (the records currently showing in the list), and only on those records in the Found Set that have Calc Royalty checked. Statistics at the upper right of the popover describe the composition of your total and current Found Set of records and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure the Found Set that the royalty buttons will run against:&lt;br /&gt;
&lt;br /&gt;
* click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements;&lt;br /&gt;
* load a Snapshot of Royalty records you created previously (see Tags &amp;amp; Snapshots for how to create Snapshots);&lt;br /&gt;
* close the Bulk Royalty Actions popover and use the Find box with criteria to generate a Found Set of the records you want to process;&lt;br /&gt;
* close the Bulk Royalty Actions popover, tag the records, and show only the tagged records you want to process (see Tags &amp;amp; Snapshots for how to tag records and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
The processes are typically run in order. However, you can choose to perform the actions on a subset of records, then move on to another set and start again from the beginning of the process. This is handy if you are working with a large volume of statements and/or working as a team where different users handle different sets of records.&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The Flag Eligible for Payout button automatically flags statements for payout in the selected period when both of the following are true:&lt;br /&gt;
&lt;br /&gt;
* Calc Royalty is checked;&lt;br /&gt;
* the total amount payable across all contracts for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
==== Payment Total Is for All Statements ====&lt;br /&gt;
Because the purpose of the payout threshold is to avoid making payments to contractees below a specified amount – no one wants to write and mail a cheque for $1.87 – PubGizmo considers all statements for each contractee when computing whether the total exceeds the threshold.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* The Minimum Royalty Payment is set to $25.&lt;br /&gt;
* An author has three statements with the following amounts owing: $10, $12, and $5.&lt;br /&gt;
&lt;br /&gt;
In this case, although no single statement reaches $25 by itself, the bulk process will flag all three statements because the total amount to pay that author is $27, which is greater than your $25 threshold. You will send those three statements (which, when sent in bulk, will be bundled into one PDF with a summary page), along with a payment of $27.&lt;br /&gt;
&lt;br /&gt;
=== 2. PDF of Royalty Statements ===&lt;br /&gt;
Most presses have found that the best way to proofread statements before sending them is to generate a PDF, or a series of PDFs, containing the statements and to work from those.&lt;br /&gt;
&lt;br /&gt;
Click this button to generate a PDF on your Desktop containing the Calc Royalty statements in the Found Set.&lt;br /&gt;
&lt;br /&gt;
=== 3. Email Royalty Statements ===&lt;br /&gt;
Click this button to have PubGizmo generate draft email messages in your default email software. Your default email program must be Apple Mail (Mail) if you are on macOS, or Outlook if you use Windows (let us know if you use something else). You can customize each email message as you like and send each one individually.&lt;br /&gt;
&lt;br /&gt;
Every Contact, whether they have their own individual contract or share a single contract for a Title, will receive an email with the relevant statement(s) attached. This includes contractees who are the only signatory to a contract, as well as contractees who share a contract with other contractees. In the latter case, each statement will show the full earnings for the contract, plus the contractee&#039;s own share as a percentage and an amount, as specified in their contract.&lt;br /&gt;
&lt;br /&gt;
Contractees, whether they are Contacts or Organizations, will receive the following in their PDF:&lt;br /&gt;
&lt;br /&gt;
==== Contacts ====&lt;br /&gt;
&lt;br /&gt;
* all their own Calc Royalty statements in the current Found Set;&lt;br /&gt;
* a summary page of all their Calc Royalty statements (including those not in the Found Set), if the contractee receives more than one statement.&lt;br /&gt;
&lt;br /&gt;
==== Organizations ====&lt;br /&gt;
&lt;br /&gt;
* all relevant Calc Royalty statements in the current Found Set;&lt;br /&gt;
* a summary page of statements, if the PDF contains more than one statement.&lt;br /&gt;
&lt;br /&gt;
==== Literary Agents ====&lt;br /&gt;
The process also generates draft emails to the agent of record on each statement, with the relevant statements attached.&lt;br /&gt;
&lt;br /&gt;
=== 4. Create Payment Records ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; amounts, such as Advance Remaining and carry-forward values, which inform the calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important notes:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* All of the steps above must be complete (all sales records imported, appropriate records set to calculate and pay out, statements fully proofed) before you do this step. If you change anything for the current period, you will have to create the Payment records again, although a single changed statement can receive a new Payment record by opening the statement and clicking the &amp;quot;$&amp;quot; button.&lt;br /&gt;
* This step is performed on all Calc Royalty records, regardless of the Found Set. Save it for the very end of your royalty process to ensure the values are final.&lt;br /&gt;
* You must complete this step for each royalty period before running the next one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period&#039;s results will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
* If you have previously created Payment records and try to do so again, PubGizmo will warn you that records already exist and will be deleted and replaced. This is fine: the new Payment records will be created using the latest royalty data.&lt;br /&gt;
&lt;br /&gt;
=== 5. CSV Export ===&lt;br /&gt;
Click this button to generate a CSV file (a spreadsheet you can open in Excel) on your Desktop that summarizes the statements. You can give this file to your accountant.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Note:&#039;&#039;&#039; this export is generic and may or may not be suitable for import into your accounting software. If there is a format that works better for you, let us know and we can discuss building it. Be sure to tell us which software you use, and provide a sample CSV or Excel file showing what a useful import would look like.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=222</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=222"/>
		<updated>2026-10-11T18:26:09Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Ensure the last period&#039;s payment records were generated, and create them if not.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records to lock-in the amounts for the next period.&lt;br /&gt;
# Optionally generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run will need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for the selected period (see below), the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can yield a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Ensure Payment Records from Last Period Have Been Generated ==&lt;br /&gt;
If this is not your first PubGizmo royalty run, make sure you have generated Payment records for the last period. These are necessary to bring forward important values like advance remaining, reserve on returns, or carry forward amounts for statements you chose not to pay.&lt;br /&gt;
&lt;br /&gt;
If you forgot to do it last time, you can do so now:&lt;br /&gt;
&lt;br /&gt;
# Select the previous royalty period&lt;br /&gt;
# Open the royalties popover&lt;br /&gt;
# Click &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After that, set your current royalty period, and proceed with the process.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where those values will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period, and must be set each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]&lt;br /&gt;
You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header above the righthand column. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, outlined below under Bulk Royalty Actions.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the Contact&#039;s first name, but can be edited). For Organization contractees, the system will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts (includes a summary page of all statements)&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk: processes that might&#039;ve taken days or weeks can be accomplished in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
Bulk actions are executed in a popover accessed using the royalties (crown – get it?) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot_2026-10-01_at_16.31.08.png|none|thumb|631x631px]]&lt;br /&gt;
Actions are performed for the set royalty period on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the upper-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshots)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, Tag the records, and show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
The processes are typically run in order. However, you can choose to perform the actions on a subset of records and then move on to another set and start again from the beginning of the process, handy if you are working with a large volume of statements and/or working as a team where different users handle different sets of records.&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button will auto-flag statements for payout in the selected period, as follows:&lt;br /&gt;
&lt;br /&gt;
# Calc Royalty is flagged&lt;br /&gt;
# the &#039;&#039;total amount payable for all contracts&#039;&#039; for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
==== Payment Total is for All Statements ====&lt;br /&gt;
Because the purpose of the payment threshold is to avoid making payments to contractees below a specified amount – no one wants to write and mail a cheque for $1.87 – PubGizmo considers &#039;&#039;all statements for each contractee&#039;&#039; when computing whether or not statements exceed the threshold.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* minimum royalty payment is set for $25&lt;br /&gt;
* author has three statements, with the following amounts owing: $10, $12, $5&lt;br /&gt;
&lt;br /&gt;
In this case, while no single statement about reaches $25, the bulk process will flag &#039;&#039;all three statements&#039;&#039;, because the &#039;&#039;&#039;total amount to pay&#039;&#039;&#039; that author is $27, which is of course greater than your $25 threshold. You will send those three statements (which when sent in bulk will be bundled into one PDF with a summary page), along with a payment of $27. &lt;br /&gt;
&lt;br /&gt;
=== 2. PDF of Royalty Statements ===&lt;br /&gt;
Most presses have found that the best way to proofread statements before sending them is to generate a PDF or a series of PDFs containing the statements and work from that.&lt;br /&gt;
&lt;br /&gt;
Click this button to generate a PDF on your Desktop containing the Calc Royalty statements the Found Set.&lt;br /&gt;
&lt;br /&gt;
=== 3. Email Royalty Statements ===&lt;br /&gt;
Click for PubGizmo to generate draft email messages in your default email software.&lt;br /&gt;
&lt;br /&gt;
Every Contact, whether they have their own individual contract or share a single contract for a Title will receive an email with relevant statement(s) attached. This means contractees where they are the only signatory to the contract, plus contractees who share a contract with other contractees. In the latter case, each statement will show the full earnings for the contract, plus their own share as a percentage and an amount, as specified on their contract.&lt;br /&gt;
&lt;br /&gt;
Contractees, whether they are Contacts or Organizations, will receive the following in their PDF:&lt;br /&gt;
&lt;br /&gt;
==== Contacts ====&lt;br /&gt;
&lt;br /&gt;
* all their own Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing all Calc Royalty statements (including those not in the Found Set), if the contractee receives more than one statement.&lt;br /&gt;
&lt;br /&gt;
==== Organizations ====&lt;br /&gt;
&lt;br /&gt;
* all relevant Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Literary Agents ====&lt;br /&gt;
The process also generates draft emails to the agent-of-record of each statement, with statements for &lt;br /&gt;
&lt;br /&gt;
and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;4. Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again, although a single changed statement can receive a new payment record by opening the statement and clicking the &amp;quot;$&amp;quot; button.&lt;br /&gt;
# This step is performed on &#039;&#039;all Calc Royalty records&#039;&#039;, regardless of the Found Set. Save it for the very end of your royalty process to ensure the values are final.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== 5. CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;br /&gt;
&lt;br /&gt;
Note: this is a generic statement, which may or may not be suitable for import into your accounting software. If there is a format that works better for you, let us know and we can discuss building it. Be sure to let us know which software your use, and provide a sample CSV or Excel file of what a useful import would look like.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=221</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=221"/>
		<updated>2026-10-11T18:00:15Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Ensure the last period&#039;s payment records were generated, and create them if not.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records to lock-in the amounts for the next period.&lt;br /&gt;
# Optionally generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run will need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for the selected period (see below), the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can yield a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Ensure Payment Records from Last Period Have Been Generated ==&lt;br /&gt;
If this is not your first PubGizmo royalty run, make sure you have generated Payment records for the last period. These are necessary to bring forward important values like advance remaining, reserve on returns, or carry forward amounts for statements you chose not to pay.&lt;br /&gt;
&lt;br /&gt;
If you forgot to do it last time, you can do so now:&lt;br /&gt;
&lt;br /&gt;
# Select the previous royalty period&lt;br /&gt;
# Open the royalties popover&lt;br /&gt;
# Click &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After that, set your current royalty period, and proceed with the process.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where those values will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period, and must be set each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]&lt;br /&gt;
You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header above the righthand column. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, outlined below under Bulk Royalty Actions.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the Contact&#039;s first name, but can be edited). For Organization contractees, the system will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts (includes a summary page of all statements)&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk: processes that might&#039;ve taken days or weeks can be accomplished in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
Bulk actions are executed in a popover accessed using the royalties (crown – get it?) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot_2026-10-01_at_16.31.08.png|none|thumb|631x631px]]&lt;br /&gt;
Actions are performed for the set royalty period on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the upper-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshots)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, Tag the records, and show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
The processes are typically run in order. However, you can choose to perform the actions on a subset of records and then move on to another set and start again from the beginning of the process, handy if you are working with a large volume of statements and/or working as a team where different users handle different sets of records.&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button will auto-flag statements for payout in the selected period, as follows:&lt;br /&gt;
&lt;br /&gt;
# Calc Royalty is flagged&lt;br /&gt;
# the &#039;&#039;total amount payable for all contracts&#039;&#039; for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
==== Payment Total is for All Statements ====&lt;br /&gt;
Because the purpose of the payment threshold is to avoid making payments to contractees below a specified amount – no one wants to write and mail a cheque for $1.87 – PubGizmo considers &#039;&#039;all statements for each contractee&#039;&#039; when computing whether or not statements exceed the threshold.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* minimum royalty payment is set for $25&lt;br /&gt;
* author has three statements, with the following amounts owing: $10, $12, $5&lt;br /&gt;
&lt;br /&gt;
In this case, while no single statement about reaches $25, the bulk process will flag &#039;&#039;all three statements&#039;&#039;, because the &#039;&#039;&#039;total amount to pay&#039;&#039;&#039; that author is $27, which is of course greater than your $25 threshold. You will send those three statements (which when sent in bulk will be bundled into one PDF with a summary page), along with a payment of $27. &lt;br /&gt;
&lt;br /&gt;
=== 2. PDF of Royalty Statements ===&lt;br /&gt;
Most presses have found that the best way to proofread statements before sending them is to generate a PDF or a series of PDFs containing the statements and work from that.&lt;br /&gt;
&lt;br /&gt;
Click this button to generate a PDF on your Desktop containing the Calc Royalty statements the Found Set.&lt;br /&gt;
&lt;br /&gt;
=== 3. Email Royalty Statements ===&lt;br /&gt;
Click for PubGizmo to generate draft email messages in your default email software.&lt;br /&gt;
&lt;br /&gt;
Every Contact, whether they have their own individual contract or share a single contract for a Title will receive an email with relevant statement(s) attached. This means contractees where they are the only signatory to the contract, plus contractees who share a contract with other contractees. In the latter case, each statement will show the full earnings for the contract, plus their own share as a percentage and an amount, as specified on their contract.&lt;br /&gt;
&lt;br /&gt;
Contractees, whether they are Contacts or Organizations, will receive the following in their PDF:&lt;br /&gt;
&lt;br /&gt;
==== Contacts ====&lt;br /&gt;
&lt;br /&gt;
* all their own Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Organizations ====&lt;br /&gt;
&lt;br /&gt;
* all relevant Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Literary Agents ====&lt;br /&gt;
The process also generates draft emails to the agent-of-record of each statement, with statements for &lt;br /&gt;
&lt;br /&gt;
and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;4. Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# This step is performed on &#039;&#039;all Calc Royalty records&#039;&#039;, regardless of the Found Set. Save it for the very end of your royalty process to ensure the values are final.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=220</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=220"/>
		<updated>2026-10-11T17:25:01Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Ensure period&#039;s payment records were generated, and create them if not.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records to lock-in the amounts for the next period.&lt;br /&gt;
# Optionally generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run will need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Ensure Payment Records from Last Period Have Been Generated ==&lt;br /&gt;
If this is not your first PubGizmo royalty run, make sure you have generated Payment records for the last period. These are necessary to bring forward important values like advance remaining, reserve on returns, or carry forward amounts for statements you chose not to pay.&lt;br /&gt;
&lt;br /&gt;
If you forgot to do it last time, you can do so now:&lt;br /&gt;
&lt;br /&gt;
# Select the previous royalty period&lt;br /&gt;
# Open the royalties popover&lt;br /&gt;
# Click &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
After that, set your current royalty period, and proceed with the process.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for the selected period (see below), the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can yield a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where those values will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period, and must be set each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]&lt;br /&gt;
You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header above the righthand column. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, outlined below under Bulk Royalty Actions.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the Contact&#039;s first name, but can be edited). For Organization contractees, the system will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts (includes a summary page of all statements)&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk: processes that might&#039;ve taken days or weeks can be accomplished in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
Bulk actions are executed in a popover accessed using the royalties (crown – get it?) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot_2026-10-01_at_16.31.08.png|none|thumb|631x631px]]&lt;br /&gt;
Actions are performed for the set royalty period on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the upper-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshots)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, Tag the records, and show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
The processes are typically run in order. However, you can choose to perform the actions on a subset of records and then move on to another set and start again from the beginning of the process, handy if you are working with a large volume of statements and/or working as a team where different users handle different sets of records.&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button will auto-flag statements for payout in the selected period, as follows:&lt;br /&gt;
&lt;br /&gt;
# Calc Royalty is flagged&lt;br /&gt;
# the &#039;&#039;total amount payable for all contracts&#039;&#039; for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
==== Payment Total is for All Statements ====&lt;br /&gt;
Because the purpose of the payment threshold is to avoid making payments to contractees below a specified amount – no one wants to write and mail a cheque for $1.87 – PubGizmo considers &#039;&#039;all statements for each contractee&#039;&#039; when computing whether or not statements exceed the threshold.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* minimum royalty payment is set for $25&lt;br /&gt;
* author has three statements, with the following amounts owing: $10, $12, $5&lt;br /&gt;
&lt;br /&gt;
In this case, while no single statement about reaches $25, the bulk process will flag &#039;&#039;all three statements&#039;&#039;, because the &#039;&#039;&#039;total amount to pay&#039;&#039;&#039; that author is $27, which is of course greater than your $25 threshold. You will send those three statements (which when sent in bulk will be bundled into one PDF with a summary page), along with a payment of $27. &lt;br /&gt;
&lt;br /&gt;
=== 2. PDF of Royalty Statements ===&lt;br /&gt;
Most presses have found that the best way to proofread statements before sending them is to generate a PDF or a series of PDFs containing the statements and work from that.&lt;br /&gt;
&lt;br /&gt;
Click this button to generate a PDF on your Desktop containing the Calc Royalty statements the Found Set.&lt;br /&gt;
&lt;br /&gt;
=== 3. Email Royalty Statements ===&lt;br /&gt;
Click for PubGizmo to generate draft email messages in your default email software.&lt;br /&gt;
&lt;br /&gt;
Every Contact, whether they have their own individual contract or share a single contract for a Title will receive an email with relevant statement(s) attached. This means contractees where they are the only signatory to the contract, plus contractees who share a contract with other contractees. In the latter case, each statement will show the full earnings for the contract, plus their own share as a percentage and an amount, as specified on their contract.&lt;br /&gt;
&lt;br /&gt;
Contractees, whether they are Contacts or Organizations, will receive the following in their PDF:&lt;br /&gt;
&lt;br /&gt;
==== Contacts ====&lt;br /&gt;
&lt;br /&gt;
* all their own Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Organizations ====&lt;br /&gt;
&lt;br /&gt;
* all relevant Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Literary Agents ====&lt;br /&gt;
The process also generates draft emails to the agent-of-record of each statement, with statements for &lt;br /&gt;
&lt;br /&gt;
and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=219</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=219"/>
		<updated>2026-10-11T17:22:33Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records to lock-in the amounts for the next period.&lt;br /&gt;
# Optionally generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run will need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Ensure Payment Records from Last Period Have Been Generated ==&lt;br /&gt;
If this is not your first PubGizmo royalty run, make sure you have generated Payment records for the last period. These are necessary to bring forward important values like advance remaining, reserve on returns, or carry forward amounts for statements you chose not to pay.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for the selected period (see below), the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can yield a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where those values will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period, and must be set each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]&lt;br /&gt;
You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header above the righthand column. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, outlined below under Bulk Royalty Actions.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the Contact&#039;s first name, but can be edited). For Organization contractees, the system will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts (includes a summary page of all statements)&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk: processes that might&#039;ve taken days or weeks can be accomplished in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
Bulk actions are executed in a popover accessed using the royalties (crown – get it?) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot_2026-10-01_at_16.31.08.png|none|thumb|631x631px]]&lt;br /&gt;
Actions are performed for the set royalty period on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the upper-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshots)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, Tag the records, and show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
The processes are typically run in order. However, you can choose to perform the actions on a subset of records and then move on to another set and start again from the beginning of the process, handy if you are working with a large volume of statements and/or working as a team where different users handle different sets of records.&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button will auto-flag statements for payout in the selected period, as follows:&lt;br /&gt;
&lt;br /&gt;
# Calc Royalty is flagged&lt;br /&gt;
# the &#039;&#039;total amount payable for all contracts&#039;&#039; for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
==== Payment Total is for All Statements ====&lt;br /&gt;
Because the purpose of the payment threshold is to avoid making payments to contractees below a specified amount – no one wants to write and mail a cheque for $1.87 – PubGizmo considers &#039;&#039;all statements for each contractee&#039;&#039; when computing whether or not statements exceed the threshold.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* minimum royalty payment is set for $25&lt;br /&gt;
* author has three statements, with the following amounts owing: $10, $12, $5&lt;br /&gt;
&lt;br /&gt;
In this case, while no single statement about reaches $25, the bulk process will flag &#039;&#039;all three statements&#039;&#039;, because the &#039;&#039;&#039;total amount to pay&#039;&#039;&#039; that author is $27, which is of course greater than your $25 threshold. You will send those three statements (which when sent in bulk will be bundled into one PDF with a summary page), along with a payment of $27. &lt;br /&gt;
&lt;br /&gt;
=== 2. PDF of Royalty Statements ===&lt;br /&gt;
Most presses have found that the best way to proofread statements before sending them is to generate a PDF or a series of PDFs containing the statements and work from that.&lt;br /&gt;
&lt;br /&gt;
Click this button to generate a PDF on your Desktop containing the Calc Royalty statements the Found Set.&lt;br /&gt;
&lt;br /&gt;
=== 3. Email Royalty Statements ===&lt;br /&gt;
Click for PubGizmo to generate draft email messages in your default email software.&lt;br /&gt;
&lt;br /&gt;
Every Contact, whether they have their own individual contract or share a single contract for a Title will receive an email with relevant statement(s) attached. This means contractees where they are the only signatory to the contract, plus contractees who share a contract with other contractees. In the latter case, each statement will show the full earnings for the contract, plus their own share as a percentage and an amount, as specified on their contract.&lt;br /&gt;
&lt;br /&gt;
Contractees, whether they are Contacts or Organizations, will receive the following in their PDF:&lt;br /&gt;
&lt;br /&gt;
==== Contacts ====&lt;br /&gt;
&lt;br /&gt;
* all their own Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Organizations ====&lt;br /&gt;
&lt;br /&gt;
* all relevant Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Literary Agents ====&lt;br /&gt;
The process also generates draft emails to the agent-of-record of each statement, with statements for &lt;br /&gt;
&lt;br /&gt;
and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=218</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=218"/>
		<updated>2026-10-08T00:22:09Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records to lock-in the amounts for the next period.&lt;br /&gt;
# Optionally generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run will need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for the selected period (see below), the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can yield a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where those values will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period, and must be set each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]&lt;br /&gt;
You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header above the righthand column. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, outlined below under Bulk Royalty Actions.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the Contact&#039;s first name, but can be edited). For Organization contractees, the system will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts (includes a summary page of all statements)&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk: processes that might&#039;ve taken days or weeks can be accomplished in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
Bulk actions are executed in a popover accessed using the royalties (crown – get it?) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot_2026-10-01_at_16.31.08.png|none|thumb|631x631px]]&lt;br /&gt;
Actions are performed for the set royalty period on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the upper-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshots)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, Tag the records, and show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
The processes are typically run in order. However, you can choose to perform the actions on a subset of records and then move on to another set and start again from the beginning of the process, handy if you are working with a large volume of statements and/or working as a team where different users handle different sets of records.&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button will auto-flag statements for payout in the selected period, as follows:&lt;br /&gt;
&lt;br /&gt;
# Calc Royalty is flagged&lt;br /&gt;
# the &#039;&#039;total amount payable for all contracts&#039;&#039; for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
==== Payment Total is for All Statements ====&lt;br /&gt;
Because the purpose of the payment threshold is to avoid making payments to contractees below a specified amount – no one wants to write and mail a cheque for $1.87 – PubGizmo considers &#039;&#039;all statements for each contractee&#039;&#039; when computing whether or not statements exceed the threshold.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* minimum royalty payment is set for $25&lt;br /&gt;
* author has three statements, with the following amounts owing: $10, $12, $5&lt;br /&gt;
&lt;br /&gt;
In this case, while no single statement about reaches $25, the bulk process will flag &#039;&#039;all three statements&#039;&#039;, because the &#039;&#039;&#039;total amount to pay&#039;&#039;&#039; that author is $27, which is of course greater than your $25 threshold. You will send those three statements (which when sent in bulk will be bundled into one PDF with a summary page), along with a payment of $27. &lt;br /&gt;
&lt;br /&gt;
=== 2. PDF of Royalty Statements ===&lt;br /&gt;
Most presses have found that the best way to proofread statements before sending them is to generate a PDF or a series of PDFS containing the statements and work from that.&lt;br /&gt;
&lt;br /&gt;
Click this button to generate a PDF on your Desktop containing the Calc Royalty statements the Found Set.&lt;br /&gt;
&lt;br /&gt;
=== 3. Email Royalty Statements ===&lt;br /&gt;
Click for PubGizmo to generate draft email messages in your default email software.&lt;br /&gt;
&lt;br /&gt;
Every Contact, whether they have their own individual contract or share a single contract for a Title will receive an email with relevant statement(s) attached. This means contractees where they are the only signatory to the contract, plus contractees who share a contract with other contractees. In the latter case, each statement will show the full earnings for the contract, plus their own share as a percentage and an amount, as specified on their contract.&lt;br /&gt;
&lt;br /&gt;
Contractees, whether they are Contacts or Organizations, will receive the following in their PDF:&lt;br /&gt;
&lt;br /&gt;
==== Contacts ====&lt;br /&gt;
&lt;br /&gt;
* all their own Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Organizations ====&lt;br /&gt;
&lt;br /&gt;
* all relevant Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Literary Agents ====&lt;br /&gt;
The process also generates draft emails to the agent-of-record of each statement, with statements for &lt;br /&gt;
&lt;br /&gt;
and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=217</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=217"/>
		<updated>2026-10-08T00:21:12Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records to lock-in the amounts for the next period.&lt;br /&gt;
# Optionally generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run will need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for the selected period (see below), the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can yield a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where those values will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period, and must be set each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]&lt;br /&gt;
You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header above the righthand column. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, outlined below under Bulk Royalty Actions.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the Contact&#039;s first name, but can be edited). For Organization contractees, the system will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts (includes a summary page of all statements)&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk: processes that might&#039;ve taken days or weeks can be accomplished in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
Bulk actions are executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot_2026-10-01_at_16.31.08.png|none|thumb|631x631px]]&lt;br /&gt;
Actions are performed for the set royalty period on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the upper-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshots)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, Tag the records, and show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
The processes are typically run in order. However, you can choose to perform the actions on a subset of records and then move on to another set and start again from the beginning of the process, handy if you are working with a large volume of statements and/or working as a team where different users handle different sets of records.&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button will auto-flag statements for payout in the selected period, as follows:&lt;br /&gt;
&lt;br /&gt;
# Calc Royalty is flagged&lt;br /&gt;
# the &#039;&#039;total amount payable for all contracts&#039;&#039; for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
==== Payment Total is for All Statements ====&lt;br /&gt;
Because the purpose of the payment threshold is to avoid making payments to contractees below a specified amount – no one wants to write and mail a cheque for $1.87 – PubGizmo considers &#039;&#039;all statements for each contractee&#039;&#039; when computing whether or not statements exceed the threshold.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* minimum royalty payment is set for $25&lt;br /&gt;
* author has three statements, with the following amounts owing: $10, $12, $5&lt;br /&gt;
&lt;br /&gt;
In this case, while no single statement about reaches $25, the bulk process will flag &#039;&#039;all three statements&#039;&#039;, because the &#039;&#039;&#039;total amount to pay&#039;&#039;&#039; that author is $27, which is of course greater than your $25 threshold. You will send those three statements (which when sent in bulk will be bundled into one PDF with a summary page), along with a payment of $27. &lt;br /&gt;
&lt;br /&gt;
=== 2. PDF of Royalty Statements ===&lt;br /&gt;
Most presses have found that the best way to proofread statements before sending them is to generate a PDF or a series of PDFS containing the statements and work from that.&lt;br /&gt;
&lt;br /&gt;
Click this button to generate a PDF on your Desktop containing the Calc Royalty statements the Found Set.&lt;br /&gt;
&lt;br /&gt;
=== 3. Email Royalty Statements ===&lt;br /&gt;
Click for PubGizmo to generate draft email messages in your default email software.&lt;br /&gt;
&lt;br /&gt;
Every Contact, whether they have their own individual contract or share a single contract for a Title will receive an email with relevant statement(s) attached. This means contractees where they are the only signatory to the contract, plus contractees who share a contract with other contractees. In the latter case, each statement will show the full earnings for the contract, plus their own share as a percentage and an amount, as specified on their contract.&lt;br /&gt;
&lt;br /&gt;
Contractees, whether they are Contacts or Organizations, will receive the following in their PDF:&lt;br /&gt;
&lt;br /&gt;
==== Contacts ====&lt;br /&gt;
&lt;br /&gt;
* all their own Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Organizations ====&lt;br /&gt;
&lt;br /&gt;
* all relevant Calc Royalty statements in the current Found Set&lt;br /&gt;
* a supplement summarizing statements, if the PDF contains more than one statement&lt;br /&gt;
&lt;br /&gt;
==== Literary Agents ====&lt;br /&gt;
The process also generates draft emails to the agent-of-record of each statement, with statements for &lt;br /&gt;
&lt;br /&gt;
and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=216</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=216"/>
		<updated>2026-10-05T23:31:03Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records to lock-in the amounts for the next period.&lt;br /&gt;
# Optionally generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run will need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for the selected period (see below), the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can yield a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where those values will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period, and must be set each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header above the righthand column. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, outlined below under Bulk Royalty Actions.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the Contact&#039;s first name, but can be edited). For Organization contractees, the system will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts (includes a summary page of all statements)&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk: processes that might&#039;ve taken days or weeks can be accomplished in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
Bulk actions are executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]Actions are performed for the set royalty period on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the upper-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshots)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, Tag the records, and show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
The processes are typically run in order. However, you can choose to perform the actions on a subset of records and then move on to another set and start again from the beginning of the process, handy if you are working with a large volume of statements and/or working as a team where different users handle different sets of records.&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button will auto-flag statements for payout in the selected period, as follows:&lt;br /&gt;
&lt;br /&gt;
# Calc Royalty is flagged&lt;br /&gt;
# the &#039;&#039;total amount payable for all contracts&#039;&#039; for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
Note for the second item it&#039;s the combined amount for all the contractee&#039;s statements, not just this statement, that determines whether or not that statement and all that contractee statements are flagged.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
minimum royalty payment threshold is set for $25&lt;br /&gt;
&lt;br /&gt;
author has three statements, with the following amounts owing: $10, $12, $5&lt;br /&gt;
&lt;br /&gt;
All three statements will be flagged, because the total amount to pay that author is $27. The idea &lt;br /&gt;
&lt;br /&gt;
in the selected period any Calc Royalty contract where the amount owing to one or more of the contractees exceeds the threshold (set in Admin), e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Click the &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=215</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=215"/>
		<updated>2026-10-04T19:13:25Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records to lock-in the amounts for the next period.&lt;br /&gt;
# Optionally generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run will need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for the period (see below), the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where they will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to use the bulk Flag Eligible for Payout function, outlined below.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period if the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; if you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send statements individually, PubGizmo&#039;s superpower is handling royalty functions in bulk – processes that might&#039;ve taken days or weeks can be completed in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
These actions are executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]Actions are performed for the set royalty period on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the upper-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshot sets)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, Tag the records, and show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records).&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button will auto-flag statements for payout in the selected period, as follows:&lt;br /&gt;
&lt;br /&gt;
# Calc Royalty is flagged&lt;br /&gt;
# the &#039;&#039;total amount payable for all contracts&#039;&#039; for at least one contractee on the statement equals or exceeds the Minimum Royalty Payment amount in Admin.&lt;br /&gt;
&lt;br /&gt;
Note for the second item it&#039;s the combined amount for all the contractee&#039;s statements, not just this statement, that determines whether or not that statement and all that contractee statements are flagged.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
minimum royalty payment threshold is set for $25&lt;br /&gt;
&lt;br /&gt;
author has three statements, with the following amounts owing: $10, $12, $5&lt;br /&gt;
&lt;br /&gt;
All three statements will be flagged, because the total amount to pay that author is $27. The idea &lt;br /&gt;
&lt;br /&gt;
in the selected period any Calc Royalty contract where the amount owing to one or more of the contractees exceeds the threshold (set in Admin), e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Click the &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=214</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=214"/>
		<updated>2026-10-04T18:57:29Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Enter new Titles since the last period and configure Editions and Contracts.&lt;br /&gt;
# Apply changes that may affect existing Titles. Did you add new editions?&lt;br /&gt;
# Complete importing and entering all sales data for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records to lock-in the amounts for the next period.&lt;br /&gt;
# Optionally generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run will need to be added, and changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import. Each Sales Import includes a checkbox to confirm completeness and accuracy.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since strictly PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for this period (see below), the the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where they will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values, if any, carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to flag the majority using of them using the bulk Flag Eligible for Payout function, outlined below.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period of the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment. If you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send individual statements, PubGizmo&#039;s superpower is handling royalty functions in bulk – processes that might&#039;ve taken days are weeks can be completed in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
These actions are accessed and executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]Actions are performed only on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the top-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshot sets)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, and Tag the records you want, then show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records)&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button in the Bulk Royalty Action popover will auto-flag for the payout for the selected period for any active contract where the amount owing to one or more of the contractees exceeds the threshold (set in Admin), e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Click the &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=213</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=213"/>
		<updated>2026-10-04T18:53:29Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Ensure all editions are added to Title records – remember to add any that may have been released since your last period, and ensure that list prices are correctly set.&lt;br /&gt;
# Ensure all contracts are configured and accurate.&lt;br /&gt;
# Complete importing and entering all sales records for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged to Calc Royalty.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records to lock-in the amounts for the next period.&lt;br /&gt;
# Optionally generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Ensure Titles, Editions, and Contracts are Current and Accurate ==&lt;br /&gt;
Titles published since your last royalty run will need to be added, and  changes to editions and/or contracts for previous titles need to be applied.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since strictly PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for this period (see below), the the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where they will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values, if any, carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to flag the majority using of them using the bulk Flag Eligible for Payout function, outlined below.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period of the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment. If you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send individual statements, PubGizmo&#039;s superpower is handling royalty functions in bulk – processes that might&#039;ve taken days are weeks can be completed in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
These actions are accessed and executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]Actions are performed only on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the top-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshot sets)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, and Tag the records you want, then show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records)&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button in the Bulk Royalty Action popover will auto-flag for the payout for the selected period for any active contract where the amount owing to one or more of the contractees exceeds the threshold (set in Admin), e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Click the &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=212</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=212"/>
		<updated>2026-10-04T18:04:23Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: /* The Process */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Royalties Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Ensure all editions are added to Title records.&lt;br /&gt;
# Ensure all contracts are configured.&lt;br /&gt;
# Complete importing and entering all sales records for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged active.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records, to lock-in the amounts for the next period.&lt;br /&gt;
# Generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since strictly PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for this period (see below), the the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where they will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values, if any, carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to flag the majority using of them using the bulk Flag Eligible for Payout function, outlined below.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period of the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment. If you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send individual statements, PubGizmo&#039;s superpower is handling royalty functions in bulk – processes that might&#039;ve taken days are weeks can be completed in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
These actions are accessed and executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]Actions are performed only on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the top-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshot sets)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, and Tag the records you want, then show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records)&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button in the Bulk Royalty Action popover will auto-flag for the payout for the selected period for any active contract where the amount owing to one or more of the contractees exceeds the threshold (set in Admin), e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Click the &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=211</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=211"/>
		<updated>2026-10-04T18:02:35Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Complete importing and entering all sales records for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged active.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records, to lock-in the amounts for the next period.&lt;br /&gt;
# Generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Complete Input of Sales Data ==&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since strictly PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
== Ensure Correct Active Contract/Statements are Flagged to Calculate ==&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for this period (see below), the the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
== Flag Royalties to Pay This Period ==&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where they will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values, if any, carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
=== Flag Manually ===&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; during the 2023 period.]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Flag Automatically ===&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to flag the majority using of them using the bulk Flag Eligible for Payout function, outlined below.&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you can hold payments until next period of the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
You can find the field to change this value in Admin &amp;gt; second tab &amp;gt; Minimum Royalty Payment. If you set this value for $0 and use the bulk process outlined below, all statements will be set to payout.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, translator, editor, etc.).&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== Bulk Royalty Actions ==&lt;br /&gt;
While you can configure and send individual statements, PubGizmo&#039;s superpower is handling royalty functions in bulk – processes that might&#039;ve taken days are weeks can be completed in minutes.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
These actions are accessed and executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]Actions are performed only on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the top-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshot sets)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, and Tag the records you want, then show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records)&lt;br /&gt;
&lt;br /&gt;
== Bulk Processes ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button in the Bulk Royalty Action popover will auto-flag for the payout for the selected period for any active contract where the amount owing to one or more of the contractees exceeds the threshold (set in Admin), e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Click the &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=210</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=210"/>
		<updated>2026-10-04T17:46:31Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Complete importing and entering all sales records for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged active.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records, to lock-in the amounts for the next period.&lt;br /&gt;
# Generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Step-by-step ==&lt;br /&gt;
=== Complete Input of Sales Data ===&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since strictly PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
=== Ensure Correct Active Contract/Statements are Flagged to Calculate ===&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for this period (see below), the the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
=== Flag Royalties to Pay This Period ===&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where they will be added (or subtracted) from those statements. Unlike the Calc Royalty checkboxes, which persist until you change them, the statements you will actually pay varies each period. By default, when you start a new period, none of the statements are flagged to payout. You decide which ones get paid, and which ones will have their values, if any, carried over until the next period.&lt;br /&gt;
&lt;br /&gt;
==== Flag Manually ====&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without the Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; with this statement.]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
If you have many statements to pay, it&#039;s easiest to flag the majority using of them using the bulk Flag Eligible for Payout function, outlined below.&lt;br /&gt;
&lt;br /&gt;
=== Apply Global Settings ===&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you hold payments until next period of the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, etc.),&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
The functions to complete royalties are executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]These actions are performed only on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the top-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshot sets)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, and Tag the records you want, then show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records)&lt;br /&gt;
&lt;br /&gt;
*&lt;br /&gt;
&lt;br /&gt;
== The Process ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button in the Bulk Royalty Action popover will auto-flag for the payout for the selected period for any active contract where the amount owing to one or more of the contractees exceeds the threshold (set in Admin), e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Click the &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=209</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=209"/>
		<updated>2026-10-04T17:35:13Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Complete importing and entering all sales records for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged active.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records, to lock-in the amounts for the next period.&lt;br /&gt;
# Generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Accessing the Royalties Menu ==&lt;br /&gt;
The steps below are activated via the crown popover available at the upper-right in Royalties list view.&lt;br /&gt;
== Step-by-step ==&lt;br /&gt;
&lt;br /&gt;
=== Complete Input of Sales Data ===&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since strictly PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
=== Ensure Correct Active Contract/Statements are Flagged to Calculate ===&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for this period (see below), the the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
The functions to complete royalties are executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]These actions are performed only on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the top-right of the popover describe the composition of your total and current Found Set of records, and how many will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshot sets)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, and Tag the records you want, then show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records)&lt;br /&gt;
&lt;br /&gt;
== Apply Global Settings ==&lt;br /&gt;
Before running royalties, ensure you set up a couple of things in Admin (only users with Admin access can perform these actions).&lt;br /&gt;
&lt;br /&gt;
=== Set your Payout Threshold ===&lt;br /&gt;
For each royalty period, you can determine which statements will be paid out and which will carry forward their values (if any) to the next royalty period, where they will be added (or subtracted) from those statements. Unlike the Calc Royalty checkbox, you can payout &lt;br /&gt;
&lt;br /&gt;
You may not want to cut cheques or send payments for contractees owed less than a specific amount. For example, you hold payments until next period of the contractee is owed less than $25.&lt;br /&gt;
&lt;br /&gt;
==== Flag Manually ====&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Without the Pay Out flagged, $137.34 will carry over to the next period; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039; with this statement.]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, etc.),&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
== The Process ==&lt;br /&gt;
&lt;br /&gt;
=== 1. Flag Eligible for Payout ===&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
The &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button in the Bulk Royalty Action popover will auto-flag for the payout for the selected period for any active contract where the amount owing to one or more of the contractees exceeds the threshold (set in Admin), e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Click the &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039; button.&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=208</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=208"/>
		<updated>2026-10-03T22:45:03Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Complete importing and entering all sales records for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged active.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records, to lock-in the amounts for the next period.&lt;br /&gt;
# Generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Accessing the Royalties Menu ==&lt;br /&gt;
The steps below are activated via the crown popover available at the upper-right in Royalties list view.&lt;br /&gt;
== Step-by-step ==&lt;br /&gt;
&lt;br /&gt;
=== Complete Input of Sales Data ===&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since strictly PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
=== Ensure Correct Active Contract/Statements are Flagged to Calculate ===&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for this period (see below), the the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
The functions to complete royalties are executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]These actions are performed only on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the top of the popover describe how many records will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# click the Show All Records button (hidden if you are already seeing all records) to do a complete run of all Calc Royalty statements&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshot sets)&lt;br /&gt;
# close the Bulk Royalty Actions popover, and use the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, and Tag the records you want, then show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag and show only tagged records)&lt;br /&gt;
&lt;br /&gt;
=== Flag Statements to Pay Out ===&lt;br /&gt;
Statements default to not being paid out. You&#039;ll notice that initially, all statements are carrying over the earned amount to the next period. You can flag these either manually or automatically.&lt;br /&gt;
&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
PubGizmo can auto-flag for payout any active contract where the amount owing to the author (for all contracts) exceeds a threshold, e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Select &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
==== Flag Manually ====&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Carrying forward; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039;]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle on display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be painfully slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, etc.),&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=207</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=207"/>
		<updated>2026-10-03T22:34:58Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Complete importing and entering all sales records for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged active.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records, to lock-in the amounts for the next period.&lt;br /&gt;
# Generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Accessing the Royalties Menu ==&lt;br /&gt;
The steps below are activated via the crown popover available at the upper-right in Royalties list view.&lt;br /&gt;
== Step-by-step ==&lt;br /&gt;
&lt;br /&gt;
=== Complete Input of Sales Data ===&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since strictly PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
=== Ensure Correct Active Contract/Statements are Flagged to Calculate ===&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run, by checking the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checkbox. Unlike flagging statements to pay out for this period (see below), the the status of the &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
The functions to complete royalties are executed in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]These actions are performed only on the Found Set (the records currently showing in the list) and then only on those records in the Found Set with &#039;&#039;&#039;Calc Royalty&#039;&#039;&#039; checked. Statistics at the top of the popover describe how many records will be processed with the buttons.&lt;br /&gt;
&lt;br /&gt;
You have four ways to configure a Found Set to run the royalty buttons against:&lt;br /&gt;
&lt;br /&gt;
# load a Snapshot of Royalty records you have created previously (see [[Tags &amp;amp; Snapshots]] on how to create Snapshot sets)&lt;br /&gt;
# click the Show All Records buttons to do a complete off all Calc Royalty statements&lt;br /&gt;
# close the Bulk Royalty Actions popover, and used the Find box with criteria to generate a Found Set of records you want to process&lt;br /&gt;
# close the Bulk Royalty Actions popover, and Tag the records you want, and show only the tagged records you want to process (see [[Tags &amp;amp; Snapshots]] on how to Tag records)&lt;br /&gt;
&lt;br /&gt;
=== Flag Statements to Pay Out ===&lt;br /&gt;
Statements default to not being paid out. You&#039;ll notice that initially, all statements are carrying over the earned amount to the next period. You can flag these either manually or automatically.&lt;br /&gt;
&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
PubGizmo can auto-flag for payout any active contract where the amount owing to the author (for all contracts) exceeds a threshold, e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Select &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
==== Flag Manually ====&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Carrying forward; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039;]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle on display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be painfully slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, etc.),&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=206</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=206"/>
		<updated>2026-10-02T00:28:45Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Complete importing and entering all sales records for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged active.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records, to lock-in the amounts for the next period.&lt;br /&gt;
# Generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Accessing the Royalties Menu ==&lt;br /&gt;
The steps below are activated via the crown popover available at the upper-right in Royalties list view.&lt;br /&gt;
== Step-by-step ==&lt;br /&gt;
&lt;br /&gt;
=== Complete Input of Sales Data ===&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sheets with sales during a royalty period imported after that royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since strictly PubGizmo filters the date range for the selected period to isolate sales for that period.&lt;br /&gt;
&lt;br /&gt;
=== The Bulk Royalty Actions Popover ===&lt;br /&gt;
The primary functions to complete royalties are located in a popover accessed using the royalties (crown) button available in the List View of the Royalties module.&lt;br /&gt;
[[File:Screenshot 2026-10-01 at 16.31.08.png|none|thumb|631x631px]]&lt;br /&gt;
&lt;br /&gt;
=== Ensure All Active Contract/Statements are Flagged to Calculate ===&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run. Unlike flagging statements to pay out for this period (see below), the the status of the Calc Royalty flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
=== Flag Statements to Pay Out ===&lt;br /&gt;
Statements default to not being paid out. You&#039;ll notice that initially, all statements are carrying over the earned amount to the next period. You can flag these either manually or automatically.&lt;br /&gt;
&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
PubGizmo can auto-flag for payout any active contract where the amount owing to the author (for all contracts) exceeds a threshold, e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Select &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
==== Flag Manually ====&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Carrying forward; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039;]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle on display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be painfully slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, etc.),&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=File:Screenshot_2026-10-01_at_16.31.08.png&amp;diff=205</id>
		<title>File:Screenshot 2026-10-01 at 16.31.08.png</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=File:Screenshot_2026-10-01_at_16.31.08.png&amp;diff=205"/>
		<updated>2026-10-01T23:31:36Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bulk Royalty Actions popover&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=204</id>
		<title>Running Royalties</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Running_Royalties&amp;diff=204"/>
		<updated>2026-10-01T02:11:27Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== The Process ==&lt;br /&gt;
Once all your data is in PubGizmo, you can run royalties. &amp;quot;Run&amp;quot; is a multi-step process.&lt;br /&gt;
&lt;br /&gt;
# Complete importing and entering all sales records for the royalty period.&lt;br /&gt;
# Ensure all relevant contracts are flagged active.&lt;br /&gt;
# Flag which statements to pay out; any not paid out will have their amounts carried forward.&lt;br /&gt;
# Compose (or edit) your stock messages, one for contract holders, and one for literary agents.&lt;br /&gt;
# Proof your statements, either in PubGizmo, or by generating a PDF.&lt;br /&gt;
# Generate email messages with the statement attached.&lt;br /&gt;
# Personalize those messages as you like, and send them.&lt;br /&gt;
# Generate payment records, to lock-in the amounts for the next period.&lt;br /&gt;
# Generate a spreadsheet that summarizes your royalties.&lt;br /&gt;
&lt;br /&gt;
== Accessing the Royalties Menu ==&lt;br /&gt;
The steps below are activated via the crown popover available at the upper-right in Royalties list view.&lt;br /&gt;
== Step-by-step ==&lt;br /&gt;
&lt;br /&gt;
=== Complete Input of Sales Data ===&lt;br /&gt;
Ensure all sales during the royalty period have been input. This means [[Importing Sales Data|importing all your sales sheets]], as well as inputting manually sales not covered by import.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Important:&#039;&#039;&#039; Any sales input after the royalty run is complete will &#039;&#039;never be counted&#039;&#039;, even in the next period, since PubGizmo uses the date range for the selected period to isolate sales for that period. If for example some sales in an imported sheet fall after the last day of the royalty period, they will be included in the subsequent period.&lt;br /&gt;
&lt;br /&gt;
=== Ensure All Active Contract/Statements are Flagged to Calculate ===&lt;br /&gt;
PubGizmo allows you flag active contracts, to determine if they get computed and included in your royalty run. Unlike flagging statements to pay out for this period (see below), the the status of the Calc Royalty flag persists through all royalty runs, i.e., contracts remain active or dormant/dead until you change them. You can set this flag in any of three locations:&lt;br /&gt;
&lt;br /&gt;
# on the Contract itself, at the upper-right,&lt;br /&gt;
# on Royalty form view,&lt;br /&gt;
# in Royalty list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; you can get a list of statements by their compute flag by entering either &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot; in the search box below the Royalties button on the Home screen, or at the top of the Royalties window.&lt;br /&gt;
&lt;br /&gt;
=== Flag Statements to Pay Out ===&lt;br /&gt;
Statements default to not being paid out. You&#039;ll notice that initially, all statements are carrying over the earned amount to the next period. You can flag these either manually or automatically.&lt;br /&gt;
&lt;br /&gt;
==== Flag Automatically ====&lt;br /&gt;
PubGizmo can auto-flag for payout any active contract where the amount owing to the author (for all contracts) exceeds a threshold, e.g., pay out only if the author is owed $25 or more, otherwise leave it unflagged, for the amount to carry over to the next royalty period (negative amounts always carry over).&lt;br /&gt;
&lt;br /&gt;
To auto-flag:&lt;br /&gt;
&lt;br /&gt;
# Set your threshold in Admin (bottom of main Admin screen).&lt;br /&gt;
# Open the Royalties Menu.&lt;br /&gt;
# Select &#039;&#039;&#039;Flag Eligible for Payout&#039;&#039;&#039;. &lt;br /&gt;
&lt;br /&gt;
==== Flag Manually ====&lt;br /&gt;
[[File:PayOutCheckbox.png|thumb|Carrying forward; check the box to &#039;&#039;&#039;Pay Out 2023&#039;&#039;&#039;]]You can flag records manually by clicking the checkbox on the statement record itself, or in list view.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Hint:&#039;&#039;&#039; in Royalty list view, you can see the Statement Amount for all listed records by clicking the header. That will toggle on display of the amounts. This setting is off by default, because it requires PubGizmo to compute royalties for every statement in the list, which can be painfully slow. Click the header again to turn off this display.&lt;br /&gt;
&lt;br /&gt;
=== Compose or Edit Stock Messages ===&lt;br /&gt;
For bulk-sending royalty statements, PubGizmo offers two stock messages:&lt;br /&gt;
&lt;br /&gt;
# contractee (author, etc.),&lt;br /&gt;
# literary agent of record for the contract, if relevant.&lt;br /&gt;
&lt;br /&gt;
==== Merge Tags ====&lt;br /&gt;
Message text is merged with recipient data at the time the message is sent. The subject and body text of these messages are set in &#039;&#039;&#039;Administration &amp;gt; Bulk Mail Templates&#039;&#039;&#039; tab. The templates include a number of merge tags, each enclosed in &amp;quot;&amp;lt;&amp;quot; and &amp;quot;&amp;gt;&amp;quot;, into which relevant data is substituted at the time the message is composed. These tags include:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Year&amp;gt;&#039;&#039;&#039; The royalty year, if your press uses the calendar year for statement period, otherwise the start and end dates of the royalty period.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Title&amp;gt;&#039;&#039;&#039; The book&#039;s title, or titles, if the author has multiple active contracts, in a comma-delimited list (Title1, Title2, etc.).&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;GreetingName&amp;gt;&#039;&#039;&#039; The value in the Correspondence Name field on the recipients Contact record (defaults to the contact&#039;s first name, but can be edited). For Organization contractees, this will attempt to use the email address of the Org&#039;s rep, if defined on the Contract, otherwise it will use the Org name.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Artist&amp;gt;&#039;&#039;&#039; The contractee&#039;s first and last name. Note: in the Agent email, this will substitute with the phrase &amp;quot;(refer to attached PDF)&amp;quot;.&lt;br /&gt;
* &#039;&#039;&#039;&amp;lt;Address&amp;gt;&#039;&#039;&#039; Recipient&#039;s mailing address in one line.&lt;br /&gt;
&lt;br /&gt;
==== Contractees/Agents With Multiple Statements ====&lt;br /&gt;
Rather than sending out multiple individual statements to an author, PubGizmo &amp;quot;rolls up&amp;quot; statements, that is, gathers all relevant statements into a single PDF, and attaches them to one email message, under these circumstances:&lt;br /&gt;
&lt;br /&gt;
* author/contractee has multiple active contracts&lt;br /&gt;
* literary agent is agent-of-record on multiple active contracts&lt;br /&gt;
&lt;br /&gt;
=== Proof the Statements ===&lt;br /&gt;
Important! You should examine every statement before it is sent. You can do this in two different ways:&lt;br /&gt;
&lt;br /&gt;
# &#039;&#039;&#039;On Screen:&#039;&#039;&#039; page through statements using the arrow buttons at the upper-left (slower)&lt;br /&gt;
# &#039;&#039;&#039;Generate a PDF:&#039;&#039;&#039; create a single PDF with all the statements (faster)&lt;br /&gt;
To generate a PDF, select &#039;&#039;&#039;PDF Found Statements&#039;&#039;&#039; (will generate a PDF containing only those Royalty records in the found set), or &#039;&#039;&#039;PDF All Calc Statements&#039;&#039;&#039; (PDF containing all statements with the Calculate Royalty flag active). The PDF is saved to your desktop.&lt;br /&gt;
&lt;br /&gt;
=== Send the Statements ===&lt;br /&gt;
When you select &#039;&#039;&#039;Bulk Email Statements&#039;&#039;&#039;, PubGizmo generates draft email messages (it does not send them) addressed to the contractee&#039;s primary email address (as configured on their Contact record), with the statement attached, and similarly generates draft email messages to literary agents. Your default email program must be Mac Mail if you are on macOS, or Outlook if you use Windows (let us know if you use something else).&lt;br /&gt;
&lt;br /&gt;
You can customize the email message as you like, and send each individually.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;&#039;Create Payment Records&#039;&#039;&#039; ===&lt;br /&gt;
This step &amp;quot;locks in&amp;quot; the amounts, such as the advance remaining and carry-forward values, which inform calculations for your next royalty run.&lt;br /&gt;
&lt;br /&gt;
Important notes:&lt;br /&gt;
&lt;br /&gt;
# All of the steps above must be fully complete (all sales records imported, appropriate records set to calculate and pay-out, statements fully proofed) before you complete this stage. If you change anything for the current period, you will have to create the Payment records again.&lt;br /&gt;
# You must complete this step for each royalty period before running the subsequent one, because important values (e.g., Advance Remaining) are carried over via Payment records. Your next period will be inaccurate if the previous period&#039;s Payment records have not been generated.&lt;br /&gt;
# If you have created any Payment records previously and try to do so again, PubGizmo will warn you that records already exist, and they will be deleted and new ones generated. This is fine: the new Payment records will be created using the latest royalties data.&lt;br /&gt;
&lt;br /&gt;
=== CSV Export ===&lt;br /&gt;
Generate on your desktop a CSV (spreadsheet, can be opened in Excel), which summarizes the statements. You can provide this to your accountant.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Tags_%26_Snapshots&amp;diff=203</id>
		<title>Tags &amp; Snapshots</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Tags_%26_Snapshots&amp;diff=203"/>
		<updated>2026-10-01T01:59:04Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags &amp;amp; Snapshots offer a way to save and share groups of records and return to them later, and to perform bulk actions like emailing sets of royalty statements. This can be especially useful if you want to create groups of Contacts for bulk emailing, or if you want to break up the full set of Royalties you need to process into smaller units.&lt;br /&gt;
&lt;br /&gt;
== Controls ==&lt;br /&gt;
Functions to control Tags &amp;amp; Snapshots can be performed using the menus at the bottom of List View in the Contacts and Royalties modules.&lt;br /&gt;
[[File:Screenshot 2026-09-17 at 17.40.05.png|none|thumb|700x700px]]&lt;br /&gt;
&lt;br /&gt;
== Tags ==&lt;br /&gt;
Tags are temporary, in that they persist only for the duration of your session. All tagged records are untagged when you log out. (If you have records tagged when you close or log out of PubGizmo, you&#039;ll be warned they will be lost if you continue.)&lt;br /&gt;
&lt;br /&gt;
Tags allow for easy flagging of records you want to perform actions on during the session. You can tag groups of records (e.g., you did a find which resulted in a Found Set of a dozen records, and you want to reload that Found Set later in the session without conducting the find again), or you can tag records one at a time by clicking the Tag button, in either Form or List view.&lt;br /&gt;
&lt;br /&gt;
==== Tagging One Record ====&lt;br /&gt;
To Tag a single record, click the tag button. It will turn purple. Click again to untag.[[File:Sep-17-2026 17-35-21.gif|thumb|none]]&lt;br /&gt;
&lt;br /&gt;
==== Tagging a Group of Records ====&lt;br /&gt;
You can tag all the records in a Found Set by using the Tags... menu at the foot of the List View window. Your options are:&lt;br /&gt;
&lt;br /&gt;
* Tag Found Records: tag all the records in the Found Set&lt;br /&gt;
* Untag Found Records: any tagged records showing in the Found Set will be untagged&lt;br /&gt;
* Show All Tagged: replace the current Found Set with a set of all the tagged records in this module&lt;br /&gt;
* Hide All Tagged: you can limit your Found Set by tagging the records you want to remove and selecting this option&lt;br /&gt;
&lt;br /&gt;
== Snapshots ==&lt;br /&gt;
Snapshots persist as named sets: they will be there next time you log in to PubGizmo. You can edit them too: add or remove records as needed. And you can  share them with other members of your team, so one user can assemble a Snapshot and then share it with another user who will perform some action on it.&lt;br /&gt;
&lt;br /&gt;
=== Module Footer Controls ===&lt;br /&gt;
Snapshots are more sophisticated than Tags, and include two selectors in the module&#039;s List View footer (shown above under Controls for Tags).&lt;br /&gt;
&lt;br /&gt;
===== Snapshot Selector =====&lt;br /&gt;
The first is for selecting the snapshot you want to work with, and shows &amp;quot;Select Snapshot...&amp;quot; when no snapshot is loaded.&lt;br /&gt;
&lt;br /&gt;
===== Action Selector =====&lt;br /&gt;
The second button, &amp;quot;Snapshot Action...&amp;quot; is where you decide what to do with the loaded Snapshot. What&#039;s available in this menu depends on what&#039;s showing in the Snapshot Selector.&lt;br /&gt;
&lt;br /&gt;
====== Shows &amp;quot;Snapshot Action...&amp;quot; ======&lt;br /&gt;
When no Snapshot is selected, you only have one option: create a new Snapshot from the records in the Found Set, provided the Found Set is not all the records in the module. This is because it makes no sense to create a Snapshot of every record. You must have narrowed the Found Set to create a Snapshot from it. This usually means you&#039;ve performed a [[QuickDex Helps with Finds|Find]] which has yielded a Found Set of records, for example, you could enter an author&#039;s name which will yield a Found Set of all that author&#039;s statements, and then create a Snapshot named after that author. &lt;br /&gt;
&lt;br /&gt;
You can also Tag records and then use the Tags... menu item &amp;quot;Show All Tagged&amp;quot; to limit your Found Set to just those records.&lt;br /&gt;
&lt;br /&gt;
====== Shows a Snapshot Name ======&lt;br /&gt;
If the Snapshot Selector displays a Snapshot name, use the Action Selector to load the Snapshot you selected under the Snapshot Selector button by selecting &amp;quot;LOAD snapshot &amp;lt;snapshot name&amp;gt;&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The Found Set you are looking at in List View is replaced with the records that comprise the named Snapshot. So if you created a Royalties Snapshot named &amp;quot;Still to do&amp;quot;  containing 18 Royalty records (perhaps after you&#039;ve done most of your Royalties, and there are stragglers you collected into a Snapshot), you will after you load &amp;quot;Still to do&amp;quot; be left with a Found Set of those 18 records.&lt;br /&gt;
&lt;br /&gt;
If a Snapshot name is showing in the Snapshot Selector, you have more options: you can create a new Snapshot, or you can add records to or remove from the records in the current Found Set. In this way you can either build up a Snapshot by doing repeated finds to create Found Sets to add to the Snapshot, or you can pare down the Snapshot by removing records. Remember, you can fine-tune your Found Set by using Tags, e.g., by flagging the records you want, selecting Show All Tagged, and adding them to an existing Snapshot. You can remove records from a Snapshot in the same way.&lt;br /&gt;
&lt;br /&gt;
=== Home Screen Controls ===&lt;br /&gt;
[[File:Screenshot_2026-09-21_at_17.55.49.png|right|frameless|550x550px]]&lt;br /&gt;
The panel on the right side of the Home screen provides a suite of controls for Snapshots. Here you can perform the following actions:&lt;br /&gt;
&lt;br /&gt;
* duplicate a Snapshot&lt;br /&gt;
* delete a Snapshot&lt;br /&gt;
* navigate to a Found List of all the records in the Snapshot in the relevant module – that is, &amp;quot;load&amp;quot; the Snapshot by clicking on the Snapshot name in the upper portal&lt;br /&gt;
&lt;br /&gt;
==== With a Snapshot Selected ====&lt;br /&gt;
You can select a Snapshot by clicking the target beside the name. Once selected, the lower portals will populate with that Snapshot&#039;s attributes, allowing further actions:&lt;br /&gt;
&lt;br /&gt;
* rename the Snapshot&lt;br /&gt;
* add a note – useful if sharing&lt;br /&gt;
* remove individual records from the Snapshot by clicking the trash can beside the record name&lt;br /&gt;
* navigate directly to a specific record in the Snapshot list by clicking on the record name&lt;br /&gt;
&lt;br /&gt;
* share the Snapshot with other PubGizmo users by highlighting their names in the Shared With portal&lt;br /&gt;
&lt;br /&gt;
When you share a Snapshot, the user you have shared it with will see the Snapshot on their Home screen panel and in modules just as you do. You remain the owner of the Snapshot; those who are sharing it cannot delete it, though they can duplicate it and make the copy their own.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Tags_%26_Snapshots&amp;diff=202</id>
		<title>Tags &amp; Snapshots</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Tags_%26_Snapshots&amp;diff=202"/>
		<updated>2026-10-01T01:57:26Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags &amp;amp; Snapshots offer a way to save and share groups of records and return to them later, and to perform bulk actions like emailing sets of royalty statements. This can be especially useful if you want to create groups of Contacts for bulk emailing, or if you want to break up the full set of Royalties you need to process into smaller units.&lt;br /&gt;
&lt;br /&gt;
== Tags ==&lt;br /&gt;
Tags are temporary, in that they persist only for the duration of your session. All tagged records are untagged when you log out. (If you have records tagged when you close or log out of PubGizmo, you&#039;ll be warned they will be lost if you continue.)&lt;br /&gt;
&lt;br /&gt;
Tags allow for easy flagging of records you want to perform actions on during the session. You can tag groups of records (e.g., you did a find which resulted in a Found Set of a dozen records, and you want to reload that Found Set later in the session without conducting the find again), or you can tag records one at a time by clicking the Tag button, in either Form or List view.&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
Functions to control Tags &amp;amp; Snapshots can be performed using the menus at the bottom of List View in the Contacts and Royalties modules.&lt;br /&gt;
[[File:Screenshot 2026-09-17 at 17.40.05.png|none|thumb|700x700px]]&lt;br /&gt;
&lt;br /&gt;
==== Tagging One Record ====&lt;br /&gt;
To Tag a record, click the tag button. It will turn purple. Click again to untag.[[File:Sep-17-2026 17-35-21.gif|thumb|none]]&lt;br /&gt;
&lt;br /&gt;
==== Tagging a Group of Records ====&lt;br /&gt;
You can tag all the records in a Found Set by using the Tags... menu at the foot of the List View window. Your options are:&lt;br /&gt;
&lt;br /&gt;
* Tag Found Records: tag all the records in the Found Set&lt;br /&gt;
* Untag Found Records: any tagged records showing in the Found Set will be untagged&lt;br /&gt;
* Show All Tagged: replace the current Found Set with a set of all the tagged records in this module&lt;br /&gt;
* Hide All Tagged: you can limit your Found Set by tagging the records you want to remove and selecting this option&lt;br /&gt;
&lt;br /&gt;
== Snapshots ==&lt;br /&gt;
Snapshots persist as named sets: they will be there next time you log in to PubGizmo. You can edit them too: add or remove records as needed. And you can  share them with other members of your team, so one user can assemble a Snapshot and then share it with another user who will perform some action on it.&lt;br /&gt;
&lt;br /&gt;
=== Module Footer Controls ===&lt;br /&gt;
Snapshots are more sophisticated than Tags, and include two selectors in the module&#039;s List View footer (shown above under Controls for Tags).&lt;br /&gt;
&lt;br /&gt;
===== Snapshot Selector =====&lt;br /&gt;
The first is for selecting the snapshot you want to work with, and shows &amp;quot;Select Snapshot...&amp;quot; when no snapshot is loaded.&lt;br /&gt;
&lt;br /&gt;
===== Action Selector =====&lt;br /&gt;
The second button, &amp;quot;Snapshot Action...&amp;quot; is where you decide what to do with the loaded Snapshot. What&#039;s available in this menu depends on what&#039;s showing in the Snapshot Selector.&lt;br /&gt;
&lt;br /&gt;
====== Shows &amp;quot;Snapshot Action...&amp;quot; ======&lt;br /&gt;
When no Snapshot is selected, you only have one option: create a new Snapshot from the records in the Found Set, provided the Found Set is not all the records in the module. This is because it makes no sense to create a Snapshot of every record. You must have narrowed the Found Set to create a Snapshot from it. This usually means you&#039;ve performed a [[QuickDex Helps with Finds|Find]] which has yielded a Found Set of records, for example, you could enter an author&#039;s name which will yield a Found Set of all that author&#039;s statements, and then create a Snapshot named after that author. &lt;br /&gt;
&lt;br /&gt;
You can also Tag records and then use the Tags... menu item &amp;quot;Show All Tagged&amp;quot; to limit your Found Set to just those records.&lt;br /&gt;
&lt;br /&gt;
====== Shows a Snapshot Name ======&lt;br /&gt;
If the Snapshot Selector displays a Snapshot name, use the Action Selector to load the Snapshot you selected under the Snapshot Selector button by selecting &amp;quot;LOAD snapshot &amp;lt;snapshot name&amp;gt;&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The Found Set you are looking at in List View is replaced with the records that comprise the named Snapshot. So if you created a Royalties Snapshot named &amp;quot;Still to do&amp;quot;  containing 18 Royalty records (perhaps after you&#039;ve done most of your Royalties, and there are stragglers you collected into a Snapshot), you will after you load &amp;quot;Still to do&amp;quot; be left with a Found Set of those 18 records.&lt;br /&gt;
&lt;br /&gt;
If a Snapshot name is showing in the Snapshot Selector, you have more options: you can create a new Snapshot, or you can add records to or remove from the records in the current Found Set. In this way you can either build up a Snapshot by doing repeated finds to create Found Sets to add to the Snapshot, or you can pare down the Snapshot by removing records. Remember, you can fine-tune your Found Set by using Tags, e.g., by flagging the records you want, selecting Show All Tagged, and adding them to an existing Snapshot. You can remove records from a Snapshot in the same way.&lt;br /&gt;
&lt;br /&gt;
=== Home Screen Controls ===&lt;br /&gt;
[[File:Screenshot_2026-09-21_at_17.55.49.png|right|frameless|550x550px]]&lt;br /&gt;
The panel on the right side of the Home screen provides a suite of controls for Snapshots. Here you can perform the following actions:&lt;br /&gt;
&lt;br /&gt;
* duplicate a Snapshot&lt;br /&gt;
* delete a Snapshot&lt;br /&gt;
* navigate to a Found List of all the records in the Snapshot in the relevant module – that is, &amp;quot;load&amp;quot; the Snapshot by clicking on the Snapshot name in the upper portal&lt;br /&gt;
&lt;br /&gt;
==== With a Snapshot Selected ====&lt;br /&gt;
You can select a Snapshot by clicking the target beside the name. Once selected, the lower portals will populate with that Snapshot&#039;s attributes, allowing further actions:&lt;br /&gt;
&lt;br /&gt;
* rename the Snapshot&lt;br /&gt;
* add a note – useful if sharing&lt;br /&gt;
* remove individual records from the Snapshot by clicking the trash can beside the record name&lt;br /&gt;
* navigate directly to a specific record in the Snapshot list by clicking on the record name&lt;br /&gt;
&lt;br /&gt;
* share the Snapshot with other PubGizmo users by highlighting their names in the Shared With portal&lt;br /&gt;
&lt;br /&gt;
When you share a Snapshot, the user you have shared it with will see the Snapshot on their Home screen panel and in modules just as you do. You remain the owner of the Snapshot; those who are sharing it cannot delete it, though they can duplicate it and make the copy their own.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=QuickDex_Helps_with_Finds&amp;diff=201</id>
		<title>QuickDex Helps with Finds</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=QuickDex_Helps_with_Finds&amp;diff=201"/>
		<updated>2026-09-29T02:02:28Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Finding Individual or Groups of Records ==&lt;br /&gt;
You can find records in PubGizmo by entering search terms in the relevant search boxes, but it helps to know there are two types of searches, one fast (QuickDex), and one slow (basic), and usually the fast/QuickDex search will serve your needs.&lt;br /&gt;
&lt;br /&gt;
== Search Boxes ==&lt;br /&gt;
You&#039;ll find multiple locations where you can type data to perform finds; we call these &amp;quot;search boxes.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
==== Home Screen ====&lt;br /&gt;
Each major module includes a search box, where you can search within that particular module.&lt;br /&gt;
&lt;br /&gt;
==== Top of Module ====&lt;br /&gt;
At the top of the single record and list view for each module you will find a search box for that specific module.&lt;br /&gt;
&lt;br /&gt;
== Search Types and Responsiveness ==&lt;br /&gt;
Both types of searches are conducted the same way: by clicking into a search box, type you search criteria, and hit &amp;lt;return&amp;gt; or &amp;lt;tab&amp;gt; to execute the search. However, how the system responds to your tying determines whether the search will be fast or slow.&lt;br /&gt;
&lt;br /&gt;
=== Autofilling ===&lt;br /&gt;
Just like entering search terms in Google, PubGizmo autofills matches as you type, but in this case, the matches are not for the entity alone, e.g., the title, but also for associated data and metadata about that entity. A host of terms are assigned to each record and assembled into a special index called the QuickDex. When you type, and it auto-fills, you are seeing data from the QuickDex.&lt;br /&gt;
[[File:QuickDex autofill.png|thumb|I typed &amp;quot;a&amp;quot; and the rest auto-filled]]&lt;br /&gt;
If you start typing a title, the QuickDex will autofill titles that match what you&#039;ve typed so far. The results will refine as you continue typing. For example, if you have multiple books that start with &amp;quot;a&amp;quot;, the first match will appear when you type the &amp;quot;a&amp;quot;, but as you continue to type more of the title, the results will come closer to your match.&lt;br /&gt;
&lt;br /&gt;
&amp;quot;A Tidy Armageddon&amp;quot; is only the first result. Click the arrow on the right of the search field to yield a list of all matches.&lt;br /&gt;
&lt;br /&gt;
Keep typing to focus your result. If you are actually looking for all the titles by the other &amp;quot;Arthur Calvin,&amp;quot; keep typing the name; the results will become more precise as you type more.&lt;br /&gt;
&lt;br /&gt;
==== Fast Results ====&lt;br /&gt;
When you use the QuickDex to search, the results are yielded quickly, because PubGizmo &amp;quot;knows&amp;quot; which records you want, without having to dig through all the records in the system to find matches for your search term(s).&lt;br /&gt;
&lt;br /&gt;
If you type something that doesn&#039;t autofill, or stops autofilling, i.e., if you go beyond the matches offered as you type, PubGizmo has to work harder to search on your criteria.&lt;br /&gt;
&lt;br /&gt;
Briefly, searching on an auto-filled term will be fast, typing something that doesn&#039;t auto-fill, or stops auto-filling as your type, will be slow.&lt;br /&gt;
&lt;br /&gt;
== QuickDex (fast) ==&lt;br /&gt;
You can tell what data is QuickDexed for each record by hovering over the the module entity&#039;s name, (e.g., in Titles, hover over the title at the top, in blue), to see the contents of that record&#039;s QuickDex, and therefore how you can find this record using a QuickDex find.&lt;br /&gt;
[[File:QuickDex Hover2.png|none|thumb|800x800px|Hover over Title to reveal QuickDex]]&lt;br /&gt;
You can yield multiple results with a search on something like the genre, for example, if you have multiple records classified as &amp;quot;fiction,&amp;quot; you will see as you type in the search box, &amp;quot;fiction&amp;quot; as en entry. When you execute the find, all Titles that are classified as fiction will appear.&lt;br /&gt;
&lt;br /&gt;
==== Title ====&lt;br /&gt;
Currently, a Title&#039;s QuickDex includes:&lt;br /&gt;
&lt;br /&gt;
* Title (with or without the article)&lt;br /&gt;
* Subtitle&lt;br /&gt;
* Contractees (author, translator, licensing orgs)&lt;br /&gt;
* Genre(s)&lt;br /&gt;
* Keyword(s)&lt;br /&gt;
* Year of Publication&lt;br /&gt;
* ISBNs&lt;br /&gt;
&lt;br /&gt;
==== Royalty ====&lt;br /&gt;
The QuickDex varies by module. For example, the QuickDex for Royalties is different than for Titles.:&lt;br /&gt;
&lt;br /&gt;
* Title&lt;br /&gt;
* Contractees (Contacts or Orgs)&lt;br /&gt;
* Agents&lt;br /&gt;
* Agencies&lt;br /&gt;
* Payout Periods (e.g., records flagged to payout in 2024 only)&lt;br /&gt;
* &amp;quot;calc&amp;quot; or &amp;quot;nocalc&amp;quot;: records with the Calculate Royalty box checked, or those set not to&lt;br /&gt;
&lt;br /&gt;
== Basic (slow) ==&lt;br /&gt;
You can type terms into the search box to search in the relevant module. For example, you could type the word &amp;quot;world&amp;quot; in the search box for Titles, and find all the books with &amp;quot;world&amp;quot; in the title, or with &amp;quot;world&amp;quot; in any of several other fields:&lt;br /&gt;
&lt;br /&gt;
* any Description&lt;br /&gt;
* any Blurb&lt;br /&gt;
* any Review&lt;br /&gt;
* Document&lt;br /&gt;
* Awards&lt;br /&gt;
&lt;br /&gt;
The search is slow because it involves searching multiple fields, some of them not directly on the record (what we call related records), and therefore not &amp;quot;indexed.&amp;quot;&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Handling_Slow_Access_and_Crashes&amp;diff=200</id>
		<title>Handling Slow Access and Crashes</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Handling_Slow_Access_and_Crashes&amp;diff=200"/>
		<updated>2026-09-28T18:47:48Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: /* Poor Network Connection */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Help! PubGizmo/FileMaker Pro is Slow/Crashing! ==&lt;br /&gt;
Both slowness and crashing are frustrating occurrences, and we are sorry for these experiences. There can be a variety of causes, some of which are us, some of which are you, and some to chalk up to the mysteries of computers and networks.&lt;br /&gt;
&lt;br /&gt;
== Background: How PubGizmo Works ==&lt;br /&gt;
As a sidebar, it helps to isolate your issue if you understand how PubGizmo operates. This is somewhat technical, so you can skip it if you just want suggestions to help with your problem.&lt;br /&gt;
&lt;br /&gt;
=== PubGizmo Runs Within FileMaker Pro ===&lt;br /&gt;
PubGizmo runs under FileMaker Pro in somewhat the same way a Word document runs under Microsoft Word, except that PubGizmo&#039;s data is located on a server (computer) in the cloud (connected to the internet), which in a way makes it more like a Google Sheet (which is why multiple users can use PubGizmo at the same time).&lt;br /&gt;
&lt;br /&gt;
=== Getting Data and Making Changes ===&lt;br /&gt;
You use FileMaker Pro on your computer to access it on the server where it is hosted, and data moves back and forth between your computer and the server. For example, when you open a Title record, PubGizmo tells FileMaker Pro to communicate to FileMaker Server in the cloud to fetch all the Title data, and display it for you. When you make a change, e.g., you add a subtitle or keyword, the data gets sent back to the server and written to the record. Changes are immediate.&lt;br /&gt;
&lt;br /&gt;
==== Moving Data Takes Time ====&lt;br /&gt;
It&#039;s important to understand that moving data takes time. The more data you&#039;re moving, the longer it takes.&lt;br /&gt;
&lt;br /&gt;
==== Computation Adds Complexity ====&lt;br /&gt;
If the data requires computation, like calculating royalty amounts, that increases the time required, especially if you are running a complex calculation, such as escalation.&lt;br /&gt;
&lt;br /&gt;
==== &amp;quot;Expense&amp;quot; ====&lt;br /&gt;
We talk about the factors of data volume and computational strain in terms of &amp;quot;expense.&amp;quot; It is &#039;&#039;expensive&#039;&#039;, in terms of computational power and data mobility, to run a hard calc on a ton of data.&lt;br /&gt;
&lt;br /&gt;
Imagine a briskly selling book, with many sales records. Each record is a piece of data, and when you open a Royalty Statement, all that data has to be collated, and then the royalty calculations must be run. A book with a 1000 sales involves 10 times more data than one with 100 sales.&lt;br /&gt;
&lt;br /&gt;
Add a complex calculation, specifically escalation, and it&#039;s a recipe for slow access, so slow, in fact, that it may appear to be a crash (when really it&#039;s a freeze, which will respond, given time – see below).&lt;br /&gt;
&lt;br /&gt;
=== Factors That Affect Speed ===&lt;br /&gt;
Many factors affect the speed of your PubGizmo experience, some of which are controllable, and some which are not:&lt;br /&gt;
&lt;br /&gt;
* volume of data being accessed and moved&lt;br /&gt;
* complexity of calculations&lt;br /&gt;
* your internet speed (provider, and also your connection to your router – bad WiFi can slow you down)&lt;br /&gt;
* your distance from the server (i.e., distance from either Toronto or Vancouver, depending on which server your solution is hosted)&lt;br /&gt;
* your computer&#039;s speed (physically, and depending on the state of its operating system) &lt;br /&gt;
* PubGizmo programming efficiency – how PG is built to handle data. We are making frequent improvements by running calculations on the server (which is quicker, since data need not transit between the server and your computer; an example is import processing – we run this on the server, which is what is happening when you see that an import is &amp;quot;PENDING&amp;quot;), and by caching and pre-calculating data.&lt;br /&gt;
&lt;br /&gt;
== Is it a Crash or a Freeze? ==&lt;br /&gt;
We should distinguish between a crash and a freeze. These are different events, and require different handling.&lt;br /&gt;
&lt;br /&gt;
=== Crash ===&lt;br /&gt;
A crash means FileMaker Pro has quit. All windows have disappeared from the screen. There&#039;s no spinning beachball, no hourglass.&lt;br /&gt;
&lt;br /&gt;
On a Mac, you&#039;ll usually receive a dialogue that tells you FileMaker Pro has crashed, with a few options: re-open, report the problem to Apple, or cancel. If you look at the [https://support.apple.com/en-ca/guide/mac-help/mh35859/mac Dock], the icon is gone, or, if you keep the icon in the Dock, there&#039;s no black dot below the icon to indicate it&#039;s running.&lt;br /&gt;
&lt;br /&gt;
On Windows, it no longer appears on the [https://support.microsoft.com/en-us/windows/how-to-use-the-taskbar-in-windows-0657a50f-0cc7-dbfd-ae6b-05020b195b07#:~:text=Typically%2C%20the%20taskbar%20is%20at,the%20top%20of%20the%20desktop. Taskbar]. If you look at the [[wikihow:Open-Windows-Task-Manager#:~:text=Press%20Ctrl%20%2B%20Shift%20%2B%20Esc%20to,and%20select%20%22Task%20Manager.%22|Task Manager]], FileMaker does not appear. Note that a message indicating FileMaker has stopped responding could be crash, but it could also be a freeze, per below.&lt;br /&gt;
&lt;br /&gt;
=== Freeze ===&lt;br /&gt;
If FileMaker Pro is still running but unresponsive, it has frozen or stalled. There&#039;s a good chance it&#039;s still alive, but it has stalled, or is hesitating, possibly because it is:&lt;br /&gt;
&lt;br /&gt;
# running a complex calculation&lt;br /&gt;
# attempting to fetch a large volume of data from the server to display, or to calculate&lt;br /&gt;
# struggling to negotiate a bad network connection&lt;br /&gt;
# impeded by your computer&#039;s speed&lt;br /&gt;
# struggling with a heavy server load (unlikely)&lt;br /&gt;
&lt;br /&gt;
==== Wait it Out ====&lt;br /&gt;
In this situation, you may just have to wait for PG to yield data and update – give it a chance to complete its processes, and your results will appear. It can take many seconds, or even many minutes, in extreme cases, to respond. Take a breath, take a break, make a cup of tea.&lt;br /&gt;
&lt;br /&gt;
===== Data Volume and/or Complexity =====&lt;br /&gt;
Frequently, the nature of the operation you are trying to perform, or the volume or complexity of data you are trying to access, will help you understand why the freeze is happening. &lt;br /&gt;
&lt;br /&gt;
For reference, these operations will be slow: &lt;br /&gt;
&lt;br /&gt;
* Opening royalty statements with escalation and/or lots of sales records&lt;br /&gt;
* Using the Reporter with many of record selected, or covering a large span of time&lt;br /&gt;
* Viewing records in List View, especially Royalties if the amount column is toggled on (PG must calculate royalties for all the statements in the view, which invokes hundreds or even thousands of calculations).&lt;br /&gt;
If some records are predictably quick, and others are predictably slow, e.g., &amp;quot;I know when I open this Royalty Statement it always takes a while,&amp;quot; you know that things are operating normally (even if waiting sucks), because there&#039;s a consistency to the slowness.&lt;br /&gt;
&lt;br /&gt;
== What to Do ==&lt;br /&gt;
&lt;br /&gt;
=== Crashes ===&lt;br /&gt;
&lt;br /&gt;
==== Isolated ====&lt;br /&gt;
An isolated crash can be dismissed as a one-off. Computers crash, software crashes – we don&#039;t always know why. Just re-open FileMaker, connect to PubGizmo, and continue where you left off.&lt;br /&gt;
&lt;br /&gt;
==== Chronic ====&lt;br /&gt;
If you are suffering chronic, not infrequent crashes, something more serious is going on. There are a host of possible causes, and solutions:&lt;br /&gt;
&lt;br /&gt;
===== Computer Problem =====&lt;br /&gt;
Do other programs also crash? If yes, then the problem lies with your computer, either the hardware or your operating system. Windows is more prone to this kind of issue that macOS. The best bet with either is a complete wipe and reinstall of your computer; it&#039;s not a trivial task, but it can yield significant improvements, not just in terms of stability, but also computer performance. You can find on various tech sites information on how to perform a wipe and reinstall. The most important step is to back up your data, since the &amp;quot;wipe&amp;quot; part involves deleting everything on your computer.&lt;br /&gt;
&lt;br /&gt;
If your problems survive a wipe/reinstall, it could be an issue with your computer hardware, for example, bad memory, a failing hard disk, overheating. This is best diagnosed by a professional.&lt;br /&gt;
&lt;br /&gt;
===== FileMaker Pro Application Problem =====&lt;br /&gt;
If only FileMaker crashes, uninstall it, and reinstall. This will ensure that your installation of FileMaker is not corrupt.&lt;br /&gt;
&lt;br /&gt;
=== Freezes ===&lt;br /&gt;
&lt;br /&gt;
==== All Records, Operations ====&lt;br /&gt;
If you experience freezes (PubGizmo eventually responds), and it doesn&#039;t seem to matter what you&#039;re looking at (e.g., just a basic Contact record), something is impeding the exchange of information between your computer and the data on the server. This could be:&lt;br /&gt;
&lt;br /&gt;
===== Poor Network Connection =====&lt;br /&gt;
If your internet is slow, access to PubGizmo will be slow. You can check your speed by going to [https://speedtest.net speedtest.net] and running a test. Faster is better, but at a minimum your up and down speeds should exceed 10 Mbps. Either or both of your internet provider speed or your network connection (e.g., on WiFi, but weak signal – get closer to the WiFi router!) can impede network traffic. If you rectify these issues, things may improve.&lt;br /&gt;
&lt;br /&gt;
====== Are You Far Away? ======&lt;br /&gt;
Wait, are you away, connecting from somewhere other than your press&#039;s location? Your speed/freeze issue may be due to network latency caused by distance. The physical server that hosts your solution is optimized for your press&#039;s physical location; we have two servers currently, and they are both in North America (Toronto and Vancouver), so if you&#039;re in Frankfurt, you are far away, and it takes longer for data to travel between your location and the server.&lt;br /&gt;
&lt;br /&gt;
===== Slow Computer =====&lt;br /&gt;
An old computer or a computer problem (corrupt OS, see above under &amp;quot;Computer Problem&amp;quot;) can impede access to PubGizmo.&lt;br /&gt;
&lt;br /&gt;
==== Some Records or Reports ====&lt;br /&gt;
Big sellers, or contracts with complicated clauses (escalation), or, worse-still, combinations of the two, will be slow to render. Try to limit your access to these records.&lt;br /&gt;
&lt;br /&gt;
== Improvements Coming ==&lt;br /&gt;
We have in our PubGizmo development plan a big update in the works that will cache sales data, instead of reading each sales record individually. This will yield a major performance improvement. Stay turned for updates.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=How_to_Use_PubGizmo&amp;diff=199</id>
		<title>How to Use PubGizmo</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=How_to_Use_PubGizmo&amp;diff=199"/>
		<updated>2026-09-22T23:53:21Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;While there are specific functions performed by each of PubGizmo&#039;s modules, there&#039;s a general convention on how to use features throughout. These gizmos and gadgets are helpful to know.&lt;br /&gt;
&lt;br /&gt;
== Documentation Covention ==&lt;br /&gt;
=== Capitalization ===&lt;br /&gt;
We capitalize record types; consider a word that seems oddly capitalized as if it is followed by the word &amp;quot;record.&amp;quot; For example, your press publishes a bunch of titles, but when we refer in documentation to those records in PubGizmo, we say &amp;quot;Titles,&amp;quot; meaning &amp;quot;title records,&amp;quot; e.g., &amp;quot;view that Title&amp;quot; means &amp;quot;view that title record.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
We also capitalize labels, and sometimes concepts. So when we refer to the &amp;quot;Keywords&amp;quot; field, it is capitalized because on the Title record you will see an actual label that reads &amp;quot;Keywords.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
=== Found Set ===&lt;br /&gt;
In PubGizmo your Found Set represents a subset of all the records in that module. Your Found Set varies depending on how you arrive at a record or records; for example, if you conduct a find for a Title which yields a single record, you have one record in your Found Set. But if you search the Titles module for all that are Genre = &amp;quot;poetry&amp;quot; of the poetry genre (by entering &amp;quot;poetry&amp;quot; in the search box – more on searches below), and 25 records are found, your Found Set = 25 records.&lt;br /&gt;
&lt;br /&gt;
You can see your Found Set record count by looking at the bottom-right of the window; here&#039;s what it looks like in Form View when viewing a single record:&lt;br /&gt;
[[File:Found set indicator.png|none|thumb|284x284px]]&lt;br /&gt;
&lt;br /&gt;
In this case, the found set is one record, and there are three records in total. &lt;br /&gt;
&lt;br /&gt;
List View (see below) will show you how many records are on view in the list, out of the total number of records, e.g., &amp;quot;7 of 659 Records.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
=== Tooltips ===&lt;br /&gt;
Some objects yield additional information when you hover your mouse pointer over them. Move the mouse pointer in place above the object and after a brief pause a box will appear with some text, such as:&lt;br /&gt;
&lt;br /&gt;
* explanation for a code or status, e.g., if something is red, hover to see why&lt;br /&gt;
* an action you can take on that object, e.g., check this box to indicate that the record is active&lt;br /&gt;
* on a field, it may yield the full contents of the field itself, e.g. if there&#039;s a chance the field cannot accommodate all the data&lt;br /&gt;
* a field hover may also provide additional info, e.g., the meaning of the code stored in the field&lt;br /&gt;
&lt;br /&gt;
== Portals ==&lt;br /&gt;
Portals are simply lists of data, each item in the list a record unto itself with multiple fields, frequently with green links to other records. You can edit data in portals is a number of ways, usually dependent on how many fields comprised that record:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;click and edit directly:&#039;&#039;&#039; click into the field and type&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;open a popover:&#039;&#039;&#039; a popover provides access to more fields than can be comfortably contained in the portal row, for example the description text for an author bio or book summary – you&#039;ll know a popover when you click, and it opens; to exit a popover, just click elsewhere, although a few popovers require you to click a button to close it.&lt;br /&gt;
== Understanding FileMaker Pro ==&lt;br /&gt;
&lt;br /&gt;
=== Your Copy of PubGizmo ===&lt;br /&gt;
Lots of presses use PubGizmo; each is hosted in an individual file or instance. All your data is self-contained and separate from the data of all other presses using PubGizmo. It cannot be seen or accessed by anyone without your account name and password. Keep these safe!&lt;br /&gt;
&lt;br /&gt;
=== PubGizmo Runs &amp;quot;Inside&amp;quot; FileMaker Pro ===&lt;br /&gt;
To access PubGizmo, you need to use [[wikipedia:FileMaker|FileMaker Pro]] (made by [https://claris.com Claris], owned by [https://apple.com Apple]) on your computer (Mac or Windows). Think of the relationship between FileMaker Pro and your copy of PubGizmo, containing all your press&#039;s Titles, Contacts, Sales Records, the way Microsoft Word is needed to open a Word document. PubGizmo is essentially a FileMaker Pro &amp;quot;document.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== PubGizmo &amp;quot;in the cloud&amp;quot; ===&lt;br /&gt;
Your copy of PubGizmo is hosted on a server on the internet, which means it&#039;s &amp;quot;in the cloud,&amp;quot; i.e., accessible from anywhere with an internet connection. So you can access it from your office, your home, or when travelling, e.g., from Frankfurt. Access speed diminishes with increased distance from your server (in Toronto or Vancouver), so if you are far away, access speed may be reduced. &lt;br /&gt;
&lt;br /&gt;
=== Committing Records ===&lt;br /&gt;
FileMaker Pro saves or &amp;quot;commits&amp;quot; records automatically once you exit all fields on that record. So if you change data in a field and click outside the field, the data is saved. You don&#039;t have to do anything else to save a record when you create it or make changes.&lt;br /&gt;
&lt;br /&gt;
==== No Undo ====&lt;br /&gt;
Immediate saving also means there&#039;s no &amp;quot;undo&amp;quot; once you&#039;ve committed or deleted a record. Be careful! If you do delete something critical, let us know ASAP so we can attempt a recovery.&lt;br /&gt;
&lt;br /&gt;
== PubGizmo Modules: Home Screen ==&lt;br /&gt;
&lt;br /&gt;
=== Module Buttons ===&lt;br /&gt;
Down the left side of the screen you will see module buttons.&lt;br /&gt;
&lt;br /&gt;
==== Main Button ====&lt;br /&gt;
Click a button to navigate to that module; you may arrive at a single record or a list of records, depending on the status of the Found Set (see above) currently active in that module.&lt;br /&gt;
&lt;br /&gt;
==== + Button ====&lt;br /&gt;
Click the &amp;quot;+&amp;quot; button (if present) to create a new record in that module; for example, to create a new Title record, click the + and a new record will be created, ready for data entry.&lt;br /&gt;
&lt;br /&gt;
==== Search Box ====&lt;br /&gt;
Search for a record in the module by typing in the box.  &lt;br /&gt;
&lt;br /&gt;
=== Session History ===&lt;br /&gt;
Whenever you visit a record, that visit gets recorded in the Session History on the Home screen. This list represents a map of everywhere you&#039;ve been, and since each record is a link, allows you to quickly return to any of those records by clicking it.&lt;br /&gt;
&lt;br /&gt;
==== Latest Visit Only ====&lt;br /&gt;
If you visit a record twice, you&#039;ll see that record only once in the Session History, showing the last visit timestamp. &lt;br /&gt;
&lt;br /&gt;
==== Retain History ====&lt;br /&gt;
You Session History is normally deleted when you logout, but you you can retain your history between sessions by clicking the Prefs button at the bottom-left and checking the &amp;quot;Retain Session History&amp;quot; box.&lt;br /&gt;
&lt;br /&gt;
=== Bookmarks ===&lt;br /&gt;
Bookmark records you use frequently, so you can navigate to them instantly from the Home screen. You bookmark a record by clicking the bookmark icon at the bottom-right of Form View records. The bookmark will turn red, and you&#039;ll be able to see and navigate to bookmarked records from the Home screen History portal.&lt;br /&gt;
&lt;br /&gt;
==== Removing Bookmarks ====&lt;br /&gt;
You can remove a bookmarked record one of two ways:&lt;br /&gt;
&lt;br /&gt;
# click the trash icon beside the record in the Bookmarks list; the record is retained – only the bookmark is removed&lt;br /&gt;
# click the bookmark icon on the record itself; it will switch from red to grey, and the record will no longer appear in the Bookmark portal on Home.&lt;br /&gt;
&lt;br /&gt;
=== Snapshots ===&lt;br /&gt;
Snapshots represents saved sets of records from selected modules. Information on their usefulness and use can be found at the page [[Tags &amp;amp; Snapshots]].&lt;br /&gt;
&lt;br /&gt;
== Form View and List View ==&lt;br /&gt;
You&#039;ll see records presented in two different ways:&lt;br /&gt;
&lt;br /&gt;
=== Form View ===&lt;br /&gt;
Form View presents a single record. When you conduct a search or click a button that yields a single record (one record in your Found Set), you will arrive at Form view of that record, with all of its data presented on a single layout.&lt;br /&gt;
&lt;br /&gt;
=== List View ===&lt;br /&gt;
List View shows you limited information about a collection of records. If you perform an operation that produces a found set with two or more records, they will be presented in List view. &lt;br /&gt;
&lt;br /&gt;
==== To Open a Single Record ====&lt;br /&gt;
In List View, open a record in the list by clicking it. The view will change to Form View of that record.&lt;br /&gt;
&lt;br /&gt;
Note however that your Found Set does not change when you enter Form View by clicking a record in List View. If you were viewing 12 records in List View, and you click on one, the record will open in List View, but the other records remain in the Found Set. You can use the left and right arrows at the upper-left of the screen to page through all the records in the Found Set.&lt;br /&gt;
&lt;br /&gt;
You can also return to List View of the Found Set by using the [[Three-Dot Menu]].&lt;br /&gt;
&lt;br /&gt;
=== Which View Do You Get? ===&lt;br /&gt;
In general PubGizmo uses the size of your Found Set to determine which view to send you to.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;one record in Found Set:&#039;&#039;&#039; Form View&lt;br /&gt;
* &#039;&#039;&#039;two or more records in Found Set:&#039;&#039;&#039; List View&lt;br /&gt;
&lt;br /&gt;
== Getting Around ==&lt;br /&gt;
&lt;br /&gt;
=== Clicking ===&lt;br /&gt;
&lt;br /&gt;
==== Buttons ====&lt;br /&gt;
Most of PubGizmo&#039;s navigation duplicates what you already do in software and on websites: click an item (only a single click is necessary) to go somewhere else. Click the Contact button to go to the Contacts module. Easy.&lt;br /&gt;
&lt;br /&gt;
==== Links ====&lt;br /&gt;
Also like the web, PubGizmo provides &amp;quot;links&amp;quot; that you can click to go to that target info. These links are created automatically as you add data; you don&#039;t need to do anything special.&lt;br /&gt;
&lt;br /&gt;
On the web, you can identify a link a couple of ways: it might be in blue, or underlined, or both.&lt;br /&gt;
&lt;br /&gt;
In PubGizmo, links are green: &amp;quot;green means go.&amp;quot; So if you are viewing a Contact record for an author, the Titles tab/portal shows all the Title records associated with this author in green. Click one to visit that Title record. In this case, if you click on the first green title:&lt;br /&gt;
[[File:Screenshot 2025-08-30 at 11.26.18.png|none|thumb|700x700px]]&lt;br /&gt;
You will navigate to that Title record.&lt;br /&gt;
&lt;br /&gt;
On the Title record, you&#039;ll see that the opposite end of this link will take you back to the author&#039;s record:&lt;br /&gt;
[[File:Link to Contacts from Title.png|none|thumb|300x300px]]&lt;br /&gt;
&lt;br /&gt;
== The Three-dot Menu ==&lt;br /&gt;
At the upper-left of every major module you&#039;ll see a green button with three vertical dots. Click it to reveal a number of options, which are slightly different depending on whether you are viewing a list of records or single record.&lt;br /&gt;
&lt;br /&gt;
==== Single Record ====&lt;br /&gt;
Here&#039;s the single record menu:[[File:Three-dot menu.png|none|thumb|342x342px]]Here are the options available from this menu:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Show List:&#039;&#039;&#039; switches from single record view to show a list of records in the module, showing all the records in the found set&lt;br /&gt;
* &#039;&#039;&#039;Show All Records:&#039;&#039;&#039; shows only if you have homed in on a single record in the found set; will also take you to&lt;br /&gt;
* &#039;&#039;&#039;NEW Record:&#039;&#039;&#039; creates a new record&lt;br /&gt;
* &#039;&#039;&#039;DELETE Record:&#039;&#039;&#039; deletes the current record – see notes below&lt;br /&gt;
* &#039;&#039;&#039;list of other modules:&#039;&#039;&#039; allows &amp;quot;cross-navigation&amp;quot; to another module, allowing you to bypass the Home screen&lt;br /&gt;
&lt;br /&gt;
==== List View ====&lt;br /&gt;
[[File:List three-dot menu.png|none|thumb|256x256px]]&lt;br /&gt;
&lt;br /&gt;
== Searching ==&lt;br /&gt;
You can also go to a specific record or set of records by searching, again much the way you do on the web, where what you type auto-completes as PubGizmo tries to anticipate what you&#039;re looking for. PubGizmo uses something called the QuickDex, which accelerates searches and navigation. Its use is more substantially covered on [[QuickDex Helps with Finds|this page]].&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=How_to_Use_PubGizmo&amp;diff=198</id>
		<title>How to Use PubGizmo</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=How_to_Use_PubGizmo&amp;diff=198"/>
		<updated>2026-09-22T23:50:38Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;While there are specific functions performed by each of PubGizmo&#039;s modules, there&#039;s a general convention on how to use features throughout. These gizmos and gadgets are helpful to know.&lt;br /&gt;
&lt;br /&gt;
== Documentation Covention ==&lt;br /&gt;
=== Capitalization ===&lt;br /&gt;
We capitalize record types; consider a word that seems oddly capitalized as if it is followed by the word &amp;quot;record.&amp;quot; For example, your press publishes a bunch of titles, but when we refer in documentation to those records in PubGizmo, we say &amp;quot;Titles,&amp;quot; meaning &amp;quot;title records,&amp;quot; e.g., &amp;quot;view that Title&amp;quot; means &amp;quot;view that title record.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
We also capitalize labels, and sometimes concepts. So when we refer to the &amp;quot;Keywords&amp;quot; field, it is capitalized because on the Title record you will see an actual label that reads &amp;quot;Keywords.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
== Terminology ==&lt;br /&gt;
&lt;br /&gt;
=== Found Set ===&lt;br /&gt;
In PubGizmo your Found Set represents a subset of all the records in that module. Your Found Set varies depending on how you arrive at a record or records; for example, if you conduct a find for a Title which yields a single record, you have one record in your Found Set. But if you search the Titles module for all that are Genre = &amp;quot;poetry&amp;quot; of the poetry genre (by entering &amp;quot;poetry&amp;quot; in the search box – more on searches below), and 25 records are found, your Found Set = 25 records.&lt;br /&gt;
&lt;br /&gt;
You can see your Found Set record count by looking at the bottom-right of the window:&lt;br /&gt;
[[File:Found set indicator.png|none|thumb|284x284px]]&lt;br /&gt;
&lt;br /&gt;
In this case, the found set is one record, and there are three records in total. &lt;br /&gt;
&lt;br /&gt;
=== Tooltips ===&lt;br /&gt;
Some objects yield additional information when you hover your mouse pointer over them. Move the mouse pointer in place above the object and after a brief pause a box will appear with some text, such as:&lt;br /&gt;
&lt;br /&gt;
* explanation for a code or status, e.g., if something is red, hover to see why&lt;br /&gt;
* an action you can take on that object, e.g., check this box to indicate that the record is active&lt;br /&gt;
* on a field, it may yield the full contents of the field itself, e.g. if there&#039;s a chance the field cannot accommodate all the data&lt;br /&gt;
* a field hover may also provide additional info, e.g., the meaning of the code stored in the field&lt;br /&gt;
&lt;br /&gt;
== Portals ==&lt;br /&gt;
Portals are simply lists of data, each item in the list a record unto itself with multiple fields, frequently with green links to other records. You can edit data in portals is a number of ways, usually dependent on how many fields comprised that record:&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;click and edit directly:&#039;&#039;&#039; click into the field and type&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;open a popover:&#039;&#039;&#039; a popover provides access to more fields than can be comfortably contained in the portal row, for example the description text for an author bio or book summary – you&#039;ll know a popover when you click, and it opens; to exit a popover, just click elsewhere, although a few popovers require you to click a button to close it.&lt;br /&gt;
== Understanding FileMaker Pro ==&lt;br /&gt;
&lt;br /&gt;
=== Your Copy of PubGizmo ===&lt;br /&gt;
Lots of presses use PubGizmo; each is hosted in an individual file or instance. All your data is self-contained and separate from the data of all other presses using PubGizmo. It cannot be seen or accessed by anyone without your account name and password. Keep these safe!&lt;br /&gt;
&lt;br /&gt;
=== PubGizmo Runs &amp;quot;Inside&amp;quot; FileMaker Pro ===&lt;br /&gt;
To access PubGizmo, you need to use [[wikipedia:FileMaker|FileMaker Pro]] (made by [https://claris.com Claris], owned by [https://apple.com Apple]) on your computer (Mac or Windows). Think of the relationship between FileMaker Pro and your copy of PubGizmo, containing all your press&#039;s Titles, Contacts, Sales Records, the way Microsoft Word is needed to open a Word document. PubGizmo is essentially a FileMaker Pro &amp;quot;document.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== PubGizmo &amp;quot;in the cloud&amp;quot; ===&lt;br /&gt;
Your copy of PubGizmo is hosted on a server on the internet, which means it&#039;s &amp;quot;in the cloud,&amp;quot; i.e., accessible from anywhere with an internet connection. So you can access it from your office, your home, or when travelling, e.g., from Frankfurt. Access speed diminishes with increased distance from your server (in Toronto or Vancouver), so if you are far away, access speed may be reduced. &lt;br /&gt;
&lt;br /&gt;
=== Committing Records ===&lt;br /&gt;
FileMaker Pro saves or &amp;quot;commits&amp;quot; records automatically once you exit all fields on that record. So if you change data in a field and click outside the field, the data is saved. You don&#039;t have to do anything else to save a record when you create it or make changes.&lt;br /&gt;
&lt;br /&gt;
==== No Undo ====&lt;br /&gt;
Immediate saving also means there&#039;s no &amp;quot;undo&amp;quot; once you&#039;ve committed or deleted a record. Be careful! If you do delete something critical, let us know ASAP so we can attempt a recovery.&lt;br /&gt;
&lt;br /&gt;
== PubGizmo Modules: Home Screen ==&lt;br /&gt;
&lt;br /&gt;
=== Module Buttons ===&lt;br /&gt;
Down the left side of the screen you will see module buttons.&lt;br /&gt;
&lt;br /&gt;
==== Main Button ====&lt;br /&gt;
Click a button to navigate to that module; you may arrive at a single record or a list of records, depending on the status of the Found Set (see above) currently active in that module.&lt;br /&gt;
&lt;br /&gt;
==== + Button ====&lt;br /&gt;
Click the &amp;quot;+&amp;quot; button (if present) to create a new record in that module; for example, to create a new Title record, click the + and a new record will be created, ready for data entry.&lt;br /&gt;
&lt;br /&gt;
==== Search Box ====&lt;br /&gt;
Search for a record in the module by typing in the box.  &lt;br /&gt;
&lt;br /&gt;
=== Session History ===&lt;br /&gt;
Whenever you visit a record, that visit gets recorded in the Session History on the Home screen. This list represents a map of everywhere you&#039;ve been, and since each record is a link, allows you to quickly return to any of those records by clicking it.&lt;br /&gt;
&lt;br /&gt;
==== Latest Visit Only ====&lt;br /&gt;
If you visit a record twice, you&#039;ll see that record only once in the Session History, showing the last visit timestamp. &lt;br /&gt;
&lt;br /&gt;
==== Retain History ====&lt;br /&gt;
You Session History is normally deleted when you logout, but you you can retain your history between sessions by clicking the Prefs button at the bottom-left and checking the &amp;quot;Retain Session History&amp;quot; box.&lt;br /&gt;
&lt;br /&gt;
=== Bookmarks ===&lt;br /&gt;
Bookmark records you use frequently, so you can navigate to them instantly from the Home screen. You bookmark a record by clicking the bookmark icon at the bottom-right of Form View records. The bookmark will turn red, and you&#039;ll be able to see and navigate to bookmarked records from the Home screen History portal.&lt;br /&gt;
&lt;br /&gt;
==== Removing Bookmarks ====&lt;br /&gt;
You can remove a bookmarked record one of two ways:&lt;br /&gt;
&lt;br /&gt;
# click the trash icon beside the record in the Bookmarks list; the record is retained – only the bookmark is removed&lt;br /&gt;
# click the bookmark icon on the record itself; it will switch from red to grey, and the record will no longer appear in the Bookmark portal on Home.&lt;br /&gt;
&lt;br /&gt;
=== Snapshots ===&lt;br /&gt;
Snapshots represents saved sets of records from selected modules. Information on their usefulness and use can be found at the page [[Tags &amp;amp; Snapshots]].&lt;br /&gt;
&lt;br /&gt;
== Form View and List View ==&lt;br /&gt;
You&#039;ll see records presented in two different ways:&lt;br /&gt;
&lt;br /&gt;
=== Form View ===&lt;br /&gt;
Form View presents a single record. When you conduct a search or click a button that yields a single record (one record in your Found Set), you will arrive at Form view of that record, with all of its data presented on a single layout.&lt;br /&gt;
&lt;br /&gt;
=== List View ===&lt;br /&gt;
List View shows you limited information about a collection of records. If you perform an operation that produces a found set with two or more records, they will be presented in List view. &lt;br /&gt;
&lt;br /&gt;
==== To Open a Single Record ====&lt;br /&gt;
In List View, open a record in the list by clicking it. The view will change to Form View of that record.&lt;br /&gt;
&lt;br /&gt;
Note however that your Found Set does not change when you enter Form View by clicking a record in List View. If you were viewing 12 records in List View, and you click on one, the record will open in List View, but the other records remain in the Found Set. You can use the left and right arrows at the upper-left of the screen to page through all the records in the Found Set.&lt;br /&gt;
&lt;br /&gt;
You can also return to List View of the Found Set by using the [[Three-Dot Menu]].&lt;br /&gt;
&lt;br /&gt;
=== Which View Do You Get? ===&lt;br /&gt;
In general PubGizmo uses the size of your Found Set to determine which view to send you to.&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;one record in Found Set:&#039;&#039;&#039; Form View&lt;br /&gt;
* &#039;&#039;&#039;two or more records in Found Set:&#039;&#039;&#039; List View&lt;br /&gt;
&lt;br /&gt;
== Getting Around ==&lt;br /&gt;
&lt;br /&gt;
=== Clicking ===&lt;br /&gt;
&lt;br /&gt;
==== Buttons ====&lt;br /&gt;
Most of PubGizmo&#039;s navigation duplicates what you already do in software and on websites: click an item (only a single click is necessary) to go somewhere else. Click the Contact button to go to the Contacts module. Easy.&lt;br /&gt;
&lt;br /&gt;
==== Links ====&lt;br /&gt;
Also like the web, PubGizmo provides &amp;quot;links&amp;quot; that you can click to go to that target info. These links are created automatically as you add data; you don&#039;t need to do anything special.&lt;br /&gt;
&lt;br /&gt;
On the web, you can identify a link a couple of ways: it might be in blue, or underlined, or both.&lt;br /&gt;
&lt;br /&gt;
In PubGizmo, links are green: &amp;quot;green means go.&amp;quot; So if you are viewing a Contact record for an author, the Titles tab/portal shows all the Title records associated with this author in green. Click one to visit that Title record. In this case, if you click on the first green title:&lt;br /&gt;
[[File:Screenshot 2025-08-30 at 11.26.18.png|none|thumb|700x700px]]&lt;br /&gt;
You will navigate to that Title record.&lt;br /&gt;
&lt;br /&gt;
On the Title record, you&#039;ll see that the opposite end of this link will take you back to the author&#039;s record:&lt;br /&gt;
[[File:Link to Contacts from Title.png|none|thumb|300x300px]]&lt;br /&gt;
&lt;br /&gt;
== The Three-dot Menu ==&lt;br /&gt;
At the upper-left of every major module you&#039;ll see a green button with three vertical dots. Click it to reveal a number of options, which are slightly different depending on whether you are viewing a list of records or single record.&lt;br /&gt;
&lt;br /&gt;
==== Single Record ====&lt;br /&gt;
Here&#039;s the single record menu:[[File:Three-dot menu.png|none|thumb|342x342px]]Here are the options available from this menu:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Show List:&#039;&#039;&#039; switches from single record view to show a list of records in the module, showing all the records in the found set&lt;br /&gt;
* &#039;&#039;&#039;Show All Records:&#039;&#039;&#039; shows only if you have homed in on a single record in the found set; will also take you to&lt;br /&gt;
* &#039;&#039;&#039;NEW Record:&#039;&#039;&#039; creates a new record&lt;br /&gt;
* &#039;&#039;&#039;DELETE Record:&#039;&#039;&#039; deletes the current record – see notes below&lt;br /&gt;
* &#039;&#039;&#039;list of other modules:&#039;&#039;&#039; allows &amp;quot;cross-navigation&amp;quot; to another module, allowing you to bypass the Home screen&lt;br /&gt;
&lt;br /&gt;
==== List View ====&lt;br /&gt;
[[File:List three-dot menu.png|none|thumb|256x256px]]&lt;br /&gt;
&lt;br /&gt;
== Searching ==&lt;br /&gt;
You can also go to a specific record or set of records by searching, again much the way you do on the web, where what you type auto-completes as PubGizmo tries to anticipate what you&#039;re looking for. PubGizmo uses something called the QuickDex, which accelerates searches and navigation. Its use is more substantially covered on [[QuickDex Helps with Finds|this page]].&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Main_Page&amp;diff=197</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Main_Page&amp;diff=197"/>
		<updated>2026-09-22T02:03:07Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages contain manuals for using [https://pubgizmo.com PubGizmo], software that helps publishers manage their presses.&lt;br /&gt;
&lt;br /&gt;
We are constantly building pages to provide help; look for more to be added her soon!&lt;br /&gt;
&lt;br /&gt;
Please [mailto:queries@pubgizmo.com click] to email us help questions.&lt;br /&gt;
&lt;br /&gt;
== Getting Started with PubGizmo ==&lt;br /&gt;
&lt;br /&gt;
# [[How to Get Your Press Aboard PubGizmo]]&lt;br /&gt;
# [[Onboarding Import: Introduction]]&lt;br /&gt;
#* [[Onboarding Import: Titles]]&lt;br /&gt;
#* [[Onboarding Import: Editions]]&lt;br /&gt;
#* [[Onboarding Import: Organizations]]&lt;br /&gt;
#* [[Onboarding Import: Contacts]]&lt;br /&gt;
#* [[Onboarding Import: Contracts]]&lt;br /&gt;
&lt;br /&gt;
== Using PubGizmo ==&lt;br /&gt;
# [[How to Use PubGizmo]] – conventions, tips, and tricks&lt;br /&gt;
# [[How to Access Your Solution]] – setting up your computer to use PubGizmo&lt;br /&gt;
# [[QuickDex Helps with Finds]]&lt;br /&gt;
# [[Tags &amp;amp; Snapshots]] – working with selected sets of records&lt;br /&gt;
&lt;br /&gt;
== Titles ==&lt;br /&gt;
# [[New vs. Existing Titles]]&lt;br /&gt;
# [[Keywords]]&lt;br /&gt;
&lt;br /&gt;
== Contracts ==&lt;br /&gt;
[[Configuring, Recording, and Disbursing Subsidiary Rights]]&lt;br /&gt;
&lt;br /&gt;
== Royalties ==&lt;br /&gt;
# [[Sales Data Needed to Compute Royalties]]&lt;br /&gt;
# [[Importing Sales Data]]&lt;br /&gt;
# [[Running Royalties]]&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
[[Handling Slow Access and Crashes]]&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Main_Page&amp;diff=196</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Main_Page&amp;diff=196"/>
		<updated>2026-09-22T02:00:36Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;These pages contain manuals for using [https://pubgizmo.com PubGizmo], software that helps publishers manage their presses.&lt;br /&gt;
&lt;br /&gt;
We are constantly building pages to provide help; look for more to be added her soon!&lt;br /&gt;
&lt;br /&gt;
Please [mailto:queries@pubgizmo.com click] to email us help questions.&lt;br /&gt;
&lt;br /&gt;
== Getting Started with PubGizmo ==&lt;br /&gt;
&lt;br /&gt;
# [[How to Get Your Press Aboard PubGizmo]]&lt;br /&gt;
# [[Onboarding Import: Introduction]]&lt;br /&gt;
#* [[Onboarding Import: Titles]]&lt;br /&gt;
#* [[Onboarding Import: Editions]]&lt;br /&gt;
#* [[Onboarding Import: Organizations]]&lt;br /&gt;
#* [[Onboarding Import: Contacts]]&lt;br /&gt;
#* [[Onboarding Import: Contracts]]&lt;br /&gt;
# [[How to Use PubGizmo]]&lt;br /&gt;
# [[How to Access Your Solution]]&lt;br /&gt;
# [[Tags &amp;amp; Snapshots]]&lt;br /&gt;
&lt;br /&gt;
== Titles ==&lt;br /&gt;
# [[New vs. Existing Titles]]&lt;br /&gt;
# [[Keywords]]&lt;br /&gt;
# [[QuickDex Helps with Finds]]&lt;br /&gt;
&lt;br /&gt;
== Contracts ==&lt;br /&gt;
[[Configuring, Recording, and Disbursing Subsidiary Rights]]&lt;br /&gt;
&lt;br /&gt;
== Royalties ==&lt;br /&gt;
# [[Sales Data Needed to Compute Royalties]]&lt;br /&gt;
# [[Importing Sales Data]]&lt;br /&gt;
# [[Running Royalties]]&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
[[Handling Slow Access and Crashes]]&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Tags_%26_Snapshots&amp;diff=195</id>
		<title>Tags &amp; Snapshots</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Tags_%26_Snapshots&amp;diff=195"/>
		<updated>2026-09-22T01:16:08Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: /* Home Screen Controls */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags &amp;amp; Snapshots offer a way to save and share groups of records and return to them later. This can be especially useful if you want to create groups of Contacts for bulk emailing, or if you want to break up the full set of Royalties you need to process into smaller units.&lt;br /&gt;
&lt;br /&gt;
== Tags ==&lt;br /&gt;
Tags are temporary, in that they persist only for the duration of your session. All tagged records are untagged when you log out. (If you have records tagged when you close or log out of PubGizmo, you&#039;ll be warned they will be lost if you continue.)&lt;br /&gt;
&lt;br /&gt;
Tags allow for easy flagging of records you want to perform actions on during the session. You can tag groups of records (e.g., you did a find which resulted in a Found Set of a dozen records, and you want to reload that Found Set later in the session without conducting the find again), or you can tag records one at a time by clicking the Tag button, in either Form or List view.&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
Functions to control Tags &amp;amp; Snapshots can be performed using the menus at the bottom of List View in the Contacts and Royalties modules.&lt;br /&gt;
[[File:Screenshot 2026-09-17 at 17.40.05.png|none|thumb|700x700px]]&lt;br /&gt;
&lt;br /&gt;
==== Tagging One Record ====&lt;br /&gt;
To Tag a record, click the tag button. It will turn purple. Click again to untag.[[File:Sep-17-2026 17-35-21.gif|thumb|none]]&lt;br /&gt;
&lt;br /&gt;
==== Tagging a Group of Records ====&lt;br /&gt;
You can tag all the records in a Found Set by using the Tags... menu at the foot of the List View window. Your options are:&lt;br /&gt;
&lt;br /&gt;
* Tag Found Records: tag all the records in the Found Set&lt;br /&gt;
* Untag Found Records: any tagged records showing in the Found Set will be untagged&lt;br /&gt;
* Show All Tagged: replace the current Found Set with a set of all the tagged records in this module&lt;br /&gt;
* Hide All Tagged: you can limit your Found Set by tagging the records you want to remove and selecting this option&lt;br /&gt;
&lt;br /&gt;
== Snapshots ==&lt;br /&gt;
Snapshots persist as named sets: they will be there next time you log in to PubGizmo. You can edit them too: add or remove records as needed. And you can  share them with other members of your team, so one user can assemble a Snapshot and then share it with another user who will perform some action on it.&lt;br /&gt;
&lt;br /&gt;
=== Module Footer Controls ===&lt;br /&gt;
Snapshots are more sophisticated than Tags, and include two selectors in the module&#039;s List View footer (shown above under Controls for Tags).&lt;br /&gt;
&lt;br /&gt;
===== Snapshot Selector =====&lt;br /&gt;
The first is for selecting the snapshot you want to work with, and shows &amp;quot;Select Snapshot...&amp;quot; when no snapshot is loaded.&lt;br /&gt;
&lt;br /&gt;
===== Action Selector =====&lt;br /&gt;
The second button, &amp;quot;Snapshot Action...&amp;quot; is where you decide what to do with the loaded Snapshot. What&#039;s available in this menu depends on what&#039;s showing in the Snapshot Selector.&lt;br /&gt;
&lt;br /&gt;
====== Shows &amp;quot;Snapshot Action...&amp;quot; ======&lt;br /&gt;
When no Snapshot is selected, you only have one option: create a new Snapshot from the records in the Found Set, provided the Found Set is not all the records in the module. This is because it makes no sense to create a Snapshot of every record. You must have narrowed the Found Set to create a Snapshot from it. This usually means you&#039;ve performed a [[QuickDex Helps with Finds|Find]] which has yielded a Found Set of records, for example, you could enter an author&#039;s name which will yield a Found Set of all that author&#039;s statements, and then create a Snapshot named after that author. &lt;br /&gt;
&lt;br /&gt;
You can also Tag records and then use the Tags... menu item &amp;quot;Show All Tagged&amp;quot; to limit your Found Set to just those records.&lt;br /&gt;
&lt;br /&gt;
====== Shows a Snapshot Name ======&lt;br /&gt;
If the Snapshot Selector displays a Snapshot name, use the Action Selector to load the Snapshot you selected under the Snapshot Selector button by selecting &amp;quot;LOAD snapshot &amp;lt;snapshot name&amp;gt;&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The Found Set you are looking at in List View is replaced with the records that comprise the named Snapshot. So if you created a Royalties Snapshot named &amp;quot;Still to do&amp;quot;  containing 18 Royalty records (perhaps after you&#039;ve done most of your Royalties, and there are stragglers you collected into a Snapshot), you will after you load &amp;quot;Still to do&amp;quot; be left with a Found Set of those 18 records.&lt;br /&gt;
&lt;br /&gt;
If a Snapshot name is showing in the Snapshot Selector, you have more options: you can create a new Snapshot, or you can add records to or remove from the records in the current Found Set. In this way you can either build up a Snapshot by doing repeated finds to create Found Sets to add to the Snapshot, or you can pare down the Snapshot by removing records. Remember, you can fine-tune your Found Set by using Tags, e.g., by flagging the records you want, selecting Show All Tagged, and adding them to an existing Snapshot. You can remove records from a Snapshot in the same way.&lt;br /&gt;
&lt;br /&gt;
=== Home Screen Controls ===&lt;br /&gt;
[[File:Screenshot_2026-09-21_at_17.55.49.png|right|frameless|550x550px]]&lt;br /&gt;
The panel on the right side of the Home screen provides a suite of controls for Snapshots. Here you can perform the following actions:&lt;br /&gt;
&lt;br /&gt;
* duplicate a Snapshot&lt;br /&gt;
* delete a Snapshot&lt;br /&gt;
* navigate to a Found List of all the records in the Snapshot in the relevant module – that is, &amp;quot;load&amp;quot; the Snapshot by clicking on the Snapshot name in the upper portal&lt;br /&gt;
&lt;br /&gt;
==== With a Snapshot Selected ====&lt;br /&gt;
You can select a Snapshot by clicking the target beside the name. Once selected, the lower portals will populate with that Snapshot&#039;s attributes, allowing further actions:&lt;br /&gt;
&lt;br /&gt;
* rename the Snapshot&lt;br /&gt;
* add a note – useful if sharing&lt;br /&gt;
* remove individual records from the Snapshot by clicking the trash can beside the record name&lt;br /&gt;
* navigate directly to a specific record in the Snapshot list by clicking on the record name&lt;br /&gt;
&lt;br /&gt;
* share the Snapshot with other PubGizmo users by highlighting their names in the Shared With portal&lt;br /&gt;
&lt;br /&gt;
When you share a Snapshot, the user you have shared it with will see the Snapshot on their Home screen panel and in modules just as you do. You remain the owner of the Snapshot; those who are sharing it cannot delete it, though they can duplicate it and make the copy their own.&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Tags_%26_Snapshots&amp;diff=194</id>
		<title>Tags &amp; Snapshots</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Tags_%26_Snapshots&amp;diff=194"/>
		<updated>2026-09-22T01:01:32Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags &amp;amp; Snapshots offer a way to save and share groups of records and return to them later. This can be especially useful if you want to create groups of Contacts for bulk emailing, or if you want to break up the full set of Royalties you need to process into smaller units.&lt;br /&gt;
&lt;br /&gt;
== Tags ==&lt;br /&gt;
Tags are temporary, in that they persist only for the duration of your session. All tagged records are untagged when you log out. (If you have records tagged when you close or log out of PubGizmo, you&#039;ll be warned they will be lost if you continue.)&lt;br /&gt;
&lt;br /&gt;
Tags allow for easy flagging of records you want to perform actions on during the session. You can tag groups of records (e.g., you did a find which resulted in a Found Set of a dozen records, and you want to reload that Found Set later in the session without conducting the find again), or you can tag records one at a time by clicking the Tag button, in either Form or List view.&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
Functions to control Tags &amp;amp; Snapshots can be performed using the menus at the bottom of List View in the Contacts and Royalties modules.&lt;br /&gt;
[[File:Screenshot 2026-09-17 at 17.40.05.png|none|thumb|700x700px]]&lt;br /&gt;
&lt;br /&gt;
==== Tagging One Record ====&lt;br /&gt;
To Tag a record, click the tag button. It will turn purple. Click again to untag.[[File:Sep-17-2026 17-35-21.gif|thumb|none]]&lt;br /&gt;
&lt;br /&gt;
==== Tagging a Group of Records ====&lt;br /&gt;
You can tag all the records in a Found Set by using the Tags... menu at the foot of the List View window. Your options are:&lt;br /&gt;
&lt;br /&gt;
* Tag Found Records: tag all the records in the Found Set&lt;br /&gt;
* Untag Found Records: any tagged records showing in the Found Set will be untagged&lt;br /&gt;
* Show All Tagged: replace the current Found Set with a set of all the tagged records in this module&lt;br /&gt;
* Hide All Tagged: you can limit your Found Set by tagging the records you want to remove and selecting this option&lt;br /&gt;
&lt;br /&gt;
== Snapshots ==&lt;br /&gt;
Snapshots persist as named sets: they will be there next time you log in to PubGizmo. You can edit them too: add or remove records as needed. And you can  share them with other members of your team, so one user can assemble a Snapshot and then share it with another user who will perform some action on it.&lt;br /&gt;
&lt;br /&gt;
=== Module Footer Controls ===&lt;br /&gt;
Snapshots are more sophisticated than Tags, and include two selectors in the module&#039;s List View footer (shown above under Controls for Tags).&lt;br /&gt;
&lt;br /&gt;
===== Snapshot Selector =====&lt;br /&gt;
The first is for selecting the snapshot you want to work with, and shows &amp;quot;Select Snapshot...&amp;quot; when no snapshot is loaded.&lt;br /&gt;
&lt;br /&gt;
===== Action Selector =====&lt;br /&gt;
The second button, &amp;quot;Snapshot Action...&amp;quot; is where you decide what to do with the loaded Snapshot. What&#039;s available in this menu depends on what&#039;s showing in the Snapshot Selector.&lt;br /&gt;
&lt;br /&gt;
====== Shows &amp;quot;Snapshot Action...&amp;quot; ======&lt;br /&gt;
When no Snapshot is selected, you only have one option: create a new Snapshot from the records in the Found Set, provided the Found Set is not all the records in the module. This is because it makes no sense to create a Snapshot of every record. You must have narrowed the Found Set to create a Snapshot from it. This usually means you&#039;ve performed a [[QuickDex Helps with Finds|Find]] which has yielded a Found Set of records, for example, you could enter an author&#039;s name which will yield a Found Set of all that author&#039;s statements, and then create a Snapshot named after that author. &lt;br /&gt;
&lt;br /&gt;
You can also Tag records and then use the Tags... menu item &amp;quot;Show All Tagged&amp;quot; to limit your Found Set to just those records.&lt;br /&gt;
&lt;br /&gt;
====== Shows a Snapshot Name ======&lt;br /&gt;
If the Snapshot Selector displays a Snapshot name, use the Action Selector to load the Snapshot you selected under the Snapshot Selector button by selecting &amp;quot;LOAD snapshot &amp;lt;snapshot name&amp;gt;&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
The Found Set you are looking at in List View is replaced with the records that comprise the named Snapshot. So if you created a Royalties Snapshot named &amp;quot;Still to do&amp;quot;  containing 18 Royalty records (perhaps after you&#039;ve done most of your Royalties, and there are stragglers you collected into a Snapshot), you will after you load &amp;quot;Still to do&amp;quot; be left with a Found Set of those 18 records.&lt;br /&gt;
&lt;br /&gt;
If a Snapshot name is showing in the Snapshot Selector, you have more options: you can create a new Snapshot, or you can add records to or remove from the records in the current Found Set. In this way you can either build up a Snapshot by doing repeated finds to create Found Sets to add to the Snapshot, or you can pare down the Snapshot by removing records. Remember, you can fine-tune your Found Set by using Tags, e.g., by flagging the records you want, selecting Show All Tagged, and adding them to an existing Snapshot. You can remove records from a Snapshot in the same way.&lt;br /&gt;
&lt;br /&gt;
=== Home Screen Controls ===&lt;br /&gt;
The Home&lt;br /&gt;
[[File:Screenshot 2026-09-21 at 17.55.49.png|thumb|550x550px]]&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=File:Screenshot_2026-09-21_at_17.55.49.png&amp;diff=193</id>
		<title>File:Screenshot 2026-09-21 at 17.55.49.png</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=File:Screenshot_2026-09-21_at_17.55.49.png&amp;diff=193"/>
		<updated>2026-09-22T00:57:10Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Snapshots panel on Home screen&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
	<entry>
		<id>https://pubgizmo.com/wiki/index.php?title=Tags_%26_Snapshots&amp;diff=192</id>
		<title>Tags &amp; Snapshots</title>
		<link rel="alternate" type="text/html" href="https://pubgizmo.com/wiki/index.php?title=Tags_%26_Snapshots&amp;diff=192"/>
		<updated>2026-09-18T00:59:27Z</updated>

		<summary type="html">&lt;p&gt;PubGizmoSysop: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Tags &amp;amp; Snapshots offer a way to save and share groups of records and return to them later.&lt;br /&gt;
&lt;br /&gt;
== Tags ==&lt;br /&gt;
Tags are temporary, in that they persist only for the duration of your session. All tagged records are untagged when you log out. (If you have records tagged when you close or log out of PubGizmo, you&#039;ll be warned they will be lost if you continue.)&lt;br /&gt;
&lt;br /&gt;
Tags allow for easy flagging of records you want to perform actions on during the session. You can tag groups of records (e.g., you did a find which resulted in a Found Set of a dozen records, and you want to reload that Found Set later in the session without conducting the find again), or you can tag records one at a time by clicking the Tag button, in either Form or List view.&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
Functions to control Tags &amp;amp; Snapshots can be performed using the menus at the bottom of List View in the Contacts and Royalties modules.&lt;br /&gt;
[[File:Screenshot 2026-09-17 at 17.40.05.png|none|thumb|700x700px]]&lt;br /&gt;
&lt;br /&gt;
==== Tagging One Record ====&lt;br /&gt;
To Tag a record, click the tag button. It will turn purple. Click again to untag.[[File:Sep-17-2026 17-35-21.gif|thumb|none]]&lt;br /&gt;
&lt;br /&gt;
==== Tagging a Group of Records ====&lt;br /&gt;
You can tag all the records in a Found Set by using the Tags... menu at the foot of the List View window. Your options are:&lt;br /&gt;
&lt;br /&gt;
* Tag Found Records: tag all the records in the Found Set&lt;br /&gt;
* Untag Found Records: any tagged records showing in the Found Set will be untagged&lt;br /&gt;
* Show All Tagged: replace the current Found Set with a set of all the tagged records in this module&lt;br /&gt;
* Hide All Tagged: you can limit your Found Set by tagging the records you want to remove and selecting this option&lt;br /&gt;
&lt;br /&gt;
== Snapshots ==&lt;br /&gt;
Snapshots persist as named sets: they will be there next time you log in to PubGizmo. You can edit them too: add or remove records as needed. You can also share them with other members of your team, so one user can assemble a Snapshot and then share it with another user who will perform some action on it.&lt;br /&gt;
&lt;br /&gt;
=== Controls ===&lt;br /&gt;
Snapshots are more sophisticated than Tags, and include two sets of controls:&lt;br /&gt;
&lt;br /&gt;
==== Module Footer ====&lt;/div&gt;</summary>
		<author><name>PubGizmoSysop</name></author>
	</entry>
</feed>