Not for profit
Bloomerang
Connect your AI to Bloomerang
Development directors, gift officers, and donor relations staff manage every constituent, gift, and interaction in Bloomerang, but spotting lapsed donors or preparing for a donor meeting means paging through records and reports. AI can surface those answers in seconds, but only if it protects donor privacy and only changes records through the steps your team has approved.
Why it matters
Capabilities that matter most for Bloomerang
01
Over 40 ready-made fundraising lists
Install summary and matrix lists for gifts, constituents and interactions, including lapsed and year-over-year giving.
02
Ready-made API endpoints
Install nearly 30 Bloomerang endpoints from the app store for constituents, transactions and interactions.
03
Donor privacy protected
AI tools answer within per-user and per-team security and redaction, and change records only through approved actions.
Use cases
Example AI Use Cases for Bloomerang
scenario
-
Finding out how a fundraising campaign is doing means comparing the raised figure in Bloomerang with its goal, then digging through designations to see which funds and appeals the money came from. Pledges get counted as cash in hand, gifts with no appeal vanish from the breakdown, and the totals rarely agree.
What popdock provides
--
Name the campaign, and optionally a start date, and it reads the goal, the amount raised and the days remaining from Bloomerang. It breaks the revenue down by fund, by appeal and by gift type from the designation records, keeps outstanding pledge balances apart from money received, reports non-deductible amounts separately and counts gifts still awaiting acknowledgement. If the designation total and the campaign's raised figure disagree, both are shown rather than adjusted to match. It only reads, and if several campaigns share the name it asks which one you mean.
Business outcome
---
You see where campaign money really came from and how close you are to goal, with pledges kept apart from cash.
scenario
-
Bounced email addresses, records with no primary phone or address, and two constituents for the same person build up quietly in Bloomerang. Finding them means opening records one at a time, and a shared address often turns out to be a household rather than a duplicate, so cleanup lists fill with false alarms.
What popdock provides
--
Name a surname or a city, or ask for everything, and it checks each constituent's emails, phones and addresses for bad emails, missing or doubled primary records and addresses with no postal code or state. Likely duplicates are grouped by shared surname and postal code or shared email, and members of the same household are left out so a shared address is not flagged. Issues come back ranked from critical to low, with counts and the three fixes that would clear the most records. Nothing is repaired or merged, inactive constituents stay out of the counts, and it tells you if the sweep was cut short.
Business outcome
---
Your team knows which donor records to fix first, without false duplicate alarms from households.
scenario
-
Before you speak to a donor, you want their contact details, what they have given, whose gifts they influenced, recent conversations and any open follow ups. In Bloomerang that means opening several screens and stitching it together, and a bad email or a refunded gift is easy to overlook.
What popdock provides
--
Give a constituent name, and optionally how many months to look back, and it finds the record, asking which one you mean if several match. It pulls addresses, phones and emails and flags anything bad or missing a primary, then summarizes giving in the window with the largest and latest gifts, refunds, payment methods and soft credits. Recent interactions, notes and open tasks follow, ending with where the relationship stands and what the next contact should be. It only reads, never estimates lifetime giving beyond the window, and does not claim which campaign a gift went to without a matching record.
Business outcome
---
You walk into every donor conversation with a full, accurate picture in one read instead of several screens.
scenario
-
Large gifts need quick stewardship, but working out who gave above your threshold, whether each donor is new or upgrading, and whether anyone has thanked them means cross-checking transactions, designations, interactions and tasks in Bloomerang. A major donor can go unthanked for weeks simply because nobody connected the dots.
What popdock provides
--
Set a minimum amount and a look-back period, and it gathers the qualifying gifts, drops refunds and groups them by donor. Each donor is classed as new, upgraded or consistent against their earlier giving, and it checks acknowledgement status, the fund and appeal, and whether anyone has already been in touch or has a task open. You get a ranked table and a prioritized action list, with large unacknowledged gifts first. It only reads, calls a gift unacknowledged only when a record says so, and asks for a higher threshold if more than fifty gifts qualify.
Business outcome
---
Major donors get thanked quickly and in the right order, so no significant gift slips through without stewardship.
scenario
-
Bloomerang tasks pile up across staff, and the task list alone does not tell you who the donor is, what they give or when someone last spoke to them. Working through it means looking up each constituent, so overdue calls to small donors get skipped and the same person gets contacted twice.
What popdock provides
--
Choose how many days ahead to look, and optionally whose queue it is, and it gathers open tasks that are overdue or due in that window. Each task gets the constituent's name, contact details, giving over the last year and most recent interaction, so you can act without further lookups. You get an overdue table and an upcoming table, then a suggested order that weighs how late a task is against what the donor gives, so an overdue small donor still outranks next week's large one. It only reads and never marks a task complete.
Business outcome
---
Staff work through follow ups in a sensible order with donor context in hand, and overdue promises stop getting lost.
scenario
-
Donors who gave a year or two ago and then stopped are the easiest to win back, but finding them in Bloomerang means comparing two periods of transactions by hand. Refunds muddy the picture, and the resulting list rarely shows who is still reachable or when they were last contacted.
What popdock provides
--
Set how many months counts as lapsed, and optionally a minimum prior gift and how many donors you want, and it compares recent givers with those who gave in the two years before. Refunds and soft credits are left out, inactive constituents are skipped, and the top donors by prior giving get names, contact details, engagement score and last interaction date. The list is grouped into donors worth a personal call, worth an email, or needing contact details verified first. It only reads, and warns when a record limit may have left the result incomplete rather than calling someone lapsed on partial data.
Business outcome
---
You get a ranked win-back list of lapsed donors, already sorted by the best way to reach each one.
scenario
-
After a donor call, the conversation should be logged in Bloomerang and any promise turned into a task, but it is easy to put it on the wrong constituent, log it twice, or forget the follow up altogether. Typing it up later also invites detail that was never actually said.
What popdock provides
--
Name the donor, describe the conversation and the channel, and it finds the constituent, asking which one you mean if several match, and never creates a new record. It checks the last week for a similar interaction, then shows the exact interaction, including subject, purpose and note, and waits for your confirmation. If something was promised it proposes a follow up task and asks again before creating it. Each is written once and read back with its id, nothing outside your summary goes in the note, and new contact details are reported for someone else to apply.
Business outcome
---
Every donor conversation is logged once, on the right record, with promised follow ups captured as tasks.
scenario
-
Checks and cash that arrive by post have to be entered against the right donor and the right fund, and a gift entered twice or to the wrong fund is painful to unpick. Doing it by hand means searching for the donor, checking the fund is active and scanning recent gifts for a duplicate.
What popdock provides
--
Give the amount, the donor and the fund, and it finds the donor and the active fund in Bloomerang, stopping to ask if either is ambiguous and never creating a new donor. It checks the last thirty days for a gift of the same amount and date and stops if one exists. You see exactly what will be recorded, including method, check details and fees, and nothing is written until you confirm. The gift is saved once, then read back with its transaction number and fund so you know it landed. The amount is used exactly as given, and the gift date is asked for, never assumed.
Business outcome
---
Offline gifts land once, against the right donor and fund, with no duplicate entries to reverse later.
scenario
-
Refunding a gift means finding the exact transaction in a donor's history, making sure it has not already been refunded, and deciding whether the payment processor should move money. Get any of that wrong and you refund twice, refund the wrong gift, or send back money that cannot be recovered.
What popdock provides
--
Name the donor, the amount and the reason, and it finds the donor and every transaction matching that exact amount, stopping if more than one fits or the gift is already refunded. It then checks for an existing refund before going further. You see the transaction, refund date, reason and whether the processor will be asked to return money, and you confirm both; the processor option stays off unless you turn it on. The refund is written once and read back, and the original gift is checked to show as refunded. A refund with no reason is never written.
Business outcome
---
Refunds go against the right gift exactly once, with a recorded reason and no accidental processor payouts.
scenario
-
People you meet on recorded Chorus calls often never make it into Bloomerang, or exist there without the email they used on the call. Spotting them means comparing call participants with constituents one at a time, and a name match alone can attach an email to the wrong person.
What popdock provides
--
Choose a look-back period, and optionally a company name, and it collects the external participants from recent Chorus conversations and checks each email against Bloomerang. People already known are dropped, a single exact name match is shown as a probable match with the email missing, and everyone else as not in Bloomerang. For each row it proposes adding the email to the existing constituent or creating a new one, and you approve rows one by one. Only approved rows are written, a name match is never treated as certain, and participants with no email are counted rather than guessed.
Business outcome
---
Contacts from your calls end up in Bloomerang with the right email, without duplicate or misattached records.
scenario
-
Fundraising leaders want to know whether calls lead to gifts, but Chorus holds the conversations and Bloomerang holds the money. Lining up who was on each call with what they gave in the following weeks is a spreadsheet job most teams never get to.
What popdock provides
--
Choose a look-back period, how many days after a call to count gifts, and optionally one fundraiser, and it matches each external participant in Chorus to a Bloomerang constituent by email. It reads the gifts each donor made in the window after the call, excluding refunds and counting each gift once against the most recent conversation. You get results per fundraiser, a gift-by-gift table, and up to ten donors spoken to who have not given, ranked by engagement score. It only reads, and states plainly that a gift after a call shows timing, not proof of cause.
Business outcome
---
You see which conversations were followed by gifts and who is ready for another ask, broken down per fundraiser.
scenario
-
Promises made on a donor call, such as sending a report or setting up a visit, live in the Chorus summary and need to become Bloomerang tasks. Copying them over by hand is slow, commitments get missed, and the same task is created twice when two people both act on the call.
What popdock provides
--
Give the Chorus conversation, the Bloomerang user to assign and a default due period, and it reads the meeting summary and finds the donor among the participants by email, asking if more than one constituent matches. Each concrete commitment becomes a draft task in the summary's own words, and drafts that match an open task already on the donor are dropped. You confirm, edit or remove each task before anything is written. It never invents commitments the summary does not state, and if the assignee is rejected it stops rather than trying someone else.
Business outcome
---
Commitments made on donor calls become assigned Bloomerang tasks the same day, without duplicates.
scenario
-
Fundraisers record calls in Chorus but do not always log them in Bloomerang, so donor records miss conversations that happened. Finding the gaps means checking each call's participants against constituents and then hunting for a matching interaction near the call date.
What popdock provides
--
Choose a look-back period, and optionally one Chorus user, and it lists recent conversations, matches external participants to Bloomerang constituents by email and checks for any interaction logged within a day of each call. Unlogged donor conversations come back in a table with the owner and constituent, along with counts of calls checked, logged, unlogged and unmatched, and a tally per owner. Calls with no Bloomerang match are counted but not listed as gaps. It only reads, and warns when the result was capped so you can shorten the window.
Business outcome
---
Donor records reflect every recorded conversation, and you can see which fundraisers are falling behind on logging.
scenario
-
A recorded Chorus meeting with three donors should appear on each of their Bloomerang records with the right channel, purpose and summary. Doing it by hand means matching each attendee, checking whether someone already logged it, and retyping the notes several times over.
What popdock provides
--
Give the Chorus conversation and a purpose, or it asks for one, and it reads the meeting and keeps only external participants. Each is matched to Bloomerang by email; anyone unmatched is listed and never created. It skips constituents who already have an interaction logged that day, then shows who will be logged and the exact interaction, with the meeting summary and who led the call. Nothing is written until you confirm, and if Bloomerang rejects a channel or purpose it asks you rather than trying other values.
Business outcome
---
One recorded meeting is logged on every donor who attended, once each, with the summary attached.
scenario
-
Donors write in by email, and Chorus captures those messages, but Bloomerang only shows them if someone logs each one as an interaction. Doing it by hand is tedious, and it is easy to log the same email twice or include a message that was marked private.
What popdock provides
--
Give the donor's email and a look-back period, and it finds the constituent in Bloomerang, stopping if none or several match. It reads the emails that donor sent through Chorus, skips private ones and tells you how many, and drops any already logged on the same day with the same subject. You see what will be logged, choose one purpose for the batch, and confirm before anything is written. Each email becomes an inbound email interaction with an excerpt of the body, and a rejected purpose is asked about rather than guessed.
Business outcome
---
Donor emails appear on their Bloomerang record without double logging or exposing private messages.
scenario
-
Before calling a donor you want their giving and open tasks from Bloomerang next to what was said on past calls and emails in Chorus. Switching between the two and lining up dates takes time, and conversations that were never logged in Bloomerang stay invisible.
What popdock provides
--
Give the donor's email, and optionally how far back to look, and it finds the constituent in Bloomerang and reads their profile, gifts without refunds, open tasks and logged interactions. From Chorus it gathers recent calls, meetings and emails with that donor. You get a briefing covering who they are, giving in the window, open tasks, a merged timeline marked by source, the key points from call summaries, and Chorus conversations with no matching Bloomerang entry. It only reads, and never guesses a constituent from a name when the email does not match.
Business outcome
---
You start every donor call fully briefed, including what was said last time and what is still owed.
scenario
-
Recent donors should hear from you by email, but many never make it into Constant Contact. Moving them over means exporting gifts, checking each address, and being careful not to re-add someone who unsubscribed, which is both a compliance risk and a quick way to lose trust.
What popdock provides
--
Name the Constant Contact list and a look-back period, and optionally a minimum gift, and it finds recent Bloomerang donors, skipping refunds, inactive constituents, missing emails and addresses flagged bad. Each email is checked in Constant Contact: unsubscribed contacts are never added, people already on the list are skipped, and existing contacts missing from the list are listed for you to add by hand. You confirm which donors to add and whether they gave direct opt-in, and permission is set only when you say so. It reports what was added, failed and skipped, by reason.
Business outcome
---
Recent donors join your email list without anyone who unsubscribed being added back.
scenario
-
After an appeal email goes out, you want to know whether the people who opened or clicked it went on to give. That means exporting engagement from Constant Contact, matching each address to a Bloomerang constituent and checking their gifts after the send date, which rarely gets done.
What popdock provides
--
Name the Constant Contact campaign and how many days to count, and it reads the campaign's sends, opens and clicks, then builds one list of engaged contacts marked clicked or opened only. Each address is matched to Bloomerang by email, never by name, and gifts in the window after the last send are read with their fund, appeal and campaign, leaving out refunds. You get a funnel from engaged to gave, a table of gifts, and a note that timing is not proof the email caused the gift. It only reads, and says how many contacts were not checked when the list is very large.
Business outcome
---
You see the giving that followed each appeal email, so future campaigns are planned on evidence.
scenario
-
Your largest donors should be reachable by email, but some unsubscribed, some addresses bounce, and some were never added to Constant Contact. Finding out means checking each major donor's addresses one by one and looking at whether they actually open anything.
What popdock provides
--
Set a minimum single gift and a look-back period, and it finds the Bloomerang donors who qualify, totals their giving and checks every address on each record in Constant Contact. Each donor lands in one group, engaged, not engaging, unsubscribed, bouncing, not in Constant Contact, or no email, using their best address and Bloomerang's bad email flags. You get counts and a table per group, sorted by total given. It only reads, matches on email and never on name, and if more than a hundred donors qualify it checks the largest first and says how many were left.
Business outcome
---
You know which major donors your emails actually reach, and which need a personal touch instead.
scenario
-
When you want to know whether a donor reads your emails, the answer is in Constant Contact while their giving is in Bloomerang. Donors often have more than one address, so checking a single email misses bounces, unsubscribes and activity on the others.
What popdock provides
--
Give the donor's name, email or account number, and it finds the constituent in Bloomerang, asking if several match, and collects every address on the record with its bad flag. Each address is checked in Constant Contact for permission status, opens, clicks, bounces and unsubscribes over the look-back period, and recent gifts are read from Bloomerang without refunds. The report shows reach per address, engagement by campaign, giving, and one factual line connecting the two without claiming cause. It only reads, and conflicts such as a bad flag on an address that still opens emails are shown side by side.
Business outcome
---
You see in one view whether a donor is hearing from you and how that sits next to their giving.
scenario
-
Donor records in Bloomerang look thin when they do not show who clicked your appeal emails. Logging engagement by hand means exporting clicks or opens from Constant Contact, matching each address, and avoiding a second entry for people already logged for that campaign.
What popdock provides
--
Name the Constant Contact campaign and whether clicks or opens count, and it reads the campaign subject and the engaged contacts with their first engagement date. Each address is matched to a Bloomerang constituent by email, and anyone who already has an interaction for that campaign subject is skipped. It offers the interaction purposes your account already uses, shows the plan and its size, and writes nothing until you confirm, offering batches of a hundred for large runs. You get counts of what was logged, skipped and failed.
Business outcome
---
Campaign engagement appears on donor records, so fundraisers see who is paying attention before they call.
scenario
-
When a donor's email bounces or they unsubscribe in Constant Contact, fundraisers working in Bloomerang have no idea and keep relying on that address. Carrying the news across means matching each problem address to a constituent and leaving a note, without noting the same problem twice.
What popdock provides
--
Choose a look-back period, and optionally a campaign, and it reads bounces and unsubscribes from Constant Contact and matches each address to Bloomerang by email. Constituents who already have a note about that address are skipped, and temporary bounces such as a full mailbox are labelled so you can drop them. You confirm all, some or none of the rows before any note is written, and an address shared by several accounts is shown so you can choose. It adds notes only, and tells you to set Bloomerang's bad email flag yourself because it cannot.
Business outcome
---
Fundraisers see email problems on the donor record and stop relying on addresses that no longer work.
scenario
-
Over time Constant Contact and Bloomerang drift apart: contacts with no constituent, names and phones that differ, and addresses Bloomerang knows are bad that are still being mailed. Comparing the two contact by contact is slow enough that it rarely happens.
What popdock provides
--
Name a Constant Contact list, or check all contacts up to a limit, and it matches each email to Bloomerang using every address on a constituent. Contacts with no constituent are listed, emails shared by several accounts are flagged without picking one, and matched records are compared on name, phone digits, employer and email status, including bad addresses that can still receive mail. It only reads and lists proposed fixes rather than making them. The report notes that it checks from the Constant Contact side, so constituents missing from Constant Contact are not covered.
Business outcome
---
You get a clear list of mismatches between your email and donor systems to clean up, with nothing changed behind your back.
scenario
-
Every Bloomerang fund carries a general ledger class that should point at a real Dynamics 365 Business Central account, but accounts get blocked, renumbered or turned into headings. You only find out when gifts fail to post, and checking each fund against the chart of accounts by hand is slow.
What popdock provides
--
Optionally name a Business Central company, and it reads every active Bloomerang fund and looks up its GL class as a G/L account number, checking dimension values when no account matches. Each fund is rated OK, blocked, no direct posting, dimension not account, missing or not found, with the matched account's name and type. Numbers are compared exactly, so a near miss such as 4000 against 40000 is reported as not found with a note rather than guessed. It only reads, and if Business Central fails for the company it stops instead of marking every fund missing.
Business outcome
---
Broken fund mappings are fixed before gift posting fails, not discovered after month end.
scenario
-
When a sponsor needs an invoice, someone has to set them up as a Dynamics 365 Business Central customer using details that already live in Bloomerang. Rekeying the name, email, phone and address invites typos, and it is easy to create a second customer for an organization that already exists.
What popdock provides
--
Name the Bloomerang organization, and optionally a Business Central company, and it finds the organization with its primary address and phone. It searches Business Central for an existing customer by email and by name, and never creates one when a likely match exists. You see the customer it would create and can supply a customer number, and nothing is written until you confirm. Once the customer is created, a note with the new customer number is added to the Bloomerang record and the customer is read back; if creation fails, no note is added.
Business outcome
---
Sponsors become Business Central customers once, with accurate details and a link back on their donor record.
scenario
-
Gifts recorded in Bloomerang need to reach Dynamics 365 Business Central, but some sit in an unposted journal and others never arrive. Finding which ones means checking each gift against both the ledger and the journals, which nobody has time for at month end.
What popdock provides
--
Give a date range, and optionally a company, and it reads the Bloomerang gifts and looks for each one in Business Central by its BLM document number, first in posted ledger entries and then in unposted journal lines. Gifts are counted as posted, in journal with the batch name, or missing, and the missing ones are listed with donor, amount and method, with refunded gifts flagged. It only reads. If nothing in the period is found at all, it warns that gifts may have been posted as daily totals and suggests a revenue reconciliation instead.
Business outcome
---
You know exactly which gifts still need posting before you close the period.
scenario
-
Sponsors often pay invoices in Dynamics 365 Business Central and also appear as donors in Bloomerang, and the two records rarely line up. Matching payments to gifts by amount and date by hand is fiddly, and a payment that was never recorded as a gift easily goes unnoticed.
What popdock provides
--
Name the organization and a look-back period, and optionally a company, and it finds the matching constituent and Business Central customer, stopping if either side is missing or ambiguous. It reads the customer's payments and the organization's gifts, then pairs them when amounts match and dates fall within seven days, preferring a check number match and using each record once. You get paired items, payments with no gift and gifts with no payment, with totals and a likely reading of each. It only reads, and differences of cents or currency are left unpaired and mentioned.
Business outcome
---
Sponsor payments and gifts are reconciled in minutes, and unrecorded gifts surface before acknowledgements go out.
scenario
-
Getting a period of Bloomerang gifts into Dynamics 365 Business Central means rekeying each fund designation as a journal line against the right G/L account. It is slow, and it is easy to post a gift twice or to an account that is blocked or closed to direct posting.
What popdock provides
--
Give a date range and the deposit account, and optionally a company, and it reads the gifts and their fund designations, leaving out refunds. Any gift already in Business Central as a ledger entry or journal line is skipped, and every account is checked, so gifts needing a missing, blocked or non-posting account are left out and listed. You see each planned line and the total before anything is written. After you confirm it creates one new journal and its lines, then reads them back and compares the count and total with the plan. The journal stays unposted for your review.
Business outcome
---
Gifts reach Business Central as a ready-to-review journal, with no double posting and no bad accounts.
scenario
-
At period end, the gift total for each fund in Bloomerang should agree with what Dynamics 365 Business Central shows on that fund's G/L account, but it rarely does at first. Tracking down the gap means listing gifts and ledger entries side by side for every fund.
What popdock provides
--
Give a date range, and optionally a company, and it totals Bloomerang gifts by fund from the designations, keeping refunds separate. Each fund is mapped to its G/L account and compared with the net credits Business Central shows for the period, with a status of matched, Bloomerang higher, Business Central higher or unmapped. For every gap it lists the entries and gifts behind it, pairing gift entries by their BLM document number. It only reads, and extra entries without that number are called probable non-gift income rather than errors.
Business outcome
---
Fund revenue ties out between your donor system and the ledger, with every variance explained.
scenario
-
An organization can be a generous sponsor in Bloomerang and at the same time carry overdue invoices in Dynamics 365 Business Central. Seeing both means looking the organization up in each system, and matching by name alone can merge two different companies.
What popdock provides
--
Name the organization, a look-back period and optionally a company, and it finds the Bloomerang organization, then the Business Central customer by email first and by name second, asking if several match. You get gift count, total, largest and latest gift beside the customer's balance, credit limit, blocked status, open invoices and overdue total, with a line on what stands out. It says whether the match was by email or by name, and never merges organizations that only share a word. It only reads, and if no customer exists it reports the giving alone.
Business outcome
---
You see a sponsor's giving and what they owe in one view before your next conversation with them.
scenario
-
Each Bloomerang fund points at a Sage Intacct account through its GL class, but values get typed with stray spaces, accounts go inactive, and some are closed to direct posting. Those problems only appear when a journal entry fails, and checking fund by fund takes an afternoon.
What popdock provides
--
Check every active fund or those matching a name, and it looks up each GL class as a Sage Intacct account, retrying once with formatting cleaned up and checking projects if no account matches. Findings are ranked blocking, warning or note: blank classes, missing or inactive accounts and no direct posting block posting, while formatting mismatches, balance sheet accounts and required department or location dimensions are warnings. Each comes with the fix and the system to change it in. It never matches by title or partial number, and it recommends fixes without making them.
Business outcome
---
Fund to account mapping is clean before gifts are booked, so journal entries post the first time.
scenario
-
Boards ask how fundraising is tracking against budget, but the budget sits in Sage Intacct, gifts in Bloomerang and booked revenue in the general ledger. Lining them up by account, while keeping pledges apart from cash received, is a monthly spreadsheet chore.
What popdock provides
--
Name the Sage Intacct budget and a date range, and it maps active Bloomerang funds to their revenue accounts, then reads the budget to date and the full budget for each account. Money raised in Bloomerang is totalled apart from new pledges and open pledge balances, and booked revenue is read from the ledger on an accrual basis. You get one row per account with percent of budget to date, the biggest shortfall and overrun, accounts where raised and booked differ by more than five percent, and campaigns ending in the period. Unbudgeted and unmapped items are flagged, and nothing is changed.
Business outcome
---
Leaders see fundraising against budget by account, with pledges separated from cash, ready for a board update.
scenario
-
Each day's Bloomerang gifts need to become journal entries in Sage Intacct by fund, but refunds, pledges and processor fees complicate the totals. Done by hand, gifts get booked twice, or to an account that is inactive or will not accept the posting.
What popdock provides
--
Give the gift date, the debit account and optionally a journal, and it totals the day's gifts by fund, leaving out refunds and pledges and setting aside gifts whose designations do not add up. Each account is checked in Sage Intacct, and required department or location IDs are asked for, not guessed. It skips any fund already booked under its reference number, or whose account already shows similar credits that day, and asks how to treat processing fees. After you confirm the plan it creates one draft entry per fund and reads each back.
Business outcome
---
Daily gifts are booked to Sage Intacct by fund as draft entries, without duplicates or failed postings.
scenario
-
Fund totals in Bloomerang and revenue in Sage Intacct drift apart for many reasons: timing, refunds not reversed, pledges booked differently, gifts coded to the wrong account. Explaining each variance means pulling both sides by fund and reading ledger detail line by line.
What popdock provides
--
Give a period, and optionally one fund, and it maps each fund to its Sage Intacct account, combining funds that share one. Bloomerang gifts, refunds, pledges and pledge payments are totalled per fund without ever adding a pledge to its payments, and Sage Intacct activity is read on an accrual basis so rows are not double counted. Each variance over one percent or 100.00 gets its likeliest cause from the evidence, and it says which pledge treatment your books appear to follow. It only reads, and reports mismapped funds rather than guessing the account.
Business outcome
---
Variances between donor records and the ledger arrive with explanations, so the close moves faster.
scenario
-
Gifts recorded in Bloomerang should match money arriving in Sage Intacct, but card processors pay out in batches net of fees, checks are bundled into deposits, and payment methods are named differently. Proving every gift reached the bank takes careful matching that rarely gets finished.
What popdock provides
--
Give a date range, and optionally a bank account, and it reads gifts and refunds from Bloomerang and the receipts, invoice payments and deposits in Sage Intacct, allowing three business days for settlement. Checks match on check number or amount and date, card and EFT gifts are batched by day with any shortfall reported as implied fees, and cash matches on amount, without counting the same money twice. You get matched items, gifts with no money, money with no gift, and refunds, ending with the unexplained difference. It only reads, and warns when a record limit means a list is partial.
Business outcome
---
You can show every gift reached the bank, with processor fees and unexplained differences called out.
scenario
-
Some donations go straight to finance and are recorded in Sage Intacct but never entered in Bloomerang, so donors miss acknowledgements and giving history is incomplete. Finding them means comparing receipts with gifts by payer, amount and date, and payers rarely appear exactly as constituents do.
What popdock provides
--
Give a date range, and optionally a minimum amount, and it reads Sage Intacct receipts, keeping only lines on the gift revenue accounts your Bloomerang funds map to. Each receipt is checked against Bloomerang by payer and by amount within seven days, and sorted into already recorded, ready to record or needs a person. You choose which ready gifts to create, and it asks rather than guessing on unclear payment methods or partly deductible receipts. It never adds a donor, reads back each new gift, and reminds you not to post these to Sage Intacct a second time.
Business outcome
---
Donations received by finance appear in Bloomerang, so donors are thanked and giving history is complete.
scenario
-
A donor may also be a customer with open invoices or a vendor your organization pays, and those records sit in Sage Intacct with no link to Bloomerang. Finding them means searching by name in several places, and people are often stored differently, so the wrong record is easy to pick.
What popdock provides
--
Give the donor's name, email or account number, and it totals their Bloomerang giving, then searches Sage Intacct customers, vendors and contacts. A record counts as a match only when the name agrees and the email or city agrees too; name-only hits are listed as possible matches and kept out of the totals. You see what they gave, what they owe on open invoices, what they paid and whether those payments also appear as gifts, and what was paid to them. A donor who is also a paid vendor is flagged for related-party review without concluding anything, and nothing is changed.
Business outcome
---
You see the whole financial relationship with a donor, including related-party items, before anyone has to ask.
scenario
-
New and recent donors often never reach your Mailchimp audience, so they miss updates and appeals. Adding them by hand means exporting gifts, checking each email, and taking care not to re-add anyone who unsubscribed or was cleaned.
What popdock provides
--
Name the Mailchimp audience, a start date and the status to give new members, and it collects recent Bloomerang donors, ignoring refunds and counting those with no email. Each is checked against the audience, and anyone already there is left alone whatever their status, so unsubscribed and cleaned contacts are never added back. You see who will be added and with what status, with a reminder that subscribed is only for people who agreed to marketing email; pending, which sends a double opt-in email, is the default. Nothing is written until you confirm.
Business outcome
---
Recent donors join your Mailchimp audience with consent respected and no unsubscribed contacts added back.
scenario
-
You sent an appeal through Mailchimp and want to know who gave afterwards, and whether openers and clickers gave more than everyone else. Answering that means matching each recipient to Bloomerang and checking their gifts over the following weeks.
What popdock provides
--
Name the Mailchimp campaign and how many days to count, and it reads the recipients, their opens and who clicked. Each address is matched to a Bloomerang constituent by email, and gifts in the window after the send are read, ignoring refunds and never double counting an email linked to two accounts. You get donors and totals split by clicked, opened but did not click, and did not open, a table of each donor's gifts, and the campaign's open and click rates for context. It only reads, and says plainly that a gift after an email is correlation, not proof.
Business outcome
---
You learn whether your Mailchimp appeals are followed by gifts, split by how recipients engaged.
scenario
-
Your biggest donors may have unsubscribed, been cleaned from Mailchimp, or never been added, and nobody notices until an appeal falls flat. Checking means totalling giving per donor in Bloomerang, then looking each one up in Mailchimp and reading their open rates.
What popdock provides
--
Set a minimum total and a start date, and it totals Bloomerang giving per donor, excluding refunds, and keeps those at or above the threshold. Each donor is looked up in Mailchimp by primary email and then by any other address on the record. Every donor is rated engaged, quiet, unreachable, not in Mailchimp or no email from audience status and open rate, and the unreachable and missing groups get a suggestion of personal outreach. It only reads, says when record limits may understate totals, and shows the top ten instead if nobody reaches the threshold.
Business outcome
---
You know which major donors your Mailchimp emails reach, and who needs a phone call instead.
scenario
-
Fundraisers want to see in Bloomerang which donors clicked or opened the latest Mailchimp campaign. Logging that by hand means exporting activity, matching each address and checking nobody already has the interaction, which is too slow to do for every send.
What popdock provides
--
Name the Mailchimp campaign and whether clicks or opens count, and it reads who engaged along with their first activity date. Each address is matched to Bloomerang by email, unmatched addresses are reported, and anyone already logged for that campaign subject is skipped. You see a table of the interactions it will create, and nothing is written until you confirm. Each becomes an outbound email interaction with a note naming the campaign and the engagement, and if Bloomerang rejects a channel or purpose it stops and asks.
Business outcome
---
Email engagement shows on donor records after each campaign, ready for fundraisers to act on.
scenario
-
To know whether a donor reads your newsletters you need Mailchimp, and to see their gifts you need Bloomerang. A donor with two or three addresses makes it harder, because the bounce or unsubscribe may sit on the address you did not check.
What popdock provides
--
Give the donor's name or email, and it finds the constituent in Bloomerang, asking if several match, and collects every address not flagged bad. Each address is checked in Mailchimp for audience membership, status, rates, opens, clicks, bounces and unsubscribes, and recent gifts are read from Bloomerang. You get a short profile, an audience table and a dated timeline merging email activity with gifts, with any unsubscribe or hard bounce at the top. It only reads, and if the donor has no email it reports their giving alone.
Business outcome
---
You see one donor's email engagement and giving on a single timeline before deciding how to reach them.
scenario
-
People who buy from your online store are good candidates for giving, but their details sit in the store connected to Mailchimp, not in Bloomerang. Working out who is new means comparing customer emails with constituents by hand and checking who has agreed to marketing.
What popdock provides
--
Optionally set a minimum amount spent, and it reads store customers from Mailchimp with their orders, spend and opt-in status, then checks each email in Bloomerang. Customers with no constituent are listed by total spent, and customers already in Bloomerang whose names differ are listed separately. Anyone who has not opted in to marketing email is pointed out. It only reads and creates no constituents, and if no customers come back it checks whether a store is connected at all.
Business outcome
---
You get a ranked list of store customers to consider for donor outreach, with marketing consent made clear.
scenario
-
When donors unsubscribe or their address hard bounces in Mailchimp, fundraisers in Bloomerang keep emailing them without knowing. Carrying that across by hand means matching each address and adding a note, without noting the same event twice or recording a bounce that was only temporary.
What popdock provides
--
Choose a start date, and it reads Mailchimp unsubscribes and hard bounces, keeping the latest event per address and ignoring soft bounces. Each address is matched to Bloomerang by email, unmatched ones are reported, and constituents already noted for that event are skipped. You see the notes it will add with the event, date and reason, and nothing is written until you confirm. It adds notes only and does not change email records or constituents.
Business outcome
---
Fundraisers know which donors email no longer reaches, straight from the donor record.
scenario
-
Your Mailchimp audience and your Bloomerang donor list should line up, but donors go missing from the audience, unknown subscribers pile up, and some donors unsubscribed without anyone noticing. Comparing the two by hand is a large spreadsheet exercise.
What popdock provides
--
Name the Mailchimp audience, and optionally a constituent status, and it reads both sides and matches on email, checking secondary addresses in Bloomerang before calling anyone unmatched. You get four tables: constituents missing from the audience, audience members with no constituent, matched donors who are unsubscribed or cleaned, and names that differ, with counts. It only reads and recommends fixes without making them. If either side returns nothing, or a read hits its limit, it says so rather than reporting everyone as missing.
Business outcome
---
You see exactly where your email audience and donor records disagree, so cleanup is targeted.
scenario
-
Fund-to-ledger mappings drift between the donor CRM and the chart of accounts, so gifts end up posting to the wrong account or to one that no longer exists. Finding out means reading each fund's GL class in Bloomerang and searching for it in NetSuite one at a time.
What popdock provides
--
Name a fund, or leave it blank for all active funds, and it reads each fund's GL class in Bloomerang and looks it up in the NetSuite chart of accounts, by account number first and by name if that finds nothing. Each fund is labelled Matched, Name-only match, No account found or No GL class set, and funds mapped to a non-income account type are flagged as possible errors. When a GL class matches several accounts it lists them rather than choosing. It only reads, so neither system is changed.
Business outcome
---
Funds that point at a missing or doubtful ledger account are found before gifts post to the wrong place, with nothing changed.
scenario
-
Fundraising totals live in the donor CRM while campaign revenue lives in the ERP, and the two are compared by copying figures into a spreadsheet. They rarely agree, and the date ranges behind each number often differ.
What popdock provides
--
Give a campaign name, and it finds the campaign in Bloomerang and the campaign with the same name in NetSuite. It shows them side by side: Bloomerang raised and goal, NetSuite revenue, total cost and profit, the difference between raised and revenue, and the percentage of goal reached. Different date ranges are noted, and a gap of more than 5 percent is called out first. It stops and lists candidates if the name matches several campaigns, says plainly when NetSuite has no matching campaign, and changes nothing.
Business outcome
---
Fundraising and ERP campaign figures are compared in one reply, with gaps and missing campaigns called out and no spreadsheet needed.
scenario
-
Donor records live in the CRM and customer records live in the accounting system, and people match them by eye. Gifts then get booked against a customer that is missing or duplicated.
What popdock provides
--
Give a constituent name to search for, and optionally how many to check (25 by default). It finds matching Bloomerang constituents, then looks each one up in NetSuite by email, using the name only when there is no email and marking that as a weak match. The table shows account number, NetSuite customer ID and balance, with a verdict of matched, weak match, not in NetSuite or several customers. Names that differ for the same email are reported with both spellings, it never picks between several matches, and it creates and changes nothing in either system.
Business outcome
---
Finance sees which Bloomerang donors have no NetSuite customer, or an unreliable one, before gifts are booked against the wrong record.
scenario
-
Gift receipts in the donor CRM are compared with payments in the ledger one donor at a time. Missing or double-booked gifts then come to light at month end.
What popdock provides
--
Give a Bloomerang constituent ID and a date range, and it reads the donor's gifts, then finds their NetSuite customer by email and reads customer payments, deposits and cash sales for the same dates. Each gift is matched to a record with the same amount and a date within three days. It lists matched gifts with the NetSuite document number, gifts with no NetSuite record, and NetSuite records with no gift, then the totals on both sides and the difference. Refunded gifts are listed apart, date mismatches are flagged, and it stops if the donor has no email or no NetSuite customer. Nothing is changed.
Business outcome
---
Gifts missing from, or double-booked in, the ledger are listed for one donor in one pass, with nothing changed in either system.
scenario
-
Donor refunds issued in the CRM are not always reflected in the ledger. Until someone compares the two by hand, revenue stays overstated.
What popdock provides
--
Give a date range, and it reads Bloomerang refunds, finds the donor for each and takes their email. It then reads NetSuite customer refunds and credit memos for the same dates and matches on donor email with NetSuite dates within seven days. The result lists matched refunds, Bloomerang refunds with no NetSuite record and NetSuite refunds or credit memos with no Bloomerang refund, with counts and the Bloomerang total. It says clearly that amounts were not compared, lists donors with no email as could not match instead of guessing, and changes nothing in either system.
Business outcome
---
Refunds missing from either system are listed for the period, so revenue is not left overstated, with nothing changed.
scenario
-
Understanding a major donor means opening Bloomerang for the giving history, then the ERP for their balance, open invoices, payments and deposits, and stitching the two together. The details sit in two systems and rarely line up at first look.
What popdock provides
--
Give a donor name and, optionally, how many days to look back, which defaults to 365. It finds the donor in Bloomerang and stops with a list if the name is ambiguous, then totals recent giving with the largest gift, latest gift and count. It matches the donor email to a NetSuite customer and reads the balance, open invoices, payments and deposits. One report combines both, noting oddities such as gifts with no NetSuite payment or a balance owed by an active donor. Amounts owed come only from NetSuite, a missing NetSuite match is stated rather than guessed, and nothing is changed.
Business outcome
---
Leaders get one donor view across Bloomerang and NetSuite, with amounts owed taken only from the ledger.
No items found.
Ready to unlock your data?
Start building tools that turn your business systems into AI superpowers
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.