MuchBetter Casino Transactions: Tax Rules in Canada

MuchBetter Casino Transactions: Tax Rules in Canada

MuchBetter arrived on the Canadian scene at a moment when players were frustrated with slow bank wires and card declines. Since then, the e-wallet has become a familiar sight at Canadian casino cashiers, valued for its speed and simple fee structure. But as more players move money through MuchBetter, one question keeps surfacing: what does the Canada Revenue Agency expect from those transactions? The short answer is that casino winnings are generally not taxable in Canada , but the details matter. For more details, visit canadian casinos paypal.

How Canada Treats Casino Winnings

Canada does not impose a specific tax on lottery or casino winnings for casual players. If you deposit $200 CAD via MuchBetter, spin the reels, and withdraw $2,000 CAD, that $1,800 CAD gain is not reported as income on your T1 return in most circumstances. The CRA views these as windfalls rather than earned income, similar to a lottery payout.

The reasoning is straightforward. Recreational gambling in Canada is treated as a matter of luck, not a business activity. There is no withholding tax applied at the casino level, and MuchBetter does not deduct anything on your behalf when you move funds. What you withdraw is what you receive.

That said, the picture changes if gambling becomes a regular, organized activity. The CRA has historically pursued cases where a player’s volume, frequency, and reliance on skill suggested a business operation rather than a hobby. Professional poker players, for example, have faced scrutiny. For the typical MuchBetter user at a Canadian online casino, though, this is rarely a concern.

What About MuchBetter Fees and Reporting?

MuchBetter charges a small deposit fee , typically 1% , depending on the casino and your account settings. These fees are transaction costs, not taxes, and they do not create a reporting obligation. However, if you are running a high-volume operation, those costs become deductible business expenses in the same way any professional would claim them.

Canadian financial institutions and payment processors must report certain transactions to the Financial Transactions and Reports Analysis Centre of Canada (FINRA C) under anti-money laundering rules. MuchBetter, as a regulated payment service, follows similar compliance standards. Large or unusual transfers may be flagged, but this is about fraud prevention, not taxation.

There is no line on your tax return for casino winnings. You do not need to issue yourself a T4A, and MuchBetter will not send you a tax slip. The only scenario where reporting becomes relevant is if gambling is your primary income source and the CRA determines it qualifies as business income.

Practical Takeaways for Canadian Players

  • Casual casino winnings through MuchBetter are not taxable in Canada.
  • No withholding tax applies at the source.
  • MuchBetter does not report your winnings to the CRA.
  • Professional or business-like gambling may be taxable , consult an accountant.
  • Keep records of large transactions for your own clarity.

For the overwhelming majority of Canadian players, MuchBetter transactions carry no tax consequences. The wallet’s appeal lies in its speed, its 1% deposit fee, and its acceptance at hundreds of Canadian-facing casinos. Understanding the tax angle simply removes one more worry from the equation.

If your gambling activity is occasional and recreational, you can use MuchBetter with confidence. The CRA is not watching your e-wallet. It is watching for patterns that look like a business , and a weekend slots session does not qualify.

Casino Bonus Terms Canadians Should Always Check

Casino Bonus Terms Canadians Should Always Check

A generous welcome offer catches the eye, but the fine print decides whether that bonus is worth claiming. In Canada, regulated and offshore operators alike publish terms that vary wildly in fairness. According to industry surveys, roughly 65% of players admit they rarely read bonus conditions before opting in. That single habit costs real money, because a headline match of 100% up to $500 CAD can quietly carry conditions that make withdrawal nearly impossible. Read more about this at casinos that accept dogecoin.

Understanding the terms is not about being suspicious. It is about knowing exactly what you are agreeing to before a single dollar of bonus funds hits your balance.

Wagering Requirements and Game Weighting

The wagering requirement is the most important number on any bonus page. It tells you how many times you must play through the bonus amount before withdrawing. A 40x requirement on a $200 CAD bonus means $8,000 CAD in total bets. Lower is better, and anything above 40x deserves scrutiny.

Equally important is game weighting. Most Canadian operators count slot play at 100%, but table games like blackjack and roulette often contribute just 10% or even 5%. Live dealer titles sometimes count at 0%. This means a $100 CAD bet on blackjack may only clear $10 CAD of your wagering target.

  • Check the exact multiplier: 30x is fair, 60x is punishing
  • Confirm which games contribute at 100%
  • Note whether live casino counts at all
  • Look for a maximum bet rule, often $5 CAD or less per spin

Breaching the maximum bet rule is the most common reason Canadian players lose bonus winnings entirely. The cap is rarely displayed prominently, but it is enforced strictly.

Time Limits, Withdrawal Caps, and Payment Rules

Bonuses do not last forever. Standard expiry windows run from seven to thirty days, and unfulfilled wagering at the deadline usually voids both the bonus and any winnings attached to it. Players who claim multiple offers at once often discover they cannot be combined, and doing so can trigger forfeiture of everything.

Withdrawal caps matter just as much. Some promotions limit cashouts to ten times the bonus value, regardless of how much you actually win. A $150 CAD bonus capped at $1,500 CAD means a $10,000 CAD win pays out only a fraction.

Term Typical Range What to Prefer
Wagering 30x to 60x Under 40x
Expiry 7 to 30 days 30 days or more
Max bet $5 to $10 CAD Higher caps
Withdrawal cap 5x to 15x bonus No cap

Payment restrictions also apply. Many bonuses exclude certain e-wallets or prepaid methods from qualifying deposits, and some require you to withdraw through the same method you used to deposit. Checking these details before claiming saves considerable frustration later.

A Quick Pre-Claim Checklist

  1. Read the wagering multiplier and game weighting
  2. Confirm the expiry date and maximum bet
  3. Check for withdrawal caps and excluded payment methods
  4. Verify whether free spins carry separate terms

Spending five minutes on these details protects far more than it costs. Canadian players who compare terms side by side consistently keep more of what they win, and that discipline separates a genuine bonus from a marketing headline.

Bankroll Management Tips for Canadians

Bankroll Management Tips for Canadians

Bankroll management separates players who last from those who burn out in a weekend. In Canada, where provincial regulators like the Alcohol and Gaming Commission of Ontario oversee licensed operators, responsible play isn’t just advice , it’s baked into the rules. Still, no regulator can manage your money for you. That job belongs to you, and it starts long before you open a casino lobby. Read more about this at canadian casinos muchbetter.

Statistics from Canadian problem gambling surveys suggest roughly 3% of adults experience moderate to severe gambling harm, and poor bankroll habits are a common thread. The good news? A few disciplined routines dramatically reduce that risk while keeping the entertainment value intact.

Set a Dedicated Bankroll Before You Play

Your bankroll should be money you can afford to lose entirely , never rent, groceries, or emergency savings. A practical approach is to carve out a fixed monthly figure in CAD, say $100 or $200, and treat it as your entertainment budget, the same way you’d budget for dining out.

Within that budget, limit any single session to 5-10% of the total. If your monthly bankroll is $200, that means $10 to $20 per session. This structure prevents one bad night from wiping out your funds and keeps you in the game across many sessions instead of a few reckless ones.

Consider keeping this money in a separate account or e-wallet. Separating gambling funds from daily spending creates a psychological barrier that makes impulsive top-ups harder to justify.

  • Never chase losses with money outside your bankroll
  • Set a hard stop-loss of 50% of your session budget
  • Review your bankroll monthly and adjust only downward, not up

Choose Bet Sizes and Games That Match Your Budget

Bet sizing is where most players go wrong. A common guideline is that a single bet should never exceed 1-2% of your total bankroll. With a $200 bankroll, that caps your typical wager at $2 to $4.

Game volatility matters just as much. Low-volatility slots and table games like blackjack with basic strategy stretch your funds further, while high-volatility slots can devour a bankroll in minutes. If you’re playing for longevity rather than a jackpot, lean toward games with higher return-to-player percentages , many licensed Canadian slots publish RTP figures above 96%.

Also factor in payment fees. Some e-wallets charge transaction costs that quietly erode your bankroll. MuchBetter, for instance, built its Canadian reputation partly on transparent, low-cost transfers, which matters when every dollar counts toward your session budget.

Use Tools, Limits, and Time Checks

Licensed Canadian casinos are required to offer deposit limits, loss limits, and session timers. Use them. Setting a weekly deposit cap of, say, $50 removes the temptation to reload after a rough session.

Track your play with a simple spreadsheet or app. Players who log wins and losses tend to gamble 30-40% less impulsively, according to behavioural research. Time limits matter too , a two-hour session cap prevents fatigue-driven decisions.

Finally, take breaks. Step away every 30 minutes, and never play while upset, intoxicated, or chasing a loss. If gambling stops feeling like entertainment, resources like the Responsible Gambling Council offer free support across Canada.

Discipline isn’t restrictive , it’s what lets you enjoy the game for years instead of weeks.

MuchBetter Casino Deposits: Speed Test for Canadians

MuchBetter Casino Deposits: Speed Test for Canadians

MuchBetter arrived in the Canadian payments scene as a mobile-first wallet, and its pitch was simple: stop making players type card numbers into a cashier screen. Founded in 2017, the service had become a fixture at Canadian casino cashiers within roughly three years, and by the time most players encounter it today, it sits alongside Interac and standard credit cards as a default deposit option. But the question Canadian players actually ask is narrower: how fast is it, really? For more details, visit idebit deposit casino.

Speed matters more than most people admit. In online gaming, hesitation at the cashier is where deposits die. A player who waits 90 seconds for confirmation may abandon the transaction entirely, and that abandoned deposit is revenue no operator recovers. So the practical test for any wallet is not marketing language but time-to-funds. Here is how MuchBetter performs for Canadian users, tested against the alternatives they actually use.

How Fast Is a MuchBetter Deposit, Measured

For a funded wallet, a MuchBetter deposit into a Canadian casino account typically clears in under 30 seconds. In practice, most users see funds reflected in their balance somewhere between 10 and 25 seconds, with the wallet itself acting as the source and the casino confirming almost immediately. That places it firmly in the instant-deposit category, alongside Interac e-Transfer and ahead of any bank wire.

Card deposits are also fast, but they carry friction MuchBetter avoids. A credit card deposit can be declined for reasons the player cannot see, and some Canadian issuers block gaming merchants outright. With MuchBetter, once the wallet balance exists, the casino receives a pre-approved payment. There is no merchant-category rejection at the cashier level, which is why the wallet’s effective success rate on deposits runs higher than raw card attempts.

The one variable that changes the math is funding the wallet itself. A bank transfer into MuchBetter can take a business day or more, and that delay is the real cost. Players who keep a standing balance never feel it. Players who fund on impulse do. The wallet solves the casino-side speed problem while shifting the delay one step earlier.

Speed Comparison for Canadian Players

Method Typical Deposit Time Notes for Canadians
MuchBetter (funded wallet) 10-30 seconds Instant at cashier, no card declines
Interac e-Transfer 1-30 minutes Fast, but depends on bank processing
Credit card Instant to 5 minutes Issuer blocks are common
Bank wire 1-3 business days Slowest, rarely used for gaming

Fees, Limits, and the Details Canadians Should Check

MuchBetter does not charge the player a deposit fee for casino transactions in most cases, which is a meaningful advantage over methods that tack on a percentage. Where costs appear, they usually land on withdrawal or currency conversion, and since Canadian players are working in CAD throughout, conversion rarely applies. The absence of a deposit surcharge is one reason operators keep offering it.

Limits vary by casino rather than by the wallet. Most Canadian-facing sites set minimum deposits around CAD 10, with maximums frequently between CAD 5,000 and CAD 10,000 per transaction. For everyday play, those ceilings are irrelevant. For high-volume players, the cap may force multiple deposits, though each one still clears in seconds.

Verification is the quiet bottleneck. MuchBetter requires identity confirmation before full use, and a new account can sit in a limited state until documents are approved. Completing that step before a session, not during one, removes the only real delay a funded player is likely to face.

For Canadians who deposit regularly, the wallet’s value is consistency. It removes the guesswork about whether a payment will go through and delivers funds in seconds rather than minutes. That reliability, more than raw speed, is why it earned its place at the cashier.

How Canadian Gambling Taxes Actually Work

How Canadian Gambling Taxes Actually Work

The Legal Framework Behind Taxed Winnings

Canada occupies a peculiar position in the global gambling landscape. Unlike many jurisdictions where winnings are treated as ordinary income, the Canada Revenue Agency generally does not tax lottery prizes, casino jackpots, or sports betting payouts won by individuals. This surprises newcomers, yet the logic is rooted in decades of tax precedent rather than legislation written specifically for gamblers. For more details, visit muchbetter casinos.

The reasoning comes down to whether gambling constitutes a “source of income” under the Income Tax Act. The CRA typically classifies casual winnings as a windfall , a one-time, unpredictable gain , rather than a recurring revenue stream. Windfalls fall outside the taxable income framework, which is why a $50,000 jackpot at a provincial casino generally arrives tax-free.

That exemption, however, applies to the player, not the operator. Provincial governments have structured legal gambling as a revenue mechanism for public services, and the taxes operators pay flow directly into provincial coffers. In Ontario alone, gaming revenue contributes hundreds of millions of dollars annually toward healthcare and infrastructure.

When the CRA Does Step In

Professional gamblers face a different reality. If the CRA determines that gambling is your primary occupation , conducted with skill, discipline, and profit intent , winnings can be treated as business income and taxed at your marginal rate. Court rulings like Luprypa v. The Queen established that organized, systematic betting can cross the line from hobby into taxable enterprise.

This distinction matters for anyone betting seriously on sports or poker. The CRA looks at factors such as frequency, volume, record-keeping, and whether the activity is pursued with commercial organization. A casual bettor tracking picks on weekends rarely triggers scrutiny. Someone running a spreadsheet with thousands of wagers annually might.

There is no fixed threshold or dollar figure that automatically flags a gambler. The assessment is qualitative, and the burden of proof rests with the taxpayer to show the activity was not a business. Documentation, consistency, and intent all carry weight.

Provincial Taxes, Withholding, and Cross-Border Considerations

Provincial lotteries and casinos remit taxes on their gross revenue, not on individual payouts. That means the effective tax is already baked into the house edge , players never see a withholding line on a winning ticket. It is a quietly efficient system, one that funds everything from hospitals to amateur sports programs.

Cross-border situations complicate matters. A Canadian resident who wins at a land-based casino in the United States faces a 30% withholding tax on the gross payout, and reclaiming that money through a treaty claim can take months. Many casual players simply accept the loss rather than fight the paperwork.

Online operators licensed by provincial regulators, such as those governed by iGaming Ontario, fall under domestic rules, meaning winnings remain untaxed for the player. This regulatory clarity is one reason Canada’s legal online market has expanded rapidly, with regulated revenue climbing sharply since Ontario opened its competitive framework.

Situation Tax Treatment
Casual lottery or casino win Not taxable
Professional gambling income Taxed as business income
U.S. casino winnings 30% withholding, possible treaty recovery
Provincially licensed online winnings Not taxable for the player

The takeaway for Canadian players is straightforward: casual winnings generally stay yours, but scale and professionalism change the equation entirely. Understanding where that line sits is far more valuable than any betting system.

Taxes on Casino Winnings in Canada: What Players Actually Owe

Taxes on Casino Winnings in Canada: What Players Actually Owe

The General Rule: Lottery and Gambling Winnings Are Not Taxable

For most Canadian players, casino winnings are not subject to federal or provincial income tax. The Canada Revenue Agency treats gambling proceeds as a windfall rather than income, provided you are not in the business of gambling. Read more about this at best usdt casino.

This applies to slot jackpots, table game payouts, and even large sums won at a land-based casino. A player who wins CAD 50,000 on a single spin generally keeps the full amount, with no withholding at the cage.

The reasoning is straightforward: the CRA distinguishes between a hobby and a profession. Occasional play, even with substantial stakes, does not meet the threshold for taxable income. Only consistent, organized activity aimed at profit can trigger a different outcome.

When the CRA Can Tax Your Winnings

The exception is narrower than many people assume, but it does exist. If the CRA determines that gambling is your primary source of income, or that you apply professional-level skill and system to generate profit, winnings can be classified as business income.

Signs the agency looks for include playing full-time hours, tracking results with spreadsheets, treating losses as operating expenses, and relying on winnings to cover living costs. Poker is the most common area where this reclassification happens, since skill plays a measurable role.

Professional gamblers may then deduct related expenses, such as travel and buy-ins, but they also owe tax at their marginal rate. For high earners in provinces like Ontario or British Columbia, that can reach the top bracket of roughly 53 percent.

Payouts From Outside Canada and US Wins

Winnings from foreign operators are a different story. The United States withholds 30 percent on casino and lottery payouts to non-residents, though a tax treaty allows Canadians to recover part of that amount by filing the appropriate forms.

Online casinos licensed abroad generally do not report to the CRA, and Canadian players are not required to declare those winnings. That said, any funds deposited into a Canadian bank account can attract scrutiny if amounts are unusually large.

The practical takeaway: keep records of your play regardless. Accurate documentation protects you if the CRA ever questions the nature of your activity.

How to Read Canadian Casino Terms Without Getting Fooled

How to Read Canadian Casino Terms Without Getting Fooled

Wagering Requirements Are the First Thing You Need to Check

Most Canadian players scan a bonus offer and stop at the number. That is exactly what operators expect. A “$500 bonus” or “100 free spins” headline means nothing until you find the wagering requirement attached to it. In Canada, the industry standard sits between 30x and 50x, though some platforms push past 60x. For more details, visit visa online casino.

Here is the math that matters. A $100 bonus at 40x wagering requires $4,000 in total bets before you can withdraw a single dollar of bonus-derived winnings. If the same bonus carries a 35x requirement, that figure drops to $3,500. Over a dozen deposits, that gap adds up fast.

Also check what the multiplier applies to. Some operators calculate wagering on the bonus amount alone. Others apply it to bonus plus deposit. A 40x requirement on a $100 bonus with a $100 deposit becomes $8,000 in playthrough, not $4,000. This single detail changes the entire value proposition.

Look for the contribution table next. Not every game counts equally. Slots typically contribute 100 percent toward wagering, while table games like blackjack and roulette often sit at 10 percent or lower. Some operators exclude certain titles entirely.

Time Limits, Maximum Bets, and Withdrawal Caps

Canadian casino terms almost always include an expiry window. Seven days is common. Thirty days is generous. If you cannot realistically clear the wagering in that period, the bonus is designed to expire before you finish.

Maximum bet clauses catch players off guard. Many terms limit individual wagers to $5 or $10 while a bonus is active. Exceed that limit once, and the operator can void your entire balance. There is no appeal process in most cases.

Withdrawal caps are quieter but equally important. Some bonuses cap winnings at 10x the bonus value. Win $5,000 on a $100 bonus with a 10x cap, and you collect $1,000. The rest disappears. Look for phrases like “maximum conversion” or “maximum cashout” in the terms section.

Payment method restrictions also apply. Deposits made through certain methods may disqualify you from bonus eligibility entirely. This varies by operator, so verify before you deposit.

Where to Find Terms and What to Do When They Are Unclear

Terms live at the bottom of the casino homepage, usually under “Terms and Conditions,” “Bonus Terms,” or “Promotions.” General terms and bonus-specific terms are often separate documents. Read both.

Use your browser’s search function. Type “wagering,” “maximum bet,” “expiry,” and “withdrawal” to jump directly to the clauses that affect your money.

If something reads ambiguously, contact support before depositing and save the response. Written confirmation from support carries weight if a dispute arises later. Screenshot the bonus offer page too, since terms can change without notice.

Canadian players have no single national regulator, so enforcement varies by province. That makes reading the terms yourself the most reliable protection you have. Five minutes of careful reading beats a week of arguing with support over a voided withdrawal.

MuchBetter vs PayPal in Canada: Which E-Wallet Wins for Casino Players?

MuchBetter vs PayPal in Canada: Which E-Wallet Wins for Casino Players?

The Trust Factor: Established Giant vs. Casino Specialist

PayPal needs no introduction to Canadians. With roughly 19 million active users across the country, it is the default digital wallet for online shopping, splitting dinner bills, and sending money to family. Its brand recognition is unmatched, and that trust runs deep. Read more about this at mastercard online casino.

MuchBetter plays a different game. Launched in 2017, it deliberately targeted the online gambling sector rather than general retail. By 2020, it had become a fixture at Canadian casino cashiers, and that focus shows. Where PayPal treats casino transactions as a reluctant side business, MuchBetter built its entire infrastructure around them.

For Canadian players, the practical difference matters. PayPal has historically restricted gambling transactions in several markets, and Canadian casinos often cannot process deposits through it at all. MuchBetter, by contrast, works with hundreds of gaming operators and processes casino payments without friction. That single distinction shapes everything that follows.

Speed, Fees, and What Actually Lands in Your Account

Both wallets move money quickly, but the numbers differ. PayPal transfers from a linked bank account typically clear within one business day, while MuchBetter deposits are near-instant once funded.

Fees tell a sharper story. MuchBetter charges a 2.5% fee on standard casino deposits, though many operators absorb this cost for players. Withdrawals back to the wallet are free, and the MuchBetter Mastercard carries no annual charge. PayPal, meanwhile, applies currency conversion spreads of roughly 3% to 4% when Canadian dollars meet foreign transactions, and business-related fees can climb higher.

Withdrawal speed also favours the challenger in gaming contexts. Casino payouts to MuchBetter often settle in under an hour. PayPal cashouts from gambling sites are frequently blocked outright or delayed for manual review. For a player who wants winnings in hand the same evening, that gap is decisive.

One caveat worth noting: MuchBetter’s Canadian dollar support has expanded but remains less seamless than PayPal’s native multi-currency handling. Players depositing in CAD should confirm the operator’s processing currency before committing.

Security, Bonuses, and the Practical Verdict

Both platforms rely on strong encryption and two-factor authentication, so baseline safety is comparable. MuchBetter adds a genuinely useful feature for casino users: a dynamic CVV that regenerates with every transaction, which limits card-not-present fraud. PayPal counters with decades of consumer protection policy and chargeback infrastructure.

The promotional angle tilts clearly toward MuchBetter. Casinos frequently bundle deposit matches, free spins, or reduced wagering requirements specifically for MuchBetter transactions, offers rarely extended to PayPal users because so few operators support it. These perks can add 10% to 25% in extra value on a first deposit.

Speed, casino acceptance, and bonus eligibility all point one direction. PayPal remains the better everyday wallet for groceries and e-transfers, but for Canadian casino play, MuchBetter is the stronger tool. Players who value instant withdrawals and deposit perks should treat MuchBetter as their primary option.

  • MuchBetter: built for gambling, near-instant withdrawals, 2.5% deposit fee
  • PayPal: broader retail use, limited casino support, 3% to 4% conversion spreads
  • Winner for casino players: MuchBetter, by a wide margin

Best High RTP Slots for Australian Players

Best High RTP Slots for Australian Players

Why RTP Matters More Than You Think

Return to player, or RTP, is the long-run percentage of all wagered money a pokie pays back to players over millions of spins. A game rated at 96.50% returns $96.50 for every $100 cycled through it, while the remaining $3.50 becomes the house edge. That gap sounds tiny, but it compounds quickly across a long session. For more details, visit australian online pokies real money.

The difference between a 94% and a 97% pokie is roughly three dollars per hundred wagered. Over 1,000 spins at $1 a spin, that is about $30 in theoretical value , real money that stays in your pocket rather than the operator’s. For Australian players who enjoy regular sessions, slot selection is one of the few variables entirely within their control.

It pays to know which games sit at the generous end of the scale. Most modern releases cluster between 94% and 96.5%, but a select group pushes past 97%, and those titles deserve a spot on any smart punter’s shortlist.

The Standout High RTP Titles

Mega Joker from NetEnt is the classic outlier, offering a base-game RTP of 97.50% that climbs toward 99% when the Supermeter mode is played correctly. It is a low-volatility, three-reel game, so wins arrive steadily rather than in dramatic bursts.

Blood Suckers, also NetEnt, sits at 98.00% and remains one of the highest-paying video slots ever produced. Its vampire theme is dated, but the mathematics are exceptional, with a frequent bonus round that keeps bankrolls ticking over.

Jackpot 6000 returns 98.90% in its optimal configuration, while 1429 Uncharted Seas from Thunderkick pays 98.60% and pairs that figure with medium volatility. For players who want modern visuals alongside elite numbers, Book of 99 from Relax Gaming delivers 99.00% , among the highest verified rates in the industry.

How to Compare Pokies Like a Pro

Start with the paytable, not the artwork. Every legitimate operator publishes RTP figures, and in Australia these are usually accessible via the in-game help menu. If a casino hides the number, treat that as a warning sign.

Volatility matters just as much as RTP. A 97% pokie with extreme variance can wipe a modest bankroll before the percentage has any chance to work in your favour. Match volatility to your balance and session length.

Consider these practical checkpoints:

  • Confirm the RTP in the game’s info screen, not a review site
  • Prefer titles above 96% for extended play
  • Check whether bonus buys change the effective RTP
  • Set a loss limit before your first spin

Finally, test games in demo mode where available. Free play reveals how often features trigger and how the base game behaves, which no statistic can fully convey. Combine that hands-on knowledge with a disciplined budget, and high RTP slots become a genuinely smarter way to play.

Comment éviter la dépendance aux jeux : méthodes et repères concrets

Comment éviter la dépendance aux jeux : méthodes et repères concrets

Comprendre les mécanismes du jeu problématique

La dépendance aux jeux d’argent ne survient pas par hasard. Elle repose sur un circuit neurologique précis : le système de récompense libère de la dopamine lors de l’anticipation du gain, et non uniquement lors du gain lui-même. Cette particularité explique pourquoi les quasi-victoires, comme deux symboles alignés sur trois, entretiennent le comportement autant qu’un vrai paiement. Pour plus de détails, visitez nouveau casino.

Les études menées auprès de joueurs réguliers indiquent qu’environ 1 à 2 % des pratiquants développent une pratique problématique. Ce chiffre grimpe à près de 10 % chez les utilisateurs de machines à sous et de jeux en ligne à cadence rapide, où les tours se succèdent en quelques secondes.

Un autre facteur amplifie le risque : la disponibilité permanente. Sur les plateformes Bitcoin, les retraits et dépôts s’exécutent 24 heures sur 24, sans intermédiaire bancaire. La friction qui freinait autrefois les dépôts impulsifs disparaît presque entièrement, ce qui oblige le joueur à créer lui-même ses propres barrières.

Fixer des limites avant de commencer une session

La règle la plus efficace reste simple : définir un budget et une durée avant d’ouvrir un compte ou de lancer un jeu. Une fois ces seuils atteints, l’arrêt doit être immédiat, sans négociation intérieure.

La plupart des casinos en ligne proposent des outils de contrôle intégrés, souvent sous-estimés :

  • Limites de dépôt quotidiennes, hebdomadaires ou mensuelles
  • Limites de pertes configurables sur une période donnée
  • Rappels de temps de jeu automatiques
  • Périodes d’auto-exclusion de 24 heures à plusieurs mois
  • Tests d’auto-évaluation accessibles depuis le compte joueur

Ces dispositifs ne sont pas décoratifs. Les opérateurs régulés sont tenus de les appliquer, et un joueur qui les active ne peut généralement pas les modifier à la hausse avant l’expiration du délai choisi. C’est précisément leur force : ils protègent contre les décisions prises sous l’impulsion.

Adopter des habitudes de jeu structurellement saines

Éviter la dépendance passe aussi par des choix concrets au quotidien. Jouer pour se refaire après une perte constitue le signal d’alerte le plus fiable. De même, emprunter de l’argent ou utiliser des fonds destinés aux charges courantes transforme un loisir en risque financier réel.

Quelques repères simples aident à garder le contrôle :

  1. Ne jamais jouer sous l’effet de l’alcool ou d’une émotion forte
  2. Considérer chaque mise perdue comme dépensée, jamais comme récupérable
  3. Alterner les activités et ne pas faire du jeu une routine quotidienne
  4. Suivre ses dépenses dans un journal ou un relevé mensuel

Enfin, lorsque le jeu cesse d’être un divertissement, des ressources existent. En France, le dispositif d’aide à distance de l’ANJ permet un chat ou un appel gratuit avec des professionnels formés. Reconnaître le problème tôt reste le facteur qui change le plus souvent la trajectoire d’un joueur.

Choosing the Right Online Casino for You

Choosing the Right Online Casino for You

Start With Licensing, Then Look at the Extras

Walk into any Ontario casino floor and you will find dozens of tables, hundreds of slots, and staff members who need a license to run the show. The online world works the same way. A legitimate operator holds a valid gaming license, publishes clear terms, and responds to player questions within a reasonable time frame. Read more about this at casinos accepting mastercard.

Licensing is not just paperwork. It signals that the site has passed audits on game fairness, has segregated player funds, and follows responsible gambling rules. In Canada, provincial regulators such as the Alcohol and Gaming Commission of Ontario (AGCO) oversee legal operators, while offshore sites may fall under the Malta Gaming Authority or the UK Gambling Commission.

Before you deposit a single dollar, check three things: the license number, the company address, and the dispute resolution policy. If any of these are missing, move on. A site that hides basic information will not treat your balance any better.

Match the Casino to How You Actually Play

Not every player wants the same experience. Some chase progressive jackpots, others prefer live dealer tables, and a growing number simply want fast payouts with low fees. Knowing your own habits makes the choice far easier.

If you play mostly on your phone, test the mobile version before signing up. Load times, button size, and menu layout matter more than flashy graphics. If you prefer table games, look at the range of blackjack, roulette, and baccarat variants , a strong library usually has 50 or more options.

Casual players should focus on wagering requirements and bonus terms. A generous headline bonus often carries a 35x or 40x playthrough requirement, which can be hard to clear on low-stakes bets. Meanwhile, high rollers may want higher table limits and personal account managers rather than a welcome bonus.

Payment methods deserve equal attention. Canadian players commonly use Interac, Visa, Mastercard, and e-wallets. Deposit and withdrawal times vary widely , some sites process e-wallet cashouts in under 24 hours, while bank transfers can take three to five business days.

One area that catches new players off guard is fees. Using debit cards at online casinos can trigger a fee of 1.5% to 3%, and some operators pass on currency conversion charges. You can read more about how iDebit casinos for Canadian players handle deposits to understand what a fair fee structure looks like before committing.

Test Support, Bonuses, and Responsible Tools

Customer support is the quiet test of any casino. Send a quick question before you register and note the response time. Live chat should reply in under five minutes, and email within 24 hours. A slow or evasive answer now usually means a slow or evasive answer when you have a withdrawal pending.

Bonuses should be read carefully, not just celebrated. Look at the wagering multiplier, the maximum bet allowed while clearing it, and the expiry window. A 100% match bonus with a 30-day expiry is far friendlier than a 200% offer that expires in seven days.

Finally, check the responsible gambling tools. Reputable operators provide deposit limits, session reminders, time-outs, and self-exclusion options. If those features are buried or missing, that tells you something about the site’s priorities.

  • Verify the license and regulator
  • Compare withdrawal speeds and fees
  • Test mobile performance and support response
  • Read bonus terms line by line
  • Confirm responsible gambling tools exist

Take your time with these steps. A casino that fits your budget, your device, and your playing style will always beat one that simply shouts the loudest.

Guide to Bank Transfer Casinos in Canada

Guide to Bank Transfer Casinos in Canada

Bank transfers occupy a peculiar position in the Canadian online gambling market. They are trusted by nearly every financial institution, yet they are rarely the fastest option at the checkout. For players who prioritize security and larger transaction sizes over instant gratification, bank transfer methods , including Interac e-Transfer, direct bank wire, and Instant Bank Transfer , remain a genuinely useful tool. This guide breaks down how they work, what they cost, and which platforms handle them best. Discover further information on muchbetter payment casino.

Canada’s gambling landscape is regulated province-by-province, with the Alcohol and Gaming Commission of Ontario overseeing the largest legal market. That means the banking rails you use matter, and not every offshore operator supports Canadian financial institutions cleanly. Knowing the difference between a domestic Interac transfer and an international wire can save you both time and money.

How Bank Transfer Deposits Work at Canadian Casinos

Most Canadian-facing casinos offer three distinct bank-based deposit routes: Interac e-Transfer, Interac Online, and traditional wire transfer. Interac e-Transfer is by far the most popular, used by roughly 80% of Canadian online gamblers who deposit through a bank. It works by sending funds from your online banking portal to an email address or mobile number supplied by the casino’s payment processor.

Interac Online differs slightly. It redirects you straight to your bank’s secure login page, authorizing the payment without leaving the casino cashier. Only a handful of major banks , RBC, TD, Scotiabank, and BMO among them , support this method, and daily limits typically sit between $1,000 and $3,000.

Direct bank wire transfers take the longest. Domestic wires usually settle within one business day, while international wires can take three to five business days. The trade-off is capacity: wires often accommodate deposits of $10,000 or more, making them the choice for high rollers.

  • Interac e-Transfer: 30 minutes to 2 hours, fees usually $0-$2
  • Interac Online: Instant, no casino fee, bank limits apply
  • Wire transfer: 1-5 business days, $15-$40 in bank fees

Fees, Limits, and Withdrawal Realities

Deposit fees at reputable casinos are typically zero, but your bank may charge separately. Interac e-Transfers are free at most Canadian institutions, while outgoing wires commonly cost $20 to $40. Always check your bank’s schedule of charges before committing to a large transfer.

Withdrawals are where bank transfers shine. Interac e-Transfer cashouts arrive in one to three business days, and many casinos cap them at $10,000 per transaction. Wire withdrawals, meanwhile, can take up to seven business days but rarely carry upper limits below $50,000.

Method Deposit Time Withdrawal Time Typical Fee
Interac e-Transfer 30 min – 2 hrs 1 – 3 days $0 – $2
Interac Online Instant Not supported $0
Bank Wire 1 – 5 days 3 – 7 days $15 – $40

One recurring frustration involves verification. Casinos are required to confirm your identity before releasing bank-based withdrawals, and that process can add 24 to 48 hours on a first cashout. Submitting documents early shortens the wait considerably.

Why Players Still Choose Bank Transfers

Speed is not everything. Bank transfers leave a clear, traceable paper trail, which appeals to players who want transaction records for tax or budgeting purposes. They also avoid the volatility of cryptocurrency and the prepaid-card fees that eat into smaller deposits.

For Ontario residents in particular, Interac-based options integrate directly with the regulated market, meaning deposits flow through audited channels. That level of oversight is difficult to replicate with e-wallets or crypto, and it explains why bank methods continue to hold roughly a third of all Canadian online casino deposits.

The main drawbacks are withdrawal delays and inconsistent bank policies. Some institutions still block gambling-related transactions outright, so confirming your bank’s stance before registering an account is a sensible first step.

Used correctly, bank transfers deliver a dependable, low-cost path in and out of Canadian online casinos. They reward patience rather than urgency, and for players moving meaningful sums, that trade-off is usually worth it.

Common Withdrawal Delays at Canadian Casinos

Common Withdrawal Delays at Canadian Casinos

Canadian players rarely complain about making deposits. Money moves instantly, and most payment rails are frictionless. The friction appears when it is time to cash out. Industry surveys suggest that roughly 30% of player support tickets at Canadian-facing operators involve payout timing, and the average withdrawal wait across the market sits somewhere between 24 and 72 hours. Understanding why those delays happen is the fastest way to avoid them. Discover further information on best dogecoin casinos.

Delays are not random. They follow predictable patterns tied to licensing, payment infrastructure, and internal anti-fraud checks. Once you know the pattern, you can choose an operator whose cashier is built for speed rather than one that quietly profits from slow processing.

Why Payouts Stall: Verification, Payment Rails and Banking Hours

The single biggest cause of delay is identity verification. Under FINTRAC rules, licensed operators must confirm a player’s identity before releasing funds. If documents are missing or blurry, the clock stops. Some casinos complete this check within minutes of registration, while others wait until the first withdrawal request, adding 24 to 48 hours overnight.

Payment method choice matters just as much. Interac e-Transfer payouts typically land in 1 to 4 hours at well-run casinos, while bank wires can take 3 to 5 business days. Credit card withdrawals are the slowest option because funds must be routed back through the original payment network, a process that can stretch past a full week.

Cashier hours also create artificial delays. Many sportsbooks and casino platforms process payout batches only on business days during office hours. A request submitted Friday evening may not be reviewed until Monday morning, effectively adding two days of dead time that has nothing to do with your account.

Bonus terms are another quiet culprit. Wagering requirements on deposit matches routinely block withdrawals until turnover conditions are met. Players who request a payout mid-wagering are often rejected and returned to the queue, losing their place entirely.

How to Reduce Withdrawal Waiting Times

Choose operators that separate themselves through speed. iDebit casinos stand out here, because the iDebit network was built for real-time bank-to-casino transfers, and it now powers payouts at dozens of Canadian platforms. The best of them complete e-Transfer withdrawals in under 60 minutes and advertise that 95% of cashouts clear within one business day.

Verify your account early. Upload your government ID, proof of address and payment method confirmation during registration rather than at withdrawal time. Players who verify upfront report payout times that are up to 70% faster than those who wait.

Use the same method for deposits and withdrawals. This lets the operator route the payout back through a channel it already trusts, which trims internal review time and often removes the need for manual approval.

Keep an eye on processing schedules. If a casino only releases funds Monday through Friday, submitting a request on Thursday morning is far smarter than submitting it on Saturday night.

Finally, read the terms before claiming a bonus. A 40x wagering requirement on a $200 bonus means $8,000 of play before a single dollar leaves the account. That is not a delay , it is a locked door.

What to Do When a Withdrawal Is Stuck

Contact live support first and ask for a specific timeline, not a general reassurance. Quote your request reference number and the exact time you submitted it. Operators that handle payouts through dedicated iDebit cashier integrations typically resolve stuck requests within 24 hours, while slower platforms may take three to five business days.

If the delay extends beyond the advertised window by more than 48 hours, escalate. Licensed operators in Ontario, Quebec and other regulated provinces must respond to formal complaints, and the Alcohol and Gaming Commission of Ontario reports that a majority of escalated payout disputes resolve in the player’s favour.

Keep records. Screenshots of your request, chat transcripts and confirmation emails make escalation straightforward and turn a vague complaint into a documented case.

Best Reload Bonuses for Regular Pokies Players

Best Reload Bonuses for Regular Pokies Players

Reload bonuses are the quiet workhorses of online pokies. Unlike the flashy welcome package that greets you once, a reload offer rewards you every time you top up your balance, which makes it the most valuable promotion for anyone who plays regularly. For Australian punters who log in a few times a week, these deals can add hundreds of dollars in extra play over a single month. Discover further information on best mastercard casino.

Understanding how reloads work , and where to find the strongest ones , is the difference between grinding through your own funds and stretching every deposit further. This guide breaks down the mechanics, the numbers, and the practical steps to claim them.

How Reload Bonuses Work

A reload bonus is a percentage match on a deposit you make after your first one. Most Australian-facing casinos structure them between 25% and 100%, with caps typically sitting anywhere from $100 to $500 per transaction. A typical offer might read “50% up to $200 every Friday” , deposit $200 and you play with $300.

These offers usually run on a fixed schedule: weekend reloads, midweek top-ups, or monthly VIP matches. Some sites pump out reloads daily, which suits high-volume players, while others focus on a single weekly drop so the value stays concentrated.

Wagering requirements are the key figure to check. Reload deals generally carry playthrough of 25x to 40x the bonus amount, and pokies contribute 100% toward clearing it at most casinos. That is far friendlier than table games, which often count at just 10% to 20%.

Time limits matter too. A 7-day window is standard, but some operators allow up to 30 days, giving casual players room to clear the terms without rushing.

What Makes a Reload Bonus Worth Claiming

Not every match is created equal. A 100% bonus with a $10 maximum is worth less than a 30% match capped at $500. Look at the absolute dollar value, not just the headline percentage.

Also weigh the minimum deposit. Offers starting at $10 or $20 suit casual players, while $50 minimums tend to unlock better percentages. If a casino demands a $100 deposit for a 25% match, the maths rarely stacks up against a rival offering 50% on $20.

  • Bonus percentage and maximum cap
  • Wagering requirement and game weighting
  • Deposit minimums and eligible payment methods
  • Expiry period and frequency of the offer
  • Maximum bet allowed while clearing the bonus

That last point catches people out. Exceed the capped bet size , often $5 or $10 per spin , and the casino can void your winnings. Read the terms before you spin.

Maximising Value as a Regular Player

Loyalty programmes are where reloads get interesting. Many casinos tier their offers, so the more you deposit over a month, the higher your match climbs. A player who deposits $1,000 monthly might unlock a 75% reload, while a newcomer sees only 30%.

Player Tier Typical Reload Monthly Value
Bronze 30% up to $100 ~$120
Silver 50% up to $250 ~$400
Gold 75% up to $500 ~$900

Stacking matters. Combine a reload with free spins or a cashback deal and your effective edge grows considerably. Always set a budget and treat the bonus as entertainment value rather than guaranteed profit.

Finally, check whether winnings from reload bonuses carry a maximum cashout. Caps of $500 to $2,000 are common, and knowing yours prevents nasty surprises at withdrawal time.

How to Use PayPal for Pokies in Australia

How to Use PayPal for Pokies in Australia

Why PayPal Appeals to Australian Pokies Players

PayPal remains one of the most recognised payment platforms on the planet, with more than 400 million active accounts worldwide. For Australian players who value speed and familiarity, it offers a convenient way to move money without entering card details at every site. Check out additional details at top crypto casinos.

The appeal is straightforward. Transactions typically clear within minutes, buyer protection covers eligible purchases, and your bank details stay hidden from merchants. That last point matters to players who prefer not to share financial data across multiple platforms.

However, there is an important catch. PayPal’s own acceptable use policy prohibits transactions linked to gambling in many jurisdictions, and Australian-licensed online casinos generally cannot process pokies deposits through this provider. Understanding this landscape saves you time and frustration before you sign up anywhere.

How Players Work Around the PayPal Restriction

Because direct deposits are rarely available, experienced players often use indirect methods. The most common approach involves funding an e-wallet or prepaid card with PayPal, then using that service at the casino. This adds a step but keeps your banking details private.

Another option is a bank transfer funded through your PayPal balance. Some platforms accept these, though processing can take one to three business days depending on your financial institution.

Before committing, always check the cashier page of your chosen site. Look for recognised e-wallet logos, confirm the minimum deposit (often $10 to $20), and review withdrawal timeframes. Pokies payouts through e-wallets usually land within 24 to 48 hours, compared with up to five days for bank transfers.

It also pays to verify licensing. Sites regulated by authorities such as the Malta Gaming Authority or Curacao eGaming tend to offer more reliable payment processing than unlicensed operators.

Practical Steps and Safety Checklist

If you decide to proceed, follow a simple process. First, confirm the casino accepts your chosen e-wallet. Second, fund that wallet through PayPal. Third, deposit at the cashier and claim any welcome bonus, which frequently ranges from 100% to 200% matched on your first deposit.

Keep these points in mind:

  • Check withdrawal limits before depositing large amounts
  • Confirm whether bonus funds carry wagering requirements, often 30x to 40x
  • Enable two-factor authentication on both PayPal and the casino account
  • Keep records of transactions for tax and dispute purposes

Finally, set a budget and stick to it. Pokies are entertainment, not income. Responsible gambling tools such as deposit limits and session reminders are available at reputable sites and take only moments to activate.

Top Pokies Games for E-Wallet Players

Top Pokies Games for E-Wallet Players

Why E-Wallet Players Choose Specific Pokies

Australian pokies fans who fund their accounts through digital wallets tend to prioritise speed, security and seamless withdrawals above all else. E-wallet transactions typically clear in under 24 hours, compared with 1-3 business days for traditional bank transfers, which changes how players approach game selection. Fast payouts mean fewer restrictions on when you can cash out and reload, so games with flexible bet ranges and frequent bonus triggers become far more attractive. Discover further information on neosurf casinos.

Another factor is volatility. E-wallet users often prefer medium to high volatility titles because they can top up instantly after a dry spell without waiting on a deposit to clear. Titles with return-to-player rates above 96% also rank highly, since every percentage point matters over hundreds of spins.

Mobile compatibility rounds out the picture. Most e-wallet users play on smartphones, so games built with HTML5 and responsive controls naturally dominate the most-played lists. If a pokie lags or resizes poorly on a small screen, it rarely survives long in this niche.

The Standout Titles Worth Your Attention

Gates of Olympus remains a fixture among digital wallet players thanks to its tumble mechanic and multipliers that can reach 500x. Its 96.5% RTP and instant-win structure suit players who deposit in small, frequent amounts. Sweet Bonanza follows closely, with a 96.51% RTP and a bonus buy option that appeals to e-wallet users comfortable with quick decisions.

For classic pokies fans, Big Bass Bonanza delivers a 96.71% RTP and simple mechanics that load fast even on older devices. Money Train 3 pushes volatility to the extreme, but its 96.1% RTP and bonus features draw players chasing large single payouts rather than steady grinding.

Progressive jackpot hunters often gravitate toward Mega Moolah, which has paid out some of the largest sums in pokies history. The trade-off is a lower base RTP of around 88%, so e-wallet players should treat it as a jackpot lottery rather than a grinding game.

Below is a quick comparison of the key metrics for these titles:

Game RTP Volatility Best For
Gates of Olympus 96.5% High Multiplier chasers
Sweet Bonanza 96.51% High Bonus buy fans
Big Bass Bonanza 96.71% Medium Casual mobile play
Money Train 3 96.1% Extreme Big payout hunting
Mega Moolah ~88% High Jackpot seekers

Matching Games to Your Wallet Strategy

Your deposit pattern should shape which pokies you play. Players who top up frequently in small amounts generally do better with medium-volatility games that return wins steadily. Those who deposit larger sums less often can afford the swings of extreme-volatility titles like Money Train 3.

Withdrawal limits matter too. Some e-wallets cap daily cash-outs, so check whether your chosen casino matches those limits before committing to a high-stakes session. Games with a maximum win cap of 5,000x or 10,000x are common, and knowing that ceiling helps you set realistic expectations.

Finally, always confirm the casino holds a valid licence and that your chosen e-wallet supports instant deposits in AUD. Speed means little if the platform itself is unreliable. Choose games that match your bankroll style, keep sessions disciplined, and let the wallet do what it does best , move your money quickly when it counts.

How to Read Casino Terms and Conditions in Australia

How to Read Casino Terms and Conditions in Australia

Why the Fine Print Matters More Than the Bonus Banner

Australian players are drawn to online casinos by eye-catching welcome offers, yet the real story sits in a document most people scroll past. Terms and conditions govern everything from how a bonus is released to whether a withdrawal ever reaches your bank account. For more details, visit best mastercard casino.

Research from consumer advocacy groups suggests a large share of player complaints stem from misunderstood wagering requirements rather than unfair games. In other words, the rules were there , they simply weren’t read.

Treating the T&Cs like a contract, not a formality, is the single most useful habit a punter can develop. It takes ten minutes and can save hundreds of dollars.

The Clauses That Deserve Your Full Attention

Wagering requirements top the list. A “50x” figure means you must bet the bonus amount fifty times before withdrawing winnings. On a $100 bonus, that’s $5,000 in turnover , a figure that separates realistic offers from impossible ones.

Maximum bet limits often sit between $5 and $10 per spin while a bonus is active. Break that cap and the casino can void your entire balance, even if you were winning.

Withdrawal caps are equally important. Some promotions limit cash-outs to $100 or $200 from bonus funds, regardless of how much you accumulate.

Game weighting determines how much each pokie or table game contributes. Pokies usually count 100%, while live dealer games might contribute just 10% or nothing at all.

Finally, check the expiry period. Bonus funds commonly vanish after 7 to 30 days, and unused spins rarely survive longer.

A Practical Checklist Before You Deposit

Work through these points methodically rather than skimming:

  • Locate the wagering requirement and calculate the true turnover needed.
  • Confirm the maximum bet permitted while the bonus is live.
  • Note the withdrawal ceiling attached to promotional winnings.
  • Check which games contribute and at what percentage.
  • Read the expiry window and any payment-method restrictions.

Licensing details also deserve a glance. A legitimate operator displays its authority , such as a Northern Territory or international regulator , plus responsible gambling tools like deposit limits and self-exclusion.

Payment clauses matter too. Some casinos exclude deposits made via certain e-wallets from bonus eligibility, and processing times for withdrawals can range from a few hours to five business days depending on the method.

If a term feels deliberately vague, that vagueness is usually intentional. Clear, well-drafted conditions protect both parties. When in doubt, contact live support and keep a copy of their written response , it becomes your evidence if a dispute arises later.

Best Welcome Bonus Offers in Australia: A Practical Guide for New Players

Best Welcome Bonus Offers in Australia: A Practical Guide for New Players

Welcome bonuses remain the single biggest drawcard for Australian players signing up to a new online casino. Whether you prefer pokies, table games or live dealer titles, a well-structured sign-up offer can stretch your bankroll considerably and give you room to explore a platform before committing real money. This guide breaks down how these offers work, what separates a genuinely valuable deal from a hollow headline, and which features deserve your attention when comparing options. Read more about this at online casino neosurf.

It is worth understanding the maths before you claim anything. A generous-looking “$5,000 bonus” often comes with wagering requirements of 40x or higher, meaning you may need to turn over tens of thousands of dollars before withdrawing a cent. The smarter approach is to weigh the bonus size against the playthrough terms, the maximum bet allowed while clearing it, and the time limit attached.

How Australian Welcome Bonuses Are Structured

Most operators now package their introductory offer as a matched deposit spread across your first two to five deposits. A typical structure might match 100% up to $500 on deposit one, then 50% up to $300 on deposit two, with smaller percentages on subsequent top-ups. The total headline figure looks impressive, but the first-deposit portion is usually where the real value sits.

Free spins are frequently bundled in alongside the cash match. You might see 100 or 200 spins credited on a specific pokie, valued at $0.10 to $0.50 per spin. Winnings from these spins are typically paid as bonus credit rather than cash, so the same wagering conditions apply. No-deposit bonuses, while rare and modest, offer a genuine risk-free way to test a site , often $10 to $20 in bonus credit or a handful of spins.

Wagering requirements are the critical variable. Anything at or below 30x is considered competitive in the current market, while 50x or more should be treated with caution. Also check game weighting: pokies usually contribute 100% toward playthrough, but table games and live dealer options may count for only 10% or 20%, or be excluded entirely.

What Separates a Premium Offer From an Average One

Licensing and payout reliability matter more than the bonus figure itself. A platform operating under a recognised regulator, with transparent audit trails and a documented history of on-time withdrawals, is worth far more than an extra $200 in bonus credit. Payment methods deserve scrutiny too , Australian players increasingly favour e-wallets and PayID-style instant transfers over traditional bank deposits, which can take one to three business days to clear.

Look for these markers of a quality welcome package:

  • A clear, plain-English summary of wagering requirements on the promotions page
  • Reasonable maximum bet limits (usually $5 to $10 per spin while clearing)
  • No hidden caps on how much you can win from bonus funds
  • Withdrawal processing times under 24 hours for verified accounts
  • Live chat support available during Australian peak hours

One practical tip: read the terms before depositing, not after. If the conditions feel deliberately confusing, that is usually a signal in itself. Reputable operators want you to understand the deal, because a smooth first experience is what keeps you playing.

Getting Maximum Value From Your First Deposit

Timing and discipline do most of the work here. Claim the full matched amount if your budget allows, since leaving part of a 100% match unclaimed is effectively turning down free credit. Set a session limit before you start, and remember that clearing a bonus requires patience , chasing losses to hit playthrough faster is the fastest route to a depleted balance.

Beyond the welcome offer, check the ongoing promotions calendar. Reload bonuses, weekly cashback and loyalty tiers often deliver better long-term value than the headline sign-up deal. A site offering 10% weekly cashback on net losses can return more over a year than a one-off $1,000 match.

Finally, verify your identity early. Sending through your documents at sign-up rather than at withdrawal time avoids the frustration of a delayed payout just when you want to cash out your winnings. Treat the welcome bonus as a trial period rather than a windfall, and you will get far more from it.

Best High Limit Pokies for Australian Players

Best High Limit Pokies for Australian Players

High limit pokies appeal to players who want bigger stakes, larger jackpots and the chance to win sums that simply aren’t possible on penny machines. In Australia, the appetite for premium spinning is strong, and online platforms have responded with dedicated high roller rooms, VIP programs and table limits that stretch into the thousands per spin. Understanding what separates a genuinely good high limit game from a mediocre one helps you get more value from every dollar you wager. For more details, visit google pay withdrawal casino.

What Makes a High Limit Pokie Worth Playing

The defining feature of a high limit pokie is the minimum bet per spin, usually starting at $5 and climbing to $50, $100 or more. Games built for this bracket almost always carry higher return-to-player percentages than their low-stakes counterparts. While the average pokie sits around 94-96% RTP, premium high limit titles frequently reach 97% or even 98%, which matters enormously over thousands of spins.

Volatility is the other key metric. High limit players generally prefer medium-to-high variance, because the whole point is chasing substantial payouts rather than grinding small wins. A game with a maximum win of 10,000x your stake, played at $20 per spin, offers a theoretical top prize of $200,000 from a single round.

Popular High Limit Titles

Several names consistently appear on high roller shortlists. Classics such as Mega Moolah and Major Millions offer progressive jackpots that regularly exceed $1 million, with minimum bets that suit serious bankrolls. Modern releases like Book of Dead, Bonanza and Wolf Gold provide high max bets, generous multipliers and free spin rounds that can extend play significantly.

  • Mega Moolah , progressive jackpots, 88.12% base RTP but life-changing top prizes
  • Book of Dead , 96.21% RTP, 5,000x maximum win
  • Bonanza Megaways , 96% RTP, up to 117,649 ways to win
  • Wolf Gold , 96% RTP, three fixed jackpots

Managing Your Bankroll at High Stakes

Discipline separates successful high limit players from those who burn through funds quickly. A sensible rule is to keep individual spins at no more than 1% of your total bankroll. If you deposit $2,000, that means betting around $20 per spin, which gives you roughly 100 spins before variance takes over.

Always check the maximum bet limit before committing. Some high limit pokies cap at $50 or $100, while true high roller tables allow $500 or more. Match the game’s limit to your comfort level rather than stretching beyond it.

Finally, take advantage of VIP loyalty schemes. Many Australian-facing casinos offer cashback of 5-15% on losses, personalised bonuses and faster withdrawal processing for high rollers. These perks can add real value over a long session and are often the difference between an average experience and an excellent one.

High Stakes and Low Taxes: Understanding Canadian Casino Payouts

High Stakes and Low Taxes: Understanding Canadian Casino Payouts

The Realities of the Payout Percentage

When Canadian players sit down at a digital felt or spin the reels of a modern slot, the conversation inevitably turns to Return to Player (RTP) rates. This percentage represents the theoretical amount a game returns to players over a vast number of spins. For instance, a slot with a 96.5% RTP will, in theory, pay back $96.50 for every $100 wagered. However, this is a marathon metric, not a sprint. Short-term variance means your actual results can swing wildly from this baseline, creating the thrilling highs and frustrating lows that define the gambling experience. Read more about this at casinos that accept muchbetter.

Land-based casinos in provinces like Ontario and British Columbia often operate with different payout structures than their online counterparts. Physical venues have higher overheads, staff, maintenance, and property costs, which historically led to lower RTPs on slot machines, sometimes dipping to 90% or less. The digital revolution has changed this dynamic entirely. Online platforms, free from the massive physical footprint, can offer significantly more generous payouts. Players are increasingly savvy, comparing these figures before committing their bankroll, knowing that a few percentage points difference on a game like blackjack or video poker can be the deciding factor between a profitable session and a losing one.

It is vital to distinguish between RTP and the house edge. While RTP is the player’s perspective, the house edge is the casino’s built-in advantage. For European roulette, that edge stands at 2.7%. For baccarat, betting on the banker carries a razor-thin 1.06% house advantage. Understanding these numbers is the bedrock of strategic play, allowing you to select games that statistically give you the best chance to walk away a winner.

The Tax Advantage for Canadian Players

Perhaps the most compelling argument for playing from Canada is the country’s unique tax structure. Unlike our neighbors to the south, where the IRS considers gambling winnings as taxable income down to the last dollar, Canada offers a starkly different scenario. According to the Canada Revenue Agency (CRA), winnings from gambling activities, whether from lotteries, slots, or table games, are not considered taxable income for the casual player. This is predicated on the activity being a game of chance with no skill involved and not a consistent source of livelihood.

This creates a monumental advantage. If you hit a $100,000 jackpot on a progressive slot, that entire amount is yours. There is no withholding, no bracket adjustment, and no need to set aside a portion for a tax bill in April. The only caveat is for professional gamblers who treat gaming as a full-time business; in that specific case, winnings become business income. For the vast majority of recreational players, this “low-tax” environment makes high-stakes play significantly more attractive than in jurisdictions with punitive gambling levies.

This favorable regime is further amplified by the premium platforms available to Canadian residents. For instance, many top-tier online casinos now offer optimized payout speeds and zero-fee banking to enhance the experience. One standout example is Jackpot City Casino, a platform that not only respects this tax-free reality but elevates it with transparent terms and rapid withdrawal processing. When you combine the Canadian tax advantage with a site that offers a stellar 96%+ average payout rate across its portfolio, the value proposition becomes undeniable. You are playing with a clear mathematical edge over international players who must sacrifice a portion of their winnings to the state, all while enjoying a superior, seamless gaming interface.

Ultimately, the key to maximizing your returns in Canada lies in leveraging this tax-free status. Always verify the payout percentages of the games you play and choose licensed, reputable operators that align with your financial interests. The combination of favorable tax law, advanced gaming software, and high RTP percentages creates an environment where your skill and luck are the only true limits to your winnings.

Copyrights


Copyright and license

Copyright © 2017 Protech Associates, Inc. All rights reserved.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Protech Associates, Inc. No part of this document may be modified or customized in any way without the express written permission of Protech Associates, Inc.

Notwithstanding the foregoing, the licensee of the software with which this document was provided may make a reasonable number of copies of this document solely for internal use.

Limitation of liability

The content of this document is furnished for informational use only, is subject to change without notice, and should not be construed as a commitment by Protech Associates, Inc. Protech Associates, Inc., assumes no responsibility or liability for any errors or inaccuracies that may appear in this manual. Neither Protech Associates, Inc. nor anyone else who has been involved in the creation, production, or delivery of this documentation shall be liable for any damages, including but not limited to any loss of anticipated profit or benefits, resulting from the use of this documentation.

License agreement

Use of this product is covered by a license agreement provided with the software product. If you have any questions, please call Protech Associates, Inc. at (800) 310-8813.

Trademarks

Microsoft, Microsoft Dynamics, SharePoint, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned in this documentation may be trademarks or registered marks – in the United States or other countries – of their respective owners.

Version History:

Original Publication Date: March 14, 2017

Revised October 20, 2017 (UX v8.1.3)

Introduction

Introduction

Welcome to Protech UX Online 8, a complete, enterprise-wide solution that helps organizations manage nearly every aspect of their business, including dues, committees, meetings, product sales, member self-service, financials, and more.

This introduction includes the following information:

What’s in this documentation

This user’s guide is intended for users who will be helping set up and administer UX Online 8, as well as for users who will be performing day-to-day procedures in the application.

This documentation includes the following parts:

  • Part 1: System Setup includes information about basic setup procedures that must be completed before you can use UX Online, and includes data maintenance procedures.

  • Part 2: Basic Procedures describes the UX Online interface and some basic procedures that apply throughout the product.

  • Part 3: Accounting Transaction Processing describes how UX Online integrates with your back office accounting system, as well as the different types of transactions you can process.

  • Part 4: Membership includes the procedures you will use to manage your organization’s membership.

  • Part 5: Chapters shows how you can use UX Online to manage your chapters and chapter members.

  • Part 6: Subscriptions includes information you will use to manage your organization’s subscriptions.

  • Part 7: Product Sales describes how you can use UX Online to manage the products that your organization sells.

  • Part 8: Committees and Rosters shows how you can use UX Online to manage your organization’s committees and rosters.

  • Part 9: Events describes the procedures you will use to manage the details for your organization’s events, such as registrations, sessions, meeting locations, speakers, exhibits, and promotion packages.

  • Part 10: Fundraising includes information about how your organization can utilize the UX Online Fundraising module to record and track all fundraising efforts.

  • Part 11: Professional Development describes how to use UX Online for your organization’s professional development activities.

  • Part 12: Advertising tells how you can use UX Online to manage the advertising publications, ad types, rates, and insertion billing.

  • Part 13: GoTransactions describes quick transaction entry options for contributions, meetings, membership, product sales, and subscriptions.

Documentation conventions

The term “UX Online” within this documentation refers to the UX module work areas in the CRM 2016 Navigation Tile Bar, including:

  • Financial Manager

  • Membership

  • Events

  • Product Sales

  • Education

  • Fundraising

  • Advertising

  • Administration

For clients working in UX Online with Web Portal for Members, the term “MX Online” is interchangeable with Web Portal for Members.

Technical support

If you need technical support for UX Online, you can contact the Protech through the Customer Care Portal.

Documentation feedback

If you have any comments, suggestions, or questions about this documentation, you can contact us by sending an email with your feedback to ptdoc@protechassociates.com.

When you send feedback, please include your contact information (name, organization, telephone number, and e-mail address) so we can follow up with you if necessary. You must include the name of the section, topic, or procedure.

System Setup

Part 1: System Setup

Before you can begin using UX Online, you must complete some foundational setup procedures.

Important

Your Protech representative may already have completed these system setup procedures for you. Do not change any of the settings described in these chapters without contacting Protech.

This information is divided into the following chapters:

  • Chapter 1: Organization Setup

  • Chapter 2: Accounting Setup

  • Chapter 3: Payment and Adjustment Product Setup

  • Chapter 4: Multicurrency Setup

  • Chapter 5: UX Online Security

Chapter 1: Organization Setup

This chapter describes the records that control how your UX Online system works. Most of these settings and products will be set up for your system during implementation, and should not be changed without consulting your system administrator or your Protech representative.

As your organization’s needs change, you may need to create additional records. For example, you may need to add or modify some of your officer title records.

This information includes the following topics:

  • UX Online Application Parameters

  • Account prefixes

  • Setting up t itles

  • Promotions

  • Credit Cards

  • Lockbox

  • Tax Rates

  • State Codes

  • Source Codes

  • Country Codes

  • Price Lists

UX Settings

There are several settings in the Administration > UX Settings menu that must be configured before you can use your UX Online system. Most of these settings will have been set up for you during the implementation process; however, you may need to modify some of these settings as your needs change. These settings are described in this part of the documentation. For additional information, see Accounting Setup .

UX Online Application Parameters

Application parameters are a set of records that control how various aspects of your UX Online system work. Typically, your system’s application parameters will be set up for you during your implementation.

The following table explains the fields in the General section of each App Config record. To view this information, in the Navigation Tile Bar, select the Administration work area. Select UX Settings > UX Online Application Parameters to open the Active App Config View. This List View will open in a new window. Locate and open the record you want to view. When you are finished, because this view opened in a new window, close the View window by clicking the “ X ” in the upper right hand corer of the window.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

Field

Description

Config Name or Key

Identifies the system parameter.

Config Value

Displays the setting for the system parameter.

Description

Provides a brief description of this system parameter and what effects the available settings have.

Owner

Displays the user ID of the user who set up this record.

Your system will be deployed with the correct application parameter configuration records for your organization based on the requirements and values determined during implementation.

Important

Do not add or remove any configuration records.There are additional parameters deployed with your system that are not on this list. They are used to support system logic and should not be changed by users.

Accounting integration application parameters

Parameter Name

Values

PABankRecModule

Value = TRUE if your organization is integrated with Microsoft Dynamics GP Bank Rec Module.

Works with Bank Rec settings in the company record setup.

CRM4M.Accounting.Solomon2011 For post to Dynamics SL 2011 or Dynamics SL 2015, set value to true; else, false
CRM4M.Accounting.Solomon2015 For post to Dynamics SL 2015, set value to true; else, false

Address verification application parameters

Parameter Name

Values

PAMelissaAddressValidation.UseCanada CountryName

Address Validation will update Canada Country name as CANADA when this value is set to true.

Backorder processing application parameters

Parameter Name

Values

PABackOrders.ApplyFreight

Set value to true, if you want to apply freight charges to the Fulfillment Invoice created during the Back Order Processing, else false.

PABackOrders.ApplyPayments

Set value to true, if you want to apply payments charges to the Fulfillment Invoice created during the Back Order Processing, else false.

Batch close application parameters

Parameter Name

Values

PANightlyProcess.CloseNonWebBatches

To automatically close non-web batches nightly, set the parameter Value = true; else, false

PANightlyProcess.CloseWebBatches

To automatically close web batches nightly, set the parameter Value = true; else, false

Batch control amount application parameters

Parameter Name

Values

PABatch.ValidatePaymentControl

Set to true if you want the Batch Control total to be checked against total payments in batch and prevent closing batch.

PABatchWeb.ValidatePaymentControl

Set to true if you want the Web Batch Control total to be checked against total payments in batch and prevent closing batch.

PANightlyProcess.WebBatches.Validate ControlAmt

Always set to False. When PANightlyProcess.CloseWebBatches = true and PABatchWeb.ValidatePaymentControl = true, set value to ‘false’ to ignore payment control on web batches.

Certification renewal billing application parameters

Parameter Name

Values

PACertification.IsCycleDateasActivityDate

This will allow overwrite Cycle date to Last Activity Date of the Eligibility. Set value true, if the value needs to be Activity date.

PACertification.IsJoinDateasActivityDate

This will allow overwrite Join date to Last Activity Date of the Eligibility. Set value true, if the value needs to be Activity date.

PACertificationRenewal.DoNotRangeOnCEUs Set value = true to ignore requirements for CEUs fulfilled during renewal processing for Fee and CEUs certification awards that create a renewal invoice.

Delayed capture application parameters

Parameter Name

Values

PANightlyProcess.RunDelayCapture

To automatically run the Delayed Capture process nightly, set the parameter Value = true; else, false.

Process will only run on closed batches.

PANightlyProcess.ScheduleCapture

Not included in base. Do not add without client customization to run Delayed Capture nightly on a custom schedule.

Gift certificate application parameters

Parameter Name

Values

PAGiftCertificate.AllowOverBalance

Set value to true to allow Gift Certificate amount over invoice balance due.

PAGiftCertificate.FilterbyIssuedTo

Set value to ‘ true’ to filter Gift Certificate ID lookup by Certificate Issued To Contact; value is case sensitive

PAGiftCertificate.Number

Indicates if the Certificate Number is entered manually (MANUAL) or calculated automatically (AUTO). Choices: MANUAL, AUTO

Invoice custom HTML email invoice description SP parameter

Parameter Name

Values

PAInvoice.CustomEmailStoreProc

Set value = false or NULL. Only used by development for custom Stored Procedure for custom HTML Email Invoice Description.

Invoice default addresses application parameters

Parameter Name

Values

PAInvoice.BillToAddressType.Default

Set value = Bill To to use More Addresses address with address type = BillTo as invoice default BillTo address. Applies only to address number 3 or above.

PAInvoice.ShipToAddressType.Default

Set value = Ship To to use More Addresses address with address type = ShipTo as invoice default ShipTo address. Applies only to address number 3 or above.

Invoice message application parameters

Parameter Name

Values

PAInvoiceMsgs.CustomerCreditHold.Show

True – Enter this value to display a warning message when a user opens an invoice for an account or contact that has a credit hold.

False – Enter this value if you do not want to display a warning message.

Invoice write-off limit application parameters

Parameter Name

Values

PAInvoice.Writeofflimit

Invoice Write-off limit. For example, to set the limit to $100.00, enter 100.

Lockbox contribution application parameter

Parameter Name

Values

PALockboxContributionAsProduct Sales

If value = true, lockbox extra contributions will be created as a product sales transaction.

If value = false, lockbox extra contributions will be created as a monetary contribution transaction.

Default = false

Meeting registration application parameters

Parameter Name

Values

PAMeetings.ParticipantName

Required. Possible values: ‘LN, FN MN’ or ‘FN MN LN’ – enter value exactly as shown; manages formatting of the participant name for back office and web transactions.

PAEvent.TransferParticipants.Showbutton

If value = true, the Transfer Participant button is displayed on the View Event Participants toolbar.

Meeting setup application parameters

Parameter Name

Values

PARestrictConflictingSession.Enable

If value = True or is NULL, restrict setup of registration packages with conflicting sessions. If = False, do not restrict setup. Default is true. This is intended to prevent the inadvertent setup of conflicting sessions within a registration package. Do not recommend changing to False.

Membership-related application parameters

Parameter Name

Values

PAMembership.NewMemberCycleState

If value = Current, then new member cycle state ignores benefit setup and sets the cycle state = Current. If value is NULL, then new member cycle state is based on the cycle start date.

PAUpgradeDowngrade.ShowButton

If value = true, then Upgrade/Downgrade Membership button is visible in the membership invoice detail benefit entry form.

Multi-company application parameter

Parameter Name

Values

PAMultiCompany.Enable

Set value to false or leave NULL.

Used only to support single company/single currency client environments with multiple transfer payment products, where the client wants to define the default transfer payment product in the parameter PAPaymentTransfer.ProductNumber.

This PAMultiCompany.Enable parameter is not used for any other system logic.

Multi-currency application parameters

Parameter Name

Values

PAMultiCurrency.Enable

Set value to true when using Multi-currency. Else NULL or false.

MX Online application parameters

Parameter Name Values
MX.CancelShoppingCartXNbrDays Enter the integer value that represents the number of days before the system cancels unfinished Shopping Cart, Meeting Registration, and Membership Application records.
PAShoppingCart.CheckDuplicateProducts Set to true to prevent duplicate Product Sales Items from being added to the MX Shopping Cart for MX 5.6.1. False allows duplicate products. Default is true. Null = true
PAShoppingCart.UseBillToParent Set to true to allow option of Bill To Parent in the MX Shopping Cart for MX 5.6.1. False always assigns the signed in user as Bill To. Default is true. Null = true.
PAWebRole.SeparateChapters Option to create a web role for each chapter if true, or use the same Chapter Member web role for all chapters if false.
PAWebRole.SeparateCommittees Option to create a web role for each committee if true, or use the same Committee Member web role for all committees if false.

Payment-related application parameters

Parameter Name

Values

PAPayment.ShowAdjustment Transaction

Set value to true to display “Adjustments” in the invoice Payments & Adjustments menu to create payment transactions where the payment product setup “Is Adjustment” = true.

PAPaymentTransfer.ProductNumber

For clients working in a single company/single currency environment that have multiple transfer payment products, enter the default Payment Transfer Product Number to be used when transferring the payment from one invoice to another invoice during Renewal Billing Overpayment Processing, Advertisement Insertion Billing, and Invoice Transfer Payment.

UX uses the default only when PAMultiCurrency.Enable = false (or NULL) AND PAMultiCompany.Enable = false (or NULL).

A Config value IS REQUIRED if PAMultiCurrency.Enable = false (or NULL) AND PAMultiCompany.Enable = false (or NULL).

PACreditCard.AllowVoidOnDistributedLines

Parameter to allow Void Credit Card Payment on distributed credit card payment (i.e., RapidPay credit card payment distributed to multiple invoices).

If config value = true, when you select Void Payment in one of the distributed credit card payment transactions, UX will void all distributed credit card payment transactions that share the same authorization.

If config = false, you cannot void a distributed credit card payment transaction.

Default = false

Product Sales application parameters

Parameter Name

Values

PAOrders.DisableCancelOnFulfilled

When set to true, this key disables delete/cancel on sales inventory or sales non-inventory invoice detail items where Date Printed or Packing Ticket Printed is not NULL

PAOrders.RestockingPercent

Restocking Fee Percentage in lieu of flat restocking fee amount.

Promotion Packages application parameter

Parameter Name

Values

PAPlaceholder Contact

Supports creating promotion package detail where the contact is not known at the time of the promotion package transaction,

RapidPay application parameters

Parameter Name

Values

PARapidPay.AutoApplySort

Values can be either oldest or newest. Select oldest for Auto Apply payment from oldest to newest. Values are case sensitive. Default = newest

PACreditCard.AllowVoidOnDistributedLines

New parameter to allow Void Credit Card Payment on distributed credit card payment (i.e., RapidPay credit card payment distributed to multiple invoices).

If config value = true, when you select Void Payment in one of the distributed credit card payment transactions, UX will void all distributed credit card payment transactions that share the same authorization.

If config = false, you cannot void a distributed credit card payment transaction.

Default = false

Renewal application parameters

Parameter Name

Values

PARenewal.AdditionalBenefitRecipientby CycleDate

Set value to true if the Non-Sales Inventory product invoice detail gets price based on renewal Cycle Start Date in lieu of system date.

PARenewal.AdditionalBenefitRecipientsCreate

Default = false. Set value to true to create add’l benefit recipient records during renewal based on # allowed in Rate Next.

Report application parameters

Parameter Name

Values

PAReportsColorURL

URL Displays color for all report headers

PAReportsLogoURL

Displays a logo for all report headers

Shipping (standard freight) application parameters

Parameter Name

Values

PAShipping.ActiveCarrier

Leave this field blank. It is not applicable to standard freight.

PAShipping.FreightIntegrationType

Leave this field blank. It is not applicable to standard freight.

PAShipping.Standard.CalculationType

If shipmentweight, Standard Shipping charges are calculated using Total Weight of products where Apply Freight = True.

If shipmentvalue, Standard Shipping charges are calculated using Total Value of products where Apply Freight = True.

PAShipping.WeightUnits

Determines the units of measure for shipment weight. Enter LBS for US pounds or KGS for kilograms. Default = LBS.

PAShipping.MarkupPercent

To add a percentage markup to standard freight charges, enter the percentage here, e.g. 5.0 = 5 percent. Else, 0 (value required).

PAShipping.WebExcludeStandardShipping

To exclude display of Standard shipping options on the web, Config value = true.

To include display of standard freight options on the web, Config value = false or NULL.

ShippingHandlingExtraFee

To add a flat amount to all standard freight charges, enter the value. For example, to add $5.00, enter 5.0. Else, enter 0 (value required).

PABackOrders.ApplyFreight

Set value to true, if you want to apply freight charges to the Fulfillment Invoice created during the Back Order Processing; else false.

Subscription-related application parameter

Parameter Name

Values

PASubscription.NewSubscribtionCycleState

If value = Current, then new subscriber cycle state ignores benefit setup and sets the cycle state = Current. If value is NULL, then new subscriber cycle state is based on the cycle start date.

Tax (multi-jurisdictional) application parameter

Parameter Name

Values

PATax.EnableCountyTax

If Config value = true, tax based on tax rate setup for ShipTo county and/or city; if = false or NULL, ShipTo county and/or city is ignored

Account prefixes

When you use a Lookup window to find an account record in UX Online, the records in the window are sorted alphabetically by the data in the Account Name Sort field on the account record. When you create a new account record, this field is automatically populated by the system, based on the account name. (You can view this field by opening an account record and viewing Preferences on the account form.)

If several of your accounts begin with the same word or prefix, this can make it difficult to find the correct account record in a Lookup window. For example, if you have several accounts that begin with the same word or phrase, such as “The University of,” the default value for the Account Name Sort field will begin with “The University of.”

If you establish these common words as account prefixes in UX Online, the system will remove them from the value it places in the Account Name Sort field when you create a new account record. For example, assume that you have set up “The University of” as an account prefix. When you create a new account record for The University of Venice, the value in the Account Name Sort field will be “Venice,” and the record will appear in the Account Lookup window with other records beginning with V, and you will be able to search for the account using the word “Venice,” rather than the full account name.

To use account prefixes, you will need to create account prefixes. For more information, see Creating account prefixes

After you have completed this procedure, the account prefixes you create will be used to filter the values automatically created for the Account Name Sort field for all new account records.

Note

Adding account prefixes will not affect the Account Name Sort field for existing account records. Only new records created after you set up prefixes will be affected.

Creating account prefixes

If you establish common words as account prefixes in UX Online, the system will remove them from the value it places in the Account Name Sort field when you create a new account record. You can define as many account prefixes as needed to meet the needs of your organization.

Note

Adding account prefixes will not affect the Account Name Sort field for existing account records. Only new records created after you set up prefixes will be affected.

In the Navigation Tile Bar, select the Administration work area. Select UX Settings > Account Prefixes to open the Active Account Prefixes List View. This will open in a new window.

In the Account Prefixes list, click New on the List View toolbar to create a new account prefix.

In the Account Prefix field, enter the words that you want to filter out when the system creates the Account Name Sort value for a new record. For example, you could enter “The University of.”

Click Save & Close to save the account prefix and return to the Account Prefix list.

Because this view opens in a new window, close the Active Account Prefixes View window by clicking the “ X ” in the upper right hand corner of the window.

Important

If you create multiple account prefixes that contain the same word, be sure to test them to verify that they work the way you expect. For example, if you create a prefix for “The” and a prefix for “The University of,” the system will filter the prefix for “The” but not the prefix for “The University of.” However, if you have a prefix for “The University of” and “The College of,” the system will use both.

Setting up titles

If your organization uses specific titles for committee members, chapter officers, or region officers, such as President, Chairperson, or Secretary, you can add them to the Titles table.

To access this information, in the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Titles to open the List view of Active Titles. This list opens in a new window.

In the Titles list, click New on the List View toolbar to create a new title.

Enter the title name (for example, President or Chairperson).

If you want to create a custom report that sorts committee members in order according to their title sequence, enter a title sequence number for this title. For example, if you want the committee president to be listed first, regardless of his/her last name, enter 1 as the sequence when creating the title record for president.

Note

The base UX Committee Roster report sorts committee members alphabetically.

Click Save & Close to save this record and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Lockbox records

If your organization imports payments made to a bank, you will need to create lockbox setup records for each bank lockbox file type to identify the file components and formats. See Lockbox Management for information on lockbox import processing.

As described below, lockbox records have four basic components:

  • General information – the section of the lockbox record that defines the basic setup for the lockbox import file including information provided by your bank.

  • Field definitions – the section of the lockbox record that defines the fields and field positions for information provided by your bank in the bank lockbox file.

  • Lockbox receipt types – a related entity to the lockbox record located in the left navigation of the lockbox file that defines payment/receipt types if provided by your bank in the bank lockbox file.

  • Lockbox extras – a related entity to the lockbox record located in the left navigation of the lockbox file that defines configuration for importing contribution payments where no invoice detail for the specified contribution exists in the UX Online invoice.

Lockbox setup

The following information in the General and Field Definitions sections of each Lockbox setup record will be configured for you during your UX Online implementation. Setup information is provided for your reference should you need to create a new lockbox setup record.

To access this information, in the Navigation Tile Bar, select the Administration work area. Select UX Settings > Lockbox Setup to open the Active Lockbox Setups View. This will open in a new window.

Select to open the record you want to view, or select New on the List View toolbar to create a new lockbox setup record.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

In the General section of the lockbox setup record, complete the following fields based on information from your bank for lockbox file setup:

Field

Description

Name

Text field to identify the name of the lockbox. There can be various types of lockbox configurations, depending on how and where the bank sends the file. For example, names like “Membership Lockbox” or “Event Lockbox” have been used by customers.

Date Format

This option set provides a list of various formats for how a date is imported. Default values include MM/DD/YYYY, MM/DD/YY, MMDDYYYY, MMDDYY, YYYYMMDD, and YYMMDD. Do not delete or edit these values. You may add additional values through Customization in your client-specific solution package.

Virtual Decimal Point

This is a Y/N bit field. For example, if the field is checked (=Yes), the bank sends a value of $10.00 as 1000; if the field is not checked (=No), the bank sends a value of $10.00 as 10. Review the bank file for this value format.

Deposit Date Location

This option sets the location of the Deposit Date sent from the bank. The bank either sends this field in a Detail line or in a Header line. Review the bank file for this value format. Do not delete or edit these values. You may add additional values through Customization in your client-specific solution package.

Customer Number Type

This option sets the record type to correspond to the Customer ID. In UX Online, the values for Account ID and Contact ID are not duplicated. If the bank does not provide the invoice number (it is recommended for the bank to provide the invoice number), then this value provides a reference for what record to use. If the bank file is for both accounts and contacts, then the file will direct the path to the proper record. Do not delete or edit these values. You may add additional values through Customization in your client-specific solution package.

Default Account

When the account ID cannot be validated, the system returns a warning error. If the warning is ignored, the system will create a payment to the default account as an invoice transaction with only that payment in it.

Default Contact

When the contact ID cannot be validated, the system returns a warning error. If the warning is ignored, the system will create a payment to the default contact as an invoice transaction with only that payment in it.

Lockbox Number

This text field allows for an identification code for isolating the lockbox file in lieu of the Name field for programming development.

In the Field Definitions section, complete the following fields based on information from your bank for lockbox file setup:

Field

Description

Header/Detail Flag

Identifies the field position and bank values in the bank lockbox file that indicates the header line and the detail lines.

Batch Group

Identifies the field position in the bank lockbox file for the bank value that indicates how transactions are grouped (a field the bank typically calls the batch number). If there is no indicator in the bank lockbox file, this setting can be blank.

Sequence Code

Identifies the field position in the bank lockbox file for the bank sequence number that indicates the order of how transactions come into the bank lockbox file.

Deposit Date

Identifies the field position in the bank lockbox file for the Deposit Date. This field looks at the Deposit Date Location and Date Format values entered in General section of the lockbox setup when importing the bank lockbox file.

Customer Number

Identifies the field position in the bank lockbox file that that contains the Customer Number. This is the account or contact ID (or Member Number), depending on the Customer Number Type value in the General section of the lockbox setup. This value is not required when the bank lockbox file contains an Invoice Number. If this value is blank and there is no Invoice Number in the bank lockbox file, the payment will go to the default Account or Contact identified in the General section of the Lockbox setup when importing the bank lockbox file.

Invoice Number

Identifies the field position in the bank lockbox file that contains the Invoice Number. The invoice number is typically provided by the customer to the bank when payment is made. For accuracy and ease of use, Protech recommends that the bank include the invoice number in the lockbox file.

Payment/Receipt Type

If the bank is tracking the type of payment receipt made by the customer, this field identifies the field position in the bank lockbox file for the payment type (check, credit card, other). If used, the payment receipt types used by the bank must be identified in the Lockbox Receipt Types in the left navigation of the lockbox setup.

Payment/Receipt Amount

Identifies the position of the payment amount in the bank lockbox file. The length of this field must accommodate the total value of the payment include decimal and cents (not commas). For example, if you accommodate a payment up to $999,999.99, then set the length to 9. This field looks at the Virtual Decimal setting in the General section of the lockbox setup.

Reference

Identifies the field position in the bank lockbox file that contains the check or credit card number. The length of this field must accommodate the possibility of the maximum value allowed of 19. Important Note: Review the number the bank will use for credit cards in the bank lockbox file. This may be a security issue and you may decide to limit the number to the last four or five digits for credit card payments.

Custom Fields

Leave this field blank. It is for future development.

Note

Although the lockbox import process can use either the Customer Number or Invoice Number (based on what fields are selected in the lockbox setup), Protech recommends that the client use the Invoice Number. Using the Invoice Number guarantees that the correct invoice is selected. If using the Customer Number, the import process looks for the first invoice for the customer (Bill To ID) that has an open balance and brings that invoice number into the import file.

Click Save & Close on the record toolbar. Because this List View opened in a new window, close the View window by clicking the “ X ” in the upper right hand corner of the window.

About Lockbox Receipt Types

Lockbox receipt types are used in conjunction with the Payment/Receipt Type field in the bank lockbox file when the bank specifies the payment type in the bank lockbox file. Configuring lockbox receipt types requires lockbox-specific payment products to associate with each lockbox receipt type for ease of tracking the source of the original payment transaction and to differentiate imported lockbox payment transactions from payments entered in the back office or through a web transaction.

For example, if the bank tracks payment/receipt types in the bank lockbox file for check and credit card payments, you will need to configure two lockbox-specific payment products: one for lockbox checks and one for lockbox credit cards. Depending on the bank’s tracking for credit card receipts, you may want to create a lockbox payment product for each credit card type, although this can be onerous and cost-prohibitive.

Once lockbox-specific product setup is complete, you will need to create a lockbox receipt type record for each related the lockbox payment product.

Creating Lockbox-Specific Payment Products

Except as noted below for lockbox-specific credit card payment products, when creating lockbox-specific payment products, follow the same basic instructions for creating a payment product (see Payment and Adjustment Product Setup). For your setup, use LB as the prefix in the product setup ID field and a lockbox specific name in the product setup Name field to differentiate these payment products as lockbox-specific.

Note

Continue to use CK payment products for checks that are manually entered into UX Online. Continue to use AX, MC and VS payment products for credit card payments that are manually entered into UX Online or processed through the a web transaction.

When creating a lockbox payment product for check lockbox receipt, enter “LBCK” as the ID and “Check Payments Received through Lockbox” as the Name or a similar differentiation for these fields. All other settings are the same as when setting up a check payment product for back office receipts.

When creating a lockbox-specific payment product for a credit card lockbox receipt, enter “LBCC” as the ID and “Credit Card Payments Received through Lockbox” as the Name or a similar differentiation for these fields. Do not treat this product as a credit card payment product in the Payment Product Info section of the product setup.

Important

Pay special attention to the Payment Product Info section when creating a lockbox-specific credit card payment product. The lockbox-specific credit card payment product is NOT tracked as a credit card. All settings in the Payment Product Info section are the same as when setting up a check payment product.

See Payment and Adjustment Product Setup for additional information on payment product setup.

Creating Lockbox Receipt Types

While working in your lockbox setup record, click the down caret (‘ ’) next to the lockbox setup record in the Top Navigation Toolbar to open the hidden Navigation Pane of related records.

Select Lockbox Receipt Types to view and create lockbox receipt type records. To create a new lockbox receipt type record, click Add New Lockbox Receipt Type on the toolbar.

In the General section of the Lockbox Receipt Type record, enter the following information:

  • Name – Enter a name in the text field that describes the receipt type (for example, Lockbox Check).

  • Receipt Type Code – Enter the code provided by the bank to identify this type of receipt. This is used in conjunction with the field definition for Payment/Receipt Type in the lockbox record setup.

  • CRM Product – Lookup to select the lockbox-specific payment product for this receipt type. You must select the appropriate payment product created for this lockbox receipt type.

Click Save & Close to save and close this record. Repeat this process to create another.

When you are finished, Save & Close the Lockbox setup record.

About Lockbox Extras

Lockbox extras allow specific amounts for monetary contributions and sales non-inventory products to be imported from your bank lockbox file where no existing invoice detail exists in the UX Online invoice. When configured in your lockbox setup and included in the bank lockbox file import, Lockbox Extras create the invoice detail for sales non-inventory products and monetary contributions.

Important Note

Requires configuration of a monetary contribution product in the Fundraising Manager or a sales non-inventory product in the Product Sales Manager where the product code matches the Extra Product Code used by your bank to identify the Lockbox Extra. Creating Lockbox Extras

Configuring your system for lockbox extras

You can manage the invoice transaction type created by lockbox extras by setting the Config value for the application parameter, PALockBox.ContributionAsProductSales. This parameter controls whether all invoice detail for all lockbox extras will be created as product sales transactions without regard to the lockbox extra setup as a product sales item or monetary contribution or whether invoice detail for lockbox extras will be based on the lockbox extra setup as a product sales item or monetary contribution.

Important Note

UX Online 2011 and earlier versions created all lockbox extra invoice transactions as product sales transactions, even when the lockbox extra was set up with a monetary contribution. If your organization wants to continue this approach, set the Config Value for this parameter = true.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This List View opens in a new window. Locate and open the parameter PALockBox.ContributionAsProductSales.

The default value for this parameter = false. Set the Config Value field to the method that your organization uses for lockbox extras:

  • true – Invoice detail for lockbox extras that are set up with a monetary contribution or with a product sales non-inventory item will be created as a product sales transactions.

  • false – Invoice detail for lockbox extras that are set up with a monetary contribution will be created as monetary contributions and invoice detail for lockbox extras set up as a product sales non-inventory items will be created as a product sales transactions.

Click Save & Close to save your changes and close the record. Because the list opened in a new window, click the “ X ” in the upper right hand corner of the window to close it.

Creating a lockbox extra

While working in your lockbox setup record, click the down caret (‘ ’) next to the lockbox setup record in the Top Navigation Toolbar to open the hidden Navigation Pane of related records.

Select Lockbox Extras to view and create lockbox extra records. To create a new lockbox extra record, click Add New Lockbox Extra on the toolbar.

In the General section of the Lockbox Extra record, enter the following information:

  • Name – Enter a name in the text field (for example, Contribution with Dues).

  • Number – The system allows up to 7 Lockbox Extra records. Each record is configured with its own number for sequencing and specific field definitions identified below.

  • Extra Amount Start Position and Length – Field definitions for this lockbox extra record that defines the starting position and field length in the bank lockbox file for the dollar amount of the extra payment. Each extra amount value is limited to 12 characters. So, if you are using a decimal and cents, the highest value of an extra is $999,999,999.99 (excluding commas)

  • Extra Product Code Start and Length – Field definitions for this lockbox extra record that defines the starting position and field length in the bank lockbox file for the monetary contribution product code from the products table. Each Extra Product Code length is limited to 12 characters, so work with your bank to determine what code it will use in the bank lockbox file to identify the Lockbox Extra, up to a limit of 12 characters.

Click Save to save the Lockbox Extra record. You must now create a related Lockbox Extra Product.

While working in your Lockbox Extra record, click the down caret (‘ ’) next to the lockbox record in the Top Navigation Toolbar to open the Navigation Pane of related records. Click Lockbox Extra Products in the Navigation Pane.

Click Add New Lockbox Extra Product on the toolbar to create a new Lockbox Extra Product.

In the General section, enter the following information:

  • Name – Enter a name in the text field for this lockbox extra product (for example, Contribution with Dues).

  • Extra Product Code – This is the code that your bank uses in the bank import file to identify this type of receipt. It is used in conjunction with the Lockbox Extra record field definitions for Extra Product Code Start and Length (limited to 12 characters).

  • Extra Product – Links the Lockbox Extra to a monetary contribution or sales non-inventory product in the Product Table. Use the Lookup to select the product to be used for this Lockbox Extra record.

Click Save & Close to save and close this record and return to the Lockbox Extra record. Click Save & Close to close the Lockbox Extra record and return to the Lockbox Setup record.

When you are finished, Save & Close the Lockbox setup record.

Promotion records

Promotion records are used to manage discounts your organization offers for UX Online transactions. These promotions can be based on date range or other parameters specific to the transaction type. Promotions can be set as a flat currency amount or a percentage discount, and they can be applied to any UX Online transaction type.

When you select a promotion on a new invoice, the system will automatically apply the specified discount to the invoice transaction detail if it meets the criteria entered on the promotion record. The promotion amount will populate the Discount field on the invoice detail line item for all transaction types, with the exception of the invoice detail line for renewal billing.

Promotion records are not price list specific.

Creating a promotion record

In the Navigation Tile Bar , select the Administration work area > UX Settings > Promotions to open the Active Promotions View. This will open in a new window. In the Promotions list, click New on the View toolbar to create a new promotion record.

On the top half of the General section of the Promotion record, enter the following general information about the promotion:

  • Name – Enter a descriptive name for the promotion, such as “2016 Spring Membership Incentive.”

  • Promotion Code – Enter a code or abbreviated name for this promotion. For example, the promotion code for the 2016 Spring Membership Incentive could be SPMBR16.

Important

Carefully consider the naming conventions that you use for the Promotion Name and the Promotion Code , because the lists and lookup dialogs throughout UX Online display records sorted alphanumerically.

  • Start Date – Click the Calendar button to select a start date for the promotion.

  • End Date – Click the Calendar button to select an end date for the promotion.

Important Note

Consider your start and end date ranges carefully. The system will not calculate a discount if the transaction date is not between the start and end dates for the promotion.

Promotions for renewal billing modules (Membership, Subscriptions, and Education) are calculated on the cycle start date in the renewal billing record – not the join date. For example, if your new member joins on 8/1/2016 but the cycle start date is 7/1/2016, your New Member promotion record must begin on or before 7/1/2016 to apply the discount.

  • Discount Type – Select whether the discount will be a flat amount, or a percentage.

  • Amount – Enter the amount of the discount. This will be the amount deducted from the transaction price, as either a flat amount or a percentage discount amount.

Note

The amount of the promotion will populate the Discount field on the invoice detail line item for all types of transactions except renewal billing invoices. Promotion amounts are not displayed on the invoice detail line item for renewal billing.

  • Campaign – If this promotion is associated with an existing campaign, click the Lookup button to select the campaign.

  • Owner – Displays the user ID of the user who created this record.

In the Apply Promotion area of General section, select the UX Online module transaction types where this promotion can be applied. Options include:

  • All Products

  • Membership

  • Meetings

  • Subscriptions

  • Product Sales

  • Advertisements

  • Exhibits

  • Education

  • Specific Products – Select this option if you want to limit the promotion to specific sales inventory or sales non-inventory product transactions. For more information, see Linking products to specific product promotions.

Important

Promotions for renewal billing modules (Membership, Subscriptions, and Education) are calculated on the cycle start date in the renewal billing record – not the join date. For example, if your new member joins on 8/1/2016 but the cycle start date is 7/1/2016, your New Member Promotion record must begin on or before 7/1/2016 to apply the discount.

Click Save & Close to save and close this promotion record.

After saving this record, the Apply Promotion options are disabled and navigation to related products is activated. Re-open the Promotion record and click the caret (‘’) next to the Promotion record to open the hidden Navigation Pane to display related records.

Click Save & Close to save this record and return to the View. Close the View window by clicking the “ X ” in the upper right hand corner of the window.

Linking products to specific product promotions

After you have created a specific product promotion, you can link specific sales inventory and sales non-inventory products to this promotion record. This is done from the product setup record.

Re-open the Promotion record and click the caret (‘’) next to the Promotion record to open the Navigation Pane of related records.

Click Product Promotions to open the Product Promotion Associated View listing of existing products that are associated with this promotion.

In the Product Promotion Associated View, click Add New Product Promotion on the List View toolbar to add a specific sales inventory or sales non-inventory product to this promotion.

In the new Product Promotion record:

  • Promotion – Displays the related promotion setup record. This field is locked and is not available for edit.
  • Product – Click the Lookup button to search and select the product to add to this product setup. The lookup is filtered to display only sales inventory and sales non-inventory products.

Click Save & Close to save the product promotion record and return to the Product Promotion Associated View. Click the promotion record in the Top Navigation Toolbar to return to the promotion setup record. Save & Close the promotion setup record to return to the Active Promotions view. Because this View opened in a new window, close the View window by clicking the “X” in the upper right hand corner of the window.

Note

Only sales inventory and sales non-inventory products can be linked to a specific product promotion through the promotion record setup.

Specific product promotions for meeting registrations and sessions, and exhibit products

UX Online extends the specific-product promotion logic to meeting registration and session products, and exhibit products. The difference between a standard specific product promotion and one created for meeting registrations and sessions, and exhibit products is that you do not link the meeting registration, session, or exhibit product to the promotion record in the promotion setup. Rather, the relationship is created in the registration, session, or exhibit. For more information, see Setting up sessions, Setting up registrations, and Setting up exhibit products.

Depending on your organization’s needs, one or more promotions can be related to one or more meeting registration, meeting session, and exhibit products. This supports:

  • The equivalent of a meeting-specific or exhibit-specific promotion – When a Specific Product Promotion is related to all registration and session setups for a meeting, or all exhibit products for an exhibit, and the promotion is added to the invoice header, any invoice transactions for that meeting (registrations, sessions, etc.) or exhibit will be eligible to receive the promotion.

  • A registration-specific promotion – When a Specific Product Promotion is related to a registration setup, only transactions for that registration will be eligible to receive the promotion. While you can related a Specific Product Promotion to registration setups where Is Cancellation Fee = Yes, UX will not calculate promotion discounts on a cancellation fee.

  • A session-specific promotion – When a Specific Promotion is related to a Session setup, only transactions for that session will be eligible to receive the promotion.

  • An exhibit product-specific promotion – When a Specific Product promotion is related to an exhibit product setup (i.e., product type = booth, misc product, exhibitor badge), only transactions for that exhibit product will be eligible to receive the promotion. While you can relate a Specific Product Promotion to an exhibit cancellation fee, UX will not calculate promotion discounts on a cancellation fee.

Using the Specific Product promotion approach for meeting and exhibit products provides increased flexibility because promotions have many-to-many relationships. Depending on your organization’s needs, for example, one or more promotion codes can be related to a specific registration and/or session product and one or more registration and/or session products can be related a specific promotion code.

Important Note

When creating specific product promotion codes for meeting registrations and sessions and exhibit products, consider your start and end date ranges carefully as they relate to your meeting registration start and end dates and your exhibit start and end dates The system will not calculate a discount if the transaction date is not between the start and end dates for the promotion.

Specific Product promotions do not work with meeting cancellation fee or exhibit cancellation fee setups.

Modifying a promotion

If necessary, you can make changes to an existing promotion, such as the name, start and end date, discount type, amount, etc. You cannot change the Apply Promotion option on an existing promotion record.

Important

If you make changes to an existing promotion, and that promotion is assigned to any renewal benefits, the changes you make will also apply to those renewal benefits. We recommend that you do not modify an existing promotion unless you want this information changed system-wide. Create a new promotion if you need to maintain existing promotion assignments in your renewal benefits.

Tax rates

Tax Rate records contain information required to calculate sales taxes your organization is responsible for collecting and remitting to various government agencies. UX Online calculates tax automatically based on data contained in the invoice Ship To address fields when the invoice detail product is flagged as taxable and the tax exempt field in the invoice header is null. The system relies on data in the tax rate records to identify the specific tax rate to be used when calculating tax and supports calculations using tax rates with up to three decimal precision.

Important Note

For taxable meeting registrations and sessions, the invoice Ship To address fields are ignored and tax is calculated based on the location record selected in the meeting setup. For more information, see Calculating tax by meeting location.

Tax Rates can be configured to support calculating tax on shipping charges (when the underlying freight product setups for standard freight service records are flagged as taxable).

Tax Rates can be configured to support tax rates at the state level, by zip code range within a state, or they can be configured to accommodate tax rates for multiple jurisdictions within a state such as city and/or county (see About multi-jurisdictional taxes below for additional information).

Setup requirements include:

  • Determining your jurisdictional tax rate structure requirements

  • Determining your accounting requirements for your tax rate structure

  • Creating requisite tax products

  • Creating tax rates

During the implementation of your UX Online system, the tax product and tax rate records you need will be set up for you based on your organizational requirements.

Creating a tax product

Each tax rate record requires a Tax Product to manage the accounting information for the calculated tax transaction. In a multicompany environment, you will need a separate tax product for each accounting company (see About multicompany taxes below for additional information). Because the tax product manages the GL account for tax revenue, if your organization directs tax revenue to different GL accounts for different states or zip code ranges, you will need a separate tax product for each.

Note

In order to create tax products in UX Online, you must first complete the accounting setup for the accounting company (or companies) and the chart of accounts.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to open the View of Active Products. This will open in a new window.

Click Add Product on the View toolbar to create a new product record. The new record will open in a new window.

In the General section, complete the new product detail entry fields:

  • Product ID – Enter a short, meaningful code that identifies the tax product and supports easy querying and lookup (for example, TAX). If you are working in a multicompany environment, you may want to append the first few characters of the accounting company name to the ID (for example, TAXFOUND).

  • Name – Enter the name of the new tax product that supports easy querying and lookup (for example, Sales Tax or Sales Tax Foundation).

  • Unit Group – Click the Lookup button , then select Each, and click OK .

  • Default Unit – Click the Lookup button , then select Each, and click OK .

  • Cur rency – By default, your preferred currency appears in this field. We recommend that you use your organization’s base currency for all products (except for payment and adjustment products).

  • Product Type – Select Tax as the product type.

  • Subject – This field is optional. If your organization relates products to subjects, click the Lookup button to select the subject.

In the Accounting section, enter the following accounting setup information for this product:

  • Company – The system will automatically populate this field with the company record flagged as the default company in your set up. If you need to make a change, click the Lookup button to select the appropriate accounting system company for this product. This controls where accounting data will post during the posting process and controls the display of GL accounts available in the GL account lookup fields.

  • Reimbursable – Select Not Reimbursable . Do not select any of the other options for tax products.

  • Primary GL Account – Click the Lookup button to select the GL account to which accounting data will post when you post UX Online transactions that include this tax. This is generally a sales tax payable account.

  • AR GL Account – Click the Lookup button to select the correct accounts receivable GL account.

  • Cash Basis – Leave the default setting of No .

  • Control Accrual Basis via AR Utility – This field is disabled and not required for this product type.

  • Secondary GL Account – This field is disabled and not required for when the Primary GL Account is a revenue account.

  • AP GL Account – This field is disabled and not required for this product type.

In the Costs section, enter the product cost setup information as shown:

  • Default Price List – Leave this field blank. When you save this tax product record for the first time, this field will automatically display the Non Member price list, and automatically creates associated price list items. You do not need to edit these price list items or create price records, because pricing for taxes are managed through the tax rate record associated with this product.

Important

Tax rates are not controlled by this field or the List Price field. They are managed by Tax Rates. For more information, see Tax rates .

  • Decimals Supported – Enter 2.

  • List Price – Leave this field blank for this product type.

  • Single Currency – Do not select. This field is not applicable.

  • Apply Freight? – This field is disabled and not required for this product type.

  • Is Bill Recipient? – This field is disabled and not required for this product type.

In the Tax Product Info section, enter the setup information as shown:

  • Taxable – This field is disabled and not required for this product type.

  • Tax Rate (Tax Product Only) – Click the Lookup button to select the tax rate associated with this tax product. For more information, see Tax rates .

The fields in the Web section do not apply to tax products.

Click Save & Close to save this record and return to the View window. Close the View window by clicking the “ X ” in the upper right hand corner of the window.

Creating a tax rate

The following information in the General section of each Tax Rate record will be set up for you during your UX Online implementation. To access this information, in the Navigation Tile Bar , select the Administration work area > UX Settings > Tax Rates to open the Active Taxes View. This will open in a new window. Locate and open the record you want to view. The record will open in a new window. When finished, Save & Close the tax rate record and return to the View window. Close the View window by clicking the “ X ” in the upper right hand corner of the window.

Important

Before creating a tax rate record, make sure that you have created a tax rate product to manage the accounting information for tax revenue. For more information, see Creating a tax product.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

Field

Description

Name

Displays the name of the tax (usually based on the state, province, county, or locality).

Tax Rate (%)

Displays the tax rate.

City

Displays the city for the tax rate when multi-jurisdictional taxes are enabled.

County

Displays the county for the tax rate when multi-jurisdictional taxes are enabled.

State Code

Displays the state abbreviation of the state for the tax rate.

Zip From

Displays the beginning of the range of ZIP or postal codes for the tax rate. This is optional and typically is used when there are different tax rates by zip code range within a state.

Zip To

Displays the end of the range of ZIP or postal codes for the tax rate. This is optional and typically is used when there are different tax rates by zip code range within a state.

City Default

Indicates how the system will prioritize this tax record when searching for the appropriate tax record when multi-jurisdictional taxes are enabled. If set to Yes , the system will prioritize city tax rates over county tax rates when multi-jurisdictional taxes are enabled.

County Default

Indicates how the system will prioritize this tax record when searching for the appropriate tax record when multi-jurisdictional taxes are enabled. If set to Yes , the system will prioritize county tax rates over city tax rates when multi-jurisdictional taxes are enabled.

Freight Taxable

Indicates whether freight charges are taxable under this tax jurisdiction. If set to Yes, the system will calculate tax on shipping charges if the underlying freight product setup is flagged as taxable.

Owner

Displays the user ID of the user who created this record.

Product

Displays the product record used to manage the accounting information for this tax.

About tax rates by zip code range

When your organization requires the system to validate tax rates using zip codes, it is important to understand that the zip code in the Ship To address of the invoice must fall within the zip code range of the tax rate setup. For example:

Tax Rate Setup

Ship To

Expected Result

Zip Code from

Zip Code to

25704

25704

25704-1538

Tax rate will not be applied to the transaction.

25704

25704

25704

Tax rate will be applied to the transaction.

25704

25705

25704-1538

Tax rate will be applied to the transaction.

25704

25705

25704

Tax rate will be applied to the transaction.

25704-1538

25704-1538

25704-1538

Tax rate will be applied to the transaction.

25704-0000

25704-9999

25704-1538

Tax rate will be applied to the transaction.

25704-0000

25704-9999

25704

Tax rate will be applied to the transaction.

25704-0000

25705-9999

25704

Tax rate will be applied to the transaction.

25704-0000

25705-9999

25704-1538

Tax rate will be applied to the transaction.

About multi-jurisdictional tax rates

You can enable your UX Online system to accommodate tax rates for multiple jurisdictions, such as city, county, state, and ZIP code ranges.

Important Note

Multi-jurisdictional tax rates (those by city or by county) are ignored when calculating taxes for meeting registrations and sessions. For more information, see Calculating tax by meeting location.

You can allow this by setting the PATax.EnableCountyTax parameter. If you enable this option, you can set up the following types of tax rates:

  • State

  • State and ZIP code

  • City and state

  • City, state, and ZIP code

  • County and state

  • County, state, and ZIP code

  • City, county, and state

  • Default tax rate (no city, county, state, or ZIP code)

Tax rate setup options when PATax.EnableCountyTax = true

Tax Rate

Setup

Name

City

County

State

Zip From

Zip To

City Default

County Default

Tax Rate

Product

Zip Code Based

Required

Required

Required

Required

Required

Required

City Based *

Required

Required

Required

True

Required

Required

County Based **

Required

Required

Required

True

Required

Required

State Based ***

Required

Required

Required

Required

Default

Required

Required

Required

* If there are any specific zip codes that require a different Tax Rate collected within a city, then set up an additional Tax Rate setup record and include the Zip From and Zip To.

** If there are any specific zip codes that require a different Tax Rate collected within a county, then set up an additional Tax Rate setup record and include the Zip From and Zip To.

*** If there are any specific zip codes that require a different Tax Rate collected within a state, then set up an additional Tax Rate setup record and include the Zip From and Zip To.

Tax rate validation when PATax.EnableCountyTax = true

Sequence 1

  • If the City Default bit field is set to True / Yes the system will look for a tax rate where the following fields match the invoice Ship To Address data exactly: City, State & Zip Code / Zip Code Range.

    • If all 3 data elements do not match then the system will go to Sequence 2

  • If the City bit field is set to No / False or is undefined (no data in city field), then the system will move to Sequence 2

Sequence 2

  • If the County bit field is set to True / Yes the system will look for a tax rate where the following fields match the invoice Ship To Address data exactly: County, State, Zip Code / Zip Code Range.

    • If all 3 data elements do not match then the system will go to Sequence 3

  • If the County bit field is set to No / False or is undefined (no data in county field), then the system will move to Sequence 3

Sequence 3

  • This was created as a “fail safe.” The system will match whatever it can and calculate the taxes accordingly:

    • City, State & Zip Code

    • County, State & Zip Code

    • City & State (No Zip Code Range)

    • County & State (No Zip Code Range)

    • State (No City, No County, No Zip Code Range)

    • Default Setup (No City, No County, No State, No Zip Code Range)

Tax rate setup options when PATax.EnableCountyTax = false

Tax Rate

Setup

Name

City

County

State

Zip From

Zip To

City Default

County Default

Tax Rate

Product

Zip Code Based

Required

Disabled

Disabled

Required

Required

Required

Disabled

Disabled

Required

Required

State Based

Required

Disabled

Disabled

Required

Disabled

Disabled

Required

Required

* If there are any specific zip codes that require a different Tax Rate collected within a state, then set up an additional Tax Rate setup record and include the Zip From and Zip To.

Tax rate validation when PATax.EnableCountyTax = false

Sequence 1

  • Then the system looks for tax rates by State and Zip Code Range where there is an exact match on the invoice Ship To Address state and the invoice Ship To Address zip code falls within the tax rate zip code range.

Sequence 2

  • If no tax rate is found by State and Zip Code Range, then the system looks for Tax Rates by State where there is an exact match on Ship To Address state.

  • If no tax rate is found by State, no tax is calculated.

Enabling multi-jurisdictional tax rates

To access this information, in the Navigation Tile Bar , select the Administration work area > UX Settings > UX Online Application Parameters to open the Active App Config View. This opens in a new window.

Locate and open the parameter PATax.EnableCountyTax. Set the Config Value field to the method that your organization uses:

  • TRUE – Allows UX Online to select tax rates based on the additional attributes (for example, city, or county) of the invoice’s Ship To record.

  • FALSE – Use the standard tax rate selection method, which uses the state or state + ZIP code of the invoice’s Ship To record.

Click Save & Close the record to return to the View window. Because the list opened in a new window, click the “ X ” in the upper right hand corner of the window to close it.

Calculating tax by meeting location

For taxable meeting registrations and sessions, the invoice Ship To address fields are ignored and tax is calculated based on the location record selected in the meeting setup under the following conditions:

  • When the location record selected in the meeting setup contains state or state and zip code address data, tax is calculated based on meeting location record selected in the meeting setup.

  • If no location record is selected in the meeting setup, no tax is calculated on registrations or sessions that are flagged as taxable.

  • The taxable field in registration and session setup dictates whether a registration/session transaction is taxed. If not checked in the registration or session setup, no tax is calculated on the selected registration or session.

Note

If the meeting setup is not taxable and the registration or session setup is taxable, tax will be calculated.

Multi-jurisdictional taxes are not supported when calculating tax by meeting location. The application parameter PATax.EnableCountyTax is ignored for calculating taxes on meeting registrations and sessions.

About multicompany taxes

If your organization works in a multi-company environment and you need to manage multiple tax rates for those companies, your UX Online system was deployed using one of two options for managing these taxes.

Important

Your UX Online system was deployed with the tax product/tax rate structure needed by your organization. If you need to make changes, we recommend that you consult your Protech representative.

Option 1 – 1 tax product per tax rate/company combination. If your system uses this option, you will have a tax product for each tax rate and company combination, and a tax rate record for each tax rate you work with. For example, if you have three tax rates and two companies, there will be six tax products. The tax rates are not assigned to a tax product, but each tax product is assigned to a tax rate. This option requires more setup if you are working with a significant number of tax rates. This option was set up in the following way:

  • The tax rate records are created, but a tax product is not assigned.

  • A tax product is created for each tax rate and company combination, with the appropriate tax rate assigned.

Option 2 – 1 tax product per company. If your system uses this option, you will have a tax product for each company, and a tax rate record for each tax you work with. All of the tax products are assigned to one tax rate record, and all of the tax rates are assigned to one tax product. This simplifies setup if you have several tax rates for multiple companies. For example, if you have three tax rates and two companies, you will have two tax products. This option was set up in the following way:

  • One tax product record is created for each company. No tax rate is assigned at this time.

  • A tax rate record is created for each tax. The same tax product is assigned to all of the tax rates.

  • The same tax rate is assigned to all of the tax products.

Credit card records

Credit card records contain information about how the credit card payments you enter on sales transactions will be processed.

Credit card records for each credit card your organization accepts will be set up for you during your UX Online implementation. If you accept credit card payments in multiple currencies, you will have a separate credit card record for each currency that you accept. For example, if you accept VISA payments in both US dollars and Euros, you will need two VISA credit card records.

To access this information, in the Navigation Tile Bar , select the Administration work area > UX Settings > Credit Cards to open the Active Credit Cards View. Locate and open the record you want to view. When you are finished Save & Close the record to return to the View window. Close the View window by clicking the “ X ” in the upper right hand corner of the window.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

Field

Description

Process Type

Indicates that this credit card will use Payflow Pro verification.

Name

Displays the name assigned to this credit card record.

Company

Displays the accounting company associated with the credit card record.

Currency

Displays the currency associated with the credit card record.

Owner

Displays the user ID of the user who created this record

Live Host Address

Displays the host address used for processing.

Test Host Address

Displays the host address used for testing processing. (This address is used only for testing the credit card processing integration.)

Partner

Displays the authorized Payflow Pro Reseller that you are registered with for Payflow Pro Service. This value is case-sensitive and is required when logging in to the Payflow Pro Manager web site.

Vendor

Displays the vendor ID assigned by Payflow Pro when you registered the account.

User

Displays the user ID for the Payflow Pro user account, if one exists. If there is no user account set up in the Payflow Pro Manager (and typically there is not), then this field displays the same value as the Vendor field. This value is case-sensitive and is required when logging in to the Payflow Pro Manager web site. NOTE: In earlier versions, this field was labeled Merchant Login.

Password

Displays the encrypted login password used to access the Payflow Pro Manager website.

Host Port

Displays the Payflow Pro host port number: 443.

Time Out

Displays the length of time (in seconds) that the Payflow Pro client will wait for the Payflow Pro server to respond to transaction requests.

Important

If the PayPal Manager account password changes, you must update this in the UX Online credit card setup. When you save your changes, the information in the Password field will be encrypted.

State Codes

Your system was deployed with the standard state codes for U.S. states and territories, and Canadian provinces. Protech does not update these tables, so you will need to update them if necessary. To access this information, in the Navigation Tile Bar, select the Administration work area > UX Settings > State Codes .

Source Codes

With the exception of the WEB source code, source code records were set up based on your organization’s specifications. Do not modify the WEB source code. You can modify the remaining source codes as needed. To access this information, in the Navigation Tile Bar , select the Administration work area > UX Settings > Source Codes .

Country Codes

Your system was deployed with standard ISO country codes. Protech does not update these tables, so you will need to update them if necessary. To view this information, in the Navigation Tile Bar , select the Administration work area > UX Settings > Country Codes .

Price lists

Pricing in UX Online is controlled by price lists. A price list is the way that UX Online groups the price records that apply to a specific group of customers. For example, if your organization offers products or renewal benefits at one set of prices for non-members in your base organizational currency, and a different set of prices for members in your base organizational currency, you will have two price lists: One for non-members in your base organizational currency and one for members in your base organizational currency. Your UX Online system can have as many price lists as needed for the different pricing structures that your organization uses, however, a minimum of two price lists are required for a single currency environment, named: ‘Member’ and ‘Non-member’.

If your organization is using the multicurrency features of UX Online, your system requires equivalent price lists for every supported currency. For example, if your organization supports multicurrency for Euro and US Dollar, you will require a minimum of four price lists, named: ‘Member’ (US Dollar), Member (Euro), ‘Non-member’ (US Dollar), and Non-member (Euro). See Currency-based price lists and Price Lists many-to-many relationships for more information.

Important

You must have one price list named ‘Member’ and one price list named ‘Non-member’ for each currency. In a multi-currency environment, you must have the same set of price list records for each currency supported by your organization. For example, assume your organization uses US Dollar, Euro, and Australian Dollar currencies. Also assume you have four Price List records where the currency = US Dollar: Member, Non-member, Faculty, and Student. You will need to set up four equivalent Price List records where the currency = Euro and four equivalent Price List records where currency = Australian Dollar.

For your base organization currency, the naming convention must equal ‘Member’ and ‘Non-member’.

To access this information, in the Navigation Tile Bar , select the Administration work area > Product Catalog > Price Lists to open the Active Price Lists View . Locate and open a record to view detailed information about the price list. When you are finished with the record, Save & Close the record to return to the Active Price Lists View. Click Product Catalog on the Top Navigation Toolbar to return to the Product Catalog.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

  • Name – This field is required and displays the name of the price list.

Warning

Do not create more than one price list for each currency named ‘Non-member’ or where the price list name contains the words ‘non-member’. See Default price list for new account and contact records, below.

  • Start Date – This field is left blank.

  • End Date – This field is left blank.

  • Currency – This field is required and displays the currency of the prices in this list.

  • Default – This field is required. It will be used in the future to flag the ‘Non-member’ price list that is the default price list for newly created account and contact records. However, there is currently no logic associated with this flag in the price list record setup.

  • Description – Displays a detailed description of the price list.

Default price list for new account and contact records

When creating new account and contact records, the system automatically assigns a non-member price list to those records. By searching price lists where the name contains the words ‘non-member’ and where the price list currency equals the user currency, UX selects the first price list record it finds that meets the “like” non-member and currency search criteria. If more than one price list record exists that meets this criteria, UX randomly selects one to use as the default price list for new account and contact records created by the user.

Until future logic is in place to flag a specific price list record as the default for new account and contact records, do not create more than one price list record per currency where the name contains or is “like” ‘non-member’. For example, for US Dollar, create one price list record named ‘Non-member’ and one price list record named ‘Student’, but do not create one price list record named ‘Non-member’ and another price list record named ‘Student Non-member’. The “like” search is not case sensitive and recognizes all forms of the words ‘non-member’, with or without the hyphen.

Important

When creating the non-member price list for your base organizational currency, the name must equal ‘Non-member’. Do not add a prefix or suffix to the name.

Default price list for contacts and accounts created by qualifying a lead

When qualifying a lead as an opportunity, CRM creates a new contact record. If the lead record contains a company name, CRM creates a new account record as the parent to the contact record with the contact as the primary contact.

UX plugins will assign the default price level to the contact record and the parent account record created by CRM based on the Price List setup record where Default = true. If no Price List is flagged as the default, no price level will be assigned to contacts or accounts created by qualifying a CRM lead.

Price lists many-to many relationships

To support currency/price level logic when creating a new invoice in a multicurrency environment, you must also configure the many-to-many price level relationships within each price list record. This allows the user to use the Currency lookup on an invoice to select an alternate currency and automatically update the invoice Price Level. For example, if the default currency in the invoice is “US Dollars” and the Price List is “Member-US” when the currency is changed to “Euro,” the Price List is automatically changed to “Member-Euro” because of the Price List X-Ref Setup.

Using this example, in the setup for the member Price List record for US Dollar, you must relate the existing member Price List record for Euro; in the member Price List for Euro, you must relate the existing member Price List record for US Dollar. This creates the cross-reference for the many-to-many relationships. If you add a currency and price list(s) for that currency, you will need to update the cross-reference for the related Price List records.

From the Price List record, click the caret (‘ ’) next to Price Lists to open the hidden Navigation Pane of related records. Select Price Lists to open the Active Price Lists View.

  • Click Add Existing Price List on the View toolbar.

  • In the Look Up Records view of Price Lists, select the related Price List record(s). In the example of a member Price List record for US Dollar, you would select the existing member Price List record for Euro, click Add, and then click OK. If you have multiple member Price Lists in alternate currencies, you must relate each one to the member Price List record for US Dollar. Never relate a Price List record that uses the same currency. See the table below for a sample of the set up for related Price List records that assumes three currencies.

Save & Close the Price List Record. Repeat this process for each Price List record.

Important Notes

When creating price list relationships, never “Add Existing Price List” that has the same currency as the Price List record for which you are creating the relationship. For example, when adding related Price Lists to the member price list for US Dollar, never select a Price List where the currency equals US Dollar as a related Price List – only relate Price Lists in alternate currencies.

Sample setup assuming three currencies where US Dollar is the organizational currency

Supported Currencies

Minimum Required Price List Records

Price List Currency

Required Related Price List Records

US Dollar

Member

US Dollar

Euro Member

Australian Member

Non-member

US Dollar

Euro Non-member

Australian Non-member

Faculty

US Dollar

Euro Faculty

Australian Faculty

Student

US Dollar

Euro Student

Australian Student

Euro

Euro Member

Euro

Member

Australian Member

Euro Non-member

Euro

Non-member

Australian Non-member

Euro Faculty

Euro

Faculty

Australian Faculty

Euro Student

Euro

Student

Australian Student

Australian Dollar

Australian Member

Australian Dollar

Member

Euro Member

Australian Non-member

Australian Dollar

Non-member

Euro Non-member

Australian Faculty

Australian Dollar

Faculty

Euro Faculty

Australian Student

Australian Dollar

Student

Euro Student

Validating product price list items after adding a new price list

Part of your initial system set up includes creating price lists and, in the case of multi-currency environments, adding the price list many-to-many relationships described above.

As your organization changes over time, you may need to add one or more price lists and, where appropriate, update the price list many-to-many relationships in the new and existing price list records.

To support correct invoice pricing, you also must update the price list items of existing products after adding a new price list by running the Validate Product Price List Items utility. This utility checks all products for price list items and if a product is missing a required price list item, creates one.

To access this utility, in the Navigation Tile Bar, select the Product Sales work area > Product Sales. Select Validate Product Price List Items to initiate.

Price lists and customer records

When you create an account or contact record, the system will assign a default price list to that record (in most organizations, this will be the non-member price list). The system will update the account or contact record as their membership status changes. For example, assume that you have two price lists: Member and Non-member. If you enter a membership invoice for a contact who is non-member, UX Online will automatically change the price list on the contact record from Non-member to Member when the invoice is paid in full. Later, if that contact’s membership is terminated, the price list will automatically change back to Non-member. These updates are based on the primary renewal billing record benefit rate Price Level X-Ref.

When you create an invoice for a contact or account, UX Online will assign that customer’s price list to the invoice (you can change the price list on an individual invoice if necessary). The prices for the products and renewal benefit rates on the invoice will be based on a price record for that price list. If the system cannot find a valid price record with that price list, the price will be set to zero.

Price records

A price record sets the price for an individual product or renewal benefit rate in a specific price list. For example, assume that you have training manual that you sell for $25 to non-members and for $20 to members. Therefore, this training manual product will have two price records: one for the non-member price, and one for the member price. A product or renewal benefit rate can have several price records. Every product and renewal benefit rate should have a price record associated with each price list in your system.

In most cases, a price record can set the price for a product as a flat currency amount, or calculate it as a percentage of the product’s list price (which is set in the product record).

Where noted in this documentation, UX Online does not use the product price record for pricing. For example, sales tax calculations are based on the tax rate rather than the price records in the underlying tax product that manages accounting information for that tax rate.

Note

Price lists also include price list items; however, price list items are Dynamics CRM records, and are not used by UX Online.

Chapter 2: Accounting Setup

This chapter describes the records that control how your UX Online accounting system works. Most of these settings and products will be set up for your system during implementation, and should not be changed without consulting your system administrator or your Protech representative.

During the implementation of your UX Online system, the Refresh Utility might be set up to automatically create your chart of accounts and products records based on the data in your Microsoft Dynamics GP system, and to keep those records up-to-date. If so, you may need to modify the settings used by this utility.

As your organization’s needs change, you may need to create additional records. For example, you may need to add or modify credit card records.

This information includes the following topics:

  • Global Setup Default

  • Companies

  • Chart of Accounts records

  • Refresh Utility overview

Global Setup Default

The Global Setup Default record establishes the link between UX Online and your back office accounting system, and your back office inventory system (if you are using one).

Important Note

There can be only one Global Setup record.

The following information on the General section of the Global Setup Defaults record will be set up for you during your UX Online implementation. To view this information, in the Navigation Tile Bar , select the Administration work area > UX Settings > Accounting Company and Charts of Account Settings > Global Setup Default to open the Active Global Setup Defaults View . This opens in a new window. Locate and open the Global Setup record you want to view. The record will open in a new window. When finished, Save & Close the record. Close the Active Global Setup Defaults View window by clicking the “ X ” in the upper right hand corner of the window.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

General

Field

Description and Possible Values

General Ledger System

Identifies the accounting system where the General Ledger data is posted.

Possible values: None, Dynamics GP or Dynamics SL.*

Inventory System

Identifies which accounting Inventory system the quantity sold is posted. If posting to Dynamics GP or Dynamics SL, the items must be set up in the accounting system as well as UX Online. If the choice is Internal, the UX Online system will use the Quantity On Hand field in the Products Table to track the quantity of the product in Inventory. Possible values: None, Dynamics GP, Dynamics SL, or Internal.

*Note: Great Plains is currently known as Microsoft Dynamics® GP; Solomon is currently known as Microsoft Dynamics® SL.

Companies

Company records establish the link between each separate organization in UX Online and the company databases in your back office accounting system. This link controls the accounting system company where UX Online transactions are posted.

Company records also manage the Refresh Control options for your chart of accounts and products. If available, Refresh Control settings also manage your accounts payable integration for refund processing.

For detailed information on Refresh Control settings, see Setting up Refresh Utility and AP integration options for a company .

For detailed information on Chart of Accounts Refresh Control, see Setting up Refresh Utility options for your chart of accounts.

The following information in each Company record will be set up for you during your UX Online implementation. To view this information, in the Navigation Tile Bar , select the Administration work area > UX Settings > Accounting Company and Charts of Account Settings > Companies to open the Active Companies View . This opens in a new window. Locate and open the Company record you want to view.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

Section

Field

Description

General

CRM Related

Name/Description

Displays the full name of the company.

Company Number

Company code in CRM

GL Account Mask

Displays the account format for the accounting system chart of accounts for this company. For example, a GL account mask of 3-4-2 equates to an account format is three segments: XXX-XXXX-XX.

Default Company

Is this the default company?

Calendar Month Fiscal Year End

Displays the numeric value of the month that this company’s fiscal year ends.

Accounting System Related

Accounting System Company Code

Displays the accounting system company code. This must exactly match the accounting system company code.

Accounting System Server Name

Displays the name of the database server for this company.

Accounting System Database Name

Displays the name of the company database in the accounting system. UX Online transactions associated with this company will be posted to this database. Note: This must exactly match the name of the accounting system database.

Post to GP Bank Reconciliation

Indicates whether transactions for this company will create Bank Reconciliation deposit entries in Microsoft Dynamics GP.

Post to Bank Reconciliation in Detail

Indicates whether this company’s deposit transactions will post in detail (one entry for each payment product on each invoice in a batch) or in summary (one entry per payment product in a batch).

Dynamics SL Related

System Database Name

Displays the name of the database server for this company.

Refresh Control

Chart of Accounts

Refresh Chart of Accounts

The refresh utility only applies to information coming from Great Plains to UX. Check this option if you want this company’s chart of accounts to be updated during the refresh process. For additional information, see Setting up Refresh Utility options for your chart of accounts .

Products

Refresh Products

The refresh utility only applies to information coming from Great Plains to UX. Check this option if you want this company’s product records to be updated during the refresh process.

Default A/R GL Account

Select the Accounts Receivable account that you want to use as the default for new product records created during the refresh process.

Force Product Overwrite

Mark this option if you want the accounting system information to replace the corresponding information in the UX Online product record during the refresh process.

Accounts Payable Refunds

Receive Check Date and Number from Accounting System

Mark this option if you want the accounting system check date and check number information to update the refund transaction invoice detail line item during refund processing.

Use Member ID as Vendor ID

Mark this option if you want to use the CRM member ID as the vendor ID during refund processing when the vendor does not exist in the accounting system.

Update Accounting System Vendor Name and Address from UX during Refund Processing.

Mark this option if you want to update the accounting system vendor record name and address with data from UX during refund processing.

Related information

In the Company record, click the down caret (‘ ’) next to the Company record to display the Associated Views. Click Chart of Accounts to view a list of the chart of accounts records associated with this company. You can also click Credit Cards in the Associated Views to view the credit card records that are set up for this company.

Note

Please do not modify or edit the settings in a company record without contacting your system administrator or Protech representative. In practice, Microsoft Dynamics GP gives the Database the same name as the Company Code; however, there is no reason to make them different. In Microsoft Dynamics SL, they usually are different (for example,”0010″ and “SolomonDemo10”). As for the Company Number (Company Code in CRM), this usually will be the same as the Company Code in Microsoft Dynamics GP or Microsoft Dynamics SL, but does not have to be the same. We recommend making the codes the same where possible and the setup as simple as possible. The Company record in UX Online ties all these fields together.

When finished, Save & Close the Company record. Close the Active Companies View window by clicking the “ X ” in the upper right hand corner of the window.

Chart of Accounts records

The Chart of Accounts records establish the link between your GL accounts in UX Online and the chart of accounts in your back office accounting system. This link controls the specific accounts where UX Online transactions will be posted.

Note

During your system implementation, the Refresh Utility may have been set up and used to create your chart of accounts and products records in UX Online. For more information, see Refresh Utility overview .

The following information in the General section of each Chart of Accounts record will be set up for you during your UX Online implementation. To access this information, in the Navigation Tile Bar , select the Administration work area > UX Settings > Accounting Company and Chart of Account Settings > Chart of Accounts to open the Active Chart of Accounts View. This View opens in a new window. Locate and open the record you want to view. The record will open in a new window. When finished, the record. Close the Active Chart of Accounts View window by clicking the “ X ” in the upper right hand corner of the window.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

Field

Description and Possible Values

Name

Displays the descriptive name of the account.

Account Number

Displays the account number, in the format entered in the GL Account Mask field of the company record.

Company

Displays the company associated with the account.

Account Type

Identifies the types of UX Online transactions that can be posted to the account. For detailed information on Account type, see Account categories and account types, below.

Account categories and account types

Account categories are used in Microsoft Dynamics GP to group the accounts that will be printed on financial statements. They are linked to account types in UX Online, and are used as part of the GL Account Refresh Utility. For more information, see Refresh Utility overview .

You can add additional account categories to Microsoft Dynamics GP if necessary. For more information, refer to your Microsoft Dynamics GP documentation.

You can select any of the following values when creating UX Online chart of accounts records:

  • General – Used for various liability accounts, such as Due To or Due From, or for revenue accounts.

  • Payment Related – Used for all payment products, including the Transfer and Refund products. When assigned to the account, it is associated with a Payment-type product.

  • A/R – Standard – Used for all accounts considered short term Accounts Receivable.

  • A/R – Long Term – Used for all accounts that are considered long term Accounts Receivable and that are used in the Fundraising module only.

  • Unapplied – Used for all accounts that are used by Payment products as the unapplied account (for overpayments or partial payments on Cash Basis invoices, or for refunds that are posted before the associated customer payment is posted). See About unapplied accounts for more detailed information.

  • Deferred – Membership and Subscription – Used for all Deferred Revenue accounts used for membership dues and subscriptions (which recognizes revenue over the life of the benefit).

  • Deferred – by Event – Used for Deferred Revenue accounts used for events when you want to recognize all of the revenue for an event at one time.

  • Deferred – by Date – Used for Deferred Revenue accounts used for events when you want to recognize the revenue for an event by date. (For more information, see Event revenue recognition and account types .)

  • A/P – Used for the refund process.

About unapplied accounts

An unapplied account is a holding account used to store temporary balances. It is used in three situations:

  • If you record a partial payment for a product that uses cash basis accounting, such as a membership renewal, the underpayment is recorded in the unapplied account. The partial payment amount will remain in the unapplied account until you record the receipt of the amount remaining to be paid; at that point, the entire payment amount will be recorded as revenue.

  • If you record an overpayment for an invoice, the overpayment is recorded in the unapplied account. The overpayment amount will remain in the unapplied account until you refund it or apply it to another invoice.

  • If you record a payment from a customer in one batch, and then a refund to that customer in another batch, and then the refund batch is posted before the payment batch. The refund amount will remain in the unapplied account until the payment batch is posted.

The following examples illustrate how the unapplied account is used in these situations:

Partial payment on an invoice with a cash basis product

Assume that you have an invoice that includes one line item for a $250 membership renewal, which is set up to use cash basis accounting, and another line item for a partial payment of $150. When this transaction is posted, the following journal entry is created:

Account

Debit

Credit

Cash

$150

Unapplied

$150

The debit amount of $150 is recorded in the account in the payment product’s Primary GL Account field, and the credit amount of $150 is recorded in the unapplied account in the payment product’s AR GL Account field.

Overpayment on an invoice with a cash basis product

Assume that you have an invoice that includes one line item for a $250 membership renewal, which is set up to use cash basis accounting, and another line item for an overpayment of $300. When this transaction is posted, the following journal entry is created:

Account

Debit

Credit

Cash

$300

Unapplied

$50

Revenue

$250

 

The debit amount of $300 is recorded in the account in the payment product’s Primary GL Account field, and the credit amount of $50 is recorded in the unapplied account in the payment product’s AR GL Account field. The $250 credit amount is recorded in the account in the membership renewal product’s Primary GL Account field

Overpayment on an invoice with an accrual basis product

Assume that you have an invoice that includes one line item for a $75 product that is set up to use accrual basis accounting, and another line item for an overpayment of $100. When this transaction is posted, the following journal entry is created:

Account

Debit

Credit

Cash

$100

Unapplied

$25

Revenue

$75

The debit amount of $100 is recorded in the account in the payment product’s Primary GL Account field, and the credit amount of $25 is recorded in the unapplied account in the payment product’s AR GL Account field. The $75 credit amount is recorded in the account in the product’s Primary GL Account field.

Refund posted before the payment

Assume that you have an invoice that includes a line item for a check payment of $200.00 in Batch 101, and another invoice with a line item for a refund payment of $200.00 in Batch 102. If you post Batch 102 before you post Batch 101, the following journal entry is created for the refund:

Account

Debit

Credit

Unapplied

$200

Refunds Payable

$200

Then, when you post Batch 101, the following journal entry is created for the $200 payment:

Account

Debit

Credit

Cash

$200

Unapplied

$200

Refresh Utility overview

The Refresh Utility is a system job that is set up during your UX Online system implementation. It can be used initially to set up the UX Online chart of accounts and product information by using information from your accounting system (either Microsoft Dynamics GP or Microsoft Dynamics SL).

The Refresh Utility can also be used to ensure that changes made to any of this information (the chart of accounts and product records) in the accounting system are reflected in UX Online. You can also select data update options for AP integration refund processing if your organization purchased the Accounts Payable module.

The utility will be scheduled to run in the background once a day at a time specified by your organization, keeping your UX Online chart of accounts and product records up-to-date. If the refresh utility creates any new products in UX Online, the base organization currency will be assigned to the product record. (For more information about the base currency, see Currency records .)

If you need to run the Refresh Utility before its next scheduled occurrence, you can initiate the system job manually from a menu item. To access the menu item, in the Navigation Tile Bar , select the Financial Manager work area > Accounting Manager > Accounting Company and Charts of Account Settings  > Start Accounting Refresh Job .

For more information, refer to the following topics:

Setting up Refresh Utility and AP integration options for a company

In the company record, you can set up the Refresh Utility for each company you maintain in your accounting system (either Microsoft Dynamics GP or Microsoft Dynamics SL) to control how chart of account and product record data is updated from your accounting system to UX Online.

In addition, if you are using the AP integration for refund processing, you can use the settings here to control how data is updated from UX Online to the Accounts Payables module of your accounting system.

To access this information, in the Navigation Tile Bar , select the Administration work area > UX Settings > Accounting Company and Charts of Account Settings > Companies to open the Active Companies View. This View opens in a new window. Locate and open the Company record you want to view.

In the Refresh Control section of the Company record, complete the following setup:

  • Mark the Refresh Chart of Accounts option if you want this company’s chart of accounts to update from your accounting system to UX when the Refresh Utility runs.

  • Mark the Refresh Products option if you want this company’s product records to update from your accounting system to UX when the Refresh Utility runs.

    • Force Product Overwrite . Left unchecked, the default for the Force Product Overwrite option prevents the Refresh program from forcing an overwrite of any fields that you may have changed in the product setup in UX Online, even if the equivalent change was not made in the accounting system. Only check this box if you want the Refresh program to ignore any changes made to products in UX Online and force an overwrite of information in the accounting system to the product in UX Online.

Important

If you mark the Refresh Products option, you must open each new product record created by the Refresh Utility in UX Online to complete the product setup by creating price records.

If you marked the Refresh Products option, select the Accounts Receivable account that you want to use as the default for new product records created during the refresh process.

Note

You can change the default Accounts Receivable account for any new product record created by the Refresh Utility in UX Online.

Note

If you change the AR GL Account and Partial Backorder fields in UX Online, these fields will not be overwritten by the Refresh Utility.

If your organization purchased the AP Integration, complete the following:

  • Mark the Receive Check Date and Number from Accounting System option if you want the accounting system check date and check number information to update the refund transaction invoice detail line item. This update does not occur during refund processing, but occurs after you have completed payables batch processing and check printing in your accounting system. The update is part of a stored procedure in the refresh system job.

  • Mark the Update Accounting System Vendor Name and Address from UX during Refund Processing option if you want to update the accounting system vendor record name and address with data from the UX Online refund transaction Payee Information during refund processing.

  • Mark the Use Member ID as Vendor ID option if you want to use the UX Online member ID as the vendor ID during refund processing instead of the Bill To Customer Vendor Number. See Accounting System Vendor Record Updates for more information.

Click Save & Close on the record toolbar. Close the Active Companies View window by clicking the “ X ” in the upper right hand corner of the window.

Refresh Products – GP item fields used to create products in UX

When the Refresh Products process creates a new product, the following fields typically are mapped from an item in Microsoft Dynamics GP to create a product in UX Online:

Important

If you mark the Refresh Products option, you must open each new product record created by the Refresh Utility in UX Online to confirm that setup is accurate and complete. Manual changes required include setting the Reimbursable field to Not Reimbursable, setting the Apply Freight, and creating price records.

Dynamics GP Item Field

UX Product Field

Item Number

ID

Item Description

Name

Item Type

Product Type

U Of M Schedule ID

Unit Group

Price Level

Default Price Level

Location Code

Default Warehouse

Tax Options

Taxable (checkbox)

Inactive (checkbox)

Status

Shipping Weight

Stock Weight

Sales Account

Primary GL Account

Allow Backorders (checkbox)

Allow Backorder?

Allow Partial Backorder?

Substitute Item 1

Substitutes

Substitute Item 2

Substitutes

Quantity on Hand

Available Inventory

Setting up Refresh Utility options for your chart of accounts

The Chart of Accounts Refresh Control manages how the Refresh Utility works with specific Microsoft Dynamics GP account categories or Microsoft Dynamics SL account classes and the corresponding UX Online account types. In addition, you can specify whether the UX Online information for each account type is updated each time the utility is used, or only for the initial chart of accounts set up.

If an account category exists in Microsoft Dynamics GP that does not have a corresponding record in UX Online, the Refresh Utility will create it; you can then set it up to create the necessary General Ledger accounts the next time the refresh process runs.

Important

You need to set up these account category/account type relationships for each accounting company where the accounting company setup includes Refresh Chart of Accounts = true.

To access this information, in the Navigation Tile Bar, select the Administration work area > UX Settings > Accounting Company and Charts of Account Settings > Chart of Accounts Refresh Control to open the Active GL Account Categories/Classes View. This View opens in a new window.

In the GP GL Account Categories list, click New to create a new relationship record between a Microsoft Dynamics GP account category or a Microsoft Dynamics SL account class and a UX Online account type, or double-click an existing record to view its settings.

  • Enter the number of the account category or the ID of the account class you want to set up, and then select the UX Online account type you want to map to this account category.

  • Enter a name for this account category/account type relationship.

  • Select the Include option (Yes/No).

  • If you want the Refresh Utility to create GL accounts for this account category or account class, select Yes for the Include option.

  • If you do not want the Refresh Utility to create GL accounts for this account category or account class, select No for the Include option.

  • Select the Create ONLY option (Yes/No). This option only functions when Include = Yes. It is ignored when Include = No.

  • If Include option = Yes and you want the Refresh Utility to create GL accounts for this account category or account class but never update them, select Yes for the Create ONLY option.

  • If Include option = Yes and you want the Refresh Utility to create GL accounts for this account category or account class and update them, select No for the Create ONLY option.

  • Select the company for the account category, class, and account relationship settings.

Click Save & Close o the record toolbar to return to the Active GL Account Categories/Classes View. Close the View window by clicking the “ X ” in the upper right hand corner of the window.

Accounting Currency

If your system is integrated with the Microsoft Dynamics GP accounting system, you must link the currency codes in UX Online with the corresponding accounting system currency IDs.

To view existing currency code/currency ID links, in the Navigation Tile Bar , select the Administration work area > UX Settings > Accounting Company and Charts of Account Settings > Accounting Currency Codes to open the Active Accounting Currency View . This View opens in a new window.

Open a record to view the details. When finished, Save & Close the record. Close the Active Accounting Currency View window by clicking the “ X ” in the upper right hand corner of the window.

These accounting currency records include the following information:

  • Currency – Displays the UX Online currency code.

  • Accounting Currency Code – Displays the corresponding accounting system currency ID.

Chapter 3: Payment and Adjustment Product Setup

UX Online manages the accounting information and the transaction processing for different types of payments by setting them up as product records. During the implementation of your UX Online system, your project team will work with you to define and set up your payment and adjustment products, such as checks, credit cards, transfers and refunds.

If your organization requires additional payment or adjustment products, such as gift certificates, refer to this documentation to set them up.

This chapter includes the following information:

Payment and adjustment products overview

Most of the following payment and adjustment products will be set up for your organization during the implementation of your UX Online system. (Gift Certificate payment products will not be set up during implementation; for more information about setting up gift certificates, see Setting up payment and adjustment payment products .)

If you are using multicurrency, you must have payment products for each currency. For example, if you accept cash and checks in both US dollars and Euros, you will have two cash/check payment products.

If you are using multicompany, you must have payment products for each company.

Important

If you have any questions about modifying these payment and adjustment products, please contact your system administrator.

You can view each of these products in the Product Setup record. In the Navigation Tile Bar , select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup .

The following table identifies the basic payment and adjustment product types.

Payment Type

Description

Check Payment

Used for payments received by check.

Credit Card Payment

Used for payments received by credit card and incorporates the Payflow Pro integration logic for authorization and settlement.

Gift Certificate

Used for payments made with gift certificates issued by your organization.

Transfer Product

Used to enter transactions to transfer a credit balance (due to an overpayment) from one invoice to another. For example, this will used to process overpayments for dues, during the pledge installment process, and to create advertising insertions.

Refund Product

Used to issue a refund to a customer to set the balance due on an invoice to zero, and to trigger the refund process. The refund process is integrated directly with Payables Management for Microsoft Dynamics GP or Microsoft Dynamics SL. ( Note: This process requires an additional license. For more information, contact your Protech representative.) For more information about refunds, see Payment and Adjustment Transactions .

Write-off Product

Used to enter write-off transactions to clear uncollectible invoice balances. Typically used in conjunction with write-off limits and the write-off process. For more information, see Writing off invoice balances .

Miscellaneous Unapplied Payment

Used to enter miscellaneous check/cash payments.

Adjustment

Used to enter adjustment payment transactions.

Lockbox

Used for payments received by Lockbox.

Setting up payment and adjustment products

When setting up any payment and adjustment product in UX Online, the information you enter or select will affect the integration to an accounting system and UX Online transaction processing. Prior to setting up a payment and adjustment product, please review your product characteristics and plan the setup that will best support your business processes.

Note

If you are using multicurrency, you must have payment products for each currency. For example, if you accept cash and checks in both US dollars and Euros, you will have two cash/check payment products – one for each currency.

If you are using multicompany, you must have payment products for each company.

Set up for all payment and adjustment products is essentially the same. There are a few key variations to the required field entries, depending on whether the product is a check, credit card, transfer, refund, write-off, gift certificate, or miscellaneous unapplied payment product. Where applicable, these variations are identified in the field entry descriptions.

Note

In order to create payment and adjustment products in UX Online, you must first complete the accounting setup for the accounting company (or companies) and the chart of accounts. For more information, see Accounting Setup .

In the Navigation Tile Bar , select the Product Sales work area > Product Sales > Product Sales Settings  > Product Setup to open the Active Products View. This View opens in a new window .

Click New on the List View toolbar to create a new payment product record. The new record will open in a new window. Complete the fields in the General section as shown:

  • Product ID – enter a payment code. Protech recommends that the ID be an abbreviation of the payment name. For example:

    • Cash and check payments: CK

    • Credit card payments: Use an abbreviation of the credit card’s name, such as MC for MasterCard or VS for Visa.

    • Gift certificates: GC

    • Transfer payments: TR

    • Refund payments: RF

    • Miscellaneous unapplied payments: MISC

    • Write-off payments: WO

Note

If your organization is working in a multi-company environment, you can append the company code as a suffix to differentiate between payment products. For example, if one of your companies is an association, and another is a foundation, the check payment product for the association could have an ID of CKASSOC, and for the foundation, it could be CKFOUND. For questions about assigning an ID, contact your system administrator.

  • Name – enter a descriptive name for the payment product.

  • Unit Group – Click the Lookup button, select Each, and click OK .

  • Default Unit – Click the Lookup button, select Each, and click OK .

  • Currency – If you are working in a single currency environment, by default, your preferred currency appears in this field. Otherwise, you will need to select the Currency .

  • Product Type – Select Payments & Adjustments from the list.

  • Subject – This field is optional.

In the Accounting section, complete the following fields:

  • Company – The system will automatically populate this field with the company record flagged as the default company in your set up. If you need to make a change, click the Lookup button to select the appropriate accounting system company for this product. This controls where accounting data will post during the posting process and controls the display of GL accounts available in the GL account lookup fields.

  • Reimbursable – Select Not Reimbursable for all payment products except refund payments. If you are creating a refund product, select Refund Payment.

  • Primary GL Account – Click the Lookup button to select the GL account to which accounting data will post for the specific payment product.

  • Check/Cash Products – Select the GL account for cash or cash equivalents.

  • Credit Card Products – Select the GL account for cash or cash equivalents.

  • Gift Certificate Products – Select the GL account for gift certificates.

  • Transfer Products – Select the transfer clearing GL account.

  • Refund Products – Select the refunds payable GL account.

  • Write-off Products – Select a write-off expense GL account.

  • AR GL Account – Click the Lookup button to select an unapplied GL account. For more information, see About unapplied accounts .

  • Cash Basis – Leave the default setting for this field as No . (This is the required setting for payment products.)

  • Control Accrual Basis via AR Utility – This field is disabled and does not apply to payment products.

  • Secondary GL Account – This field is disabled and does not apply to payment products.

  • AP GL Account –

    • If you selected Not Reimbursable in the Reimbursable field, this field is disabled and not required.

    • If you selected Refund Payment in the Reimbursable field, this field is active and requires entry. Click the Lookup button to select the accounts payable GL account for the refund payment product.

In the Payment Product Info section, select the fields appropriate to the payment product you are creating:

  • For Cash/Check products: Checkbook ID – If you are using the integration with Microsoft Dynamics GP Bank Reconciliation, enter the Checkbook ID of the GP checkbook you use for cash/check payment transactions

  • For Credit Card products

    • Is it a credit card? Set this option to Yes . (This allows the system to process this as a credit card payment using Payflow Pro.).

    • Credit card type – Select the credit card type from the list. (This allows the system to verify that the card number entered during transaction entry is valid for the card type selected.)

    • If Credit Card, Use Live Verification – Select the appropriate option as follows:

      • If you are working in a test mode for credit card processing, select No .

      • If you are working in a live mode for credit card processing, select Yes .

    • Checkbook ID – If you are using the integration with Microsoft Dynamics GP Bank Reconciliation, enter the Checkbook ID of the GP checkbook you use for this credit card’s payment transactions.

  • For Gift certificate products: Is it a Tracked Gift Certificate – Set this option to Yes .

Note

Gift certificates usually will not be set up for you during the implementation of your UX Online system. If your organization issues gift certificates to members or non-members to use as payment toward an invoice, you must have a payment product to manage the accounting information for the Gift Certificate payment in an invoice.

    • For Transfer products: Is it a Transfer Product – Set this option to Yes.

    • For Refund products: Is it a Refund Product – Set this option to Yes.

Note

If the Is it a Refund Product option to Yes , the system will display an alert message if you attempt to create a refund transaction for a customer when there are existing unpaid invoices for the same Bill To ID. The alert message is informational only; you can still create the refund transaction.

    • For Write-off products: Is it a Write-off Product – Set this option to Yes .

    • For Adjustment products: Is Adjustment – Set this option to Yes .

    • For Miscellaneous Unapplied Payment products: Checkbook ID – If you are using the integration with Microsoft Dynamics GP Bank Reconciliation, enter the Checkbook ID of the GP checkbook you use for miscellaneous unapplied payment transactions.

The fields in the Description section do not apply to payment products; however, you may enter descriptive text in the Description field.

In the Web section, the only field that applies to a payment product is the Publish to Web field that is used with Protech’s MX Online. It will be set as needed during that implementation. Do not change these settings.

Click Save & Close to save this record and return to the Active Products View. Close the View window by clicking the “ X ” in the upper right hand corner of the window.

Defining a default transfer payment product

For clients working in a single company/single currency environment that have multiple transfer payment products, UX Online supports the ability to define the default transfer product. This feature is enabled through application parameter settings described below in Configuration Setup Required.

By entering the transfer payment product code as the Config value in the existing PAPaymentTransfer.ProductNumber application parameter, UX will use this transfer product to create invoice detail for transfers during Renewal Billing Overpayment Processing, Advertisement Insertion Billing, and the Invoice Transfer Payment process.

Note

An active, valid transfer product code is required in the PAPaymentTransfer.ProductNumber parameter when using the application parameter setups for this feature. If UX cannot find the transfer product entered as the Config value, payments will not be transferred.

Configuration Setup Required

Application Parameter Name

Config Value Settings for this Feature

Description

PAPaymentTransfer.ProductNumber

[default transfer payment product code]

Enter the default Payment Transfer Product Number used for transferring the payment from one invoice to another invoice.

Required if PAMultiCurrency.Enable = false (or NULL) AND PAMultiCompany.Enable = false (or NULL).

PAMultiCurrency.Enable

false (or NULL)

Set value = false or leave NULL to indicate that the system is not enabled for multi-currency.

PAMultiCompany.Enable

false (or NULL)

Set value = false or leave NULL to indicate that the system is not enabled for multi-company.

Note: This new application parameter was added to support this feature. There is no other logic associated with this parameter.

Payment transfer logic for Overpayment Processing, Advertisement Insertion Billing and Invoice Transfer Payment has been modified to use the default transfer payment product when:

  • the Config value in the existing PAMultiCurrency.Enable parameter = false (or NULL) AND

  • the Config value in a new PAMultiCompany.Enable parameter = false (or NULL).

If both of these conditions are not met, the system will ignore the default transfer product and will randomly select the transfer product to use.

If both of these conditions are met, but the system cannot find a transfer product that matches the Config value in the PAPaymentTransfer.ProductNumber parameter, or if no Config value has been set, no transfer will be processed.

Note

This configuration does not affect selection of the transfer payment product for pledge installment billing. UX Online will continue to use the transfer product identified in the monetary pledge setup.

Chapter 4: Multicurrency Setup

If your organization needs to enter transactions in more than one currency, you can set up your UX Online system to support as many currencies as necessary. Any Microsoft Dynamics CRM or UX Online transaction – opportunities, quotes, orders, and invoices – as well as records such as payment products and price lists can use any of the currencies you have set up in your system. You can view information in reports, Advanced Find lists, and by exporting information to Microsoft Office Excel in those currencies as well.

This chapter outlines the information that must be set up to enable your system to use multiple currencies.

Note

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

Enabling multicurrency

In order to use the multicurrency features of UX Online, the PAMultiCurrency.Enable parameter must be set to the correct value.

In addition, you may need to change how batch control amount validation works, depending on your business practices. You can set up UX Online to require that the total net amount of the payment transactions in a batch must match a control amount entered for the batch. This batch control amount is entered in the Control Amount field on the Batch Log record. If the total amount of the transactions does not match the amount in the Control Amount field, you will not be able to close the batch. (For more information, see Batch controls overview.)

However, if your organization allows multiple currencies in a single batch, the system will not be able to perform this kind of validation, and you must disable this by changing the PABatch.ValidatePaymentControl parameter. If your organization does not allow multiple currencies in a single batch, you do not need to change the PABatch.ValidatePaymentControl parameter.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

To enable multicurrency for your system, in the Navigation Tile Bar , select the Administration work area > UX Settings > UX Online Application Parameters . This View opens in a new window. Locate and open the parameter PAMultiCurrency.Enable.

Set the Config Value field to the method that your organization uses:

  • TRUE – Allows UX Online to perform multicurrency transaction processing and manage single currency sales product, meeting, and exhibit invoice transactions.

  • FALSE – Use a single currency for all transaction processing.

Click Save & Close to save your change and close this record.

If your organization allows multiple currencies in a single batch, you must also disable the system default for validating payment control amounts in a batch. Locate and open the parameter PABatch.ValidatePaymentControl . Set the Config Value to False.

Click Save & Close to save your change and close this record. Because the list opened in a new window, click the “ X ” in the upper right hand corner of the window to close it.

Currency records

If your organization uses the multicurrency features of UX Online, you will have a number of currencies defined in your system.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

Base currency – Whether or not your organization uses multicurrency, it will have a base currency, which is used for financial statements and is the currency that all other currency values are based on. Your base currency was defined during your server setup process and cannot be changed.

Transaction currencies – Your system will also have a currency record for each of the currencies that you perform transactions in, including your base currency. To view a list of your existing currency records, in the Navigation Tile Bar , select the Administration work area > Business Management > Currencies . Double-click a record to open and view the details.

These currency records include the following information:

  • Currency code – This is the ISO approved code for the currency.

  • Currency precision – Displays the decimal precision – should equal 2 .

  • Currency symbol – The system displays the appropriate symbol for the currency code. This can be changed if necessary.

  • Currency name – The system displays the appropriate name for the currency code. This can be changed if necessary.

  • Exchange rate – Displays the exchange rate (based on the base currency). Leave blank or enter 1, regardless of the currency exchange rate. Currency exchanges are not managed within UX Online.

Important

If your UX Online system is integrated with your accounting system, work with your Protech representative to manage exchange rates in the accounting system. Currency exchange is not managed in UX Online.

New currency records can be created individually, or you can import several currencies at once. For more information, contact your Protech representative.

Accounting Currency

If your system is integrated with the Dynamics GP accounting system, you must link the currency codes in UX Online with the corresponding accounting system currency IDs. To view existing currency code/currency ID links and to set up new links, in the Navigation Tile Bar , select the Administration work area > UX Settings > Accounting Company and Charts of Account Settings > Accounting Currency to open the Active Accounting Currency View. This View opens in a new window . Double-click a record to view the details.

These accounting currency records include the following information:

  • Currency – Displays the UX Online currency code.

  • Accounting Currency Code – Displays the corresponding accounting system currency ID.

Close the View window by clicking the “ X ” in the upper right hand corner of the window.

Currency-based price lists

In order to create transactions in different currencies in UX Online, your system must include price lists for each currency you use. For example, assume that your organization has three basic price structures, one for members, one for non-members, and one for students. In addition, you need to enter transactions in US dollars and Euros. Assuming US Dollar is your base organizational currency, you will need to have six price lists:

  • Member

  • Non-member

  • Student

  • Euro Member

  • Euro Non-member

  • Euro Student

Each of these price lists will be linked to a currency, and the price records in the price list will be in that currency. Each product and renewal benefit rate must have a price record in each of the price lists. When you create a new product or renewal benefit rate, UX Online automatically creates a price record for the product or renewal benefit rate in each price list. You will need to revise these price records after creating the product or renewal benefit rate. For more information, see Price Lists.

To support currency/price level logic when creating a new invoice in a multicurrency environment, you must also configure the many-to-many price level relationships within each price list record. If you add a currency and a price list for that currency, you will need to add the relationship. For more information, see Price lists many-to-many relationships.

Setting user currency preferences

Each UX Online user can set their preferred currency. The system uses this preferred currency as the default currency when you create new account and contact records. For example:

  • New account records – When a user creates a new account that has no parent, the system will enter the user’s preferred currency in the Currency field, and the non-member price list for that currency in the Price Level field. (If the account has a parent account record, the new record will inherit the parent’s currency and price list.)

  • New contact records – When a user creates a new contact that has no parent, the system will enter the user’s preferred currency in the Currency field, and the non-member price list for that currency in the Price Level field. (If the contact has a parent account or contact record, the new record will inherit the parent’s currency and price list.)

If you do not select a preferred currency, then your organization’s base currency will be used as the default currency.

To set your user preferred currency, in the Top Navigation Toolbar, select the Settings gear > Options to open the Set Personal Options . Click the General tab.

In the Select a default currency section, select the currency you will use most of the time when creating new records.

Click OK to save your changes and close the window.

Currency display settings

There are a number of settings that control how the system will display currency amounts, including the number of decimal places, whether the system will use a currency code or symbol, and where the currency code or symbol will appear before or after the currency amount.

Warning

This setup information was configured during your UX Online system deployment. Do not change this setup information without consulting with your system administrator and your Protech representative.

To view these settings, in the Navigation Tile Bar , select the Administration work area > Administration > System Settings . The System Settings window opens.

Note

You must have System Administrator rights to view these settings.

On the General tab of System Settings , view the following currency display settings:

  • Currency Precision – This is number of decimal places that the system will use for displaying currency amounts. This value must be set as 2.

  • Currency Display Option – This indicates whether the system will display currency amounts with the currency symbol or a currency code. This value should be set to Currency Symbol.

On the Format tab of System Settings , view how CRM displays number, currency, time, short date, and long date.

Click OK to close System Settings.

Managing single currency sales products, meetings and exhibits

UX Online offers clients working in a multi-currency environment (PAMultiCurrency.Enable = true), the option to limit invoice transactions to those where there is a match between the invoice currency and the currency defined in the setup for a sales product, meeting or exhibit. This logic is managed by the Single Currency field value in the respective setup record(s).

When a sales product, meeting, or exhibit setup is flagged as single currency (Single Currency = true), UX Online only creates price records for the price list/currency for currency defined in the sales product, meeting or exhibit setup. When creating an invoice transaction for a sales product, meeting or exhibit where Single Currency = true in the respective setup, UX logic limits transactions to those where the setup currency matches the invoice currency. This means, for example, that the client whose meeting setup is flagged as single currency, UX Online will only allow meeting registration transactions for that meeting in a the meeting setup currency.

When a sales product, meeting, or exhibit setup is not flagged as single currency (Single Currency = false), UX Online creates a price record for each price list/currency that is set up for the organization, without regard to the currency defined in the sales product, meeting or exhibit setup. When creating an invoice transaction for a sales product, meeting or exhibit where Single Currency = false, UX will find the price list where there is a match to the invoice price list/currency and create the transaction without limitation.

Setup record Single Currency defaults

  • Sales Product Setup – the single currency setting is defined in the sales product setup using the Single Currency attribute in the product record. By default, the Single Currency value = false (unchecked). To invoke single currency product sales transaction controls, the value for Single Currency must be changed to = true (checked) before you save the setup record.

  • Meeting Setup – the single currency setting is defined in the meeting setup. By default, the Single Currency value = true in the meeting setup (checked). All related meeting setups (i.e., registrations, sessions, etc.) will inherit these values automatically. To remove single currency controls and allow setup for all price lists/currencies in the organization, the value for Single Currency in the meeting setup must be changed to = false (unchecked) before you save the setup record.

  • Exhibit Setup – the single currency setting and currency are defined in the exhibit setup. By default the Single Currency value = true in the exhibit setup. All related exhibit product setups (booth, rep, misc exh product, cancel fee, etc.) will inherit these values automatically. To ignore single currency controls and allow setup for all price lists/currencies in the organization, the value for Single Currency in the exhibit setup must be changed to = false (unchecked) before you save the setup record.

Invoice price list/currency and single currency transactions

When creating a new invoice, the invoice inherits the price list and currency of the invoice customer. If appropriate, a user can modify the price list/currency before the initially saving the invoice or initiating a new transaction. Once saved, these fields are locked and no longer available for edit in the invoice.

To accommodate single currency controls, UX manages sales product, meeting and exhibit transactions based on whether or not there is existing invoice detail in the invoice. In other words, UX first determines whether the transaction is the first or a subsequent transaction, as described below.

First invoice transaction

When a user creates the first invoice transaction, if the selected sales product, meeting or exhibit setup is flagged as single currency and there is not a match between the setup currency and the invoice currency, the user receives an alert that the selected transaction is not available for the invoice currency and that the invoice currency and related price list will be updated.

Upon saving the transaction, UX will automatically update the invoice currency and price list to match the setup currency for the selected sales product, meeting, or exhibit. The change is visible to the user after refreshing the invoice record and only occurs on the first invoice transaction.

Subsequent invoice transactions

If invoice detail exists in an invoice, and a user creates a subsequent invoice transaction:

  • If the setup for the selected sales product, meeting or exhibit is flagged as a single currency and there is not a match between the setup currency and the invoice currency, UX returns an alert that the selected transaction product is not available for the invoice currency. The user can exit the transaction or make another selection. The user cannot create a subsequent sales product, meeting or exhibit transaction if Single Currency = true in the respective setup and there is no match to the invoice currency.

  • If the setup for the selected sales product, meeting, or exhibit is not flagged as a single currency, UX will find the respective price record for the invoice currency and price list, and create the transaction.

Invoice Payments and Adjustment Transactions

As is the case with all payment and adjustment transactions, only payment and adjustment product setups (including credit card setup) that match the invoice currency are available for selection. This is standard logic for all multi-currency environments.

.

Chapter 5: UX Online Security

The security features of UX Online control what actions users can perform, and what areas of the application they can access.

This information includes the following topics:

Security overview

UX Online incorporates both Microsoft Dynamics CRM Security Roles and UX Online Menu Roles to grant users’ access to those features of UX Online they need to perform their job functions and to restrict them from those areas that do not support their job function.

During implementation, Protech will work with you to define the specific security roles and menu roles required for your users.

Security roles set the privileges and access levels a user has for the entities in specific areas of UX Online. For more information, see UX Online security roles .

Menus roles control the menu choices that appear for users, and the types of invoice transactions they can create and process. UX Online includes two types of menu roles:

  • Administrator – grants users access to the setup menu for a module

  • User – grants users access to the specific transaction types for a module

For more information, see UX Online menu roles .

Security roles and menu roles work together, and users must have both types assigned to them. For example, if a user has either the CRM4M Advertising Administrator or CRM4M Advertising User menu role assigned to them, they must also have the related CRM4M Advertising security role assigned to them as well.

Important

All users must have the CRM4M Core security role in order to access UX Online.

Do not make any changes to the default security roles or menu roles deployed with your system.

UX Online security roles

Security roles are used to simplify assigning the privileges and access levels to users. (Privileges are the types of action that a user can perform on the records within an entity. Access levels control what level of the organization that a privilege applies to. For more information, see About privileges and access levels .) Rather than setting up each individual user with the privileges and access levels that they need, these privileges and access levels are already set in pre-defined security roles.

For example, the CRM4M Advertising security role defines the privileges and access levels for entities in the Advertising module. If you assign this security role to users, then all of the pre-defined privileges and access levels in the CRM4M Advertising security role will apply to those users. For instructions on assigning security roles to users, see Assigning security roles to a user .

The following security roles are deployed with UX Online:

  • CRM4M Advertising

  • CRM4M Core

  • CRM4M Exhibits

  • CRM4M Fundraising

  • CRM4M Professional Development

  • CRM4M Speaker Facility

  • CRM4M Subscriptions

  • CRM4M System Customizer

Note

Your system will also include some security roles that are part of the base Microsoft Dynamics CRM deployment.

If your organization needs additional security roles, you can create new ones by copying any existing security role and modifying the copy as needed.

Important

Do not make changes to any of the default security roles listed above.

About privileges and access levels

Security role records in UX Online manage the privileges and access levels that users in each role have.

Privileges

Privileges are the types of action that a user can perform on the records within an entity. For example, you could create a role that has the Read privilege for the Account and Contact entities, but that does not have the Create or Write privilege (that is users in this role can view account and contact records, but cannot add, modify, or delete them).

Privileges include the following actions:

  • Create – Add a new record.

  • Read – View a record. (Some UX Online processes use this privilege.)

  • Write – Edit an existing record. (Some UX Online processes use this privilege.)

  • Delete – Delete a record. (Some UX Online processes use this privilege.)

  • Append – Attach another entity or associate another entity with the record. This works in conjunction with ‘Append To’.

  • Append To – Attach another entity or associate another entity with the record. This works in conjunction with ‘Append’.

  • Assign – Change a record’s owner to a different user.

  • Share – Share a record with another user or team.

  • Enable/Disable – Activate or deactivate records. This privilege appears only on the Business Management tab of the “Business Unit” and “User” entities.

Not all privileges apply to every entity.

Access levels

Access levels control what level of the organization that a privilege applies to. Dynamics CRM allows you to set up a security model that is based on your association’s structure. The hierarchy of the structure includes the organization at the top level (that is, the company that owns the deployment), with business units, that is, a logical grouping of business operations, below it. If necessary, a business unit can be the “parent” of any number of “child” business units. (A child business unit can also be a parent business unit.) The lowest level of the hierarchy is the user.

Note

Microsoft Dynamics CRM also allows organizations to group users in teams, which can be used to help share records.

Each of these levels in the organizational hierarchy is tied to an access level, and the access level in turn uses the ownership of a record to determine who can do what with the record. The access levels included are:

  • User – Only the user who owns a record can perform the action on that record, unless the owner has shared the record with a team or with other users.

  • Business Unit – Any user who is in the same business unit as a record’s owner can perform the action on that record.

  • Parent – Child Business Unit – Any user who is in the parent business unit of a record’s owner can perform the action on that record.

  • Organization – Any user in the organization can perform the action on records in the entity, regardless of the owner.

For example, assume that the organizational hierarchy includes four levels: the organization, a parent level of business units, one child level of business units, and users. The default security role CRM4M Core has all of the privileges for the Account entity set to the Organization access level, which means that any user in the organization who is assigned that security role can create, read, write, delete, append, append to, assign, or share an account record. However, the privileges for the User entity are set to Business Unit, which means that a user in this role must belong to the same business unit as a record’s owner before they will be allowed to perform any actions on the record.

UX Online menu roles

Menu roles control the UX Online menus available to users, and the types of invoice transactions they can create and process. UX Online includes two basic types of menu roles: Administrator roles, which grant access to specific setup and process menu options for a module; and User roles, which grant access to specific transaction types on invoices and selected menu options.

For example, users who have the CRM4M Advertisement Manager menu role assigned to them will be able to navigate to the UX Online Advertisement Manager menu. Users who have the CRM4M Advertisement User menu role assigned to them will be able to create and process advertising transactions on invoices. For instructions on assigning menu roles, see Assigning menu roles to a user .

Access granted by default security roles and related menu roles

The following table identifies access granted through the security roles and the related Administrator and User menu roles included in UX Online:

Security role Menu role Access
CRM4M Core CRM4M Accounting Administrator Administration work area > UX Settings

  • Credit Cards
  •  Promotions
  •  Account prefix
  •  State Codes
  •  Source Codes
  •  UX Online Application Parameters
  •  Lockbox Setup
  •  Tax Rates
  •  Country Codes
  •  Titles
  •  Melissa Data Bulk Address Validation

Financial work area > Accounting Manager

  •  Batch Management
    •  Batch Log Manager
    •  Standard GL Detail – Post to Accounting
    •  Special GL Detail – Post to Accounting
  •  Credit Card Payments Delayed Capture Process
  •  Gift Certificates
  •  Restore Meeting and Exhibit Product GL Accounts
  •  Cash Reconciliation
  •  Accounting Company and Chart of Accounts Setup
    •  Global Setup Default
    •  Accounting Companies
    •  Chart of Accounts
    •  Accounting Currency Code
    •  Chart of Accounts Refresh Control
    •  Start Accounting Refresh Job

Financial work area > Payment Processes

  •  AutoPay Processes
    •  AutoPay Invoices
    •  AutoPay Renewal Invoices
    •  AutoPay for Monetary Pledge Installments
    •  AutoPay for Recurring Gift Installments
    •  Re-authorize Payment Demographics
  •  Lockbox Management
    •  Lockbox Import
    •  Lockbox Data View
    •  Lockbox Processing

Product Sales work area > Product Sales

  •  Validate Product Price List Items
CRM4M Core   CRM4M Advertising CRM4M Advertisement Administrator Advertising work area > Advertisement

  •  Advertisement Settings
    •  Advertising Ad Size
    •  Advertising Publications
  •  Advertisement Insertion Process
CRM4M Advertisement User Allowed invoice transactions

  •  Advertisements
CRM4M Core CRM4M Chapter Administrator Membership work area > Chapters

  •  Chapter Settings
    •  Chapters Setup
    •  Regions Setup
    •  Territory Zip Code X-Ref
    •  Titles
  •  Chapter Manager
    •  Update Members Chapter Territory
CRM4M Core CRM4M Committee Administrator Membership work area  > Committees/Rosters

  •  Committee Manager
    •  Committees
    •  Titles
CRM4M Core   CRM4M Exhibits CRM4M Exhibits Administrator Events work area > Events

  •  Event Settings
    •  Industry Product Categories
    •  Industry Products
CRM4M Exhibits User Allowed invoice transactions

  •  Exhibits
CRM4M Core   CRM4M Fundraising CRM4M Fundraising Administrator Fundraising work area > Fundraising

  •  Contribution and Pledge Setup
  •  Pledge Installment Invoice Generation
  •  Recurring Gift – Invoice Generation
CRM4M Fundraising User Allowed invoice transactions

  •  Contributions
CRM4M Core CRM4M Meeting Administrator Events work area > Events

  •  Event Settings
    •  Event Setup
    •  Event Badges and Tickets
    •  Location
  •  Bulk Meeting Registration Cancellation
CRM4M Meeting User Allowed invoice transactions

  •  Meetings

Events work area > Events

  •  Event Meeting Waitlist View
  •  Event Session Waitlist View
  •  View Event Participants
CRM4M Core CRM4M Membership Administrator Membership work area > Membership/ Subscriptions

  •  Renewal Billing Settings
    •  Step One: Prorate Table
    •  Step Two: Installment Schedule
    •  Step Three: Renewal Benefit
    •  Step Four: Renewal Package
    •  Price Level Member X-Ref
  •  Renewal Manager
    •  Generate Renewal Billing Invoices
    •  Renewal Process Log
    •  Re-calculate Benefit Recipients
    •  Renewal Overpayment Process
    •  Renewal Billing Termination Process
CRM4M Membership User Allowed invoice transactions

  •  Membership Dues
  •  Benefit Packages
CRM4M Core CRM4M Menu Administrator Administration work area > History Store

  •  History Store Settings
CRM4M Core CRM4M Payment User Allowed invoice transactions

  •  Payments and Adjustments

Financial work area > Payment Processes

  •  RapidPay
    •  RapidPay Payments
    •  Create Payments
CRM4M Core CRM4M Product Sales Administrator Product Sales work area > Product Sales

  •  Product Sales Settings
    •  Product Setup
    •  Warehouses
    •  Freight
    •  Prices
  •  View and Edit Backorders
  •  Backorder Processing
  •  Order Shipping Fulfillment View
CRM4M Product Sales User Allowed invoice transactions

  •  Product Sales
CRM4M Core   CRM4M Professional Development CRM4M Professional Development Administrator Education work area > Professional Development

  •  Professional Development Settings
    •  Categories
    •  Certification Awards
    •  Courses
    •  Programs
  •  Certification Renewal Process
  •  Validate CEU’s Fulfillment
  •  Certification Termination Process
  •  Mass Load Attendees
CRM4M Professional Development User Allowed invoice transactions

  •  Professional Development
CRM4M Core CRM4M Promotion Package Administrator Events work area > Promotion Packages
CRM4M Promotion Package User Allowed invoice transactions

  •  Promotion Package
CRM4M Core CRM4M Roster Administrator Membership work area  > Committees/Rosters

  •  Roster Manager
    •  Group
    •  Rosters
    •  Roster Member Utility
CRM4M Core   CRM4M Speaker Facility CRM4M Speaker Facility Administrator Events work area > Speakers & Facilities

  •  Speaker Facility Settings
    •  Facility Specialty Types
    •  Facility Items
    •  Speaker Specialty Types
    •  Speaker Specialty Setup
CRM4M Core   CRM4M Subscriptions CRM4M Subscription Administrator Membership work area > Membership/ Subscriptions

  •  Subscription Manager
    •  Galley Utility
    •  Galley View
    •  Galley Run Log
CRM4M Subscription User Allowed invoice transactions

  •  Subscriptions
CRM4M System Customizer This role is identical to the CRM ‘System Customizer’ role; however, it does not have the ability to import managed solutions. The ‘CRM4M System Customizer’ security role is the most privileged role that should be given to a designated user in the PCBS shared environment.

 

Assigning security roles to a user

You can assign the security roles to users to give them the necessary privileges and access levels for the activities they perform in UX Online.

Note

Security roles must be used in conjunction with menu access roles to grant users access to the areas of UX Online they need. For example, if you assign the CRM4M Core and CRM4M Advertising security roles to a user, but do not assign them either the CRM4M Advertisement Administrator or the CRM4M Advertisement User menu roles, they will not be able to navigate to the Advertising menus, nor will they be able to select the Advertisements option on the invoice New Transactions menu.

In the Navigation Tile Bar , select the Administration work area > Security > Users . In the Users list, locate and open the user record where you want to assign security roles.

In the Navigation Pane of the user record, click Security Roles . A list of the security roles assigned to the user appears.

Click Manage Roles on the List View toolbar . The Manage User Roles dialog appears. Mark the checkbox next to each security role that you want to assign to this user. Clear the checkbox next to any role that should not be assigned to this user.

Click OK to close the dialog.

Click Save & Close.

Managing user menu roles

You can manage user menu roles to grant or remove access to menu items and available invoice transaction types. (For more information, see UX Online menu roles.)

Note

Menu roles must be used in conjunction with security roles to grant users access to the areas of UX Online they need. For example, if you assign the CRM4M Advertisement Administrator menu role to a user, but do not assign them the CRM4M Advertising security role, they will be able to navigate the Advertising menus, but they would not be able to make any changes to the entities in the Advertising module.

To manage menu roles for a single user, in the Navigation Tile Bar, select the Administration work area > Security > Users. In the Users list, locate and open the user record where you want to assign menu roles. In the Navigation Pane of the user record, click UX Menu Roles to open the CRM4M User Role Associated View listing of the menu roles assigned to the user.

Click the Manage UX Roles button on the List View toolbar. The Manage User Menu Roles dialog opens. The roles currently assigned to the user are marked with a checkbox . Unassigned menu roles are not checked. Click to mark the checkbox  next to each unmarked menu role that you want to assign to this user. Click a checked role to remove the mark in the checkbox next to each menu role that you want to remove from this user. Click OK in the dialog to process your changes and return to the CRM4M User Role Associated View. Click Save & Close on the user record.

To manage menu roles for multiple users, in the Navigation Tile Bar, select the Administration work area > Security > Users. In the list of Enabled Users, click to select one or more user records where you want to assign the same set of menu roles.

Click the Manage UX Roles button on the List View ribbon toolbar to open the Manage User Menu Roles dialog. When more than one user is selected in the list of Enabled Users, no menu roles in the dialog will be checked. Click to mark the checkbox  next to each menu role that you want to assign to all users selected in the list of Enabled Users. Click OK in the dialog to process your changes.

About creating new security roles

If your organization needs additional security roles, you can create new ones.

Important

Do not make changes to any of the default security roles that were deployed with your system.

You can use two different methods to create a custom security role:

  • Copy an existing security role and modify the privileges and access levels of the copy.

  • Create a new security role.

Copy an existing security role

In the Navigation Tile Bar , select the Administration work area > Security > Security Roles to open list of the existing security roles.

Click the security role you want to copy to open the record. In the More Actions button on the security role Record toolbar , Copy Role . The Copy Security Role dialog opens.

Enter a name for the new security role.

Note

We recommend that you add the acronym for your organization at the beginning of the name.

Mark the Open a new security role when copying is complete checkbox , then click OK .

The Role record will appear, showing the new role you created. It will have all the same settings as the role that you copied. Make the necessary changes to the role’s privileges and access levels. (For more information, see Modifying privileges and access levels for a new security role .) Then click Save & Close .

Create a new security role

In the Navigation Tile Bar , select the Administration work area > Security > Security Roles to open list of the existing security roles.

On the List toolbar of the security roles list, click New . In the Role record, enter a name for the new security role.

Note

We recommend that you add the acronym for your organization at the beginning of the name.

Mark the necessary settings for this role’s privileges and access levels. (For more information, see Modifying privileges and access levels for a new security role .) Then click Save & Close .

After modifying and saving the new security role, you can assign it to your users. For more information, see Assigning security roles to a user .

Modifying privileges and access levels for a new security role

You can modify the privileges and access levels for a security role that you have created to control the UX Online entities that users in that role can manipulate.

Important

Do not make changes to any of the following default security roles deployed with your system. For more information, see UX Online security roles .

The entities and the privileges and access levels are grouped on the Role record on several tabs related to the different functional areas within UX Online.

In the Navigation Tile Bar , select the Administration work area > Security > Security Roles to open list of the existing security roles.

Locate and open the new security role you created. In the Role record, click the tab that includes the entities where you want to set privileges and access levels.

Locate each entity that you want to modify, and then click the circle under each privilege where you want to modify the access level. As you click the circle, the setting advances through each access level, as shown in the following table:

Symbol

Access Level

No users in this role can perform this action.

Only the user who owns a record can perform the action on that record, unless the owner has shared the record with a team or with other users.

Any user who is in the same business unit as a record’s owner can perform the action on that record.

Any user who is in the parent business unit of a record’s owner can perform the action on that record.

Any user in the organization can perform the action on records in the entity, regardless of the owner.

Note

Not all access levels apply to every privilege for an entity. As you click on a privilege, only those access levels that are available will appear.

If the tab displays any miscellaneous privileges, modify the access levels as needed for this role.

Click the next tab that includes entities and miscellaneous privileges that you need to modify, and repeat steps to modify privileges and access levels as needed.

Click Save & Close when you have finished modifying privileges and access levels for this role.

Creating a new menu role

You can create a new menu role and then associate it with the UX Online menus that you want users in the new role to have access to.

Note

Menu roles must be used in conjunction with security roles to grant users access to the areas of UX Online they need. If you create a new menu role, you must have a corresponding security role.

After creating a menu role, you must associate it with UX Online menu or submenu that you want users in this role to have access to. For more information, see Associating a menu role with a menu item .

In addition, you must assign this role to the appropriate users. For more information, see Assigning menu roles to a user . New menu roles are created through Advanced Find.

On the Top Navigation Toolbar, select Advanced Find to open a new query window. In the Look for entity drop down, select Menu Roles.

In the Advanced Find toolbar, s elect New.

In the Menu Role record, enter a name for this new role.

Note

We recommend that you add the acronym for your organization at the beginning of the name to differentiate the new menu role from roles deployed with UX Online.

Click Save & Close to return to the Advanced Find results .

Associating a menu role with a menu item

After creating a menu role, you must associate it with the menu items that you want users in this role to access. For example, assume that you have created a menu role to give some users access to certain menu items in the Accounting Manager (Navigation Tile Bar > Financial Manager work area > Accounting Manager). You will need to select each of the menu items that you want these users to be able to access.

Important

You cannot associate a menu item with more than one menu role.

Before you begin, you must be logged in as a user with the CRM4M Menu Administrator menu role.

Navigate to the menu that you want to associate with the menu role. For example, if you want to associate the role to some menu items in the Accounting Manager, in the Navigation Tile Bar , select the Financial Manager work area > Accounting Manager . Each menu item will have a Menu Edit icon by them. Click the icon for the first item you want to associate with the role.

The Menu Item window opens. Click the Lookup button on the Security Role field to select the menu role that you want to control access to this menu item.

Click Save to save your changes.

Basic Procedures

Part 2: Basic Procedures

This information describes the UX Online interface and some basic procedures that apply throughout the product.

This information is divided into the following chapters:

  • Chapter 6: UX Online User Interface

  • Chapter 7: Advanced Find and Saved Views

  • Chapter 8: Sending E-mail in UX Online

  • Chapter 9: Invoices

  • Chapter 10: Account and Contact Record Maintenance

  • Chapter 11: History Store

  • Chapter 12: Audit History

Chapter 6: UX Online User Interface

This chapter describes the basics of the user interface terminology used to navigate within Microsoft Dynamics CRM and UX Online. As a first step to learning this application, reading this documentation will help you understand how to move around the system and take advantage of the standard UX Online capabilities.

Additional resources, such as those found in Explore CRM, which is available to all users opening the application, are also very helpful.

This information includes the following topics:

  • Top Navigation Toolbar

  • Navigation Tile Bar

  • List View Toolbar

  • Record Toolbar

  • Record Navigation Pane

  • List Views

  • Required fields

  • Navigation in a sub-grid

Top Navigation Toolbar

The Top Navigation Toolbar appears on all pages in CRM 2016.

Features include:

  • Main menu – Selecting the Main menu icon will expand to display the Navigation Tile Bar of work areas

  • Shortcut to recent views and records

  • Add activities such task tasks, email, and appointments

  • Global Search – With Global Search, you can run a simple query across multiple entities. Enter a simple term such as a last name and the query will now search for results multiple entities. UX Online is deployed with Global Search configured for the account, contact, invoice, and batch log entities.

  • Advanced Find

  • Settings – Selecting Settings > Options will open the Set Personal Options window

Navigation Tile Bar

When you select the Main menu on the Top Navigation Toolbar , UX Online displays the Navigation Tile Bar . This bar displays a tile for each of the main work areas in the site map. The CRM work area contains navigation to less frequently used CRM settings and functions. The Administration work area contains navigation to UX settings and functions and more frequently used CRM settings and functions.

The remaining work areas are specific to UX Online modules and contain navigation to UX sub-areas unique to that work area. Navigation to area-specific dashboards and to all contacts, accounts, reports, invoices, and invoice details are available in every UX Online area except Administration.

Main work area tiles include:

  • CRM

  • Financial Manager

  • Membership

  • Events

  • Product Sales

  • Education

  • Fundraising

  • Advertising

  • Administration

List View toolbar

The List View toolbar displays the command buttons shown across the top of the List View window. These buttons are contextual. In other words, they may vary depending on the entity in which you are working and whether or not you have selected a record. They may also vary depending on the user’s security roles.

Using the contacts window as an example, common command buttons with no record selected may include:

  • New

  • Delete

  • Email a Link

  • Run Report

  • Excel Templates

  • Export to Excel

  • Import Data

  • Chart Pane

  • View

The ellipses at the end of the List View toolbar display infrequently used additional options.

Again, using the contacts window as an example, common buttons with a record selected may include:

  • New

  • Edit

  • Activate

  • Deactivate

  • Delete

  • Merge

  • Send Direct E-mail

  • Add to Marketing List

  • Assign

The ellipses at the end of the List View toolbar when a record is selected display many additional options specific to the selected record.

Record toolbar

The Record toolbar replaces the Ribbon toolbar in earlier versions of CRM and displays the command buttons shown across the top of an individual record. These buttons also are contextual and vary based on the type of record and the user’s security settings.

Using a contact record as an example, the Record toolbar command buttons include:

  • Save

  • Save & Close

  • New

  • Address Validation

  • New Invoice

  • Copy Address

  • Deceased

  • Deactivate

  • Connect

The ellipses at the end of the Record toolbar display additional options specific to the record type.

Record Navigation Pane

From within any record with related entities, the Navigation Pane provides access to related records specific to the record type that you are working with. This pane is hidden until you select the caret (‘ ’) next to the record name on the Top Navigation Toolbar. The related records that appear vary depending on the type of record you are viewing.

Using a contact record as an example, the Navigation Pane of related entities is shown below when selecting the caret next to the contact record name:

List Views

List Views are used in many places within UX Online to display several records sequentially. For example, the Roster Members list view displays the accounts and contacts that are assigned to a roster, the Committee Members list view displays the contact records that are assigned to a committee, and the Contacts list view displays all contact records in the database.

Some List Views open in a new window, while others open in the same CRM window. You will need to close List Views that open in a new window by clicking the “ X ” in the upper right hand corner of the window. Use navigation in the Top Navigation Toolbar to navigate List View that open in the same CRM Window.

List Views that open in a new window include the following searching and sorting capabilities:

  • Search and View

  • Column sorting

List Views that open in the same CRM window include the following searching and sorting capabilities:

  • Search and View

  • Alphabet Bar

  • Column sorting

Look For and View Filters

The Look For and View filters appear at the top of each list view window.

  • The Search filter allows you to enter partial or complete information about the records you are searching for. You may also use a wildcard (*) to broaden your search.

  • The View filter allows you to pick from a list of pre-defined system views and custom views to display a list of records.

All entities come with standard system views that cannot be modified. (For example, the Committee Members list includes views to show Active Committee Members, Current Members, Inactive Committee Members, Members Elect & Nominees, and Past Members.) However, you can create your own custom views and add them to a list, making them available to all users. You can also create personal views just for yourself. These are called My Views and will only appear for you. To learn more about creating custom views, see Advanced Find and Saved Views .

Personalize your default view

If there is a system or custom personal view of records that you access frequently, you can set that view as the default view for displaying records. For example, if you have created a personal view of all contacts in New York named “NY Contacts” that you work with regularly, you can set that view as your default each time you navigate to Contacts.

To set the default view, first select the “NY Contacts” view to open the list of selected records. At the top of the page, click the “Push Pin” icon next to the View Name. Once “NY Contacts” is set as your default view, each time you return to Contacts, the system will display the records from your default view.

Alphabet Bar

The Alphabet bar is available at the bottom of List Views that open in the same CRM window, such as accounts, or contacts. Click on a letter to view a list of records that begin with that letter.

Directly above the alphabet bar, the number of records being displayed in the view is shown. To view more records in a list, you may use the Page arrows provided in the lower, right hand corner of this list view. If no arrows are activated, then there is only one page of data that matches your search on the view you are working with.

Column sorting

You can change the order of a list by clicking on the column headings. For example, you can sort the Committee Members list by the member name, the committee, the members’ titles, or by their term dates. Click the column heading once to sort in ascending order, and click again to sort in descending order.

Note

Although column sorting is available on almost all of the lists in UX Online, there are a few lists where this feature is not available, such as the RapidPay Payment Entry list.

If a column displays data from a related entity, column sorting is not available.

Required fields

UX Online records frequently have required fields, that is, fields that you must enter information in before you can save the record. For example, when you are creating a new invoice, you must select at least a customer and a price list in the invoice header before you can save the invoice. You can leave the other fields in the invoice header blank, but you will not be allowed to save the invoice until you have entered valid data in the required fields— Customer and Price List .

These required fields are marked with a red asterisk.

Navigation in a sub-grid

If there is a sub-grid on the record, you may see a + or list icon at the top of the grid. These icons provide quick navigation access in lieu of accessing the information through the Navigation Pane. Selecting the + icon allows you to create a new record for that sub-grid entity. Selecting the list icon takes you directly to the associated view for that sub-grid entity.

Chapter 7: Advanced Find and Saved Views

In UX Online, you can use different views anywhere you work with a list of records. For example, in the Contacts list, you can use different views to display only active contacts, inactive contacts, your active contacts, etc. Besides the pre-defined system views, you can create your own customized views to show the information that meets your specific needs.

This information includes the following topics:

  • Saved views overview

  • Creating a saved view

  • Modifying a saved view

  • Using your saved view

  • Deleting a saved view

Saved views overview

A view is a filter applied to a list of records. Users can choose different views that contain all the records or activities of a particular type or that are a subset of that type. For example, the Contacts list includes pre-defined views to show all active contacts, your active contacts, and inactive contacts.

There are two types of views: System Views and My Views .

System Views are pre-defined in UX Online, and include any custom System Views created by your system administrator in the client-specific solution package.

My Views are views that you create and save, using Advanced Find. Advanced Find is a search tool you can use to find specific records in UX Online, using extensive search criteria. For example, you can find records by account name, city or region, and the name of the salesperson responsible for the account.

Creating views specific to your needs helps you find the information that you frequently need. When you create or customize a saved view, you are creating a query to search the UX Online database for the specific information you want. For example, you could create a view for the Contacts list that shows active contacts in a specific state.

The area where a saved view appears is based on the type of query defined for the view. For example, when you create a saved view for a committee list, this view will only appear on the View menu of the Committee Members list. When you create a saved view for contact records, this view will only appear on the View menu of the Contacts list.

After you create and save a view, you can customize it by adding or removing columns, rearranging columns, modifying the search conditions, or changing the sorting order.

You can always access any of your saved views using the Saved Views tab on the Advanced Find window.

Creating a saved view

When you open the Advanced Find query window, the default search conditions that appear depends on what list and what view you were using when you clicked Advanced Find . For example, if you are using the Active Contacts view on the Contacts list, the search conditions for that view appear in Advanced Find . You can add more search conditions to the existing query, or you can create a completely new query from this view.

On the Top Navigation Toolbar , click the Advanced Find button to open the Advanced Find query window.

Hint

To create a saved view based on a system view or another saved view, navigate to the list that includes that view and select it from the View menu, and then click Advanced Find .

If you want to create a saved view without using any of the default search conditions, click New . This will clear all search conditions.

  • Click the Look for menu and select the type of data. For example, you can create a view that shows contacts that fit specific criteria. In addition, if you want to base your new view on an existing view, select it in the Use Saved View list.

  • Click Select to begin defining the search conditions for this view. A list appears, displaying all the fields available for searching based on the data type you selected in the Look For field. Select the field that contains the information you want to search in your view. For example, you can select ‘Address 1: State/Province’ to display a list of contacts based on their state.

  • The next option that appears is the search condition—the default condition is Equals . Click this field to select the search condition you want to use for the selected field. For example, if want the saved view to display contacts in a specific state, you would select Equals .

  • Click the Enter Value field to specify the information you want to look for. Based on the field and condition selected, you can either enter the value. If a Lookup button appears, you can click it to select existing values defined for that field. (The Lookup button may not appear, depending on which field you selected.)

  • To add more search conditions, repeat steps 6 through 9.

  • To remove search conditions, click the down arrow next to the search conditions row, and select Delete .

You can group two or more search conditions into logical and OR statements. To do so, click the down arrow next to the first search conditions row you want to group and select Select Row from the menu. Select the next row you want to group, and then click either the Group AND or the Group OR button. For example, to view contacts from a group of states, you could add search conditions for each of the states and group them using the Group OR button.

When you finish defining the search conditions for your saved view, click Save As .

Enter a name for your saved view, and click OK . Your view will be available on the Use Saved View drop-down in Advanced Find , or on the View menu when you are viewing a list that shows the record you selected in the Look For list.

Now that you have your conditions defined, you can further customize your view by adding and arranging columns and defining how you want the data sorted. For more information, see Modifying a saved view .

Modifying a saved view

You can modify any of your saved views in any of the following ways:

Adding columns to a saved view

Click the Advanced Find button on the Top Navigation Toolbar . Then, in Advanced Find , click the Use Saved View drop-down. Select the saved view you want to modify.

  • Click Edit Columns on the Advanced Find query toolbar to open the Edit Columns window.

  • Click Add Columns .

For each field you want to see on your view, select that checkbox . You may select more than one at a time. If you select too many columns to display, a message will appear. You can clear the checkbox of any columns you want to remove from the view to make room for the new ones. When you add a new column to a saved view, it is automatically positioned as the last column.

Click OK in the Add Columns window to save the new columns, and then click OK in the Edit Columns window to close.

Moving columns in a saved view

Click the Advanced Find button on the Top Navigation Toolbar . Then, in Advanced Find , click the Use Saved View drop-down. Select the saved view you want to modify.

  • Click Edit Columns on the Advanced Find query toolbar to open the Edit Columns window.

  • Click the column heading and use the green arrow keys to move the column left or right.

When you finish rearranging columns, click OK in the Edit Columns window to close.

Removing columns from a saved view

Click the Advanced Find button on the Top Navigation Toolbar . Then, in Advanced Find, click the Use Saved View drop-down. Select the saved view you want to modify.

  • Click Edit Columns on the Advanced Find query toolbar to open the Edit Columns window.

  • Click the column heading of the column you want to remove. This will outline the selected column heading in green.

  • Click Remove on the Common Tasks pane.

When you finish removing columns, click OK in the Edit Columns window to close.

Change a saved view’s sort order

Click the Advanced Find button on the Top Navigation Toolbar . Then, in Advanced Find , click the Use Saved View drop-down. Select the saved view you want to modify.

  • Click Edit Columns on the Advanced Find query toolbar to open the Edit Columns window.

  • Click Configure Sorting in the Common Tasks pane.

  • In the Configure Sort Order dialog, select the column you want to use for sorting your view. Select whether you want the data to sort in either ascending or descending order.

Click OK to save your new sort order, and then click OK in the Edit Columns window to close.

Change column width in a saved view

Click the Advanced Find button on the Top Navigation Toolbar . Then, in Advanced Find , click the Use Saved View drop-down. Select the saved view you want to modify.

  • Click Edit Columns on the Advanced Find query toolbar to open the Edit Columns window.

  • Select the column you want to modify. This will outline the selected column heading in green.

  • Click Change Properties in the Common Tasks pane. Select the length you want for the column selected.

Click OK in the Change Column Properties dialog, and then click OK in the Edit Columns window to close.

Hint

You may need to experiment with the column widths to get the best arrangement. You can select a width and then go to the area where your view will be and see what it looks like. If you want it wider or narrower, return to the Advanced Find window and continue modifying your saved view until it meets your needs.

Change a saved view’s name and description

Click the Advanced Find button on the Top Navigation Toolbar . Then, in Advanced Find , click the Use Saved View drop-down. Select the saved view you want to modify.

Click Edit Properties on the Advanced Find query toolbar . Enter the new name and description for the saved view.

Click OK to save your changes.

Using your saved view

Saved views are available in the area of CRM that pertains to the main CRM entity used in the search conditions of your saved view. The following are some examples of where a saved view can be found based on the type of search used for the saved view:

  • A saved view that searches by Contacts are available within CRM Contacts area

  • A saved view that searches by Accounts are available within the CRM > Accounts area.

  • A saved view that searches by Invoices are available within the CRM > Transactions area.

My Views

Saved views automatically appear in the My Views section of a list’s View menu.

Deleting a saved view

You can delete one of your own saved views at any time.

On the Top Navigation Toolbar, click Advanced Find . Click the Saved Views button on the Advanced Find query toolbar.

To display a list of all Saved Views for all records or for one specific record type, click the Record Type drop down and select. Based on your Record Type selection, this will display a list of Saved Views.

Select the saved view you want to delete from the list of saved views. Click Delete Saved View .

A message opens asking you to confirm that you want to delete the saved view. Click OK .

Chapter 8: Sending E-mail in UX Online

You can send an e-mail from anywhere in UX Online that the Send Direct E-mail button appears on a toolbar or menu, whether you are viewing a single record or a list of records. You can send a message to a single contact or account record, to all contacts or accounts on a list, or to a selected subset of contact or account records.

Using Quick Campaigns for an e-mail activity from Advanced Find queries on the contact entity makes it easy to create a list of e-mail recipients for a mass e-mail. The same concept applies to account records. Composing the e-mail message in Quick Campaigns is much the same as composing a message in Outlook.

This information includes the following sections:

  • UX Online e-mail overview

  • Sending e-mail to a list of contacts using Quick Campaigns

  • Sending e-mail to a single contact

  • Sending e-mail to committee and roster members without a template

UX Online e-mail overview

When you send e-mails from Dynamics CRM, whether you select one or hundreds, a record of that message is saved with each contact record, giving you a history of the times you have communicated with them. Dynamics CRM also keeps track of any incoming replies to your messages. It is also sent to your normal Outlook inbox for convenience.

You can view e-mail responses from either Outlook or UX Online whichever is convenient at the time. You can select any e-mail in your Outlook inbox to be tracked in UX Online and linked to any type of record.

If you add a recipient to a message who does not have an e-mail address or if the Contact Methods: E-mail option is set to Do Not Allow on their contact record, a warning message will display.

You can send e-mail to several contacts using Microsoft CRM Send Direct E-mail, Quick Campaigns, Workflows, and Mail Merge. Send Direct E-mail requires an e-mail template. If your e-mail includes a file attachment, it must be part of the template. “On the Fly” emails (no template) to several contacts are available using Quick Campaigns, but they do not support file attachments.

You can send an e-mail with a file attachment “on-the-fly” to several committee or roster members without a template using UX Send E-mail functionality that is available on toolbar for Committee and Roster Member views.

Sending e-mail to a list of contacts using Quick Campaigns

In this example, we show how to send an e-mail to contacts whose primary mailing address is in the state of Maryland using Quick Campaigns. For managing other Microsoft CRM mass e-mail options, please refer the Dynamics CRM Help.

Note

The Advanced Find query must originate from the contact, account, leads, or opportunity entities.

From any UX work area on the Navigation Tile Bar, click Contacts . Select Advanced Find from the Top Navigation Toolbar.

Create a query from the Contact entity > Address1 State or Province = MD > Status = Active, Email address1 contains data. Click Results on the toolbar to display a list of all active contact records with a primary e-mail address and where the primary address state = MD. If appropriate, select one or more of the contact records that should receive the e-mail.

  • To select a single record, click once on that record.

  • To select multiple records, hold down the Ctrl key as you click on each record.

  • To select all records in a view, select the checkbox located on the column-heading row.

Once you have selected the records you want, click Quick Campaign on the Records Window toolbar . From the button drop-down, make your record selection.

  • Selected records

  • All records on the current page

  • All records on all pages

This launches the Quick Campaign wizard. Enter a descriptive name for the Quick Campaign such as “Email to Maryland Residents” and select Next.

In the Quick Campaign Activity Type and Owner window, select E-mail as the Activity type and select the owner of this activity.

Select whether the system created e-mail activities should be sent immediately and marked closed.

  • Check this box if you want Dynamics CRM to send the email immediately. This is the default setting.

  • Uncheck this box if you want do not want to send the email immediately. The e-mail activity status will be Draft in the Quick Campaign and the activity will be available in your Workplace Activities until you open each e-mail activity and Send.

Click Next.

In the Specify Activity Content page, you have the option to use an e-template or compose the e-mail message.

  • When composing an email message, enter a subject and the message content.

  • When using a template, use the Lookup to select the template and enter a subject.

Note

If you need to send your e-mail message with a file attachment, you must use a template when sending an e-mail using Quick Campaigns.

Click Next to review a summary of the Quick Campaign. The summary displays the name of the campaign, the number of records, the activity type, and activity owner.

Click Create to create the Quick Campaign and create the e-mail activities. Dynamics CRM immediately creates the e-mail activities for all of the contacts you selected.

To view your Quick Campaign and the completed activities, in the Navigation Tile Bar, select the CRM work area > Marketing > Quick Campaigns. Select your campaign to view the status of the campaign, the e-mail messages sent, e-mail responses, contacts selected, and contacts excluded. A copy of the completed e‑mail activity also is saved under Closed Activities within each contact record.

Note

Contacts where the contact communication preferences do not allow e-mail or do not allow bulk e-mail will be excluded from the Quick Campaign results.

Sending e-mail to a single contact

You can send e-mail messages to a single contact directly from their contact record. From the Navigation Pane of the contact record, click Activities .

Click Add New Activity on the List toolbar and select E-mail as the activity type. A new e-mail message record will open in a new window with this contact’s name appearing in the To field.

Enter the e-mail subject and body as you normally would. You can also use an e-mail template or attach files.

Click Save if you want to add an attachment. When you are done, click Send on the Record toolbar. If there is no attachment, click Send on the toolbar to send immediately. The e-mail will be saved in the Closed Activities.

To send the e-mail later, enter a Due Date and click Save & Close. The e-mail will remain in the Activities folder and the owner’s Workplace until it is sent.

Note

If the e-mail could not be sent to the contact due to an invalid e-mail address or no e-mail address in their record, upon Save, you will see a Communications Error warning at the top of the e-mail message window. You will also receive a notice about the failure to deliver the message in your Outlook inbox.

Sending an e-mail to committee and roster members without a template

You can send an e-mail “on the fly” to one or more committee or roster members without using a template. This is a UX feature and is available through the Send E-mail button on the List toolbar of Committee and Roster Member views.

The maximum number of records (e-mail recipients) is limited to the number of records displayed on your view. (The number of records displayed in a list is controlled by your Personal Settings. The maximum value for this setting is 250.)

In this example, we show how to send an e-mail to several roster members using Send E-mail. From the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Roster Members.

From the list of roster members, select one or more roster member records that should receive the e-mail message.

Click the Send E-mail button on the List toolbar to open a new e-mail activity message form.

Complete the message header fields, as follows:

  • From – defaults to the user

  • To – defaults to the selected recipient records

  • Subject – enter a subject for the e-mail

Note

UX will automatically filter to exclude selected records that do not have an email address or where the record is flagged Do Not Email. They will not populate the ‘To’ area of the e-mail message form. There is no warning message.

Complete the message content as you would with any e-mail activity. Click Save to save the message. If an e-mail address does not exist or Do Not Email is flagged for one or more recipients, the system returns an alert.

Note

This feature does NOT honor the Do Not Bulk Email setting. There is no alert if Do Not Bulk Email is flagged in a recipient’s record.

If you have a file attachment, click Attach File on the e-mail Record toolbar to open the Manage Attachment window.

Note

The Attach File button is not enabled on the message toolbar until you first save the message.

Use the Browse button to look for and select the file to be attached. Select Attach to attach the file. Select Close to continue.

Once the e-mail message is complete, click Send to send the message immediately or click Save & Close to save the message in your workplace to send later. A copy is also available in each recipient’s Activities.

Note

Sending an e-mail from the Roster or Committee Members view does not store the e-mail activity in the roster or committee member record. It is stored in the recipient’s contact or account record as an Activity (e-mail not yet set) or as a Closed Activity (e-mail sent).

Chapter 9: Invoices

UX Online relies on the CRM invoice entity form for creating invoice records in UX Online. Sometimes confused with report output, the CRM invoice is the actual transaction record. For example, when you add new members or renew memberships, enter new subscriptions, or register attendees for meetings, you will enter the details for these transactions in an invoice record.

Regardless of the type of transaction, much of the information you enter in the invoice record will be the same, and the basic procedure will be the same for creating a new invoice record.

This chapter is divided into the following sections:

  • Invoice record elements

  • Batch overview

  • Creating an invoice and entering basic invoice information

  • Viewing and editing invoice address information

  • Using Alternate Ship To and Bill To addresses

  • Invoice administration information

  • Creat ing transaction details

  • Viewing invoice totals

  • Adding a comment to an invoice

  • Proforma invoices

  • Adding custom text to invoice report output

  • Invoice detail type codes

Invoice record elements

All UX Online transactions include the following record components:

Record toolbar – Located across the top of the invoice record, the Record toolbar provides additional buttons that manage additional UX Online functionality for the invoice. These include:

Summary section – Located on the left side of the invoice record, the Summary section contains the data specific to the transaction such as Invoice Number, Date, Customer, Tax Exempt, Bill To Account or Bill To Contact, Name, Promotion, Price List, Currency, Proforma, and Source Code. See Creating an invoice and entering invoice header information. See also, Viewing and editing invoice address information.

Transactions Area – Located to the right of the Summary section contains the following:

  • Actions toolbar – Located at the top of the Transactions grid, this area contains buttons for Cancel and Update Sales Rep.

  • Transactions Grid – Displays the details of the actual commerce transactions, payment transactions, and freight charges. Comments added to an invoice are also displayed here.

  • Invoice totals – Displays a summary of the invoice detail line items, as well as any calculated tax, the amounts paid, and the balance due.

Addresses Area – Located below the Summary section. The address data is populated upon Save or when adding the first New Transaction. Like the address data in an account or contact record, invoice addresses are composite address fields. The invoice includes the following address components:

  • Bill To Address

  • Ship To Address

Activities and Notes – displays existing Activities or Notes. Click NoteS to add a new note. Click ACTIVITIES to create a new activity.

Footer – displays the user who created this record, when it was created, the user who last modified the record, when it was last modified, and the status reason. See Invoice Footer Information .

Batch overview

Before you begin entering invoices, you need to understand how batches are used in UX Online, as well as your organization’s policies and procedures regarding the entry of cash, check, or credit card payments.

In UX Online, each invoice transaction must be assigned to batch, which is a control mechanism that assigns an ID and date to every invoice transaction entered into the system. In most organizations, each batch is closed at the end of the business day so no other transactions can be entered into it and the accounting department can reconcile the currency amounts entered into that batch with the daily bank deposit.

Note

You must be in an open batch in order to enter or open invoice detail.

Once the batch is reconciled, the batch is then posted to an accounting system such as Microsoft Dynamics GP or Dynamics SL, if your organization integrates with an accounting system. If your organization does not integrate with a third party accounting system, then the batch is simply posted within UX Online and reports can be run for manual entries to your general ledger. For more information about creating and posting batches, see Integration with General Ledger .

Some organizations use two working batches per day; one for web transactions and one for back office transactions. Other organizations prefer to create batches by department, for example, one for meetings, one for membership dues, and so forth.

Although UX Online requires separate batches for certain processes such as dues renewal billing and revenue recognition, your organization can incorporate whatever batch requirements best support your daily workflow. Whatever batch rules you set up, you will need to confirm them with your accounting department and the UX Online project lead within your organization.

Creating an invoice and entering invoice basic information

The Summary section along the left side of the invoice record contains basic information about the invoice. The Transactions section to the right contains the list of invoice transactions; and the totals provide a summary of transaction detail amounts, discounts, taxes, payments, and the balance due.

You will enter some of the information in the invoice Summary; other fields display information from other records or are populated automatically by UX Online.

For related topics, see:

This procedure illustrates creating an invoice and entering general invoice header information beginning from a contact record. You can also begin the process of creating an invoice from an account record or from the Invoices list ( any UX work area > Invoices ). If you begin from a contact or an account record, some of the information – such as the basic customer information – will be entered for you. Regardless of where you begin, the basic procedure will be the same.

From any of the UX work areas on the Navigation Tile Bar, click Contacts . Open the contact record where you want to create an invoice. On the Record toolbar of the contact’s record, click New Invoice .

Click Select Batch to select the appropriate open batch based on your organization’s business rules. For information about batches, see Batch overview .

Note

You must be in an open batch in order to enter or open invoice detail. If you are not in an open batch, a warning message directs you to select a batch. If you already are in an open batch, confirm that you are working in the correct batch.

After selecting or confirming your working batch, Save the invoice to auto populate the Invoice ID and address information fields. You also select New Transactions and begin creating transactions. This action will also auto populate the Invoice ID and address information fields in the new invoice. For more information, see Creating invoice transactions .

At the top left of the Summary section, enter and view basic information about the invoice, as described below:

  • Invoice ID – This field is blank until you select Save or select New Transactions, when the system assigns a unique invoice record ID.

  • Invoice Date – This field is blank until select a batch, when it displays the Batch Date. If you are already in a working batch, this field displays the batch date.

  • Customer – If you are creating a new invoice from an account or customer record, this field displays the name from that record. (Typically, you would not change this unless you started by creating a new invoice in the wrong contact record.) If you are creating a new invoice from the Invoices list, click the Lookup button to select the account or contact record.

  • Name – This field refers to the invoice name; when you first create an invoice, it displays “New.” When you Save the invoice, this field displays the transaction type in the invoice, for example, Product Sales . If the invoice contains transactions from more than one UX Online application, then this field displays each of the pertinent transaction types, separated by commas.

  • Bill To Contact – Displays the name of the contact responsible for payment of this invoice. If the customer does not have a parent contact, this field displays the name from the Customer field. If the customer has a parent contact, and the Bill To Parent option is set to Yes on the customer’s record, this field displays the name of the parent contact record. If necessary, you can click the Lookup button to select a different contact to bill this invoice to.

  • Bill To Account – Displays the name of the account responsible for payment of this invoice. If the customer does not have a parent account, this field displays the name from the Customer field. If the customer has a parent account, and the Bill To Parent option is set to Yes on the customer’s record, this field displays the name of the parent account record. If necessary, you can click the Lookup button to select a different account to bill this invoice to.

Important Note

Each invoice must have either a Bill To Account or a Bill To Contact. It cannot have both. UX Online does not support issues resulting from the absence of either a Bill To Account or a Bill To Contact in the invoice header.

  • Tax Exempt – Displays the tax exempt number from the account or contact record in the Bill To Account or Bill To Contact field. (If the customer has a tax exempt number, but the Bill To account or contact does not, this field will be blank.) If a number is entered here, sales of taxable items in the invoice are tax exempt. You can type a different tax exempt number if necessary; however, your entry here will not update the customer’s record or the Bill To customer’s record.

  • Price List – Displays the price list defined for the invoice customer. Pricing for all invoice transactions is based on the invoice Price List. Price List works in conjunction with the invoice currency. Only price lists associated with the invoice currency are available. If necessary, click the Lookup button to change the Price List for this invoice.

  • Currency – Displays the customer’s currency. If necessary, you can click the Lookup button to select a different currency for this invoice. Changing the invoice currency will update the invoice Price List. If necessary, click the Lookup button to change the Currency for this invoice.

  • Source Code – If necessary, click the Lookup button to select the source code for this invoice. (This is typically an organization code to identify marketing efforts that contributed to the invoice transaction.)

  • Promotion – If necessary, click the Lookup button to select the promotion code for this invoice. Any promotion you enter here will apply to eligible invoice detail line items that you add to the invoice. For more information, see Promotion records .

Note

If you are entering a promotion code in the invoice, you must select the promotion code before the initial save of your invoice so that eligible invoice detail line items can inherit the promotion code.

  • Proforma – If you want to flag this as an official quote rather than an actual invoice, select this checkbox . You can only mark an invoice as Proforma when you first create it; you cannot change a saved invoice to Proforma. For more information, see Proforma invoices .

Important

If you change the Proforma option to Yes , the system will not perform any calculations for inventory control and back order processing, and you will not be able to enter any payment transactions. In addition, any batch assignments will be removed, and no General Ledger or Accounts Receivable detail will be generated for the invoice detail line items.

  • Status Reason – UX Online automatically sets the invoice status to Ready for Close. If you are not finished working with the invoice, you must change the Status Reason to Hold manually. Hold Indicates that this invoice transaction is not complete and not ready to be posted. For instance, you could use this status when you are working in an invoice and need to leave the transaction before you are finished. When you return to the invoice, finish the transaction, you must manually change the status to Ready for Close. UX Online does not prompt the user to select or confirm a status reason. You cannot close a batch containing invoices where the Status Reason = Hold.

  • Owner – This is the user who created this invoice record.

  • Click Save to save the invoice summary information with your selected batch.

Viewing and editing invoice address information

The composite addresses are not populated until you either Save the invoice or add a New Transaction to the new invoice. You can view the billing and shipping address information for an invoice in the left side Addresses section of the invoice form. If necessary, you can modify the address information by selecting the composite address field and making changes to the individual composite field elements. You can also validate the address by clicking on the Address Validation button on the invoice Record toolbar. Any changes you make apply only to the invoice, and will not update the customer’s record. See Validating invoice Bill To and Ship To addresses for more information.

By default, both the Bill To Address and the Ship To Address are composite fields that will already display some name and address information, either from the customer’s record, or from the customer identified in the Bill To Contact or Bill To Account field in the invoice header. This documentation assumes that neither the customer nor the Bill To are using alternate Bill To or Ship To addresses. See Creating alternate Ship To and Bill To Addresses for more information.

To view the bill to address information, open the invoice, and scroll down to BILL TO in the left side Addresses section. This area displays the following information:

  • Bill To Name – Displays the address name of the primary address record of the customer in the Bill To Account or Bill To Contact field in the invoice header. Note that this is not the name of the account or contact record, but the Address Name of the primary address for the Bill To record.

  • Bill To Attention – If the invoice Bill To is a contact record, the system populates this field with the contact “Label Name” of the Bill To Contact record. If the invoice Bill To is an account record, the system populates this field with the “Label Name” of the primary contact of the Bill To Account record.

  • Bill To Address – the record displays a composite of the address elements. Select this field to display the composite address elements:

    • Street 1 – Displays the first street line of the primary address of the customer in the Bill To field on the General tab.

    • Street 2 – Displays the second street line of the primary address of the customer in the Bill To field on the General tab.

    • Street 3 – Displays the third street line of the primary address of the customer in the Bill To field on the General tab.

    • City – Displays the city of the primary address of the customer in the Bill To field on the General tab.

    • State/Province – Displays the state or province of the primary address of the customer in the Bill To field on the General tab.

    • Zip/Postal Code – Displays the postal code of the primary address of the customer in the Bill To field on the General tab.

    • Country/Region – Displays the country or region of the primary address of the customer in the Bill To field on the General tab.

  • Bill To Phone – Displays the main telephone number of the customer displayed in the Bill To field on the General tab.

  • Bill To Fax – Displays the main fax number of the customer displayed in the Bill To field on the General tab.

  • Bill To Email – Displays the main email address of the customer displayed in the Bill To field on the General tab.

To view the Ship To Address information, open the invoice, scroll down to SHIP TO in the left side Addresses section. This area displays the following information:

  • Ship To Name – Displays the name of the primary address of the customer record. It is important to note that this is not the name of the account or contact record, but the Address Name of the primary address for the Customer record.

  • Ship To Attention – If the Customer is a contact record, the system populates this field with the contact “Label Name” of the Customer record. If the Customer is an account record, the system populates this field with the “Label Name” of account’s primary contact.

  • Ship To Address – The record displays a composite of the address elements. Select this field to display and/or edit the composite address elements.

    • Street 1 – Displays the first street line of the invoice customer’s primary address.

    • Street 2 – Displays the second street line of the invoice customer’s primary address.

    • Street 3 – Displays the third street line of the invoice customer’s primary address.

    • City – Displays city of the invoice customer’s primary address.

    • County – Displays the county of the invoice customer’s primary address.

    • State/Province – Displays the state or province of the invoice customer’s primary address.

    • Zip/Postal Code – Displays the zip or postal code of the invoice customer’s primary address.

    • Country/Region – Displays the country or region of the invoice customer’s primary address.

  • Phone – Displays the primary telephone number of the customer on the General tab.

  • Fax – Displays the primary fax number of the customer on the General tab.

  • Email – Displays the primary email address of the customer on the General tab.

  • Shipping Method – Leave this field blank. If you calculate freight on the invoice, the system will update this field with the selected shipping method.

Using alternate Ship To and Bill To addresses

When you create an invoice, by default, the system populates the information on the Bill To Address and Ship To Address in the Addresses section on the invoice in one of two ways:

  • If the customer’s record does not have the Bill To Parent option marked, the system uses the customer’s primary address for both the Bill To Address and Ship To Address tabs.

  • If the customer’s record has the Bill To Parent option marked, the system uses the customer’s primary address for the Ship To Address tab, and the parent customer’s primary address for the Bill To Address tab.

However, you can configure your system so that it will use customer addresses other than the primary address for the Bill To Address and Ship To Address of new invoices. These alternate customer addresses are maintained in More Addresses in the account or contact record. Configuring a change to use alternate addresses is managed by the following UX Online Application Parameters:

  • PAInvoice.BillToAddressType.Default

  • PAInvoice.ShipToAddressType.Default

After setting these application parameters, if any of your customers have an additional address marked as address type Bill To or Ship To, that address will be used on new invoices for those customers. For information on configuring your system to use alternate Bill To and Ship To addresses, see Configuring your system to use alternate Bill To addresses and Configuring your system to use alternate Ship To addresses .

Important Note

The Addresses view in an account or contact record displays additional addresses for the account or contact – those addresses in addition to the primary and secondary address. When the application parameters are configured to use this feature, the system looks for additional address records with an address type of Bill To or Ship To where the address number is greater than 2. It ignores address 1 or address 2 (primary and secondary address). If no additional address can be found, the system will use the default address as described above.

For more information on marking additional addresses as Bill To or Ship To, see Creating alternate billing and shipping addresses .

Configuring your system to use alternate Bill To addresses

You can configure the system to use an alternate Bill To address in your transactions in lieu of the primary address of the invoice Bill To Account or Bill To Contact by modifying the Config value of the PAInvoice.BillToAddressType.Default application parameter.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters. This list opens in a new window. L ocate and open the parameter PAInvoice.BillToAddressType.Default .

Set the Config value field to Bill To. (If you leave the value of this field blank, the system will use the Bill To Account or Bill To Contact record primary address on an invoice.)

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “ X ” in the upper right hand corner of the window to close it.

Configuring your system to use alternate Ship To addresses

You can configure the system to use an alternate Ship To address in your transactions in lieu of the primary address of the invoice customer by modifying the Config value of the PAInvoice.ShipToAddressType.Default application parameter.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters. This list opens in a new window. L ocate and open the parameter PAInvoice.ShipToAddressType.Default .

Set the Config value field to Ship To. (If you leave the value of this field blank, the system will use the invoice customer’s primary address on an invoice.)

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “ X ” in the upper right hand corner of the window to close it.

Invoice footer information

The footer section of an invoice provides information about the invoice record – who created the record, when it was created, who last modified the record, and when it was last modified.

Creating invoice transactions

When you create a new invoice, the system will add a separate invoice detail line item for each individual transaction on the invoice. For example, if you are recording an invoice for a customer’s meeting registration, you will create a meeting transaction, resulting in an invoice detail line item for the meeting registration. If you are creating a payment, you will create a payment transaction, resulting in an invoice detail line item for the payment. Each invoice transaction type has a specific invoice detail type code that is useful when search for invoices that contain a particular transaction type through Advanced Find. For a list of invoice detail type codes, see Invoice Detail Type Codes below.

The New Transactions button on the Record toolbar is used for creating transactions for dues, meeting registrations, contributions, etc., as well as for creating payment transactions.

Note

You cannot add invoice detail line items until you have selected a batch for the invoice.

To create a transaction, click New Transactions on the invoice Record toolbar.

From the drop-down, select the type of transaction you want to enter. Each transaction type uses a different transaction entry form. Depending on your security role settings, the available invoice transaction types may include:

Viewing invoice totals

Invoice Totals are displayed directly below the Transaction section of the invoice record. These fields display the total amounts for the invoice transaction detail. These fields are managed by the system and cannot be changed.

  • Detail Amount – Displays the sum of the charges for all invoice transaction detail items.

  • Total Discount – Displays the sum of the discounts for all invoice transaction detail items.

  • Total Tax – Displays the total tax due for all taxable products contained in the invoice transaction detail items.

  • Total Amount – Displays the sum of the detail amount, less discounts, plus tax, for all invoice transaction detail items.

  • Total Payments – Displays the sum of all payment invoice transaction detail items.

  • Balance Due – Displays the result of the Total Amount less Total Payments.

Adding a comment to an invoice

You can add a comment to any invoice to add any information or notes that are necessary. There are two types of comments available: invoice comments, which will appear on SRS invoice report output, and packing ticket comments, which will appear on SRS Packing ticket reports.

Before you can add a comment to an invoice, your system must have comment products set up—one for invoice comments and one for packing ticket comments. For more information, see Creating an invoice comment product .

Note

You must be in an open batch before you can add new or open existing invoice detail transactions.

Open the invoice where you want to add a comment. Click New Transactions on the invoice Record toolbar and select Comments from the menu.

In the Comments record, enter or select the invoice comment product. Enter the comment you want to add to this invoice or to the packing ticket.

Click Save & Close to save this comment and return to the invoice.

Proforma invoices

Proforma invoices are frequently used to provide customers with a quote of what specific products would cost if they placed an order. If you have marked an invoice as being Proforma, you can add only product sales line items and invoice comments. You can also calculate freight charges, but you will not be able to enter any payments. Proforma invoices are not posted to general ledger, and no GL detail will be created for any of the line items.

To create a Proforma invoice, create a new invoice, and enter the invoice basic information. Mark Yes on the Proforma option before you save the invoice and before you select New Transaction. For more information, see Invoices .

Note

You must mark Yes on the Proforma option before you save the invoice or select New Transaction. You cannot create a standard invoice and then change it to a Proforma invoice.

If the customer decides they want to purchase the items on a Proforma invoice, you can convert it to a standard invoice. For more information, see Converting a proforma invoice to a standard invoice .

Converting a proforma invoice to a standard invoice

If a customer decides they want to purchase the items on a Proforma invoice, you can convert it to a standard invoice, rather than re-entering the information on a new invoice.

If your association uses inventory control, and you convert a Proforma invoice, any items that are out of stock and available for back order will automatically be marked for backorder on the converted invoice.

Note

If you convert a Proforma invoice that includes a line item for freight charges, you should recalculate the freight charges if any of the items are marked for backorder on the new invoice.

When you convert a Proforma invoice to a standard invoice, all of the line items will be associated with the batch you are currently working in. When that batch is processed to create GL detail and posted, the line items will have GL detail created. For more information, see Integration with General Ledger .

Locate the Proforma invoice and open it. If you have not already selected your batch, select the appropriate open batch.

Click Convert to Invoice button on the invoice Record toolbar . A message will appear, asking you to confirm that you want to convert this Proforma to an invoice. Click Yes .

Note

If the Proforma invoice includes more than 15 line items, it will take a few moments to convert to a standard product sales invoice.

After processing is complete, the invoice reappears, with the Proforma option changed to No . You can make any necessary changes to the invoice (such as adding a payment line item, calculating freight charges, modifying the original line items, or adding new sales line items).

Click Save & Close .

Adding custom text to invoice report output

You can add custom text at the end of each invoice report based on invoice module. For instance, if you want to add “remit to” information to the meeting invoice, you can do so by entering the requisite text in the “Invoice Text” field in the meetings module form. Similarly, you can define different text for fundraising module invoice. The text entered in the module “Invoice Text” field will appear on the base invoice report and the base EasyPrint invoice report for that module.

Note

The amount of text you define can affect the layout of your invoice report. While the invoice text field accommodates multiple lines of text and up to 4000 characters, if you enter too much text, it is possible that it will force a second page to the report.

To define custom text by module, using the meetings module as an example:

Using Advanced Find, Look for Modules and select Results on the toolbar to display a list of modules. Open the Meetings module record.

In the Invoice Text field, enter the custom text that you want to appear on all UX Online base meeting invoice reports.

Click Save & Close to save the invoice text. Do not make any other changes to this module record.

Repeat these steps for each module where you want to add invoice text.

Note

You can add Invoice Text to all modules except the Accounts Receivable module. Module-specific invoice text will appear on base module-specific invoice reports (i.e., the UX Meeting Invoice). It will not appear on generic reports such as the UX Print Invoice report.

Invoice Detail Type Codes

Using Advanced Find, you can easily find all invoices that contain a particular invoice transaction based on the invoice detail type. For example, in Advanced Find, begin your search with the Invoices entity. Add a related search on Invoice Products and then search on Detail Type = [code]. Enter the detail type code based on the following transaction type cross-reference.

Module Transaction Type Invoice Detail Type Code
Advertising Ad contract 600000
Ad related charges 600001
Ad insertion 600001
Comments Invoice comment 500001
Exhibits Exhibit contract 700000
Booth 700001
Reps 700003
Misc products 700004
Exhibit cancel fee 700000 (same as contract)
Exhibit (cancelled) 7000010
Freight Freight charges 500000
Fundraising Monetary contribution 300001
Monetary pledge 300003
In kind contribution 300002
Auction win 300006
Recurring gift 300005
Meetings Registrations 200000
Guest registrations 200002
Sessions 200001
Cancel fee 200000 (same as registration)
Meeting Registration (cancelled) 200010
Membership Membership dues 100000
Chapter dues 100005
Membership Dues (cancelled) 100010
Membership Dues (upgrade/downgrade prorated detail) 100011
Membership Dues (partial cancellation) 100012
Benefit recipient charges Product Sales – not a membership detail type
Payments Payment 900000
Product Sales Product sales 500000
RMA product return 500005
Prof. Development Certification benefit 800000
Course 800001
Certification (cancelled) 800010
Certification (partial cancellation) 800012
Promotional Packages Promotion/Sponsorship Package 990000
Subscriptions Subscription benefit 400000
Subscription (cancelled) 400010
Subscription (upgrade/downgrade prorated detail) 400011
Subscription (partial cancellation) 400012

Chapter 10: Account and Contact Record Maintenance

This part of the documentation describes some of the procedures you will use to maintain features of your contact and account records that are specific to UX Online. (Many other contact and account record maintenance procedures use basic Microsoft Dynamics CRM features, and you can find information about these in the Microsoft Dynamics CRM documentation.)

This information includes the following topics:

Parent and child records

Each account record can have one parent account record, multiple child sub-account records, and multiple child contact records. Similarly, each contact record can have one parent (contact or account record) and multiple child contact records. The basis for these relationships is established when you assign an account record as the parent to an account record or when you assign an account or contact record as the parent to a contact record.

UX Online expands further on these parent/child relationships by allowing you to define whether the child should use the parent price level, share the parent primary address, or share the parent secondary address. Further, you can set the parent as the default Bill To Customer for all invoices created for the child record. These settings are managed on a record-by-record basis.

Note

Default values for new contact and new account records are based on the default value assigned to the respective fields in customization for the contact and account entities.

For more information, see Using parent price level, Sharing parent primary address, Sharing parent secondary address, and Billing the parent record.

Using parent price level

When an account or contact has a Parent record, you have the option for that child record to inherit the price level of its Parent record by setting the value for Use Parent Price Level to Yes. When the value for this field is set to Yes, the child record will inherit the parent record Price Level, Currency, and Member flag settings. As changes to the parent’s Price Level occur, these changes will automatically flow to the child record. As changes to the parent occur, these changes will automatically flow to the child record.

Changing the value from Yes to No in the child record does not automatically update these fields. Regular system updates to the child record’s Price Level are based upon the child record’s eligible primary renewal billing record (Primary = Yes, Cycle State = Current, Benefit Status = New, Renew, Reinstate), if one exists.

If you remove the Parent record, the value for Use Parent Price Level automatically reverts to No. If you subsequently add a Parent record and want to share the parent’s price level, you must manually set the value for Use Parent Price Level to Yes.

Important Note

If no eligible primary renewal billing record exists for the child record, then the child record’s Price Level and Member flag must be set manually.

Sharing parent primary address

When a contact has a Parent contact or account record, you have the option for that contact to inherit the primary address of its Parent record by setting the value for Use Parent’s Address to Yes. When set to share the parent’s primary address, the address information in the parent’s primary address will automatically update the child contact’s primary address data field. As changes to the parent’s primary address are saved, these changes will automatically flow to the child contact record. Changing the value from Yes to No will not update the primary address fields. You must manually edit the address fields, if appropriate.

When an account has a Parent account record, you have the option for that account to inherit the primary address of its Parent record by setting the value for Use Parent’s Address to Yes. When set to share the parent’s primary address, the address information in the parent’s primary address will automatically update the child account’s primary address data field. As changes to the parent’s primary address are saved, these changes will automatically flow to the child account record. Changing the value from Yes to No will not update the primary address fields. You must manually edit the address fields, if appropriate.

If you remove the Parent record, the value for Use Parent’s Primary Address automatically reverts to No. If you subsequently add a Parent record and want to share the parent’s secondary address, you must manually set the value for Use Parent’s Address to Yes.

Sharing parent secondary address

When a contact has a Parent contact or account record, you have the option for that contact to inherit the secondary address of its Parent record by setting the value for Use Parent’s Address to Yes. When set to share the parent’s secondary address, the address information in the parent’s secondary address will automatically update the child contact’s secondary address data field. As changes to the parent’s secondary address are saved, these changes will automatically flow to the child contact record. Changing the value from Yes to No will not update the secondary address fields. You must manually edit the address fields, if appropriate.

When an account has a Parent account record, you have the option for that account to inherit the secondary address of its Parent record by setting the value for Use Parent’s Address to Yes. When set to share the parent’s secondary address, the address information in the parent’s secondary address will automatically update the child account’s secondary address data field. As changes to the parent’s secondary address are saved, these changes will automatically flow to the child account record. Changing the value from Yes to No will not update the secondary address fields. You must manually edit the address fields, if appropriate.

If you remove the Parent record, the value for Use Parent’s Address automatically reverts to No. If you subsequently add a Parent record and want to share the parent’s secondary address, you must manually set the value for Use Parent’s Address to Yes.

Billing the parent record

When an account or contact has a Parent record, you have the option to set the parent as the default Bill To for all invoices created for that child record by setting the value for Bill To Parent to Yes.

If you remove the Parent record, the Bill to Parent setting automatically reverts to No. If you subsequently add a Parent record and want to bill that parent, you must manually set the value for Bill To Parent to Yes.

Creating alternate billing and shipping address records

When you create an invoice, by default, the system populates in the Bill To and Ship To address information on the invoice using either the customer’s primary address or the parent customer’s primary address. However, you can set up your system so that it will use additional addresses that have been marked as Bill To and Ship To addresses. (For more information, see Using Alternate Ship To and Bill To addresses .)

If your system is configured to use additional customer addresses on invoices, you will need to create or identify the existing additional addresses that you want to use as billing or shipping addresses.

Important Note

The More Addresses view in an account or contact record displays the additional addresses for the account or contact record. It does not display the primary (address 1) and secondary address (address 2) of the account or contact record. When the application parameters are configured to use alternate billing and/or shipping addresses, the system looks for additional address records with an address type of Bill To or Ship To where the address number is greater than 2. It ignores address 1 or address 2. If no additional address can be found, the system populates the Bill To and Ship To address information on the invoice using either the customer’s primary address or the parent customer’s primary address.

The primary (address 1) and secondary address (address 2) of an account or contact record are maintained from within the account or contact record. If you need to edit the address data for Address Number 1 or 2, you must do so within the account or contact record.

From any of the UX work areas on the Navigation Tile Bar, click Contacts or Accounts . For this example, click Contacts. Locate and open the account or contact record where you want to set up alternate billing and shipping addresses. In the Navigation Pane of the record, click Addresses .

If this contact already has an additional address record that you want to mark as their billing address (any address record where the address number is greater than 2), open that address record. If not, click the Add New Address button on the toolbar ; the New Address record will appear where you can enter the appropriate address information.

In the Address Type field, select Bill To . Click Save & Close to save and close the record.

Repeat steps for the address that you want to mark as the customer’s shipping address, if appropriate, by selecting Ship To as the address type.

Note

The attributes for managing address types for the primary and secondary address in the contact entity, the primary and secondary address in the account entity, and the address type in the address entity are distinct attributes with distinct option set values. Do not delete or edit these base options. You may add additional options through Customization in your client-specific solution package

Because the More Addresses view is based on the address entity, what appears as the address type for address 1 inside the contact or account record may differ from the address type for address 1 displayed in an Advanced Find on the Addresses entity. This will depend on the set up for option set values. Do not delete or edit the existing base options. You may add additional options through Customization in your client-specific solution package.

Copy Address

You can copy and paste an account or contact record’s primary address by selecting the Copy Address button on the Record toolbar.

This feature copies the following data elements for a contact record:

  • Prefix FirstName MiddleName LastName, Suffix

  • Contact Address Name

  • Contact Street 1, Street 2, Street 3

  • Contact City, State Zipcode

  • Contact Country

This feature copies the following data elements for an account record:

  • Primary Contact Prefix FirstName MiddleName LastName, Suffix

  • Account Name

  • Account Street 1, Street 2, Street 3

  • Account City, State Zipcode

  • Account Country

Communication preferences

In the Default Billing and Contact Preferences section of an account record or the Contact Preferences section of a contact record, you can specify the Contact Preferences for that record. These settings include:

  • Preferred (method of contact):

  • E-mail: Allow or Do Not Allow

  • Phone: Allow or Do Not Allow

  • Fax: Allow or Do Not Allow

  • Mail: Allow or Do Not Allow

  • Bulk E-mail: Allow or Do Not Allow

It is important to note that there is system logic associated with the E-mail and Bulk E-mail settings. If the preference for Email or Bulk Email is set as Do Not Allow, the record is not eligible for UX Online email and bulk email communications, respectively.

Updating a deceased contact’s records

If one of your contacts is deceased, there are several records that you should update, including roster and committee memberships, renewal billing records and invoices with a balance due or a credit balance. You can use the Deceased Contact Utility to update this information. This utility will perform the following actions:

  • Sets the price level to Non-Member and the Member flag updates to No on the contact record.

  • Deactivates roster memberships.

  • Updates current committee membership term end dates with the system date and deactivates nominee (future term) committee member records.

  • Updates current chapter officer term end dates with the system date and deactivates nominee (future term) chapter officer records.

  • Updates current region officer term end dates with the system date and deactivates nominee (future term) region officer records.

  • Terminates active renewal billing records as of the system date and enters a termination reason of “Deceased.”

The utility also identifies invoices with a balance not equal to zero and sends a task to the Deceased Contact queue for follow up action. These invoices must be dealt with manually.

We recommend that you cancel the dues invoice for the terminated renewal billing. If the invoice was paid, you can refund the credit to the deceased member’s estate or transfer the balance to an open invoice, depending on your organization’s business practices.

Note

The utility does not deactivate the contact’s record. If your organization’s business rules require that a deceased contact’s record should be deactivated, you must do that manually after you have resolved any remaining open invoices.

From any of the UX work areas on the Navigation Tile Bar, click Contacts . Locate and open the contact record.

Click the Deceased button on the contact Record toolbar to open the Deceased Contact Utility dialog.

Click the Queue Lookup button. In the Look Up Records dialog, select the Deceased Contacts queue, and then click OK .

Setting up Payment Demographics for automatic credit card payments

If you have members who want some of their invoices automatically paid by credit card (for either single payment-in-full invoices or installment payments), you must create a Payment Demographics record that includes the information that will be used during AutoPay processing.

For example, a contact might want to have their subscription renewal invoices automatically paid by credit card. Or, an account might want to have their exhibit invoices automatically paid by credit card.

When you create and save a Payment Demographics record, UX Online validates the credit card type and processes the credit card through Payflow Pro to obtain authorization and create a reference transaction that will be used during AutoPay processing. Upon approval, a series of asterisks and the last four digits of the card number replace the credit card number. For security purposes, UX Online does not save credit card numbers in the database. AutoPay will rely on the approved reference transaction linked to the Payment Demographics record to process credit card payments.

Important Note

Payflow Pro reference transactions expire 365 days from the last authorization date. Once the reference transaction expires, the Payment Demographic record is no longer valid for AutoPay. Please refer to About automatic credit card payments, Recommended AutoPay Actions, and Re-authorize Payment Demographic Records for important information on maintaining your payment demographic records.

A single account or contact can have multiple Payment Demographics records that are used for different modules in UX Online. For example, a contact can use one credit card to pay their subscription renewal invoices automatically and another credit card for their membership renewal invoices.

Note

If an account or contact has more than one Payment Demographics record set up for a module – for example, if there are two demographic records that have the Membership option set to Allow – UX Online will use the first record for all AutoPay transactions in that module.

From any of the UX work areas on the Navigation Tile Bar, click Contacts or Accounts . Open the account or contact where you want to set up automatic credit card payments.

In the Navigation Pane of the account or contact record, click Payment Demographics to display a list of Payment Demographics records already set up for the account or contact. Click Add New Payment Demographics on the List View toolbar to create a new Payment Demographics record.

In the Payment Demographics record, enter the following information about the credit card to be used for automatic payments:

  • Payment Source – Click the Lookup button to select the credit card product to use for this Payment Demographics record. When you select a credit card product, UX Online updates the Credit Card Type field.NoteAutoPay evaluates the accounting company of the batch selected for AutoPay against the accounting company of the credit card product setup selected for the Payment Source in the payment demographic record.
  • Currency – Select the currency of the invoices that you want to pay with this Payment Demographics information.

  • Credit Card Number – Enter the number of the credit card. Do not enter dashes or spaces.

Note

When the Payment Demographics record is saved, UX Online validates the credit card and authorizes the card (described below). If authorization is successful, it replaces the card number with a series of asterisks and the last four numbers of the card number. The actual credit card number is not saved in the database.

  • Expiration – Enter the expiration date of the credit card (in MMYY format).

  • CVV2 – This field is optional. If your organization’s business practices require it, enter the 3 or 4 digit security code. If a code is entered, the code will be transmitted with the credit card number and expiration date to the processor for verification. (When the credit card payment is authorized, this information is removed.)

  • Account Type – Leave the default entry of Credit Card .

  • Authorization – Displays the authorization ID after the record is saved for the initial authorization. The field is updated with the new authorization each time this record is used in AutoPay processing and each time the record is re-authorized by the Re-Authorize Payment Demographics utility.

  • Credit Card Type – Displays the type of the credit card product you select in the Product field.

In the Cardholder Billing Information section, the following information about the cardholder defaults from the account or contact record (these values can be edited):

  • Name on Card – If this is for a contact record, defaults to the contact full name. If this is for an account record, defaults to the full name of the account’s primary contact, if one exists.

  • Address 1 – Defaults from the primary address

  • City – Defaults from the primary address

  • State – Defaults from the primary address

  • Zip – Defaults from the primary address

In the Modules section, select the UX Online modules where you want to use this Payment Demographics record during AutoPay processing. For example, if the account or contact wants to use this credit card to automatically pay for only Membership invoices, mark the Allow option for Membership, and leave the rest of the modules set to Do not allow . Module selection can be modified at any time. The following modules are available for AutoPay:

  • Membership (renewal invoices)

  • Subscriptions (renewal invoices)

  • Certification (renewal invoices)

  • Exhibits

  • Meetings

  • Contributions (pledge installments and recurring gifts)

The Administration section contains the following fields:

  • Credit Card Has Problem – System populated bit field when authorization during AutoPay processing fails. When this value = No, the card can be used for AutoPay processing; when this value = Yes, the card will not be used for AutoPay processing, eliminating unnecessary transaction fees.

  • Authorization date – System populated date field displaying the date each time this record is authorized through PayPal. This includes the initial authorization to create the record, the date each time the record is used during AutoPay processing, and each time the record is re-authorized by the Re-Authorize Payment Demographics utility.

  • Problem Description – Populated by the system with a short description if the credit card authorization fails during AutoPay processing.

  • Expire Date – System populated date field based on credit card expiration date. Can be used to support record queries for Payment Demographics records by expiration date.

  • Owner – Displays the user who owns this record.

  • Modified By – Displays the user who last modified this record.

  • Modified On – Displays the date this record was last modified.

  • Created By – Displays the user who created this record.

  • Created On – Displays the date this record was created.

  • Contact – Displays the contact record for this Payment Demographics record.

  • Account – Displays the account record for this Payment Demographics record.

Click Save to save this record. UX Online will validate the credit card and, if successful, process the credit card for authorization in your organization’s credit card authorization account. (This is a $1.00 Payment Demographics authorization only—no actual charges will appear on the cardholder’s account due to this authorization process, however, there is a PayPal transaction fee for this authorization.)

If the credit card can not be validated, an error message will appear. Correct the credit card information and click Save to re-authorize . (For more information about validation, see Credit card validation .)

If the credit card type is validated but the credit card is declined, an error message will appear. (For example, “Invalid Expiration Date,” or “Invalid Credit Card Number.”) Correct the credit card information and click Save to re-authorize .

When the card number is successfully validated and the credit card is authorized through PayPal, UX Online updates the Authorization and the Authorization Date fields. The Credit Card Number and Expiration fields remain enabled for re-authorization should this information need to be updated and re-authorized later with more current or changed information.

Click Save & Close to save this record and return to the account or contact record.

Credit holds

You can place a credit hold on any account or contact. Placing a credit hold on an account or contact causes the following:

  • When a user views the account or contact record, a warning about the credit hold appears at the top of the record.

  • If your system is set up to display credit hold warnings, and a user creates a new invoice, opens an invoice, or edits and saves an invoice for an account or contact with a credit hold, a warning message will appear. (For more information about credit hold warnings, see Displaying credit hold warning messages .)

  • If you are using the MX Online, a customer who has a credit hold placed on their account or contact record will not be able to create a transaction – for example, to purchase a product or register for a meeting.

Note

Placing a credit hold on an account or contact does not prevent users from creating, opening, or editing and saving invoices for that customer, nor does it prevent the system from processing that customer’s invoices.

Placing a credit hold on an account or contact

From any of the UX work areas on the Navigation Tile Bar, click Contacts or Accounts . Locate and open the account or contact where you want to place a credit hold.

Scroll down to the Contact Preferences section on the record . In the Billing Information section, click to select Yes on the Credit Hold option.

Click Save & Close to save the account or contact record.

Placing a credit hold on multiple accounts or contacts

You can place a credit hold on multiple accounts or contacts at one time.

From any of the UX work areas on the Navigation Tile Bar, click Contacts or Accounts . From the list of records, select the accounts or contacts you want to place a credit hold on.

Hint

To select a range of accounts or contacts, click the first record in the range, then press and hold the Shift key, and click the last record. All of the records in the range will be selected. To select multiple records not in a range, press and hold the Ctrl key while clicking individual records.

When you have selected the records you want to place a credit hold on, click the Edit button on the List View toolbar.

In the Edit Multiple Records window, scroll to the Default Billing Information area. In the Billing Information section, click Yes on the Credit Hold option.

Click Change to save your changes to the selected account or contact records.

Displaying credit hold warning messages

You can control whether UX Online displays a warning message when you create, open, or edit and save an invoice for a customer who has a credit hold placed on their record.

Note

Whether or not you set up your system to display the credit hold warning message, a customer who has a credit hold will not be able to create an invoice in MX Online.

In the Navigation Tile Bar , select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. The list will open in a new window.

Important

Do not add or remove any configuration records from this list.

Locate and open the parameter PAInvoiceMsgs.CustomerCreditHold.Show. Set the Config Value field as follows:

  • TRUE – Display a warning message when a user opens an invoice for an account or contact that has a credit hold.

  • FALSE – Do not display a warning message.

Click Save & Close to save your change and close the record . Because the list opened in a new window, close the list window by clicking the “ X ” in the upper right hand corner of the window.

Address validation overview

Part of every UX Online deployment is the ability to domestic (US) and Canadian addresses for contacts and accounts using the Melissa Data verification service. Because address data is maintained in a composite field, address validation changes will not be displayed until you Save of the record.

You can verify primary and secondary addresses on contact and account records.

You can verify the additional addresses that your account and contact records may have. These addresses appear when you click Addresses in the Navigation Pane of an account or contact record.

You can verify the Ship To and Bill To addresses on invoices by clicking the Address Validate on the invoice Record toolbar .

If you want to verify multiple primary and secondary addresses at the same time, you must use the Melissa Data Bulk Address Validation utility.

Melissa Data address data requirements and results

The Melissa Data web service validates only United States and Canadian addresses. If the Country/Region field is blank, or contains United States, US or USA, Canada or CA, the web service will attempt to validate the address. Otherwise, proposed data changes may not be returned in the Address Validation window.

To fully verify, update, and standardize an address with the Melissa Data web service, an address record must have at least one of the following combinations of valid data:

  • Street 1, City, State or Province

  • Street 1, ZIP Code or Postal Code

There are various components to updating to an address, and Melissa Data will update and standardize eligible data based on the data submitted.

Important

Melissa Data does not recognize special characters in Canadian addresses.

The Melissa Data web service verifies, corrects, and updates US and Canadian addresses in the following ways:

  • Standardizes addresses to United States Postal Service or Canada Post specifications.

  • For U.S. addresses – Updates existing U.S. ZIP code data to ZIP +4.

  • Updates the Country field data to US for United States addresses and to CA for Canadian addresses.

Note

You can configure your system to return CANADA for the country in lieu of CA for Canadian addresses. See Configuring your system to return CANADA for Canadian addresses .

  • For U.S. addresses – If a record’s primary address can be verified, adds the primary address’s U.S. congressional district to the Summary section of the account or contact record.
  • For U.S. addresses – If a record’s primary address can be verified, adds the primary address’s State Senate and State House districts to the respective fields published to the Summary sections in the Account form or the Contact form.
  • For U.S. addresses – If a record’s primary or secondary address can be verified, adds the primary or secondary address’s latitude and longitude to the respective address in the Address Information section of the account or contact record.

Note

If you need the system to add longitude and latitude information to Canadian addresses, contact your Protech representative.

Configuring your system to return CANADA for Canadian addresses

Depending on your organization’s requirement, you can configure the system to return CANADA in the country field for Canadian address validation by modifying the Config value of the PAMelissaAddressValidation.UseCanadaCountryName application parameter.

To access this information, in the Navigation Tile Bar , select the Administration work area > UX Settings > UX Online Application Parameters. The list will open in the new window. L ocate and open the parameter PAMelissaAddressValidation.UseCanadaCountryName.

Set the Config value field to true. (If you leave the value of this field blank, the system will use the default value of CA as the country name during address validation.)

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “ X ” in the upper right hand corner of the window to close it.

Address validation and child account or contact addresses

If an account or contact is a child of a parent account or contact, the setting of the Use Parent Address option on the primary address and the Use Parent Address option on the secondary address will affect how Melissa Data address verification updates child account and child contact addresses.

  • If an account has a child account, and the child account has the Use Parent Address option set to Yes on the primary address , the system will update the child account’s primary address if it makes any changes to the parent account’s primary address during address validation. If the child account has the Use Parent Address option set to Yes in the secondary address , the system will update the child account’s secondary address if it makes any changes to the parent account’s secondary address during address validation.

  • If a parent account has a child contact, and the child contact has the Use Parent Address option set to Yes on the primary address , the system will update the child contact’s primary address if it makes any changes to the parent account’s primary address during address validation.

  • If a contact has a child contact, and the child contact has the Use Parent Address option set to Yes on the primary address , the system will update the child contact’s primary address if it makes any changes to the parent contact’s primary address during address validation.

Validating primary and secondary addresses at the record level

You can verify that the primary and secondary address information for a contact or account record by using the Address Validation button Record toolbar of an account or contact record.

Note

See Address validation and child account or contact records and Melissa Data address data requirements and results for additional information related to this utility.

When you click the Address Validation button, UX Online will contact the Melissa Data service and open an Address Validation window displaying the existing and proposed (validated) address data for both the primary and secondary addresses. Existing address data is displayed on the left column of the window; proposed data changes are outlined in red are displayed on the right column of the window.

To change only the primary address, select Use This under the primary. To change only the secondary address, select Use This under the secondary address. To change both addresses, select Use Both at the bottom of the window. Because address data is maintained in a composite field, changes will not be displayed until you Save of the record.

The Melissa Data web service validates only United States and Canadian addresses. If the Country/Region field is blank, or contains United States, US or USA, Canada or CA, the web service will validate the address. Otherwise, proposed data changes may not be returned in the Address Validation window.

Important

Melissa Data does not recognize special characters in Canadian addresses. Your results may not be satisfactory for any addresses that contain the following characters: &, %, $, *, or @.

Validating additional addresses at the record level

You also can verify that any additional addresses for a contact or account record are formatted properly. From the Navigation Pane in an account or contact record, click Addresses to display a list of additional addresses. Select and open an address record. Select the Address Validation button on the Record toolbar.

Validating invoice Bill To and Ship To addresses

You can verify that the Bill To and Ship To addresses on an invoice are formatted properly and complete. From the Record toolbar of an invoice, select the Address Validation button.

To change only Ship To address, select Use This under the Ship To address. To change only the Bill To address, select Use This under the Bill To address. To change both addresses, select Use Both at the bottom of the window. Because address data is maintained in a composite field, changes will not be displayed until you Save the invoice record.

Melissa Data Bulk Address verification

You can verify multiple domestic and Canadian primary and secondary addresses for your account and contact records at one time using the Melissa Data Bulk Address Validation utility. This utility updates address data for eligible address records. Additionally, the utility updates the Congressional District, State Senate, and State House fields published to the related Account or Contact form, based on the primary address (address number 1). The State Senate and State House attributes are published to the Account and Contact forms. This is a prerequisite for the utility to update this data

Note

If a large number of address records are to be validated, this process could take some time to complete. We recommend that you run this process after business hours so that you do not interfere with normal daily activities.

Eligible address records search criteria

When initiating the Melissa Data Bulk Address Validation utility, the system searches for address records that meet the following criteria:

  • Address line 1 is not NULL, and

  • Address number is less than 3 <primary and secondary address>, and

  • Modified On or After <prompt from date entered>, and

  • Modified On or Before <prompt to date entered>, and

  • (country = NULL or country =”US” or country = “USA” or country = “CA” or country = “CANADA” or country = “United States of America” or country = “United States”)

Initiating Melissa Data Bulk Address Validation

In the Navigation Tile Bar , select the Administration work area > Address Validation > Melissa Data Bulk Address Validation .

In the Address Validation window, enter the beginning and end of the date range to identify account and contact addresses that have been modified in the range you enter. Click Search .

A window will open showing the number of primary and secondary address records that will be submitted for processing. This may not be the number of records that are actually updated.

Click Run to initiate the process. The system will begin validating the selected address records. Click Search to enter new search criteria. Click Close to cancel the process.

Running Melissa Data Bulk Address Validation on 50,000+ records

When running the Melissa Data Bulk Address Validation utility, the utility first searches for the records based on the parameters entered and this search query returns a count of eligible records. If the number of records found exceeds 50,000 records, the search query will return a count of 50,000+. No exact count will be returned.

Note

The utility processes addresses “one page at a time” to avoid record limits. When validating addresses on a large number of records, the process could take several hours.

Identifying address records updated during the bulk address validation process

If an eligible primary or secondary address record is updated during the Bulk Update Process, the system flags the Address Validation Error field in the address record = No. To identify these successfully updated address records, use Advanced Find on the address entity immediately following the bulk address validation process to search for address records modified on <date> and Address Validation Error = No.

Identifying address records not updated during the bulk address validation process

If an eligible primary or secondary record fails to update during the Bulk Update Process, the system flags the Address Validation Error field in the address record = Yes. When an error occurs, the system also enters an error description in the Error Description field in the address record. To identify these address records, use Advanced Find on the address entity immediately following the bulk address validation process to search for address records modified on <date> and Address Validation Error = Yes and Error Description contains data.

Use this opportunity to identify bad address records and update them manually to maintain the integrity of your data.

Clearing the Address Validation Error after correcting bad addresses

Once you have updated the bad address data, you can clear the Address Validation Error and Error Description fields using the On Demand Workflow: Clear Address Validation Error Flags.

In your Advanced Find results, select the records you wish to clear and click Run Workflow > Clear Address Validation Error Flags, which is located on the toolbar of your Advanced Find address query. This workflow clears the Address Validation Error bit field and clears the Error Description fields when Validation Error bit field = Yes. It does not clear the Address Validation Error bit field value when the value = No.

Chapter 11: History Store

This chapter explains how your organization can set up and customize the UX Online History Store to track invoice transactions for any given account or contact.

Based on your organization’s History Store set up, a UX Online History Store nightly process will automatically create entries nightly for eligible transactions contained in a closed batch. Eligible transactions include those invoice transactions where the invoice is paid in full and where the transaction type is flagged for tracking in the History Store setup.

Note

The History Store Created bit field on the batch log record is a system-managed field that indicates whether History Store records were created for this batch during the nightly process on closed batches. Do not change the value of this field. When creating a new batch, the default for this field is No, indicating that History Store records have not yet been created. When the batch is closed and the nightly process creates History Store records, the system updates this field to Yes.

This information is divided into the following sections:

  • Set up transaction types to record in the History Store

  • View History Store information for a contact or account

  • History Store View

Set up transaction types to record in the History Store

This section explains how to set up the History Store Manager in UX Online.

Note

You only need to create entries for those transaction types that you wish to track in the History Store.

In the Navigation Tile Bar , select the Administration work area > History Store > History Store Settings . The History Store Setup records list opens in a new window, showing all of the entities in UX Online that are currently being tracked for your organization. If there is no setup, then this list will be blank.

Click New on the List View toolbar to set up a transaction type to be tracked.

In the History Store Setup record, enter the required information for the type of transaction you want to track in the history store. (Refer to the following table for the naming conventions needed for this record).

History Type Name

History Type Code

Source Module

Advertisements

26

Advertisements

Auction Items

27

Contributions

Gift in Kind

22

Contributions

Monetary Contributions

21

Contributions

Monetary Pledges

23

Contributions

Pledge Summary

29

Contributions

Recurring Gifts

25

Contributions

Promotion Package

42

Events

Exhibit

17

Exhibits

Exhibitor Badge

16

Exhibits

Booth

14

Exhibits

Misc. Exhibit

19

Exhibits

Cancel Fee Exhibit

20

Exhibits

Registration

9

Meetings *

Session

10

Meetings *

Dues Billing

11

Membership

Chapter Billing

13

Membership

Payments

6

Payments

Sales Inventory

1

Product Sales **

Sales Non Inventory

5

Product Sales **

Freight

7

Product Sales

Tax

8

Product Sales

Miscellaneous Charges

2

Product Sales

Certification

15

Professional Development

Course Registration

18

Professional Development

Subscription

12

Subscription

* Meeting participant transfers are not captured in the History Store.

** Negative quantities of Product Sales items returned through RMA processing are not captured in the History Store at this time.

  • History Type Name – Enter the name of the transaction that you want to track.

  • History Type Code – Enter the code for this transaction type.

  • Source Module – Enter the source module name for each type name.

  • Track History – Click Yes if you want UX Online to create an historical record of this transaction type.

Click Save & Close to save the history store record and return to the History Store Setup list. Repeat this process for each setup record. When you are finished, click the “ X ” in the upper right hand corner of the window to close the setup records list window.

View History Store information for a contact or account

When you have set up the types of transactions you want recorded in the History Store, you can view a running journal of each invoice for contact or account transactions where the invoice has been paid in full and the batch has been closed.

Note

The history store will only record an entry for those transaction types that you have entered in the History Store Manager and set the Track History field to Yes . In UX Online, History Store entries are created nightly for eligible transactions in closed batches.

Meeting participant transfers are not captured in the History Store. RMA Product returns are not captured in the History Store.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts . Open the account or contact record where you want to view history store information.

In the Navigation Pane of the record, select History Store to open the History Store Associated View.

This list displays a date-stamped entry for each invoice transaction for this account or contact that has been paid in full and where the batch has been closed and captured in the nightly process for creating History Store entries.

You can sort this view by clicking on the column headings. You can also print or export this information to Excel for further data manipulation.

To view more detailed information about any of the entries on this list, double-click that entry.

Note

All History Store data can be queried using the Advanced Find tool and SRS Reporting tools that come standard with your UX Online application.

History Store View

UX Online also offers a History Store View that provides advanced find search capability from a single view. To open this view, in the Navigation Tile Bar , select the Administration work area > History Store  > History Store View.

Chapter 12: Audit History

This chapter explains how to track changes made to your business data by auditing the data. Use auditing to analyze the history of a particular record, view a summary of everything that changed, track when a user accessed Microsoft Dynamics CRM, or to comply with regulation standards. Keep track of the changes done to a record, a field, or by a user.

Note

Auditing is enabled or disabled by entity and field. There is no mechanism to enable or disable auditing by user.

When you enable auditing, Microsoft Dynamics CRM automatically stores the change history for transactions in the form of audit logs in the database. All auditing data is stored in a single audit table. This design keeps the audit logs completely separated from other CRM data.

In Microsoft Dynamics CRM, audit tracking for entity relationships is handled differently than audit tracking for entities or fields. See Tracking changes for entity relationships for more information.

Important Note

By default, the UX Online Account, Contact, and Product entities are enabled for auditing. If you enable auditing on other core UX entities or change the field auditing settings on these three core entities, these changes may be overwritten during a release patch or upgrade.

Enabling auditing on client-custom entities in the client solution will not be overwritten during a release patch or upgrade.

Best practices for auditing

Turn off auditing when doing the initial import of data. Auditing is meant to keep track of user made changes. There is no need to waste disk space auditing bulk load or changes done by the initial bulk import. Enabling or disabling the whole auditing mechanism can be done with a single click.

Do not audit read only entities and fields. Turning off audit on read only entities and fields will not only save disk space but system resources, too. If the field cannot be changed, there is no opportunity for auditing.

Choose carefully what you audit. As you design the items to audit, examine the fields that could have a business impact and from a financial, process, or regulatory perspective. These are the fields you want to audit. You should disable auditing on all other non-essential fields. This will not only save disk space but system resources, too. For example, a client using CRM for sales automation is a steel manufacturing company and one of the entities used is a custom steel plate entity. This steel plate entity has dozens and dozens of fields and logic to calculate the final price. However, the sales reps have the ability to override the system-generated price. In this case, do not audit the dozens of fields used for calculations, but do audit the final price field. Why? Because this is the field that has a financial impact on the business.

Delete old log entries. Audit logs use disk space. The more activity the system has on audit-enabled entities, the more logs, and thus the more disk space will be used. There is no need to keep audit logs indefinitely. CRM 2011 allows an administrator to delete auditing in batches. Each batch is a calendar quarter. Determine the time frame to keep audit logs and incorporate into a process deleting old entries. Please contact your Protech representative before deleting audit logs.

Configure and manage auditing

As described below, configuring auditing requires setup in the following areas:

  • Start or stop auditing for the organization globally

  • Enabling or disabling auditing for entities

  • Enabling or disabling auditing for fields

Note

These tasks require the System Administrator or System Customizer security role or equivalent permissions. For users working in the shared PCBS environment, these tasks require the CRM4M System Customizer role, which is the most privileged role assigned to designated users in this environment.

Start or stop auditing for the organization globally

Start auditing at the organization level to allow auditing for entities and fields. When you start auditing for the first time, auditing is started by default on the following entities: Account, Contact, Goal, Goal Metric, Lead, Marketing List, Product, Quick Campaign, Rollup Query, and Sales Literature.

You may want to stop auditing for maintenance purposes or when importing data. Stopping auditing at the organization level stops the tracking of changes for the entities or fields for the period for which auditing is stopped at the organization level. When you start organization level auditing again, the same entities and fields are selected for auditing that were selected when you stopped auditing for the organization.

In the Navigation Tile Bar, select the Administration work area > Auditing > Global Audit Settings to open the Audit tab of the System Settings dialog window.

To start audit tracking, click the Start Auditing checkbox . To initiate auditing on all Common Entities, select this check box.

To stop audit tracking, clear the Start Auditing check box.

Click OK.

Audit log on user access in CRM

You can track when a user logs on to Microsoft Dynamics CRM by enabling auditing on the user access. The audit log of the user access is available in the Audit Summary View page. For more information, see View audit summary of records.

In the Navigation Tile Bar, select the Administration work area > Auditing > Global Audit Settings to open the Audit tab of the System Settings dialog window.

To start audit tracking, click the Start Auditing checkbox . To initiate auditing on all users, select the Audit user access check box

To stop tracking the user access details, clear the Audit user check box.

Click OK.

Note

Before you enable auditing for user access, you must first start auditing for the organization globally.

Enabling or disabling auditing for entities

You must start auditing at the organization level to enable auditing for an entity.

Important

Enable/disable auditing for entities in the client-custom solution or your settings may be overwritten during a solution update.

Caution

Do not enable auditing on all entities. Only enable auditing on entities where you have a business need to view audit history.

By default, when you enable auditing for an entity, all of that entity’s fields are automatically enabled for auditing until you disable auditing for unnecessary fields. See Enabling or disabling auditing for fields for more information.

Enabling for auditing for all entities will consume database space and system resources unnecessarily.

In the Navigation Tile Bar, select the Administration work area > Auditing > Entity and Field Audit Settings. Under Components, expand entities. Select to open the entity where you want to enable auditing.

To start auditing, on the General tab in the Options for Entity section, select the Auditing checkbox .

To stop auditing for the entity, clear the Auditing checkbox.

To publish the changes, click Publish.

Note

By default, when you start or stop auditing for an entity, you also start or stop auditing for all the fields of this entity.

Enabling or disabling auditing for fields

By default, when you enable auditing for an entity, auditing is also enabled on all its fields. You can select or clear fields for which you want to enable auditing.

Caution

Because all fields are enabled for auditing when the entity is enabled for auditing, you must disable auditing on those fields where there is no business need to track changes.

Failure to do disable auditing on unnecessary fields will ultimately result in an unmanageable audit history filled with useless data. Leaving all fields enabled for auditing will consume system resources and database space.

In the Navigation Tile Bar, select the Administration work area > Auditing > Entity and Field Audit Settings. Under Components, expand Entities. Expand the entity that is enabled for auditing where you want to enable or disable auditing for the fields. Click Fields.

To start or stop auditing for a single field, open the field and in the Auditing field, click Enabled or Disabled, respectively.

To start or stop auditing for more than one field, select all the fields to be started or stopped. On the Actions toolbar, click Edit. Then in the Edit Multiple Fields dialog box, in Auditing, click Enabled or Disabled, respectively.

Click Save.

Click Publish All Customizations.

Notes

Before you enable field auditing, you must first enable auditing for the organization.

Field auditing only tracks value changes to the field. Field auditing does not track enabling or disabling Field Level Security for the field.

Not all fields can be audited in Microsoft Dynamics CRM. Fields that cannot be audited display ‘Not Applicable’ in the Audit Status.

View Audit Summary

As described below, options for viewing audit history include:

  • View audit summary of records

  • View the audit history of individual records

View audit summary of records

For each entity for which auditing is enabled, the audit summary shows the change details of all records that are audited in a chronological order, starting from the recent ones.

Note

Viewing the audit summary requires the System Administrator or System Customizer security role or equivalent permissions. For users working in the shared PCBS environment, these tasks require the CRM4M System Customizer role, which is the most privileged role assigned to designated users in this environment.

In the Navigation Tile Bar, select the Administration work area > Auditing > Audit Summary View.

The following table shows various tasks that you can perform on the Audit Summary View page.

Tasks

Required Steps

See when the user logged on to Microsoft Dynamics CRM

Click Enable/Disable Filters .

On the Operation column header, click the Filter button.

Select Access , and then click OK .

The entries User Access via Web and User Access via Web Services in the Event column specify whether a user accessed Microsoft Dynamics CRM through a Web page or Outlook, or programmatically.

See when auditing was enabled or disabled for user access

Click Enable/Disable Filters .

On the Event column header, click the Filter button.

Select User Access Audit Started or User Access Audit Stopped , and then click OK .

See the changes made on a particular date

Click Enable/Disable Filters .

On the Changed Date column header, click the Filter button.

Click one of the default date filters, and then click OK .

Or, click Custom Filter , specify the filter criteria, and then click OK .

See the records on which a particular action was performed

Click Enable/Disable Filters .

On the Action column header, click the Filter button.

Under Custom Filter , select the check boxes for the actions that you want to see, and then click OK .

See the changes done by a particular user

Click Enable/Disable Filters .

On the Changed By column header, click the Filter button.

Click Custom Filter , specify the filter criteria, and then click OK .

Or , c lick Filter by specific Changed By , and in the Look Up Records dialog box, search and select users, and then click OK .

See all the changes done in a particular record

In the Record column, double-click the record.

See all the changes made to a particular entity

Click Enable/Disable Filters .

On the Entity column header, click the Filter button.

Under Custom Filter , select the check box for the entity, and then click OK .

See the records that underwent a particular operation

Click Enable/Disable Filters .

On the Operation column header, click the Filter button.

Under Custom Filter , select the check box for the operation, and then click OK .

Important

If you share a record with another user, and if that user has View Audit History permissions on the shared record, the other user will be able to view the changes to the shared record.

Note

If auditing is stopped and restarted at the organization, entity, or field level, any new values prior to stopping the audit will not be used in an audit log or audit history. For example, two days ago the value in the Rating field is Cold when auditing is stopped. Auditing was started today. During the two days without auditing, the value for the field changed from Cold to Warm to Hot. When restarting the audit, the audit history has Cold (the value when the auditing stopped), although the New Values column has a symbol to show you that auditing had been disrupted.

View audit history of individual records

You can view the change history of individual records only when auditing is enabled for the organization and enabled for the record types and fields.

  • In any list of records, open the Navigation Pane of the record for which you want to view the changes made and click Audit History .

  • In the Filter on the drop-down box, click a field for which you want to view the audit history.

  • To view the audit history of all the fields in the record, click All Fields.

Note

By default, all fields for which auditing is enabled are displayed in the list.

The following details are listed for the audited fields:

  • The date when the fields were changed.

  • The user who updated the fields.

  • The action performed on the fields, such as Create or Update.

  • The previous and new value for the changed field.

Note

If auditing is stopped and restarted at the organization, entity, or field level, any new values prior to stopping the audit will not be used in an audit log or audit history. For example, two days ago the value in the Rating field is Cold when auditing is stopped. Auditing was started today. During the two days without auditing, the value for the field changed from Cold to Warm to Hot . When restarting the audit, the audit history has Cold (the value when the auditing stopped); although the New Values column has a symbol to show you that auditing had been disrupted.

To open the change list for an item, double-click to open the item.

Note

When a reference for a record to another record is changed or added, the changes for the referenced record will not be tracked. The changes will be tracked for the referring record. For more information, see Tracking changes for entity relationships.

Tracking changes for entity relationships

In Microsoft Dynamics CRM, audit tracking for entity relationships is handled differently than audit tracking for entities or fields.

Note

Entity relationships are metadata configurations that allow for related records to have lookup fields, which let users link the related records to other records. Any related records can appear in a list that is visible from the record that they have been related to.

Here are some examples of how entity relationships are audited:

Entity Relationships

Scenarios

What is audited

Summary

1:N

Contact associated with a parent account

If auditing is enabled for the Contact entity, the changes to the parent account reference are tracked.

If auditing is enabled for the Account entity but not for the Contact entity, no change will be tracked for this transaction because the Account entity did not change.

In a 1:N relationship between entities, the change is reflected only on a single entity. Only changes to the entity that changed are recorded, provided the entity is enabled for audit.

N:N

Lead added to a marketing list

If auditing is enabled for the Lead entity, the marketing list it is added to is tracked for changes.

If auditing is enabled for the Marketing List entity, the lead that is added is tracked for changes.

In an N:N relationship between entities, the change is captured on both entities, provided that the entities are enabled for audit.

If auditing is enabled for one entity, the association of this entity with the other entity is tracked.

Special Cases

Lead added to an activity, such as an e-mail activity

If auditing is enabled for the e-mail entity, e-mail activity is tracked for changes.

If auditing is enabled for the Lead entity, nothing is tracked because the Lead entity did not change.

When the N:N relationship involves certain type of entities, such as an ActivityPartyBase or a PartyList, the relationship internally is handled as 1:N and the changes are tracked only on the ActivityPartyBase entity or the PartyList entity, provided ActivityPartyBase or PartyList is enabled for audit.

Reporting on Audit History

Because there is limited capability out of the box to filter Audit History data at the record level or in the Audit View Summary, and no capability for exporting that data, UX Online includes three base reports to address this need. These reports provide additional search capability and report results can be exported easily to PDF or Excel.

The UX Online reports return Audit History records that were triggered by an Update event to an individual record. They do not return results for Audit History records that were triggered by other events such as Create, Delete, etc.

These reports include:

  • UX Audit Log Report

  • UX Account Audit Log Report

  • UX Contact Audit Log Report

The UX Audit Log Report returns audit history for any selected entity that is enabled for auditing. For example, if auditing is enabled only on the account, contact, product, and opportunity entities, only these entities are available for selection when running the report. This report supports searches for audit history data from the selected entity by date range or all dates, and by selected field or on all fields (fields must be enabled for auditing). This report does not support a search by Modified By. Report output is not filtered based on the user’s security roles/privileges. This report returns the following results based on the search criteria entered:

  • Modified On (date/time)

  • Record Name (depends on the selected entity)

  • Schema Name

  • Field Name

  • Old Value

  • New Value

  • Modified By

The UX Account Audit Log Report is designed to be run from the “Run Reports” button on the Record toolbar of an account record but can be run from the report list by selecting a single account record. Similarly, the UX Contact Audit Log Report is designed to be run from the “Run Reports” button on the Record toolbar of a contact record but can be run from the report list by selecting a single contact record. Both reports support a search by date range or on all dates and a search by selected field or on all fields (fields must be enabled for auditing). These reports do not support a search by Modified By. Report output is not filtered based on the user’s security roles/privileges. These reports return the following results based on the search criteria entered:

  • Modified On (date/time)

  • Record Name (account name or contact name)

  • Schema Name

  • Field Name

  • Old Value

  • New Value

  • Modified By

Sample reports are available in the UX Online Base Report Sample Library.

Accounting Transaction Processing

Part 3: Accounting Transaction Processing

Managing the transactions entered in UX Online is part of the foundation of the system. This part of the documentation describes how UX Online integrates with your back office accounting system (either Microsoft Dynamics GP or Microsoft Dynamics SL), as well as the different types of transactions you can process, such as credit card processing, adjustments, and payment transactions. It also describes the revenue recognition process.

This information is divided into the following chapters:

  • Chapter 13: Integration with General Ledger

  • Chapter 14: Integration with Bank Reconciliation

  • Chapter 15: RapidPay Processing

  • Chapter 16: Payment and Adjustment Transactions

  • Chapter 17: AutoPay Processing

  • Chapter 18: Gift Certificates

  • Chapter 19: Credit Card Transaction Daily Settlement

  • Chapter 20: Revenue Recognition

  • Chapter 21: Lockbox Management

Chapter 13: Integration with General Ledger

This chapter outlines the set up and explains the processes involved in the integration between UX Online and the General Ledger. Most of the time, the accounting procedures you will use in UX Online are the same regardless of the back office General Ledger you are using. However, the setup and integration points will vary depending on whether your organization is using Microsoft Dynamics GP (formerly known as Great Plains) or Microsoft Dynamics SL (formerly known as Solomon).

In addition, you will use different procedures to validate a batch in Microsoft Dynamics GP or Microsoft Dynamics SL.

  • Setup and integration points

  • Multicompany overview

  • Batch controls overview

  • Automatically close batches

  • Creating a batch in UX Online

  • Creating GL detail for a batch

  • Posting a batch

  • GL posting reports

  • Validating posting in Microsoft Dynamics GP General Ledger

  • Validating posting in Microsoft Dynamics SL

  • Resetting a batch

  • Diagnosing batch posting

  • Resolving posting errors

Setup and integration points

If you are using UX Online with Microsoft Dynamics GP, the following setup must be completed in Microsoft Dynamics GP:

  • Company (Tools > Setup > Company > Company)

  • Intercompany (Multicompany) optional (Tools > Setup > System > Intercompany Setup)

  • Chart of Accounts (Cards > Financial > Account)

  • System (Tools > Setup)

  • Posting (Tools > Setup > Posting > Posting)

  • Financial (Tools > Setup > Financial > General Ledger)

For detailed instructions for setting up these features, refer to the Microsoft Dynamics GP documentation.

If you are using UX Online with Microsoft Dynamics SL, the following setup must be completed in Microsoft Dynamics SL:

  • Chart of Accounts (Module – General Ledger > Setup > GL Setup)

  • Sub-Accounts (Module – General Ledger > Maintenance > Chart of Accounts Maintenance)

  • GL Setup (Module – General Ledger > Maintenance > Subaccount Maintenance)

For detailed instructions for setting up these features, refer to the Microsoft Dynamics SL documentation.

For integration with Dynamics SL, set the value for the accounting application parameters.

If you integrate with SL 2011

  • CRM4M.Accounting.Solomon2011 = true
  • CRM4M.Accounting.Solomon2015 = false

If you integrate with SL 2015:

  • CRM4M.Accounting.Solomon2011 = true
  • CRM4M.Accounting.Solomon2015 = true

For integration with Dynamics GP or Dynamics SL, you must set up the following in UX Online:

  • Global Setup Defaults (Administration > UX Settings > Accounting Company and Chart of Account Settings > Global Setup Default) – The Global Setup Default record establishes the link between UX Online and your back office accounting system and inventory system. For more information, see Global Setup Defaults.

  • Companies (Administration > UX Settings > Accounting Company and Chart of Account Settings > Companies) – Company records establish the link between each separate organization in UX Online and the company databases in your back office accounting system. This link controls the accounting system company where UX Online transactions will be posted as well as automated refresh settings. For more information, see Companies.

  • Chart of Accounts (Administration > UX Settings > Accounting Company and Chart of Account Settings > Chart of Accounts) – The Chart of Accounts records establish the link between your GL accounts in UX Online and the chart of accounts in your back office accounting system. For more information, see Chart of Accounts records.

  • Payment Products (Product Sales > Product Sales > Product Sales Setting) – Set up products for the payment, refund, transfer, and write-off products your organization uses. For each product, be sure to set the following:

    • Company – This is the company where this product with its account numbers resides.

    • Primary GL Account – This is the account number that is used to create the journal entry when the GL Detail is created.

    • Secondary GL Account – This is the revenue account that is used if you defer renewal billing (for membership or subscriptions) or event revenue, and is used during a Revenue Recognition process in the system. This can be either the Revenue Recognition Process for Renewal Billing or the Revenue Recognition Process for Events.

    • AR Account – This is the account number that is used when an accrual product is not paid in full. For Payment Products only, this represents the unapplied account that is used when an accrual invoice is overpaid and when a cash basis invoice is either underpaid or overpaid, or if a refund is posted before the associated customer payment. For more information, see About unapplied accounts.

    • AP Account – This account is used if your organization purchased the integration to Payables and is the payables account that will be credited in a refund or chapter reimbursement product.

For detailed information about this setup, see Organization Setup and Accounting Setup.

Multicompany overview

If your organization wishes to use the multicompany features of UX Online, and your system is integrated with Microsoft Dynamics GP, you must complete the following setup and configuration procedures.

In Microsoft Dynamics GP:

  • Install the Intercompany module.

  • Create the chart of accounts for each company.

  • Create intercompany relationships in the Intercompany Setup window (Tools > Setup > System > Intercompany).

In UX Online:

  • In the Global Setup Defaults record, set the General Ledger System option to Great Plains. For more information, see Global Setup Defaults.

  • Create your company records. For more information, see Companies.

  • Create the accounts needed for UX Online. (Note: Not all of the accounts used in Microsoft Dynamics GP are needed in UX Online.) For more information, see Chart of Accounts records.

  • Create the products needed for each company.

Note

You must set up payment products for each company when working in a multicompany environment.

After you have completed multicompany setup in both Microsoft Dynamics GP and UX Online, you will assign the batches you create in Microsoft Dynamics GP to one of your companies. When you post the batch, this company will be the “destination” company in Microsoft Dynamics GP for the journal entry. When the journal entry is posted in Microsoft Dynamics GP, the offset transactions for multicompany transactions will be created based on the intercompany relationships set up in the Intercompany Setup window.

Batch controls overview

UX Online includes features that give you greater control over how batches are used and how and when they can be closed. These include:

  • Validate batch control amount

  • Batch Type controls

  • RapidPay payments controls

  • On-hold invoices control

Validate batch control amount

You can set up UX Online to require that the total currency amount of the payment transactions in a batch must match a control amount entered for the batch. This batch control amount is entered in the Control Amount field on the Batch Log record for batch type Standard GL Detail Creation.

If you system is configured for batch control amount validation, if the total amount of the transactions does not match the amount in the Control Amount field, you will not be able to close the batch for posting. You must adjust either the payment transaction amounts or the batch’s control amount in order to close the batch. (If there are no transactions with payments in the batch, the batch control amount must be zero.)

If your system is not set up to require this batch control amount validation, the amount in the Control Amount field is for your reference only; you will be able to close and post batches whether or not the payment transaction total matches the control amount.

You can choose to close validate standard non-web batches, your web batches, or both. These default settings are managed by UX Online Application Parameters, as described below.

Configuring your system to require batch control validation

Validate payment control for standard non-web batches

To configure your system to require batch control validation for non-web batches where batch type is Standard GL Detail Creation, the UX Online parameter PABatch.ValidatePaymentControl must be set to TRUE.

In the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This View opens in a new window. Locate and open the parameter PABatch.ValidatePaymentControl and set the Config Value field as follows:

  • TRUE – Enter this to enforce validation of the batch control amount for non-web Standard GL Detail Creation batches

  • FALSE – Enter this if you do not want to enforce validation of the batch control amount for non-web batches

Click Save & Close to save your change and close the record. Close the View window by clicking the “X” in the upper right hand corner of the window.

Non-web batch control amount validation when automatically closing non-web batches

When considering your system settings for validating payment control on non-web batches, you must also consider your settings for automatically closing non-web batches. See Automatically closing batches for more information.

Sample configuration options for validating control amount and the nightly process for closing standard non-web batches:

Business Need for Non-Web Batches

UX Online Application Parameter Configuration Settings

Recommended if you require validation control

You want the system to validate the batch Control Amount against the total payments processed in standard non-web batches AND if the Control Amount can be validated, you want the system to automatically close standard non-web batches nightly.

Result: Validation of the control Amount is enforced during the nightly process to close standard non-web batches and when a user closes a standard non-web batch manually. If the Control Amount is validated during the nightly process, standard non-web batches will be closed automatically by the system. If the Control Amount is not validated during the nightly process, standard non-web batches must be closed manually on a daily basis.

PABatch.ValidatePaymentControl = true

and

PANightlyProcess.CloseNonWebBatches = true

Recommended if you do not require validation control

You do not want the system to validate the batch Control Amount against the total payments processed in standard non-web batches AND you want the system to automatically close standard non-web batches nightly.

Result: There is no validation of the Control Amount for standard non-web batches at any time. All standard non-web batches will be closed automatically by the system during the nightly process.

PABatch.ValidatePaymentControl = false

and

PANightlyProcess.CloseNonWebBatches = true

You want the system to validate the batch Control Amount against the total payments processed in standard non-web batches AND you do not want the system to automatically close batches nightly.

Result: When a user attempts to close a standard non-web batch manually, validation of the Control Amount is enforced. All standard non-web batches must be closed manually on a daily basis.

PABatch.ValidatePaymentControl = true

and

PANightlyProcess.CloseNonWebBatches = false

You do not want the system to validate the batch Control Amount against the total payments processed in standard nob-web batches AND you do not want the system to automatically close batches nightly.

Result: There is no validation of the Control Amount for standard non-web batches. All standard non-web batches must be closed manually on a daily basis.

PABatch.ValidatePaymentControl = false

and

PANightlyProcess.CloseNonWebBatches = false

Validate payment control for standard web batches

To configure your system to require batch control validation for web batches where batch type is Standard GL Detail Creation, the UX Online parameter PABatchWeb.ValidatePaymentControl must be set to TRUE.

In the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This View opens in a new window. Locate and open the parameter PABatchWeb.ValidatePaymentControl and set the Config Value field as follows:

  • TRUE – Enforce validation of the batch control amount for web batches where batch type Standard GL Detail Creation.

  • FALSE – Do not enforce validation of the batch control amount on web batches.

Click Save & Close to save your change and close the record. Close the View window by clicking the “X” in the upper right hand corner of the window.

Web batch control amount validation when automatically closing web batches

When considering your system settings for validating payment control on web batches, you must also consider your settings for automatically closing web batches. See Automatically closing batches for more information.

When you configure your system to validate the control amount on web batches and to close web batches automatically, you also must configure your system to ignore the control amount validation on web batches during the nightly process that closes web batches by setting the Config value on the PANightlyProcess.WebBatches.ValidateControlAmt application parameter.

In the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This View opens in a new window.

Locate and open the parameter PANightlyProcess.WebBatches.ValidateControlAmt and set the Config Value field as follows:

  • TRUE – Never set this value to TRUE.

  • FALSE – Always set this value to False. Used to ignore validation of the Control Amount on web batches during the nightly process to close web batches when PABatchWeb.ValidatePaymentControl = true and PANightlyProcess.CloseWebBatches = true.

Click Save & Close to save your change and close the record. Close the View window by clicking the “X” in the upper right hand corner of the window.

Sample configuration options for validating control amount and the nightly process for closing web batches:

Business Need for Web Batches

UX Online Application Parameter Configuration Settings

Recommended if you require validation control

You want the system to validate the batch Control Amount against the total payments processed in web batches when a user closes a batch manually AND you want the system to automatically close web batches nightly regardless of the Control Amount.

Result: Validation of the control amount is ignored during the nightly process to close web batches but is enforced when a user closes a web batch manually. All standard web batches are closed automatically by the system during the nightly process.

PABatchWeb.ValidatePaymentControl = true

and

PANightlyProcess.CloseWebBatches = true

PANightlyProcess.WebBatches.ValidateControlAmt = false

Recommended if you do not require validation control

You do not want the system to validate the batch Control Amount against the total payments processed in web batches AND you want the system to automatically close web batches nightly.

Result: There is no validation of the Control Amount on standard web batches. All standard web batches are closed automatically by the system during the nightly process.

PABatchWeb.ValidatePaymentControl = false

and

PANightlyProcess.CloseWebBatches = true

PANightlyProcess.WebBatches.ValidateControlAmt = false

You want the system to validate the batch Control Amount against the total payments processed in web batches AND you do not want the system to automatically close batches nightly.

Result: When a user attempts to close a standard web batch, validation of the Control Amount is enforced. All standard web batches must be closed manually on a daily basis.

PABatchWeb.ValidatePaymentControl = true

and

PANightlyProcess.CloseWebBatches = false

PANightlyProcess.WebBatches.ValidateControlAmt = false

You do not want the system to validate the batch Control Amount against the total payments processed in web batches AND you do not want the system to automatically close batches nightly.

Result: There is no validation of the Control Amount for standard web batches. All standard web batches must be closed manually on a daily basis.

PABatchWeb.ValidatePaymentControl = false

and

PANightlyProcess.CloseWebBatches = false

PANightlyProcess.WebBatches.ValidateControlAmt = false

Batch type controls

When you create a batch in UX Online, you will select a batch type to control the type of transaction processing for that batch. The batch types available are:

  • Standard GL Detail Creation – The standard batch type used for invoice transactions.

  • Membership and Subscriptions Income Recognition – A processing batch type used solely for recognizing deferred revenue from membership and subscription renewal transactions. Batches of this type are automatically marked as closed when they are selected to prevent other users from inadvertently using them for standard transactions.

  • Revenue Recognition by Date – A processing batch type used solely for recognizing deferred revenue from events as of a specified date. Batches of this type are automatically marked as closed when they are selected to prevent other users from inadvertently using them for standard transactions.

  • Revenue Recognition by Event Number – A processing batch type used solely for recognizing deferred revenue by event. Batches of this type are automatically marked as closed when they are selected to prevent other users from inadvertently using them for standard transactions. During the revenue recognition by event process, the system automatically updates the event meeting and exhibit product GL accounts, replacing the deferred by event Primary GL account with the revenue account.

  • Refund Processing – A processing batch type used solely for refund processing, this batch type creates a Payables invoice in Microsoft Dynamics GP for each customer refund that is processed. (This process is available only if your organization purchased the license for the integration with Payables.)

  • Chapter Reimbursement Processing – A processing batch type used solely for processing the reimbursement of chapter membership dues, this batch type creates a Payables invoice in Microsoft Dynamics GP for dues revenue collected on behalf of a chapter. Batches of this type are automatically marked as closed when they are selected to prevent other users from inadvertently using them for standard transactions.

  • Close Date Related Revenue Recognition – A processing batch type used solely for the non-financial process of clearing fully recognized date-related items (membership, subscriptions, and events by date), so they do not continue to appear on the revenue recognition report. Batches of this type are automatically marked as closed when they are selected to prevent other users from inadvertently using them for standard transactions.

This process searches for invoices that have been fully recognized as of a specified date. In this process, the specified date is equal to the batch date. It changes the deferral flag on the related GL Detail records so that they will not continue to show on the Revenue Recognition report or be included in future revenue recognition processes. By eliminating records that would otherwise have been included, the revenue recognition process will run faster.

When you create this batch type, the batch date you enter should be a date when you believe that no entries affecting revenue recognition will be needed for fiscal periods equal to or prior to that date.

Important

You will not be able to reprint Revenue Recognition reports for fiscal periods equal to or prior to the batch date for Close Date Related Revenue Recognition batches.

  • AR Utility – Do not use this batch type without consulting your Protech representative. This processing batch type is used in conjunction with the Control Accrual Basis via AR Utility field on the dues product setup for clients who treat membership dues on an accrual basis rather than a cash basis but do not want to see any AR until the membership year begins.

RapidPay payments controls

UX Online includes batch controls that prevent closing a batch that contains pending RapidPay entries. The RapidPay process includes creating the RapidPay entries in a selected batch and then running the RapidPay Create Payments process. This feature prevents a user from closing any batch with pending RapidPay entries—those that have not been processed through the RapidPay Create Payments Process.

If you attempt to close a batch that contains pending RapidPay entries, you will receive a message stating that you should review the items in the batch and complete the RapidPay process before closing it.

On-hold invoices control

UX Online includes batch controls that prevent closing a batch that contains any invoice with invoice detail line items and a status reason of Hold. These invoices have not been marked as Ready for Close.

If you attempt to close a batch that contains invoices with invoice detail line items and a status reason of Hold, you will receive a message stating that you should review the invoices in the batch and change the status of any that are currently on hold.

To view all invoices in a batch with a status reason of Hold, print the UX Transaction Edit List Report.

Automatically close batches

By default, you must manually close batches before you can create GL detail and post them. However, you can set up you system to automatically close batches on a nightly basis. Before configuring your system to automatically close batches, see Configuring your system to require batch control validation and refer to the sample configuration tables.

Note

This nightly process is a system job that will run at a time set up when your UX Online was configured.

The same batch control mechanisms that apply to manually closing batches will also apply to automatically closing standard batches:

  • If the PABatch.ValidatePaymentControl application parameter is set to TRUE, and a non-web batch’s control amount does not equal the batch total, the batch will not be closed.

  • If the PABatchWeb.ValidatePaymentControl application parameter is set to TRUE, and a web batch’s control amount does not equal the batch total, the batch will not be closed.

Important Note

You can configure your system to ignore the web batch validate payment control when your system is configured to close web batches automatically. See Ignore web batch control amount when automatically closing web batches, below.

  • If a batch includes any invoices that are on hold, the batch will not be closed.

  • If a batch includes any RapidPay payments where the RapidPay Create Payments process has not been run, the batch will not be closed.

You can choose to close your standard batches automatically, your web batches, or both. These default settings are managed by UX Online Application Parameters, as described below.

Configuring your system to close batches automatically

Auto-close standard batches

Set the system to close your standard (non-web) batches automatically by modifying the Config value of the PANightlyProcess.CloseNonWebBatches application parameter.

Important

If you set the Config Value for PABatch.ValidatePaymentControl = True and you set the Config Value for PANightlyProcess.CloseNonWebBatches = True, the system will not close non-web batches where the batch Control Amount does not equal the total payments processed in the batch.

In the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This List View opens in a new window.

Locate and open the parameter PANightlyProcess.CloseNonWebBatches. Set the Config value field to TRUE.

Click Save & Close to save your change. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Auto-close web batches

Set the system to close your web batches automatically by modifying the Config value of the PANightlyProcess.CloseWebBatches application parameter.

In the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This List View opens in a new window.

Locate and open the parameter PANightlyProcess.CloseWebBatches. Set the Config value field to TRUE.

Click Save & Close to save your change. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Ignore web batch control amount when automatically closing web batches

If you have configured your system to close web batches automatically and to validate the control amount on web batches, you must configure your system to ignore the control validation during the nightly process that closes web batches by setting the Config value on the PANightlyProcess.WebBatches.ValidateControlAmt application parameter.

In the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This List View opens in a new window.

Locate and open the parameter PANightlyProcess.WebBatches.ValidateControlAmt and set the Config Value field as follows:

  • TRUE – Do not use this Config value without consulting your Protech representative.

  • FALSE – Always set Config value to False. When PABatchWeb. When ValidatePaymentControl = true and PANightlyProcess.CloseWebBatches = true, set the Config value for PANightlyProcess.WebBatches.ValidateControlAmt = false to ignore validation of the batch control amount on web batches during the nightly process to automatically close web batches.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Creating a batch in UX Online

Before you can enter transactions in UX Online, you must create batches. A batch is a control mechanism that assigns an ID and date to every invoice transaction entered into the system. In most organizations, each batch is closed at the end of the business day so no other transactions can be entered into it and the accounting department can reconcile the money entered into that batch with the daily bank deposit. Once the batch is reconciled, the batch is then posted to the accounting system (either Microsoft Dynamics GP or Microsoft Dynamics SL).

You must create separate batches for each company.

You should create batches that meet the requirements of your organization’s policies and procedures regarding the entry of cash, check, and credit card payments, and adjustment transactions.

Important

Protech recommends that your organization use separate daily batches for credit card charges and for cash and checks payments in order to reflect this activity accurately on the General Ledger and the Bank Statement.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window. In the Batch Log list, click New on the toolbar.

In the General section of the Batch Log record, enter the general batch setup information:

  • Description – Enter a description for this batch. When this batch is posted, the entry here will appear in the Reference field in the accounting system’s general ledger transaction entry window. If you are integrating with Microsoft Dynamics GP, note that there is a 30-character limit. This description also appears as the Batch Name in the Comments field in the Batch header file in Microsoft Dynamics GP.

  • Batch Number – Displays an automatically generated number. The number increases by one each time you Save a new batch. This number will appear in the batch ID field in the accounting system’s general ledger transaction entry window.

  • Batch Date – This field defaults to the system date. This will be the transaction date when this batch is posted to the accounting system, and will appear in the transaction date field in the accounting system’s general ledger transaction entry window. If this is not correct, edit the date as required.

Note

Because the batch date is the date the journal entry posts into the accounting system, be sure you enter the correct date.

If the batch type is Close Date Related Revenue Recognition, the batch date you enter controls how the system searches for fully recognized invoices. See the Batch Type information below for more information.

  • Batch Type – Select the type for this batch, based on the type of transactions you are creating this batch for:

    • Standard GL Detail Creation – Select this option if you are going to use this batch for invoice transactions.

    • Membership and Subscriptions Revenue Recognition – This is a utility process batch type. Select this option if you are going to use this batch for recognizing deferred income from membership and subscription renewal transactions. When you select this type, the batch will automatically be marked as closed to prevent other users from inadvertently using it for standard transactions.

    • Revenue Recognition by Date – This is a utility process batch type. Select this option if you are going to use this batch for recognizing portions of the revenue for an ongoing event or course by date. When you select this type, the batch will automatically be marked as closed to prevent other users from inadvertently using it for standard transactions.

    • Revenue Recognition by Event – This is a utility process batch type. Select this option if you are going to use this batch for recognizing all of an event’s deferred revenue at once, after the event is over and all of the associated transactions have been entered and posted. When you select this type, the batch will automatically be marked as closed to prevent other users from inadvertently using it for standard transactions. During the revenue recognition by event process, the system automatically updates the event meeting and exhibit product GL accounts, replacing the deferred by event Primary GL account with the revenue account.

    • Refund Processing – This is a utility process batch type. Select this option if you are going to use this batch for refund processing (which is available if your organization purchased the license for the integration to Payables). When you select this type, the batch will automatically be marked as closed to prevent other users from inadvertently using it for standard transactions.

    • Chapter Reimbursement Processing – This is a utility process batch type. Select this option if you are going to use this batch for processing the reimbursement of chapter membership dues. When you select this type, the batch will automatically be marked as closed to prevent other users from inadvertently using it for standard transactions.

    • Close Date Related Revenue Recognition – This is a utility process batch type. Select this option if you are going to use this batch to clear fully recognized items—including membership, subscriptions, and events—so they no longer appear on the Revenue Recognition Report. When you select this type, the batch will automatically be marked as closed to prevent other users from inadvertently using it for standard transactions.

This process searches for invoices that have been fully recognized as of a specified date. In this process, the specified date is equal to the batch date. It changes the deferral flag on the related GL Detail records so that they will not continue to show on the Revenue Recognition report or be included in future revenue recognition processes. By eliminating records that would otherwise have been included, the revenue recognition process will run faster.

The batch date you enter should be a date when you believe that no entries affecting revenue recognition will be needed for fiscal periods equal to or prior to that date.

Important

You will not be able to reprint Revenue Recognition reports for fiscal periods equal to or prior to the batch date for Close Date Related Revenue Recognition batches.

    • AR Utility – This is a utility process batch type. Do not select this option without consulting your Protech representative. This utility is used in conjunction with the Control Accrual Basis via AR Utility field on the due product setup for clients who treat membership dues on an accrual basis rather than a cash basis but do not want to see any AR until the membership year begins.

  • Event – If this batch will be used for revenue recognition for a specific event (that is, if you selected Revenue Recognition by Event as the batch type), click the Lookup button to select the event. Otherwise, leave this field blank.

  • Company – Click the Lookup button to select the company in the accounting system where you want this batch posted.

  • Closed – If this is a Standard GL Detail Creation batch, mark this checkbox if you want to prevent any more transactions from being added. If the batch type is one of the system process types, do not change this checkbox. It is automatically marked to prevent users from inadvertently using a system process batch for standard transactions.

  • Web Batch – If this batch was created from MX Online, Yes will be marked. Do not change this field.

  • Control Amount – Enter a dollar amount to use as a control for this batch. If you are using batch control amount validation, the net payment transaction total for the batch must match this amount before you can close the batch. For more information, see Batch controls overview.

  • Owner – Displays the user ID of the user who owns this record.

  • History Store Created – System managed field that indicates whether History Store records were created for this batch during the Nightly Process on closed batches. Do not change the value of this field. When creating a new batch, the default for this field is No, indicating that History Store records have not yet been created. When the batch is closed and the Nightly Process creates History Store records, the system updates this field to Yes.

In the GL Detail Information section of the Batch Log record, the following fields are used for managing your batch in preparation for creating GL detail:

  • Ready for GL Detail – Do not mark or unmark this checkbox from within the batch log record. You must manage this field in either the Standard GL Detail grid or the Special GL detail grid. If checked and enabled, this field indicates that this batch has been marked in the GL Detail grid for creating GL detail the next time the Create GL Detail-Post to Accounting Process is run. For more information, see Creating GL detail for a batch.

  • GL Detail Created – Indicates whether GL detail was created. The system manages this field and it cannot be edited.

  • Created Date – Displays the date that GL detail was created. The system manages this field and it cannot be edited.

In the Accounting System Posting section of the Batch Log record, the following fields are used for managing your batch in preparation for posting the GL detail to your accounting system:

  • Ready to Post – Do not mark or unmark this checkbox from within the batch log record. You must manage this field in either the Standard GL Detail grid or the Special GL detail grid. If checked and enabled, this field indicates that the batch has been marked in the GL Detail grid for posting the next time the Create GL Detail-Post to Accounting Process is run. For more information, see Creating GL detail for a batch and Posting a batch.

  • Posted – Indicates whether the batch has been posted. The system manages this field and it cannot be edited.

  • Posted Date – Displays the date that this batch was posted. The system manages this field and it cannot be edited.

Note

The date the transactions will post in your accounting system will be the batch date, even if you post the batch on a later date.

In the Notes section, view existing Notes or click Add a new note to add a text note for this record.

In the Administration section, view the user who created this record, when it was created, the user who last modified this record, when it was modified, and the batch Currency.

Click Save & Close to save this record and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Closing a batch in UX Online

Before you can process a batch for GL Detail or Post to Accounting, you must first close your batch.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window. In the Batch Log list, locate and open the batch you want to close. The batch log record will open in a new window.

In the General section of the Batch Log record, select Closed to mark this batch closed.

Note

If your system is configured to validate batch payment control, you may receive a Business Process message indicating that the batch control amount does not equal the net amount of transactions in this batch. You must correct the control amount before you can close the batch.

If the batch includes pending RapidPay entries, you will not be able to close it. You must run the process to create the payment transactions. For more information, see Creating RapidPay payment transactions.

Do not select the Ready for GL Detail or Ready to Post checkboxes when closing the batch. These fields must be managed in either the Standard GL Detail grid or the Special GL grid. For more information, see Creating GL detail for a batch.

Save & Close the batch log record to return to the list view of records.

Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Creating GL detail for a batch

Before a batch can be posted, you need to create the detailed journal entries of the debits and credits associated with the transactions in the batch, otherwise known as General Ledger Detail records or GL Detail records. At the invoice level, you can view system-created General Ledger Detail records that have been created for that invoice’s transactions by navigating to General Ledger Details located in the Navigation Pane of an invoice.

To create GL detail for a batch, in the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management. There are two menu items for managing closed batches and the Create GL Detail-Post to Accounting processes.

  • Standard GL Detail – used only for batch type = Standard GL Detail

  • Special GL – used only for all other batch types

Each menu item opens a grid of closed batches that are available for creating GL detail and or posting to accounting. They are the UX Online tools for marking your batches as Ready for GL Detail, Ready to Post, and initiating the processes that actually create GL detail and post the batch.

You can mark one or more batches as Ready for GL Detail, with or without marking them Ready for Post. By selecting only the Ready for GL Detail checkbox, you can create GL Detail for marked batches without posting. If you select both the Ready for GL Detail and the Ready to Post checkboxes, you can run both processes – all based on your selections. The only restriction is that you cannot mark a batch Ready to Post if it is not marked Ready for GL Detail.

If the Ready for GL Detail checkbox is checked and disabled on the grid, this indicates that you have already created GL detail for that batch. That batch is ready for posting.

Important

If you marked the checkbox for Ready for GL Detail within the actual batch log record instead of using the grid, it will also appear as checked and disabled in the grid. However, UX does not recognize a batch that you mark manually inside the batch log record when running the Create GL Detail or Posting processes from the grid.You must used the grid to mark your batches as Ready for GL Detail and/or Ready to Post.

The processes that create GL detail and post batches are initiated by selecting OK in the grid. They run on the marked batches – depending on the checkboxes marked in the grids.

Selecting Standard GL Detail will open the Standard GL Detail grid dialog. This grid lists all closed batches where batch type = Standard GL Detail, which have not been processed for GL detail or that have been processed for GL Detail but not yet processed for posting.

Selecting Special GL will open the Special GL Detail grid dialog. This grid lists all closed batches where batch type does not equal Standard GL Detail, which have not been processed for GL detail or that have been processed for GL detail but not yet processed for posting.

Using the checkboxes, select one or more batches to Create GL Detail. Select OK to initiate the process. After the process is complete, select Close to close the processing window.

Important Note

You can mark both the Ready for GL Detail and the Ready to Post checkboxes at the same time, but you cannot mark the Ready to Post checkbox if the Ready for GL Detail has not been marked. Select OK to initiate the process. To Create GL Detail only without Posting to Accounting, mark only the checkbox for Ready for GL. The process will run based on the marked checkboxes.

Upon completion of the Create GL Detail process, the system will update the batch log record fields GL Detail Created = Yes and Created Date = [system date]. If there is no GL detail created for a batch when the Create GL Detail – Post to Accounting process is run, in addition to updating the batch GL Detail Created = Yes and Created Date = [system date] fields, the system will automatically update the batch Posted = Yes and the Posted Date = [system date] because there is no GL detail in the batch to post to the accounting system.

Review the journal entries by printing either the UX Account Distribution Detail Report or the UX Account Distribution Summary Report. For more information, see GL posting reports.

Note

If you discover a mistake in a transaction after creating GL detail or after posting, you can reset the batch and correct the error. For more information, see Resetting a batch.

Posting a batch

If your system is integrated with a back-office financial application, posting a batch in UX Online transfers the GL detail in summary to Microsoft Dynamics GP or Microsoft Dynamics SL, where they will be saved in a General Ledger batch, ready to post and update the account balances in the period that includes the batch date.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management. To process Standard GL Detail batches, select Standard GL Detail. To process all other batch types, select Special GL.

Selecting Standard GL Detail will open a new window listing closed batches where batch type = Standard GL Detail that have not been processed for GL Detail and/or Post to Accounting.

Selecting Special GL will open a new window listing closed batches where batch type ≠ Standard GL Detail that have not been processed for GL Detail and/or Post to Accounting.

Using the checkboxes, select one or more batches to process. Select OK to initiate the process. After the process is complete, select Close to close the processing window.

If GL detail has already been created for this batch, the GL Detail Created field will be checked. If it has not been created, you must mark the Ready for GL Detail checkbox before you mark the Ready to Post checkbox.

Important

You can mark both the Ready for GL Detail and the Ready to Post options at the same time, but you cannot mark the Ready to Post option if the Ready for GL Detail option has not been marked.

Upon completion, the system will update the batch fields Posted = Yes and Posted Date = [system date].

Review the journal entries by printing either the UX Account Distribution Detail Report or the UX Account Distribution Summary Report. For more information, see GL posting reports.

After posting, we recommend that you verify the batch in your financial application. For more information, see Validating posting in Microsoft Dynamics GP General Ledger or Validating posting in Microsoft Dynamics SL.

Note

If you discover a mistake in a transaction after creating GL detail or after posting, you can reset the batch and correct the error. For more information, see Resetting a batch.

GL posting reports

The following are the UX Online reports that show the General Ledger information that will be updated when you post batches.

  • UX Account Distribution Detail Report – Displays detail journal entry information for all transactions in a batch range, sorted by batch.

  • UX Account Distribution Detail Report by GL Account – Displays detail journal entry information for a specified account for all transactions in a batch date range, sorted by batch.

  • UX Account Distribution Detail Report by GL Account Excel Report – a Displays detail journal entry information for a specified account for all transactions in a batch date range, sorted by GL Account and batch. Report is designed for exporting report result to Microsoft® Excel.

  • UX Account Distribution Summary Report – Displays summary journal entry information for all transactions in a batch range, sorted by batch.

  • UX Account Distribution Summary Report by GL Account – Displays summary journal entry information by account for all transactions in a batch range.

  • UX Account Distribution Summary by GL Account Excel Report – Displays summary journal entry information for all transactions in a batch range, sorted by GL Account and batch. Report is designed for exporting report result to Microsoft® Excel.

Validating posting in Microsoft Dynamics GP General Ledger

When you post a batch in UX Online, it appears in Microsoft Dynamics GP in summary as a general journal transaction. We recommend that you view the transaction in Microsoft Dynamics GP to verify the amounts before posting it. In Microsoft Dynamics GP, click Transactions > Financial > General to open the Transaction Entry window, and then click the lookup button on the Journal Entry field to locate and select the transaction. The transaction’s batch ID will be the same as the batch number in UX Online, and the reference will be the batch reference from UX Online.

Warning

If you find errors in the transaction, do not modify the journal entry here. In order to maintain the integrity of the data in both UX Online and Microsoft Dynamics GP, do not modify this journal entry. If there is an error in this journal entry, delete it from Microsoft Dynamics GP, and reset the batch in UX Online. (For more information, see Resetting a batch.) Then you can make the necessary corrections in UX Online, create GL detail, and re-post the batch in UX Online.

The following table shows the batch fields in UX Online and the corresponding fields in Dynamics GP.

UX Online Field

Microsoft Dynamics GP Field

Batch Number

Batch ID

Batch Date

Transaction Date

Batch Reference

Reference

Currency

Currency ID

Accounts – Debits and Credits Accounts – Debits and Credits

Note

If the batch includes multicompany transactions, the Intercompany checkbox in the Microsoft Dynamics GP window will be marked.

You must post this transaction in Microsoft Dynamics GP to update your general ledger accounts. There are three methods to post a transaction in Microsoft Dynamics GP:

  • Batch Posting

  • Series Posting

  • Master Posting

For more information about these posting methods, refer to the Microsoft Dynamics GP on-line help or documentation.

Validating posting in Microsoft Dynamics SL

When you post a batch in UX Online, it appears in Microsoft Dynamics SL as a General Ledger journal transaction, with the Status field set to “On Hold” and the Released field set to “Balanced.” We recommend that you view the transaction in Microsoft Dynamics SL to verify the amounts before posting it. In Microsoft Dynamics SL, click General Ledger > Input > Journal Transactions. Use the F3 Key on the Batch ID to open the journal entry. Always refer to Dynamics SL user documentation for validating posting.

The transaction’s batch number is assigned automatically by Microsoft Dynamics SL. The UX Online batch ID will appear in the Description and Reference columns of the detail section in the journal entry. The Status field will be set to On Hold, and the Released field will be set to Balanced.

Warning

If you find errors in the transaction in Microsoft Dynamics SL, do not modify the journal entry here. In order to maintain the integrity of the data in both UX Online and Microsoft Dynamics SL, do not modify this journal entry. If there is an error in this journal entry, delete it from Microsoft Dynamics SL, and reset the batch in UX Online. (For more information, see Resetting a batch.) Then you can make the necessary corrections in UX Online, create GL detail, and re-post the batch in UX Online.

The following table shows the batch fields in UX Online and the corresponding fields in Microsoft Dynamics SL.

UX Online Field

Microsoft Dynamics SL Field

Batch Number

The UX Online Batch Number appears in the Ref Nbr field of each detail line in the Journal Transaction with CRM as a prefix.

Batch Description

The UX Online Batch Description appears in the Description field of each detail line in the Journal Transaction with a limited number of characters.

Batch Date

Period in the Header( MM-YYYY format) and Date in the Detail (MM-DD-YY format)

Accounts – Debits and Credits

Accounts – Debits and Credits

You must post this transaction in Microsoft Dynamics SL to update your general ledger accounts. The procedures involved in posting a transaction in Microsoft Dynamics SL are:

  • Release GL Batches

  • Post Transactions

For more information about these posting procedures, refer to the Microsoft Dynamics SL on-line help or documentation.

Resetting a batch

If you discover a data entry error in batch that has already had GL detail created or has been posted, you can reset the batch, and then make the necessary changes.

Resetting a batch moves the batch back one step in the process of creating GL detail and posting. If you reset the batch after GL detail has been created but before posting, the system will create reversing journal entries when you re-create the GL Detail. If you reset the batch after it has been posted, you will be able to re-post the batch to your accounting system.

Important

Do not use this procedure for batches that cannot be posted due to batch errors. For more information about resolving these issues, see Resolving posting errors.

If you discover the error after creating GL detail but before posting, resetting the batch does the following:

  • Changes the Ready for GL Detail field from Yes to No.

  • Changes the GL Detail Created field from Yes to No.

  • Deletes the date in the Created Date field.

After you correct the error, you must create the GL detail again before posting the batch.

If you discover the error after posting the batch, resetting the batch does the following:

  • Changes the Ready to Post field from Yes to No.

  • Changes the Posted field from Yes to No.

  • Deletes the date in the Posted Date field.

You will need to reset the batch again before you can make any changes to the transactions.

Important

Resetting a batch that has been posted does not make any changes to the information posted to your accounting system. You must manually delete or void the transactions in your accounting system.

Reset an unposted batch

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window. In the Batch Log list, locate and open the batch you want to reset. The batch log record will open in a new window.

In the batch log record, select Reset Batch on the Record toolbar.

The GL Detail Created option will reset to No. You can now unmark the Closed checkbox, make any necessary changes to the transactions in the batch, and then mark the batch as Closed. When you process the batch to create GL detail, the existing GL detail for this batch will be deleted and replaced with new, correct GL detail.

Reset a posted batch

IMPORTANT: If the batch has been posted to your accounting system, you must address the batch from within your accounting system. If the batch has not been posted within your accounting system, delete it. If you have already posted the batch within your accounting system, you must void or reverse the transactions in that batch.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window. In the Batch Log list, locate and open the batch log record you want to reset. The batch log record will open in a new window.

In the batch log record, select Reset Batch on the Record toolbar.

The Posted option will be reset to No, but the GL Detail Created option will still be Yes. You must reset the batch again before you will be able to correct the transaction error.

Diagnosing batch posting

If you are having issues with batch posting, you can use Batch Posting Diagnostics to review the services that are running and try to isolate the problem. This dialog displays your accounting server settings, the SQL Agent status, whether the standard GL detail creation, non-standard GL batches (revenue recognition, refund processing, and chapter reimbursement), the accounting system refresh posting jobs are enabled, and the posting status.

Note

You can only review information about the services that are running; you cannot take any action.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Posting Diagnostics.

The Batch Posting Diagnostics dialog displays messages about the status of the system components that manage the posting process. The possible messages include:

  • Accounting Server Settings (ignores inactive accounting companies when the Global Default Settings = Dynamics GP or Dynamics SL)

    • Please check accounting server if accounting server has been assigned for all UX Online companies

    • OK

  • SQL Agent Status (checks the agent that manages SQL jobs; if the server has been rebooted, the SQL agent must be restarted)

    • You do not have privileges (Sys Admin) to check this

    • Running

  • Posting Job – General Ledger (indicates whether the SQL posting jobs are active or disabled)

    • Enabled

    • Disabled

  • Posting Job – GL Special

    • Enabled

    • Disabled

  • Posting Job – Accounting System Refresh

    • Enabled

    • Disabled

  • Current Posting Status (indicates whether the SQL posting job is running or idle)

    • Idle

    • Posting in Progress

Resolving posting errors

In rare cases, a batch might not complete the posting process correctly. The steps needed to resolve this depend on whether the problems occurred while creating GL detail or while posting to accounting.

If the problem occurs while the system is attempting to create GL detail, the GL Detail Created field on the Batch Log record will display the message “Error – See Batch Error Report.” The batch will remain closed.

If the problem occurs while the system is attempting to post the batch to accounting, the Posted field on the Batch Log record will display the message “Error – See Batch Error Report.” The batch will remain closed, and the batch will be updated as follows:

  • The Ready for GL Detail field will be changed from Yes to No.

  • The GL Detail Created field will be changed from Yes to No.

  • The date in the Created Date field will be deleted.

  • The Ready to Post field will be changed from Yes to No.

Typical errors include the following:

  • Account not found in GL master – This indicates that the GL account in UX Online does not exist in the accounting system.

  • Product contains errors – This indicates that the product record has missing GL accounts.

  • Batch does not balance – This indicates that the debits and credits in the batch are not equal.

  • Invalid Chapter Vendor Number – This indicates that a chapter does not have a Microsoft Dynamics GP vendor ID assigned to it.

  • SQL Server Agent located on the SQL server is not running.

Important

Do not use the Reset Batch button for batches that have posting errors. Resetting a batch with posting errors will not clear the error.

Resolving GL detail creation errors

  • Print the UX Batch Error Report to identify the error.

  • Resolve the error.

  • Repeat the create GL detail procedure.

Note

Setting the Ready for GL Detail field to Yes will clear the error message from the GL Detail Created field.

Resolving post to accounting errors

  • Print the UX Batch Error Report to identify the error.

  • Resolve the error.

  • Repeat the create GL detail and posting procedures.

Note

Setting the Ready for GL Detail field to Yes will clear the error message from the GL Detail Created field.

Chapter 14: Integration with Bank Reconciliation

This documentation describes the integration between UX Online and Dynamics GP Bank Reconciliation.

Note

To use the Bank Reconciliation integration, you must have the Bank Reconciliation module, and you must have purchased the companion UX Online module license for this feature.

In addition to the Bank Reconciliation integration, you can also use the Cash Reconciliation list to view all of your cash transactions, and assign them to deposit IDs.

This information includes the following topics:

  • Enabling the Bank Reconciliation integration

  • Bank Reconciliation and payment products

  • Posting deposits in UX Online

  • Posting deposits in Microsoft Dynamics GP

  • Cash reconciliation

Enabling the Bank Reconciliation integration

If you have purchased the integration with Dynamics GP Bank Reconciliation, payment transactions in UX Online can create deposit transactions in the Dynamics GP Bank Reconciliation module. You must enable the Bank Reconciliation integration for each company where you want to use it. In addition, you must indicate whether you want to post deposit transactions in detail—that is, one entry per payment product on each invoice in a batch—or in summary—that is, one entry per payment product in a batch.

To enable Bank Reconciliation integration, in the Navigation Tile Bar, select the Administration work area > UX Settings > Accounting Company and Charts of Account Settings > Companies to open the Active Companies View. This View opens in a new window. Locate and open the Company record where you want to enable Bank Reconciliation. The record will open in a new window.

In the Company record, set the Post to Dynamics GP Bank Rec option to Yes.

Set the Post to Bank Rec in Detail option as follows:

  • If you want to post in detail, set the option to Yes. When you use this setting and post a deposit to Dynamics GP, the Number field on the Bank Deposit Entry window will display the batch number, the payment product ID, and the invoice number for each transaction in the deposit.

  • If you want to post in summary, set the option to No. When you use this setting and post a deposit to Dynamics GP, the Number field on the Bank Deposit Entry window will display the batch number, the payment product ID, and the date that the batch was created in UX Online. (The date will appear in YYYYMMDD format.)

Bank Reconciliation and payment products

Several of the payment products that are set up in your UX Online system—check or cash, credit card, lockbox, and miscellaneous unapplied payments—can be linked to a checkbook in Dynamics GP. If you want to link a payment product to a Dynamics GP checkbook, the Checkbook ID field on the Product record in UX Online must have the checkbook ID exactly as it appears in Dynamics GP.

In addition, the currency, company, and primary GL Account of the payment product must be the same as the company, currency, and cash account for the checkbook record in Dynamics GP.

When you have linked a payment product to a Dynamics GP checkbook, posting transactions that include that payment product will create deposit entries for that checkbook in the Bank Reconciliation module, in either detail or summary, depending on your system setup. (For more information, see Enabling the Bank Reconciliation integration.)

If you do not have a checkbook ID entered for a payment product, and your system is integrated with Bank Reconciliation, the system will attempt to identify the correct checkbook by matching the payment product’s currency and primary GL account against the currency and cash accounts for the checkbooks in Dynamics GP.

Posting deposits in UX Online

If you are using the Bank Reconciliation integration, payments recorded in UX Online are saved in batches that post to Dynamics GP General Ledger and Bank Reconciliation in summary or in detail, depending on your system setup. (For more information, see Enabling the Bank Reconciliation integration.) Each posting to Bank Reconciliation will be recorded as a deposit.

Note

Because checks, American Express, Visa, and MasterCard payments take different amounts of time to deposit, Protech recommends your organization use separate daily batches for each type of payment—cash and check payments, American Express payments, and Visa and Master Card payments, for a total of three payment batches. This batch method will assist in easily matching your organization’s bank statement to deposits recorded.

After running the Post to Accounting process on the deposit batch in UX Online, you must post the deposit in Dynamics GP. For more information, see Posting deposits in Microsoft Dynamics GP.

Posting deposits in Microsoft Dynamics GP

After posting the deposit batch in UX Online, you must also post the deposit in the Dynamics GP Bank Reconciliation module to update the checkbook balance.

Posting the batch in UX Online transfers journal entries to update the General Ledger Cash account in summary. In addition, posting creates a Deposit with Receipts transaction in the Bank Reconciliation module to update the checkbook balance. When you post the Deposit with Receipts transaction in Dynamics GP, the checkbook balance will be updated, but the General Ledger Cash account will not be changed because it was already updated by the UX Online posting process.

For example, assume you have a UX Online batch that contains check transactions to pay for inventoried items. When you post this batch, the Dynamics GP modules that are affected are:

  • General Ledger (Transactions > Financial > Batches) – Contains summarized journal entries created by the UX Online Create GL Detail process.

  • Inventory (Transactions > Inventory > Batches) – Contains the variance or adjustment inventory transactions from product sales invoices in UX Online.

  • Bank Reconciliation (Transactions > Financial > Bank Deposits) – Contains the deposit from check, cash, or credit card payment products included in the UX Online batch.

You will use the Bank Deposit Entry window in Dynamics GP to choose the receipts to deposit. All of the selected checkbook’s receipts from UX Online that are available for deposit appear in the window. After you post a Deposit with Receipts transaction, the receipts will not be available for future deposits.

In Dynamics GP, open the Bank Deposit Entry window (Transactions > Financial > Bank Deposits). In the Option field, select Enter/Edit, and in the Type field, select Deposit with Receipts.

  • Enter the deposit date, which should be the same date the batch was posted in UX Online.

  • Enter or select the checkbook ID and the description for this deposit transaction. (The next available deposit number appears when you select the checkbook ID.)

  • The UX Online deposits that have not been checked for posting will appear in the scrolling window.

  • Mark the checkbox for each line that you want to include in this deposit. To mark or unmark all of the lines, click Mark All or Unmark All. The deposit amount at the bottom of the window will be updated each time you mark or unmark a line.

Note

We recommend that you record each type of deposit (cash and check, Visa and MasterCard, and American Express) separately, since the will appear on your bank statement as separate deposits.

  • To print a Bank Deposit Worksheet, which you can use to verify the receipts, click File > Print.

  • Click Post to post the deposit.

Cash reconciliation

You can use the UX Online Cash Reconciliation list to view all of the cash, check, and credit card transactions from your accounts and contacts.

Note

The system creates cash reconciliation records for cash and check payments at the time you create the payment transaction. The system creates cash reconciliation records for credit card payment transactions after they captured in the Delayed Capture process. The system creates cash reconciliation records for credits to credit card transactions at the time you process the credit transaction.

To view this list, in the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Cash Reconciliation. This list will open in a new window.

You can sort the information in this list by clicking the column headings, and you can create your own views to group the transactions by criteria that meet your needs.

You can also use this list to select individual transactions or groups of transactions and assign them to a deposit ID. To assign a deposit ID to a single transaction, locate and open the entry in the Cash Reconciliation list and then enter the deposit ID.

To assign a deposit ID to a group of transactions, hold down the Ctrl button and click on the records you want in the Cash Reconciliation list, then click Edit on the toolbar. In the Edit Multiple Records record, enter the deposit ID for this group of deposit transactions, and then click Save.

Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Chapter 15: RapidPay Processing

You will use the UX Online RapidPay feature to apply a customer’s single check or credit card payment to multiple invoices for that customer. You can use RapidPay to apply a customer payment to any invoices your organization uses—membership dues, sales, subscriptions, meeting registrations, and so on—as well as miscellaneous payments and contributions.

This information includes the following topics:

  • RapidPay process overview

  • Entering and distributing payments in RapidPay

  • Controlling how RapidPay applies payments

  • Creating RapidPay payment transactions

  • About contributions in RapidPay

  • Processing a returned (NSF) check originally processed through RapidPay

  • Reversing a credit card transaction originally processed through RapidPay

RapidPay process overview

You can use the UX Online RapidPay feature to speed data entry when you are recording customer payments. With RapidPay, you can easily apply a single payment to more than one invoice for the same invoice BillTo customer. In addition, you can record all or a portion of the payment as a contribution, or as a miscellaneous unapplied payment.

The RapidPay process includes two main procedures. First, you will enter the basic payment information and choose the invoices where you want to apply the payment. (For more information, see Entering and distributing payments in RapidPay.) Then you will launch the process of actually creating the payment invoice detail line items in the selected invoices for the payment amounts you entered. (For more information, see Creating RapidPay payment transactions.)

Entering and distributing payments in RapidPay

If a customer has sent a single check or provided credit card information to pay for multiple open invoices, you can quickly apply that payment to those invoices using RapidPay. This procedure shows how to perform the first step in using RapidPay, selecting the invoices and entering the payment amounts you want applied to them. When you have finished this procedure, you will actually create the payment line items in the invoices. For more information, see Creating RapidPay payment transactions.

Note

Before you begin processing payments with RapidPay, be sure that the daily batches needed for cash, check, and credit card payments have been created. For more information, see Integration with General Ledger.

Entering the payment

In the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > RapidPay > RapidPay Payments, to open the Active Rapid Pay List View of existing RapidPay payment record. This list opens in a new window.

Click New on the RapidPay Payments list Actions toolbar to open the Payment Entry record.

  • In the Member ID field, enter the account number or the contact number of the customer making the payment – that is, the invoice Bill To customer. If you do not know the account or contact number, click the Customer Lookup button on the Record toolbar to lookup and select the appropriate invoice Bill To account or contact. All of the open invoices (that is, invoices with a balance due greater than zero) where the customer is entered in the invoice Bill To field appear in the Invoice list.

  • Click the Currency Lookup button to select the appropriate currency for the RapidPay payment.

  • Click the Select Batch button on the Record toolbar to lookup and select the appropriate batch for this RapidPay payment.

  • Click the Payment Product Lookup button to select the type of payment you are entering. For example, if you are recording a check payment, select the check/cash payment product. If you are recording a credit card payment, select the appropriate credit card payment product. Only those payments types that match the batch company and your selected currency will be available for selection.

  • Enter the payment amount in the Amount $ field.

  • If you are recording a check payment, enter the check number in the Reference\Credit Card No. field. If you are recording a credit card payment, enter the credit card number in the field.

  • If you are entering a credit card payment, enter the expiration date in MMYY format in the Expiration Date field; otherwise, leave this field blank.

  • If you are entering a credit card payment and your organization’s business rules require it, enter the three or four security code from the credit card in the CVV2 field; otherwise, leave this field blank. If a code is entered, the code will be transmitted with the credit card number and expiration date to the processor for verification. (When the credit card payment is authorized, this information is removed.)

  • If the Bill To customer selected is a contact record, the Name on Card field defaults to the first and last name of the contact. If the Bill To customer selected is an account record, the Name on Card field defaults to the first and last name of the primary contact for the account. This field can be edited as necessary prior to saving the RapidPay payment. This data is used primary for credit card payments.

  • Click Save.

Upon Save, the total open AR for the selected Bill To customer appears at the bottom of the payment entry record.

  • If you are entering a check payment, clicking Save will disable all payment related fields on the payment record except Amount, where the user has the option to edit the amount of the check payment.

  • If you are entering a credit card payment, clicking Save will validate the credit card information you entered and attempt to authorize the credit card through PayPal. If the payment is authorized, the bottom left part of the record displays Credit Card Status: Approved. The fields in the header will be locked, and you will not be able to make any changes.

  • If authorization fails, you must either correct the information entered and Save in order to achieve authorization or close the record by clicking the File Menu button and clicking Close. If you attempt to use the Save & Close button without correcting the information, UX Online will attempt to authorize the payment again.

At the bottom of the payment entry record, you can view the RapidPay totals:

  • Total of Open AR – displays the total open AR in the selected currency for the selected Bill To customer.

  • Total AR Payments – dynamically displays the total AR payments as the payment is distributed to the invoices displayed.

  • Other Payments – dynamically displays the total other payments (i.e., monetary contribution) as the payment is distributed

  • AR Balance – dynamically displays an updated AR balances as payment is distributed to the invoices displayed.

  • Available Distribution Total – dynamically displays the amount available for distribution as payment is distributed.

Distributing the payment

All of the open invoices (that is, invoices with a balance due greater than zero) where that customer is entered in the invoice Bill To field appear in the Invoice list. You can apply the payment to invoices automatically or manually.

  • To automatically apply the payment amount to the invoices, click Auto Apply. The system will apply the payment amount to the open invoices, beginning with either the newest invoice, or the oldest invoice (depending on how your system is set up), until the total amount of the payment is distributed. If only one invoice appears, the amount applied is the balance due. (For more information on setting up the Auto Apply option, see Controlling how RapidPay applies payments.)

  • To manually enter the amount you want applied to each invoice, mark the Distribute checkbox next to an invoice in the list, enter the amount you want to apply, and click Save to save your manual distributions.

Note

You can change the sorting order of the invoices by clicking the column headings of the invoice list. For example, you could sort the invoices by date. However, regardless of how you sort the invoices, clicking the Auto Apply button will apply the payment to either the newest or the oldest invoice first, depending on how you have set this option up. If you manually distribute the payment to the invoices, you must click Save to save your manual distributions. If you do not Save, the manual distributions will be lost when you close the RapidPay record.

If your organization has set up a monetary contribution product to be available in RapidPay, it will appear in the invoice list. You can distribute all or a portion of the payment to these line items. For example, a contact may have a $100 invoice, and has sent a $150 check, with instructions to apply the excess to a fundraising drive. You can apply $100 to the invoice, and the remaining $50 to the monetary contribution product. (For more information, see About contributions in RapidPay.)

Note

If the payment amount is greater than the total amount due of all the invoices, , you can manually apply the remaining payment amount as a monetary contribution. If the payment source is a check, you can also apply the remaining amount as an overpayment on one of the invoices. If you apply the check payment as an overpayment, the invoice will have a credit balance, which you can then transfer to another invoice or refund. You cannot distribute an overpayment to an invoice when the payment source is a credit card – you must apply the remaining amount as a monetary contribution. The payment amount must equal the total of the amounts distributed. In other words, the Available Distribution Total at the bottom of the payment record must equal 0.00.

Continue distributing amounts to the invoices until you have fully applied the payment amount, and then click Save just above the column headings in the invoices grid.

Important Note

When you finish distributing the last payment, you must click Save to save your payment distribution before you Save & Close the record. Otherwise, your payment distributions will be lost.

Then click Save & Close to save and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Controlling how RapidPay applies payments

When you enter a payment using RapidPay, you can apply amounts to invoices manually, or you can allow UX Online to apply payment amounts automatically. If you choose to apply the amounts automatically, the payment will be applied to the oldest invoice first and working up to the newest (until the payment amount is fully applied), or to the newest invoice first and working down to the oldest, depending on how your system is set up. You can control how the payment is applied by setting the value of the PARapidPay.AutoApplySort application parameter.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters. This list will open in a new window. Locate and open the parameter PARapidPay.AutoApplySort.

Set the Config value field as follows.

  • NEWEST – Enter this if you want payments applied to the newest invoices first.

  • OLDEST – Enter this if you want payments applied to the oldest invoices first.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Creating RapidPay payment transactions

After you have entered RapidPay payment information for check or credit card payments (see Entering and distributing payments in RapidPay for more information), you must create the actual payment transactions and apply the payment amounts to the invoices you specified. This process automatically creates payment transaction invoice detail line items in each invoice you selected for distribution.

In the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > RapidPay > Create Payments, to display the Create Payments for RapidPay dialog.

Click the Batch Lookup button to select the batch that you used when entering the RapidPay payment information. Then click OK.

A confirmation dialog appears, displaying the number of RapidPay payment records in the batch. Click OK to begin the process of creating the payments. A progress dialog will appear, showing the progress of the process.

Note

The batch selected when the RapidPay payment information was entered is the batch that the system will use to create invoice detail line items for all of the payment transactions created by this process. If there was any monetary contribution information entered in this batch, the system will create the actual transactions in the same batch.

When the process is completed, select Reports from any work area in the Navigation Tile Bar to display a list of UX Online reports. In the Reports list, locate and run the UX Deposit Report. Use this report to verify that the payments were applied correctly.

If you are satisfied with the information in the UX Deposit Report, you can close the batch, create GL detail for it, and post it. For more information, see Integration with General Ledger.

Note

After posting the batch, we recommend that you print the Account Distribution Journal Detail Report to verify the transactions, and for your records.

About contributions in RapidPay

When you apply all or a portion of a payment to a monetary contribution product in the RapidPay Payment Entry record, UX Online automatically creates contribution detail line items when you create RapidPay payment transactions. The line items include one for the monetary contribution product and another for the payment amount. If the customer does not have an existing miscellaneous invoice, the system will create a new one. If the customer has an existing miscellaneous invoice, the new invoice detail line items will be added to it.

If the system creates a new miscellaneous invoice during this process, it will use the customer’s default Bill To relationships. For example, if the Bill To Parent option on the customer’s contact record is set to Yes, then the customer’s parent account will appear in the Bill To field on the new miscellaneous invoice. Any subsequent monetary contribution created during the RapidPay process for this customer will be added to the original invoice, regardless of any changes to the customer’s Bill To information.

Note

The batch selected when the RapidPay payment information was entered is the batch that the system will use to create invoice detail line items for all of the monetary contribution transactions.

Processing a returned (NSF) check originally processed through RapidPay

If a check processed through RapidPay is returned because of non-sufficient funds (NSF), you will need to reverse the payment on each invoice the payment was applied. The method you use to deal with that transaction depends on whether the original check was applied to one invoice or to multiple invoices.

Note

Before you begin processing a returned (NSF) check, be sure that the daily batches needed for cash, check, and credit card payments have been created. You may choose to create a separate batch for an NSF check transaction to match the notice from the bank and assure that all bank transactions are in the General Ledger as they appear on the bank statement. For more information, see Integration with General Ledger.

Processing an NSF check applied to one invoice

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact record where you need to process an NSF check.

In the Navigation Pane of the record, click Invoices. Locate and open the appropriate invoice. Click Select Batch to select the batch you are using for this reversing transaction.

Select New Transactions > Payments & Adjustments > All Others from the invoice Record toolbar.

In the General section of the Payment record, enter the following information:

  • Product – Enter the same payment code that was used for the original NSF check or click the Lookup button to select the payment type.

  • Description – Once you select the product, UX will update this field with the product description.

  • Reference – Enter the same number as the original NSF check.

  • Payment – Enter the check amount as a negative number.

  • Batch Number – Automatically displays your selected batch. Do not change this field.

  • Customer Account/Customer Contact – Defaults from the invoice Bill To Account or Contact. Do not change this field.

Note

If there is only one check payment transaction in the invoice and you are using the same product code to reverse that check payment, the system will validate that amount and limit the negative amount entered to the amount of the original check payment. If more than one check payment transaction exists in the invoice, the system does not validate the negative amount entered.

Click Save & Close to save the payment transaction and return to the invoice. Review the new NSF payment transaction line item to ensure that it is correct. Review the invoice totals to ensure that the fields are calculated correctly. Because you entered the NSF check amount as a negative number, the invoice may have a balance due.

Click Save & Close to save and close the invoice and return to the RapidPay Payments record. Click Save & Close on the RapidPay Payment record to return to the list of RapidPay Payment records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Processing an NSF check applied to multiple invoices

In the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > RapidPay > RapidPay Payments to display the RapidPay Payments list. This list opens in a new window. Locate the RapidPay Payment record with the NSF check and open it to review the RapidPay distribution record.

Double-click to open the first invoice that has part of this payment applied to it to open it. Click Select Batch to select the batch you are using for this reversing transaction.

Select New Transactions > Payments & Adjustments > All Others from the invoice Record toolbar.

In the General section of the Payment record, enter the following information:

  • Product – Enter the same payment code that was used for the original NSF check or click the Lookup button to select the payment type.

  • Description – Once you select the product, UX will update this field with the product description.

  • Reference – Enter the same number as the original NSF check.

  • Payment – Enter the check amount as a negative number.

  • Batch Number – Automatically displays your selected batch. Do not change this field.

  • Customer Account/Customer Contact – Defaults from the invoice Bill To Account or Contact. Do not change this field.

Click Save & Close to save the payment transaction and return to the invoice. Review the new NSF payment transaction line item to ensure that it is correct. Review the invoice totals to ensure that the fields are calculated correctly. Because you entered the NSF check amount as a negative number, the invoice may have a balance due.

Click Save & Close to save and close the invoice.

Repeat steps for each invoice that had an amount applied to it.

When you are finished, Save & Close the RapidPay Payment record to return to the list of RapidPay Payment records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Post the batch using your usual business procedures.

Reversing a credit card transaction originally processed through RapidPay

Use the following procedure to reverse a credit card payment processed through RapidPay.

The method you use to deal with that transaction depends on whether or not the original credit card payment has gone through the delayed capture process. If the payment has not gone through the delayed capture process, you can void the transaction; however, if it has gone through delayed capture, you must credit the payment amount to the credit card.

Note

Before you begin reversing a credit card transaction, be sure that the daily batches needed for cash, check, and credit card payments have been created. For more information, see Integration with General Ledger.

Void a RapidPay credit card payment

The Void Payment option for a credit card payment authorized in the RapidPay payment record is only available if the Create Payments process that distributes the payment across selected invoices has not been run.

If the credit card payment has not been distributed through the Create Payments process, the Void Payment button will be available on the Record toolbar at the top of the RapidPay payment distribution record. If the credit card payment has already been distributed through the Create Payments process, the Void Payment button is not available on the Record toolbar.

In the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > RapidPay > RapidPay Payments, to display the RapidPay Payments list. This list opens in a new window. Locate the RapidPay Payment record with the credit card payment you want to void and double-click it to open the RapidPay Payment record.

If the credit card payment has not been distributed through the Create Payments process, the Void Payment button will be available on the Record toolbar. Click Void Payment. In the Void Payment Process dialog box, click OK to process the void payment.

Click Save & Close on the RapidPay payment record to return to the list of payment records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Note

If the Create Payments process has already been run on this distribution record, the Void Payment button will not be available on the RapidPay payment distribution record. In this case, you must close the batch, run Delayed Capture, and then credit the payment from within each invoice where payment was distributed. For more information, see Credit a credit card payment processed through RapidPay.

Void distributed RapidPay credit card payments

When you run the Create Payments process for a RapidPay payment record containing an authorized credit card payment, UX creates a credit card payment transaction in each of the selected invoices for the distribution amount entered in the RapidPay payment record. You cannot void an individual credit card payment transaction that was part of a distributed authorization because there is no functionality for a partial void (the distributed payment amount is part of the original authorization amount). You must run Delayed Capture and then credit the distributed payment.

You can, however, configure you system to allow voiding all distributed credit card payments transactions that were part of a distributed authorization by setting the config value of the PACreditCard.AllowVoidOnDistributedLines application parameter. This functionality is only available after you run the RapidPay Create Payments process and before you run the Delayed Capture process on the RapidPay batch.

Important

If your system is configured to allow this feature, when a user selects Void Payment in one of the distributed credit card payment transactions, UX will void all distributed credit card payment transactions that share the same authorization. The void is not limited to that one transaction.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters. This list will open in a new window. Locate and open the parameter PACreditCard.AllowVoidOnDistributedLines.

Set the Config value field as follows:

  • false – Enter this if you do not want to allow Void Payment in distributed credit card payment transactions. This is the default value.

  • true – Enter this if you want to allow Void Payment in distributed credit card payment transactions. UX will void all distributed credit card payment transactions that share the same authorization.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Once you configure your system to allow voiding all distributed credit card payment transactions that were part of a RapidPay authorization, use Void Payment in one of the invididual invoices where the credit card payment was distributed by the RapidPay Create Payments process.

In the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > RapidPay > RapidPay Payments, to display the RapidPay Payments list. This list opens in a new window. Locate and open the RapidPay Payment record with the credit card payment authorization you want to void.

Double-click the first invoice that has a distributed RapidPay payment applied to it. This will open the invoice record. Click Select Batch to select the batch you are using to void all distributed payments.

In the invoice, double-click to open the distributed credit card payment line item that you want to void.

If the credit card has not been processed to your merchant through delayed capture, the Void Payment button will be available on the toolbar. Click Void Payment.

UX will void all distributed credit card payments in all invoices for the selected RapidPay payment record. You can validate the voided credit card payments distributed across all invoices by running the UX Batch Proof report for the batch used to void the distributed credit card payment.

Credit a credit card payment processed through RapidPay

After you run the Delayed Capture process, you can credit a distributed credit card payment processed through RapidPay. Credits must be applied to each individual invoice where the credit card payment was distributed in RapidPay. You cannot credit the payment in the RapidPay Payment record.

In the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > RapidPay > RapidPay Payments, to display the RapidPay Payments list. This list opens in a new window. Locate and open the RapidPay Payment record with the credit card payment you want to reverse.

Double-click the invoice that has a distributed RapidPay payment applied to it. This will open the invoice record. Click Select Batch to select the batch you are using for this credit transaction.

In the invoice, double-click to open the distributed credit card payment line item that you want to credit.

If the credit card has been processed to your merchant through delayed capture, the Credit Payment button will be available on the toolbar. Click Credit Payment.

Note

If the credit card has not been processed through delayed capture, the Void Payment button will appear instead of Credit Payment. However, you will not be able to void a credit card payment that is distributed through RapidPay unless your system is configured to allow void on distributed payments. See Void distributed RapidPay credit card payments for more information.

The Credit Payment Process dialog box opens. The Credit Amount field displays the amount of the credit card payment distributed to this invoice. If you are entering a partial refund, enter the amount to be credited. (Do not enter a negative number for the refund amount. The system recognizes the amount as a credit.)

Note

You can credit any amount up to the amount of the original credit card payment amount distributed to this invoice.

Click OK to process the credit. UX immediately credits the amount indicated to the customer’s credit card. (There is no delayed capture process required for credits.) The original charge and the subsequent credit will appear on the customer’s credit card statement. The system also creates a credit transaction entry in the credit card log, which you can view by clicking Credit Card Log in the Navigation Pane of the invoice.

Click Save & Close to save the payment transaction and return to the invoice. Review the original credit card payment transaction detail line and a new payment transaction detail line for the credit transaction with a negative amount to ensure that it is correct.

To view the detail for the new credit line item, double-click it. The product name in the transaction detail will have Credit Transaction appended to it.

If you open the original credit card payment transaction item, you will see that the product name in the original transaction detail has Authorized – Captured – Credited appended to it.

Review the invoice totals to ensure that the fields are calculated correctly.

Click Save & Close to save and close the invoice.

Repeat these steps for each invoice where the RapidPay credit card payment was distributed.

Post the batch using your usual business procedures.

Chapter 16: Payment and Adjustment Transactions

Payment and adjustment transactions are generally created the same way throughout UX Online. However, in certain application areas, additional information is added by the system to the invoice, the record, or both, after you create a payment or adjustment transaction. In those cases, you will need to consult the module documentation for module-specific information.

This documentation assumes that your organization is following the best practices for creating GL Detail and posting batches to your accounting system on a regular (preferably daily) basis, and that you are using the standard payment products that are deployed with your system.

This chapter contains UX Online basic instructions on processing payment transactions and related adjustment transactions, including:

  • Applying a cash or check payment to an invoice

  • Canceling a cash or check payment

  • Applying a credit card payment to an invoice

  • Credit card validation

  • Voiding a credit card payment

  • Credit card log

  • Invoice credit balance adjustments overview

  • Deleting an invoice detail line item – open batch

  • Canceling an invoice detail line item – closed batch

  • Transferring a payment from one invoice to another

  • Cancelling a payment transfer

  • Issuing a refund by check

  • Refund processing

  • Issuing a credit card refund

  • Writing off invoice balances

For information about applying gift certificates as a payment, see Applying a gift certificate payment to an invoice.

Applying a cash or check payment to an invoice

Use this procedure to apply a cash or check payment to a single invoice. If you need to apply a single customer payment to multiple invoices, you can use the UX Online RapidPay. For more information, see RapidPay Processing.

Note

If any items on the invoice are back ordered, applying a check payment will result in a credit balance on the invoice. Later, when you process the back order, UX Online will automatically create a new invoice and transfer the credit balance from the original invoice to the new invoice. For more information, see Back order processing overview.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to enter a cash or check payment. In the Navigation Pane of the account or contact record, click Invoices to display a list of invoices.

Locate and open the appropriate invoice. If you have not already selected your batch, select the appropriate open batch.

Note

You can open any invoice whether or not you are working in an open batch. However, to open invoice detail line items, or to make any changes to the invoice, you must be working in an open batch.

On the invoice Record toolbar, select New Transactions > Payments & Adjustments > All Others to open a new payment transaction record.

In the General section of the Payment record, enter the following information:

  • Product – Enter the payment code for the type of payment you are entering or click the Lookup button on the Product field to select the check or cash payment product.

Note

If you are using multicurrency, only payment products that match the invoice currency will be displayed in the lookup payment results.

  • Description – Once you select the product, UX will update this field with the product description.

  • Reference – If you are entering a check payment, enter the check number. Do not include spaces, dashes, or any other special characters.

  • Payment – Enter the check amount.

Note

If any items on the invoice are back ordered, the default payment amount may be different from the customer’s actual payment amount. For example, if all of the items on the invoice are back ordered, the default payment amount will be zero. You must enter the actual payment amount.

  • Batch Number – Automatically displays your selected batch. Do not change this field.

  • Transaction Date – This date defaults from the batch date and cannot be changed.

  • Customer Account/Customer Contact – Displays the Bill To customer account or contact from the invoice. To enter a payment from someone other than the invoice Bill To customer, click the Lookup button and select the appropriate account or contact.

In the Payee Information section of the payment transaction record, the following information defaults from the Bill To Customer record name and primary address fields. If the Bill To Customer is an account record, the name field defaults to the primary contact. You may edit this information as necessary.

  • Name – If the Bill To Customer is a contact, defaults to the first and last name of the contact. If the Bill To Customer is an account, defaults to the account name. Enter a different name, if necessary.

  • Street – Automatically displays the Bill To Customer’s primary address street 1. Enter a different address if necessary.

  • City – Automatically displays the Bill To Customer’s primary address city. Enter a different city if necessary.

  • State – Automatically displays the Bill To Customer’s primary address state. Enter a different state if necessary.

  • Zip – Automatically displays the Bill To Customer’s primary address zip. Enter a different zip if necessary.

  • Country – Automatically displays the Bill To Customer’s primary address country. Enter a different state if necessary.

  • Telephone – Automatically displays the Bill To Customer’s main telephone number. Enter a different number if necessary.

Click Save & Close to save the payment transaction and return to the invoice. Review the new payment transaction line item to ensure that it is correct.

Review the invoice totals to ensure that the fields are calculated correctly.

Click Save & Close to save and close the invoice record and return to the list of invoices.

Canceling a cash or check payment

At times, you may need to cancel a check or cash payment entered on an invoice. For example, a check might be returned for Non-Sufficient Funds (NSF) from the bank, entered for the wrong amount, or the payment was applied to the wrong invoice. Regardless of the reason for canceling a check or cash payment, the process for canceling it is the same: you must enter a reversing transaction.

Important

Regardless of the batch status, you should never delete a payment detail line item from the invoice. Accounting principles and best practices for consistent entry require that cancellations must be recorded using a reversing entry.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to cancel a cash or check payment. In the Navigation Pane of the account or contact record, click Invoices to display a list of invoices.

Locate and open the appropriate invoice. If you have not already selected your batch, select the appropriate open batch.

Note

You can open any invoice whether or not you are working in an open batch. However, to open invoice detail line items, or to make any changes to the invoice, you must be working in an open batch.

On the invoice Record toolbar, select New Transactions > Payments & Adjustments > All Others to open a new payment transaction record.

In the General section of the Payment record, enter the following information:

  • Product – Enter the payment code for the type of payment you are entering, or click the Lookup button on the Product field to select the payment type.

Note

If you are using multicurrency, only payment products that match the invoice currency will be displayed in the lookup payment results.

  • Description – Once you select the product, UX will update this field with the product description.

  • Reference – If you are entering a check payment, enter the check number. Do not include spaces, dashes, or any other special characters.

  • Payment – Change the amount displayed to the amount of the check payment you are reversing, entered as a negative amount. For example, if you are canceling a check payment of $100, enter -100.00.

Note

If there is only one check payment transaction in the invoice and you are using the same product code to reverse that check payment, the system will validate that amount and limit the negative amount entered to the amount of the original check payment. If more than one check payment transaction exists in the invoice, the system does not validate the negative amount entered.

  • Batch Number – Automatically displays your selected batch. Do not change this field.

  • Transaction Date – This date defaults from the batch date and cannot be changed.

  • Customer Account/Customer Contact – Displays the Bill To customer account or contact from the invoice.

Click Save & Close to save the reversing payment transaction and return to the invoice. Review the new reversing payment transaction line item to ensure that it is correct.

Review the invoice totals to ensure that the fields are calculated correctly.

Click Save & Close to save and close the invoice record and return to the list of invoices.

Note

If you have any questions about the business processes surrounding this type of transaction, please contact the accounting manager at your organization.

Applying a credit card payment to an invoice

When a credit card payment is received to apply against an invoice, it is entered on the invoice using a credit card product. When you save the payment, the credit card is validated, and the payment is immediately authorized or declined through Payflow Pro in UX Online. (For more information about validation, see Credit card validation.)

Important Note

The maximum credit card payment amount that can be processed is $99,999.00. If you need to create a credit card payment transaction for more than $99,999.00, you will need to create multiple credit card payment transactions.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to apply a credit card payment. In the Navigation Pane of the account or contact record, click Invoices to display a list of invoices.

Locate and open the appropriate invoice. If you have not already selected your batch, select the appropriate open batch.

Note

You can open any invoice whether or not you are working in an open batch. However, to open invoice detail line items or to make any changes to the invoice, you must be working in an open batch.

On the invoice Record toolbar, select New Transactions > Payments & Adjustments > Credit Card to open a new payment transaction record.

In the General section of the Payment record, enter the following information:

  • Product – Enter the payment code for the type of payment you are entering or click the Lookup button on the Product field to select the credit card payment product.

Note

If you are using multicurrency, only credit card payment products that match the invoice currency will be displayed in the lookup payment results.

  • Description – Once you select the product, UX will update this field with the product description.

  • Credit Card/Ref – Enter the full card number. Do not include spaces, dashes, or any other special characters. After the card is preauthorized, the card number will be replaced with a series of asterisks and the last four digits of the card number. No credit card data is saved in UX Online.

  • Payment – Automatically displays the balance due on the invoice. If the payment amount is different, enter the amount of the payment.

  • Expiration – Enter the card expiration date, formatted as MMYY.

  • Security Code (CVV2) – This field is optional. If your organization’s business practices require it, enter the 3 or 4 digit security code. If a code is entered, the code will be transmitted with the credit card number and expiration date to the processor for verification. (When the credit card payment is authorized, this information is removed.)

  • Batch – Automatically displays your selected batch. Do not change this field.

  • Transaction Date – This date defaults from the batch date and cannot be changed.

  • Customer Account/Customer Contact – Displays the Bill To customer account or contact from the invoice. To enter a payment from someone other than the invoice Bill To customer, click the Lookup button and select the appropriate account or contact.

In the Cardholder Billing Information section,

  • Name on Card – If the Bill To Customer is a contact, defaults to the FN LN of the contact. If the Bill To Customer is an account, defaults to the account name. Enter a different name, if necessary.
  • Street – Automatically displays the Bill To Customer’s primary address street 1. Enter a different address if necessary.
  • City – Automatically displays the Bill To Customer’s primary address city. Enter a different city if necessary.

  • State – Automatically displays the Bill To Customer’s primary address state. Enter a different state if necessary.

  • Zip – Automatically displays the Bill To Customer’s primary address zip. Enter a different zip if necessary.

  • Country – Automatically displays the Bill To Customer’s primary address country. Enter a different Country if necessary.

  • Email – Automatically displays the Bill To Customer’s primary email address. Enter a different email if necessary.

  • Telephone – Automatically displays the Bill To Customer’s primary telephone number. Enter a different number if necessary.

In the Credit Card Transaction Results section:

    • Origination/Ref ID – Automatically populated with the PayPal transaction ID once the transaction is saved for processing the authorization through PayPal. This field is disabled.

    • Capture ID – Automatically displays the Delayed Capture ID once the batch is processed for capture. This field is disabled.

Click Save to send the transaction to PayPal for authorization.

If the system could not validate the credit card number against the card type, a message will appear stating that the credit card number or the number format is not valid. Click OK, and verify that you selected the correct credit card product and that you entered the number correctly. After correcting your entries, click Save to re-try the authorization.

Depending on whether the transaction is approved or declined, the system updates these fields, as follows:

  • Credit Card/Ref – The system encrypts this field.

  • Origination/Ref ID – Displays the transaction ID returned by PayPal.

Additional information regarding this credit card transaction is available in the Credit Card Log record for this transaction.

  • Authorization Code – Displays the authorization code if the transaction was approved. If the transaction was declined, this field remains blank.

  • Message – Displays the message as part of credit card authorization. If the credit card charge was approved, this field will display Approved. If the charge was declined, this field will display Declined and further action is needed.

  • Result Code – Displays the result code as part of credit card authorization. If the transaction was approved, the result code is 0. If the transaction was declined, the result code is 12.

Note

Please refer to your Payflow Pro Manager documentation complete details on Result Code, Authorization Code, and Message translations.

  • Comment 1 – Defaults to the batch number

  • Comment 2 – If authorized, defaults to UX Authorize

Note

When a credit card payment is processed, the payment product name is updated to append Authorized or Declined to the credit card product name. An entry is also recorded in the credit card log, which you can view by clicking Credit Card Log in the Navigation Pane of the invoice.

If the system could not validate the credit card number against the card type, a message will appear stating that the credit card number or the number format is not valid. Click OK and verify that you selected the correct credit card product, and that you entered the number correctly. After correcting your entries, click Save to re-try the authorization.

Important

If a credit card is declined, you must close the record by clicking the File menu button in the top-left corner of the payment record, and then clicking Close. If you click Save & Close after a credit card has been declined, the system will attempt to authorize the credit card again.

Click Save & Close to return to the invoice.

Review the invoice. If the credit card transaction was approved, the system creates a credit card payment detail line. Review the payment to make sure it is correct. If the transaction was declined, the system does not create any invoice detail line items. Refer to the declined payment entry in the credit card log to view the details of the declined transaction.

Review the invoice totals to make that the invoice balance due is correct.

Click Save & Close to close the invoice and return to the list of invoices.

Credit card validation

When you save a credit card payment, the system validates the credit card number against the credit card type using an industry-standard validation table. (This validation is internal to UX Online, and does not check the number with the credit card merchant, bank, or any other outside source.) This validation occurs prior to sending the transaction to Payflow Pro for authorization.

Note

If your credit card number passes validation for your selected payment product card type and you select a different credit card payment product, UX will clear the credit card number and expiration date fields to force re-validation with the newly selected credit card payment product.

During this validation, the system checks for the following:

  • Credit card is a valid for the transaction’s accounting company and currency.

  • Number of digits in the credit card number is valid for the given credit card type.

  • Prefix of the credit card number is valid for the given credit card type.

  • Credit card number could be valid according to a special check digit algorithm, known as the Modula 10.

This validation can return the following error messages:

  • There is no Credit Card record in your Organizational Settings for this currency and/or accounting company – The credit card payment product you selected is not valid for the transaction’s accounting company, currency, or both.

  • Credit card number is not valid – This indicates that the number does not meet the Modula 10 algorithm test.

  • Credit card number format is not valid – This indicates that the number is not numeric, contains dashes or other special characters, or contains spaces (except after every 4 digits).

Voiding a credit card payment

If there is an error on an invoice or a credit card payment transaction, you can void the payment transaction if the payment has not been processed for delayed capture. (If the payment has been processed for delayed capture, you must issue a credit. For more information, see Issuing a credit card refund.)

When you void a credit card payment, the system will automatically create entries that reverse the original transaction. You cannot partially void a credit card payment; the entire authorized transaction amount will be reversed.

If your system is configured for multiple accounting companies, when selecting the Void Payment button, UX will first validate that the accounting company of the user’s working batch matches the batch accounting company of the original credit card payment transaction. If the batch accounting companies do not match, UX will return an alert message directing you to select a different batch. If the batch accounting companies match, UX will continue with the Void Payment process described below.

Important Notes

You cannot delete a credit card payment transaction from the invoice transaction detail list.

Because you cannot partially void a credit card payment, you cannot void a credit card payment where the authorized payment amount is distributed to multiple invoices. This includes RapidPay credit card payment distributions. It also includes credit card payments processed online that are distributed to more than one invoice. If Delayed Capture has not been run on the original batch, the Void Payment button will appear but selecting this option will return an alert that you cannot void a distributed credit card payment.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to void a credit card payment. In the Navigation Pane of the account or contact record, click Invoices to display a list of invoices.

Locate and open the appropriate invoice. If you have not already selected your batch, select the appropriate open batch. Double-click to open the original credit card detail line item that you want to void.

If the credit card has not been processed through delayed capture, the Void Payment button will be available on the Record toolbar. Click Void Payment. In the Void Payment Process dialog box, click OK to process the void payment.

Note

If the credit card has already been processed through delayed capture, the Credit Payment button will appear instead of Void Payment. In this case, you must issue a credit card refund. For more information, see Issuing a credit card refund.

If the credit card payment was part of a distributed credit card payment transaction, the system will return an alert indicating that you cannot void this credit card payment.See Void distributed RapidPay credit card payments for more information.

In the list of invoice detail line items, the original charge and a new void transaction will appear. The balance field will be updated based on the voided amount. The system also creates a Void Transaction entry the credit card log, which you can view by clicking Credit Card Log in the Navigation Pane of the invoice. At this point, you may enter a different credit card for payment processing.

Note

When you run the Delayed Capture process, the original charge and the void transaction are processed together and no transactions will appear on the customer’s credit card statement.

Click Save & Close to save your changes to the invoice and return to the list of invoices.

Credit card log

For each credit card transaction added to an invoice and processed, the system creates an equivalent entry in the invoice credit card log, providing you with an at-a-glance view of the credit card transaction life cycle. This log records the following transaction entries:

  • Authorized transactions

  • Declined transactions

  • Credit transactions

  • Void transactions

  • Delayed Capture

To view the credit card log for any invoice, open the invoice and click Credit Card Log in the Navigation Pane of the invoice.

Invoice credit balance adjustments overview

There are several reasons why an invoice may have a credit balance. For example:

  • When you receive a customer payment to apply against an invoice, it must be applied in the exact amount of the payment received and on the invoice indicated by the customer. If the customer’s payment is greater than the balance due, it will cause the invoice to have a negative (credit) balance due.

  • If the invoice has both purchase line items and a payment, and then one or more purchase line items are canceled.

Your options for managing a credit balance on an invoice are:

Deleting an invoice detail line item – open batch

If you want to remove a line item from an invoice, you can delete the invoice detail line items as long as both of the following conditions apply:

  • The line items you want to remove are not payment, membership, subscription, certification, or contribution transactions. Depending on the transaction type, these items must be cancelled from within the invoice detail.

  • The invoice is in a batch that has not been closed.

Regardless of the batch status, you should never delete a payment detail line item from the invoice. Accounting principles and best practices for consistent entry require that payment cancellations must be recorded using a reversing entry. For information about reversing cash or check payments, see Canceling a cash or check payment. For information about reversing credit card payments, see Voiding a credit card payment.

If the batch has been closed, or closed and posted, you must cancel any unwanted line items, rather than deleting them. For more information, see Canceling an invoice detail line item – closed batch.

When the invoice is in an open batch, you can delete a purchase line item because the transaction has not been posted to the accounting system.

Note

Do not use this process to cancel transaction detail related to renewal billing for membership, subscriptions, or certification. Please refer to the module-specific documentation for information related to cancellations.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to enter a cash or check payment. In the Navigation Pane of the account or contact record, click Invoices to display a list of invoices.

Locate and open the appropriate invoice. If you have not already selected your batch, select the appropriate open batch.

Click to highlight the invoice detail line item you want to cancel. To select multiple line items, hold the Ctrl key while you click.

Click the Cancel button on the Transactions grid toolbar.

A message appears stating that the selected items will be deleted. Click Yes to delete the selected line items.

Review the resulting transaction. Since you are working in the same batch in which the item was added to the invoice, the item is deleted.

Note

The invoice may now have a negative balance due. For information about correcting this, see Invoice credit balance adjustments overview.

Click Save & Close to save your changes to the invoice and return to the list of invoices.

Canceling an invoice detail line item – closed batch

If you want to remove a line item from an invoice where the batch has been closed, or closed and posted, you must cancel the line item; you cannot simply delete it because the information is in a batch that is closed or has already been posted to the accounting system.

Regardless of the batch status, you should never delete a payment detail line item from the invoice. Accounting principles and best practices for consistent entry require that payment cancellations must be recorded using a reversing entry. For information about reversing cash or check payments, see Canceling a cash or check payment. For information about reversing credit card payments, see Voiding a credit card payment.

After you cancel an invoice detail line item, the canceled line item is zeroed out and has a red X to the left of it. It is flagged in the data as a canceled item.

Note

Do not use this process to cancel transaction detail related to renewal billing for membership, subscriptions, or certification. Please refer to the module-specific documentation for information related to cancellations.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to enter a cash or check payment. In the Navigation Pane of the account or contact record, click Invoices to display a list of invoices.

Locate and open the appropriate invoice. If you have not already selected your batch, select the appropriate open batch.

Click to highlight the invoice detail line item you want to cancel. To select multiple line items, hold the Ctrl key while you click.

Click the Cancel button on the Transactions grid toolbar.

A Cancel/Delete message appears stating that the selected items will be deleted. Click Yes to cancel the selected line items.

Review the resulting transaction. Since the original transaction batch is closed or closed/posted, the item is canceled. The line item has a zero extended amount and a red X to the left.

Note

The invoice may now have a negative balance due. For information about correcting this, see Invoice credit balance adjustments overview.

Click Save & Close to save your changes to the invoice and return to the list of invoices.

Transferring a payment from one invoice to another

If necessary, you can transfer a customer’s payment from one invoice to another. For example, if you have an invoice that has a credit balance (that is, a negative amount due), you can transfer the payment to another invoice.

Note

You must have a transfer product set up in your UX Online system before you begin.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to enter a cash or check payment. In the Navigation Pane of the account or contact record, click Invoices to display a list of invoices.

Locate and open the appropriate invoice. If you have not already selected your batch, select the appropriate open batch.

Note

You can open any invoice whether or not you are working in an open batch. However, to open invoice detail line items or make any changes to the invoice, you must be working in an open batch.

On the invoice Record toolbar, click the Transfer Payment button.

The Transfer Payment Process dialog appears, with the invoice number of the invoice you are transferring the payment from displayed in the Source Invoice field. Click the Target Invoice Lookup button to select the invoice that you want to transfer the payment amount to, and then enter the payment amount to transfer. Click OK.

Note

You cannot transfer an amount greater than the total payment amount displayed in the Payments field at the bottom of the invoice.

UX Online will create the necessary invoice detail on both the source invoice and target invoice to transfer the payment amount.

Review the payment transfer detail transaction line to make sure it is correct.

Review the invoice totals to make that the fields are calculated correctly, then click Save & Close to save and close the source invoice record and return to the invoices list.

In the customer’s Invoice list, locate and open the target invoice you transferred the payment to.

Review the invoice detail to verify that the payment transferred correctly.

Click Save & Close on the target invoice to return to the invoices list.

Canceling a payment transfer

You can cancel payment transfer transactions that were created using the Transfer Payment option.

If you cancel a payment transfer when the original transfer transaction is still open, UX Online will delete the transfer invoice detail transactions in both the source and target invoices. If the batch is closed, the transfer invoice detail transactions will be canceled in both the source and target invoices.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to enter a cash or check payment. In the Navigation Pane of the account or contact record, click Invoices to display a list of invoices.

Locate and open the invoice that includes the transfer you want to cancel (either the source or the target invoice).

Click to highlight the invoice detail line item for the payment transfer you want to cancel.

Click the Cancel button on the Transactions grid toolbar.

A Cancel/Delete message appears stating that the selected item will be deleted. Click Yes to cancel the transfer payment. If the original batch for the payment transfer transaction is still open, the transfer detail line item will be deleted from both the source and target invoices. If the batch is closed, the transaction will be canceled.

Note

You can open any invoice whether or not you are working in an open batch. However, to open invoice detail line items or make any changes to the invoice, you must be working in an open batch.

Save & Close the invoice to return to the invoices list.

Issuing a refund by check

If a customer or account has a credit balance on an invoice (due to either an overpayment or a canceled invoice detail line item), you can refund the credit balance to the customer by issuing a check.

The method you use to issue refund checks depends on whether you are using the UX Online GL and AP Integrations:

  • If you are using the UX Online GL Integration and the UX Online AP Integration, the check refund process requires that you enter a refund transaction in UX Online, and then run the Refund Processing process to create the appropriate payment vouchers in your organization’s payables accounting module. For more information, see Refund processing.

  • If you are not using the UX Online GL Integration and the UX Online AP Integration, the check refund process requires that you enter a refund transaction in UX Online and manually create the appropriate payment vouchers in your organization’s payables accounting module. (As part of this process, you will print the UX Refund Report to use as a reference for data entry in your accounting system payment voucher.) We recommend that the voucher be recorded at the same time the refund is processed.

Note

If you issue a refund check, and the batch is posted before the batch containing the associated customer payment, the refund amount will be posted to the unapplied account for the refund product. Then, when you post the batch containing the payment, the refund amount will be transferred from the unapplied account. For more information, see About unapplied accounts.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact record. In the Navigation Pane of the record, click Invoices. Locate and open the invoice that includes the transfer you want to cancel (either the source or the target invoice). If you have not already selected your batch, select the appropriate open batch.

On the invoice Record toolbar, select New Transactions > Payments & Adjustments > All Others to open a new payment transaction record.

In the General section of the Payment record, enter the following information:

  • Product – Enter the payment code for the type of payment you are entering, or click the Lookup on the Product field to select the refund payment product.

Note

If you are using multicurrency, only payment products that match the invoice currency will be displayed in the lookup payment results.

  • Description – Once you select the product, UX will update this field with the product description.

  • Reference – Enter a meaningful reference for the refund, such as “Refund of Overpayment.”

  • Payment – Automatically displays the credit balance of the invoice (as a negative amount). If necessary, you can modify the amount you want to refund, up to the amount of the credit balance. Whether you leave the default amount or change it, the amount to be refunded from this invoice must be a negative entry and cannot exceed the amount of the credit balance on the invoice.

Note

If there is only one check payment transaction in the invoice and you are using the same product code to reverse that check payment, the system will validate that amount and limit the negative amount entered to the amount of the original check payment. If more than one check payment transaction exists in the invoice, the system does not validate the negative amount entered.

  • Batch Number – Automatically displays your selected batch. Do not change this field.

  • Transaction Date – This date defaults from the batch date and cannot be changed.

  • Customer Account/Customer Contact – Displays the Bill To customer from the invoice. To enter a refund for a payment received from someone other than the invoice Bill To customer, click the Lookup button and select the appropriate account or contact.

Note

Changing the Customer Account/Customer Contact will automatically update the fields in the Payee Information section of the payment record as described below.

In the Payee Information section of the Payment record, you will notice that the system automatically populates these fields based on the refund transaction Customer Account or Customer Contact record in the General section, as follows:

  • If the refund transaction is for a Customer Account, the system pulls the account Name into the Payee Information Name field and the account’s primary address into the Payee Information address fields.

  • If the refund transaction is for a Customer Contact, the system pulls the contact FN LN into the Payee Information Name field and the contact’s primary address into the Payee Information address fields.

Click Save & Close to save the refund transaction and return to the invoice. Review the invoice totals to ensure that the fields are calculated correctly.

Click Save & Close to save and close the invoice record and return to the list of invoices.

If you are using the UX Online GL Integration and the UX Online AP Integration, continue with the refund processing procedures. For more information, see Refund processing. If you are not using the GL Integration and the AP Integration, continue with the following steps.

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online report. Locate and open the UX Refund Report.

Enter the batch number of the batch you entered the refund transaction in, and click Run Report to generate the report.

Use the UX Refund Report as a reference to create a voucher in your accounting system to pay the customer.

Refund processing with AP integration

If you are using the UX Online GL Integration and the UX Online AP Integration, the check refund process requires that you enter a refund transaction in UX Online, and then run the Refund Processing process. This process will search for all refund transactions that have not yet been processed, transfer funds from the refund product’s Refunds Payable GL account to the refund product’s Accounts Payable GL account, and create the appropriate payment vouchers in your organization’s Payables accounting module.

Important

Do not use this process if you are not using the UX Online GL Integration and the UX Online AP Integration.

Depending on the Accounts Payable Integration settings for your organization, refund processing can update the refund transaction invoice detail line item with the check number and check date from the accounting system. It can also update the vendor record name and address in the accounting system or create new vendor records when a matching vendor record cannot be found. For more information, see Setting up Refresh Utility and AP integration options for a company.

UX Online refund processing for AP integration uses a special batch type: Refund Processing. A Refund Processing batch can only be used for this process, and it cannot be used for any other types of transactions or batch processes.

This “fiscally oriented” process uses the batch date to determine the month-end date to be used for the process. All GL detail records used in the process are filtered to include only those with a fiscal date less than or equal to the month end of the batch log batch date. This allows the process to be run at any time and GL entries entered beyond the month-end date of the batch log batch date are ignored.

The procedures for creating GL detail and posting to accounting can be performed at the same time, or they can be managed separately, depending on your association’s business rules. This procedure shows how to perform them at the same time.

Important

You must create a batch to use for refund processing before running the process. The Batch Type field for this batch must be set to Refund Processing. For more information, see Creating a batch in UX Online.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window. In the Batch Log list, click New on the toolbar to open a new batch log record.

In the General section of the Batch Log record, enter the general batch setup information:

  • Description – Enter a description for this batch. When this batch is posted, the entry here will appear in the Reference field in the accounting system’s general ledger transaction entry window. If you are integrating with Microsoft Dynamics GP, note that there is a 30-character limit. This description also appears as the Batch Name in the Comments field in the Batch header file in Microsoft Dynamics GP.

  • Batch Number – Displays an automatically generated number. The number increases by one each time you save a new batch. This number will appear in the batch ID field in the accounting system’s general ledger transaction entry window.

  • Batch Date – This field defaults to the system date. This will be the transaction date when this batch is posted to the accounting system, and will appear in the transaction date field in the accounting system’s general ledger transaction entry window. If this is not correct, edit the date as required.

Note

Because the batch date is the date the journal entry posts into the accounting system, be sure you enter the correct date.

  • Batch Type – Select Refund Processing as the type for this batch. Selecting this batch type will automatically mark the batch as Closed.

UX will mark the batch Closed. Do not mark the Ready for GL Detail and Ready To Post checkboxes in the batch log record.

Click Save & Close on the batch log record to return to the list of active batch log records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management. Select Special GL to create GL Detail and post to accounting.

Selecting Special GL will open a new window listing closed batches where batch type ≠ Standard GL Detail that have not been processed for either GL Detail. This includes your refund processing batch.

Use the checkboxes to mark Ready for GL Detail and Ready to Post. Select OK to initiate the process and close the window. After the process is complete, select Close to close the processing window.

Important Note

You can mark both the Ready for GL Detail and the Ready to Post checkboxes at the same time, but you cannot mark the Ready to Post checkbox if the Ready for GL Detail has not been marked. Select OK to initiate the process. To Create GL Detail only without Posting to Accounting, mark only the checkbox for Create GL Detail. The process will run based on the marked checkboxes.

If your system is integrated directly with Payables Management in the accounting system, the process will also create the necessary refund vouchers in the accounting system. (If you do not use the direct payables integration, you must create the payment vouchers manually.)

Review the journal entries by printing either the UX Account Distribution Detail Report or the UX Account Distribution Summary Report. For more information, see GL posting reports.

When the AP transaction is created in the accounting system (PM10100 in GP and APTrans in SL) during the posting process, an accounting system reference field is updated with the appropriate next voucher number, which is retrieved from the accounting system. That number is also updated into the AP Reference field of the corresponding General Ledger Detail record in UX Online.

After you process the payables batch and print checks in the accounting system, the UX Online AP refresh job will automatically update the check number and check date in the invoice detail for the refund payment transaction in UX Online. When this system job runs, it uses one of the reference fields in the accounting system data and searches for the same value in the UX General Ledger Detail record APReference field to locate the invoice detail where the check number and check number is updated.

Accounting system vendor record updates

The Accounts Payable Integration settings for your organization will dictate how refund processing manages the vendor record when creating payables vouchers in your accounting system.

Note:

Any changes in SL to vendor name and address are done to both the main and remittance addresses. In GP, changes are made to the vendor maintenance record and the related “PRIMARY” vendor address record.

Please refer to the charts below:

When ‘Use Member ID as Vendor ID’ is false:

Refund Trx Bill To Customer Has Vendor Number in UX1

Permanent Vendor Exists in Accounting System where Vendor ID matches Refund Bill To Vendor Number2

Expected Result

Update Vendor Name and Address from UX Refund Transaction Payee Information during Refund Processing

Yes

No

Yes

No

True3

False

X

X

GP: Updates permanent Vendor record and related “PRIMARY” vendor address record, if one exists. If no related “PRIMARY” Vendor Address record exists, creates a new Vendor Address record.

SL: Updates permanent Vendor record main and remittance addresses.

No change to accounting system vendor record.

X

X

GP: Creates new permanent Vendor record and related “PRIMARY” Vendor Address record.

SL: Creates new permanent Vendor record, with main and remittance addresses.

X

Not applicable if no Vendor Number exists in UX Refund Bill To Customer record

Creates Temporary Vendor Record. Vendor Id is retrieved from the next vendor in the Accounting System.

When Use Member ID as Vendor ID is true:

1 Updates to the account or contact record Vendor Number with the accounting system Vendor ID is always manual. There is no system update from the vendor record in the accounting system to UX. If creating a new vendor in the accounting system for an existing record in UX, or if the system creates a new Permanent Vendor record during refund processing, you must manually update the UX record Vendor Number with the accounting system Vendor ID.

2 To update the GP Vendor, the system gets the Vendor number from the Refund Transaction Customer BillTo ID Vendor Number. If the Refund Transaction Customer Bill To ID is not available, system gets the vendor number from the Invoice Customer BillTo ID Vendor Number. Then, if no vendor is retrieved, the system produces an error. There is no check for match against name or address data.

3 The GP Vendor Name will be updated/created from the Account or Contact name of the Refund Transaction Customer BillTo ID and if not available, from the Invoice BillTo ID.

The GP Vendor Address will be updated/created from the Refund Transaction Payee Address if populated. If not populated, then from the address of the Refund Transaction Customer BillTo ID, if available. Then, if not available, the GP Vendor Address will be updated/created from the Invoice BillTo address, if available. Then, if not available, from the Invoice Bill To ID address.

The Refund Transaction Payee Name is used for the GP Vendor Check Name ONLY.

4 To update the GP Vendor, the system gets the Vendor number from the Refund Transaction Customer BillTo ID member ID. If the Refund Transaction Customer Bill To ID is not available, system gets the vendor number from the Invoice Customer BillTo ID member ID. Then, if no vendor is retrieved, the system produces an error. There is no check for match against name or address data.

5 The GP Vendor Name will be updated/created from the Account or Contact name of the Refund Transaction Customer BillTo ID and if not available, from the Invoice BillTo ID.

The GP Vendor Address will be updated/created from the Refund Transaction Payee Address if populated. If not populated, then from the address of the Refund Transaction Customer BillTo ID, if available. Then, if not available, the GP Vendor Address will be updated/created from the Invoice BillTo address, if available. Then, if not available, from the Invoice Bill To ID address.

The Refund Transaction Payee Name is used for the GP Vendor Check Name ONLY.

Refund Trx Bill To Customer Has Vendor Number in UX

Permanent Vendor Exists in Accounting System where Vendor ID matches Refund Bill To Member ID4

Refund Trx Default

Payee Name and/or Address Information Changed

Expected Result

Update Vendor Name and Address from UX Refund Transaction Payee Information

during Refund Processing

Yes

No

Yes

No

Yes

No

True5

False

Vendor Number Ignored. Setting relies on Member ID

X

X

Updates Permanent Vendor name and address with refund Payee information.

No change to accounting system vendor record.

X

Not applicable if no matching Permanent Vendor ID exists.

Creates new Permanent Vendor Record using refund Payee name and address Information

Creates new Permanent Vendor Record using refund Payee name and address Information

Issuing a credit card refund

You can issue a refund to a customer by crediting their credit card account if the payment was made by credit card and the payment has been processed for delayed capture. For example, if you make a change to an invoice such as a meeting cancellation that results in a credit balance on the invoice, you can credit the customer’s card if they request it, rather than issue a refund check.

If your system is configured for multiple accounting companies, when selecting the Credit Payment button, UX will first validate that the accounting company of the user’s working batch matches the batch accounting company of the original credit card payment transaction. If the batch accounting companies do not match, UX will return an alert message directing you to select a different batch. If the batch accounting companies match, UX will continue with the Credit Payment process described below.

Important

We recommend that you create a batch to use for refund transactions. Select Standard GL Detail Creation for the batch type. For more information, see Creating a batch in UX Online.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to enter a cash or check payment. In the Navigation Pane of the account or contact record, click Invoices to display a list of invoices.

Locate and open the appropriate invoice. If you have not already selected your batch, select the appropriate open batch.

Double-click to open the original credit card detail line item that you want to credit.

If the credit card has been processed through delayed capture, the Credit Payment button will be available on the Record toolbar. Click Credit Payment.

Note

If the credit card has not already been processed through delayed capture, the Void Payment button will appear instead of Credit Payment. In this case, you must void the credit card payment. For more information, see Voiding a credit card payment.

In the Credit Payment Process dialog box, the amount to credit defaults to the amount of the original payment. You may edit this amount, up to the amount of the original transaction.

Click OK to process the refund and immediately credit the amount indicated to the customer’s credit card. (There is no delayed capture process required for credits.) The original charge and the subsequent credit will appear on the customer’s credit card statement. The system also creates a credit transaction entry in the credit card log, which you can view by clicking Credit Card Log in the Navigation Pane of the invoice.

The invoice detail record appears, where you can view the original credit card payment transaction detail line and a new payment transaction detail line for the credit transaction with a negative amount.

To view the detail for the new credit line item, double-click it. The product name in the transaction detail will have Credit Transaction appended to it.

If you open the original credit card payment transaction item, you will see that the product name in the original transaction detail has Authorized – Captured – Credit appended to it.

Click Save & Close to save your changes to the invoice and return to the list of invoices.

Writing off invoice balances

If necessary, you can write off the balance due on one or more invoices, automatically creating the necessary write-off transactions to bring the invoice balances to zero. In addition, you may want to set limit on the amount that users can write-off before processing write-off transactions. See Setting the write-off limit and Processing write-off transactions for more information.

Note

These instructions assume that you have set up the write-off payment product required for this process. See Setting up payment and adjustment products.

Setting the write-off limit

When you set the write-off limit in UX Online, you are specifying the maximum amount that can be written off on an invoice transaction. For example, if you set this application parameter to 100, users in your system will not be able to create write-off transactions for more than $100.

This limit is managed by the Config value in the UX Online Application Parameter, PAInvoice.Writeofflimit.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters. Then locate and open the parameter PAInvoice.Writeofflimit.

Set the Config Value field to the maximum amount you want to allow for write-off transactions. For example, if you want the maximum write-off transaction to be $100, enter 100.

Click Save & Close to save your change. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Processing write-off transactions

From any of the UX work areas on the Navigation Tile Bar, click Invoices. In the Invoices list, locate the invoices that you want to write off, and click to select them. (To select multiple invoices, hold the Ctrl key while clicking the invoices.)

Hint

We recommend that you create a saved view that will display only those invoices that match the criteria of invoices that you might want to write off. For example, if your system is set up with a write-off limit of $100, you could create a view that shows invoices with an amount due of $100 or less.

After selecting the invoice records, the Write-off button will be available on the list toolbar. Select the Write-off button.

In the Invoice Write-off dialog, select the batch you want to use for the write-off transactions that will be created in the selected invoices. Protech recommends a separate batch used only for this process.

Select the write-off payment product to use.

Enter the text that will appear as a note on the Bill To Customer for each of the invoices you have selected.

Click OK. The system will create a write-off transaction for each selected invoice that had a balance due less than the write-off limit and update the invoice balance due to $0.00. In addition, the system will create a note in the invoice Bill To Customer record for each invoice where the write-off was processed using the text you entered in the Invoice Write-off dialog.

After creating the write-off transactions, close the batch and process according to you posting procedures. For more information, see Integration with General Ledger.

Chapter 17: AutoPay Processing

You will use the UX Online AutoPay feature to process payments for account or contact records that have opted to pay certain types of invoices automatically. For example, a contact might want to have their subscription renewal invoices automatically paid by credit card, or an account might want to have their exhibit invoices automatically paid by credit card.

Important Note

All eligible Payment Demographics records processed to Payflow Pro for authorization during AutoPay processing will create an entry in the Credit Card Log and will incur a Payflow Pro transaction fee.

This information includes the following topics:

  • About automatic credit card payments

  • Processing automatic credit card payments for invoices

  • Processing automatic credit card payments for renewal installments

  • Processing automatic credit card payments for monetary pledge installments

  • Processing automatic credit card payments for recurring gift installments

  • Re-authorize Payment Demographics

About automatic credit card payments

If you have members who want some of their invoices automatically paid by credit card, you can use the UX Online AutoPay feature. You can use AutoPay for single invoices for membership, subscriptions and certification renewals; meeting registrations, exhibit invoices, monetary pledge installments, and recurring gifts. You can also use it for installment renewal invoices for membership, subscriptions, or certification.

For example, a contact might want to have their subscription renewal invoices automatically paid by credit card, or an account might want to have their exhibit invoices automatically paid by credit card.

Before you can create automatic credit card payments, you must create Payment Demographics records for the customers who want to use AutoPay. A Payment Demographics record includes the customer’s credit card information, as well as the UX Online modules where the card can be used during AutoPay. For more information, see Setting up Payment Demographics for automatic credit card payments.

The AutoPay process is based on the account or contact that appears in the Bill To field of an invoice. For example, if the customer for the invoice has an eligible Payment Demographics record, but the Bill To account or contact does not, the invoice will not be selected for automatic payment.

When accounts or customers have an eligible Payment Demographics record set up, you can use AutoPay to authorize credit card payments automatically.

  • If authorization is approved during AutoPay processing, a credit card payment transaction is created in the invoice and an entry is created in the Credit Card Log. UX Online also updates the Payment Demographics record Authorization Number and Authorized Date.

  • If authorization is declined during AutoPay processing, no credit card transaction is created in the invoice; however, a declined entry is created in the Credit Card Log. UX Online also updates the Payment Demographics record Authorized Date, and since the transaction is declined, the Credit Card Has Problem field is updated to Yes so that this Payment Demographics record is no longer eligible for future AutoPay processing until the problem is resolved by re-authorizing the Payment Demographic record by entering corrected credit card information. A successful re-authorization will update the Authorization Number and clear the Credit Card Has Problem attribute in the payment demographic record. Declines are typically the result of an expired credit card or an expired Payflow Pro reference transaction (Payflow Pro expires reference transactions 365 days from the last authorization date). See Re-authorize Payment Demographics for more information on maintenance to keep reference transactions current.

Important Note

All eligible Payment Demographics records processed to Payflow Pro for authorization during any AutoPay process will create an entry in the Credit Card Log and will incur a Payflow Pro transaction fee.

Payment Demographics records eligible for AutoPay processing

Payment Demographics records eligible for AutoPay processing include those where the record status = Active and Credit Card Has Problem <> True, and where the accounting company of the credit card product setup selected as the payment source in the payment demographic record matches the accounting company of batch selected for AutoPay processing.

Important Note

All eligible Payment Demographics records processed to Payflow Pro for authorization during AutoPay processing will create an entry in the Credit Card Log and will incur a Payflow Pro transaction fee.

Recommended AutoPay actions

To minimize declined AutoPay transactions that rely on the Payment Demographics record, you should consider data cleanup of your Payment Demographics records before running AutoPay processes. This will minimize (not eliminate) declined transactions. This is also an opportunity to contact your customers and obtain current credit card information to create a new or re-authorize an existing Payment Demographics record. Recommendations include:

  • Expired reference transactions. Run an Advanced Find query on Active Payment Demographics records where the Authorization Date is less than the system date less 12 months. Through Advanced Find, you can update the status of these records to inactive using the Bulk Edit function. Because Payflow Pro expires reference transactions 365 days from the last authorization date, deactivating the Payment Demographics records where the reference transaction has expired will prevent them from being captured in the re-authorization utility and/or being used for AutoPay processing (and thus incurring a transaction fee). Alternatively, you can obtain updated information from your customers and re-authorize the existing records.

  • Regularly run an Advanced Find query on active Payment Demographics records, where credit card Expiration Date is less than the system date (end of month), to locate those credit cards that are expired. You can update the Payment Demographic record status to inactive using the Advanced Find Edit function to exclude them from the utility or obtain updated information from your customers and re-authorize the existing records.

Important

If you create a new record in lieu of re-authorizing an existing Payment Demographic record and the problem record was selected in a pledge contract or recurring gift, you will need to select the new Payment Demographic record in the pledge or recurring gift.

Processing automatic credit card payments for invoices

Use AutoPay Invoices to generate customer payment transactions on eligible single installment invoices for the invoice BillTo accounts or contacts that have eligible payment demographic records.

Note

To identify the invoices eligible for AutoPay Invoices processing, run the UX AutoPay Invoices Report using the same search criteria and batch that you will use in the AutoPay Invoices process. The report will return a list of the eligible invoices to be processed.

You can use the AutoPay Invoices process to generate automatic credit card payments for the following types of invoices:

  • Membership renewal (single installment)

  • Subscription renewal (single installment)

  • Certification renewal (single installment)

  • Meeting registration

  • Exhibits

Note

This procedure does not create automatic payments for new member dues invoices, renewal benefits set up to be paid in installments, monetary pledge installments, or recurring gift installments.

Membership, subscription, or certification renewal invoices that are eligible for AutoPay Invoices include those where:

  • An eligible payment demographic records exists for the renewal billing invoice BillTo customer (account or contact)
  • The eligible payment demographic record modules for membership, subscriptions or certification = Allow
  • The renewal billing invoice balance due > $0.00
  • The related renewal billing record benefit status = new, renew, or reinstated
  • The related renewal billing record number of installments = 1
  • The related renewal billing record expiration date (required) = [date selected]
  • The related renewal billing record benefit (optional) = [benefit selected]
  • The related renewal billing record rate (optional when benefit is selected) = [rate selected]

Meeting invoices that are eligible for AutoPay invoices include those where:

  • An eligible payment demographic records exists for the invoice BillTo customer (account or contact)
  • The eligible payment demographic record module for meetings = Allow
  • The invoice balance due > $0.00
  • The meeting (required) = [meeting selected]
  • The meeting registration (optional) = [registration selected]

Exhibit invoices that are eligible for AutoPay invoices include those where:

  • An eligible payment demographic records exists for the invoice BillTo customer (account or contact)
  • The eligible payment demographic record module for exhibits = Allow
  • The invoice balance due > $0.00
  • The exhibit (required) = [exhibit selected]

To process automatic payments for eligible invoices, in the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > AutoPay Processes > AutoPay Invoices.

In the AutoPay Invoices window, select the batch for processing the AutoPay credit card payment transactions.

Note

For control purposes, we recommend that you use separate batches for the payment transactions for each type of invoice. For example, if you want to create payments for membership renewal invoices and meeting registration invoices, use one batch for the membership payments and a different batch for the registration payments. This makes it easier to locate and track the different types of transactions.

Important Note

When identifying eligible payment demographic records for AutoPay Invoices, UX evaluates the accounting company of the batch selected for AutoPay processing against the accounting company of the credit card product setup selected as the payment source in the payment demographic record. If there is not a match, the invoice is not eligible for AutoPay Invoices processing.

To limit the amount of the automatic payments created, enter the maximum balance due that you want to process. Invoices with a balance due greater than this amount will not be selected for payment.

Use the Search sections to identify the invoices you want to generate automatic credit card payments for:

  • Membership – Enter an expiration date. You can also search for invoices by membership benefit, rate, or both.
  • Subscription – Enter an expiration date. You can also search for invoices by subscription benefit, rate, or both.
  • Certification – Enter an expiration date. You also can search for invoices by the certification.
  • Meetings – Enter or select a meeting. After selecting a meeting, you can also search for invoices by registration.
  • Exhibits – Select the exhibit for the invoices you want to create automatic payments.

Important

The expiration date for membership, subscription, and certification renewal invoices refers to the expiration date in the related renewal billing record. The process will only select ‘renewal’ invoices with the exact date that you enter. It does not select new renewal invoices.

Click OK.

UX Online will search for invoices that match the criteria you entered, where the account or contact in the invoice Bill To field has an eligible Payment Demographics record. A dialog will appear, displaying the number of invoices that met the search criteria entered.

Click OK to authorize credit card payments for these invoices.

Processing automatic credit card payments for renewal installments

The AutoPay for Renewal Installments process is designed to work with new membership and new subscription invoices with multiple installments where at least the first installment has been paid and also with renewing membership and subscription invoices with multiple installments. For eligible multiple installment renewal invoices, the process generates credit card payment transactions where the renewal billing invoice BillTo account or contact has an eligible payment demographic record.

Note

This process does not include automatic payments for one-time invoices, such as meetings, exhibits, or single installment renewal billing invoices. For information about AutoPay and invoices, see Processing automatic credit card payments for invoices.

To process automatic payments for eligible multiple installment renewal billing invoices, in the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > AutoPay Processes > AutoPay for Renewal Installments.

In the AutoPay for Renewal Installments window, select the batch for processing the AutoPay credit card payment transactions.

Note 

For control purposes, we recommend that you use separate batches for the payment transactions for each type of renewal. For example, if you want to create payments for membership renewal installments and subscription renewal installments, use one batch for the membership installment payments and a different batch for the subscription installment payments. This makes it easier to locate and track the different types of transactions.

Important Note 

When identifying eligible payment demographic records for AutoPay for Renewal Installments, UX evaluates the accounting company of the batch selected for AutoPay processing against the accounting company of the credit card product setup selected as the payment source in the payment demographic record. If there is not a match, the invoice is not eligible for AutoPay for Renewal Installments processing.

To limit the amount of the automatic payments created, enter the maximum balance due that you want to process. Installment invoices with a balance due greater than this amount will not be selected for payment.

Select the module you want to create payments for – membership or subscriptions.

If you want to restrict the installments you want to generate automatic credit card payments for, you can select the specific benefit and rate.
Enter or select the Next Installment Due Date of the installments you want to process for payment. This is the paid through date indicated on the installment invoice detail line item – not the paid through date on the renewal billing record.

Important

The process will look for installments with paid through dates up to the date that you enter. For example, assume that you have a customer with two unpaid membership installment payments—one with a paid through date of 6/30/2017 and the second with a paid through date of 12/31/2017. If you enter 6/30/2017 as the Next Installment Due Date in the AutoPay Process window, the process will pay only the first installment. If you enter 12/31/2017, the process will pay both installments.

Click OK to search for eligible records that match the criteria you entered, where the account or contact in the invoice’s Bill To field has an eligible Payment Demographics record modules for Membership or Subscriptions = Allow.

A confirmation dialog will appear, displaying the number of records that met the search criteria. Click OK to authorize credit card payments for these installments.

Processing automatic credit card payments for monetary pledge installments

Eligible monetary pledge installment invoices are those with a balance due > $0.00, where the pledge installment invoice detail is not cancelled, contains an eligible Payment Demographic record, and the AutoPay Status is Active. See Creating a Monetary Pledge Contract for more information.

Important Note

When identifying eligible payment demographic records for AutoPay for Monetary Pledge Installments, UX also evaluates the accounting company of the batch selected for AutoPay processing against the accounting company of the credit card product setup selected as the payment source in the payment demographic record. If there is no match, UX Online creates a new batch for the “unmatched” accounting company with a batch name = ‘AutoPay (Automatically Created)’ and currency = default currency. This allows AutoPay to process pledge installment payment transactions for the “unmatched” accounting company in the system-created AutoPay batch.

To process automatic payments for monetary pledge installment invoices, in the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > AutoPay Processes > AutoPay for Monetary Pledge Installments.

In the AutoPay Process window, select the batch for processing the AutoPay credit card payment transactions.

Note

For control purposes, we recommend that you use separate batches for creating AutoPay pledge installment payment transactions. This makes it easier to locate and track the transactions.

Enter the Installment Date for the monetary pledge installments to be processed for payment.

Click OK to search for eligible invoices with pledge installment invoice detail that matches your search criteria.

A confirmation dialog will appear, displaying the number of invoices that met the search criteria. Click OK to authorize credit card payments for these invoices.

Processing automatic credit card payments for recurring gift installments

Eligible recurring gift installment invoices are those with a balance due > $0.00, where the recurring gift invoice detail is not cancelled, contains an eligible Payment Demographic record, and the AutoPay Status is Active. See Creating a recurring gift invoice for more information.

Important Note

When identifying eligible payment demographic records for AutoPay for Recurring Gifts, UX also evaluates the accounting company of the batch selected for AutoPay processing against the accounting company of the credit card product setup selected as the payment source in the payment demographic record. If there is no match, UX Online creates a new batch for the “unmatched” accounting company with a batch name = ‘AutoPay (Automatically Created)’ and currency = default currency. This allows AutoPay to process recurring gift installment payment transactions for the “unmatched” accounting company in the system-created AutoPay batch.

To process automatic payments for recurring gift installments, in the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > AutoPay Processes > AutoPay for Recurring Gift Installments.

In the AutoPay Process window, select the batch for processing the AutoPay credit card payment transactions.

Note

For control purposes, we recommend that you use separate batches for creating AutoPay recurring gift installment payment transactions. This makes it easier to locate and track the transactions.

Enter the Installment Date for the recurring gift installment invoices to be processed for payment.

Click OK to search for invoices containing eligible recurring gift invoice detail that matches your search criteria.

A confirmation dialog will appear, displaying the number of invoices that met the search criteria. Click OK to authorize credit card payments for these invoices.

Re-authorize Payment Demographics Records

This maintenance utility allows you to re-authorize eligible Payment Demographics records to update the Authorization Number (Reference ID) used for AutoPay without processing a credit card payment transaction (similar to the initial authorization on a payment demographic record). Designed for customers that use AutoPay annually or less frequently, the re-authorization of eligible records will minimize AutoPay declined authorizations based on “Original Transaction ID Not Found” where the Payflow Pro reference transaction has expired (reference transactions expire 365 days after the last authorization date).

This utility is available in the Navigation Tile Bar, by selecting the Financial Manager work area > Payment Processes > AutoPay Processes > Re-Authorize Payment Demographics.

Payment Demographics records eligible for re-authorization

Payment Demographics records eligible for re-authorization using this utility include those where:

  • Record status = Active

  • Authorization Date is greater than the system date, less 12 months

  • Credit Card Expiration Date is greater than the system date (ignores expired)

  • Credit Card Has Problem <> True

To identify records eligible for re-authorization, create an Advanced Find on the Payment Demographics entity, using the following search criteria:

Status: Equals Active
Authorization Date: Older than X Months 12
Expire Date: On or After [system date + 1 day]
Credit Card Problems: Does Not Equal Yes

When an eligible record is re-authorized

When an eligible Payment Demographics record is successfully re-authorized by PayPal, the system updates the Authorization Date and the Authorization Number fields. Additionally, an entry is created in the Credit Card Log entity.

When an eligible record is not re-authorized

If an eligible record is not successfully re-authorized by PayPal, the system updates the Payment Demographics record Credit Card Has Problem = True and a description of the error is entered in to the Problem Description field. As an example, this may occur if the reference transaction has already expired or is not longer valid at PayPal.

Possible errors that would trigger Credit Card Has Problem = True:

  • 19 – Original transaction ID not found

  • 23 – Invalid account number
  • 24 – Invalid expiration date

  • 25 – Transaction type not mapped to this host (Processor)

  • 50 – Insufficient funds available

  • 99 – General error

  • 112 – Failed AVS check

  • 114 – CVV2 Mismatch

By updating the Credit Card Has Problem = True, the record will be excluded from further AutoPay processing until the Payment Demographics record is successfully re-authorized. Once the Payment Demographics record is successfully re-authorized, the problem attributes are cleared and the record is again eligible for AutoPay processing.

Note

The Credit Card Number and Expire Date fields are now enabled to allow users to enter a valid credit card information and re-authorize an existing Payment Demographics record.

Identifying records processed for re-authorization

Identify records that fail re-authorization

You can identify eligible records that failed re-authorization through an Advanced Find query where Modified On = the system date that you ran the utility, Modified By = the user who ran the utility, Problem = True. This query should be run immediately after running the utility. This is an opportunity to contact your customers and obtain current credit card information to update and re-authorize their Payment Demographics record so that it is available for AutoPay processing.

Identify records successfully re-authorized

You can identify successfully updated eligible Payment Demographics records through an Advanced Find query where Authorization Date = system date that you ran the utility, Modified On = the system date that you ran the utility, Modified By = the user who ran the utility, Problem <> True.

Payment Demographics record recommended actions

To minimize declined AutoPay transactions that rely on the Payment Demographics record, you should consider data cleanup of your Payment Demographics records before running the re-authorization utility and before running AutoPay processes. This will minimize (not eliminate) declined transactions. This is also an opportunity to contact your customers and obtain current credit card information to create a new or re-authorize an existing Payment Demographics record. Recommendations include:

  • Run an Advanced Find query on Active Payment Demogrpahics records where the Authorization Date is less than the system date end of month less 12 months. Through Advanced Find, you can update the status of these records to inactive using the Edit function. Because Payflow Pro expires reference transactions 365 days from the last authorization date, deactivating the Payment Demographics records will prevent them from being captured in the re-authorization utility and/or being used for AutoPay processing (and thus incurring a transaction fee). Alternatively, you can obtain updated information from your customers and re-authorize the existing records.

  • Regularly run an Advanced Find query on active Payment Demographics records where credit card Expiration Date is less than the system date (end of month). These records are expired. You can update the record status to inactive using the Advanced Find Edit function to exclude them from the utility or obtain updated information from your customers and re-authorize the existing records.

Chapter 18: Gift Certificates

If your organization issues gift certificates to contacts—either members or non-members—that they can use as payments on product and service invoices, you can track those transactions in UX Online.

This documentation assumes that you have already set up the gift certificate payment product records you need. For more information about creating gift certificate payment products, see Payment and Adjustment Product Setup.

This chapter contains instructions on defining set up defaults for gift certificates, types of gift certificates, issuing gift certificates to a contact, and accepting them as a payment type in a payment transaction.

  • Setting gift certificate defaults

  • Payment Options: Use in Full vs. Multiple Payments Allowed

  • Issuing a gift certificate to a contact

  • Viewing the status of a contact’s gift certificates

  • Viewing the status of all gift certificates

  • Applying a gift certificate payment to an invoice

  • Voiding a gift certificate payment

Setting gift certificate defaults

You can define defaults for all gift certificates that you issue that control gift certificate numbering, restrict use to the issued-to contact, and control whether the gift certificate payment can exceed the invoice balance.

These default settings are managed by UX Online Application Parameters, as described below.

Gift certificate numbering

You can set the system to number your gift certificates automatically, or you can require the users creating new gift certificates to enter a gift certificate number manually. If your system is set up to assign gift certificate numbers automatically, the numbering will begin at 1 when your system is deployed and increase by increments of 1 for each new gift certificate.

You can manage automatic numbering by the Config value of the PAGiftCertificate.Number application parameter.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters. This List View opens in a new window. Locate and open the parameter PAGiftCertificate.Number.

If you want UX Online to set the gift certificate number to the next available number automatically, set the Config Value field to AUTO. If you want users to enter the number manually when they create a new gift certificate, set it to MANUAL. Changes to this setting will become effective with the next gift certificate you issue.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Restrict gift certificate use to the contact

By default, UX Online allows you to apply a gift certificate issued to any contact as a payment on any invoice, regardless of who the customer is.

However, you can set up the system to restrict gift certificate payments on an invoice. In this case, you can only apply a gift certificate that has been issued to the contact on the invoice or to the customer’s parent customer contact. You can manage this by changing the default Config value of the PAGiftCertificate.FilterbyIssuedTo application parameter.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters. This List View opens in a new window. Locate and open the parameter PAGiftCertificate.FilterbyIssuedTo.

If you want UX Online to restrict gift certificate payments to gift certificates issued to the invoice contact or the parent customer contact, change the Config Value field to TRUE. If you want to allow gift certificates issued to any contact to be used as payment by any customer on an invoice, leave the default Config value to FALSE.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Allow gift certificate payments in excess of the invoice balance

By default, UX Online does not allow you to apply a gift certificate payment amount in excess of the invoice balance because it results in a credit balance on the invoice.

However, you can set up the system to allow gift certificate payments that exceed the invoice balance by changing the Config value of the PAGiftCertificate.AllowOverBalance application parameter.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters. This List View opens in a new window. Locate and open the parameter PAGiftCertificate.AllowOverBalance.

If you want UX Online to allow gift certificate payments to exceed the invoice balance (resulting in a credit balance on the invoice), set the Config Value field to TRUE. If you do not want to allow gift certificate payments to exceed the invoice balance, leave the default Config value to FALSE.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Payment Options: Use in Full vs. Multiple Payments Allowed

When you issue a gift certificate to a contact, you have two payment options: Use in Full or Multiple Payments Allowed.

If you select Use in Full, an unexpired gift certificate can be used one time only, up to the full amount of the certificate. When this certificate is applied to an invoice with a balance due less than the gift certificate amount, the excess amount is forfeited and the certificate balance updates to $0.00.

If you select Multiple Payments Allowed, an unexpired gift certificate can be used multiple times, on multiple invoices, up to the full amount of the certificate. Each time this certificate is applied to an invoice, the payment amount is deducted from the certificate balance and the certificate is available for re-use until the certificate balance is $0.00 or it expires.

Any gift certificate, regardless of its payment option, can be used as payment on an invoice up to but not exceeding the gift certificate amount, as long as it has not expired.

Issuing a gift certificate to a contact

To issue a gift certificate to contact – either a member or a non-member – you will attach a gift certificate record to the contact record. The gift certificate can then be applied to an invoice as a form of payment. For more information, see Applying a gift certificate to an invoice.

Gift certificates can be issued from within a contact record, as described below, or from the Gift Certificates list (in the Navigation Tile Bar, select Financial Manager work area > Accounting Manager > Gift Certificates). Whether you begin the process from a contact record or the Gift Certificates list, the process is the same, with one exception: If you begin the process from the Gift Certificates list, you will select the contact after creating the new gift certificate.

From any of the UX work areas on the Navigation Tile Bar, click Contacts. Open the contact record where you want to create a gift certificate.

In the Navigation Pane of the contact record, click Gift Certificates to open the Gift Certificate Associated View. Click Add New Gift Certificate on the List View toolbar.

In General section of the Gift Certificate record, enter the information for this gift certificate:

  • Use Prefix – If want the gift certificate ID to include a prefix that you specify, select Yes.

  • Certificate Prefix – If you selected Yes for the Use Prefix option, enter the ID prefix for this gift certificate.

  • Identification – If your system is set up for manually numbered gift certificates, enter an alphanumeric ID for this gift certificate. If your system is set up to automatically number gift certificates; this field is disabled and an ID number will appear when you save this record.

  • Issued to – Displays the contact you are issuing this gift certificate to.

  • Campaign ID – If this gift certificate is associated with an existing campaign, click the Lookup button to select the campaign.

  • Payment Option – Select Use in Full if this gift certificate can only be used one time or Multiple Payments Allowed if this gift certificate can be used for multiple payments.

  • Amount – Enter the amount of the gift certificate.

  • Product – Click the Lookup button to select the payment product for this gift certificate.

  • Date Issued – Enter the date that this gift certificate was issued.

  • Owner – Displays the user ID of the user who created this record.

  • Currency – If necessary, click the Lookup button to select the appropriate currency for this gift certificate.

  • Expiration Date – Enter the date that this gift certificate will expire. On this date, the gift certificate will no longer be available for use.

In Gift Certificate Tracking section of the Gift Certificate record, the following information is available:

  • Received On – Optional field where you can enter the date the contact received the certificate.

  • Certificate Balance – System field that displays the amount remaining on the gift certificate. For unused certificates, this will be the amount of the issued certificate. Once used:

    • For a Use in Full certificate, the system displays $0.

    • For a Multiple Payments Allowed certificate, the system displays the remaining amount available.

  • Status – System field that displays the status of the gift certificate. This will be updated by the system as the certificate is used. The values differ based on the payment option for the certificate.

    • Issued – Appears when the certificate is first issued.

    • Used – Indicates when a certificate with the Multiple Payments Allowed payment option has been used at least once but still has a balance available.

    • Cashed – Appears when the certificate balance is zero.

  • Used On – System field that displays the most recent date that this gift certificate was applied to an invoice. For newly issued gift certificates, this field will be blank.

  • Amount Used – This field is blank until the gift certificate has been applied as a payment on an invoice.

    • For a Use in Full certificate, the system displays the original amount of the gift certificate, regardless of the amount applied to the invoice. For example, if the gift certificate has a value of $50, and it is applied to an invoice with a balance of $40, the Amount Used field will display $50.

    • For a Multiple Payments Allowed certificate, the system displays the total amount that has been applied to invoices. For example, if the gift certificate has a value of $50, and has been applied to one invoice with a balance of $40, the Amount Used field will display $40

Click Save & Close to save the gift certificate and return to the Gift Certificates list.

Additional information

  • Click Gift Certificate Payments in the Navigation Pane to view all invoices where this gift certificate has been applied as payment.

Viewing the status of a contact’s gift certificates

You can view the status of the gift certificates issued to a contact. From any of the UX work areas on the Navigation Tile Bar, click Contacts. Locate and open the contact record. In the Navigation Pane of the contact record, click Gift Certificates to view a list of gift certificates issued to this contact. To view details about an individual gift certificate, double-click it in the list to open it.

Viewing the status of all gift certificates

You can view the status of all gift certificates that your organization has issued from the Gift Certificates list. In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Gift Certificates to view a list of all gift certificates issued. To view details about an individual gift certificate, double-click it in the list to open it.

Applying a gift certificate payment to an invoice

When using a gift certificate as payment for an invoice, you enter it using a gift certificate payment transaction.

From any of the UX work areas on the Navigation Tile Bar, click Contacts Open the contact record where you want to enter a gift certificate payment. In the Navigation Pane of the record, click Invoices. Locate and open the appropriate invoice. Click Select Batch to select the batch you are using for this transaction.

Select New Transactions > Payments & Adjustments > Gift Certificate from the invoice Record toolbar.

In the General section of the Payment record, enter the following information:

  • Product – Click the Lookup button to select the appropriate product for the gift certificate payment. Only gift certificates created with the selected payment products that match the invoice currency are available in the lookup. If no product is available, you must complete your gift certificate product setup before you can proceed.

  • Payment – Before selecting the Gift Certificate, this defaults to the balance due on the invoice. Once you select the Gift Certificate, if the invoice balance due is less than the gift certificate balance, displays the balance due on the invoice. If the gift certificate balance is less than the invoice balance due, this field displays the remaining value of the gift certificate. If the gift certificate payment option is Multiple Payments Allowed, you can change this amount to a smaller value. If the gift certificate payment option is Use In Full, you cannot change the amount.

Note

If the gift certificate is set up to be used in full, and its value is greater than the balance due, the remaining balance on the gift certificate will be lost; it cannot be applied to any other invoices. If the gift certificate is set up to allow use for multiple payments, its remaining value can be applied to other invoices.

  • Gift Certificate – Click the Lookup button to select the gift certificate the contact is using on this invoice. If no certificates are available, no gift certificates are available under the payment product selected.

  • Reference – Enter a note to help identify this gift certificate transaction

  • Batch – Automatically displays your selected batch. Do not change this field.

  • Transaction Date – Displays the batch date.

The system populates the fields in the Payee Information section of the Gift Certificate Payment record, based on the following conditions.

  • If the invoice Bill To Customer is an account, the system pulls the name and primary address of the primary contact into the Payee Information fields. If there is no primary contact, the Payee information fields are blank. These fields are available for editing, if necessary.

  • If the invoice Bill To Customer is a contact, the system pulls the name and primary address of the contact into the Payee Information fields. These fields are available for editing, if necessary.

Click Save & Close to save the payment transaction and return to the invoice. Review the new gift certificate payment transaction line item to ensure that it is correct. Review the invoice totals to ensure that the fields are calculated correctly.

Click Save & Close to save and close the invoice and return to the invoices list.

Voiding a gift certificate payment

If there is an error on a gift certificate payment transaction, you can void the payment transaction.

When you void a gift certificate payment, the system will automatically create invoice entries that reverse the original payment transaction. In addition, the gift certificate will be restored back to its state prior to the payment:

  • If it is a single-use certificate (that is, the payment option is Use in Full), its status will be reset to Issued, and the certificate balance will be reset to the original amount.

  • If it is a multiple-use certificate (that is, the payment option is Multiple payments allowed), its status will be reset to either Issued or Used (depending on what it was before the payment), and the certificate balance will be increased by the payment amount.

Note

You cannot delete a gift certificate payment transaction from the invoice transaction detail list.

From any of the UX work areas on the Navigation Tile Bar, click Contacts Open the contact record where you want to void a gift certificate payment. In the Navigation Pane of the record, click Invoices. Locate and open the appropriate invoice. Click Select Batch to select the batch you are using for this transaction.

Open the original gift certificate payment detail line item that you want to void. Click the Void Gift Certificate button on the Record toolbar.

A message will appear, asking you to confirm that you want to void this gift certificate payment. Click OK to process the void payment.

In the list of invoice detail line items, the original gift certificate payment will reflect the void and a new void transaction will appear. The balance field will be updated based on the voided amount.

Click Save & Close to save your changes and close the invoice.

Chapter 19: Credit Card Transaction Daily Settlement

This chapter contains basic instructions on the daily settlement procedures for settling your authorized credit card transactions. Using the best practices, reports, and prescribed batch management protocols described in this documentation, daily settlement relies on completion of two key components:

  • Daily Closing, which processes authorized transactions through UX Online Credit Card Payment Delayed Capture.

  • Reconciliation of UX Online captured credit card transactions to the transactions in your Payflow Pro Manager account, following the procedures in place for your organization.

This documentation assumes that your organization is following the best practice for creating GL Detail and posting batches to your accounting system on a regular (daily preferred) basis.

This information includes the following sections:

  • Credit card daily closing overview

  • Printing the UX Credit Card Authorization by Batch Report

  • Closing the daily credit card batch

  • Running the credit card payment delayed capture process

  • Automatically running delayed capture

  • Printing credit card reports

  • Creating GL detail for a credit card batch and mark as Ready to Post

Credit card daily closing overview

The daily closing process for credits cards is very important. The delayed capture process flags all pre-authorized payments in UX Online as ready for settlement in Payflow Pro. This process is part of the daily reconciliation of all cash and equivalent transactions. If you do not run the delayed capture process, the transactions will not be available for the merchant to capture in order to finalize the transactions and process payment to your organization for those amounts.

We recommend that you use the following checklist as your organization’s standard operating procedures for closing each day’s credit card batch:

Note

Protech recommends that your organization separate credit card charges from checks received and deposited in order to reflect this activity accurately on the General Ledger and the Bank Statement.

  • Enter all credit card charges using this batch. This includes entering invoices with payment, adding a payment to an existing invoice, and entering payments in RapidPay.

  • Stop credit card authorization processing at a pre-determined time every business day. Through your organization’s business processes, determine a stopping point every day; no more transactions should be added to the daily credit card batch after this point.

  • Print the UX Credit Card Authorization by Batch Report to verify the accuracy of the charges entered. For more information, see Printing the UX Credit Card Authorization by Batch Report.

  • Close the daily credit card batch. The delayed capture process will not capture any credit card transactions in open batches. For more information, see Closing the daily credit card batch.

  • Run the credit card delayed capture process to capture all authorized and uncaptured credit card transactions and make them available to your merchant for processing. For more information, see Running the credit card payment delayed capture process.

  • Print the UX Online credit card reports to verify the credit card transaction history. For more information, see Printing credit card reports.

  • Create GL detail for the credit card batch, and then post it. For more information, see Creating GL detail for a credit card batch and mark as Ready to Post.

  • After completing these procedures, we recommend that you reconcile the captured credit card transactions with the transactions in your Payflow Pro Manager account, following the procedures in place for your organization.

Printing the UX Credit Card Authorization by Batch Report

After you have stopped authorizing credit cards for the day, print the UX Credit Card Authorization by Batch Report. Use this report to verify the accuracy of the credit card charges that were entered, using your organization’s method. For example, your organization might require that you verify the charges against the original source documents.

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online reports. In the Reports list, open the UX Credit Card Authorization by Batch Report.

Enter the batch number of the daily credit card batch in both the Greater Than or Equal To and Less Than or Equal To fields, and click Run Report to generate the report.

Use this report to verify the accuracy of the charges entered, using the method determined by your organization.

When you are satisfied with the accuracy of the charges, continue with the next step of the credit card daily closing checklist: Closing the daily credit card batch.

Closing the daily credit card batch

After you have verified the accuracy of the day’s credit card charges (see Printing the UX Credit Card Authorization by Batch Report for more information), close the batch created for these charges. The delayed capture process will not process any credit card transactions in an open batch. (In addition, closing the batch keeps any additional credit card transactions from being added and prevents any changes to the existing transactions.)

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window.

Locate and open the daily credit card batch. Click the Closed checkbox to mark the batch as closed. Do not mark checkboxes for Ready for GL Detail or Ready for Post.

Click Save & Close to return to the list of batch log records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Continue with the next step of the credit card daily closing checklist: Running the credit card payment delayed capture process.

Running the credit card payment delayed capture process

After you have the closed the daily credit card batch (see Closing the daily credit card batch for more information), you can run the delayed capture process for credit card payments. This process captures all authorized, uncaptured credit card transactions in closed batches and makes them available to your merchant for processing at a time determined by your merchant. Only authorizations with an amount greater than 0.00 will captured for processing.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Credit Card Payments Delayed Capture Process.

The Credit Card Payments Delayed Capture Process dialog box appears, displaying the Capture ID that will be used for this process. (This is an incremental number assigned by the system.) Make note of this ID; you will use it to generate credit card reports to verify this process. Click OK to complete the delayed capture process.

After the delayed capture process is complete, we recommend that you print the UX Online credit card reports to validate the results. For more information, see Printing credit card reports.

Automatically running delayed capture nightly

You can configure your system to run the delayed capture process for closed credit card batches automatically on a nightly basis as part of the UX Nightly Process System Job. You can do this by setting the value of the PANightlyProcess.RunDelayCapture application parameter.

Note

This nightly process will run at a time set up when your UX Nightly Process System Job was configured.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters. This View opens in a new window. Locate and open the parameter PANightlyProcess.RunDelayCapture.

If you want UX Online to run delayed capture on closed batches automatically, set the Config Value field to TRUE. If you do not want to run delayed capture automatically, set the Config value to FALSE.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Note

UX can also be customized to automatically run the delayed capture process nightly on a custom schedule. Please see your Protech representative for additional information on this customization.

Printing credit card reports

After completing the credit card delayed capture process (for more information, see Running the credit card payment delayed capture process), we recommend that you print the following UX Online credit card reports to verify your credit card transaction history:

  • UX Credit Card Authorization by Authorized Date

  • UX Credit Card Authorization by Capture ID

  • UX Credit Card Authorization by Batch

  • UX Credit Card Summary by Capture ID

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online reports. In the Reports list, open each report you want to print.

Enter the required search criteria. Click Run Report to generate the report. Because the reports list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

After printing and validating the information on these reports, you can create the GL detail for the credit card batch, and post it. For more information, see Creating GL detail for a credit card batch and mark as Ready to Post.

Creating GL detail for a credit card batch and mark as Ready to Post

After the delayed capture process is complete (see Running the credit card payment delayed capture process for more information), you must create the GL detail for the batch and post it to your accounting system. (Creating GL detail for a batch creates the detailed debits and credits associated with the transactions in the batch, which will be posted to your General Ledger system.)

See Creating GL Detail for a batch and Posting a batch for creating GL detail and posting to your accounting system.

Note

If you have any questions about the business processes surrounding this type of transaction, please contact the accounting manager at your organization.

After posting the credit card batch, the final step in the credit card daily closing process is to reconcile UX Online credit card transactions with the transactions in your Payflow Pro Manager account.

Chapter 20: Revenue Recognition

This chapter describes the processes you will use to recognize deferred revenue. Deferred revenue is earned from renewal transactions (such as membership, and subscriptions), and from event transactions (exhibits, meetings, registrations, and sessions). Recognizing revenue is the process of transferring revenue from the deferred revenue GL accounts to the revenue GL accounts.

This part of the documentation includes the following information:

  • About deferral flags

  • About event revenue recognition

  • About course revenue recognition

  • Recognizing an event’s revenue

  • Recognizing event and course revenue by date

  • Recognizing revenue for memberships and subscriptions

  • Restore Meetings and Exhibits Product GL Accounts

  • Close date related revenue recognition

About deferral flags

In order to manage revenue recognition processing in UX Online, whether it is incremental as is the case with recognizing date-related revenue (membership and subscriptions, and events by date) or all at once as is the case with recognizing revenue by event, UX Online assigns a deferral flag to each GL detail record.

GL detail is created for standard batch types and when recognizing revenue using one of the revenue recognition batch type processes described in more detail later in this section. As shown in the table below, the deferral flag assigned to the GL detail record is based on the type of deferred account used for the Primary GL account in the underlying transaction product setup:

  • Deferred – Membership and Subscriptions

  • Deferred – by Date

  • Deferred – by Event

You can run the Close Date Related Revenue Recognition batch process to update the deferral flags as closed for date-related GL detail for receipts, deferral, and revenue once revenue has been fully recognized. This will exclude them from further revenue recognition processing for Membership and Subscriptions and Event by Date. For example, during the close date batch process, the system will update the deferral flag in the deferral GL detail of a fully recognized membership from D to F, the revenue GL detail from I to K, and the receipt GL detail from C to B.

Updated deferral flag values for close date related GL detail are shown in the three columns to the right in the table below. See Close Date Related Revenue Recognition for additional information on this process.

Note

This process does not affect the deferral flags for deferral and revenue where the deferred account type in the primary GL account is Deferred – by Event because revenue recognition by event is event specific.

Deferral Flag Values

Primary GL Account – Deferred Account Type

Assigned when creating GL Detail for Standard and Revenue Recognition Batch Types

Updates to existing GL Detail record during the Close Date Related Revenue Recognition Process

Receipts

Deferral

Revenue

Receipt Close

Deferral Close

Revenue Close

Deferred – Membership and Subscriptions

C*

D

I

B

F

K

Deferred – by Date

S

T

V

R

U

W

Deferred – by Event

E

J

Not applicable

*The term “Receipts” is used because usually these are Cash Basis and the “C” entry occurs when the GL is created for a payment. If they are Accrual Basis then the “C” entry occurs when GL is created for a charge line.

About event revenue recognition

If your association defers the revenue associated with an event, you will need to run the revenue recognition process. Recognizing revenue is the process of transferring event revenue (that is, revenue from all of the associated exhibits, meetings, sessions, and registrations) from the deferred revenue GL accounts to the revenue GL accounts. These accounts were selected when you set up the event’s exhibits, meetings, sessions, and registrations.

UX Online gives you two options for recognizing event revenue:

  • Revenue Recognition by Event – You can recognize all of an event’s deferred revenue at once, after the event is over and all of the associated transactions have been entered and posted. For more information, see Recognizing an event’s revenue.

  • Revenue Recognition by Date – You can recognize portions of an ongoing event’s revenue by date. For example, assume that you offer training that takes place in a series of meetings spread over several months. Each month, you can recognize a portion of the revenue for that training. For more information, see Recognizing event and course revenue by date.

Note

Revenue Recognition by Date also recognizes revenue for any course purchased through the Professional Development module. For more information, see About course revenue recognition.

You can use both methods within a single organization, but you should not mix methods for a single event. For example, if you recognize a portion of the revenue for Event A using the by Date method, you should not use the by Event Number method to finish recognizing revenue for that event.

About course revenue recognition

If your association defers the revenue associated with a Professional Development course, you will need to run the revenue recognition process. Recognizing revenue is the process of transferring course revenue (that is, revenue from Professional Development course transactions) from the deferred revenue GL accounts to the revenue GL accounts. These accounts were selected when you set up the course.

Note

If course participation is part of a meeting registration, revenue recognition for that course is done as part of the event revenue recognition process. For more information, see About event revenue recognition.

To recognize deferred revenue for Professional Development course transactions, you will use the Revenue Recognition by Date process. For more information, see Recognizing event and course revenue by date.

Recognizing an event’s revenue

You can recognize the revenue for a single event by using a special batch type: Revenue Recognition by Event. When you create a batch of this type, you will identify the event that this batch will be used for. A Revenue Recognition by Event batch can only be used to recognize income from transactions for a single event; it cannot be used for any other types of transactions or batch processes. It should only be run after the event is ended and all transactions related to the event are complete.

The Revenue Recognition by Event batch process performs the following actions:

  • Searches for transactions for the selected event where GL detail has been created and creates GL detail for posting in the accounting system, by summarizing and transferring revenue from the deferred revenue GL account to the revenue GL account.

  • Replaces the Primary GL account with the Secondary GL account in the product setup.

This batch process does not close the event. You must perform this manually in the event record.

Important

Do not use a Revenue Recognition by Event batch type for an event that has a Deferred – by Date account set up as the deferred revenue account for its associated records. This process works only for an event that has a Deferred – by Event account set up as the deferred revenue account for its associated records.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window.

Create a new Revenue Recognition by Event batch for each event that you want to process (Batch Type = Revenue Recognition by Event; see Creating a batch in UX Online).

UX will mark the batch Closed. Do not mark the Ready for GL Detail and Ready To Post checkboxes in the batch log record.

Click Save & Close on the batch log record to return to the list of active batch log records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Create GL Detail and post to accounting. See Creating GL Detail for a batch and Posting a batch for creating GL detail and posting to your accounting system. The appropriate GL detail will be created for these batches, summarizing the deferred revenue for each event and creating the transactions to transfer it to the revenue accounts defined in each event record.

Print the Account Distribution report and any other posting reports required by your association.

Print the UX Account Distribution Detail by GL Account and compare the account balances for the deferred income accounts to the balances in the Microsoft Dynamics GP GL Detail Inquiry Report or the Microsoft Dynamics SL Detail General Ledger Report.

Recognizing event and course revenue by date

You can recognize the revenue for events and courses by date by using a special batch type: Revenue Recognition by Date. When you create a batch and assign it to this type, the batch date should be the end of the revenue recognition period. For example, if you want to recognize the portion of event and course revenue for January 2016, you would enter 01/31/2016 as the batch date.

When you recognize event and course revenue by date, UX Online calculates the amount of event and course revenue to recognize using the following formula:

(Deferral Period Days/Event Period Days) x Total Event and Course Revenue = Period Recognized Revenue

Where:

  • Deferral Period Days = the number of days between the event’s or course’s start date or the last deferral date (whichever is later), and the batch date

  • Event Period Days = the number of days between an event’s or course’s start date and end date

A Revenue Recognition by Date batch can only be used to recognize income from transactions for events and courses; it cannot be used for any other types of transactions or batch processes.

Note

This process recognizes revenue only for events or courses that have a Deferred – by Date account set up as the deferred revenue account for its associated records.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window.

Create a new Revenue Recognition by Date batch for each event that you want to process (Batch Type = Revenue Recognition by Date; see Creating a batch in UX Online). Be sure to set the batch date as the end of the recognition period.

UX will mark the batch Closed. Do not mark the Ready for GL Detail and Ready To Post checkboxes in the batch log record.

Click Save & Close on the batch log record to return to the list of active batch log records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Create GL Detail and post to accounting. See Creating GL Detail for a batch and Posting a batch for creating GL detail and posting to your accounting system. The appropriate GL detail will be created for these batches, summarizing the deferred revenue for each event and creating the transactions to transfer it to the revenue accounts defined in each event record.

Print the Account Distribution report and any other posting reports required by your association.

Print the UX Revenue Recognition for Events by Date – Summary or the UX Revenue Recognition for Events by Date – Detail. These reports run off an “As of Date,” which will be the batch date of the batch you used to run the process.

Print the UX Account Distribution Detail by GL Account and compare the account balances for the deferred income accounts to the balances in the Microsoft Dynamics GP GL Detail Inquiry Report or the Microsoft Dynamics SL Detail General Ledger Report.

Recognizing revenue for memberships and subscriptions

If your association defers the revenue associated with memberships or subscriptions, you will need to run the Membership and Subscription Revenue Recognition process. This batch process transfers the membership or subscription revenue from the deferred revenue GL account to the revenue GL account. These accounts were selected when you set up the default membership product and the default subscription product for the renewal benefit. For more information, see Creating default dues and chapter billing products and see Creating a default subscription product.

Important

If your organization uses calendar-based dues, you must follow the guidelines provided in Membership Renewal Setup regarding revenue recognition deferral start and end dates with multiple installment rates. For important additional information, see Calendar-based dues prorate guidelines.

The revenue recognition process for memberships and subscriptions uses the batch date to determine the month-end date to be used for the process. All GL detail records used in the process are filtered to include only those with a fiscal date less than or equal to the month end of the batch log batch date. This allows the process to be run at any time and GL entries entered beyond the month-end date of the batch log batch date are ignored.

Important

You must create a batch to use for the revenue recognition transactions before running the process. The Batch Type field for this batch must be set to Membership and Subscriptions Revenue Recognition. For more information, see Creating a batch in UX Online.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window.

Create a new batch where batch type = Membership and Subscriptions Revenue Recognition (see Creating a batch in UX Online). Be sure to set the batch date as the end of the recognition period.

UX will mark the batch Closed. Do not mark the Ready for GL Detail and Ready To Post options for these batches.

Click Save & Close on the batch log record to return to the list of active batch log records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Create GL Detail and post to accounting. See Creating GL Detail for a batch and Posting a batch for creating GL detail and posting to your accounting system. The appropriate GL detail will be created for these batches, summarizing the deferred revenue for memberships and subscriptions and creating the transactions to transfer it to the revenue accounts.

Print the UX Account Distribution Report and any other posting reports required by your association.

Print the UX Account Distribution Detail by GL Account, and compare the account balances for the deferred income accounts to the balances in the Microsoft Dynamics GP GL Detail Inquiry Report or the Microsoft Dynamics SL Detail General Ledger Report.

Reversing Event Revenue Recognition

If you have run revenue recognition by event for a specific event (Revenue Recognition by Event) and find that you need to reverse this process, contact your Protech account manager for assistance before taking any action. In some cases, a reversal is possible. At a minimum, it will require the restoring the meeting and exhibit product GL account settings to their original state before you ran the revenue recognition by event batch process.

Restore Meetings and Exhibits Product GL Accounts

This process can be used to restore the original meeting and exhibit product GL accounts for an Event where the Revenue Recognition by Event process has been run. This is a necessary first step to reversing a previously run Revenue Recognition by Events. This process does not apply to Events where revenue has been recognized by date. It does not reverse previously run recognition.

How it works

There are two fields in the product table:  pa_PrimaryGLAccountSaved and pa_SecondaryGLAccountSaved. These fields store the Primary GL Account and Secondary GL accounts from the original meeting and exhibit product setup. When revenue was recognized by event, the recognition process updated the meeting and exhibit product GL account settings, changing the Primary GL Account from a deferred account to the revenue account.

When you run this process on the selected event (in the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Restore Meetings and Exhibits Product GL Accounts), the system uses the values in these two fields to restore the GL accounts in the product table to their original settings (before revenue was recognized for that event).

Close date related revenue recognition

You can run the Close Date Related Revenue Recognition batch process to update the deferral flags as closed for date-related GL detail for receipts, deferral, and revenue once revenue has been fully recognized. This will exclude them from further revenue recognition processing for Membership and Subscriptions and Event by Date.

This process searches for invoices that have been fully recognized as of a specified date. In this process, the specified date is equal to the batch date. It changes the deferral flag on the related GL Detail records so that they will not continue to show on the Revenue Recognition report or be included in future revenue recognition processes. By eliminating records that would otherwise have been included, the revenue recognition process will run faster.

This process is typically run after the end of your fiscal year. For example, if your fiscal year ends December 31, 2015, you would run this process sometime in January 2016 after all batches for that fiscal year have been posted and revenue recognized. When you create this batch type, the batch date you enter should be a date when you believe that no entries affecting revenue recognition will be needed for fiscal periods equal to or prior to that date.

Note

This process does not affect the deferral flags for deferral and revenue where the deferred account type in the primary GL account is Deferred – by Event because revenue recognition by event is event specific.

Important

You will not be able to reprint Revenue Recognition reports for fiscal periods equal to or prior to the batch date for Close Date Related Revenue Recognition batches.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window.

Create a new batch where batch type = Close Date Related Revenue Recognition (see Creating a batch in UX Online). Be sure to set the batch date as the end of the fiscal year for which you are closing date related revenue recognition.

UX will mark the batch Closed. Do not mark the Ready for GL Detail and Ready To Post options for these batches.

Click Save & Close on the batch log record to return to the list of active batch log records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Create GL Detail and post to accounting. See Creating GL Detail for a batch and Posting a batch for creating GL detail and posting to your accounting system.

The system will update the deferral flag in the deferral GL detail of a fully recognized membership from D to F, the revenue GL detail from I to K, and the receipt GL detail from C to B. This will exclude them from further revenue recognition processing for Membership and Subscriptions and Event by Date. See About deferral flags for more information.

Chapter 21: Lockbox Management

This chapter describes the processes for importing a file in a pre-defined format from a financial institution to create payments in any type of UX Online invoice. See Lockbox records for more information about defining the lockbox file format. With proper configuration, you can also use the import file to create monetary contribution invoice detail and payments. This application provides for viewing the data and error checking such as an Account or Contact ID and Invoice Number so that various bank “keying” errors can be corrected before importing the file.

This chapter includes the following topics:

  • Configure system for contribution transactions

  • Lockbox Import

  • Lockbox Data View

  • Lockbox Processing

Configure system for contribution transactions

By default, UX Online processes a monetary contribution lockbox extra as a monetary contribution invoice detail transaction. However, using the application parameter, PALockBox.ContributionAsProductSales, you can configure UX Online to process a monetary contribution lockbox extra using the invoice detail transaction type for monetary contributions or using the invoice detail transaction type for product sale. This provides clients upgrading from UX 2011 the option to continue creating these lockbox extra transactions as product sales or start creating these lockbox extra transactions as monetary contributions.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters. This View opens in a new window. Locate and open the PALockBox.ContributionAsProductSales application parameter.

When the config value = false, lockbox extra monetary contributions will be created using invoice detail for a monetary contribution and lockbox extra sales non-inventory products will be created using invoice detail for product sales. This is the setting that would be used for new UX Online clients who have no previous data considerations.

When the config value = true, all lockbox extra products will be created using the invoice detail for product sales, regardless of lockbox extra product type. This is the option to use if an upgrading client wishes to continue with the invoice detail type used in UX 2011 and previous versions for data continuity.

The default value for this parameter is false.

Lockbox Import

When you receive the pre-defined import file from the bank, save it to an accessible network location.

Create a new batch to use only for importing the bank lockbox file, selecting Standard GL Detail Creation for the batch type. For more information, see Creating a batch in UX Online. Do not use this batch for any other purpose, remembering to close it once you have completed lockbox processing to prevent inadvertent transaction entry in this batch by others.

To access Lockbox Import, in the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > Lockbox Management > Lockbox Import. In the Lockbox Import window, enter the following information:

  • File Name – Click the Browse button to locate the file and select the file to be imported.

  • Batch Number – Click the Lookup button to select the batch created for lockbox processing.

  • Lockbox – Click the Lookup button to select the lockbox record containing the pre-defined formatting for the file to be imported.

Click Import to import the file into UX Online for viewing and error checking before you process the imported data into transactions. See Lockbox Data View for more information.

Lockbox Data View

Once you import the file, run the Lockbox Import Edit Report to confirm the imported transaction data received from the bank and check for errors. If changes are necessary, you can access each individual transaction directly through Lockbox Data View.

To view the data direction, in the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > Lockbox Management > Lockbox Data View. The List View of active lockbox import records opens in a new window where you can review the import records that have not been processed. You can open each transaction to view and/or make any changes, if required, and then click Save & Close.

Important

Once you run Lockbox Processing for the import batch, the transactions will be cleared from the Lockbox Data View and not available for reporting.

To confirm the lockbox import records in a report, from any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online reports. Open the UX Lockbox Import Edit Report and enter the batch number used for the lockbox import and click Run Report.

The report will generate results for each transaction item contained in the Lockbox Data View based on the batch you selected during Lockbox Import. If there are errors in any transaction, they will be displayed in the report so that you can make necessary corrections from the Lockbox Data View. For example, if the payment amount exceeds the invoice balance due, the report will display an error description. Export the report to a PDF and save for reference against the bank file report, if needed.

Lockbox Processing

Once you complete your review of the imported data and confirm that it is correct, run the Lockbox Processing utility to create payment transactions from the imported data. In the Navigation Tile Bar, select the Financial Manager work area > Payment Processes > Lockbox Management > Lockbox Processing.

Important

Once you run Lockbox Processing for the import batch, transactions where the create payment was successful will be cleared from the Lockbox Data View and no longer available for reporting. If Lockbox Processing is not successful on any of the imported transactions, they will remain in the view and available for output in the Lockbox Import Edit report.

In the Create Payments from Lockbox Import window, use the Lookup to select the same batch you used to import the data file and click OK. The system returns a confirmation displaying the number of invoices found for creating payments. Click OK to continue.

UX Online will create payments for each invoice payment in the import file, and if the file contained monetary contributions, UX Online will create a monetary contribution transaction with the invoice customer as the Donor, and payment.

Membership

Part 4: Membership

This part of the documentation describes the procedures you will use to manage your organization’s membership.

This information is divided into the following chapters:

  • Chapter 22: Membership Renewal Setup

  • Chapter 23: Membership Renewal Billing Transactions

  • Chapter 24: Membership Renewal Billing Processes

Chapter 22: Membership Renewal Setup

Renewal processes in your organization can apply to several things, including organization and chapter memberships and subscriptions.

Note

The same concepts for setting up membership renewal billing also apply to setting up subscription renewal billing. For more information on subscriptions, see Subscription Renewal Billing Setup.

In addition, several variables can change the way the renewal is billed, such as:

  • Does your organization have multiple dues rates?

  • Are the dues prorated?

  • Are dues volume-based (that is, are they based on a measurement such as the annual sales or revenue of a member company)?

  • Are dues factor-based (that is, are they based on a factor calculation of a volume measurement such as the annual sales or revenue of a member company)?

  • Can dues be invoiced and paid in installments?

  • Does your organization use progressive rates for dues (that is, moving from one rate to another)?

  • Do you need to limit the number of recipients for your organization’s benefits?

  • Does your organization allow renewal billing for unpaid members?

  • Does your organization have chapters for which you bill chapter dues?

Because of the complexity of managing all these variables in the renewal billing process, you can use UX Online to set up the components for each type of renewal billing you perform and save those components as a renewal benefit.

This part of the documentation describes how to create each component for your membership and chapter renewals, and then how to bring them together into the renewal benefits you need for your organization’s membership renewal processes.

This documentation also describes how to use renewal packages, which are combinations of renewal benefits and non-renewing products, such as one-time application fees, that you can use to simplify the new member billing process.

This information includes the following topics:

  • Membership renewal benefits overview

  • Creating default dues and chapter billing products

  • Current cycle and next cycle proration

  • Creating prorate schedules

  • Prorate schedule maintenance

  • Creating installment schedules

  • Installment schedule maintenance

  • Creating a membership or chapter renewal benefit

  • Creating membership benefit rates and prices

  • Creating complimentary membership rates and prices

  • Setting up progressive benefit rate structures

  • Setting up volume-based rates and prices

  • Setting up factor-based rates and prices

  • Benefit recipients

  • Additional benefit recipient charges

  • Creating a new product for additional benefit recipient charges

  • Linking an additional benefit recipients product to a renewal benefit rate

  • Creating a new member renewal package

  • Creating new member package detail records

Membership renewal benefits overview

A membership renewal benefit is the basis for creating membership dues transactions on a new member’s first invoice. When you create a new member dues invoice, UX Online uses the information from the membership benefit to create the invoice detail line item for the new member’s dues. At the same time, the system also creates a separate renewal billing record for each renewal benefit included in the invoice. A renewal billing record is a record associated with an individual account or contact record, and it contains the membership information needed for renewal billing processes, such as generating renewal invoices or processing terminations.

Note

If your organization uses chapters and manages renewal transactions for chapter membership, you must set up your chapters before you create any chapter membership renewal benefits. For more information about chapter setup, see Chapter Manager.

There are six basic components to renewal billing setup—default dues billing and chapter billing products, prorate schedules, installment schedules, renewal benefits, rates, and prices—that you will use to simplify the process of generating invoices for membership or chapter dues transactions. These components allow you to customize your renewal billing and offer the flexibility for multiple renewal configurations.

  • Default dues billing products – In order to create a renewal benefit, you first must create at least one default dues billing product. This default dues billing product contains the accounting information to support GL detail for the renewal benefit when it is used in membership dues transactions and payments. By extension, the same information applies to any renewal invoice you create using that benefit. If your organization uses different GL accounts for different dues, you must set up a separate dues billing product for each. For example, assume that your organization collects dues for a sister organization where the dues revenue is captured in a different GL account than the account used for your organization’s dues. In this case, you would set up one dues billing product for your organization, and a separate dues billing product for the sister organization. The same concept applies to chapter dues, where you must create at least one default chapter billing product.

  • Prorate schedules – Create prorate schedules if the renewal basis is a calendar year and your organization prorates the renewal benefit based on the date a member joins. For example, assume your organization’s membership period is from January 1 through December 31, and you prorate the dues for members who join throughout the year. You can include a prorate schedule to your membership renewal benefit to automatically calculate the prorated dues for new members. (Prorate schedules are not used for renewals that use an anniversary basis.) Prorate schedules are not specific to accounting data or modules. The same prorate schedule setups can be used to support memberships, subscriptions, and certifications.

  • Installment schedules – All renewal benefits require at least one installment schedule to support the benefit rate setup. This is typically a standard single annual installment. You can also create additional installment schedules if your organization offers a variety of payment options for your renewal billings. Installment schedules are not specific to accounting data or modules. The same installment schedule setups can be used to support membership, subscriptions, and certification.

Important

If your organization uses calendar-based dues, you must follow the guidelines provided in Membership Renewal Setup regarding revenue recognition deferral start and end dates with multiple installment rates. For important additional information, see Calendar-based dues prorate guidelines.

  • Renewal benefits – Renewal benefits are the parent records under which you create rates and prices that inherit the core characteristics of the parent benefit. These characteristics include the default dues billing or chapter billing product, renewal method (calendar or anniversary), prorate cycle (for calendar only), and default start date.

  • Rates – A rate defines the pricing of the renewal benefit billing and is used to calculate the dues amount. A rate determines whether the price is calculated based on quantity, volume or factor, the installment schedule used, price levels, and the number of benefit recipients specific to the rate. While you must create at least one rate within each renewal benefit, a single benefit can have multiple rates. For instance, multiple rates are required if your organization’s dues structure is based on different installment billing options. Multiple rates can also be used if your dues structure for company membership is tiered to track a specific number of company contacts entitled to receive a particular member benefit. For more information, see Benefit recipients.

  • Prices – Pricing, or the actual dues amounts, is defined within the rate. Each membership or chapter dues rate must have at least one member price item and one non-member price item. If your organization bases its dues on specific volume ranges, you will need a member price and a non-member price for each volume range. If your organization bases its dues on a factor of specific volume ranges, you will need a member price and a non-member price for each volume range.

Creating default dues and chapter billing products

The first step in creating your renewal benefits is to create a default dues billing product in the Product Sales Manager. If your organization uses chapters, you will need to create a default chapter billing product. These products define the general ledger accounts that are used for transactions when members join the organization or renew their membership.

When you create your default dues billing product and chapter billing product, you will enter the basic information about the products, including the accounting system company, whether your organization recognizes dues revenue on a cash basis, and the general ledger accounts you use for dues revenue and deferred dues revenue, if applicable. If your organization reimburses chapters for chapter dues, you will need to select the appropriate chapter dues payable account, as well, where the revenue for reimbursable chapter dues does not belong to your organization; it belongs to the chapter.

If all of your organization’s membership dues billing will use the same accounting system company and GL accounts (for dues revenue and deferred revenue), then you will only need to create one dues billing product. If, however, your association has dues that are allocated to different accounting system companies or to different GL accounts, you will need to set up a separate product for each scenario.

Note

The process for setting up a membership dues billing product and a chapter dues billing product is the same.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to open the List View of active products. This View opens in a new window.

On the List View toolbar, click Add Product to create a new product. In General section, select the fields appropriate to the product you are creating:

  • Product ID – Enter a code or abbreviated name for this product. For example, the ID for membership dues billing could be MEMBER-PRODUCT.

  • Name – Enter a short descriptive name of the product, for example, ‘Membership Product’.

  • Unit Group – Click the Lookup button, select Each, and click OK.

  • Default Unit – Click the Lookup button, select Each, and click OK.

  • Currency – If you are working in a single currency environment, by default, your preferred currency appears in this field. Otherwise, select Currency.

  • Product Type – Select Dues Billing from the list for membership dues; select Chapter Billing for chapter dues.

  • Subject – This field is optional.

In the Accounting area, complete the following fields:

  • Company – The system will automatically populate this field with the company record flagged as the default company in your set up. If you need to make a change, click the Lookup button to select the appropriate accounting system company for this product. This controls where accounting data will post during the posting process and controls the display of GL accounts available in the GL account lookup fields.

  • Reimbursable – Select Not Reimbursable for membership dues billing products; select Chapter Payment if you are creating a default chapter dues billing product where chapter dues are reimbursed to the chapter.

  • Primary GL Account – Click the Lookup button to select the appropriate primary GL account for this product. The type of account you select depends on what kind of membership renewal product you are setting up, and whether you defer dues revenue:

    • Dues billing product, dues revenue not deferred – select the dues revenue account.

    • Dues billing product, dues revenue deferred – select the deferral account.

    • Chapter billing product, dues not reimbursed, revenue not deferred – select the chapter dues revenue account.

    • Chapter billing product, dues not reimbursed, revenue deferred – select the chapter dues deferral account.

    • Chapter billing product, dues reimbursed – select the chapter dues payable account.

  • AR GL Account – Click the Lookup button to select the appropriate AR account for this product and click OK.

  • Cash Basis – If your organization recognizes all dues revenue on a cash basis, click to select Yes. If dues revenue is on an accrual basis, select No. Dues revenue is most commonly managed on a cash basis.

Important

For organizations that manage membership dues on an accrual basis, the Cash basis = No setting does not result in accurate AR when dues are billed in more than one installment. AR is created for the entire dues amount for all installments – not incrementally for each installment period.

  • Control Accrual Basis via AR Utility – This field is enabled when Cash Basis = Yes and mainly is used by organizations that manage membership dues on accrual basis but do not want to see any AR until the membership year begins. When Cash Basis = Yes and Control Accrual via AR Utility = Yes, the “AR Utility” batch process converts invoice detail from cash basis to accrual basis at the start of the membership year. If this situation does not apply to your organization, leave the default setting = No.

  • Secondary GL Account – This field is enabled and required when the Primary GL account selected is a deferral account. If your organization defers dues revenue, click the Lookup button to select the appropriate revenue account for this product and click OK. If the Primary GL account selected is not a deferral account, the field is disabled and no entry is required.

  • AP GL Account – This field is enabled and required if you selected Reimbursable = Chapter Payment. If this is a reimbursable chapter billing product, click the Lookup button to select the appropriate chapters payable account. If you selected Reimbursable = Not Reimbursable, the field is disabled and no entry is required.

In the Costs area, select the fields appropriate to the dues billing product you are creating:

  • Default Price List – Click the Lookup button to open the Look Up Records dialog box. Select Member and click OK.

  • Decimals Supported – Enter the number of decimal places needed for this product’s currency format. For example, the default value of 2 is for a 0.00 currency format.

  • Single Currency – Do not select. It is not applicable to Dues Billing product types.

  • List Price – Leave blank. Pricing is not driven by a default dues billing or chapter billing product types.

  • Apply Freight – This field does not apply and is disabled for dues billing and chapter billing product types.

  • Is it a Bill Recipient – This field does not apply and is disabled for dues billing and chapter billing product types.

In the Tax Product Info area, select the fields appropriate to the dues billing product you are creating:

  • Taxable – Check the Taxable field if tax should be calculated on dues.

  • Tax Rate – This field does not apply and is disabled for dues billing and chapter billing product types.

The fields in the Description section do not apply to dues billing or chapter billing products; however, you may enter descriptive text in the Description field.

The fields in the Web section are not available as they do not apply to dues billing or chapter billing product types.

Click Save & Close to save this record and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Notes

When you save a product record, additional related entities in the Navigation Pane are available, such as Substitutes, Price List Items, and Prices. These features are not applicable to dues billing or chapter billing product types.

Because pricing for membership dues billing and chapter billing products is driven by the benefit/rate set up, you don not need to set up prices for default dues billing product types.

Current cycle and next cycle proration

Proration only applies if your organization manages renewals on a calendar basis. The calendar is any 12-month period that applies to all renewals, regardless of the join date. It is not restricted to a 12-month period that begins in January and ends in December; it can be any defined 12-month period such as July to June or October to September. For example, if your dues year begins in October and all memberships expire on September 30, renewal is calendar-based.

Proration does not apply if your organization manages membership and/or chapter dues on an anniversary basis. For example, if membership expires 12 months from the month a member joins the organization, regardless of what month that may be, renewal is based on the membership anniversary, and dues are not prorated.

When your organization’s dues are calendar-based, you can create prorate schedules for to offer new members reduced dues pricing based on the month a member joins your organization. The proration can occur in either the current cycle (the first year of membership) or the next cycle (the first renewal year).

For example, if your membership year begins in January, you can set up a prorate schedule so members who join in January pay the full dues amount, but members who join in any other month have their dues reduced by a given amount, depending on which month they join. This is a current cycle prorate.

You can also prorate the new member’s dues for the next dues year, rather than the current dues year. This way, a new member will pay a full year’s dues the first year, regardless of what month they join, but their second year dues (first renewal year) will be prorated. This is a next cycle prorate.

You can also choose not to prorate the new member’s calendar dues. This requires a prorate schedule where the number of prorate months = 0 for each prorate detail month. This will result in calendar-based dues for a new member who pays a full year’s dues regardless of what month the member joins.

Important

The set up for a calendar-based benefit requires a prorate schedule, even if your organization does not prorate calendar dues. If your organization’s dues are calendar based and you do not prorate dues, use a prorate schedule where all prorate detail records contain prorate number of months = 0.

Dues proration will have an impact on how the deferred dues revenue is recognized. Therefore, when working with calendar-based dues, you must use these following guidelines when you select the rates to use for a new member’s first dues invoice and for their subsequent renewal invoices.

Calendar-based dues prorate guidelines

Important

If you do not follow these guidelines, deferred dues revenue may not be recognized correctly.

If you do not prorate calendar-based dues:

  • New Member Dues Invoice – You must select a single annual installment rate for the initial new member dues invoice so that the system creates the deferral start and end dates for revenue recognition. If you select a multiple installment rate, you will need to manually enter the deferral start and end dates in the renewal transaction invoice detail for each installment.

  • First and Subsequent Renewal Invoices – After the initial new member dues invoice, you can select any rate as the Rate Next Rate to generate the first and subsequent dues renewal invoices, allowing the member to renew with an installment schedule that accommodates multiple installments, if needed.

If you prorate calendar-based dues in the current cycle:

  • New Member Dues Invoice – You must select a single annual installment rate for the initial new member dues invoice so that the system creates the deferral start and end dates for revenue recognition. If you select a multiple installment rate, you will need to manually enter the deferral start and end dates in the renewal transaction invoice detail for each installment.

  • First and Subsequent Renewal Invoices – After the initial new member dues invoice, you can select any rate as the Rate Next Rate to generate the first and subsequent dues renewal invoices, allowing the member to renew with an installment schedule that accommodates multiple installments, if needed.

If you prorate calendar-based dues in the next cycle:

  • New Member Dues Invoice – You must select a single annual installment rate for the initial new member dues invoice so that the system creates the deferral start and end dates for revenue recognition. If you select a multiple installment rate, you will need to manually enter the deferral start and end dates in the renewal transaction invoice detail for each installment.

  • First and Subsequent Renewal Invoices – After the initial new member dues invoice, you can select any rate as the Rate Next to generate the first and subsequent dues renewal invoices, allowing the member to renew with an installment schedule that accommodates multiple installments, if needed.

Creating prorate schedules

Calendar-based dues (no prorate, current prorate, next cycle prorate) will have an impact on how deferred dues revenue is recognized. Therefore, when you select the rates to use for a new member’s first dues invoice and for their subsequent renewal invoices, you must follow the guidelines in Current cycle and next cycle proration. See Calendar-based dues prorate guidelines for more information.

Note

If your organization has calendar year renewals that begin in different months, repeat this procedure to create prorate schedules for each of those calendar year renewals. For instance, if the national dues year begins in January, you would create a prorate schedule that begins in January. If the chapter dues year begins in July, you would create a prorate schedule that begins in July for those chapter dues.

Important

The set up for a calendar-based benefit requires a prorate schedule, even if your organization does not prorate calendar dues. If your organization’s dues are calendar based and you do not prorate dues, use a prorate schedule where all prorate detail records contain prorate number of months = 0.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Billing Settings > Step One: Prorate Table to open the Active Prorate List View. This View opens in a new window. Click New on the List View toolbar to create a new prorate schedule.

In the General section, enter a descriptive name for the prorate schedule, such as “January Start Monthly Prorate.” Click Save and proceed to create Prorate Detail records.

Creating Prorate Detail

Note

You must create prorate detail for each month of the calendar year.

In the Navigation Pane of the prorate record, click Detail to open the List View of Prorate Detail records. You must create a prorate detail record for each month of the calendar year.

Click Add New Prorate Detail on the List View toolbar to open the Prorate Detail Form.

In the General section, complete the general information about the proration detail:

  • Prorate – Displays the name you entered for this prorate schedule. Do not change this field.

  • Join Date Month – Select the month for this prorate detail record.

  • Number of Months – Enter the number of months that dues should be prorated (reduced) based on the Join Date Month selected above. For example, if your membership year begins in January, and you want members who join in March to have their dues reduced by two months, you would enter 2 in this field when the Join Date Month = March.

Click Save & Close on the Prorate Detail Record toolbar to return to the prorate record.

Important Note

If you enter 12 as the number of months, the cycle start date for the prorate schedule will automatically be set to the first day of the next dues cycle, regardless of whether the renewal benefit this prorate schedule is assigned to is set up to use Current Cycle or Next Cycle proration. This means that any prorate detail entry with a value of 12 will forgive (prorate) 12 months of the benefit amount during the current cycle, even if the benefit is set up to use Next Cycle proration.

If you enter 12, the renewal billing record for new members who pay the new member invoice in full will have a cycle state = Upcoming and will not acquire membership benefits until their cycle start date, which is the beginning of the next dues cycle. You can override the default cycle state for new members by changing the Config value for the application parameter, PAMembership.NewMemberCycleState. For more information, see Configuring New Member Cycle State Override.

Repeat these steps to create prorate detail records for each calendar month of the dues year.

Click Save & Close to save the prorate schedule and return to the Prorate list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Prorate schedule maintenance

You can make changes to a prorate schedule at any time. Changing the name of a prorate schedule or changing any of the prorate detail records will change the proration of new renewal billing records only, but does not affect existing renewal billing records or invoices.

If you are going to create a new prorate schedule and want to leave the old schedule in place for historical reference, on the list of active prorate schedules, click the schedule to select it, and then click Deactivate from the Record toolbar.

Important

If you deactivate a prorate schedule that is assigned to an existing benefit, you must update the benefit with a new prorate schedule.

Creating installment schedules

UX Online relies on installment schedules in the benefit rate setup to create and calculate invoice detail line items for pricing in new member and renewal invoices that are based on that benefit rate. You must create at least one installment schedule. This is typically an annual installment schedule based on a 12-month cycle. With this installment schedule, the dues invoice would have one detail line item for the full renewal amount.

Note

All renewal billing setup (membership, subscriptions, and professional development) share the same installment schedule records. You do not need to create a separate set of schedules for each module.

You can create alternate installment schedules based on your organization’s needs and assign each to a different rate within a single renewal benefit. For example, your organization might offer its Gold members the ability to pay their $400.00 annual dues on an annual, semi-annual, and quarterly basis. Under the Gold renewal benefit, you would create three rates, each with a different installment schedule and a price of $400.00. The dues invoice using the rate with an annual installment schedule would have one detail line item for $400.00. The dues invoice using the rate with a semi-annual installment schedule would have two detail line items, each for $200.00. The dues invoice using the rate with a quarterly installment schedule would have four detail line items, each for $100.00.

Important

If your organization uses calendar-based dues, you must follow the guidelines provided in Membership Renewal Setup regarding revenue recognition deferral start and end dates with multiple installment rates. For important additional information, see Calendar-based dues prorate guidelines.

For more examples illustrating how you can set up installment schedules, see Installment schedule examples.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Billing Settings > Step Two: Installment Schedule to open the Active Installment Schedule List View. This View opens in a new window. Click New on the List View toolbar to open an installment schedule record.

In the General section of the Installment Schedule record, complete the general information about the Schedule:

  • Name – Enter a descriptive name for the Installment, such as ‘1 Year Annual Installment’, in the Name field.

  • Bill Frequency – Select a billing frequency for this installment schedule. You can select Annual, Semi-Annual, Quarterly, Semi-Monthly, or Monthly.

  • Number of Months – Enter the number of months that represents the duration of the dues cycle. If the dues cycle is one year, enter 12. If the dues cycle is two years, enter 24, etc.

  • Number of Installments – Displays the number of installments calculated based on the billing frequency and number of months. Do not change this field unless you are setting up a multi-year installment schedule and want to adjust the number of installments.

Click Save. The following options on the Navigation Pane become active:

  • Activities – Displays a list of pending activities created for this record (for example, e-mail, appointments, or phone calls).

  • Closed Activities – Displays a list of completed activities for this record.

  • Rate – Displays a list of renewal billing rates that use this installment schedule. Use this listing for viewing only. Do not edit existing rate records from this location. Do not use the Add New Rate button on the toolbar.

Click Save & Close to save the installment schedule and return to the Installment Schedule List View. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Installment schedule examples

The following examples show how you can set up different single and multi-year installment schedules. The multi-year examples illustrate when you need to override the default number of installments.

One-year installment schedule settings

1-year renewal cycle, billed once:

  • Number of Months = 12

  • Bill Frequency = Annual

  • Number of Installments = 1 (keep default)

1-year renewal cycle, billed semi-annually:

  • Number of Months = 12

  • Bill Frequency = Semi-Annual

  • Number of Installments = 2 (keep default)

1-year renewal cycle, billed quarterly:

  • Number of Months = 12

  • Bill Frequency = Quarterly

  • Number of Installments = 4 (keep default)

1-year renewal cycle, billed bi-monthly:

  • Number of Months = 12

  • Bill Frequency = Bi-Monthly

  • Number of Installments = 6 (keep default)

1-year renewal cycle, billed monthly

  • Number of Months = 12

  • Bill Frequency = Monthly

  • Number of Installments = 12 (keep default)

Multi-year installment schedule settings

2-year renewal cycle, billed annually for 1/2 of the amount:

  • Number of Months = 24

  • Bill Frequency = Annual

  • Number of Installments = 2 (keep default)

2-year renewal cycle, billed one time for the full amount:

  • Number of Months = 24

  • Bill Frequency = Annual

  • Number of Installments = 1 (override the default)

3-year renewal cycle, billed annually for 1/3 of the amount:

  • Number of Months = 36

  • Bill Frequency = Annual

  • Number of Installments = 3 (keep default)

3-year renewal cycle, billed one time for the full amount:

  • Number of Months = 36

  • Bill Frequency = Annual

  • Number of Installments = 1 (override the default)

Lifetime membership, billed one time for the full amount:

  • Number of Months = 999

  • Bill Frequency = Annual

  • Number of Installments = 1 (override the default)

Installment schedule maintenance

You can make changes to an installment schedule at any time. Changing the name of an installment schedule or any other information on it will change the installment information of new renewal billing records and invoices only. Existing renewal billing records and invoices are not affected.

If you are going to create a new installment schedule and want to leave the old schedule in place for historical reference, on the list of active installment schedules, click the schedule to select it, and then click Deactivate from the Record toolbar.

Important

If you deactivate an installment schedule that is assigned to an existing rate, you must update the rate with a new installment schedule.

Creating a membership or chapter renewal benefit

You will use renewal benefits when you generate invoices for transactions that require renewal processing, such as membership and chapter dues renewals and subscription renewals. Renewal benefits also are used for first-time invoicing—new memberships, new chapter memberships, and new subscriptions. If your organization uses both corporate and individual memberships, you will have a minimum of two benefits, with the various rates for companies and individuals defined under each benefit.

Important

Before you begin creating benefits and rates, carefully review and document your organizational requirements for renewal billing and work with your Protech representative to explore the best setup based on your needs.

You will need at least one benefit. You will need to create additional renewal benefits if any of the rates within a module do not share all of the characteristics of the benefit. As your organization grows and changes, you can change your renewal benefits and add new benefits at any time.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Billing Settings > Step Three: Renewal Benefit to open the Active Benefits List View. This View opens in a new window. Click New on the List View toolbar to create a new benefit.

In the General section of the Benefit record, complete the general information about the renewal benefit:

  • Module – Click the Lookup button to select the Membership module for the new benefit. The Membership module is used for both membership and chapter benefit setup.

  • Default Product – Click the Lookup button to select the default product for this renewal benefit. For a membership dues renewal benefit, select the dues billing product you created to support membership and click OK. For a chapter dues renewal benefit, select the chapter billing product you created to support chapters and click OK. All transactions associated with this renewal benefit will use the accounting setup defined in this default product. See Creating default dues and chapter billing products for more information.

Note

The default product will be used as the default for all rates defined within the benefit. However, you can assign a different dues billing or chapter billing product to specific rates if needed.

  • Name – Enter a descriptive name for the benefit, such as ‘National Membership.’

  • Is Primary Benefit – Click to select Yes if this benefit controls membership status. If this benefit does not control membership status, click to select No. (Chapters typically are not considered the primary membership benefit.)

  • Renewal Method – Select either Calendar or Anniversary.

  • Chapter Benefit – If you are creating this benefit to manage chapter renewal billing, click to select Yes. Click to select No if this benefit is for any renewal other than chapter renewal billing, including membership dues billing, subscription renewal billing, etc.

  • Sequence – Used to control the order in which invoice detail is created in a UX Online grouped invoice that is created during the generate renewal billing process. See About renewal benefit sequencing for important information on how UX Online relies on the Sequence number during renewal processing.

  • Group Invoices – Click to select Yes if this benefit should be grouped during renewal processing with other renewal benefits that share the same invoice customer, invoice Bill To, and renewal billing expiration date into a single invoice. For example, if a subscription benefit for an account or contact has the same as this membership renewal benefit, and you want the two benefits grouped into one invoice, you would select Yes. If you do not want benefits with the same expiration date grouped on a renewal invoice, click to select No.

Note

If you choose to group benefits on renewal invoices, the sequence number you enter in the Sequence field for each benefit determines the sequence of the invoice detail on a renewal invoice. All benefits must have a sequence number. See About renewal benefit sequencing for important information on how UX Online relies on the Sequence number during renewal processing.

  • Prorate – If you selected the Calendar renewal method, and you want to prorate the new member’s dues for this benefit, click the Lookup button to select the prorate schedule and click OK. A prorate schedule is required for all benefits where the renewal method = Calendar. If you selected the Anniversary renewal method, do not select a prorate schedule. See Creating prorate schedules for more information.

Important

The set up for a calendar-based benefit requires a prorate schedule, even if your organization does not prorate calendar dues. If your organization’s dues are calendar based and you do not prorate dues, use a prorate schedule where all prorate detail records contain prorate number of months = 0.

  • Prorate Cycle – This setting works in conjunction with the Calendar renewal method only. See Current cycle and next cycle proration for more information. Select the desired cycle:

    • Current Cycle – Select this option if a new member’s dues are prorated during the first calendar year of their membership. For example, assuming a January to December dues year, if a member joins in June, the member would pay the half of the dues amount.

    • Next Cycle – Select this option if a new member’s dues are prorated during their second dues cycle (that is, their second calendar year of membership – their first renewal). For example, assuming a January to December dues year, if a member joins in June, the member would pay the full dues amount for the first year of membership – even though actual membership was only for six months. When the member renews at the end of December, they would pay half of the dues amount for the second full year of membership.

  • Default Start Date – Select the starting date of the renewal cycle. In all instances, the default start date will be the 1st of a month. The options available here depend on what renewal method you selected.

Important

It is important to consider the implications of selecting the Default Start Date in scenarios where the default start date is in the future (for example, Begin Next Month). When the new member renewal billing cycle start date is equal to or less than the system date, the renewal billing record cycle state will equal Current. When the new member renewal billing cycle start date is greater than the system date (future default start date), the renewal billing record cycle state will equal Upcoming. If the benefit default start date is in the future, a new member’s primary membership and member pricing does not become effective until the renewal billing cycle state updates to Current. This update occurs when the renewal billing cycle start date equals the system date. In the scenario of a future start date, Membership is not conferred automatically based on a fully paid new member invoice. You can override the default cycle state to Current for all new members through the application parameter PAMembership.NewMemberCycleState. For more information, see Configuring new member cycle state override.

    • If the renewal method is Calendar, select the month your renewal cycle begins. For example, if your membership year begins in January and ends in December, select January. (Note: You must select a calendar month if the renewal method is Calendar.)

    • If the renewal method is Anniversary, select one of the following options. (Note: You cannot select a calendar month if the renewal method is Anniversary.)

      • Beginning of Current Month – the default start date is the first of the current month, regardless of when the member joins during the month. This setting works in conjunction with the Anniversary Renewal Method only and does not require an entry in the Cut Off Day field.

Important

If you select this option as the default start of a benefit’s renewal cycle, new members who pay the new member invoice in full will acquire membership benefits immediately.

      • Beginning of Next Month – the default start date is the first of the next month, regardless of when the new member joins during the month. This setting works in conjunction with the Anniversary Renewal Method only and does not require an entry in the Cut Off Day field.

Important

If you select this option as the default start of a benefit’s renewal cycle, new members who pay the new member invoice in full will not acquire membership benefits until their cycle start date (the first of the next month) unless the application parameter Config value for PAMembership.NewMemberCycleState = Current. For more information, see Configuring new member cycle state override.

      • Beginning Based on Cutoff Day – used in conjunction with the Cut Off Day (COD) field described below, the default start date is calculated based upon the day of the month that the new member joins. If the new member joins on or before the Cut Off Day (COD), then the default start date is the first of the current month; if the new member joins after the Cut Off Day (COD), then the default start date is the first of the next month.

It is important to note that if you select this option as the default start of a benefit’s renewal cycle, new members who join on or before the Cut Off Day (COD) and pay the new member invoice in full will acquire membership benefits immediately; new members who join after the Cut Off Day (COD) and pay the new member invoice in full will not acquire membership benefits until their cycle start date (the first of the next month) unless the application parameter Config value for PAMembership.NewMemberCycleState = Current. For more information, see Configuring new member cycle state override.

      • Beginning of Current Quarter – the default start date is the first day of the current quarter, regardless of when the member joins during the quarter. This setting works in conjunction with the Anniversary Renewal Method only and does not require an entry in the Cut Off Day field.

It is important to note that if you select this option as the default start of a benefit’s renewal cycle, new members who pay the new member invoice in full will acquire membership benefits immediately.

      • Beginning of Next Quarter – the default start date is the first day of the next quarter, regardless of when the new member joins during the quarter. This setting works in conjunction with the Anniversary Renewal Method only and does not require an entry in the Cut Off Day field.

It is important to note that if you select this option as the default start of a benefit’s renewal cycle, new members who pay the new member invoice in full will not acquire membership benefits until their cycle start date (the first of the next quarter) unless the application parameter Config value for PAMembership.NewMemberCycleState = Current. For more information, see Configuring new member cycle state override.

    • Cut Off Day (COD) – Enter the appropriate cut-off day for the renewal method and default start date you selected. It is important to consider the implications of selecting the COD. In scenarios where the default start date is in the future, a new member’s membership and member pricing does not become effective until the actual cycle start date. Membership is not conferred automatically based on a fully paid new member invoice when the cycle start date is greater than the system date unless the application parameter Config value for PAMembership.NewMemberCycleState = Current. For more information, see Configuring new member cycle state override.

      • If the renewal method is Anniversary and the default start date is Beginning Based on Cutoff Day, enter the cut-off day to use to calculate the cycle start date. If you are using the Anniversary renewal method and you select anything other than Beginning Based on Cutoff Day as the default start date, do not change the default entry of 1; it is a required minimum value.

      • If the renewal method is Calendar, enter the cut-off day to use with the Default Start Date month to calculate prorated dues.

  • If a new member joins on or before the cut-off day, then the renewal cycle start date will be the 1st day of the month you selected in the Default Start Date. To calculate the prorate, the system uses the prorate number of months for the month in which the new member joins.

  • If a new member joins after the cut-off day, then the renewal cycle start date will be the 1st day of the month following the month you selected in the Default Start Date. To calculate the prorate, the system uses the prorate number of months for the month after the month in which the new member joins.

    • Allow Renewal on Unpaid – If you want to allow the system to create a new renewal billing invoice when the contact or account has a previous renewal invoice that is still unpaid, click to select Yes. Click to select No if you want to require that the previous renewal billing invoice must be paid before a new one can be created.

In the Pricing area of the General section of the Benefit record, complete the information about the renewal benefit:

    • Start Date – Select the default pricing starting date for all of the rates and prices created in this renewal benefit. This date will also be used by the Price Progression utility. (For more information, see Creating new rate prices using Price Progression.) You should always select the first day of the month for your price start date in order to be consistent with other renewal logic and to enhance functionality for creating new prices for new dues years.

    • End Date – Select the default pricing ending date for all of the rates and prices created in this renewal benefit. This date will also be used by the Price Progression utility. You should always select the last day of the month for your price end date in order to be consistent with other renewal logic and to enhance functionality for creating new prices for new dues years.

Click Save to save this benefit. After saving this record, other options in the record Navigation Pane are activated: Activities, Closed Activities, Rate, and Galley Setup.

    • Click Activities to view activities related to this benefit that require immediate action or follow up (for example, e-mail, appointments, or phone calls).

    • Click Closed Activities to view all activities related to this benefit (e-mails, appointments, etc.) that have been completed.

    • Click Rate to add rates to this benefit. For more information, see Creating membership benefit rates and prices.

    • Galley Setup is not used with membership or chapter renewal benefits; it is used for subscription renewal benefits.

The Web section is used with Protech’s MX Online and will be set as needed during that implementation. Do not change these settings.

Click Save & Close to save the benefit and return to the Benefit list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Creating membership benefit rates and prices

Rates are the mechanism by which you group and define common pricing structures for the renewal invoice. It is also the mechanism for managing benefit recipients. Keeping in mind the billing component relationships, each renewal benefit must have at least one rate. However, a renewal benefit can have multiple rates and each rate can have multiple prices as long as each child rate shares the same core characteristics of the parent renewal benefit.

For example, as shown below, a national dues benefit can have rates for dues based on volume ranges, rates for dues based on a quantity, rates for dues based on a factor. You could also have separate rates that allow for varying benefit recipients, other installment schedules, and rates that support a progressive rate structure.

Important

For each rate included in a renewal benefit, you must have a member price and a non-member price, even if both members and non-members are charged the same price. In addition, if your organization uses pricing options in addition to your standard member and non-member prices, such as a government or academic price, you must create prices for those. For example, if you want to offer academic pricing, you must create an academic member price and an academic non-member price.

If one or more of your rates do not share all of the parent renewal benefit characteristics, you will need to create additional renewal benefits and build the rates under that renewal benefit.

To set up multiple rates under a single benefit, repeat the following steps for each rate.

To set up complimentary rates, see Creating complimentary rates and prices for more information.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Billing Settings > Step Three: Renewal Benefit to open the Active Benefits List View. This View opens in a new window. In the Benefits list, open the benefit you where you want to add rates.

Benefit rates

In the Navigation Pane of the selected Benefit record, click Rate to open the Rate Associated View. Click Add New Rate on the List View toolbar to create a new rate.

In the General section of the Rate record, complete the general information about the rate:

  • Name – Enter a descriptive name for the rate. If a rate is going to have a specific installment option, we recommend that you include that in your name rate (for example, “National Membership – Quarterly Installments”).

  • Benefit – This field displays the name of the parent benefit for this rate and is not available for edit.

  • Rate Type – Select the calculation method for this rate:

    • Select Quantity if the pricing is not calculated based on volume data in the account or contact record; instead, the price is based on a flat quantity (typically 1).

    • Select Volume if the pricing is calculated based on volume data in the account or contact record. For example, your organization can base its dues amount on a company’s sales revenue and you capture that sales revenue figure for purposes of calculating dues. You could use Volume rates so that the system will calculate the dues automatically for you based on the value ranges in your price setup for this rate. For more information, see Setting up volume-based rates and prices.

    • Select Factor if the pricing is calculated based on a factor calculation using volume data in the account or contact record. For example, your organization can base its dues amount based on a factor calculation of a company’s sales revenue. You could use Factor rates so that the system will calculate the dues automatically for you based on the value ranges in your price setup for this rate. For more information, see Setting up factor-based rates and prices.

  • Chapter – If the parent benefit is not a chapter benefit (that is, the Chapter Benefit option is set to No), leave this field blank. If the parent benefit is a chapter benefit (that is, the Chapter Benefit option is set to Yes), do one of the following:

    • If you have different rates for each chapter, and the rate is for a specific chapter, click the Lookup button to select the chapter. (For more information about chapters, see Chapters.) For example, if you have a chapter for each state and each chapter has a different rate, then you would create a separate rate for each chapter and define the chapter within the rate. When you create an invoice using a rate where the chapter is defined, the system will automatically assign the new member to that chapter.

    • If you have multiple chapters that share the same price, leave this field blank. When you create a new member invoice, you can use a renewal package that will prompt you for the appropriate chapter. For more information, see Creating a new member renewal package.

Note

To take full advantage of the features of renewal packages, we recommend that you do not create a chapter benefit that has some rates with a chapter defined and other rates without achapter defined.

  • Installment – Click the Lookup button to select the installment schedule for this rate. (For more information, see Creating installment schedules.)

Important

If your organization uses calendar-based dues, you must follow the guidelines provided in Membership Renewal Setup. For important additional information, see Calendar-based dues prorate guidelines.

  • Number Benefit Recipients – You must enter at least 1; however, the number is based on your organizational needs. For example, if you are creating a rate that is specific to account records, enter the number of records that can benefit from the account’s renewal billing record. See Benefit recipients and Additional benefit recipient charges for more information.

Note

Benefit Recipients do not confer membership status or member pricing. It is used primarily for extending member benefits, such as a publication, to a defined number of benefit recipients.

  • Default Price Level – Click the Lookup button to select the default price level for this rate. Price levels in CRM allow an organization to have multiple price lists. Typically, organizations have two price levels to differentiate pricing for members from pricing for non-members (although some have more intricate pricing structures). Every account and contact record in CRM has a field that indicates the price list that applies to that record. Each product also has a field relating that product to a particular price level. If an account or contact record does not have a default price level, the system uses the default price level indicated for the product itself. For membership or chapter dues, the default price level will typically be Non-Member.

  • Default Price – Enter the default price for this rate. The system will use this entry to create a price for each price level that you have set up. You can modify these prices at any time, or you can create additional price records for this rate, if needed.

  • Volume Field Name Contact – If you selected Volume or Factor as the Rate Type, enter the attribute name for the contact field used to maintain volume data for purposes of calculating dues. The typical contact attribute is pa_volume. If the Rate Type selected is Quantity, leave this field blank.

Important

You must identify the account and/or contact attribute used to determine volume-based dues pricing. Eligible contact attributes include those with a field type equal to whole number, decimal number, floating point number and money. Selecting an ineligible field type will generate an error causing system logic to fail.

  • Volume Field Name Account – If you selected Volume or Factor as the Rate Type, enter the attribute name for the account field used to maintain volume data for purposes of calculating dues. The typical account attribute is pa_volume. If the Rate Type selected is Quantity, leave this field blank.

Important

You must identify the account and/or contact attribute used to determine volume-based dues pricing. Eligible account attributes include those with a field type equal to whole number, decimal number, floating point number and money. Selecting an ineligible field type will generate an error causing system logic to fail.

  • Product – Displays the default product entered on the benefit record. If this particular rate’s revenue needs to be tracked in a GL account other than the one that was defined for the benefit, select the appropriate product.

  • Recipient Product – If this rate supports a specific number of “free” benefit recipients (as defined in the Number of Benefit Recipients field), and your organization charges for any additional recipients above this number, you will need to assign a product for this. This product is used to calculate additional charges on the renewal invoice if a company member’s benefit recipient count exceeds the number defined for this rate. For more information, see Creating a new product for benefit recipient charges. See also Benefit recipients and Additional benefit recipient charges.

  • Rate Next – This field is not enabled until you save the rate, when the system automatically populates this field with this rate. If this rate is part of a progressive rate structure, click the Lookup button to select the rate to be used after this rate. (See Setting up progressive benefit rate structures for more information.) If this rate is not part of a progressive rate structure, do not change this entry – the next renewal cycle will create dues based on this rate.

  • Airmail – Do not change this option; it is used for subscription benefits.

The Web section is used with Protech’s MX Online, and will be set as needed during that implementation. Do not change these settings.

Click Save to activate additional setup in the Navigation Pane of the Rate record, where you will set up Prices and Price Level X-ref for this rate, as described below.

Benefit Rate Prices

In the Navigation Pane of the rate, click Prices to display the price records created by the system for each price list in your system setup. All will use the default price in the rate, as well as the price start date and price end date that you defined for the benefit. You will need to review and revise these prices. See also Setting up Volume-based Rates and Prices and Setting up Factor-based Rates and Prices.

Important

If the Rate Type is Volume, you will need to edit the price records that were created by the system to set the price and the Value Minimum and Value Maximum. In addition, you will need to create additional prices for each volume range. Make sure that the Value Minimum and Value Maximum values do not overlap.

If the Rate Type is Factor, you will need to edit the price records that were created by the system to set the factor (price is ignored) and the Value Minimum and Value Maximum. In addition, you will need to create additional prices for each volume range. Make sure that the Value Minimum and Value Maximum values do not overlap.

If you create price records based on date ranges, make sure that the Start Date and End Date values do not overlap. When calculating pricing, the system will select the price record where the cycle start date falls within the date range of the rate prices record.

Open the price record you want to view/edit. Fields are described below for creating a new price record. To create a new price, click Add New Prices on the toolbar.

In the General section of the Prices record, complete the general information about the price:

  • Price Level – Click the Lookup button to select either Member or Non-member as the price level for this price record. (Remember that you must create both member and non-member versions of every price your organization uses.)

  • Name – The system will populate this field based on the Price Level you selected.

  • Calculation Method –For dues and chapter billing, do not change the default value of Flat Rate. This method applies to all rate types.

  • Price/Percent of List Price – If you selected Quantity or Volume for the rate type, enter the total amount due. (If the rate includes installment billing, the system automatically calculates the installment amounts.) Price is ignored for rate type Factor.

  • Value Minimum – If you selected Volume or Factor for the rate type, enter the minimum value for the range for this price. If you selected Quantity for the rate type, you do not need change the default values.

  • Value Maximum – If you selected Volume or Factor for the rate type, enter the maximum value for the range for this price. If you selected Quantity for the rate type, you do not need change the default values.

  • Start Date – The default start date is the Pricing Start Date entered for this benefit, which typically reflects the start date of the benefit dues year. If the price is valid for a different date range, select the starting date. For example, if this rate is valid for the 2008 dues year, enter January 1, 2008 as your start date.

  • End Date – The default end date is the Pricing End Date entered for this benefit, which typically reflects the end date of the benefit dues year. If the price is valid for a different date range, select the end date. For instance, if this rate is valid for the 2008 dues year, enter December 31, 2008 as your end date.

Important

When calculating pricing, the system will select the price record where the cycle start date falls within the start and end date range of the rate prices record. If no price record is found, the system will calculate dues as $0.00.

  • Factor – If you selected Factor for the rate type, enter the factor (as a decimal representing the percentage) for calculating dues. Otherwise, leave this field blank.

  • Product – This field is disabled. It is not used for setting rate prices.

  • Rate – Displays the name of the rate.

  • Adv Ad Type – This field is disabled. It is not used for setting rate prices.

Click Save & Close to save the price and return to the Prices list.

Once you have completed setting up prices records, click the rate record on the Top Navigation Toolbar to return to the rate record.

If this rate is for a primary membership, in the rate Navigation Pane, click Price Level X-ref to continue the setup described below. If not, Save & Close the Rate to return to the Rates list of the benefit. Click the benefit record on the Main Tile Bar to return to the benefit record.

Click Save & Close to save this renewal benefit and return to the Benefit list. Because the Benefit list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Benefit Rate Price Level X-ref

If this rate setup is for a primary benefit (that is, a benefit that controls membership status), you must have a Rate Price Level X-ref record that controls the price level of a record when membership is active and when membership is terminated. If you are working in a multi-currency environment, you must have a Rate Price Level X-ref for each currency.

In the Navigation Pane of the rate, click Price Level X-ref to display a list of records. To view an existing record, double-click to open it. To create a new record, click Add New Rate Price Level X-ref on the list toolbar.

In the General section of the Price Level X-ref record, complete the following fields:

    • Currency – Click the Lookup button to select the currency for this record. (Remember that you must create a record for each active currency your organization uses.)

    • Owner – Defaults to the owner of the record.

    • Price Level Active – Click the Lookup button to select the Price Level for active (not terminated) members for this rate.

    • Price Level Terminated – Click the Lookup button to select the Price Level for terminated members for this rate.

Click Save & Close to save this record. Once you have completed setting up Price Level X-ref records, click the rate record on the Main Tile Bar to return to the rate record.

Click Save & Close to save this rate record and return to the benefit record. Click Save & Close to save this renewal benefit and return to the Benefit list. Because the Benefit list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Creating complimentary membership rates and prices

If your organization offers one or more complimentary memberships—for example, for its honorary members—you can set up a complimentary rate to manage these members as you would all other members. You no longer need to manipulate the record by setting an expiration date sometime beyond your natural life span, or work around your renewal process to avoid these records, or enter special payment types to accommodate members who are not required to pay dues.

Complimentary rates have prices of zero. When creating a new member invoice or running the renewal process, it is this zero price that tells the system to automatically update the member’s renewal information, including the expiration date, as if the dues invoice had been paid in full. In other words, as soon as the renewal invoice is generated using a complimentary rate, the renewal billing record updates the paid through date field with the end date of the renewal cycle, the expiration date field with the end date of the renewal cycle, and the date renewed field with the date that the renewal process was run.

To create a complimentary rate, see Creating membership benefit rates and prices. In the Default Price field, enter $0.00. When you save the rate, the system creates a member price item and a non-member price item—each has a price of $0.00.

Setting up progressive benefit rate structures

You can set up a progressive benefit rate structure that automatically advances a member from their current rate to the selected Rate Next during the renewal process; you will not need to modify the renewal record prior to generating renewal invoices. Setup can accommodate rate progressions within a single benefit or rate progressions across different benefits that share the same Module, Renewal Method, and Is Chapter Benefit setup.

For example, assume your organization offers multiple levels for its student members who eventually progress to full membership. You will first create a rate (with prices) for each of the different levels. Then you will set up the progressive structure by selecting the next level in the Rate Next field for each rate. In this example, the student’s first invoice will be based on the first year rate and during renewal, the system will automatically progress the student to the 2nd year student rate. During the next renewal cycle, the system will automatically progress the student to the 3rd year student rate, and so on.

Current Rate

Selected Rate Next

1st Year Student

2nd Year Student

2nd Year Student

3rd Year Student

3rd Year Student

Active

Active

Active

Important Note

The Rate Next Lookup filters the rates available for selection based on the benefit setup for the existing rate. If the existing rate’s benefit setup ‘Is Primary’ = Yes, then the rates available for selection are limited to rates where the benefit setup ‘Is Primary’ = Yes, Additionally, for benefits where the renewal method equals Anniversary, then the Rate Next Lookup shows only rates from other benefits that are also Anniversary and have the same module and Chapter Benefit setting. For benefits where the renewal method equals Calendar, then the Rate Next Lookup shows only rates from other benefits that are also Calendar and have the same module, Chapter Benefit setting, and Default Start Date.

You first must set up all benefits, rates, and prices included in the progression before you define the rate progression. The following procedure assumes that you have already set up required benefits, rates, and prices.

In the General section of the Rate record, click the Lookup button on the Rate Next field to select the rate that will apply to the next renewal cycle. Click Save & Close to save this rate and return to the Rate list.

Repeat steps for each rate in the progression.

When you have finished setting up the progressive rate structure, click Save & Close to save this rate record and return to the benefit record.

Click Save & Close to save this renewal benefit and return to the Benefit list. Because the Benefit list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Setting up volume-based rates and prices

If your organization bases its dues rates on a series of volume ranges – for example, sales volume or number of employees – you can set up volume-based benefit rates, with separate prices for each volume range. The Rate Type must equal Volume for this pricing structure. Then, when the system creates renewal billing records, the volume data in the account or contact record will be used to find the correct volume-based prices record and corresponding price to determine the dues amount.

In the Navigation Pane of the benefit, click Rate to display the rates set up for this benefit. Click Add New Rate to add a new, volume-based rate to this benefit. (For detailed instructions on setting up a new rate, see Creating membership benefit rates and prices.)

Select Volume as the rate type for this rate.

  • If this rate will be used to calculate dues for accounts, in the Volume Field Account Name, enter the attribute name for the account field used to maintain volume data for purposes of calculating volume based dues. The base account attribute for this field is pa_volume.

  • If this rate will be used to calculate dues for contacts, in the Volume Field Contact Name, enter the attribute name for the contact field used to maintain volume data for purposes of calculating volume based dues. The base contract attribute for this field is pa_volume.

Important

You must identify the account and/or contact attribute used to determine volume-based dues pricing. Eligible contact and/or account attributes include those with a field type equal to whole number, decimal number, floating point number. Selecting an ineligible field type will generate an error causing system logic to fail.

Click Save to save this rate setup. Click Prices in the Navigation Pane.

Create a member and non-member prices record for each volume range, setting the price and the minimum and maximum values required for your organization’s dues structure. The first volume range must have a minimum value = 1 and the minimum and maximum values for each prices record cannot overlap. (For detailed instructions on creating prices, see Creating membership benefit rates and prices.)

Important

When calculating pricing, the system will select the price record where the cycle start date falls within the start and end date range of the rate prices record. If no price record is found, the system will calculate dues as $0.00.

When you finish creating price items for each volume range, click the rate record on the Main Tile Bar to return to the rate record. Click Save & Close to save this rate record and return to the benefit record.

Click Save & Close to save this renewal benefit and return to the Benefit list. Because the Benefit list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Setting up factor-based rates and prices

If your organization bases its dues rates on a calculated value or “factor” based on one or more volume ranges – for example, sales volume or number of employees – you can set up factor-based benefit rates, with separate price records with a factor used to calculate dues. The Rate Type must equal Factor for this pricing structure. Then, when the system creates renewal billing records, the volume data in the account or contact record will be used to find the correct factor-based prices record and corresponding factor to calculate the dues amount (factor times the account or contact volume = dues amount).

In the Navigation Pane of the benefit, click Rate to display the rates set up for this benefit. Click Add New Rate to add a new, factor-based rate to this benefit. (For detailed instructions on setting up a new rate, see Creating membership benefit rates and prices.)

Select Factor as the rate type for this rate.

  • If this rate will be used to calculate dues for accounts, in the Volume Field Account Name, enter the attribute name for the account field used to maintain volume data for purposes of calculating factor-based dues. The base account attribute for this field is pa_volume.

  • If this rate will be used to calculate dues for contacts, in the Volume Field Contact Name, enter the attribute name for the contact field used to maintain volume data for purposes of calculating factor-based dues. The base contract attribute for this field is pa_volume.

Important

You must identify the account and/or contact attribute used to determine factor-based dues pricing. Eligible contact and/or account attributes include those with a field type equal to whole number, decimal number, or floating point number. Selecting an ineligible field type will generate an error causing system logic to fail.

Click Save to save this rate setup. Click Prices in the Navigation Pane.

Create a member and non-member prices record for each volume range, entering the Factor to be used for calculating dues and the minimum and maximum values required for your organization’s dues structure. The first volume range must have a minimum value = 1 and the minimum and maximum values for each prices record cannot overlap. The Calculation Method and Price/Percent of List Price fields are ignored when Rate Type = Factor. (For detailed instructions on creating prices, see Creating membership benefit rates and prices.)

Important

When calculating pricing, the system will select the price record where the cycle start date falls within the start and end date range of the rate prices record. If no price record is found, the system will calculate dues as $0.00.

When you finish creating price items for each volume range, click the rate record on the Main Tile Bar to return to the rate record. Click Save & Close to save this rate record and return to the benefit record.

Click Save & Close to save this renewal benefit and return to the Benefit list. Because the Benefit list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Benefit recipients

When you set up a benefit rate in UX Online, you can define the number of benefit recipients available for a particular rate. A benefit recipient record is used to determine which contact or account records are associated with a renewal billing record to receive a particular benefit.

For example, assume that a corporate membership rate includes five copies of a monthly publication as a member benefit. An account may have hundreds of contact records, but you can designate the five specific contacts who should receive the monthly publication as benefit recipients for the account.

When a renewal billing record is created for the first time (for example, a new membership or a new subscription), the system creates the appropriate number of placeholder benefit recipient records in the renewal billing record based on number defined in the rate setup.

When the system creates placeholder benefit recipient records for an account renewal billing record, the system uses the account primary contact record name as the default name for each benefit recipient placeholder record. When creating placeholder benefit recipient records for a contact renewal billing record, the system uses the contact name as the default name for each benefit recipient placeholder record. After these placeholder records are created, you can assign a contact to each of them. (You will use this feature primarily during the galley process for account records where you have the option to generate a galley for all contacts or to generate the galley only for contacts designated as benefit recipients.)

During renewal processing, existing benefit recipient records are copied from the current renewal billing record to the newly created upcoming renewal billing record. Renewal processing does not alter existing benefit recipient records.

Renewal processing also evaluates the number of benefit recipient records in the current renewal billing record against the number allowed in the renewing Rate Next.

  • If your organization’s business rules require that you charge for the number of benefit recipients that exceed the number allowed in the renewing rate, the system will automatically create an invoice detail line for additional benefit recipient charges in the renewal invoice. See Additional benefit recipient charges for more information.

  • If your system is configured to create additional placeholder benefit recipient records during renewal and the number of benefit recipient records in the current renewal billing record is less than the number allowed in the renewing rate, the system will create the appropriate number of new placeholder benefit recipient records in the upcoming renewal billing record. See Configuring create benefit recipient records during renewal for additional information.

Caution

There is no logic that prevents you from manually creating additional benefit recipient records in the renewal billing record or deleting existing benefit recipient records. All updates to the benefit recipient records must be managed manually as part of standard record maintenance.

Configuring create benefit recipient records during renewal

To configure your system to create additional placeholder benefit recipient records during the renewal process based on the number allowed in the renewing rate, change the default Config value for the application parameter, PARenewal.AdditionalBenefitRecipientsCreate = true.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This View opens in a new window. Locate and open the parameter PARenewal.AdditionalBenefitRecipientsCreate.

Set the Config Value field to the method that your organization uses:

  • True – creates additional placeholder benefit recipient records during renewal based on number allowed in renewing Rate Next.

  • False – does not create additional placeholder benefit recipient records during renewal. This is the default value for this parameter.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Benefit recipient type

You can classify benefit recipient records using the optional Benefit Recipient Type field that is present on the benefit recipient record. By default, the value for this field is null, as there are no existing values for this option set field unless values were added as part of your implementation. Otherwise, you will need to customize this field to add values appropriate for your organization’s requirements. There is no renewal billing logic associated with this field, but it can be useful for reporting and Advanced Find queries.

Note

If data was migrated to this field during implementation without the corresponding option set values in the benefit recipient type field, the system will not be able to generate renewal billing invoices. If data is present in this field, there must be a corresponding option set value.

Managing benefit recipient records from the renewal billing record

You can manage benefit recipient records from within the renewal billing record or from within the related invoice transaction detail.

When adding benefit recipient records from the renewal billing record, the Ship To Contact lookup displays only contact records that are linked to the account in the Ship To Account field, if one exists. You can override this filter and search all contacts in the database by clearing the data in the Ship To Account field.

If any benefit recipient records need to be removed, you will need to delete them manually. The UX Membership Benefits Recipient Report can be generated to identify which contacts are defined as a benefit recipient for each member record.

Any adds, changes, or deletes to benefit recipient records accessed from the renewal billing record will be reflected when accessing benefit recipients from the invoice transaction.

Managing benefit recipient records from the invoice transaction

When adding benefit recipients records from within the invoice transaction detail that is related to the renewal billing record, the contact lookup displays only contact records that are linked to the account selected in the Account field. You can override this and search all contacts in the database by clearing the data in the Account field.

If any benefit recipients need to be removed, you will need to delete them manually. The UX Membership Benefits Recipient Report can be generated to identify which contacts are defined as a benefit recipient for each member record.

Any adds, changes, or deletes to benefit recipient records accessed from the invoice transaction detail will be reflected when accessing benefit recipients from the related renewal billing record.

Additional benefit recipient charges

If your organization’s membership rates include a prescribed number of benefit recipients, and your business rules require that you charge a member for benefit recipients that exceed that prescribed number, UX Online will automatically create invoice detail charges for the additional benefit recipients during the renewal process. If you find that you need to add additional benefit recipients to the dues renewal invoice, you can use the Re-Calculate Benefit Recipients on the benefit entry record within the dues invoice detail line item to re-calculate invoice detail for the additional charges you need for recipients added after the renewal process was run.

Important Note

Pricing for additional benefit recipient charges is based on cycle start date of the related renewal billing record. The system will select the price record where the cycle start date falls within the price record date range of the additional benefit recipient product.

Before the system can calculate additional benefit recipient charges, you must first set up an “additional benefit recipient” product with the appropriate pricing and General Ledger account information for the additional charges. Then, you must add the new product to the Renewal Billing Rate setups where these additional benefit recipient charges apply.

For more information, see the following topics:

Creating a new product for additional benefit recipient charges

The first step in setting up your system to calculate additional benefit recipient charges during the renewal process is to create an “additional benefit recipient” product with the appropriate pricing and General Ledger account information for the additional charges.

After you have created the additional benefit recipients product, you will need to link it to the appropriate renewal benefit rate. For more information, see Linking an additional benefit recipients product to a renewal benefit rate.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to open the List View of active products. This View opens in a new window.

In the Product list, click New on the List View toolbar to create a new product. In General section, select the fields appropriate to the product you are creating:

  • ID – Enter a code or abbreviated name for this product. For example, the ID for membership dues billing could be ADDLBENRECIPIENT.

  • Currency – If working in a single currency environment, by default, your preferred currency appears in this field. Otherwise, select the Currency for the additional billing recipient product.

  • Name – Enter a short descriptive name of the product, for example, ‘Additional Benefit Recipients’.

  • Unit Group – Click the Lookup button, select Each and click OK.

  • Default Unit – Click the Lookup button, select Each and click OK.

  • Product Type – Select Sales Non-inventory from the list.

  • Subject – This field is optional.

In the Accounting area, complete the following fields:

  • Company – The system will automatically populate this field with the company record flagged as the default company in your set up. If you need to make a change, click the Lookup button to select the appropriate accounting system company for this product. This controls where accounting data will post during the posting process and controls the display of GL accounts available in the GL account lookup fields.

  • Reimbursable – Select Not Reimbursable.

  • Primary GL Account – Click the Lookup button to select the appropriate primary GL account to which accounting data will post when you post UX Online transactions that include this additional benefit recipient product. This is generally a deferral or revenue account. The type of account you select depends on whether you defer revenue for these additional charges. Many customers use the same accounting setup used for the default dues product, as follows:

    • Dues billing product, dues revenue not deferred – select the dues revenue account.

    • Dues billing product, dues revenue deferred – select the deferral account.

Note

If you enter a deferral account, CRM will create the deferral start and end dates on the invoice detail for additional benefit recipient charges, and will capture the additional benefit recipient charges in the revenue recognition process.

  • AR GL Account – Click the Lookup button to select the appropriate AR account for this product and click OK.

  • Cash Basis – Mark this checkbox if transactions for this additional benefit recipient product should be managed on a Cash basis.

  • Control Accrual Basis via AR Utility – This field is enabled when Cash Basis = Yes and mainly is used by organizations who manage membership dues on accrual basis but do not want to see any AR until the membership year begins. When Cash Basis = Yes and Control Accrual via AR Utility = Yes, the “AR Utility” batch process converts invoice detail from cash basis to accrual basis at the start of the membership year. If this situation does not apply to your organization, leave the default setting = No.

  • Secondary GL Account – This field is enabled and required when the Primary GL account selected is a deferral account. If your organization defers this revenue, click the Lookup button to select the appropriate revenue account for this product and click OK. If the Primary GL account selected is not a deferral account, the field is disabled and no entry is required.

  • AP GL Account – This field is disabled and no entry is required.

In the Costs area, select the fields appropriate to the dues billing product you are creating:

  • Default Price List – Click the Lookup button to select Non-Member and click OK.

  • Decimals Supported – Enter the number of decimal places needed for this product’s currency format. For example, the default value of 2 is for a 0.00 currency format.

  • Is it a Bill Recipient – This field is disabled, as it does not apply to this product type.

  • List Price – Enter the base price for additional benefit recipient charges. The amount entered here will be used as the price amount in the system-created prices records when you save this product setup.

  • Apply Freight – This field does not apply. Do not check this box.

  • Single Currency – Do not select. It is not applicable to additional benefit recipient products.

In the Tax Product Info area, select the fields appropriate to the dues billing product you are creating:

  • Taxable – Check the Taxable field if tax should be calculated on additional benefit recipient charges.

  • Tax Rate – This field is disabled and does not apply to this product type.

The fields in the Description section do not apply to this setup; however, you may enter descriptive text in the Description field. The fields in the Web section do not apply to this product type.

Click Save. The following options on the Navigation Pane become active:

  • Substitutes – This does not apply to additional benefit recipient records.

  • Price List Items – Displays the price lists for this record. The system will create one price list item for each price list set up in the CRM Price List table. You do not need to make any changes.

  • Prices – Use this option to set up the pricing structure for this additional benefit recipient charges. For more information, see Creating product prices.

Important Note

When the application parameter PARenewal.AdditionalBenefitRecipientbyCycleDate = true, pricing for additional benefit recipient charges is based on cycle start date of the related renewal billing record. The system will select the price record where the cycle start date falls within the price record date range of the additional benefit recipient product.

Click Save & Close to complete your product setup and return to the Product list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Linking an additional benefit recipients product to a renewal benefit rate

After you create an additional benefit recipient product (see Creating a new product for additional benefit recipient charges), you must link it to the associated renewal benefit rate.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Billing Settings > Step Three: Renewal Benefit to open the Active Benefit List View. This View opens in a new window. Open the renewal benefit with the rate where you want to link the new additional benefit recipient product.

Click Rate in the Navigation Pane to view a list of available rates for this renewal benefit. Open the rate where you want to link the additional benefit recipients product.

In the Add’l Benefit Recipients Product field, click the Lookup button to select the additional benefit recipients product you created.

Click Save & Close to save the rate and return to the renewal benefit record.

Click Save & Close to save the benefit record and return to the benefit list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Creating a new member renewal package

A new member renewal package allows you to combine multiple renewal benefits with selected benefit rates and products from your product catalog into a single package that is used to create a new member invoice transaction. Each benefit and product in the package is known as a package detail item. The purpose of a new member renewal package is to save time when you create a new member invoice. By using a renewal package, the system generates the invoice detail line item for each item in the package for you, rather than you having to add each item as a separate transaction in the invoice.

For example, assume that a new member of your organization will be invoiced for membership dues, chapter dues, and a one-time application fee. You can create a new member renewal package that includes a package detail item for the membership renewal benefit, another package detail item for the chapter renewal benefit, as well as a package detail item for the application fee product. When the system processes the initial transaction for a new member, it will create a single new member invoice that includes a detail line for membership dues, a detail line for the chapter dues, and a detail line for the application fee. During subsequent renewal processing, if the benefits are flagged to group invoices, UX Online will create a single renewal invoice that will include a detail line for membership dues and a detail line for the chapter dues. There will be no detail line for the non-renewing product (the application fee). See About renewal benefit sequencing for important information on how UX Online relies on the Sequence number for grouping invoices during renewal processing.

Before you create a renewal package, you must complete the set up for the renewal benefits you need, along with any products you want to include in the package. For information about setting up renewal benefits, see Creating a membership or chapter renewal benefit.

In addition, you must follow these guidelines when creating a renewal package:

  • There can only be one package detail for a Primary Membership benefit in a package.

  • There can only be one package detail Chapter Membership benefit in a package when the Chapter is not built into the benefit rate (requires prompt for Chapter).

  • There can be multiple Chapter Members Benefits in a package when the Chapter is built into the benefit rate (no prompt required).

  • There can be multiple Other Benefits in a package (such as a subscription benefit).

  • There can be multiple Products in a package.

  • Because you are combining multiple benefits into a single invoice, each benefit in a package must have the identical setup for the following key benefit components:

    • Renewal Method (anniversary or calendar)

    • Prorate Cycle (used on for calendar renewal methods)

    • Prorate Schedule

    • Default Start Date

    • Cut Off Day

    • Installment Schedule

Important

The system will not recognize a benefit package detail benefit that does not have the same setup as all other package detail benefit entries.

When applying payment to a renewal billing invoice created from a package, the payment must be equal to or greater than the sum of all 1st installments before the renewal billing record is updated. For example, you create a package that contains a single installment primary membership benefit with rate of $120.00 and a single installment chapter membership benefit with a rate of $25.00. When you use this package to create a new member invoice and the member pays only the primary membership amount of $120.00, the system will not update the renewal billing status until payment for the chapter is applied.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Billing Settings > Step Four: Renewal Package to open the Active Member Package List View. This View opens in a new window.

Click New on the List View toolbar to create a new renewal package. In the General section of the Renewal Package record, complete the general information to define the package.

  • Name – Enter a descriptive name for the package.

  • Account or Contact – If this member package will be used for account records select Account. If it will be used for contacts records, select Contact.

  • Prompt for Chapter – Click to select Yes if this package will contain a chapter benefit where the chapter is not defined in the chapter benefit rate. This would be the case where you have one rate for all chapters and your rate setup does not contain a pre-defined chapter. By selecting Yes, you will have the opportunity to assign the specific chapter at the time you create an invoice using this package. Click to select No if this package contains a chapter benefit where the chapter is defined in the chapter benefit rate. Click to select No if this package will not contain a chapter benefit.

  • Prompt for Volume – Click to select Yes if you want the system to enable a prompt asking for the volume information when you are creating the renewal invoice. Click to select No if you do not require a prompt.

Click Save to save this record. In the Navigation Pane, click Package Details to add the renewal benefits and other products you want to include with this package. For more information, see Creating renewal package detail.

Creating renewal package detail records

After defining the basic information about a renewal package, the next step is to create the package detail records. These records identify the renewal benefits, benefit rates, and sales non-inventory products you want to include in the package. You will need a separate package detail for each benefit in the renewal package. You can use any of the following four types of package details; the options you will set for each of them depends on the type.

  • Primary Membership Detail – Used to calculate the billing amounts for the primary organization membership dues. You will select the membership benefit and rate. All renewal billing information for this package detail will be based on the setup for the benefit and rate selected, including the product and installment schedule. You cannot have more than one primary membership in a renewal package.

  • Chapter Membership Detail – Used to calculate the billing amounts for the chapter dues. You will select the chapter benefit and rate. If the Prompt for Chapter option is set to No, select the rate where the Chapter is defined in the rate setup. If the Prompt for Chapter option is set to Yes, select a rate where the Chapter is not defined in the rate setup. All renewal billing information for this package detail will be based on the setup for the benefit and rate selected, including product and installment schedule.

Note

You cannot have more than one Chapter Membership Detail in a renewal package where the Chapter is not defined in the rate setup (requires prompt). You can have multiple Chapter Membership Detail records in a renewal package when the Chapter is defined in the benefit rate (no prompt required).

  • Other Benefit – Used to calculate billing amounts for other renewal benefits such as subscriptions, special interest groups (SIGs), etc. You will select the benefit and rate. All other renewal billing information for this package detail will be based on the benefit and rate selected, including the product and the installment schedule. You can have multiple Other Benefits in a renewal package.

  • Product – Used to generate first-time billing for a sales non-inventory product (such as an application fee) that is part of a renewal package, but is not subject to renewal. You can have multiple Products in a renewal package.

Create the basic renewal package information (see Creating a new member renewal package). Select Package Details from the Navigation Pane of the Benefit Package record. From the Member Package Detail list, click Add New Member Package Detail on the List View toolbar.

In the General section of the Member Package Detail record, complete the following information to define the detail.

  • Detail Type – Select the type for this detail: Primary Membership, Chapter Membership, Other Benefit, or Product.

  • Sequence – Used to control the order in which invoice detail is created in a UX Online new member invoice created from a benefit package. Each package detail record must have a unique sequence number.

  • Benefit – If the detail type is Primary Membership, Chapter Membership, or Other Benefit, click the Lookup button to select the renewal benefit for this package detail. If the detail type is Product, this field is disabled and no entry is required.

  • Rate – If the detail type is Primary Membership, Chapter Membership, or Other Benefit, click the Lookup button to select the rate to use for this package detail. If the detail type is Product, this field is disabled and no entry is required.

  • Product – If the detail type is Product, click the Lookup button to select the one-time sales non-inventory product to use for this package detail. If the detail type is Primary Membership, Chapter Membership, or Other Benefit, this field is disabled and no entry is required.

Click Save & Close to save this package detail and return to the Member Package Detail list.

Repeat steps for each package detail item to be included in the renewal package.

When you have finished creating package details for this member package, click the Member Package record in the Top Navigation Toolbar to return to the Member Package record.

Save & Close to save the member package and return to the Member Package list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Chapter 23: Membership Renewal Billing Transactions

This chapter describes how to create a new member invoice (transaction) record and payment. When you create a new member invoice, UX Online automatically creates a related renewal billing record that will be used to generate the membership renewal invoice for the next dues year.

In addition, this chapter describes how to manage payments for membership invoices, how to terminate and reinstate current memberships, rejoin terminated memberships, and how to cancel a membership invoice.

This chapter is divided into the following sections:

  • New member invoice process overview

  • Creating a new member invoice using a renewal benefit

  • Creating a new member invoice using a renewal package

  • Renewal billing records overview

  • Configuring new member cycle state override

  • Renewal billing record components

  • Sample renewal billing record lifecycle scenarios

  • About Renewal Billing Cycle State

  • About Cycle Year

  • Cycle State Update Utility

  • Setting the primary renewal billing record

  • Managing payments, transfers, refunds and credits

  • Applying payments to a membership renewal invoice

  • Deleting a cash or check membership payment

  • Canceling a renewal invoice line item

  • Canceling a renewal invoice

  • Terminating a single membership

  • Reinstating a terminated membership

  • Recalculating a membership renewal invoice

  • Rejoin Membership

  • Renewal billing pricing overrides

  • Upgrade/Downgrade membership

New member invoice process overview

When you create an invoice for a new member’s membership dues and for chapter dues – that is, a membership dues transaction – you will select one of the renewal benefits or renewal packages set up in the Membership Manager.

Important

You must complete your renewal benefit setup before you can create a new member dues invoice. See Membership Renewal Setup for more information.

When you create an invoice for a new member where the invoice detail line items were created using renewal benefits (such as membership dues and subscriptions), UX Online also creates renewal billing records for each of those detail line items to manage renewal information and the subsequent renewal processes. See Renewal billing records overview for more information.

You can also create new membership invoices using renewal packages. A member renewal package allows you to combine multiple renewal benefits with selected benefit rates, and products from your product catalog into a single package that is used to create a new member invoice transaction. For more information, see Creating a new member renewal package.

Creating a new member invoice using a renewal benefit

This procedure describes how to create a new member invoice for billing initial membership dues, chapter dues, or both, by selecting a renewal benefit.

You can also create new membership invoices using a renewal package. For more information, see Creating a new member invoice using a renewal package.

You can create a new invoice from within an existing account or contact record or directly from Invoices in any of the UX work areas on the Navigation Tile Bar. By creating an invoice from an existing record, the system automatically fills many data entry fields in the invoice header by using data from the record. These fields include the Customer name, Bill To and Ship To names and addresses, Price List, and Currency.

Note

The following procedure shows how to begin the membership invoice process from the contact’s record, but you can also begin from an account record or the Invoices list.

From any of the UX work areas on the Navigation Tile Bar, click Contacts. Open the contact record where you want to create an invoice.

On the Record toolbar of the contact’s record, click New Invoice to open a new invoice transaction. For more information about creating invoices, see Invoices.

Click Select Batch to select the appropriate open batch based on your organization’s business rules.

Note

After the first time you select a batch, the same batch will be used for each transaction you enter until you select a different batch, or that batch is closed.

Click Save to save the invoice with the selected batch or proceed directly and click New Transactions on the invoice Record toolbar. Either option will save the batch with the invoice, populate the Invoice ID, transaction date, and invoice address information.

From the New Transactions drop-down list, select Membership Dues from the menu.

On the New Renewal Billing transaction record, enter the following information at the top of the General section:

  • Benefit – Click the Lookup button to select the membership or chapter benefit.

  • Volume – If the rate you select is Rate Type = Volume or Factor, the system automatically displays the value from the specified pa_volume field in the account or contact record. You can enter a different volume if necessary. If you change the volume in a new renewal transaction, the system will update pa_volume field in the customer record and the related renewal billing record with this new value when the new transaction is saved for the first time. If the rate you selected is not a volume-based rate, this field is ignored and no entry is required.

Note

Updates to the record volume field only occur during the creation of new renewal transaction where the rate type = volume or factor. Volume field updates in the benefit entry record of an existing transaction do not update the record volume field. Renewal processing will use the value in the member’s record field without regard to the value in the renewal billing record.

  • Rate – Click the Lookup button to select the membership dues or chapter rate. When you select the rate, the system automatically fills in several of the remaining fields on the benefit entry form.

Important

If your organization uses calendar-based dues, you must follow the guidelines provided in Membership Renewal Setup regarding revenue recognition deferral start and end dates with multiple installments. For important additional information, see Calendar-based dues prorate guidelines.

  • Quantity – Displays a quantity of one by default. If you change the quantity and the selected Rate type = quantity, the system will calculate the price based on price per unit times the quantity entered. The system will also update the quantity field in the related renewal billing record for renewal processing.

  • Chapter – If the benefit you selected is a chapter benefit and the chapter was assigned as part of the benefit setup for the rate you selected, the chapter will appear in this field. If the benefit you selected is a chapter benefit and the chapter was not assigned as part of the benefit setup for the rate, click the Lookup button to select the correct chapter for this transaction. If the benefit you selected is not a chapter benefit, leave this field blank.

  • Current Join Date – Displays the system date. If you need to change the date, click the Calendar button to select a date. If necessary, the system will use this date to calculate the prorate, installment billing, and cycle start date, using the information in the benefit and rate selected.

  • Chapter Is Primary? – If the benefit you selected is a chapter benefit, select this checkbox if the chapter is the member’s primary chapter.

  • Paid Through Date – This field is blank until payment is applied on the invoice. When it will displays the paid through date based on the number of installments the member has paid. If your organization allows installment billing, this date updates each time an installment is paid against the dues invoice. If your organization does not support installment billing, then the paid through date will equal the member expiration date provided the invoice is paid in full.

  • Rate Next – Displays the Rate Next defined in the select Rate setup. If you need to make a change, use the Lookup button and manually select the Rate Next.Important NoteThe Rate Next Look Up filters the rates available for selection based on the benefit setup for the existing rate. If the existing rate’s benefit setup ‘Is Primary’ = Yes, then the Rate Next Look Up Records displays only rates for benefits where the benefit setup ‘Is Primary’ = Yes. Additionally, for benefits where the renewal method equals Anniversary, then the Rate Next Look Up shows only rates from other benefits that are also Anniversary, and have the same module and Chapter Benefit setting. For benefits where the renewal method equals Calendar, then the Rate Next Look Up shows only rates from other benefits that are also Calendar, and have the same module, Chapter Benefit setting, and Default Start Date.
  • Cycle Start Date – Calculated by the system based on the Current Join Date and the selected benefit setup.

  • Product – Displays the default dues product used in the selected rate setup. This field is disabled and cannot be modified.

  • Number of Benefit Recipients – Displays the number of benefit recipients defined in the selected rate setup. This field is disabled and cannot be modified.

In the Financials area of the General section:

  • Override Price – To override the default price per unit, mark this checkbox and then enter the price you wish to charge for this dues invoice in the Price Per Unit field.

  • Price Per Unit – Displays the full price for the dues rate selected and the price that will be used when the member renews (unless rates are changed in the setup area). This field is disabled unless Override Price = Yes.

  • Override Price Temporary – If Override Price = Yes, mark this checkbox if this is a one-time override and you want the system to use pricing in the Rate Next setup during the next dues renewal. Do not select this checkbox if this is a permanent override and you want the system to use the Price Per Unit.

  • Do Not Renew – Select this checkbox if you want to exclude this membership from the dues renewal process. Otherwise, do not mark this checkbox.

  • Promotion – If you want to apply a one-time discount to this new membership, use the Lookup to select the predefined promotion code.

  • Override Discount – If you want to override the default discount calculated for this invoice, mark this checkbox and change the amount in the Discount Amount field. Any discount you enter applies to the current invoice only and is not applied to dues renewal invoices.

  • Discount Amount – If you are using a predefined promotion code (discount), the amount of that discount is displayed in this field.

  • Override Prorate Amount – If you want to override the prorate amount, mark this checkbox and then change the amount in the Prorate Amount field to whatever is appropriate for this member.

  • Prorate Amount – If your organization prorates new member dues, the amount prorated (based on the rate selected and the join date) is calculated and displayed in this field.

  • Prorate Cycle – Defaults from the selected benefit setup. This field is disabled and cannot be modified.

  • Base Amount – Displays the dues price that was defined when the benefit and rate selected for this member was set up.

  • Prorate Number of Months – Displays the system calculated number of prorate months based on the benefit setup and the Cycle Start Date.

  • Installment Price – Displays the amount of each installment.

  • Number of Months – If your organization supports installment billing options, and the rate selected for the member is set up for installment billing, the number of months defined for the duration of that benefit are displayed here. For example 12 months, 24 months, 36 months, etc. This is the length of the dues billing cycle.

  • Installment Amount – Displays a calculated value of Installment Price times Quantity. For membership or chapter dues, this will display the Installment Price because dues are always a quantity of 1. For subscriptions, where you might have a quantity of 2, this would display 2 times the installment price.

  • Billing Frequency – Displays the billing frequency associated with the installment schedule for the selected rate setup.

  • Rounding Adj. – Displays a system calculated adjustment amount, if needed, when using multiple installments.

  • Number of Installments – Displays the number of installments associated with the installment schedule for the selected rate setup.

  • Total Charge – Displays the base amount less any discounts, prorated amounts.

Click Save on the New Renewal Billing transaction record toolbar.

Important

If you click Save or Save & Close, and a renewal billing record already exists for this benefit and rate, a message stating that the benefit already exists will appear. You can enter a different benefit and rate, or you can cancel this transaction and use the existing invoice for the current benefit and rate. You cannot have two invoices for the same benefit and rate combination.

If there is no duplicate benefit/rate, a new renewal billing record will be created for this benefit.

Click Save & Close to save this invoice detail line item and return to the invoice. Review the invoice and detail to ensure that the invoice is correct. Verify that it is correct and click Save & Close if you are finished and there are no payments to apply to this invoice. If you have a payment to apply, click Save to save the invoice and then create a payment transaction. (For more information, see Applying payments to a membership renewal invoice.)

Benefit Recipients

When you save a renewal transaction, the Benefit Recipients option in the Navigation Pane of the new Renewal Billing transaction record becomea available.

Click Benefit Recipients to view the individuals listed to receive benefits under this member’s dues. For individual members, there is typically only one benefit recipient record for that individual member. However, for an account membership (a company or organization), you can define how many individuals at that account can be included in the membership benefits, such as receiving your publication. (For more information on setting up benefit recipients, see Benefit recipients.)

  • All of the benefit recipient records that are created for an account membership display the ship-to address of the primary contact by default. You can change this address by double-clicking the record and then selecting the contact.

  • When you modify or create a benefit recipient record, you can enter an address that is different than the contact’s primary address; however, if you manually enter a different address in the benefit recipient record, be sure to mark Yes for the Use This Address option. (If you do not, the Galley Utility will use the contact’s primary address.)

  • If a contact does not want to receive your publication, click to select Yes for the Opt Out Publication option.

Note

You can also add additional benefit recipients. If your organization charges extra for additional benefit recipients, the account will be charged for the extra recipients during the next renewal cycle. If you manually add a benefit recipient and want to calculate charges before the next renewal cycle, you can open the renewal transaction and select Recalculate Benefit Recipients. If the number of benefit recipient records is greater than the number allowed in the rate times the renewal quantity, the system will create invoice detail for the additional charges.

Invoice Detail information

When you save a renewal transaction, the Invoice Detail option in the Navigation Pane of the new Renewal Billing transaction record becomes available.

Click Invoice Detail to view the invoice detail line items that are included in this renewal transaction. A record will be created for each installment.

For a new member transaction that is based on anniversary dues, the system will calculate the deferral start and end dates used for revenue recognition for each installment.

For a new member transaction that is based on calendar dues, the system will calculate the deferral start and end dates used for revenue recognition when the rate is for a single installment. See Calendar-based dues prorate guidelines for important information on deferral start and end date for multiple installment new member dues.

Creating a new member invoice using a renewal package

You can create a new member invoice using a renewal package. (For more information, see Creating a new member renewal package.) Because the rate is defined in the package, the system will automatically create the invoice detail line items based on the Package setup

Note

When applying payment to a renewal billing invoice created from a package, the payment must be equal to or greater than the sum of all 1st installments before the renewal billing record status is updated. For example, you create a package that contains a single installment primary membership benefit with rate of $120.00 and a single installment chapter membership benefit with a rate of $25.00. When you use this package to create a new member invoice and the member pays only the primary membership amount of $120.00, the system will not update the renewal billing status until payment for the chapter is applied.

Note

The following procedure shows how to begin the membership invoice process from the contact’s record, but you can also begin from an account record.

From any of the UX work areas on the Navigation Tile Bar, click Contacts. Open the contact record where you want to create an invoice. On the Record toolbar of the contact’s record, click New Invoice.

Click Select Batch to select the appropriate open batch based on your organization’s business rules.

Note

After the first time you select a batch, the same batch will be used for each transaction you enter until you select a different batch, or that batch is closed.

Click Save to save the invoice with the selected batch or proceed directly and click New Transactions on the invoice Record toolbar. Either will save the batch with the invoice, populate the Invoice ID, transaction date, and invoice address information.

From the New Transactions drop-down list, select Benefit Packages from the menu.

In the Benefit Packages dialog, click the Lookup button on the Package field to select the renewal package that is being purchased.

Click the Calendar button to select the original join date for the new member. This is a required field for a new member package.

  • If membership dues for this package benefit are volume-based and Prompt for Volume option on the package was set to Yes, enter the volume you want to use to calculate the dues amount in the Volume field. If membership dues for this package benefit are not volume-based and the Prompt for Volume option on the package was set to No, this field is disabled and not required.

  • If the package contains a chapter benefit where the chapter was not assigned in the rate and the Prompt for Chapter option on the package was set to Yes, click the Chapter Lookup button to select the correct chapter for this transaction. If the package contains a chapter benefit where the chapter was assigned in the rate and the Prompt for Chapter option on the package was set to No, this field will display the chapter define. You can change this if necessary.

Click OK. A message appears asking you to confirm that no duplicates where found. Click OK to proceed. The system will create an invoice detail line item for each benefit package detail in the package.

Important

If a renewal billing record already exists for a benefit and rate combination in the renewal package, the message “Benefit already exists” will appear. If you click OK, the system will create renewal billing records for each benefit and rate combination that is not a duplicate. If you click Cancel, no renewal billing records will be created.

Review the invoice and invoice detail line items to ensure that the invoice is correct. If it is correct, click Save & Close if you are finished and there are no payments to apply to this invoice. If you have a payment to apply, click Save to save the invoice and then create a payment transaction. (For more information, see Applying payments to a membership renewal invoice.)

Renewal billing records overview

The renewal billing record tracks the renewal information used in renewal billing transactions such as renewals and terminations. For membership and subscriptions, the renewal billing record also includes the Rate Next to be used for the next renewal billing cycle. You can use this to change the Rate Next before your run your Generate Renewal Billing Invoices process. See Setting up progressive benefit rate structures for more information.

During the process of creating an invoice using a membership dues or subscription transaction, you will select the renewal benefit and define the specific billing components that are needed to calculate the invoice (see New member invoice process overview). For each invoice that you create using a renewal benefit, the system first checks to see if renewal billing record exists for that benefit. If one does not already exist, the system creates a new renewal billing record.

When a new renewal billing record is created, the system calculates the Cycle State based on the join date and the benefit setup default start date. If the cycle state is in the future as would be the case when the benefit default start = Begin Next Month, the cycle state in the renewal billing record would equal Upcoming. If the benefit default start = Begin Current Month, the cycle state in the renewal billing record would equal Current. Cycle State is a critical component for new member processing as it controls the effective start date for membership and member pricing. You can override the default cycle state for all new members and set the cycle state = Current. For more information, see Configuring new member cycle state override. Similarly, you can override the default cycle state for all new subscribers and set the cycle state = Current. For more information, see Configuring new subscriber cycle state override.

Important

A fully paid new membership that results in a renewal billing record, where the cycle state = Upcoming, will not update the account or contact record member status or price level until the cycle start date in the renewal billing record is equal to or less than the system date.

You can override the default cycle state for all new members to set the cycle state = Current. For more information, see Configuring new member cycle state override.

A contact or account record can have multiple renewal billing records for the same benefit and rate. For each benefit and rate, it can have a combination of multiple renewal billing records for the same benefit and rate with a Cycle State = Past, but only one with a Cycle State = Current and only one with a Cycle State = Upcoming.

For a detailed description of the information included in a renewal billing record, see Renewal billing record components.

Any membership renewal billing record can potentially control whether or not an account or contact is considered a member or non-member, and whether they are eligible to receive member or non-member pricing. Because an account or contact can have multiple membership renewal billing records, one of those records has to be marked as the primary renewal billing record for purposes of determining membership. For more information, see Setting the primary renewal billing record.

Configuring new member cycle state override

You can override the system default Cycle State that is based on cycle start date and setting the Cycle State = Current for all new members by changing the Config value for the application parameter, PAMembership.NewMemberCycleState.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This View opens in a new window. Locate and open the parameter PAMembership.NewMemberCycleState.

Set the Config Value field to the method that your organization uses:

  • Current – Ignores the renewal billing cycle start date and sets the Cycle State = Current for all new members.

  • Leave the Config value blank to set the renewal billing Cycle State based on the cycle start date.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Renewal billing record components

The renewal billing record tracks the renewal information used in renewal billing transactions such as renewals and terminations. When you create a new renewal invoice, whether it is for a new membership or a new subscription, the system creates a renewal billing record, and all of the information in the renewal billing record is based on entries in the invoice or system logic associated with those entries. (For more information, see New member invoice process overview. Each time you run the Generate Renewal Billing Invoices process, the system creates renewal invoices and new renewal billing records that are related to existing, eligible renewal billing records.

There are five sections in each renewal billing record:

  • General

  • Next Renewal

  • Installments

  • Administration

  • Certification

To view the renewal billing records for an individual account or contact record, from any of the UX work areas on the Navigation Tile Bar, click Contacts or Accounts. Open the account or contact record whose renewal billing records you want to view. Click Renewal Billing in the Navigation Pane to view the list of available renewal billing records. Open the renewal billing record you wish to view.

General section

The General section displays information from the invoice Renewal Billing transaction record broken down into four areas: Benefit Information, Chapter, Renewal Cycle Information, and Financial.

Benefit Information

  • Benefit – Displays the benefit from the invoice renewal billing transaction record.

  • Benefit Status – Based on system logic, displays one of these statuses: New, Renew, Terminated or Reinstated. This field is typically updated by the system during the life cycle of the invoice or during renewal billing processing.

  • Rate – Displays the rate from the invoice renewal billing transaction record.

  • Primary Benefit – Displays whether or not this benefit is primary.

  • Rate Type – Displays the rate type from the invoice renewal billing transaction record.

  • Volume – Displays the information from the invoice renewal billing transaction record.

  • Quantity – Displays the information from the invoice renewal billing transaction record.

  • Number of Benefit Recipients – Displays the information from the invoice renewal billing transaction record.

  • Membership Length – Displays the information from the invoice renewal billing transaction record.

  • Do Not Renew – Displays the information from the invoice renewal billing transaction record. If checked, this renewal record will not be captured during renewal billing processing.

Chapter

  • Chapter Benefit? – Displays the information from the invoice renewal billing transaction record.

  • Chapter Is Primary? – Displays the information from the invoice renewal billing transaction record.

  • Chapter – Displays the information from the invoice renewal billing transaction record.

Renewal Cycle Information

  • Cycle Start Date – For a new member or subscriber, displays the information from the invoice renewal billing transaction record based on join date and benefit setup default start date. As renewals are generated that create new renewal billing records for this benefit and rate, this field displays that start date of that renewal cycle based on the benefit rate setup.

  • Cycle State – Based on the cycle start date and the system date, displays one of these states: Past, Current, or Upcoming. This field is updated by the system using a nightly process. For more information, see About Renewal Billing Cycle State and Cycle State Update Utility.

  • Cycle Year – This field is displayed on the renewal billing records view but not on the renewal billing record form. It represents the year of the Cycle Start Date.

  • Date Renewed – Displays a date calculated by the system based on the date payment in full is applied. This field is typically updated by the system during the life cycle of the related renewal invoice.

  • Expiration Date – Displays a date calculated by the system based on cycle end date when payment in full is applied. This field is typically updated by the system during the life cycle of the related renewal invoice.

  • Original Join Date – Displays a date calculated by the system.

  • Paid Through Date – Displays a date calculated by the system, based on installment schedule detail, when installment payment in full is applied. This field is typically updated by the system during the life cycle of the related renewal invoice.

  • Termination Date – Displays a date calculated by the system during the Renewal Termination Process or manual termination of an individual renewal billing record.

  • Current Join Date – Displays a date calculated by the system.

  • Expire of Last Renewal – Displays a date calculated by the system during the Generate Renewal Billing Invoices process using the expiration date of previous renewal.

  • Termination Reason – Displays the reason selected during the Renewal Termination Process or manual termination of an individual renewal billing record.

Financial

  • Override Price Temporary – Flag to indicate whether the override price is temporary (this renewal cycle only) or for all future renewals.

  • Override Price – Displays the information from the invoice renewal billing transaction record.

  • Price per Unit – Displays the information from the invoice renewal billing transaction record.

  • Promotion – Displays the information from the invoice renewal billing transaction record.

  • Base Amount – Displays the information from the invoice renewal billing transaction record.

  • Override Discount – Displays the information from the invoice renewal billing transaction record.

  • Discount Amount – Displays the information from the invoice renewal billing transaction record.

  • Prorate Cycle – Displays the information from the invoice renewal billing transaction record.

  • Prorate # of Months – Displays the information from the invoice renewal billing transaction record.

  • Override Prorate? – Displays the information from the invoice renewal billing transaction record.

  • Prorate Amount – Displays the information from the invoice renewal billing transaction record.

  • Bill Frequency – Displays the information from the invoice renewal billing transaction record.

  • Total Charge – Displays the information from the invoice renewal billing transaction record.

Next Renewal section

You can use the Next Renewal section to modify the rate to be used during the next renewal cycle for membership and subscriptions. If you need to change the rate for the next renewal, click the Rate Next Lookup button and select the new next rate.

  • Bill To Account – Displays the information from the invoice.

  • Bill To Contact – Displays the information from the invoice.

  • Rate Next – Displays the information from the invoice renewal billing transaction record. If you need to change the rate to be used in the next (upcoming) renewal, you can make the change in the current renewal billing record or in the benefit entry of the renewal invoice related to the current renewal billing record.

Installments section

The Installments section displays the installment information from the renewal invoice’s renewal billing transaction record as well as a link to the renewal billing invoice associated with this renewal billing record.

Administration section

Click Administration to view the user who created this record, when it was created, the user who last modified the record, and when it was last modified. The owner of the record is also displayed, along with the default dues or chapter billing product used for the benefit.

Certification

The fields in the Certification section are not used for membership dues or chapter dues renewals.

Related Information

In the Navigation Pane of the renewal billing record, additional related information is available, as described below:

  • Renewal Billing – Displays renewal billing records that were created from the renewal billing record you have open. For example:

    • Where cycle state = Current in the record you have open, you will see the upcoming renewal billing record (if renewal has been run).

    • Where cycle state = Upcoming in the record you have open, there will be no records displayed.

    • Where cycle state = Past in the record you have open, you will see the current renewal billing record (except if this record is from an upgrade where the current renewal billing record was not created in UX Online).

  • Benefit Recipients – Displays the benefit recipient records related to this renewal billing record.

  • Recert Category – Displays the recert category records related to Professional Development renewal billing records. This is not used for membership dues, chapter dues, or subscription renewal billing records.

  • Galley – Displays the galley records related to eligible renewal billing records.

Sample renewal billing record lifecycle scenarios

Cycle Start Date is greater than system date and the Config value for the application parameter PAMembership.NewMemberCycleState is blank.

  • Join Date = 06/01/2016 (system date joined as default)

  • Cycle Start Date = 07/01/2016

  • Cycle End Date = 06/30/2017

New Member Invoice Unpaid > Paid in Full

Renewal Billing Record Component

On 6/1/16

New Member –Invoice Unpaid

On 6/1/16

New Member – Invoice Paid in Full

On 7/1/16

On 7/1/17

Benefit Status

NULL

New

New

New

Cycle State

Upcoming

Upcoming

Current

Past

Cycle Start Date

07/01/2016

07/01/2016

07/01/2016

07/01/2016

Expiration Date

NULL

06/30/2017

06/30/2017

06/30/2017

Date Renewed

NULL

System Date Paid

System Date Paid

System Date Paid

Paid Through Date

NULL

06/30/2017

06/30/2017

06/30/2017

Original Join Date

06/01/2016

06/01/2016

06/01/2016

06/01/2016

Current Join Date

06/01/2016

06/01/2016

06/01/2016

06/01/2016

Termination Date

NULL

NULL

NULL

NULL

Termination Reason

NULL

NULL

NULL

NULL

Expire of Last Rnl

NULL

NULL

NULL

NULL

Account or Contact Record Component

Price Level

Non-member

Non-member

Member

Member

Member

No

No

Yes

Yes

Cycle Start Date is greater than system date and the Config value for the application parameter PAMembership.NewMemberCycleState = Current.

  • Join Date = 06/01/2016 (system date joined as default)

  • Cycle Start Date = 07/01/2016

  • Cycle End Date = 06/30/2017

New Member Invoice Unpaid > Paid in Full

Renewal Billing Record Component

On 6/1/16

New Member –Invoice Unpaid

On 6/1/16

New Member – Invoice Paid in Full

On 7/1/16

On 7/1/17

Benefit Status

NULL

New

New

New

Cycle State

Current

Current

Current

Past

Cycle Start Date

07/01/2016

07/01/2016

07/01/2016

07/01/2016

Expiration Date

NULL

06/30/2017

06/30/2017

06/30/2017

Date Renewed

NULL

System Date Paid

System Date Paid

System Date Paid

Paid Through Date

NULL

06/30/2017

06/30/2017

06/30/2017

Original Join Date

06/01/2016

06/01/2016

06/01/2016

06/01/2016

Current Join Date

06/01/2016

06/01/2016

06/01/2016

06/01/2016

Termination Date

NULL

NULL

NULL

NULL

Termination Reason

NULL

NULL

NULL

NULL

Expire of Last Rnl

NULL

NULL

NULL

NULL

Account or Contact Record Component

Price Level

Non-member

Non-member

Member

Member

Member

No

No

Yes

Yes

Cycle Start Date is equal to or less than system date.

  • Join Date = 06/01/2016 (system date joined as default)

  • Cycle Start Date = 06/01/2016

  • Cycle End Date = 05/31/2015

New Member Invoice Unpaid > Paid in Full

Renewal Billing Record Component

On 6/1/16

New Member –Invoice Unpaid

On 6/1/16

New Member – Invoice Paid in Full

On 6/1/17

Benefit Status

NULL

New

New

Cycle State

Current

Current

Past

Cycle Start Date

06/01/2016

06/01/2016

06/01/2016

Expiration Date

NULL

05/31/2017

05/31/2017

Date Renewed

NULL

System Date Paid

System Date Paid

Paid Through Date

NULL

05/31/2017

05/31/2017

Original Join Date

06/01/2016

06/01/2016

06/01/2016

Current Join Date

06/01/2016

06/01/2016

06/01/2016

Termination Date

NULL

NULL

NULL

Termination Reason

NULL

NULL

NULL

Expire of Last Rnl

NULL

NULL

NULL

Account or Contact Record Component

Price Level

Non-member

Member

Member

Member

No

Yes

Yes

About Renewal Billing Cycle State

Because UX Online creates a separate renewal billing record for each membership and subscription renewal process, each renewal billing record has a Cycle State. There are three possible values: Current, Upcoming, and Past.

In a member record, there can be only one Current, one Upcoming, and multiple Past renewal billing records for the same benefit and rate. Combined, these records create the history of the member’s renewal lifecycle. The Renewal Billing list view in a member’s record can provide a snapshot of the member’s lifecycle for each benefit and rate at glance, easily identifying the Current renewal billing record, the renewal billing Cycle Year, whether or not it is Primary, whether there is a related Upcoming renewal billing record, and more.

Generally, a renewal billing record for the current renewal cycle has a Cycle State = Current, a renewal billing record for the upcoming renewal cycle has a Cycle State = Upcoming, and a renewal billing record for a prior renewal cycle has a Cycle State = Past. There are exceptions for new members and new subscribers that are controlled by application parameters that can force a Cycle State = Current, regardless of the benefit setup default start date. See Configuring New Member Cycle State and Configuring New Subscriber Cycle State for more information.

The Cycle State is not determined by the renewal billing record benefit status, expiration date, or payment of the related renewal invoice. It is determined by system logic based on the system date, the renewal billing Cycle Start Date and the length of the membership or subscription.

Because many UX Online renewal billing processes and other related renewal billing actions rely on the renewal billing record Cycle State, a system job runs nightly to update the Cycle State automatically. See Cycle State Update Utility for more information.

About Cycle Year

The renewal billing Cycle Year attribute is not displayed on the Renewal Billing form; it is only visible in the Renewal Billing list view. The Cycle Year is defined as the year of the renewal billing cycle start date and cannot be modified. It is used for reference/reporting only.

Cycle State Update Utility

This utility is a system job included in the UX Online Renewal Billing Nightly Process designed to maintain the renewal billing record Cycle State for membership and subscriptions. It identifies all renewal billing records with a Cycle State = Upcoming where the Cycle Start Date is less than or equal to the system date.

For those records, it updates the Cycle State on the “Upcoming” renewal billing record to Current and if a related “Current” renewal billing record exists, it updates the Cycle State to Past.

For example, assume you have a renewal billing record with a Cycle State = Current for the current dues year with a Cycle Start Date of 1/1/16. When you generate renewals for the next renewal year, the system creates another renewal billing record with a Cycle State = Upcoming with a Cycle Start Date of 1/1/17 for the same benefit and rate. This Upcoming renewal billing record is related to the Current renewal billing, through the Prior Renewal Billing ID in the Upcoming renewal billing record.

When the Update Cycle State system job runs on 1/1/17, it will change the Cycle State on the “Upcoming” renewal billing record (the one with the Cycle Start Date = 1/1/17) to “Current” and change the Cycle State on the related “Current” renewal billing record (the one with the Cycle Start Date = 1/1/16) to “Past”.

To eliminate “orphaned” renewal billing records with a Cycle State = Current that have no relationship to an Upcoming renewal billing record (renewal was never generated for this record), the system job identifies those records, and based on a virtual expiration date, updates the Cycle State to Past. This update to “Past” occurs when the virtual expiration date is less than or equal to the system date AND no relationship exists to an Upcoming renewal billing record. (It does not look at the actual expiration date in the renewal billing record.) Renewal billing records where Cycle State = Past are excluded.

Note

Once the renewal billing record Cycle State is updated to Past, it is no longer eligible for the Generate Renewal Billing Invoices Process or for the Renewal Billing Termination Process. It can, however, be terminated manually so that it is eligible for Rejoin, assuming no Current renewal billing record exists for that benefit and rate.

The virtual expiration date is calculated as follows:

Cycle start Date + Number of Months defined in the Renewal Billing record – 1 Day = Virtual Expiration Date

Setting the primary renewal billing record

Any membership renewal billing record with a Cycle State = Current can potentially control whether or not an account or contact is considered a member or non-member and whether they are eligible to receive member or non-member pricing. Because any single account or contact can have multiple membership renewal billing records with a Cycle state = Current, at least one of those records must be marked as the primary renewal billing record for purposes of determining membership.

For example, assume that an account has two membership renewal billing records (for different membership levels) – both with a Cycle state = Current. Their status as a member and their eligibility for member pricing depends on whether their primary membership dues are paid; therefore, the renewal billing record for their primary membership is the record that should be used to control their membership status; that is, it should be marked as the primary renewal billing record.

Each renewal billing record has a Primary Benefit option that controls whether the system will update an account or contact’s Price Level field and the Member option. (Any changes made to these fields are based on the settings in the Renewal Billing Manager Price Level Member X-Ref and the benefit rate set up for Price Level Active and Price Level Terminated.) When the Primary Benefit option is Yes on a membership renewal billing record where the Cycle State = Current, the system relies on status information in the renewal billing record to update these two fields. When the Primary Benefit option is No, the renewal billing record will not have any effect on these fields.

Important

There can be only one current primary renewal billing record and one related upcoming primary renewal billing record. If you have already run the renewal process for the upcoming dues year and you are changing the primary renewal billing record, the Make Primary utility will update the primary benefit flag on the selected current renewal billing record and its related upcoming renewal billing record.

By default, the first time renewal benefit record for an account or contact record is created, the system sets the Primary Benefit option to Yes. If you create an invoice using a renewal benefit package that contains multiple benefits, the system will set the Primary Benefit option to Yes for the benefit detail type = Primary Membership.

After the first renewal benefit record is added to an account or contact, the Primary Benefit option for any subsequent records is automatically set to No.

You can use the Make Primary utility in the account or contact Renewal Billing list to override the system defaults and select which billing record should be primary. For example, if a contact was a non-member and their first renewal billing record was for a subscription, that renewal billing record would be the primary record by default. If you create a new member invoice for that contact, the new renewal billing record will not be the primary record, so you will need to make it primary.

Important

When you add or change a membership renewal billing record, you should verify that the correct record is marked as the primary. For example, if a contact had an existing subscription renewal billing record marked as primary and that contact then joins your organization, and you create a new member invoice, you will need to change the Primary Benefit option on this membership renewal billing to Yes. If you do not do so, the system will not update the member price level and member flag.

Use this procedure to change a renewal billing record primary flag for an account or contact record.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to set the primary renewal billing record.

Click Renewal Billing in the record’s Navigation Pane to open the List View of renewal billing records. Click to select the renewal billing record with a cycle state = current that you want to make primary. Click the Make Primary button on the List View toolbar.

The system will update the Primary Benefit option from No to Yes on the selected renewal billing record and if one exists, it updates its related upcoming renewal billing record. The system updates the Primary Benefit option on the previous primary renewal billing record from Yes to No and if one exists, it updates its related upcoming renewal billing record.

Important

System logic to update the account or contact price level and member flag for renewal billing records where Primary Flag is Yes depends on the status and cycle state of the renewal billing record.

Validating Membership

Following manual renewal billing invoice changes, you can manually validate the price level of the primary membership renewal billing record with a Cycle State = Current to update the account or contact record price list and member flag.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want validate the price list and member flag.

Click Renewal Billing in the record’s Navigation Pane to open the List View of renewal billing records. Click to select the primary membership renewal billing record with a cycle state = current (there should only be one). Click the Validate button displayed under the more icon (…..) on the List View toolbar. Assuming the selected record does not share its parent price list, UX will validate the selected renewal billing record and update the record price list and member flag based accordingly. You must Save & Close and then reopen the record to see the changes to the data in the record.

Managing payments, transfers, refunds and credits

UX Online payment logic supports updates to the renewal billing record, and if that renewal billing record is primary and the Cycle State = Current, also updates to the account/contact record. These updates occur only when the payment satisfies the full amount of the first installment for each renewal benefit in the invoice. In the case of an invoice that contains detail for a renewal benefit that has a single annual installment, the update does not occur until the full amount of that benefit is paid. In the case of an invoice that contains a renewal benefit that has multiple installments, the update does not occur until the full amount of the first installment is paid. In situations where a single invoice contains multiple renewal benefits, updates do not occur until payment of the first installment for each benefit is paid full.

Important

All examples above assume a Cycle State = Current. The system will not update the price level or the member flag of an account or contact record, regardless of the payments applied to a new member invoice or the renewal billing status, unless the renewal billing record Cycle State = Current and the renewal billing record is primary.

Applying payments to a membership renewal invoice

Use this procedure to apply payments to a membership renewal invoice.

Important

When applying payment to a renewal billing invoice created from a package, the payment must be equal to or greater than the sum of all 1st installments before the renewal billing record is updated. For example, you create a package that contains a single installment primary membership benefit with rate of $120.00 and a single installment chapter membership benefit with a rate of $25.00. When you use this package to create a new member invoice and the member pays only the primary membership amount of $120.00, the system will not update the renewal billing information until full payment for the chapter is applied.

Note

The following procedure shows how to begin this process from the contact’s record, but you can also begin from an account record.

From any of the UX work areas on the Navigation Tile Bar, click Contacts. Open the contact record where you want to apply a payment to an invoice. In the Navigation Pane of the customer’s record, click Invoices. Locate and open the membership invoice where you want to apply a payment.

Within the invoice, if you have not already selected your batch, select the appropriate open batch.

Note

You can open any invoice whether or not you are working in an open batch. However, to open invoice detail line items or make any changes to the invoice, you must be working in an open batch.

To apply a payment to the invoice, click New Transactions > Payments & Adjustments on the invoice Record toolbar. See Payment and Adjustments Transactions for details on entering transactions based on payment type.

Note

If you enter a payment on a renewal billing invoice, and the customer has an older unpaid renewal billing invoice, an alert message will appear notifying you of the existing invoice.

Click Save & Close to save the payment and return to the invoice.

Review the payment invoice detail line item to make sure it is correct and that the invoice balance due is correct. Click Save & Close to close the invoice.

Note

When you enter a transaction that changes a customer’s membership status, the UX Online system takes a few minutes to finish updating the renewal billing record. However, if you select the renewal billing record and click the Validate button on the List View toolbar at the top of the list of renewal billing records, the system will update the records immediately, if appropriate to do so.

When the payment is entered and you Save & Close the invoice, the system updates the associated renewal billing record. The changes to the associated renewal billing record depend on whether the invoice is for a new membership, membership renewal, or rejoin membership.

New membership invoice – If the invoice is for a new membership, the renewal billing record will change as follows:

  • Benefit Status will change from NULL to New if the payment was equal to or greater than the first installment detail line.

  • Date Renewed field will change to the system date when the payment is applied.

  • Paid Through Date will change to the installment end date. In the case of a single annual installment, this date will be the cycle end date. In the case of multiple installments, this date will be the end of the last fully paid installment.

  • Expiration Date will change to the cycle end date.

  • If the renewal billing record for the benefit in this invoice was marked as primary and the Cycle State = Current, the system will change the account or contact price level from non-member to Member and change the member flag from No to Yes.

Membership renewal invoice – If the invoice is for a membership renewal where the renewal billing Cycle State = Current or Upcoming, the renewal billing record will change as follows:

  • Benefit Status will change from New to Renew if the payment was equal to or greater than the first installment detail line.

  • Date Renewed field will change to the system date when the payment is applied.

  • Paid Through Date will change to the installment end date. In the case of a single annual installment, this date will be the cycle end date. In the case of multiple installments, this date will be the end of the last fully paid installment.

  • Expiration Date will change to the cycle end date.

Membership rejoin invoice – If the invoice is the result of rejoining a terminated membership where the renewal billing Cycle State = Past, the system creates a new associated renewal billing record based on the terminated renewal billing record.

Important

Rejoin is only available for renewal billing records where the Cycle State = Past, Benefit Status = Terminated, and there is no existing renewal billing record for the same benefit/rate where the Cycle State = Current.

When payment is applied:

  • Benefit Status will change from NULL to NEW, if the payment was equal to or greater than the first installment detail line in the invoice.

  • Date Renewed field will change from NULL to the system date, when the payment is applied.

  • Paid Through Date will change from NULL to the installment end date. In the case of a single annual installment, this date will be the cycle end date. In the case of multiple installments, this date will be the end of the last fully paid installment.

  • Expiration Date will change from NULL to the cycle end date.

  • If the renewal billing record for the benefit in this invoice was marked as primary, the system will change the account or contact price level from non-member to member and change the member flag from No to Yes.

Deleting a cash or check membership payment

You cannot delete a payment detail line item from the invoice if the originating batch is closed. Accounting principles and best practices for consistent entry require that payment cancellations must be recorded using a reversing entry. For information about reversing cash or check payments, see Canceling a cash or check payment. For information about reversing credit card payments, see Voiding a credit card payment.

This option is useful when you have applied a cash or check payment to the wrong invoice by mistake and the batch in which you applied the payment is still open.

Note

The following procedure shows how to begin this process from the contact’s record, but you can also begin from an account record.

From any of the UX work areas on the Navigation Tile Bar, click Contacts. Open the contact record and click Invoices in the Navigation Pane. Locate and open the membership invoice where you want to delete a cash or check payment.

Within the Invoice, check the batch number for the payment detail line that you want to delete. Click Select Batch on the invoice Record toolbar and then select the same batch.

Check the box to left of the payment detail record you want to delete to select it.

Click the Cancel button in the transactions grid toolbar. A message will appear asking you to confirm that you want to cancel/delete the payment detail. Click Yes to delete the payment.

Verify that the payment detail record has been deleted from the invoice. Confirm updates to the invoice totals. Click Save & Close.

When the cash or check payment is deleted and you Save & Close the invoice, the system updates the renewal billing record.

Canceling a renewal invoice

If necessary, you can cancel a customer’s current renewal benefit invoice. This is a permanent transaction. In other words, once you cancel a current renewal benefit, it cannot be reinstated or renewed. The member cannot rejoin for the same benefit and rate in the current dues cycle.

Important

If you have already generated renewals for the upcoming renewal year and are cancelling the Current renewal invoice, you must also cancel the Upcoming renewal invoice.

Depending on batch status, cancellation in a dues or subscription benefit entry, cancels or deletes invoice detail, terminates the related renewal billing record, and breaks the relationship between the renewal billing record and the renewal invoice for this invoice and its related renewal billing record only. For example:

  • If you are cancelling the benefit entry in the invoice for a past renewal billing record, the cancellation will not affect any related current or upcoming renewal billing records or their related invoices. If this was a primary benefit, cancellation will not affect the price level or member flag in the record.

  • If you are cancelling the benefit entry in the invoice for a current renewal billing record, the cancellation will not affect any related past or upcoming renewal billing records or their related invoices. If this was a primary benefit, cancelling the benefit entry in the invoice for a current renewal billing record will update the price level and member flag in the record.

  • If you are cancelling the benefit entry in the invoice for an upcoming renewal billing record, the cancellation will not affect any related past or current renewal billing records or their related invoices. If this was a primary benefit, cancellation will not affect the price level or member flag in the record.

Note

If processing a full cancellation in the originating (open) batch and the renewal billing record status = NULL, as would be the case for an unpaid new member invoice, cancelling the benefit entry will delete the invoice detail and delete the related renewal billing record.

Full or partial cancellation

If a member wishes to cancel their membership and your organization does not prorate the amount of “unused” membership, you would process a full cancellation on the current renewal invoice. If you had already run the renewal process for the next renewal cycle, you would also process a full cancellation on the upcoming renewal invoice.

If a member wishes to cancel their membership and your organization prorates the “unused” membership based on the cancellation date, you would process a partial cancellation on the current renewal invoice. You can partially cancel single and multiple-installment anniversary dues, single-installment calendar dues, and multiple-installment calendar dues if they are not prorated. If you had already run the renewal process for the next renewal cycle, you would then process a full cancellation on the upcoming renewal invoice.

Note

You cannot partially cancel multiple-installment calendar dues with prorate. If you attempt a partial cancellation in a multiple-installment prorated calendar dues line item, the system will cancel the entire amount.

If a member wishes to change their membership to a different benefit during the current dues cycle, you would use Upgrade/Downgrade in the benefit entry record of the invoice for the current renewal billing record instead of cancellation. See Upgrading or downgrading membership for additional information. If you had already run the renewal process for the next renewal cycle, you would upgrade/downgrade the current renewal invoice and process a full cancellation on the upcoming renewal invoice. Once the current upgraded/downgraded renewal invoice is paid, you can generate a new upcoming renewal invoice for the customer.

Batch open or closed

There are two batch scenarios for canceling a renewal invoice:

  • Canceling a renewal invoice line item in a closed batch

    • Full cancellation will cancel the invoice detail line item and create the necessary general ledger entries to reverse the dues transaction.

    • Partial cancellation will cancel the original invoice detail line item and create a new invoice detail line item for a prorated portion of the full dues charge.

  • Canceling a renewal invoice line item in the originating open batch

    • Full cancellation will delete the invoice detail line item.

    • You cannot partially cancel a renewal invoice line item in the originating open batch. Selecting partial will result in a full cancellation.

Canceling a renewal invoice line item in a closed batch

From the account or contact’s record, open the renewal billing invoice that needs to be canceled. If you have not already selected your batch for the day, select the appropriate open batch, and then click Save.

Double-click the dues renewal invoice detail line item to open the benefit entry form. Click the Cancel button on the Record toolbar.

The Renewal Billing Cancel dialog appears. Indicate whether you are processing a full or a partial cancellation and select a cancellation reason.

If you select Partial Cancellation, enter the cancellation date, which must be the last day of the month, and a cancellation reason. (The system uses this date to calculate the prorated portion of the renewal dues to credit to the customer.) If you select Full, select a cancellation reason.

Note

You cannot partially cancel multiple-installment calendar dues with prorates. If you attempt a partial cancellation in a multiple-installment, prorated calendar dues line item, the system will treat it as a full cancellation and cancel the entire amount.

If the user enters a cancellation date that is prior to the deferral start date of the original invoice detail, there is no partial cancellation. The system will treat it as a full cancellation and cancel the entire amount.

Click OK. The system will cancel the original dues renewal invoice detail line, and if you processed a partial cancellation, will create a new line item for the prorated dues amount.

If a payment was applied to the invoice, you will need to deal with the credit balance. Depending on the type of the payment, you can create a refund for a check payment, or credit a credit card payment. (For more information, see Issuing a refund by check or Issuing a credit card refund.) Or, you can transfer the credit balance to another invoice for this account or contact. (For more information, see Transferring a payment from one invoice to another.)

Canceling a renewal invoice line item in the originating open batch

Go to the account or contact record and open the renewal billing invoice that needs to be canceled. Double-click the dues renewal invoice detail line item to open the benefit entry form.

Click the Cancel button on the Record toolbar. The Renewal Billing Cancel dialog appears. Select Full and a cancellation reason. You cannot partially cancel a renewal invoice line item in the originating open batch. Selecting partial will result in a full cancellation.

Select OK to continue. Because you are working in the originating open batch, the system deletes the dues renewal invoice detail line item and related renewal billing record.

If a payment was applied to the invoice, you will need to deal with the credit balance. Depending on the type of the payment, you can create a refund for a check payment or credit a credit card payment. (For more information, see Issuing a refund by check or Issuing a credit card refund.) Or, you can transfer the credit balance to another invoice for this account or contact. (For more information, see Transferring a payment from one invoice to another.)

Invoice Detail Calculations for Partial Cancellations

When the cancellation date entered for a partial cancellation is greater than the deferral start date of the invoice detail being cancelled, the process creates a new invoice detail line item for the partial (prorated) amount, using the renewal product from the cancelled invoice detail.

Note

If the user enters a cancellation date that is prior to the deferral start date, there is no partial cancellation – the system will cancel the existing invoice detail line and will not create invoice detail for a partial cancellation.

To support proper revenue recognition, the new invoice detail inherits the deferral start date from the original invoice detail and uses the cancellation date entered as the deferral end date.

To calculate the amount for the partial cancellation, the system:

  • uses the deferral start date and end dates as the basis for calculating the # of membership months in the original invoice detail

  • uses the deferral start date and cancellation date as the basis for calculating the # of partial membership months used

  • uses the total amount charged in the original invoice detail / (calculated membership # of months * calculated # partial membership months) for calculating the new invoice detail amount.

For example:

  • Cancellation Date = 10/31/16

  • Deferral Start Date = 9/1/2016

  • Deferral End Date = 12/31/2016

  • Total Amount Charged = $33.33

  • Calculated # of original membership months = 4 months (9/1/2016 to 12/31/2016)

  • Calculated # of partial membership months = 2 months (9/1/2016 to 10/31/2016)

  • New invoice detail amount:  33.33 / 4 * 2 = $16.66

The user will have the option to override the calculated amount inside the invoice detail record and re-calculate the invoice. If the benefit is taxable, the system will calculate taxes based on the prorated amount.

Terminating a single membership

Terminating a single membership does not alter the charges in the dues renewal invoice, as is the case with cancellation. Typically, you would only terminate the current renewal billing record, unless you have already run the renewal process for the upcoming renewal year.

The effect of the termination depends on the renewal billing record Cycle State:

  • Terminating a Past renewal billing record is not recommended. These records are in the past and have no effect on renewal billing or membership status.

  • If you are terminating a Current renewal billing record, the termination will not affect any related Past or Upcoming renewal billing records or their related invoices. If this was a primary benefit, terminating a Current renewal billing record will update the price level and member flag in the record. Benefit status is updated to Terminated, along with updates to the Termination Date and Reason. The record is no longer eligible for renewal; however, the invoice detail for dues remains in place.

Note

If you terminate a current renewal billing record and you have already run the renewal process, you should cancel the upcoming renewal billing invoice as this renewal billing record will eventually update to the current renewal billing record.

  • If you are terminating an Upcoming renewal billing record, the termination will not affect any related Past or Current renewal billing records or their related invoices. If this was a primary benefit, termination will not affect the price level or member flag in the record. Benefit status is updated to Terminated, along with updates to the Termination Date and Reason.

You can terminate an individual membership in UX Online using either of these methods:

  • Terminating from the renewal billing record

  • Terminating from the renewal billing invoice detail line item

Terminating from the renewal billing record

Note

The following procedure shows how to begin this process from the contact’s record, but you can also begin from an account record.

From any of the UX work areas on the Navigation Tile Bar, click Contacts. Locate and open the contact whose membership you want to terminate. Click Renewal Billing in the record’s Navigation Pane to display a List View of this contact’s renewal billing records.

Important

If you have already generated renewals for the upcoming renewal year and are terminating the Current renewal billing record, you must also terminate the Upcoming renewal billing record.

Click to select the membership renewal billing record you want to terminate. Click the Terminate button on the List View toolbar.

In the Renewal Billing Termination dialog box, select the reason you are terminating this membership from the Reason list.

Click OK. The system updates the following fields on the renewal billing record:

    • Benefit Status – Changes to Terminated.

    • Termination Date – Displays the system date.

    • Termination Reason – Displays the termination reason you selected in the Renewal Billing Termination dialog box.

If this was the primary renewal billing record (that is, the Primary Benefit field was set to Yes) and Cycle State = Current, the system also updates the price level from Member to Non-Member and changes the Member field on the account or contact record to No. If this was not the primary renewal billing record or the cycle state <> current, the system does not update the account or contact record’s price level or membership.

Depending on your organization’s business requirements, if the terminated renewal billing record was the primary benefit, you may want to select another renewal billing record as primary. For more information, see Setting the primary renewal billing record.

Note

Please allow a few minutes for the system to process the termination and update all requisite fields in the renewal billing record and the account/contact record. It is not instant.

Click the name of the record on the Top Navigation Toolbar to return to the contact record.

Terminating from the renewal billing invoice detail line item

Note

The following procedure shows how to begin this process from the contact’s record, but you can also begin from an account record.

From any of the UX work areas on the Navigation Tile Bar, click Contacts. Locate and open the contact whose membership you want to terminate. In the Navigation Pane of the customer’s record, click Invoices. Locate and open the membership invoice you want to terminate.

Important

If you have already generated renewals for the upcoming renewal year and are terminating the Current renewal invoice, you must also terminate the Upcoming renewal invoice.

Within the Invoice, if you have not already selected your batch, select the appropriate open batch. Double-click the renewal benefit invoice detail line item to open the benefit entry form.

Click the Terminate button on the Record toolbar.

In the Renewal Billing Termination dialog box, select the reason you are terminating this membership from the Reason list.

Click OK. The system processes the invoice for termination and returns you to the invoice. Click Save & Close to close the invoice and return to the List View of invoices.

Click the name of the record on the Top Navigation Toolbar to return to the contact record.

Note

Please allow a few minutes for the system to process the termination and update all appropriate fields in the renewal billing record and the account or contact record. It is not instant.

Depending on your organization’s business requirements, if this is the primary renewal billing record, you may want to select another renewal billing record as primary. For more information, see Setting the primary renewal billing record.

Reinstating membership

Reinstatement should only be used on current renewal billing records that have been terminated during the current renewal year. The procedure you will use to reinstate a current membership renewal billing record depends on the reason the membership was terminated:

  • Reinstate a current membership renewal billing record that was terminated for nonpayment

  • Reinstate a current membership renewal billing record that was terminated for other reasons

Important

If the membership renewal billing record was terminated for a past dues cycle or if the terminated renewal billing record was converted from your organization’s previous system, and you want to allow the customer to join again, UX Online treats this as a Rejoin. See Rejoin Membership for more information.

Reinstating membership terminated for nonpayment

If a member’s current renewal billing record was terminated for non-payment, you can reinstate the current renewal billing record by applying full payment to the related current membership dues invoice.

Important

You can only reinstate during the current dues cycle. Payments applied to a Past or Upcoming membership dues invoices will not reinstate membership.

If a membership was terminated for a past dues cycle and you want to allow that customer to join again, UX Online treats this as a Rejoin. See Rejoin Membership for more information.

Once payment is entered and you Save & Close the invoice, the system processes the reinstatement:

  • The system then updates the Benefit Status field on the terminated renewal billing record to Reinstated, and the record is now eligible for renewal in the next renewal billing cycle.

  • If this is the primary renewal billing record, the system also updates the record price level from member to non-member and the member flag to Yes. If this is not the primary renewal billing record, no changes are made to the price level or member option.

Note

Normally, when you enter a transaction that changes a customer’s membership status, the UX Online system takes a few minutes to finish updating the membership record.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Locate and open the account or contact whose membership you want to reinstate. In the Navigation Pane of the account or contact record, click Invoices. Locate and open the current membership invoice where the related renewal billing record is terminated.

Hint

The current membership invoice also can be found within the Current renewal billing record.

Click Select Batch to select the appropriate open batch based on your organization’s business rules. For information about batches, see Batch overview.

Click New Transactions > Payments & Adjustments button on the invoice Record toolbar and select the payment type. Enter the full payment. (For more information, see Payment and Adjustment Transactions.)

Click Save & Close to save and close the invoice and return to the invoices List View.

To verify that the current renewal billing record was reinstated, in the Navigation Pane of the account or contact’s record, click Renewal Billing, and then double click the current renewal billing record for this membership. Verify that the Benefit Status is Reinstated, and that the Expiration Date and Paid through Date have increased by the correct term. The Terminated Date and Reason will still display the information as a reference for reporting.

Reinstating membership terminated for reasons other than nonpayment

If the current renewal invoice was paid in full prior to termination, and the membership was terminated for any reason other than nonpayment, you can reinstate the current membership during the current renewal cycle.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Locate and open the account or contact whose membership you want to reinstate. In the Navigation Pane of the account or contact record, click Invoices to open the List view of invoices. Locate and open the current membership invoice where the related renewal billing record is terminated.

Hint

The current membership invoice also can be found within the Current renewal billing record.

Click Select Batch to select the appropriate open batch based on your organization’s business rules. For information about batches, see Batch overview.

Double-click the renewal benefit invoice detail line item to open the benefit entry form. Click the Re-calculate Invoice button on the Record toolbar.

The system will cancel the original invoice detail line item(s) and create a new one using the selected batch.

Note

This may affect GL detail since the invoice was fully paid prior to termination. The appropriate reversing entries and new entries will be created.

Confirm that the invoice balance due is $0.00. Click Save & Close on the invoice to return to the invoices List View.

Note

Please allow a few minutes for the system to process the reinstatement and update all appropriate fields in the renewal billing record. It is not instant.

To verify that the current renewal billing record was reinstated, in the Navigation Pane of the account or contact’s record, click Renewal Billing, and then double click the current renewal billing record for this membership. Verify that the Benefit Status is Reinstated. The Terminated Date and Reason will still display the information as a reference for reporting. If this is the primary renewal billing record, the system also updates the record price level from non-member to member and the member flag to Yes. If this is not the primary renewal billing record, no changes are made to the price level or member option.

Reinstating a terminated membership from a legacy system

If you have terminated membership records that were converted from your organization’s previous association management system, they will not have associated membership dues invoices in UX Online. If you want to reinstate any of these members, you will need to process a rejoin. See Rejoin Membership for more information.

Recalculating a membership renewal invoice

You may recalculate a renewal billing invoice if you need to change the join date, the rate, the quantity, or the volume if the rate selected is a volume-based rate. You cannot recalculate a membership invoice if you need to change the benefit selected.

Note

The following procedure shows how to begin this process from the contact’s record, but you can also begin from an account record.

From any of the UX work areas on the Navigation Tile Bar, click Contacts. Locate and open the contact with the membership renewal invoice you want to recalculate. In the Navigation Pane of the customer’s record, click Invoices.

Hint

The current renewal invoice also can be found within the Current renewal billing record.

Important

If you have already generated renewals for the upcoming renewal year and are recalculating the Current renewal invoice, you must also recalculate the Upcoming renewal invoice.

Locate and open the membership invoice you want to recalculate. Click Select Batch to select the appropriate open batch based on your organization’s business rules. For information about batches, see Batch overview.

Note

You can open any invoice whether or not you are working in an open batch. However, to open invoice detail line items or make any changes to the invoice, you must be working in an open batch.

Double-click to open the renewal billing invoice detail line item. In the renewal billing transaction record, if you need to change the benefit rate, click the Lookup button on the Rate field and select a new rate.

To change the original join date, click the Calendar button on the Original Join Date field to select a new date.

To modify the volume, enter a new value in the Volume field. For rates where the rate type = volume or factor, UX will update the price based on the changed value and the rate/prices setup.

To modify the quantity, enter a new value in the Quantity field. For rates where the rate type = quantity, UX will update the price based on the quantity x price per unit for the selected rate. Changes to this field do not affect pricing for rates where rate type = volume or factor.

The entries in the renewal billing transaction record will be updated based on the new rate, new original join date, or new volume selected. Review the entries carefully.

Click the Save button to save your changes. Click the Re-Calculate Invoice button on the Record toolbar. When you recalculate the invoice, any changes will be updated in the related renewal billing record, as well as related invoice detail.

A message will appear asking you to confirm that you want to recalculate the invoice. Click OK.

Note

The invoice will not be recalculated until you click the Re-Calculate Invoice button to complete the transaction.

The system will recalculate the invoice amount and totals based on the new rate, join date, or volume, etc. For example, if the recalculation is based on a new rate, you will see the new rate and amounts due based on the new rate selected. If the recalculation was based on a change to the volume or the original join date, only the amounts will be updated.

Click Save & Close to save your renewal billing transaction changes and return to the invoice. Save & Close the invoice.

Note

If the batch in which the original detail line item had been entered has since been closed, then the Re-Calculate logic will automatically cancel the original line item and create a new line item with the new information. If the batch is still open, the original line item will be deleted, and a new line item will be created.

If a payment had been entered on the original transaction, you may have a balance due or a credit balance depending on whether the price on the new rate is more or less than what was originally paid.

If full payment had been entered on the original transaction and the recalculation results in a balance due of the first installment for any renewal benefit in the recalculated invoice, the system will update the renewal billing record as follows:

  • If the renewal benefit status is New or Reinstated and the renewal cycle state = Current, the system will update the renewal billing record and update the account/contact default price level field and member flag if the renewal billing record flag is primary.

  • If the renewal benefit status is Renew and the renewal cycle state = Current, the system will update the renewal billing record. There are no changes to the account/contact default price level field and member flag if the renewal billing record flag is primary.

Rejoin Membership

Rejoining an existing renewal billing record is available only for renewal billing records where the cycle state = Past and the benefit status = Terminated and there is no renewal billing record for the same benefit with a cycle state = Current.

This feature can also be used for terminated renewal billing records converted from a legacy system where no current renewal billing invoice exists.

To process a rejoin, in the Navigation Pane of the account or contact’s record, click Renewal Billing to view a list of existing renewal billing records.

Click to select the past and terminated renewal billing record for the membership benefit. Click Rejoin from the List View toolbar on the list view of renewal billing records.

In the Rejoin Renewal dialog, use the Lookup to select the batch to be used for this transaction and use the Calendar to select the Current Join Date.

Click OK. The system will create a new renewal invoice and a new related renewal billing record for the current renewal cycle. The benefit status will remain NULL until full payment is applied against the newly created renewal invoice.

To apply payment to the invoice, see Applying payments to a membership renewal invoice.

Once the invoice is paid in full, the system will update the renewal billing record as follows:

Benefit Status will change from NULL to New, if the payment was equal to or greater than the first installment detail line in the invoice.

  • Date Renewed field will change from NULL to the system date, when the payment is applied.

  • Paid Through Date will change from NULL to the installment end date. In the case of a single annual installment, this date will be the cycle end date. In the case of multiple installments, this date will be the end of the last fully paid installment.

  • Expiration Date will change from NULL to the cycle end date.

  • If the renewal billing record for the benefit in this invoice was marked as primary, the system will change the account or contact price level from non-member to member and change the member flag from No to Yes.

Renewal billing pricing overrides

Price per unit overrides – permanent or temporary

If you override the default price per unit on the renewal billing transaction record of a membership invoice—whether it is a new member invoice or an existing membership renewal invoice—the new price you enter will apply to all future renewal invoices, unless Override Price Temporary = Yes. For example, if the price per unit for a membership benefit is $300, but you change it to $250 when creating an invoice for a new member, the future renewal invoices created for that member will use the $250 price, unless Override Price Temporary = Yes. If Overprice Price Temporary = Yes, the override price is valid only for this renewal invoice.

Price, discount, or prorate amount overrides on a new member dues invoice

Create a new member invoice, following the procedure in Creating a new member invoice using a renewal benefit. In the renewal billing transaction record:

To override the price, set the Override Price option to Yes and enter the new price in the Price Per Unit field.

If this is a temporary (one-time) price override, set the Override Price Temporary = Yes. If this is a permanent price override for this rate, set the Override Price Temporary = No.

Note

If you override the price for a benefit where the prorate cycle is Current, the system automatically recalculates the prorate amount based on the new price per unit.

To override the discount, set the Override Discount option to Yes, and enter the new discount in the Discount Amount field. This is a one-time override for this invoice.

To override the prorate amount, set the Override Prorate Amount option to Yes and enter the new prorate amount in the Prorate Amount field. (This is not recommended.)

Note

If you override the prorate amount on a new member invoice, and the prorate cycle in the selected benefit is Current, the new prorate amount will apply to the new member invoice. If the prorate cycle for the selected benefit is Next, the new prorate amount will apply to the first renewal invoice.

Click Save & Close the renewal billing transaction to return to the invoice. Save & Close the invoice.

Price or discount overrides on an existing renewal invoice

You can override the price on an existing membership renewal invoice and recalculate the invoice.

Note

The following procedure shows how to begin this process from the contact’s record, but you can also begin from an account record.

From any of the UX work areas on the Navigation Tile Bar, click Contacts. Locate and open the contact record where you want to override membership price or prorate. In the Navigation Pane of the contact’s record, click Invoices. Locate and open the membership renewal invoice you want to modify. In the invoice, open the renewal invoice detail line item to open the renewal billing transaction record.

To override the price, set the Override Price option to Yes and enter the new price in the Price Per Unit field. If this is a temporary (one-time) price override, set the Override Price Temporary = Yes. If this is a permanent price override for this rate, set the Override Price Temporary = No.

To override the discount, set the Override Discount option to Yes and enter the new discount in the Discount Amount field. This is a one-time override.

Note

You should not override the prorate amount for any renewal member invoice.

Select Re-calculate Invoice on the benefit entry Record toolbar.

Click Save & Close in the renewal billing transaction record. Click Save & Close to close the invoice.

Cancel price per unit overrides

You can cancel price per unit overrides for calculating future membership renewal invoices by changing the Override Price Temporary flag from No to Yes in either the most current membership renewal invoice or in the renewal billing record where cycle state = Current. If you have already generated your next renewal invoices, you will need to make the change in the renewal billing record where cycle state = Upcoming.

Upgrade/Downgrade Membership

This optional feature can be used if a member wants to change their membership benefit during the renewal year, you can use Upgrade/Downgrade Membership. You can upgrade or downgrade a membership at any time within the renewal cycle.

Because not all organizations allow mid-year changes, this feature is only available when the PAUpgradeDowngrade.ShowButton application parameter = true. By default, this parameter is set to false.

Important considerations

  • Upgrade/Downgrade Membership is available for benefit rate setups with a single annual installment only. It does not support multiple installment rates.

  • If you are changing only the rate, join date, or quantity, do not use Upgrade/Downgrade. See Re-calculating a renewal membership invoice for more information.

  • The current join date entered in the Upgrade/Downgrade process should always be the first day of a month. It represents the effective date of the change and is used to calculate the number of months used under the original benefit. It is used again to establish the cycle start date for the new benefit based on the setup of the new membership benefit.

  • When using Upgrade/Downgrade, the system will calculate the cycle start date for the new benefit based on the setup for benefit you select and the current join date you enter. The current join date for the new benefit should always be a date within the same Cycle Year as the benefit you are upgrading/downgrading.

  • Charges for the new benefit are calculated in the same manner as those for a new membership. If the new benefit is anniversary-based, charges are not prorated. If the new benefit is calendar-based, the charges might be prorated.

  • Upgrades/Downgrades will update the related renewal billing record based on the invoice balance due using standard system logic. For example, the renewal billing record for a new member who paid their new member dues invoice in full prior to the Upgrade/Downgrade will lose benefit status, expiration date, paid through date, and date renewed if the recalculated invoice balance is greater than $0.00. This, in turn, would also trigger an update to the Price Level and Member flag until the invoice is paid in full.

  • Since recalculating the invoice is included in the Upgrade/Downgrade process, using the recalculate button on the renewal billing transaction Record toolbar is not required.

Mid-year v. full year changes

This process accommodates mid-year benefit changes when a member wants to change their membership after the beginning of the renewal cycle but before the end of the renewal cycle. In this scenario, charges for the original benefit should be partially discounted, so that the member is charged a prorated amount for the number of months used. The member is charged for the new benefit by creating new invoice detail in a manner that mirrors calculating dues for a new membership.

  • Updates the original invoice detail line item by calculating a discount amount for the number of unused membership months for the original benefit. See Calculation Methodology for additional details.

  • Cancels the benefit entry in the original invoice detail line item – “Benefit Cancelled” (the invoice detail line is not cancelled as it contains the updated charges for the original benefit).

  • Creates new invoice detail line item with charges based on the new benefit, rate and, join date selected.

  • Recalculates the invoice totals.

  • Updates the related renewal billing record based on the new benefit, rate and join date selected, and the recalculated invoice totals.

This process accommodates full year benefit changes when a member wants to change their membership for the entire renewal cycle. In this scenario, charges for the original benefit should be fully discounted, so that the member is not charged for the unused membership. The member is charged for the new benefit by creating invoice detail in a manner that mirrors calculating dues for a new membership.

  • Updates the charges in the original invoice detail by calculating a discount amount based on the entire renewal cycle – this is essentially a 100% discount, bringing the charges for the original invoice detail to $0.00. See Calculation Methodology for additional details.

  • Cancels the benefit entry in the original invoice detail line item – “Benefit Cancelled” (the invoice detail line is not cancelled, as it contains the updated charges for the original benefit).

  • Creates new invoice detail line item with charges based on the new benefit, rate, and join date selected.

  • Recalculates the invoice totals.

  • Updates the related renewal billing record based on the new benefit, rate and join date selected, and the recalculated invoice totals.

Important

If you have already generated renewals for the upcoming renewal year and are processing an Upgrade/Downgrade on the Current renewal invoice, you must also process the same Upgrade/Downgrade on the Upcoming renewal invoice. Cancelling the Upcoming renewal invoice and attempting to generate a new renewal invoice based on the upgraded renewal billing will not work.

Processing an Upgrade/Downgrade

From the account or contact’s record, select the renewal billing invoice that needs to be upgraded or downgraded.

Hint

The current renewal billing invoice also can be found within the Current renewal billing record.

If you have not already selected your batch for the day, select the appropriate open batch and then click Save.

Double-click the dues invoice detail line item to open it. Click the Upgrade/Downgrade Membership button.

In the Upgrade/Downgrade Membership dialog, enter the new benefit and rate.

Caution

Selecting a calendar-based benefit with prorating will trigger prorate calculations as if this is a new membership.

In the Current Join Date field, enter or select the effective date for the membership upgrade or downgrade. Select a date that is within the current renewal cycle.

Note

The Current Join Date field will display the first day of the next month by default. For any date that you enter, the system will use the first day of that month for its calculations. For example, if you enter 10/15/13, the system will use 10/01/13.

After verifying your entries for benefit, rate, and current join date, click OK. The system will recalculate original dues invoice detail line item and create a new invoice detail line item for the new benefit, rate, and join date.

Upgrade/Downgrade logic for determining the discount when recalculating the original invoice detail line item

NoOfMonthsUsed = CurrentJoinDate – CycleStartDate

ProratedDiscount = TotalAmount / Number of Months; (Both of these are the Renewal Billing)

DiscountApplied = TotalAmount  – (NoOfMonthsUsed  * ProratedDiscount)

Note: The DiscountApplied is the Discount amount shown in the original invoice detail line item to recalculate the charges.

Sample scenario: Member is a Senior Associate and a dues renewal invoice exists for this membership for the period 1/1/2016 to 12/31/2016. In February 2016, the member wants to change his membership from Senior Associate to Junior Associate, effective March 1, 2016.

Renewal Billing Record Assumptions:

  • Benefit = Senior Associate

  • Rate = 1 Year Senior (single installment)

  • Cycle Start Date = 1/1/2016

  • Number of Months = 12

  • Total Charge = $100.00

Upgrade/Downgrade Assumptions:

  • Current Join Date (Effective Date) = 3/1/2016

  • Benefit = Junior Associate

  • Rate = 1 Year Junior (single installment)

  • Price = $75.00

Sample recalculation of the original invoice detail line item for the Senior Associate membership

Calculate the Number of Months Used: 2 months

  • Current Join Date Entered for Upgrade/Downgrade = 3/1/16

  • Existing Renewal Billing Cycle Start Date = 1/1/2016

  • Calculation: Current Join Date – Cycle Start Date = Number of Months Used

  • 3/1/2016 – 1/1/2016 = 2 months

Calculate the Prorated Discount Amount per Month: $8.3333

  • Senior Associate Renewal Billing Total Amount = $100.00

  • Senior Associate Renewal Billing Number of Months = 12

  • Calculation: Total Amount/Number of Months Used = Prorated Discount

  • $100.00/12 = $8.33

Calculate the Discount Applied: $83.34

  • Senior Associate Renewal Billing Total Amount = $100.00

  • Calculated Number of Months Used = 2

  • Prorated Discount = $8.3333

  • Calculation: Total Amount – (Number of Months Used * Prorated Discount) = Discount Applied

  • $100.00 – (2*$8.33) = $83.34

Recalculated Charges for Senior Associate: $16.66

  • Total Amount = $100.00

  • Discount Applied = $83.34

  • Calculation: Total Amount – Discount Applied = Recalculated Charges

  • ($100.00 – $83.34) = $16.66

Chapter 24: Membership Renewal Billing Processes

Note

The same renewal processes found in the UX Online Renewal Manager are used for both membership and subscription renewal billing. See Chapter 28: Subscription Processing for information specific to subscriptions.

You will periodically need to run a process to renew memberships. Depending on your organization’s practices, this may be monthly or annually. Additionally, renewal billing can be run against a single customer.

You can require a membership fee based on a set dues rate or progressive dues rate, or it can be based on a voluntary or good will basis.

In any case, this process creates an open invoice and creates a new renewal billing benefit record to allow the renewal of a membership benefit. The new invoice is needed so you can send a renewal notice to your members and apply the payment when it is received.

Also part of the membership lifecycle is the periodic need to terminate memberships that are past due. This is a system-wide process that can be run at intervals based on your organization’s needs.

This chapter includes the following sections:

  • Best practices for processing membership renewal billing invoices

  • Membership renewal process overview

  • Creating new rate prices using Price Progression

  • Verifying additional benefit recipient prices

  • Printing the UX Membership Dues Renewal Edit Report

  • Creating a batch for membership renewal invoices

  • Generating membership renewal billing invoices

  • Printing the UX Membership Dues Invoice Register Report

  • Applying overpayments from current to upcoming renewal invoices

  • Membership termination overview

  • Printing the UX Membership Termination Edit Report

  • Terminating expired memberships

  • Do Not Renew Termination Utility

  • Renewal Billing Process Log

  • Renewal Billing View

  • Renewal Process Rollback Utility

Best practices for processing membership renewal billing invoices

We recommend the following as best practices for managing the process of generating membership renewal billing invoices.

  • Validate all membership benefit, rate and price settings before you generate renewal billing invoices. For more information, see Membership Renewal Setup.

  • Validate pricing for your rates. The system will select the price record where the cycle start date falls within the price record start and end date range of the rate price record. If no price record is found, the system will calculate dues = $0.00.

  • Validate pricing for additional benefit recipient products that may be related to your rates. Pricing for additional benefit recipients is based on the cycle start date. The system will select the price record where the cycle start date falls within the price record date range of the additional benefit recipient product setup. For more information, see Additional Benefit Recipient Charges.

  • Print and review carefully the UX Membership Dues Renewal Edit Report before generating the renewal billing invoices.

  • Create a separate batch for the renewal billing invoices and mark this batch closed as soon as the process is complete.

Important

Do not use this batch for any transactions other than the generate renewal billing invoices.

  • Print and review carefully the UX Membership Dues Invoice Register Report before printing any invoices.

  • Spot-check new invoices to verify that the invoices reflect the correct benefit cycle start date and pricing.

  • Post the renewal billing invoices batch as soon as possible after verifying that the invoices were generated correctly. Failure to post the batch will prevent the system from properly distributing payments to the correct GL account.

  • If you are going to apply overpayments from the current year’s dues to the upcoming renewal invoices, create a separate batch for this process. Mark this batch closed when the process is complete and post it as soon as possible after validating.

  • Disable client-specific workflows prior to generating renewal billing invoices

Important

To maintain system performance during renewal billing processing, disable client-specific workflows in your custom solution on the following entities prior to initiating the Generate Renewal Billing Invoices process. You can re-enable them after renewal processing is complete.

    • Invoice

    • Invoice Detail

    • Renewal Billing

    • Benefit Recipients

Membership renewal process overview

Your organization may manage membership on an anniversary basis, which means that an individual’s membership is valid for a specified period beginning from the month they joined. For example, if a member joins in November, a 12-month membership would expire at the end of the following October. On the other hand, your organization may manage memberships on a calendar basis, which means that your membership year is a specified period where membership begins on a specified month for all members. For example, your membership year might be July 1 through June 30. Regardless of when a member joins during the year, that membership begins on July 1 and expires on June 30, unless it is renewed.

Note

The same concepts for membership renewal processes apply to subscription renewal as well. See Subscription renewal process overview for more information.

Whether your organization manages membership on a calendar or anniversary basis, new members typically are entered into the system all throughout the year. However, how frequently you run the membership renewal process depends on whether your organization uses the calendar or anniversary method for managing membership.

  • If your organization uses the calendar renewal method, you will need to run the renewal process to generate membership renewal invoices once a year, before the end of your membership year.

  • If your organization uses the anniversary renewal method, you will need to run the renewal process each month, to generate the renewal invoices for memberships that are expiring.

  • In special circumstances, you may need to run the renewal process to generate a membership renewal invoice for a single customer.

When you launch the renewal process, you will select the Membership module, the renewal benefit, and the expiration date. If you are generating renewal for a single customer, you will also select the customer. Based on the search conditions selected in the Generate Renewal Billing Invoices window, the system then identifies eligible renewal billing records.

Eligible renewal billing records

Based on the benefit and expiration date range entered, renewal processing relies only on information in the renewal billing records where cycle state = Current, benefit status = New, Renew or Reinstated and no related renewal billing record where cycle state = Upcoming exists. Renewal billing records flagged as Do Not Renew are ignored.

Generate Renewal Billing Invoice Conditions

Allow Renewal On Unpaid

= Yes

= No

Expiration Date Entered

= Cycle Start Date + # of Months, less 1 day

= Expiration Date

Expiration Date = Pd Thru Date

Ignored

True

Benefit Status =

New, Renew, Reinstated

New, Renew, Reinstated

Expire of Last Renewal

Ignored

Is NULL or < Expiration Date Entered

Rate Next

Is not NULL

Is not NULL

Bill To

Is not NULL

Is not NULL

Cycle State

Current

Current

Do Not Renew

= False or NULL

= False or NULL

Prior Renewal Billing ID

<>Renewal Billing ID

<>Renewal Billing ID

If all conditions are met, creates new renewal billing invoice

Renewal process procedures

Your membership renewal process includes performing the following procedures, in this order:

  • Create new rate price records for the next renewal year and, if necessary, update the prices.

  • If used, validate prices on any additional benefit recipient products that are linked to your membership benefit rates. Create new price records, if needed, for the next renewal year and update the prices.

  • If membership dues are volume- or factor-based, complete routine maintenance on your account and contact records to update the pa_volume field so that the renewal invoice is calculated using the correct amount. (For more information about volume-based dues, see Setting up volume-based rates and prices. For more information about factor-based dues, see Setting up factor-based rates and prices.)

  • Create a batch for the membership renewal process. The membership renewal process requires its own batch for the renewal invoices.

  • Generate a membership edit report. You can generate the Membership Renewal Edit Report to view a list of memberships that need to be renewed.

Important

To maintain system performance during renewal billing processing, disable client-specific workflows in your custom solution on the following entities prior to initiating the Generate Renewal Billing Invoices process. You can re-enable them after renewal processing is complete.

    • Invoice

    • Invoice Detail

    • Renewal Billing

    • Benefit Recipients

  • Generate renewal billing invoices. In this procedure, you will select the membership renewal benefit you are renewing and enter the membership expiration dates you want to include in the process.

  • Verify the renewal process results.

The timing for performing this process will depend on your organization’s policy for when you need to send membership renewal notices. For example, if your policy is to give members two months’ notice that their membership is expiring, you will perform this process in January for memberships that expire on March 31st. This gives you enough time to mail them their 1st notice and any follow up notices.

Creating new rate prices using Price Progression

The dues amounts on renewal invoices are managed prices in the rate setup associated with the renewal benefit. If your dues are changing, you can use the Price Progression utility to create new price records, without altering existing pricing. This utility creates the new price records for you, eliminating the need for you to create each price item manually.

Important Note

Do no run the utility for the same date ranges more than one time. UX does not check for duplicates and will create another set of prices records if you run the utility a second time for the same date range.

To create the new price records, this utility runs a series of processes:

  • It searches for all price items within the selected benefit that either match or fall within the date range that you specify. In other words, any price records that have a start date equal to or greater than the start date you enter, and an end date that is equal to or less than the end date you enter will be included.

  • It creates new price records that are copies of the existing price records in the date range you specified.

  • It sets the start date for each new price record by adding one day to the end date of the original price record. For instance, if the original price record has an end date of 12/31/2016, the start date for the new price record will be 01/01/2017. This prevents any gaps in the effective dates of the existing price record and the new price record.

  • It sets the end date for each new price record so it is effective for at least the same number of days as the existing price record and falls on the last day of the month. For instance, assume that the existing price record start and end dates are 01/01/2016 and 12/31/2016. There are 365 days between these two dates. To set the end date for the new price record, the system adds 365 to 01/01/2017 to arrive at a calculated end date of 12/31/2017. To ensure that the new end date falls on the last day of the month, the system looks to the 1st of the following month, in this case, 01/01/2018, subtracts one day, and assigns 12/31/2017 as the end date for the new price record. (This calculation accommodates potential variations in the number of days, such as leap years.)

Caution

If the end date in the original price record does not fall on the last day of the month, the system calculation to create the new end date may alter the number of days between the start and end dates in the new price record. For example, if the original start and end dates are 01/01/2016 and 12/15/2016, the new start date will be 12/16/2016 and the new end date will be 11/30/2017. The best practice is to keep the start dates at the beginning of a month and the end dates at the end of a month.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Billing Settings > Step Three: Renewal Benefit to open the List View of benefits in a new window. In the Benefit list, locate and open the benefit record where you want to update prices.

Before running the utility, review each rate and its price records and note the following information:

  • Start and end dates: You will specify the date range to search for existing price records, so take note of the start and end dates for the price records in each rate that you want to duplicate. Also, note the number of price records in those date ranges.

  • Rate default price: All new price records will inherit the default price for the rate, whether the price record is created by the system or by you manually.

    • If the new price applies to all new price records, consider updating the rate default price before running the utility. The system will not alter the price in the existing price records, but the new price records will inherit the new default price from the rate and you will not need to edit the price in each new price record.

    • If the new price does not apply to all new price records, do not alter the default rate price. The system will create the new price records and you can change the price records that need the new price.

Click the Price Progression Utility button on the Record toolbar.

In the Price Progression Utility dialog, enter the start and end date range that will include the price records you want to copy and click OK.

The system will search for all price items within the selected benefit that fall within the date range you entered. The Price Progression Utility dialog will display the number of price records found in the search. 

If the number of price records found is correct, click OK. The system will automatically create the new price records. For example, the following table shows the result of running the Price Progression utility where the search start date is 01/01/2008 and the search end date is 12/31/2009.

Name

Rate

Price

Start & End Date

Minimum – Maximum

Existing price records

Member

Quarterly Install – Volume

$200.00

01/01/2008 – 12/15/2009

1.00 –

999.00

Non-Member

Quarterly Install – Volume

$200.00

01/01/2008 – 12/15/2009

1.00 –

999.00

Member

Quarterly Install – Volume

$500.00

01/01/2008 – 12/15/2009

1,000.00 –

10,000.00

Non-Member

Quarterly Install – Volume

$500.00

01/01/2008 – 12/15/2009

1,000.00 – 10,000.00

New price records

Member

Quarterly Install – Volume

$200.00

12/16/2009 – 11/30/2009

1.00 –

999.00

Non-Member

Quarterly Install – Volume

$200.00

12/16/2009 – 11/30/2009

1.00 –

999.00

Member

Quarterly Install – Volume

$500.00

12/16/2009 – 11/30/2009

1,000.00 –

10,000.00

Non-Member

Quarterly Install – Volume

$500.00

12/16/2009 –

11/30/2009

1,000.00 – 10,000.00

If you did not modify the default price in the rate, you will need to update the price in the new price records as needed. In the Benefit list, open the benefit where you you need to modify the rate.

Click Rate in the Navigation Pane to open the Rate list. In the Rate list, locate and open the rate you need to modify.

Click Prices in the Navigation Pane to open the Prices list. In the Prices list, locate and open the new price record you need to modify.

Enter the new price in the Price/Percent of List Price field. Click Save & Close.

Repeat steps as required.

Verifying additional benefit recipient prices

If used, then validate prices on any additional benefit recipient products that are linked to your membership benefit rates. See Additional Benefit Recipient Charges for more information.

After you have created new price records needed for the next renewal cycle, and if appropriate, verified pricing for additional benefit recipients, you can continue with the next step of preparing to run the Generate Renewal Billing Invoices process, Printing the UX Membership Dues Renewal Edit Report.

Printing the UX Membership Dues Renewal Edit Report

Before you generate renewal billing invoices, we recommend that you generate the Print the UX Membership Dues Renewal Edit Report for Accounts and Contacts to view a list of all accounts and contacts subject to membership renewal, based on expiration date and renewal benefit. This report is designed to give you a snap shot of all the records that will be updated with a new renewal billing invoice for the upcoming renewal cycle. The data selections you make when you generate this report should match the data selections you will make when you generate renewal billing invoices.

Note

Based on the benefit and expiration date range entered, renewal processing relies only on information in the renewal billing records where Cycle State = Current, benefit status = New, Renew, or Reinstated, and no related renewal billing record where cycle state = Upcoming exists. Renewal billing records flagged as Do Not Renew will be ignored.

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online reports. Open the UX Membership Dues Renewal Edit Report for Accounts and Contacts report.

Select a benefit if you are running the renewal process on selected membership benefits. The selections you make for this report should match the selections you make when you generate renewal invoices.

Do not select a rate if you are preparing for the renewal process. This field is included for reference only if you want to view your data by rate; however, if you use this option for the renewal process, the number of records on the report will not match the number of records selected during the process of generating renewal billing invoices.

Add the following report filtering criteria:

  • Benefit Status equals New; Renew; Reinstated

  • Expiration Date on [enter or select the expiration date]

Click Run Report. The report will appear on your monitor. You can view the report online, send it to your printer, or export it as a PDF file.

Use this report to verify counts, as well as the current rates and next rates assigned to each record. (Every record must have a rate next.) Also, check to verify there is a Bill To entry for each record. After reviewing this report, make any account or contact record changes, if appropriate. If you make any changes, run the report again to revalidate the records prior to generating renewal billing invoices.

Review this report to verify that the data for the records selected is correct. If you see any errors, access those records and correct them prior to running the Generate Renewal Billing Invoices process.

Important

Dues proration will have an impact on how the deferred dues revenue is recognized. Therefore, when you select the rates to use for a new member’s first dues invoice and for their subsequent renewal invoices, you must follow the guidelines in Calendar-based dues prorate guidelines.

Verify your Rate Next settings on the report. If these rules are not followed, the deferral will not be calculated correctly:

  • If the calendar-based renewal benefit is prorated in “Current Cycle,” the member may renew with a multi-installment rate as the Rate Next.

  • If the calendar-based renewal benefit is prorated in “Next Cycle,” the member may only renew with a single installment rate where the number of months is 12 as the Rate Next.

Creating a batch for membership renewal invoices

Before you can perform the membership renewal process in UX Online, you must create a batch for the renewal transactions. A batch is a control mechanism that assigns an ID and date to every transaction entered into the system. The membership renewal process requires its own separate batch.

You should create batches that meet the requirements of your organization’s policies and procedures regarding the entry of cash, check, or credit card payments. For more information about batches, see Integration with General Ledger. For more information about creating batches, see Creating a batch in UX Online.

Note

If you do not have rights to access the Batch Log area, communicate with the appropriate people within your organization to have this done. You can set up alerts in CRM to remind yourself and others that this needs to be done.

Generating membership renewal billing invoices

When you launch the Generate Renewal Billing Invoices process to create membership renewal billing invoices, you will select the membership renewal benefit you are renewing and enter the membership expiration date you want to include in the process. The system will create an invoice and a new renewal billing record for this renewal cycle for eligible renewal billing records that meet your search criteria.

If your organization’s membership rates include a prescribed number of benefit recipients, and you have members with benefit recipients that exceed that number, the Generate Renewal Billing Invoices process will automatically calculate the additional charges in the system-created renewal invoice.

Note

Please see Membership renewal process overview for eligible renewal billing record conditions.

Based on the benefit and expiration date range entered, renewal processing relies only on information in the renewal billing records where cycle state = Current, benefit status = New, Renew or Reinstated, and no related renewal billing record where cycle state = Upcoming exists. Renewal billing records flagged as Do Not Renew will be ignored.

See About renewal benefit sequencing for important information on how UX Online relies on the Sequence number during renewal processing.

Important

To maintain system performance during renewal billing processing, disable client-specific workflows in your custom solution on the following entities prior to initiating the Generate Renewal Billing Invoices process. You can re-enable them after renewal processing is complete.

    • Invoice

    • Invoice Detail

    • Renewal Billing

    • Benefit Recipients

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Manager > Generate Renewal Billing Invoices. The Generate Renewal Invoices dialog appears.

Enter the appropriate renewal information:

  • Expire Date – Click the Calendar button and select the expiration date that is up for renewal. This date will always be the last day of the month. The date you enter must match the date you entered when you created the UX Membership Dues Renewal Edit Report for Accounts and Contacts. This is required.

  • Batch – Click the Lookup button to select the batch you created for this process. This is required.

  • Module – Click the Lookup button and select Membership. This is optional.

Important

If you do not select a module, you will be able to select benefits from both Membership and Subscription modules.

  • Benefit – Click the Lookup button to select the membership benefit you are running the renewal process for. You can select more than one benefit if you want to. To do so, press and hold the Ctrl key while clicking the benefits. This is optional.

Important

If you do not select a benefit, the system will run the renewal process on all renewal benefits within the selected module. If no module was selected, the system will run the renewal process on all eligible membership and subscription renewal billing records for the selected Expiration Date.

  • Customer – If you are generating a renewal invoice for a single customer, click the Lookup button to select the customer you are running the renewal process for. This is optional.

Click OK to start the process. A message will appear displaying the number of renewal billing records found that meet the search criteria you entered and meet the conditions for eligible renewal billing records described earlier. Verify that this number matches the number of records shown on the UX Membership Dues Renewal Edit Report for Accounts and Contacts.

If the numbers match, click OK to initiate the process.

Important

Please note that this process may take several minutes to complete if there is a large number of invoices to be generated. After you click the OK button, allow the system several minutes to generate the invoices. Do not attempt to re-run the process.

You can check the status of the process in the Renewal Process Log (Membership work area > Membership/Subscriptions > Renewal Manager > Renewal Process Log), which displays a list of renewal billing processes that have been run or are currently in process.

Print the UX Membership Dues Invoice Register Report to make sure the invoices were created properly. For more information, see Printing the UX Membership Dues Invoice Register Report.

Printing the UX Membership Dues Invoice Register Report

You can review the membership renewal invoices by generating the UX Membership Dues Invoice Register Report, entering the same membership benefit and date range, and comparing it to the UX Membership Dues Renewal Edit Report you generated prior to generating the renewal invoices. The reports should match, except the UX Membership Dues Invoice Register Report will show a balance due amount. For more information, see Printing the UX Membership Dues Renewal Edit Report.

Note

Be sure the renewal billing invoices process is complete before generating this report. You can check the status of the process in the Renewal Process Log; for more information see Renewal Billing Process Log.

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online report. Open the UX Membership Dues Invoice Register Report in the Reports list.

Enter the range of expiration dates for the renewal processes you want to include on this report. This should be the same date that used to run the UX Member Dues Renewal Edit Report and the same date you used for generating the renewal billing invoices.

Click Run Report. The report will appear on your monitor. You can view the report online, send it to your printer, or export it as a PDF file.

Use this report to verify the counts against the count in the Renewal Edit Report and the count in the Generate Renewal Billing Invoices process. Also, verify counts against the number of records processed in the Renewal Process Log.

If all of your invoices are correct, to maintain the integrity of your generate renewal billing invoice transactions, close your renewal billing batch so that no other transactions can be entered in this batch.

About renewal benefit sequencing during renewal processing

The Sequence number assigned in the renewal benefit setup defines the order in which the UX renewal billing process for membership, chapter and subscription renewals are processed. Sequence numbers do not need to be unique, but they should define the order in which one or more renewal benefits is processed during the Generate Renewal Billing Invoices process. The process runs on renewal benefits with Sequence number = 0 (or NULL) first, followed sequentially by benefits where the Sequence number is 1, 2, 3, 4, 5, etc.

If your organization runs the Generate Renewal Billing Invoices process on more than one benefit at a time (i.e., by module or by expiration date), and benefits are flagged Group Invoice = Yes, UX will create and group invoice detail line items for eligible renewal billing records into a single renewal invoice. The Sequence number in the benefit setup will define the order that UX processes those renewal benefits. Benefits with the lowest Sequence number will be processed first, followed by benefits with a higher Sequence number.

When benefits with the same Sequence number are grouped in a single invoice, the process is entirely random. This would occur, for example, if a primary membership benefit Sequence number = 0 (or NULL) and a chapter benefit Sequence number = 0 (or NULL), and these benefits are flagged to Group Invoices. When the Sequence numbers are the same, there is no hierarchy.

Applying overpayments from current to upcoming renewal invoices

If members have overpaid their membership dues in the current dues year, you can automatically transfer their credit balances, which are held in the unapplied deposits GL account, from the current year’s renewal invoice to the newly created upcoming renewal invoice.

Caution

You will not be able to run the Renewal Rollback Utility on renewal billing invoices that contain payment transactions transferred from the current year’s invoice to the newly created upcoming renewal invoice.

Note

If subscribers have overpaid their subscription renewal invoice in the current renewal year, the Renewal Overpayment Process will transfer those overpayments from the current subscription renewal invoice to a newly created upcoming subscription renewal invoice.

The Renewal Overpayment Process uses the Transfer Payments payment type to transfer the credit balance out of the current year’s invoice into the upcoming renewal invoice for both membership and subscriptions. (For more information about the Transfer Product payment type, see Payment and adjustment products overview). See, also Defining a default payment transfer product.

Note

You must run this process after you run and validate the Generate Renewal Billing Invoice process. If your organization does not maintain credit balances on renewal invoices, do not perform this procedure. Also, be sure that the batch containing the renewal billing invoices and all batches containing renewal billing invoice payments are closed and posted before you perform this procedure.

Important

You must create a separate batch for the transactions created by this procedure. For more information about creating a batch, see Creating a batch in UX Online.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Manager > Renewal Overpayment Process.

The Renewal Overpayment Process dialog appears, displaying the number of current renewal invoices having credit balances that will be included in this process.

If there are invoices with money to transfer, verify the count against the Renewal Edit report. If there are no invoices with money to transfer, then you do not need to continue this process. Click Cancel. If the count is correct, click the Lookup button to select the batch to be used for this process. Click OK to begin the process.

After the process has completed, it is recommended that you print the Transaction Edit report and the Membership Dues Invoice Register report to verify that the overpayments process ran correctly. You can use the Renewal Process Log (Membership work area > Membership/Subscriptions > Renewal Manager > Renewal Process Log) to verify that the process has completed.

  • Transaction Edit Report – Check the payments column in this report to verify the payments that were applied.

  • UX Membership Dues Invoice Register Report – Check the payments column in this report to verify the payments that were applied.

If all of your invoices are correct, close your overpayment process batch so that no other transactions can be entered in this batch. (This helps maintain the integrity of your overpayment process transactions.) For more information about closing and posting batches, see Integration with General Ledger.

Membership termination overview

Note

The Renewal Billing Termination Process for terminating expired memberships also applies to terminating expired subscriptions. To filter the process for membership only, select Module = Membership. For more information, see Subscription termination overview.

Terminating current renewal billing records for past due members using the Renewal Billing Termination Process should be part of your membership maintenance procedures. The frequency depends on your business rules and your membership renewal method – anniversary or calendar. This process terminates current memberships that have a common past-due paid through date, all at one time.

Important Note

UX Online identifies eligible renewal billing records where the cycle state = Current using the search criteria that you enter to initiate the process. It will not terminate renewal billing records where the cycle state <> Current.

If your membership renewal benefits use the Calendar renewal method, you will run this process annually. If they use the Anniversary renewal method, you will run this process monthly.

You can perform this process before or after the membership renewal process, since members who are past due will not be included in the current dues renewal process.

The membership termination process includes performing the following procedures, in this order:

  • Generate the UX Membership Termination Report. This report shows a list of members whose memberships need to be terminated.

  • Terminate memberships. In this procedure, you will select the membership renewal benefit you are terminating, and enter the membership paid through date you want to include in the process.

  • Verify the termination process results.

Note

You can set up alerts within CRM to remind yourself and others when this process should be run.

Membership records eligible for termination

The UX Online Renewal Billing Termination Process uses the following renewal billing record criteria to identify membership records that will be selected for termination:

Benefit Status

New, Renew, Reinstated

Cycle State

Equals Current

Do Not Renew

Does Not Equal True

State Code (Status)

Active

Module

Equals <optional prompt – select Membership

Benefit

Equals <optional prompt>

Paid Through Date

Equals <required prompt>

Certification ID

NULL

Printing the UX Membership Termination Edit Report

Before you run the renewal billing termination process for your members, we recommend that you generate and review the UX Membership Termination Edit Report. This report shows all memberships that need to be terminated because they have expired. This report is designed to give you a snap shot of all the records that will be updated with a new benefit status, termination date, termination reason, price level, and member flag. The selection criteria for this report match the data selection criteria for running the Renewal Billing Termination Process.

Review this report to verify that the data for the records selected is correct. If you see any errors, open those records and correct them before terminating expired memberships.

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online report. Open the UX Membership Termination Edit Report in the Reports list.

Enter the date range for this report in the Paid Thru Date On or After and Paid Thru Date On or Before fields. This will be the range of expiration dates you are preparing to perform the membership termination process for. For example, to generate this report for memberships expiring in March 2009, enter the dates 03/01/2009 and 03/31/2009.

Note

The Paid Through Date will equal the Expiration Date if the invoice is paid in full.

Select the membership renewal benefit you are running this report for.

Click Run Report. The report will appear on your monitor. You can view the report online, print it, or save it as a PDF file if needed.

Use this report to verify the count of the memberships you will be terminating. Make any account or contact record changes, if appropriate. If you make any changes, run the report again to revalidate the records.

Terminating expired memberships

Note

The Renewal Billing Termination Process for terminating expired memberships also applies to terminating expired subscriptions. To filter the process for membership only, select Module = Membership. For more information, see Subscription termination overview.

When you terminate memberships, you will select the membership module, the membership renewal benefit you are terminating, and enter the Paid Through date you want to include in the process. The timing for performing this process will depend on your organization’s policy for when you need to terminate membership.

When you perform this procedure, the system searches for eligible renewal billing records that match your entries, confirms the number of those records, and then processes the termination of those memberships. For more information on eligible records, see Membership records eligible for termination.

We recommend that you generate the UX Membership Termination Report before performing this procedure. This report shows all members whose memberships need to be terminated because it has expired. You can use the total number of memberships to terminate on this report to verify that the correct number of memberships will be terminated by this process. For more information, see Printing the UX Membership Termination Edit Report.

After reviewing the UX Membership Termination Report to verify that the correct records will be terminated, continue with the following procedure:

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Manager > Renewal Billing Termination Process. The Termination Process dialog appears.

In the Termination Process dialog, enter the appropriate termination information.

  • Paid Thru Date – Click the Calendar button and select the expiration date of the memberships you want to terminate. This date will always be the last day of the month you are running this for.

  • Module – Click the Lookup button and select Membership.

Important

If you do not select a module, the system will run the termination process on both the membership and subscription modules. Certification renewal billing records are specifically excluded from this process.

  • Benefit – Click the Lookup button to select the membership renewal benefit you are running this termination process for.

Important

A module is required to select a benefit. If you do not select a benefit, the system will run the termination process on all renewal benefits within the selected module. If no module or benefit is selected, the system will run the termination process on all membership and subscription benefits. Certification renewal billing records are specifically excluded from this process.

  • Reason – Select a termination reason from the menu. This reason will be recorded on the renewal billing record.

Note

The Termination Reason list can be modified in your client-specific solution package to add additional reasons reflecting your organization’s reasons by your system administrator. Do not delete or edit existing Termination Reason option set values. Because a Termination Reason field exists in both the Renewal Billing entity and in the Renewal Process entity, you must add the client-specific option to the Termination Reason field in both entities. Contact your Protech account manager for guidance on the recommended framework for core entity customization of Termination Reason option set fields.

Click OK to start the process. A message will appear displaying the number of memberships that will be terminated. Verify that this number matches the number of terminations shown on the UX Membership Termination Report.

If the numbers do not match, click Cancel to stop the process. Resolve the discrepancy before proceeding with the process. If the numbers match, click OK to continue.

Note

If there are many membership records to be terminated, UX Online will display a green progress bar while the process is running.

When UX Online terminates the records, it updates the following records:

  • Renewal Billing Record Benefit status = Terminated

  • Renewal Billing Record Termination date = system date

  • Renewal Billing Record termination reason = selected reason

  • If the renewal benefit was flagged as Primary, Account/Contact Price Level = Non-member

  • If the renewal benefit was flagged as Primary, the Account/Contact Member Flag = No

Note

If the renewal benefit was not flagged as Primary, the account/contact price level or member flag will not be changed; you must make this change manually.

When the process is finished, we recommend that you print the UX Membership Termination Report again to make sure the memberships were terminated properly. You can use the Renewal Process Log (Membership work area > Membership/Subscriptions > Renewal Manager > Renewal Process Log) to verify that the process has completed.

Do Not Renew Termination Utility

This utility is a system job included in the UX Online Renewal Billing Nightly Process that runs in the background – it is not initiated from the Renewal Manager. It identifies active membership and subscription renewal billing records flagged as Do No Renew where the system date is greater than or equal to the calculated date of the Renewal Billing Cycle Start Date + the Number of Months defined in the Renewal Billing record. The utility terminates those records, regardless of benefit status.

For example, assume you have an active membership renewal billing record with a Cycle Start Date = 10/1/2016. The number of months defined in the renewal billing record = 12 and Do Not Renew = True. On 10/1/2017, the system job will update the following renewal billing record fields:

  • Benefit status > Terminated

  • Termination date > system date (in this example, 10/1/2017)

  • Termination reason > Other

Renewal Billing Process Log

The Renewal Billing Process Log provides a view of all renewal billing processes that have been run or are currently being run. This includes renewal billing for membership, subscriptions, and professional development, overpayment processing, and termination processing. The grid view identifies the date the process was run, the type of process, the renewal benefit, the expiration/paid thru date, the status, the batch number, the number of transactions processed upon completion, and the user who ran the process. This gives a quick overview of the status of all renewal billing processes, as well as a log of all renewal processes that have been run.

Each time you initiate one of the renewal billing processes, the system will create a new record in this grid.

To view this list, in the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Manager > Renewal Process Log. The Renewal Process Log list includes the following columns:

  • Process Type – Displays the specific renewal process that was run

  • Module – Displays the UX Online module selected for the selected process. If no module was selected, this field will be blank.

  • Benefit Name – Displays the name of the benefit selected for the specific process. If no process was selected, this field will be blank.

  • Expiration Date – Displays the expiration date you entered to generate renewal billing invoices or the paid thru date you entered to terminate renewal billing. For all other process, this field will be blank.

  • Batch No – Displays the batch number used to run the process. If no batch was required, this field will be blank.

  • Batch Date – Display the batch date of the batch used to run the process. If no batch was required, this field will be blank.

  • Process Status – Displays the status of the process. If the process has finished running for all selected records, the status will be Completed. If the process is still running on the selected records, the status will be Running.

  • Total Processes – Displays the total number of records captured in the completed process. This number should match the number of records identified at the beginning of the process in the confirmation web dialog page and the number of records identified in the edit reports you ran before initiating the process.

  • Created By – Displays the user who ran the process.

Renewal Billing View

  • The Renewal Billing View provides a list view of all renewal billing records, including membership, subscriptions, and professional development. You can sort the records by column headings, which include benefit, rate, benefit status, cycle state, cycle year, invoice, benefit product, Customer Account and Customer Contact.

  • Select and double-click any record line to open the renewal billing record. Single-click the available hyperlink within the column data for benefit, rate, invoice, benefit product, Customer Account or Customer Contact for direct access to that data.

  • Select Export to Excel on the List View toolbar to export the records to an Excel worksheet.

  • Narrow the records displayed by selecting from the list of alternate System Views or My Views. My Views are any Advanced Find queries on renewal billing records that you have saved or queries that others have shared with you.

Renewal Process Rollback Utility

The Renewal Process Rollback utility can be used if a Membership or Subscription renewal process was run in error and needs to be reversed. Professional Development renewals are not eligible for rollback.

Based on the renewal process you select for rollback, the utility will identify and delete eligible upcoming renewal billing records and related invoices that were created by the system during the original renewal process. It will reverse system updates to the existing current renewal billing record so that it is eligible for renewal processing following the rollback.

Important

Only users with System Administrator rights can run the utility.

Protech recommends that you run a backup prior to running this utility.

You are responsible for managing any accounting implications resulting form running the rollback.

This utility runs without regard to the condition of the original batch that was used for the Generate Renewal Billing Invoices process (open/closed, GL Detail created, or Posted to Accounting).

This utility ignores renewals where a payment/adjustment transaction exists in the renewal invoice, including transfer payments processed through the Overpayment Process utility. These renewals are not eligible for rollback.

For renewal invoices containing other transactions (i.e., product sales), instead of deleting the invoice, this utility will delete only the invoice detail line item(s) for renewal (invoice detail containing a prior Renewal Billing ID) and delete the related upcoming renewal billing record. It will not update the invoice name after deleting the invoice detail line item.

Invoice detail created by the renewal billing process for Additional Benefit Recipient charges is included in the rollback. While the underlying product for the Additional Benefit Recipient is a sales non-inventory product, if it is included in the rate setup, these charges are included in the rollback.

For records that are rolled back, this utility updates the existing renewal billing record (Cycle State = Current) by returning the value in the Expire Date of Last Renewal field to NULL so that the renewal billing record is eligible for renewal processing after the rollback.

The length of time required depends on the number of records affected.

Best practices before running the rollback utility

  • Create a backup.

  • Prepare for managing the accounting implications of running utility, such as determining whether GL detail was created for the original renewal process batch. If GL detail was created in the original renewal process batch, was it posted to the accounting system?

    • If the batch was posted, what steps are required to correct (reverse) the journal entries in the accounting system where the batch was posted, and then re-create GL detail and re-post the batch after running the utility?

    • If the batch was not posted to the accounting system, what steps are required to re-create GL detail after running the utility?

  • Resolve the underlying problem that prompted the rollback. For example, if the rate prices were not updated before the renewal process was run, update the end date on existing price records and create new rate price records with the new amount and start date so that you can re-generate renewal billing with the corrected pricing after the rollback.

  • Document the steps for managing any records that are not rolled back because a payment transaction exists in the related renewal invoice. For example, if renewals are being rolled back because the rate amount was wrong at the time the renewals were generated, you will need to:

    • Update the end date on existing price records in the rate setup and create new price records for the new amount and start date in the rate setup.

    • Identify the renewal invoice detail line items/invoices that were not rolled back.

    • Working in a distinct batch, open each renewal invoice detail line. Use the Rate lookup and re-select the same rate. This will update the pricing in the benefit entry form. Then, select the Re-calculate Invoice button to update the invoice totals.

Best practices after running the rollback utility

  • Validate the rollback process and identify records that were not rolled back. See Validating the Rollback for more information.

  • Complete documented steps identified prior to running the utility for managing records that were not rolled back.

  • Manage accounting implications, if any, identified prior to running the utility.

Rolling back renewals

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Manager > Renewal Rollback Process to open the Renewal Rollback Process webpage dialog.

Use the lookup button in the Select Renewal Process field to select the renewal process that you want to roll back. This lookup displays a list of all renewal billing processes found in the Renewal Process Log, by the expiration date and batch used during the original Generate Renewal Billing Invoices process.

After selecting the renewal process that you want to roll back, click OK to continue. Allow the system to complete processing. Depending on the number of records, the process may take less than a minute or it could take well over an hour.

When the process is complete, the system creates a “Renewal Process Rollback” record in the Renewal Process Log, indicating the status (Process Status) and the number of records processed (Total Processes).

Validating the rollback

You can validate the number of renewal billing records that were processed by comparing the Total Processes for the original renewal process to the Total Processes for renewal process rollback in the Renewal Process Log. If the numbers match, all renewal billing records were rolled back and their related invoices deleted. If the numbers do not match, then some renewal records were not eligible for rollback and should be examined individually.

To identify renewal billing records that were not rolled back, you can create an Advanced Find or search on Invoice Details, as described below.

  • Create an Advanced Find query on renewal billing records using the same search criteria that was used for the initial renewal process (benefit and expiration date), plus a search where Expire Date of Last Renewal contains data.

Note

The benefit and expiration date of your original process is referenced on the record in the Renewal Process Log. The search results will return renewal billing records that were not rolled back during the rollback process.

  • Assuming you used a unique batch for the original renewal process, you can identify renewal invoice detail line items (and invoice number) that were not deleted during the rollback process by conducting a search in the Invoice Details view. From any UX work area in the Navigation Tile Bar, select Invoice Details. This view opens in a new window. Search for records using the batch number of the original renewal process. The search results will return any that were not rolled back.

Chapters

Part 5: Chapters

This part of the documentation describes the procedures you will use to manage your organization’s chapters.

This information is divided into the following chapters:

  • Chapter 25: Chapter Manager

  • Chapter 26: Chapter Reimbursement Processing

Chapter 25: Chapter Manager

You can use UX Online to set up and manage your organization’s chapters, chapter officers, regions, and region officers. When you have your chapters set up in UX Online, you can easily keep track of chapter officers and communicate with chapter officers via e-mail. By using regions, you can easily group chapters by a region, track region officers, and communicate with region officers via e-mail.

When you set up chapters in UX Online, you can also set up ZIP code cross-reference records that the system can use to automatically assign chapter territories to account and contact records. If you make changes to your ZIP code cross-reference records, you can update your account and contact records with the new information.

Although you must set up chapters if you want to use renewal benefits to manage chapter membership, membership in a chapter is not managed through the Chapter Manager. Accounts and contacts that are members of a chapter are managed through renewal billing. See Membership Renewal Setup for information on renewal setup, renewal billing transactions, and renewal billing processes.

If your organization groups chapters by region, Protech recommends that you create regions before you create your chapters so that you can assign the region to the chapter during setup.

This information includes the following topics:

  • Creating a region

  • Setting up a region officer

  • Creating a chapter

  • Setting up a chapter officer

  • Automatically assigning chapter territories

  • Creating a chapter territory ZIP code cross-reference

  • Overriding automatic chapter territory assignments

  • Updating members chapter territory

Creating a region

You can use regions to group chapters that share common characteristics, based upon your organizations requirements. By using regions, you can easily keep track of region officers, their titles, and their terms. If you create regions and assign chapters to them, you can create reports for specific chapter regions, or perform queries on those regions. (Creating and using regions is optional.)

If your organization groups chapters by region, Protech recommends that you create regions before you create your chapters so that you can assign the region to the chapter during setup.

In the Navigation Tile Bar, select the Membership work area > Chapters > Chapter and Region Settings > Regions Setup to open the List View of active regions. This list opens in a new window.

Click New on the List View toolbar to create a new region. In the General section of the Region record, enter the general region setup information:

  • Name – Enter the name of the region – for example, Mid-Atlantic.

  • Owner – Displays the user ID of the user who created this record.

Click Save. After saving this record, other options in the record Navigation Pane are activated:

  • Click Chapter to view all chapters related to this region. For more information, see Creating a chapter.

  • Click Region Officer to view all officers related to this region. For more information, see Setting up a region officer.

Save & Close to save this record and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Setting up a region officer

Follow this procedure to set up an officer for a region, assign a term of office and title.

Note

You can also set up a region officer from within a contact record by selecting Region Officer from the Navigation Pane in the contact record.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Chapter and Region Settings > Regions Setup to open the List View of active regions. This list opens in a new window.

Open the region you where you want to add an officer. In the Navigation Pane of the region record, click Region Officer to view a list of existing region officers. Click Add New Region Officer on the List View toolbar.

In the General section of the Region Officer record, enter the general region officer setup information:

  • Contact – Click the Lookup button to select the contact.

  • Title – Click the Lookup button to select the position or title of the region officer, if appropriate. For additional information, see Setting up titles.

  • Name – The name of the region appears by default based upon the region selected in the region field.

  • Region – The name of the region for which you are creating an officer appears by default.

  • Term Start – Enter the beginning date of the region officer’s term in MM/DD/YYYY format, or click the Calendar button to select the date. Note: If the term begins in the future, we recommend that you select Nominee as the Officer Status.

  • Term End – Enter the ending date of the region officer’s term in MM/DD/YYYY format, or click the Calendar button to select the date.

  • Officer Status – Select the status of the officer: Current, if you are adding a current officer; Nominee, if the officer has been nominated, or if they have been elected but their term has not started yet; or Past, if this officer’s terms has expired.

Note

There is no systematic update of Officer Status based on the term start and end dates. This requires manual maintenance.

Owner – Displays the user ID of the user who created this record.

Click Save & Close to save this record and return to the list of region officer records. Click the region name in the Top Navigation Toolbar to return to the region record. Save & Close the region record to return the list of region records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Creating a chapter

Follow this procedure to create a chapter.

Important Note

You should never delete a chapter record. If a chapter record is no longer active, de-activate the chapter.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Chapter and Region Settings > Chapter Setup to open the List View of active chapters. This list opens in a new window.

In the General section, enter the general chapter setup information:

  • Name – Enter a descriptive name for the chapter (for example, Maryland State Chapter).

  • Chapter Code – Enter an abbreviation for the chapter you are creating. For example, if you only have state chapters, enter the state abbreviation. If you have local chapters, enter an abbreviation using a consistent naming convention for easy lookup.

  • Chapter Type – Select a chapter type for this chapter, if appropriate: State or Local. You should not set up more than one chapter with the same chapter code and chapter type.

  • Region – If appropriate, click the Lookup button to select the region for this chapter.

  • Account – This field is optional. You may use this field to link the chapter to a corresponding chapter account record. When you link a chapter to an account record, you can track UX Online transactions and other information specific to the chapter account record. For example, if you sell products to a chapter, these transactions can only be recorded in the chapter account record, not in the chapter record. Click the Lookup button to select an account record for this chapter, if appropriate.

  • Accounting System Vendor Number – Enter the Vendor ID from the Great Plains accounting system to support accounts payable for chapter reimbursement, if appropriate. See Chapter Reimbursement Processing.

The Web section is used with Protech’s MX Online and SX Online and will be set as needed during those implementations. Do not change these settings. The following fields are available:

  • Publish to Web – Defaults to No.

  • SP site created – Populated by the system when the Chapter SharePoint site is created. Do not modify this field.

  • SP site URL – Populated by the system when the Chapter SharePoint site is created. Do not modify this field.

Click Save. After saving this record, other options in the record Navigation Pane are activated: Activities, History, Chapter Officers, Contacts, and Accounts.

  • Click Chapter Officers to view all chapters officers related to this chapter. For more information, see Setting up a chapter officer.

  • Click Contacts to view a list of all contact records where this chapter is the assigned Chapter Territory.

  • Click Accounts to view a list of account records where this chapter is the assigned Chapter Territory.

Click Save & Close to save this record and return to the list of chapter records.

Setting up a chapter officer

Follow this procedure to set up a chapter officer and assign a term of office and title.

Note

You can also create a chapter officer from within a contact record by selecting Chapter Officers from the Navigation Pane in the contact record.

In the Navigation Pane of the chapter record, click Chapter Officers to open a List View of chapter officer record. Click Add New Chapter Officer on the List View toolbar.

In the General section, enter the general chapter officer setup information:

  • Contact – Click the Lookup button to select the contact and click OK.

  • Title – Click the Lookup button to select the position or title of the chapter officer, if appropriate. For additional information, see Setting up titles.

  • Term Start – Enter the beginning date of the chapter officer’s term in MM/DD/YYYY format, or click the Calendar button to select the date.

  • Term End – Enter the ending date of the region officer’s term in MM/DD/YYYY format, or click the Calendar button to select the date.

  • Chapter – The name of the chapter for which you are creating an officer appears by default.

  • Officer Status – Populated by the system upon Save and updated daily by the nightly system job based on term start and end dates.

  • Description – Enter a description for the chapter officer.

Click Save & Close to save this record and return to the list of chapter office records. Click the chapter record name on the Top Navigation Toolbar to return to the chapter record. Save & Close the chapter record to return to the list of chapter records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Automatically assigning chapter territories

In UX Online, you can assign a chapter territory to an account or contact record. If you set up ZIP code cross-reference records, the system will automatically enter the appropriate chapter in the Chapter Territory field, based on the ZIP code, state, or country entered for the account’s or contact’s primary address. (ZIP code cross-reference records establish the relationship between a ZIP code or range of ZIP codes, state, or country, and a chapter. For more information, see Creating a chapter territory ZIP code cross-reference.)

You can choose to override the automatic chapter territory assignment for individual contact or account records by marking Yes on the Override Chapter Territory option on the General tab of the account or contact record. If you override automatic chapter territory assignment for an account or contact, you can select a different chapter territory, and the system will not automatically change it when you change the primary address ZIP code, state, or country in the record.

If you do not override automatic chapter territory assignment for an account or contact, each time you change the ZIP code, state, or country in the primary address and save the record, the system will automatically update the chapter territory when you save the record, using the appropriate ZIP code cross-reference. For more information, see Overriding automatic chapter territory assignments.

Creating a chapter territory ZIP code cross-reference

Territory ZIP code cross-reference records establish the relationship between a ZIP code (or range of ZIP codes), state, or country, and a chapter to create a chapter territory. These cross-reference records are used to assign the correct chapter territory to an account or contact record automatically.

Note

If you change an existing ZIP code cross-reference record, it will not automatically update the chapter territory on existing account or contact records. If you change an existing ZIP code cross-reference record, use the Update Member Chapter Territory utility to update existing account and contact records. For more information on updating the chapter territory in account and contact records, see Updating members chapter territory.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Chapter and Region Settings > Territory ZIP Code Xref to open a List View of records. This list opens in a new window.

Click New on the List View toolbar to create a new ZIP code cross-reference record.

In the General section, enter the general setup information:

  • X-Ref Type – Select State Chapter, Region, or District. The type field is used to identify the whether the cross-reference is being defined to cover an entire state chapter, a region, or a district. This allows you to define a cross-reference for a single chapter based upon the entire state, regions within the state, and/or districts within a state.

  • State or Province – If you want the chapter territory to be assigned by state, enter the state code. Otherwise, leave this field blank.

  • ZIP Code Start – If you want the chapter territory to be assigned by ZIP code, enter the ZIP code that represents the beginning of the range. Otherwise, leave this field blank.

  • Country – If you want the chapter territory to be assigned by country, enter the country. Otherwise, leave this field blank.

  • ZIP Code End – If you want the chapter territory to be assigned by ZIP code, enter the ZIP code that represents the end of the range. Otherwise, leave this field blank.

  • Chapter – Use the Lookup button to select a chapter. (A single chapter may be used on multiple cross-reference records.)

Important

You must enter a ZIP code in both the ZIP Code Start and ZIP Code End fields, even if you want to use only a single ZIP code.

Click Save & Close to save this record and return to the list of records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Best practices for creating X-ref records

As you create ZIP code cross-reference records, please keep the following in mind:

  • Understand your data before you create these records. Decide on the best cross-reference approach for your requirements.

  • A single cross-reference record cannot contain all three cross-reference elements; that is, you cannot create a ZIP code cross-reference record that includes a combination of ZIP codes, states, and countries. You can set up your records based on Chapter Territory by zip code range only, by state only, by country only, or by zip and country. Avoid mixing and matching the setup.

  • A single cross-reference record that assigns chapter territory by ZIP codes must use a single range. For example, if you want to assign ZIP codes 58000 through 58500 and 58700 through 58999 to the same chapter territory, you must create a separate cross-reference record for each range.

  • A single cross-reference record that assigns chapter territory by state must use a single state. For example, if you want to assign North Dakota, South Dakota, and Montana to the same chapter territory, you must create separate cross-reference records for each state.

  • If you are using Zip+4 in your setup, then the zip code ranges for all X-ref records should be Zip+4 to ensure that the correct record is selected. Otherwise, do not use +4 in the X-ref record setup.

  • If you have foreign addresses (non-US) and assign Chapter Territories by zip code, always include a Country Code in every X-ref record setup to distinguish between domestic and foreign zip codes that may fall within the same zip code range. For domestic addresses, select the country code used for United States for the domestic records (typically ‘US’) for every X-ref record.

  • If you track a Chapter Territory for both domestic and foreign (non-US) addresses, you will need a corresponding record for each foreign country and zip code range.

  • If you do not track a Chapter Territory for foreign (non-US) addresses, create a Chapter named “No Chapter Territory” and an X-ref record for this “Chapter” using a zip code range 00001 to 99999 (or 00001-0000 to 99999-9999 if using zip+4). Do not enter a country in this record. Important: With this setup, if you have gaps in the zip code ranges for US records, if there is no match, the record will be assigned to the “No Chapter Territory” chapter because the system could not find an exact match with zip code and country and defaults to a match on zip code.

  • Do not allow X-ref records with overlapping zip code ranges. Each X-ref record must be unique.

Chapter territory assignment search conditions

  • Search 1 – Zip and Country: Look for an X-ref record where there is an address1 zip code (between start and end zip) match and an address1 country exact match. If it finds a matching x-ref record, use the first matching record in the table.

If the system does not find a matching zip plus country, then go to Search 2.

  • Search 2 – Zip: Look for an X-ref record where there is an address1 zip code (between start and end zip) match. If it finds a match, use the first matching record in the table.

If the system does not find a zip code between match, then go to Search 3.

  • Search 3 – State: Look for an X-ref record where there is an address1 state exact match. If it finds a match, use the first matching record in the table.

If the system does not find a state exact match, then go to Search 4.

  • Search 4 – Country: If no zip code between (start and end zip) match or no state exact match, then look for country exact match. If it finds a match, it uses the first matching record in the table.

Overriding automatic chapter territory assignments

You can choose to override the automatic assignment of the chapter territory for individual contact or account records by marking Yes on the Override Chapter Territory option in the General section of the account or contact record. If you override automatic chapter territory assignment for an account or contact, you can select a different chapter territory, and the system will not automatically change it when you change the primary address ZIP code, state, or country in the record.

Note

The following procedure shows how to override the automatic assignment of chapter territory for an account record; the same procedure applies to contact records.

From any of the UX work areas on the Navigation Tile Bar, click Accounts. Open the account you where want to change the override chapter territory setting.

Mark the checkbox on the Override Chapter Territory option. In the Chapter Territory field, click the Lookup button to select the appropriate chapter territory for this record. Save & Close the account record.

Important

If you have set the Override Chapter Territory option to Yes for an account or contact and then later decide that you want the system to automatically assign the chapter territory, you can change the Override Chapter Territory option to No by clearing the checkbox and then save the record. UX Online will then assign the appropriate chapter territory.

Updating members chapter territory

Use the Update Members Chapter Territory utility to run a system-wide update to the chapter territory assigned to account and contact records. You will need to use this utility if you change any ZIP code cross-reference records and need to update the chapter territories assigned to existing account and contact records because of this change. For instance, if your chapter territories are based on ZIP code ranges and the U.S. Postal Services changes the assigned ZIP code, you will need modify the ZIP code cross-reference record and then update the chapter territories assigned to your account and contact records. For additional information, see Creating a chapter territory ZIP code cross-reference.

In addition, you can use this utility to update the chapter territory field for accounts and contacts after you dissolve a chapter.

Note

If you select either the Update Contacts Chapter Territory or the Update Accounts Chapter Territory option, this utility will not change the assigned chapter territory for any accounts or contacts that have the Override Chapter Territory option set to Yes. For more information, $see Overriding automatic chapter territory assignments. If you select the Dissolve Chapter option, the utility will update the assigned chapter territory for all accounts and contacts assigned to the selected chapter, regardless of how the Override Chapter Territory option is set.

In the Navigation Tile Bar, select the Membership work area > Chapters > Chapter Manager > Update Members Chapter Territory. You have three options:

  • Update Contacts Chapter Territory

  • Update Accounts Chapter Territory

  • Dissolve Chapter

Update Contacts Chapter Territory

After updating the Zip Code X-Ref records, in the Update Members Chapter Territory window, select Update Contacts Chapter Territory. Click OK to initiate the process.

Important

This action cannot be undone. After you click OK, the system will begin updating the Chapter Territory of contact records where Override Chapter Territory <> Yes.

Update Accounts Chapter Territory

After updating the Zip Code X-Ref records, in the Update Members Chapter Territory window, select Update Accounts Chapter Territory. Click OK to initiate the process.

Important

This action cannot be undone. After you click OK, the system will begin updating the Chapter Territory of account records where Override Chapter Territory <> Yes.

Dissolve Chapter

Before running this utility:

  • Create a new chapter that will replace the chapter you wish to dissolve.

  • Create a new zip code x-ref for the newly created chapter – presumably using the zip code x-ref from the chapter you wish to dissolve.

  • Deactivate the zip code x-ref for the chapter you wish to dissolve.

Once you have updated your chapter and zip code x-ref records, in the Update Members Chapter Territory window, select Dissolve Chapter. Click the Chapter Lookup button to select the chapter you wish to dissolve. Click OK to initiate the process.

Important

This action cannot be undone. After you click OK, the system will begin updating the Chapter Territory field of account and contact records where the Chapter Territory = the selected chapter with the new chapter, regardless of the Override Chapter Territory setting in the record.

Since the chapter has been dissolved, Protech recommends that you deactivate the old chapter record after running this process.

Chapter 26: Chapter Reimbursement Processing

If you are using the UX Online GL Integration and the UX Online AP Integration, and your association reimburses chapters for chapter dues, you will need to run the chapter reimbursement process.

If you are not using the UX Online GL Integration and the UX Online AP Integration, you will not run this process. Instead, you will rely on client-specific reporting on the Chapter Dues Payable Account in UX Online and appropriate manual entries in your accounting system.

This information includes the following topics:

  • Chapter reimbursement overview

  • Processing chapter dues reimbursement

Chapter reimbursement overview

Chapter reimbursement is a batch process that creates journal entries to transfer revenue from each chapter’s “revenue” GL account (debiting the chapters payable account) to their payable GL account (crediting the accounts payable account). These accounts were assigned when you set up the default chapter membership renewal product. (For more information, see Creating default dues and chapter billing products.)

Important

Do not use this process if you are not using the UX Online GL Integration and the UX Online AP Integration.

If your organization uses UX Online Accounts Payable, the process also creates the necessary payment vouchers in the accounting system. Each chapter’s chapter record must assigned a Dynamics GP or Dynamics SL vendor (using the same ID as in UX Online). The process will automatically create a voucher for the vendor associated with the chapter.

Important

The vendor IDs used in Dynamics GP or Dynamics SL must be the same ID as is used in UX Online.

If you organization does not utilize UX Online Accounts Payable, the process does not create vouchers in the accounting system. They must be created manually.

The process consists of the following procedures:

  • Create a batch for chapter reimbursement processing. The batch type must be Chapter Reimbursement Processing. (For more information, see Creating a batch in UX Online.)

  • Create GL detail for a chapter reimbursement batch.

  • Post to Accounting for a chapter reimbursement batch.

For detailed information, see Processing chapter dues reimbursement.

Note

The procedures for creating GL detail and posting to accounting can be performed at the same time, or they can be managed separately, depending on your association’s business rules.

Processing chapter dues reimbursement

If your association reimburses chapter membership dues, you will need to run the chapter dues reimbursement process. Chapter reimbursement is the process of transferring the revenue for each chapter’s membership dues from the chapter’s revenue GL account to their payable GL account. These accounts were assigned when you set up the default chapter membership renewal product. (For more information, see Creating default dues and chapter billing products.

Important

Do not use this process if you are not using the UX Online GL Integration and the UX Online AP Integration.

The chapter reimbursement process uses a special batch type: Chapter Reimbursement Processing. A Chapter Reimbursement Processing batch can only be used for this process, and it cannot be used for any other types of transactions or batch processes.

This “fiscally oriented” process uses the batch date to determine the month-end date to be used for the process. All GL detail records used in the process are filtered to include only those with a fiscal date less than or equal to the month end of the batch log batch date. This allows the process to be run at any time so that GL entries entered beyond the month-end date of the batch log batch date are ignored.

The procedures for creating GL detail and posting to accounting can be performed at the same time, or they can be managed separately, depending on your association’s business rules. This procedure shows how to perform them at the same time.

Important

You must create a batch to use for chapter dues reimbursement before running the process. The Batch Type field for this batch must be set to Chapter Reimbursement Processing. For more information, see Creating a batch in UX Online.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management > Batch Log to view a list of batch log records. This View will open in a new window. In the Batch Log list, click New on the toolbar to open a new batch log record.

In the General section of the Batch Log record, enter the general batch setup information:

  • Description – Enter a description for this batch. When this batch is posted, the entry here will appear in the Reference field in the accounting system’s general ledger transaction entry window. If you are integrating with Microsoft Dynamics GP, note that there is a 30-character limit. This description also appears as the Batch Name in the Comments field in the Batch header file in Microsoft Dynamics GP.

  • Batch Number – Displays an automatically generated number. The number increases by one each time you save a new batch. This number will appear in the batch ID field in the accounting system’s general ledger transaction entry window.

  • Batch Date – This field defaults to the system date. Enter the last day of the month for which you are running this process.

Note

Because the batch date is the date the journal entry posts into the accounting system, be sure you enter the correct date.

  • Batch Type – Select Chapter Reimbursement Processing as the type for this batch.

Selecting this batch type will automatically mark the batch as Closed. Do not mark the Ready for GL Detail and Ready To Post checkboxes in the batch log record.

Save & Close the batch log record to return to the list of active batch log records. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

In the Navigation Tile Bar, select the Financial Manager work area > Accounting Manager > Batch Management. Select Special GL to create GL Detail and post to accounting.

Selecting Special GL will open a new window listing closed batches where batch type ≠ Standard GL Detail that have not been processed for either GL Detail. This includes your chapter reimbursement processing batch.

Use the checkboxes to mark Ready for GL Detail and Ready to Post. Select OK to initiate the process and close the window. After the process is complete, select Close to close the processing window.

The appropriate GL detail will be created for this batch and post the GL detail to the accounting system.

If your system is integrated directly with your accounting system’s Payables Management module, the process will also create the necessary payment vouchers in your accounting system. For more information, see Chapter reimbursement overview. (If you do not use the direct payables integration, you must create the payment vouchers manually.)

Print the UX Account Distribution Detail Report, UX Chapter Reimbursement Detail or Summary Report (or both) to help you verify the chapter reimbursement entries:

  • The Account Distribution Detail Report shows the debits and credits that were created by the chapter reimbursement process.

  • The Chapter Reimbursement Detail Report and the Chapter Reimbursement Summary Report will show the reimbursement amounts processed for each chapter for the date range selected.

Print the UX Account Distribution Detail by GL Account and compare the account balances for the chapters payable account to the balances in the Microsoft Dynamics GP GL Detail Inquiry Report or the Microsoft Dynamics SL Detail General Ledger Report.

Subscriptions

Part 6: Subscriptions

This part of the documentation describes the procedures you will use to manage your organization’s subscriptions. You will learn about entering new subscriptions, renewing subscriptions, and running the galley to produce your mailing label file.

This information is divided into the following chapters:

  • Chapter 27: Subscription Renewal Billing Setup

  • Chapter 28: Subscription Transactions

  • Chapter 29: Subscription Processing

Chapter 27: Subscription Renewal Billing Setup

Renewal processes in your organization can apply to several areas, including national and chapter memberships, subscriptions, and certifications. With regard to subscription setup and processing, several variables can affect the way your organization bills subscribers:

  • Does your organization sell subscriptions for more than one publication?

  • Can subscriptions be invoiced and paid in installments?

  • Do you need to limit the number of recipients for your organization’s benefits?

  • Does your organization have two-year subscription rates?

  • Does your organization have agency subscribers?

  • Does your organization create a monthly subscription mailing export?

  • Does your organization charge international shipping fees?

Because your organization may need to support all these variables in the subscription renewal billing process, you can use UX Online to set up all of the details for each type of subscription renewal billing you perform and save those details as a renewal benefit.

Note

If your association charges sales taxes on subscriptions, contact Protech Associates for assistance with configuring the set up.

This part of the documentation describes how to set up the subscription renewal benefits required to support your organizations subscription billing needs.

Additionally, this documentation describes how to create a galley export for your publication mailing labels and run automated subscription renewal and termination processes.

This information is divided into the following topics:

  • Subscription renewal benefit setup overview

  • Creating a default subscription product

  • Using Installment schedules

  • Creating a subscription renewal benefit

  • Configuring new subscription cycle state override

  • Creating subscription benefit rates and prices

  • Editing subscription rate price records

  • Setting up galleys and galley details

  • Galley Run Log

Subscription renewal benefit setup overview

A subscription renewal benefit is made up of several separate components—prices, installment schedules, rates, and galley details—that you will use to simplify the process of generating invoices for subscription transactions. There are five basic components to a subscription renewal benefit: subscription products, installment schedules, rates, prices, and galleys (if you run a galley for labels).

  • Renewal Products – CRM uses products from the product catalog to support GL detail. In order to create invoices for subscriptions, you must create default products for them. The renewal products are also used to define G/L accounts and the accounting system company.

  • Installment Schedules – You must create at least one installment schedule—a standard single annual installment—for use with subscription renewals. You can also create additional installment schedules if your organization offers a variety of payment options for your subscription billings.

  • Rates – A rate defines the pricing of the renewal benefit billing and is used to calculate the subscription amount. A rate determines whether the price is calculated based on quantity, volume, or factor, as well as the installment schedule used, price levels, and the number of benefit recipients specific to the rate. While you must create at least one rate within each renewal benefit, a single benefit can have multiple rates. For instance, multiple rates are required if your subscription pricing structure is tiered to track a specific number of benefit recipients. For more information, see Benefit recipients.

  • Prices – Pricing, or the actual subscription amounts, is defined within the rate. Each rate must have at least one member price item and one non-member price item. If your organization bases its pricing on specific volume ranges, you will need a member price and a non-member price for each volume range. If your organization bases its pricing on a factor of specific volume ranges, you will need a member price and a non-member price for each volume range. Additionally, you can define prices based on a date range to allow price changes from year to year as needed.

Important

When calculating pricing, the system will select the price record where the cycle start date falls within the start and end date range of the rate prices record. If no price record is found, the system will calculate dues as $0.00.

  • Galleys – A galley is a means of generating a list of subscribers for a publication. You will use galleys to create the mailing labels for each issue of your publications and to verify the total number of paid and unpaid recipients for advertising purposes.

Creating a default subscription product

This section describes how to create the subscription product required for setting up the subscription renewal benefit.

Note

If your organization sells subscriptions to multiple publications and has separate revenue accounts for each publication, then you will need to create a subscription/publication product for each publication and its corresponding revenue account. If your organization only uses one revenue account to track subscription revenue, then you only need one subscription/publication product.

When you create your subscription products, you will enter the basic information about each publication such as whether your organization recognizes subscription dues revenue on a cash basis, if your organization defers subscription revenue, and the general ledger accounts you use for dues revenue.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to open the List View of active products. This View opens in a new window.

On the List View toolbar, click Add Product to create a new product. In General section, select the fields appropriate to the product you are creating:

  • Product ID – Enter a code or abbreviated name for this product. For example, the ID for your subscription could be ‘PUB’ or ‘JOURNAL’. Or, if you have multiple publications with subscriptions, you can use the initials of the publication name as the ID, for example ‘AEJ’ for ‘Association Executives Journal’.

  • Name – Enter a short descriptive name of the product, for example, ‘Subscription Product’. If you have more than one subscription product that you need to define, you might enter the actual name of the publication in this field.

  • Unit Group – Click the Lookup button, select Each, and click OK.

  • Default Unit – Click the Lookup button, select Each, and click OK.

  • Currency – If you are working in a single currency environment, by default, your preferred currency appears in this field. Otherwise, you will need to select the Currency.

  • Product Type – Select Subscriptions from the list of product types.

  • Subject – This field is optional.

In the Accounting area, complete the following fields:

  • Company – The system will automatically populate this field with the company record flagged as the default company in your set up. If you need to make a change, click the Lookup button to select the appropriate accounting system company for this product. This controls where accounting data will post during the posting process and controls the display of GL accounts available in the GL account lookup fields.

  • Reimbursable – Select Not Reimbursable for subscription products.

  • Primary GL Account – Click the Lookup button to select the appropriate primary GL account for this product. The type of account you select depends whether you defer subscription revenue:

      • Subscription revenue not deferred – Select the subscription revenue account.

      • Subscription revenue deferred – Select the subscription deferral account.

  • AR GL Account – Click the Lookup button to select the appropriate AR account for this product and click OK.

  • Cash Basis – If your organization recognizes all subscription revenue on a cash basis, select Yes. If subscription invoices should create an accounts receivable entry (that is, if you use accrual basis), select No.

Important

For organizations that manage subscription revenue on an accrual basis, the Cash Basis = No setting does not result in accurate AR when subscriptions are billed in more than one installment. AR is created for the entire subscription amount for all installments – not incrementally for each installment period.

  • Control Accrual Basis via AR Utility – This field is enabled when Cash Basis = Yes and mainly is used for membership dues. Leave the default setting = No.

  • Secondary GL Account – This field is enabled and required when the Primary GL account selected is a deferral account. If your organization defers subscription revenue, click the Lookup button to select the appropriate revenue account for this product and click OK. If the Primary GL account selected is not a deferral account, the field is disabled and no entry is required.

  • AP GL Account – This field is disabled and no entry is required.

In the Costs area, select the fields appropriate to the dues billing product you are creating:

  • Default Price List – Click the Lookup button to open the Look Up Records dialog box. Select Member and click OK.

  • Decimals Supported – Enter the number of decimal places needed for this product’s currency format. For example, the default value of 2 is for a 0.00 currency format.

  • Single Currency – Do not check this field. It is not applicable to Subscription product types.

  • List Price – Leave blank. Pricing is not driven by a default subscription product types.

  • Apply Freight – This field does not apply and is disabled for subscription product types.

  • Is it a Bill Recipient – This field does not apply and is disabled for subscription product types.

In the Tax Product Info area, select the fields appropriate to the dues billing product you are creating:

  • Taxable – Check the Taxable field if tax should be calculated on subscriptions.

  • Tax Rate – This field does not apply and is disabled for dues billing and chapter billing product types.

The fields in the Description section do not apply to subscription products; however, you may enter descriptive text in the Description field.

The fields in the Web section work with MX Online. Do not modify these fields unless directed to do so during an MX Online implementation.

Click Save & Close to save this subscription product record and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Notes

When you save a product record, additional related entities in the Navigation Pane are available, such as Substitutes, Price List Items, and Prices. These features are not applicable to subscription product types. Because pricing for subscriptions is driven by the benefit/rate set up, you do not need to set up prices for default subscription product types.

Using Installment schedules

If your organization offers installment plans for subscriptions, you can incorporate these installment schedules into your subscription renewal benefits. For example, your organization might offer subscription payment schedules of a single annual payment, semi-annual payments, and quarterly payments. On the other hand, your journal subscription may only have a single annual payment. You can create installment schedules to cover all of the installment plans you offer, and then add them to your renewal benefits as needed.

Because installment schedules are also used for membership renewal benefits, you may find that the installment schedule you need for subscription billing is already set up. If this is the case, you may skip this section and go to Creating a subscription renewal benefit. If you do not have the installment schedule setup required, see Creating installment schedules.

Creating a subscription renewal benefit

A subscription renewal benefit consists of a subscription product, along with at least rate to manage the installment schedule, pricing, and galley information. You will use subscription renewal benefits when you create invoices for your new and renewing subscribers.

As your organization grows and changes, you can change your subscription renewal benefits and add new benefits at any time.

Note

You must have a default subscription product and at least one installment schedule set up before you begin this procedure. For more information, Creating a default subscription product and see Creating installment schedules.

Important

Before you begin creating benefits and rates, carefully review and document your organizational requirements for renewal billing and work with your Protech representative to explore the best setup based on your needs.

You will need at least one benefit. You will need to create additional renewal benefits if any of the rates do not share all of the characteristics of the parent benefit. As your organization grows and changes, you can change your renewal benefits and add new benefits at any time.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Step Three: Renewal Benefit to open the List View of active benefits. This list opens in a new window.

Click New on the List View toolbar to create a new benefit. In the General section of the Benefit record, complete the general information about the renewal benefit:

  • Module – Click the Lookup button to select the Subscription module for the new benefit.

  • Default Product – Click the Lookup button to select the default product for this renewal benefit. Select the subscription product you created and click OK. All transactions associated with this renewal benefit will use the accounting setup defined in this default product.

Note

The default product will be used as the default for all rates defined within the benefit. However, you can assign a different a subscription product to specific rates, if needed.

  • Name – Enter a descriptive name for the benefit.

  • Is Primary Benefit – Click to select Yes if this benefit controls membership status. If this benefit does not control membership status, click to select No. (Subscriptions typically are not considered the primary membership benefit.)

  • Renewal Method – Select either Calendar or Anniversary. Anniversary is typical for subscription benefits.

  • Chapter Benefit – Click to select No. This option is only supported for membership module benefits.

  • Sequence – Used to control the order in which invoice detail is created in a UX Online grouped invoice that is created during the generate renewal billing process. For example, if membership benefits should appear first in the invoice detail of the system created renewal invoice for grouped benefits, enter 1. If subscription benefits should appear second, enter 2. See About renewal benefit sequencing for important information on how UX Online relies on the Sequence number during renewal processing.

  • Group Invoices – Click to select Yes if this benefit should be grouped during renewal processing with other renewal benefits that share the same invoice customer, invoice Bill To, and renewal billing expiration date into a single invoice. For example, if a subscription benefit for an account or contact has the same invoice customer, invoice Bill To, and renewal billing expiration date as this membership renewal benefit, and you want the two benefits grouped into one invoice, you would select Yes. If you do not want benefits with the same expiration date grouped on a renewal invoice, click to select No.

Note

If you choose to group benefits on renewal invoices, the sequence number you enter in the Sequence field for each benefit determines the sequence of the invoice detail on a renewal invoice. See About renewal benefit sequencing for important information on how UX Online relies on the Sequence number during renewal processing.

  • Prorate – If you selected the Calendar renewal method, and you want to prorate the new subscriber’s price for this benefit, click the Lookup button to select the prorate schedule and click OK. If you selected the Anniversary renewal method, do not select a prorate schedule.

Important

The set up for a calendar-based benefit requires a prorate schedule, even if your organization does not prorate subscriber’s price for the calendar benefit. If your organization’s subscriptions are calendar based and you do not prorate a new subscriber’s price, use a prorate schedule where all prorate detail records contain prorate number of months = 0.

  • Prorate Cycle – This setting works in conjunction with the Calendar renewal method only. Select the desired cycle:

    • Current Cycle – Select this option if a new subscription is prorated during the first calendar year. For example, assuming a January to December renewal year, if a subscriber begins in June, the customer would pay half of the subscription amount.

    • Next Cycle – Select this option if a new subscription is prorated during the second renewal cycle. For example, assuming a January to December renewal year, if a subscription begins in June, the customer would pay the full subscription amount for the first year. When the subscriber renews at the end of December, they would pay half of the subscription amount for the second full renewal year.

  • Default Start Date – Select the starting date of the renewal cycle. In all instances, the default start date will be the 1st of a month. The options available here depend on what renewal method you selected.

Important

It is important to consider the implications of selecting the Default Start Date in scenarios where the default start date is in the future (for example, Begin Next Month). When the new subscription renewal billing cycle start date is equal to or less than the system date, the renewal billing record cycle state will equal Current. When the new subscription renewal billing cycle start date is greater than the system date (future default start date), the renewal billing record cycle state will equal Upcoming. If the benefit default start date is in the future, a new subscription does not become effective until the renewal billing cycle state updates to Current. This update occurs when the renewal billing cycle start date equals the system date. In the scenario of a future start date, subscriptions are not eligible for galley processing automatically based on a fully paid new subscriber invoice. You can override the default cycle state to Current for all new subscriptions through the application parameter PASubscription.NewSubscriptionCycleState. For more information, see Configuring new subscription cycle state override.

    • If the renewal method is Calendar, select the month your renewal cycle begins. For example, if your renewal year begins in January and ends in December, select January. (Note: You must select a calendar month if the renewal method is Calendar.)

    • If the renewal method is Anniversary, select one of the following options. (Note: You cannot select a calendar month if the renewal method is Anniversary.)

      • Beginning of Current Month – the default start date is the first of the current month, regardless of when the subscriber joins during the month. This setting works in conjunction with the Anniversary Renewal Method only and does not require an entry in the Cut Off Day field.

      • Beginning of Next Month – the default start date is the first of the next month, regardless of when the new subscriber joins during the month. This setting works in conjunction with the Anniversary Renewal Method only and does not require an entry in the Cut Off Day field.

      • Beginning Based on Cutoff Day – used in conjunction with the Cut Off Day (COD) field described below, the default start date is calculated based upon the day of the month that the new member joins. If the new subscriber joins on or before the Cut Off Day (COD), then the default start date is the first of the current month; if the new subscriber joins after the Cut Off Day (COD), then the default start date is the first of the next month.

      • Beginning of Current Quarter – the default start date is the first day of the current quarter, regardless of when the subscriber joins during the quarter. This setting works in conjunction with the Anniversary Renewal Method only and does not require an entry in the Cut Off Day field.

      • Beginning of Next Quarter – the default start date is the first day of the next quarter, regardless of when the new subscriber joins during the quarter. This setting works in conjunction with the Anniversary Renewal Method only and does not require an entry in the Cut Off Day field.

  • Cut Off Day (COD) – Enter the appropriate cut-off day for the renewal method and default start date you selected.

Important

It is important to consider the implications of selecting the Default Start Date and COD (Cut Off Day). In scenarios where the cycle start date for a new subscriber is in the future, the new subscriber is not eligible for the galley until the related renewal billing record cycle start date is equal to or less than the system date, which is when the renewal billing record cycle state updates from Upcoming to Current. Subscription benefits are not conferred automatically based on a fully paid new subscription invoice when the renewal billing record cycle state is Upcoming. You can override the default cycle state to Current for all new subscriptions through the application parameter PASubscription.NewSubscriptionCycleState. For more information, see Configuring new subscription cycle state override.

    • If the renewal method is Anniversary and the default start date is Beginning Based on Cutoff Day, enter the cut-off day to use to calculate the cycle start date. If you are using the Anniversary renewal method and you select anything other than Beginning Based on Cutoff Day as the default start date, do not change the default entry of 1; it is a required minimum value.

    • If the renewal method is Calendar, enter the cut-off day to use with the Default Start Date month to calculate prorated pricing.

      • If a new subscriber joins on or before the cut-off day, then the renewal cycle start date will be the 1st day of the month you selected in the Default Start Date. To calculate the prorate, the system uses the prorate number of months for the month in which the new member joins.

      • If a new subscriber joins after the cut-off day, then the renewal cycle start date will be the 1st day of the month following the month you selected in the Default Start Date. To calculate the prorate, the system uses the prorate number of months for the month after the month in which the new member joins.

  • Allow Renewal on Unpaid – If you want to allow the system to create a new renewal billing invoice when the contact or account has a previous renewal invoice that is still unpaid, click to select Yes. Click to select No if you want to require that the previous renewal billing invoice must be paid before a new one can be created.

In the Pricing area of the General section of the Benefit record, complete the information about the renewal benefit:

  • Start Date – Select the default pricing starting date to be used for all of the rates and prices created in this renewal benefit. You should always select the first day of the month for your price start date in order to be consistent with other renewal logic and to enhance functionality for creating new prices.

  • End Date – Select the default pricing ending date to be used for all of the rates and prices created in this renewal benefit. You should always select the last day of the month for your price end date in order to be consistent with other renewal logic and to enhance functionality for creating new prices.

Click Save to save this benefit. After saving this record, other options in the benefit record Navigation Pane are activated: Activities, Closed Activities, Rate, and Galley Setup.

The Web section is used with Protech’s MX Online, and will be set as needed during that implementation. Do not change these settings.

Click Save & Close to save the benefit and return to the Benefit list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Configuring new subscription cycle state override

You can override the system default cycle state that is based on cycle start date and setting the cycle state = Current for all new subscriptions by changing the Config value for the application parameter, PASubscription.NewSubscriptionCycleState.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This List View opens in a new window. Locate and open the parameter PASubscription.NewSubscriptionCycleState.

Set the Config Value field to the method that your organization uses:

  • Current – Ignores the renewal billing cycle start date and sets the cycle state = Current for all new subscribers.

  • Leave the Config value blank to set the renewal billing cycle state based on the cycle start date.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Creating subscription benefit rates and prices

A single subscription benefit can have multiple rates, which define how a renewal benefit is calculated. For example, a journal subscription benefit can have rates for students, members, and non-members, as well as domestic and international rates, rates for regular and airmail delivery, and single or multiple year rates. Additionally, you can define the number of benefit recipients for each rate. As long as each rate shares the attributes of the benefit setup, you can create multiple billing rates under the same benefit.

To set up multiple rates under a single benefit, repeat the following steps for each rate. For more information about defining benefit recipients, see Benefit recipients.

Subscription Rates

In the Navigation Pane of the Benefit record, click Rate to open the Rate Associated View. Click Add New Rate on the List View toolbar to create a new rate.

In the General section of the Rate record, complete the general information about the rate:

  • Name – Enter a descriptive name for the rate. If a rate is going to have a specific installment option, we recommend that you include that in your name rate (for example, ‘One Year Domestic Subscription’).

  • Benefit – This field displays the name of the parent benefit for this rate and is not available for edit.

  • Rate Type – Select the calculation method for this rate:

    • Select Quantity if the pricing is not calculated based on volume data in the account or contact record; instead, the price is based on a flat quantity (typically 1). This is the typical rate type for subscriptions.

    • Select Volume if the pricing is calculated based on volume data in the account or contact record. For example, your organization can base its subscription price on a company’s sales revenue and you capture that sales revenue figure for purposes of calculating pricing. You could use Volume rates so that the system will calculate the pricing automatically for you based on the value ranges in your price setup for this rate. For more information, see Setting up volume-based rates and prices in Membership Renewal Setup.

    • Select Factor if the pricing is calculated based on a factor calculation using volume data in the account or contact record. For example, your organization can base its subscription price based on a factor calculation of a company’s sales revenue. You could use Factor rates so that the system will calculate the price automatically for you based on the value ranges in your price setup for this rate. For more information, see Setting up factor-based rates and prices in Membership Renewal Setup.

  • Chapter – Leave this field blank. It does not apply to subscription benefits.

  • Installment – Click the Lookup button to select the installment schedule for this rate.

Important

If your organization uses calendar-based subscriptions and defers revenue, you must follow the guidelines provided in Membership Renewal Setup. For important additional information, see Calendar-based dues prorate guidelines.

  • Number Benefit Recipients – You must enter at least 1, however, the number is based on your organizational needs. For example, if you are creating a rate that is specific to account records, enter the number of records that can benefit from the account’s renewal billing record.

  • Default Price Level – Click the Lookup button to select the default price level for this rate. Price levels in CRM allow an organization to have multiple price lists. Typically, organizations have two price levels to differentiate pricing for members from pricing for non-members (although some have more intricate pricing structures). Every account and contact record in CRM has a field that indicates the price list that applies to that record. Each product also has a field relating that product to a particular price level. If an account or contact record does not have a default price level, the system uses the default price level indicated for the product itself. For subscriptions, the default price level will typically be Non-Member.

  • Default Price – Enter the default price for this rate. The system will use this entry to create a price for each price level that you have set up. You can modify these prices at any time, or you can create additional price records for this rate, if needed.

  • Volume Field Name Contact – If you selected Volume or Factor as the Rate Type, enter the attribute name for the contact field used to maintain volume data for purposes of calculating price. The typical contact attribute is pa_volume. If the Rate Type selected is Quantity, leave this field blank.

  • Volume Field Name Account – If you selected Volume or Factor as the Rate Type, enter the attribute name for the account field used to maintain volume data for purposes of calculating price. The typical account attribute is pa_volume. If the Rate Type selected is Quantity, leave this field blank.

  • Product – Displays the default product entered on the benefit record. If this particular rate’s revenue needs to be tracked in a GL account other than the one that was defined for the benefit, select the appropriate product.

  • Recipient Product – If this rate supports a specific number of “free” benefit recipients (as defined in the Number of Benefit Recipients field), and your organization charges for any additional recipients above this number, you will need to assign a product for this. This product is used to calculate additional charges on the renewal invoice if the renewal billing benefit recipients count exceeds the number defined for this rate.

  • Rate Next – This field is not enabled until you save the rate, when the system automatically populates this field with this rate. If this rate is part of a progressive rate structure, click the Lookup button to select the rate to be used after this rate. (See Setting up progressive benefit rate structures for more information.) If this rate is not part of a progressive rate structure, do not change this entry – the next renewal cycle will create a subscription renewal invoice based on this rate.

  • Airmail – Click the Yes option if subscriptions using this rate should be mailed via airmail. You can use this field to separate galley records that should be sent via airmail.

The Web section is used with Protech’s MX Online, and will be set as needed during that implementation. Do not change these settings.

Click Save to save the new rate record and activate additional setup in the Navigation Pane of the rate, where you will set up Prices for this rate, as described below.

Subscription Rate Prices

In the Navigation Pane of the rate record, click Prices to display the price records created by the system for each price list in your system setup.

All system created prices records will use the default price in the rate, as well as the price start date and price end date that you defined for the benefit. You will need to review and revise these prices. See also Setting up Volume-based Rates and Prices and Setting up Factor-based Rates and Prices.

Important

If the Rate Type is Volume, you will need to edit the price records that were created by the system to set the price and the Value Minimum and Value Maximum. In addition, you will need to create additional prices for each volume range.

If the Rate Type is Factor, you will need to edit the price records that were created by the system to set the factor (price is ignored) and the Value Minimum and Value Maximum. In addition, you will need to create additional prices for each volume range.

Open the price record you want to view/edit. Fields are described below for creating a new price record. To create a new price, click Add New Prices on the List View toolbar.

In the General section of the Prices record, complete the general information about the price:

  • Price Level – Click the Lookup button to select either Member or Non-member as the price level for this price record. (You must create both member and non-member versions of every price your organization uses.)

  • Name – The system will populate this field based on the Price Level you selected.

  • Calculation Method – For subscriptions, do not change the default value of Flat Rate. This method applies to all rate types.

  • Price/Percent of List Price – If you selected Quantity or Volume for the rate type, enter the total amount due. (If the rate includes installment billing, the system automatically calculates the installment amounts.) Price is ignored for rate type Factor.

  • Value Minimum – If you selected Volume or Factor for the rate type, enter the minimum value for the range for this price. If you selected Quantity for the rate type, you do not need change the default values.

  • Value Maximum – If you selected Volume or Factor for the rate type, enter the maximum value for the range for this price. If you selected Quantity for the rate type, you do not need change the default values.

  • Start Date – The default start date is the Pricing Start Date entered for this benefit, which typically reflects the start date of the benefit year. If the price is valid for a different date range, select the starting date. For example, if this rate is valid for the 2008 year, enter January 1, 2008 as your start date.

  • End Date – The default end date is the Pricing End Date entered for this benefit, which typically reflects the end date of the benefit year. If the price is valid for a different date range, select the end date. For instance, if this rate is valid for the 2008 year, enter December 31, 2008 as your end date.

Important

When calculating pricing, the system will select the price record where the cycle start date of the related renewal billing record falls within the start and end date range of the rate prices record. If no price record is found, the system will calculate dues as $0.00.

  • Factor – If you selected Factor for the rate type, enter the factor (as a decimal representing the percentage) for calculating price. Otherwise, leave this field blank.

  • Product – This field is disabled. It is not used for setting rate prices.

  • Rate – Displays the name of the rate.

  • Adv Ad Type – This field is disabled. It is not used for setting rate prices.

Click Save & Close to save the price and return to the Prices list. Repeat as needed for each Prices record required for this rate.

Once you have completed setting up prices records, click the rate in the Top Navigation Toolbar to return to the Rate record.

Click Save & Close on the rate record to save your changes and return to the benefit record.

Note

If your organization’s subscription rates change, you can create additional price records for this rate to reflect the new start and end dates for that price. When you create additional price records, be sure that the start and end dates do not overlap the start and end dates of existing price records for any rate.

Editing subscription rate price records

If your organizations decides to increase subscription rates—for example, if the price will be changing at the beginning of next year—you will need to create additional price lists to support the upcoming price increase. At the same time, however, you still need to keep your current price lists until the new prices go into effect. To support this scenario, you need to edit the end date of your existing price records and create the member and non-member price records for the new price and dates in which they are to go into effect for each subscription rate.

To edit existing subscription rate price records, in the Navigation Pane of the rate record for the subscription benefit, click Prices in to display the List View of existing price records. This list opens in a new window.

To change the End Date for the existing price lists, select the price lists that you want to change. (To do this, press and hold the Ctrl key while you click the individual records.)

Click Edit on the List View toolbar to open the Edit Multiple Records window. In the Edit Multiple Records window, enter the End Date to reflect when the selected price levels should expire. Click Save in the Edit Multiple Records window to update the selected price records with the new end date.

To create the new price records, use the Price Progression utility on the benefit Record toolbar. See Creating new rate prices using Price Progression. When you have created your new subscription prices, UX Online will automatically use the new prices on or after their start dates.

Note

If you create a new subscription invoice and no price is assigned, it is likely that one or more of your price records have an overlapping start date or end date, or there are gaps between the start date and end date.

Important

When calculating pricing, the system will select the price record where the cycle start date falls within the start and end date range of the rate prices record. If no price record is found, the system will calculate dues as $0.00.

Setting up galleys and galley details

A galley is used to identify all the individuals who should receive a particular publication. This could include members who receive the publication as part of their membership, members who have paid for an additional subscription, non-members who have subscribed, and any other recipients. You will use galleys to create mailing labels for an issue of the publication.

This procedure describes how to set up the galley and galley details for printing mailing labels for all paid and member subscribers. When you are going to print and distribute an issue of a publication, you will use the galley process to create a SQL file that includes the names and addresses of all paying subscribers and members who are to receive this publication. This SQL File can be used to print labels in-house or you can export the data to a report and send electronically to your mail house.

Note

At any time, you can view a galley’s Galley Run Log to see when the last galley was run and for what issue start date. For more information, see Galley Run Log.

Galley

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Billing Settings > Step Three: Renewal Benefit to open the List View of Active Benefits. This list opens in a new window.

In the Benefits list, open the subscription benefit where you want to set up a galley. In the Navigation Pane of the Benefit record, click Galley Setup to open the Galley Setup Associated View. Click Add New Galley Setup on the List View toolbar. In the galley setup record, enter the following information:

  • Enter the full publication name in the Name field. (The information in the Owner and Benefit fields appears by default and no changes are needed.)

  • The Benefit field defaults from the parent subscription benefit. Do not change this value.

Click Save to save the Galley Setup record and activate setup options in the record Navigation Pane, including Galley Run Log, Galley Details, and Galley.

Continue you setup by creating Galley Details for this Galley record. See Galley Details for Paid Subscriptions and/or Galley Details for Membership Benefit.

Galley Details for Paid Subscribers

To define galley details for the subscription rates that should be included in the galley for this publication (paid subscribers), in the Navigation Pane of the Galley setup record, click Galley Details to open the Galley Setup Details Associated View.

Click Add New Galley Setup Detail on the List View toolbar to open a new Galley Setup Details record. In the General section of the Galley Setup Details record, complete the general information about the galley detail for paid subscribers:

  • Benefit – Do not change this value. This defaults from the parent benefit for this galley.

  • Rate – Click the Lookup button to select the first subscription rate that should be included in the galley for label printing.

  • BPA Qualifier – If your organization produces BPA Audit reports required for advertising, you can select the type of qualifier this subscription rate represents. If your organization does not do BPA Audit reporting, skip this field.

  • Galley Type – This defaults to Benefit Recipients. Do not change this setting.

  • Grace Period Months – Enter the number of months beyond their expiration date that subscribers will continue to receive the publication.

Click Save & Close to save this galley detail. Repeat these steps for each subscription rate that should be included in this galley process. When finished with the last one, continue your setup by defining galley details for membership benefits, as described below.

Galley Details for Membership Benefit

Once you have defined galley details for the subscription rates that should be included in the galley for this publication, you also need to define the galley details for any membership dues rates in which the member receives the publication as part of their member benefits.

Click Add New Galley Setup Detail on the List View toolbar to open the Galley Setup Details record. In the General section of the Galley Setup Details record, complete the general information about the galley detail for membership benefits:

  • Benefit – Click the Lookup button to select the first dues membership benefit that receives this publication as part of its benefits.

  • Rate – Click the Lookup button to select the first renewal benefit rate that should be included in the galley for label printing.

  • Galley Type –

    • If the membership benefit you are adding to the galley detail is a “company” member benefit where the contacts at the member company receive this publication, select the Account’s Contacts option from this pull down.

    • If the membership benefit you are adding to the galley detail is for a contact, select the Benefit Recipients option from this pull down.

  • BPA Qualifier – If your organization produces BPA Audit reports required for advertising, you can select the type of qualifier this subscription rate represents. If your organization does not do BPA Audit reporting, skip this field.

  • Grace Period Months – Enter the number of months beyond their expiration date that subscribers will continue to receive the publication.

Click Save & Close to save this galley detail. Repeat these steps for each membership benefit/rate that should be included in this galley process. When finished with the last one, click Save & Close to return to subscription benefit record.

Galley view

The Galley view allows you to view the galley information for the account and contact records selected in each galley run. You can sort this view by the Publication Issue Date column to view the galley records by issue date.

In the Navigation Pane of the subscription Benefit record, click Galley Setup. Open the galley setup for the publication. In the Navigation Pane of the Galley Setup record, click Galley.

Galley Run Log

Each time the galley process is run for a publication, the date it is run and the subscription issue start date for which is was run is recorded in the Galley Run Log. At any time, you can view a galley’s Galley Run Log to see when the last galley was run and for what issue start date.

In the Navigation Pane of the subscription Benefit record, click Galley Setup. Open the galley setup for the publication. In the Navigation Pane of the Galley Setup record, click Galley Run Log.

Chapter 28: Subscription Transactions

This chapter describes how to create a new subscription invoice (transaction) and payment. Subscription invoices can be created for both non-members and members. In either case, the process is the same. The only difference may be in price if your organization offers member and non-member pricing for paid subscriptions to your publication.

In addition, this chapter describes the procedures you will use to cancel and terminate subscriptions, and how to process refunds on canceled subscriptions.

This chapter is divided into the following sections:

  • Creating a subscription invoice

  • Entering agency and library subscriptions

  • Renewal billing records for subscriptions

  • Changing an existing subscription

  • Canceling a subscription

  • Changing a subscription

  • Terminating a single subscription

  • Reinstating a terminated subscription

Creating a subscription invoice

This procedure describes how to create a new subscriber invoice for billing the initial subscription by selecting a subscription renewal benefit.

You can create a new invoice from within an existing account or contact record or directly from Invoices in any of the UX work areas on the Navigation Tile Bar. By creating an invoice from an existing record, the system automatically fills many data entry fields in the invoice header by using data from the record. These fields include the Customer name, the Bill To and Ship To name and address, Price List and Currency.

Note

The following procedure shows how to begin the membership invoice process from the contact’s record, but you can also begin from an account record or the Invoices list.

From any of the UX work areas on the Navigation Tile Bar, click Contacts. Open the contact record where you want to create an invoice.

On the Record toolbar of the contact’s record, click New Invoice to open a new invoice transaction. For more information about creating invoices, see Invoices.

Click Select Batch to select the appropriate open batch based on your organization’s business rules.

Note

After the first time you select a batch, the same batch will be used for each transaction you enter until you select a different batch, or that batch is closed.

Click Save to save the invoice with the selected batch or proceed directly and click New Transactions. Either will save the batch with the invoice, populate the Invoice ID, transaction date, and invoice address information.

From the New Transactions drop-down list, select Subscriptions from the menu.

On the renewal billing transaction record, enter the following information at the top of the General section:

  • Benefit – Click the Lookup button to select the subscription benefit.

  • Rate – Click the Lookup button to select the membership dues or chapter rate. When you select the rate, the system automatically fills in several of the remaining fields on the benefit entry form.

Important

If your organization uses calendar-based dues, you must follow the guidelines provided in Membership Renewal Setup regarding revenue recognition deferral start and end dates with multiple installment rates. For important additional information, see Calendar-based dues prorate guidelines.

  • If the customer is purchasing more than one subscription to this publication, change the Quantity field to reflect how many subscriptions to this publication they are purchasing. If purchasing more than 1, for rates where the rate type = Quantity, UX will update the price based on the price per unit times quantity entered. Also, UX will automatically create the requisite number of benefit recipient records based on the number allowed in the rate setup times the quantity entered in the transaction.

Click Save to save your transaction.

Important

If you click Save or Save & Close, and a renewal billing record already exists for this benefit and rate, a message stating that the benefit already exists will appear. You can enter a different benefit and rate, or you can cancel this transaction and use the existing invoice for the current benefit and rate. You cannot have two invoices for the same benefit and rate combination.

If there is no duplicate benefit/rate, a new renewal billing record will be created for this benefit.

If this subscriber has indicated an address other than their default address where this publication should be mailed, click Save and then click Benefit Recipients in the Navigation Pane. This will display the default recipient(s) for this subscription, which is the contact or account selected for this transaction.

Open the benefit recipient record displayed on this record. Make the necessary changes to the address information that appears on the benefit recipient record and set the Use Address option to Yes.

Click Save & Close to return to the subscription transaction.

Click Save to save your transaction and return to the invoice. To add a payment, click the New Transactions > Payments & Adjustments button on the invoice Record toolbar to apply a payment to this invoice. See Payment and Adjustment Transactions for additional information.

Review the invoice and detail to ensure that the invoice is correct. If it is correct, click Save & Close when you are finished.

Entering agency and library subscriptions

If your organization sells publication subscriptions to subscription agencies or libraries, follow this procedure to create the subscription invoice transaction.

Note

If your organization has special agency or library subscription rates, make sure these rates are set up before proceeding. For more information, see Creating subscription benefit rates and prices.

From any of the UX work areas on the Navigation Tile Bar, click Accounts. Open the account record where you want to create an invoice.

On the Record toolbar of the account’s record, click New Invoice to open a new invoice transaction. For more information about creating invoices, see Invoices.

Click Select Batch to select the appropriate open batch based on your organization’s business rules.

Note

After the first time you select a batch, the same batch will be used for each transaction you enter until you select a different batch, or that batch is closed.

Click Save to save the invoice with the selected batch or proceed directly and click New Transactions. Either will save the batch with the invoice, populate the Invoice ID, transaction date, and invoice address information.

From the New Transactions drop-down list, select Subscriptions from the menu.

In the renewal billing transaction record, click the Lookup button on the Benefit field to select the subscription benefit that is being purchased.

Click the Lookup button on the Rate field to select the subscription rate for this agency or library.

Enter the quantity of subscriptions to this publication the customer is purchasing.

If you want all of the subscriptions to go to the primary contact associated with the account, click Save & Close to close the subscription transaction.

If some of the subscriptions should go to other contacts, click Save and then click Benefit Recipients in the Navigation Pane. The list that appears displays the same number of benefit recipient records as the quantity of subscriptions. For example, if you entered 5 in the Quantity field, there will be five benefit recipient records. Or, the number of benefit recipients may be defined by the rate you selected. By default, each benefit recipient record will be the primary contact associated with the account selected.

You will need to change the ship-to addresses for each subscription that needs to go to a different address. To modify the address on a benefit recipient record, double-click it to open the Benefit Recipient record.

In the benefit recipient record, you can use one of the following methods to modify the address:

  • Click the Lookup button on the Contact field to select an existing contact from the database. If you select a contact from the database, you can use the contact’s primary address, or enter a different address, and change the Use This Address option to Yes.

  • Manually enter address information where this copy of the publication should be sent. If you do this, enter the recipient’s name in the Ship To Attention field, and change the Use This Address option to Yes.

Note

If you use the Lookup button on the Contact field, the system will display the contacts associated with the account defined for this record. To see all of the contacts in your system, remove the account name from the Account field.

  • Select which type of benefit recipient this individual is. (This can be used by your organization to group your mailing labels or identify different classes of subscribers.)

  • If this benefit recipient does not wish to receive the publication, change the Opt Out Publication option to Yes.

  • When you finish entering the necessary addresses for each benefit recipient, click Save & Close to return to the subscription transaction.

Click Save to save your subscription transaction and return to the invoice. To add a payment, click the New Transactions > Payments & Adjustments button on the invoice Record toolbar to apply a payment to this invoice. See Payment and Adjustment Transactions for additional information.

Review the invoice and detail to ensure that the invoice is correct. If it is correct, click Save & Close if you are finished.

Renewal billing records for subscriptions

A Renewal Billing record is created whenever a new subscription invoice is created and when the subscription is renewed by the generate renewal billing invoices process. The cycle start date for new subscribers is based on the join date and the benefit setup. As with renewal billing records for new members, a new invoice that creates a renewal billing record where the cycle start date is greater than the system date will result in a cycle state = Upcoming. You can override the default cycle state to Current for all new subscriptions through the application parameter PASubscription.NewSubscriptionCycleState. For more information, see Configuring new subscription cycle state override.

Note

The same components, conditions such as cycle state, and lifecycle updates exist in subscription renewal billing records as they do for membership renewal billing records. For more information, see Renewal billing records overview and Renewal billing record components.

To view the renewal billing records for a contact or account record, open the record and click Renewal Billing in the Navigation Pane. The Renewal Billing List appears, showing all renewal billing records for this individual or company. A member, for example, may have a membership dues renewal billing record here and perhaps a chapter dues renewal billing record. A non-member may only have a subscription renewal record listed here.

Depending on the lifecycle of renewal billing, you may see one or more records for the same benefit. For example, you may see multiple records for the same benefit where the cycle state = Past, one record where the cycle state = Current, and if you have run the renewal process, one record where the cycle state = Upcoming. For more information, see About Renewal Billing Cycle State and Cycle State Update Utility.

Important

Subscription renewals and the Galley rely only on information in the renewal billing record where cycle state = Current and benefit status = New, Renew or Reinstated.

To view specific information related to the current subscription renewal record, such as the subscription start date, expiration date, paid through date and status, double-click ro open the subscription renewal billing record within this view where cycle state = Current.

Click Benefit Recipients in the Navigation Pane of the renewal billing record to view the contact record that is designated to receive this publication. If multiple subscriptions were purchased, you will see a benefit recipient record for each subscription.

To view the subscription mailing address for any benefit recipient record, locate and open the record. (By default, the account or contact’s primary mailing address will be used.)

If a benefit recipient asks that their subscription be mailed to a different address, enter the new address the Ship To fields, and change the Use Address option to Yes on their benefit recipient record.

If they do not want to receive the publication, mark the Yes option for the Opt Out Publication field.

Click Save & Close when you are done making address changes for the benefit recipient. These settings will be used by the Galley utility when the galley process is run.

Changing an existing subscription

This section describes how to change an existing subscription invoice record. It is important that changes are made in the subscription invoice related to the Current renewal billing record.

Important

If you have already generated renewals for the upcoming renewal year and are changing the Current renewal invoice, you must also change the Upcoming renewal invoice.

The types of changes you can make include the following:

  • Changing the quantity

  • Changing the rate

  • Cancelling a subscription

  • Changing the publication

  • Terminating a subscription

Changing a subscription quantity

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to change a subscription invoice. In the Navigation Pane of the customer’s record, click Invoices. Locate and open the Current subscription invoice that needs to be changed.

Hint

The current subscription invoice also can be found within the Current renewal billing record for the subscription.

Important

If you have already generated renewals for the upcoming renewal year and are changing the subscription quantity in the Current renewal invoice, you must also change the subscription quantity the Upcoming renewal invoice.

Click Select Batch to select the appropriate open batch based on your organization’s business rules. For information about batches, see Batch overview.

Double-click the subscription invoice detail line item to open the renewal billing transaction record. Change number in the Quantity field and click Re-Calculate Invoice on the Record toolbar.

Note

If the batch this subscription product was entered in is still open, this will recalculate the invoice amount and totals based on the new quantity entered. If the batch is closed, the original entry will be canceled, and a new subscription detail line item will be created, with the new quantity and new totals.

A message will appear, asking you to confirm that you want to recalculate the invoice. Click OK to proceed and return to the invoice. If the original batch was closed, you will see a canceled line item with a red X next to it and the newly created line item to the recalculated subscription transaction.

Note

If a payment had been entered on the original transaction, you may have a balance due or a credit balance depending on whether the quantity was increased or decreased. If there is a balance due, you can apply a payment, or send the customer an invoice for payment. If there is a credit balance, you can leave the credit balance, refund the balance, or transfer it to another open invoice.

Click Save & Close to save and close your invoice.

Changing a subscription rate

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to change a subscription invoice. In the Navigation Pane of the customer’s record, click Invoices. Locate and open the Current subscription invoice that needs to be changed.

Hint

The current subscription invoice also can be found within the Current renewal billing record for the subscription.

Important

If you have already generated renewals for the upcoming renewal year and are changing the subscription rate in the Current renewal invoice, you must also change the rate in the Upcoming renewal invoice.

Click Select Batch to select the appropriate open batch based on your organization’s business rules. For information about batches, see Batch overview.

Double-click the subscription invoice detail line item to open the renewal billing transaction record.

Click the Lookup button on the Rate field to select the new subscription rate. Click Re-Calculate Invoice. A message will appear, asking you to confirm that you want to recalculate the invoice. Click OK.

Note

If the batch this subscription product was entered in is still open, this will recalculate the invoice amount and totals based on the new rate entered. If the batch is closed, the original entry will be canceled, and a new subscription detail line item will be created, with the new rate and new totals.

A message will appear, asking you to confirm that you want to recalculate the invoice. Click OK to proceed and return to the invoice. If the original batch was closed, you will see a canceled line item with a red X next to it and the newly created line item to the recalculated subscription transaction.

Canceling a subscription

In this situation, the customer wants to cancel their existing subscription, so you must cancel the current subscription using a full or partial cancellation.

This section describes how to cancel a current subscription and the system rules that apply based on batch status and payments within the invoice. When you cancel a subscription, invoice detail line items and charges are updated to reflect the cancellation. If the originating batch is closed, when you create GL detail for batch used to cancel the subscription, reversing GL detail will be created to reflect these changes. The subscription is no longer eligible for renewal or the galley utility.

Important

If you have already generated renewals for the upcoming renewal year and are cancelling the subscription in the Current renewal invoice, you must also cancel the subscription in the Upcoming renewal invoice. Protech does not recommend cancelling a Past renewal invoice.

There are two scenarios for canceling a renewal invoice:

  • Full cancellation – Fully canceling the subscription line item cancels/deletes the original invoice line item and creates a credit balance if there was a payment on the invoice.

  • Partial cancellation – A partial cancellation cancels the original subscription line item and creates a new line item for a prorated portion of the full subscription charge. You can partially cancel single and multiple-installment anniversary subscriptions, and single-installment calendar subscriptions. In addition, you can partially cancel multiple-installment calendar subscriptions if they are not prorated.

Note

You cannot partially cancel multiple-installment calendar subscriptions with proration because the invoice detail line item does not include start and end dates. If you attempt process a partial cancellation on a multiple-installment prorated calendar subscription line item, the system will process a full cancellation.

Canceling a subscription line item will have the following effects on the renewal billing record:

  • Current renewal invoice – Fully or partially canceling a current renewal invoice does not affect Past or Upcoming renewal billing records. When cancelling a Current renewal invoice, if the associated renewal billing record has any benefit status other than NULL, the status will be changed to Terminated, and the Termination Reason field will say Cancelled. The related invoice will be removed from the renewal billing record. If the renewal billing record has a status of NULL, it will be deleted.

  • Prior renewal invoice – Not recommended. Fully or partially canceling a prior renewal invoice does not affect the Current renewal billing record. When cancelling a Past renewal invoice, if the associated renewal billing record has any benefit status other than NULL, the status will be changed to Terminated, and the Termination Reason field will say Cancelled. The related invoice will be removed from the renewal billing record. If the renewal billing record has a status of NULL, it will be deleted.

  • Upcoming renewal invoice – Fully or partially canceling an upcoming renewal invoice does not affect the Current or Past renewal billing records. When cancelling an Upcoming renewal invoice, if the associated renewal billing record has any benefit status other than NULL, the status will be changed to Terminated, and the Termination Reason field will say Cancelled. The related invoice will be removed from the renewal billing record. If the renewal billing record has a status of NULL, it will be deleted.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to cancel a subscription. In the Navigation Pane of the customer’s record, click Invoices. Locate and open the Current subscription invoice that needs to be canceled.

Hint

The current subscription invoice also can be found within the Current renewal billing record for the subscription.

Important

If you have already generated renewals for the upcoming renewal year and are cancelling the subscription in the Current renewal invoice, you must also cancel the subscription in the Upcoming renewal invoice.

Click Select Batch to select the appropriate open batch based on your organization’s business rules. For information about batches, see Batch overview.

Double-click the subscription invoice detail line item to open the subscription renewal billing transaction record. Click the Cancel button on the benefit entry Record toolbar.

  • The Renewal Billing Invoice Detail Cancel dialog appears. Indicate whether you are doing a full or a partial cancellation. If you select Partial Cancellation, enter the cancellation date, which must be the last day of the month. (The system uses this date to calculate the prorated portion of the subscription renewal charge to credit to the customer.)

  • Click OK.

Depending the originating batch status (open or closed), the system will take the following actions:

  • Batch closed – If the originating batch is closed, the system will cancel the original invoice detail line item, and if you selected a partial cancellation, will create a new line item for the prorated subscription amount. (If necessary, you can override the prorated subscription amount on this new line item.)

  • Batch open – If the originating batch is open, the system deletes the original invoice detail line for both a full or partial cancellation. You cannot process a partial cancellation when the originating batch is open.

If a payment was applied to the invoice, you will need to deal with the credit balance. Depending on the type of the payment, you can create a refund for a check payment or credit a credit card payment. (For more information, see Issuing a refund by check or Issuing a credit card refund and Transferring a payment from one invoice to another.)

Save & close the invoice.

Changing a subscription

In this situation, the customer wants to change their current subscription to a different publication, so you must cancel the current subscription using a full or partial cancellation, and then create a new subscription transaction with a different subscription benefit and rate. See Canceling a subscription; see also Creating a subscription invoice.

Terminating a single subscription

In this situation, you want to manually terminate the customer’s current subscription without changing the invoice detail line charges.

This section describes how to terminate a subscription and the system rules that apply based on batch status and payments within the invoice. When you terminate a subscription, there are no changes to the invoice detail line item charges. The subscription is no longer eligible for renewal processing or the galley utility.

Note

The Galley Utility will not select any subscription renewal billing records that have a status of terminated.

These instructions terminate the current subscription from within the invoice detail. You may also terminate from the list view of renewal billing records by selecting the checkbox next to the current renewal billing record and clicking Terminate on the List View toolbar of the list of renewal billing records.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to terminate a subscription. In the Navigation Pane of the customer’s record, click Invoices. Locate and open the Current subscription invoice that needs to be terminated.

Click Select Batch to select the appropriate open batch based on your organization’s business rules. For information about batches, see Batch overview.

Double-click the subscription product detail record to open the benefit entry form.

  • Click Terminate on the benefit entry Record toolbar.

  • In the Renewal Billing Termination dialog, select the reason you are terminating this subscription, and then click OK to process and return to the invoice.

Save & close the invoice. The customer’s related renewal billing record for the terminated subscription will show a benefit status of Terminated.

Reinstating a terminated subscription

If a subscriber’s Current renewal billing record has been terminated for non-payment, you can reinstate the subscription by applying full payment to the current subscription invoice.

Important

You can only reinstate a Current subscription that was terminated for non-payment. Payments applied to a Past or Upcoming subscription invoice will not reinstate the current subscription.

From any of the UX work areas on the Navigation Tile Bar, click Accounts or Contacts. Open the account or contact where you want to reinstate. In the Navigation Pane of the customer’s record, click Invoices. Locate and open the Current subscription invoice.

Hint

The current subscription invoice also can be found within the Current renewal billing record for the subscription.

Click Select Batch to select the appropriate open batch based on your organization’s business rules. For information about batches, see Batch overview.

Click the New Transactions > Payments & Adjustments button on the invoice Record toolbar and select the payment type. Enter the full payment received for this subscription. (For more information, see Payment and Adjustment Transactions.) Save & Close the payment transaction and return to the invoice. Save & Close the invoice.

To verify that the invoice was paid and the subscription resumed, in the Navigation Pane of the account or contact’s record, click Renewal Billing, and then double click the current renewal billing record for this subscription. Verify that the Benefit Status is Reinstated, and that the Expiration Date and Paid through Date have increased by the correct subscription term. The Terminated Date and Reason will still display the information from this subscription being terminated as a reference for reporting.

Chapter 29: Subscription Processing

Similar to dues renewal procedures, you will also need to generate renewal invoices and terminate expired subscriptions. Additionally, for subscriptions you are able to generate galleys for mailing your publications to paid subscribers and to your members who may receive the publication as a membership benefit.

This chapter includes the following sections:

  • Subscription renewal process overview

  • Creating a batch for subscription renewal

  • Generating a subscription invoice report

  • Generating subscription renewal billing invoices

  • Verifying subscription renewal process results

  • Subscription termination overview

  • Generating a subscription termination report

  • Terminating expired subscriptions

  • Mailing labels and galley overview

  • Generating the pre-galley edit report

  • Using the Galley Utility

  • Viewing galley information

  • Generating the post-galley edit report

Subscription renewal process overview

Typically, new subscribers are entered into the system all throughout the year because even if your organization’s publication is only issued twice a year, subscribers can subscribe at any point in time. If your subscription benefit is anniversary-based, you will potentially have subscriptions expiring every month of the year.

  • The subscription renewal process includes performing the following four procedures, in this order:

  • Create a batch for the subscription renewal process. The subscription renewal process requires its own batch for the renewal invoices.

  • Generate a subscription invoice report. You can generate either the Subscription Invoice Detail Report or the Subscription Invoice Summary Report to view a list of paid subscribers whose subscriptions need to be renewed.

  • Generate renewal billing invoices. In this procedure, you will select the subscription renewal benefit you are renewing, and enter the subscription expiration dates you want to include in the process.

  • Verify the renewal process results.

The timing for performing this process will depend on your organization’s policy for when you need to send renewal notices. For example, if your policy is to give subscribers two months’ notice that their subscription is expiring, you will perform this process in January for subscriptions that expire on March 31st. This gives you enough time to mail them the 1st notice and then any follow up notices.

Important

Based on the benefit and expiration date range entered, subscription renewal processing relies only on information in the renewal billing records where cycle state = Current, benefit status = New, Renew or Reinstated, and no related renewal billing record where cycle state = Upcoming exists. Renewal billing records flagged as Do Not Renew will be ignored.

Creating a batch for subscription renewal

Before you can perform the subscription renewal process in UX Online, you must create a batch for the renewal transactions. A batch is a control mechanism that assigns an ID and date to every transaction entered into the system. The subscription renewal process requires its own separate batch.

You should create batches that meet the requirements of your organization’s policies and procedures regarding the entry of cash, check, or credit card payments. For more information, see Creating a batch in UX Online.

Note

If you do not have rights to access the Batch Log area, communicate with the appropriate people within your organization to have this done. You can set up alerts in CRM to remind yourself and others that this needs to be done.

Generating a subscription invoice report

Before you generate renewal billing invoices, we recommend that you generate and review the Subscription Invoice Detail Report or the Subscription Invoice Summary Report. These reports show all paid subscribers whose subscriptions need to be renewed. These are subscribers whose subscriptions will be expiring in a date range you enter.

You can also print these reports for your records. Both reports show the same information but one is more detailed than the other.

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online reports. In the Reports list, locate and open the UX Subscriptions Invoice Detail or UX Subscription Invoice Summary report.

  • Select the benefit (publication) for this report.

  • Enter the date range for this report in the Expire Date From and Expire Date To fields. This will be the range of expiration dates you are preparing to perform the subscription renewal process for. For example, to generate this report for subscriptions expiring in November 2016, enter the dates 11/01/2016 and 11/30/2016.

  • Select the Cycle State = Current.

Click Run Report. The report will appear on your monitor. (You can view the report online, print it, or save it as a PDF file if needed.) Use this report to verify counts as well as the subscription rates assigned to each subscriber and the amounts charged.

Note

If you have not performed the renewal process for these invoices yet, all invoices on this report should show a zero balance unless you allow renewal on unpaid invoices.

Generating subscription renewal billing invoices

When you generate subscription renewal billing invoices, you will select the subscription renewal benefit you are renewing, and enter the subscription expiration dates you want to include in the process. The timing for performing this process will depend on your organization’s policy for when you need to send renewal notices. For example, if your policy is to give subscribers two months’ notice that their subscription is expiring, you will perform this process in January for subscriptions that expire on March 30th. This gives you enough time to mail them their 1st notice and then any follow up notices.

We recommend that you generate either the Subscription Invoice Summary Report or the Subscription Invoice Detail Report before performing this procedure. These reports show all paid subscribers whose subscriptions will be expiring in a date range you enter. You can use the total number of invoices on these reports to verify that the correct number of invoices will be generated by this process. For more information, see Generating a subscription invoice report.

Important

Based on the benefit and expiration date range entered, subscription renewal processing relies only on information in the renewal billing records where cycle state = Current, benefit status = New, Renew or Reinstated and there is no related renewal billing record where cycle state = Upcoming. Renewal billing records flagged as Do Not Renew will be ignored.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Manager > Generate Renewal Billing Invoices to open the Generate Renewal Invoices dialog.

Enter the appropriate renewal information:

  • Expire Date – Click the Calendar button and select the expiration date that is up for renewal. This date will always be the last day of the month. The date you enter must match the date you entered when you created the UX Subscription Invoice Detail Report.

  • Batch – Click the Lookup button to select the batch you created for this process.

  • Module – Click the Lookup button and select Subscriptions. This is optional.

Important

If you do not select a module, you will be able to select benefits from both Membership and Subscription modules.

  • Benefit – Click the Lookup button to select the subscription benefit you are running the renewal process for. You can select more than one benefit if you want to. To do so, press and hold the Ctrl key while clicking the benefits.

Important

If you do not select a benefit, the system will run the renewal process on all renewal benefits within the selected module.

  • Customer – If you are generating a renewal invoice for a single customer, click the Lookup button to select the customer you are running the renewal process for.

Click OK to start the process. A message will appear displaying the number of renewal billing records found that meet the search criteria you entered and meet the conditions for eligible renewal billing records. Verify that this number matches the number of invoices shown on the Subscription Invoice Detail Report or the Subscription Invoice Summary Report.

Click OK to continue.

Important

Please note that this process may take several minutes to complete if there is a large number of records to process. After you click the OK button, allow the system several minutes to generate the invoices and related renewal billing records. Do not attempt to re-run the process.

When the process is finished, we recommend that you print the Subscription Invoice Detail Report to be sure the invoices were created properly. For more information, see Generating a subscription invoice report.

Verifying subscription renewal process results

When you perform the subscription renewal process, two things occur:

  • A subscription renewal invoice is created with a balance due. You can verify this by viewing a subscription invoice report, by using the Invoice Detail view or by viewing subscribers’ invoice lists.

  • A new renewal billing record is created with a new Cycle Start Date for the upcoming renewal year. The cycle state for this renewal billing record will be Upcoming.

Subscription invoice reports

You can review the renewal invoices by generating the Subscription Invoice Detail Report or the Subscription Invoice Detail Report again, entering the same subscription benefit and date range and comparing it to the report you generated prior to generating the renewal invoices. The report should match the version you ran prior to running the renewal process except now a Balance due amount will show. For more information, see Generating a subscription invoice report.

Subscription termination overview

Similar to membership dues termination procedures, you have the option of terminating past due subscribers using the Renewal Billing Termination process. This process should be part of your monthly subscriber maintenance and is used to terminate many subscribers at one time.

Running the renewal billing termination process updates the renewal billing records Benefit Status to Terminated, enters a Terminated Date, and populates the Termination Reason field with the selected reason. Based on the galley setup grace periods, these subscribers will no longer be included in the Galley process. These subscribers will no longer be included in the subscription renewal process.

Important

Subscription termination processing relies only on information in the renewal billing record where cycle state = Current and benefit status <>Terminated. It does not terminate Past or Upcoming subscription renewal billing records.

The subscription termination process includes performing the following procedures, in this order:

  • Generate the Subscription Termination Report. This report shows a list of subscribers whose subscriptions need to be terminated.

  • Terminate subscriptions. In this procedure, you will select the subscription module and subscription renewal benefit you are terminating, and then enter the subscription paid-through date you want to include in the process.

  • Verify the termination process results.

Note

You can set up alerts within CRM to remind yourself and others when this process will be run.

If you have only a few subscriptions to terminate, you can choose to terminate them individually. For more information, see Terminating a single subscription.

Subscription records eligible for termination

The UX Online Renewal Billing Termination Process uses the following renewal billing record criteria to identify subscription records that will be selected for termination:

Benefit Status

New, Renew, Reinstated

Cycle State

Equals Current

Do Not Renew

Does Not Equal True

State Code (Status)

Active

Module

Equals <optional prompt> – select Subscriptions

Benefit

Equals <optional prompt>

Paid Through Date

Equals <required prompt>

CertificationID

NULL

Generating a subscription termination report

Before you run the renewal billing termination process for your subscribers, we recommend that you generate and review the UX Subscription Termination Report. This report shows all subscriptions that need to be terminated because they have expired. You can also print this report for your records.

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online reports. In the Reports list, locate and open the UX Subscription Termination Report.

  • Select the benefit (publication) for this report.

  • Enter the date range for this report in the Paid Through Date From and Paid Through Date To fields. This will be the range of dates you are preparing to perform the subscription termination process for. For example, 3/1/2016 to 3/31/2016.

Click Run Report. The report will appear on your monitor. You can view the report online, print it, or save it as a PDF file if needed. Use this report to verify the count of the subscriptions you will be terminating.

Terminating expired subscriptions

When you terminate subscriptions, you will select the subscription renewal benefit you are terminating, and enter the subscription paid-through date you want to include in the process. The timing for performing this process will depend on your organization’s policy for when you need to terminate subscriptions.

We recommend that you generate the UX Subscription Termination Report before performing this procedure. This report shows all paid subscribers whose subscriptions need to be terminated because their subscription has expired. You can use the total number of subscriptions to terminate on this report to verify that the correct number of subscriptions will be terminated by this process. For more information, see Generating a subscription termination report.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Renewal Manager > Renewal Billing Termination Process.

In the Termination Process dialog, enter the appropriate termination information:

  • Paid Thru Date – Click the Calendar button and select the expiration date of the subscriptions you want to terminate. This date will always be the last day of the month you are running this for.

  • Module – Click the Lookup button and select Subscriptions.

  • Benefit – Click the Lookup button to select the publication you are running this termination process for.

  • Reason – Select a termination reason from the menu. This reason will be recorded on each subscribers detail invoice record.

Note

The Termination Reason list can be modified in your client-specific solution package to add additional reasons reflecting your organization’s reasons by your system administrator. Do not delete or edit existing termination reason option set values. Because a Termination Reason field exists in both the Renewal Billing entity and in the Renewal Process entity, you must add the client-specific option to the Termination Reason field in both entities. Contact your Protech account manager for guidance on the recommended framework for core entity customization of termination reason option set fields.

Click OK to start the process. A message will appear displaying the number of subscription renewal billing records that match the search criteria. Verify that this number matches the number of terminations shown on the UX Subscription Termination Report. (For more information, see Generating a subscription termination report.)

Click OK to proceed.

Note

If there are many subscription records to be terminated, UX Online will display a green progress bar while the process is running. When the process is complete, wait for the system to complete updating all transaction and renewal billing records before you run the Subscription Termination report again.

When the process is finished, we recommend that you re-print the Subscription Termination Report again to make sure the subscriptions were terminated properly. For more information, see Generating a subscription termination report.

Mailing labels and galley overview

A galley is a file that identifies all the accounts or contacts who should receive a particular publication. These recipients could include members who receive the publication as part of their membership, members who have paid for an additional subscription, non-members who have subscribed, and any other recipients. You will use the UX Online Galley Utility to update the galley. This file is then used to print labels in-house or to create an Excel or CSV export file that can be sent to a mailing house for label printing. The galley file can also be used for BPA (Business Publication Audit) reporting.

Important

The galley utility relies only on information in eligible renewal billing records where cycle state = Current. Past or Upcoming renewal billing records are excluded from this process.

The instructions in this part of the documentation assume that you have set up galley details for your publications. For more information, see Setting up galleys and galley details.

The process of generating mailing labels includes performing the following four procedures, in this order:

  • Generating the Pre-Galley Edit Report. This report lists all members who are eligible to receive an issue, plus all current subscribers.

  • Using the Galley Utility.

  • Verify the galley run with the Post-Galley Edit Report. You will compare this report to the Pre-Galley Edit Report; the accounts and contacts on the two reports should match.

After the mailing label process is completed, you can use the galley file to print labels in-house, or you can create an Excel or CSV export file that can be sent to a mailing house for label printing. For more information, consult your Protech representative.

Important

Because these reports and the Galley Utility will be using your subscription transaction data, be sure all current subscription transaction processing has been completed, and that no subscription transactions are entered or posted until after the Galley Utility has run and the reports have been generated.

Generating the pre-galley edit report

Prior to running the Galley Utility program, it is recommended that you first run the UX Subscriptions Pre-Galley Edit Report to see a list of all current subscribers and members who are eligible for the next issue.

The current subscriber list for a publication includes all subscribers whose expiration date has not passed, as well as those who are still within the grace period set up for the galley. For example, if you are running this report for a publication date of 10/01/2009, any subscriber whose expiration date falls after that date will be included. In addition, if the grace period for a publication rate is 2 months, then any subscriber whose expiration date is after 08/01/2009 will also be included in the report. This report will also show all active members who are to receive your publication as part of their membership benefits.

Important

Because this report and the Galley Utility will be using your subscription transaction data, be sure all current subscription transaction processing has been completed, and that no subscription transactions are entered or posted until after the Galley Utility has run and the reports have been generated.

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online reports. In the Reports list, locate and open the UX Subscriptions Pre-Galley Edit Report.

  • In the Module field, select All, Membership, or Subscriptions in the Module field to indicate which records you want to see in this report.

  • In the Galley Publication field, select the publication for which you want to run the Galley Utility.

  • Enter the issue date you are running this galley for.

Click Run Report. The report will be generated and appear on your display. We recommend that you save this report so you can compare it to the Post-Galley Edit report, which is printed after the Galley Utility is executed. These two reports should match.

Using the Galley Utility

The Galley Utility is a program that selects all the paid subscribers and members defined in the subscription setup who are to receive a copy of each issue of your publication. Each time an issue is due out, you will run the Galley Utility to support mailing your publication.

  • For subscribers, the Galley Utility will check the subscription rates defined within the Galley Details setup for each publication. For each subscription rate defined in the galley detail setup, the Galley Utility will select those records having an eligible current renewal billing record for one of the rates defined (provided the subscription expiration date is greater than or equal to the issue date the galley is being run for, or within the grace period defined in the galley setup).

  • For members, the Galley Utility will check the membership dues rates defined within the Galley Details setup for each publication. Any account or contact that has an eligible renewal billing record for one of the membership dues rates in their record will be selected during the Galley Utility run (provided their membership dues expire date is greater than or equal to the issue date the galley is being run for, or within the grace period defined in the galley setup).

Important

Because the Galley Utility and the galley edit reports will be using your subscription transaction data, be sure all current subscription transaction processing has been completed, and that no subscription transactions are entered or posted until after the Galley Utility has run and the reports have been generated.

The galley utility relies only on information in eligible renewal billing records where cycle state = Current. Past or Upcoming renewal billing records are excluded from this process.

In the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Subscription Manager > Galley Utility to open the Galley Utility process window and enter the data, as follows

  • Galley Publication – use the lookup button to select the publication you are running the galley for.

  • Issue Date – Enter the publication issue date you are running the galley for. This date represents the next issue date that your publication is due out for mailing to your subscribers and members. For example, if your organization has a publication that is issued monthly, you would run this process each month. If your organization has a publication that is issued quarterly, you would run this process each quarter, etc.

Note

Based on the Issue Date entered in this field, UX Online subtracts the number of months defined as the subscription grace period. For example; if you are running the Galley for 06/01/2016 and the publication you are running this for has been set up to have a 2 month grace period, then the Galley utility will recalculate the issue date as 04/01/2016. Based on the 04/01/2016 issue date the galley calculates, any subscriber who has a subscription to this publication where this issue date is less than or equal to the subscription expire date will be selected. Or, another way to think about this logic, is that all subscribers who have a subscription expiration greater than 04/01/2016 will be selected. (You can set up you publications to have no grace period or as many months as appropriate.)

  • Prior Galley Run – use the lookup button to select the last date this process was run for this publication. This will help you keep track of when this process was last run and that it is being run on a timely basis.

Click OK to start the process.

A confirmation dialog box showing the number of records selected for this galley run will appear. Keep in mind that the Galley is not only selected paid subscribers but all members who are designated to receive this publication as part of their membership benefits, plus any complimentary subscriptions.

Note

When the process is complete, wait for the system to complete updating all galley records before you view or print galley data.

Viewing galley information

To see an on-line view of the galley data selected for this issue date, in the Navigation Tile Bar, select the Membership work area > Membership/Subscriptions > Subscription Manager > Galley View to open the List View of Active Galley records. This list opens in a new window.

This list shows all paid subscribers and members who have been selected by the Galley Utility to receive a publication. You may click on any of the column headers to sort the data in a manner that is most helpful for viewing this data or you can search by benefit, issue date, etc.

Note

The galley retains all data selected for previous issues. Printing your labels is a separate process from running the galley. When the data is added to the galley file, you can print your labels whenever appropriate. Or, you can use this file to export to Excel and send it to your mailing house.

Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Address changes in the galley

If your organization relies on the UX Subscription Galley Export to send to your mailing house, and a temporary address change is necessary after you have run the galley, you must change the address in the UX Subscription Galley Export report for this issue. If you want the address change to be permanent, you should change the address in the account or contact record or, if appropriate, in the benefit recipient record.

If your organization relies on an export of Galley Detail records to send to your mailing house, and a temporary address change is necessary after you have run the galley, you can change the address in the Galley Detail record before exporting the records to Excel. If you want the address change to be permanent, you must change the address in the account or contact record or, if appropriate, in the benefit recipient record.

Note

Address changes to records captured in the Galley Run Log (Galley Detail records) are not captured in the UX Subscription Galley Export report. While the Galley Detail records returned in this report are driven from the selected Galley Run Log, the address data for those records is not. For address data, this report looks first at the respective benefit recipients Ship To Address and if this address is null, the reports pulls address data from the respective contact or account record primary address.

Opt-out requests in the galley

In cases where a member or subscriber has requested that they not receive a particular issue, you may simply remove their Galley Detail record from the galley for that issue date. This should be done before creating mailing lists or labels.

In the Active Galley List View, double-click to open the Galley Detail record for the account or contact that you wish to remove from the galley. Click the Delete button on the Record toolbar.

Note

Deleting a record from the galley for a particular issue date only removes that account or contact for that issue. If a paid subscriber should be permanently removed from the galley, you need to cancel or terminate their subscription. If a member asks to be excluded from publication mailings, they should be flagged for opt out on their benefit recipient record.

Generating the post-galley edit report

After running the Galley Utility program, it is recommended that you print the UX Subscriptions Post-Galley Edit Report to verify that the paid subscribers and members who are eligible for this issue were selected in the process. This report should be compared to the pre-galley edit report, which is printed before the Galley Utility is executed. (See Generating the pre-galley edit report.) These two reports should match, except where you have manually deleted a galley record.

Important

Because this report and the Galley Utility will be using your subscription transaction data, be sure all current subscription transaction processing has been completed, and that no subscription transactions are entered or posted until after the Galley Utility has run and the reports have been generated.

This report looks directly at the Galley Detail file based on issue date selected when the report is executed.

Note

If you deleted any galley records via the Galley View, then these two reports will be off by the number of records you deleted from the galley view.

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online reports. In the Reports list, locate and open the UX Subscriptions Post-Galley Edit Report.

  • In the Module field, select All, Membership, or Subscriptions in the Module field to indicate which records you want to see in this report. This should match the selection made in the Pre-Galley Edit Report.

  • In the Galley Publication field, select the publication for which you ran the Galley Utility.

  • Enter the issue date you ran this galley

Click Run Report.

Product Sales

Part 7: Product Sales

This part of the documentation describes how you can use UX Online to manage the products that your organization sells.

This information is divided into the following chapters:

Chapter 30: Product and Kit Product Setup

Product setup for your organization can apply to several things, including products to support membership dues, subscriptions, payments, etc.

Note

UX Online 8 currently does not support Dynamics CRM Product Properties, Product Bundles, or Product Families.

This documentation describes the components available in the UX Online Product Sales Manager as they relate to sales order products and product kits. These components include:

  • Warehouses

  • Product Setup

Note

For product setup other than sales order products and product kits, see the following:

During product setup, you will be working with a combination of related entities including price lists, unit groups, and prices.

You can also set up the framework needed for automating the accounting entries needed for product sales returns and creating RMAs (Return Merchandise Authorizations).

Note

In order to create sales order products in UX Online, you must first complete the setup for the accounting company (or companies) and the chart (or charts) of accounts in the UX Online Organizational Settings. For more information, see Accounting Setup.

This information is divided into the following sections:

  • Warehouse records

  • Creating a warehouse record

  • Viewing product records associated with a warehouse

  • Creating a new sales order product

  • Creating product prices

  • Creating a kit product

  • Adding kit components

  • Modifying a kit’s components

  • Managing inventory for kits

  • Creating an invoice comment product

  • Product sales RMAs and returns setup overview

  • Creating a restocking fee product

Warehouse records

UX Online uses the relationship between sales inventory products and your warehouse records to keep track of the item quantities available to sales order transactions.

You must set up warehouse records in UX Online in the following circumstances:

  • If you have integrated accounting system inventory control, you can set up as many warehouse records in UX Online as you have available sites in your accounting system.

  • If you have internal inventory control, UX Online logic supports a single warehouse record.

If you have no inventory control, you do not need to set up warehouse records and you can skip this procedure.

See Creating a warehouse record for additional information.

Creating a warehouse record

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Warehouses to open the List View of Active Warehouse records. This list opens in a new window. Click New on the List View toolbar to create a new warehouse record.

In the General section of the Warehouse record, complete following:

  • Name – Enter the name of the warehouse.

  • Warehouse Code – Enter a code for the warehouse.

Important

If your organization relies on inventory control that is integrated with your accounting system, you must enter a warehouse code that exactly matches the warehouse ID in your accounting system.

  • Address 1 – Enter the first address line for this warehouse. (This field is optional.)

  • Address 2 – Enter the first address line for this warehouse. (This field is optional.)

  • City – Enter the city where this warehouse is located. (This field is optional.)

  • State or Province – Enter the state or province where this warehouse is located. (This field is optional.)

  • Postal Code – Enter the ZIP or postal code for this warehouse. (This field is optional.)

  • Country – Enter the country where this warehouse is located. (This field is optional.)

Click Save. When you save a new warehouse record, the additional options in the Navigation Pane are activated, including:

Warning

The Workflows option displays the system log file for CRM workflows associated with this warehouse record. Do not make any changes to this information.

Click Save & Close to save the warehouse record and return to the Warehouse list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Viewing product records associated with a warehouse

You can view a list of Sales Inventory products related to a warehouse from within the warehouse record.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Warehouses to open the List View of Active Warehouse records. This list opens in a new window. Open the warehouse record you want to view. To view the list of products associated with this warehouse, click Products in the Navigation Pane.

Creating a new sales order product

When setting up products, the choices you make will affect the integration to your accounting system (including the inventory module), transaction processing, freight, tax, and fulfillment processing. Prior to setting up a product, review your product characteristics and plan the setup that will best support your business processes.

Note

This procedure describes setting up sales order products; however, UX Online uses product records to manage payments, taxes, freight charges, and other records as described in other areas of this documentation. For product setup other than sales order products and product kits, see the following:

For related information on creating product kits, see Creating a kit product.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to display a List View of Active Products. This list opens in a new window.

Click Add Product on the List View toolbar to create a new product record. In the General section at the top of the Product record, complete the following information:

  • Product ID – Enter an ID for the product. (This ID must be unique.)

Note

For products with a product type of “Sales Inventory,” you must enter an ID that is the same as the accounting system record code for this product (that is, the Product ID in Dynamics GP or Dynamics SL). This field establishes the link to the accounting system record where the product’s quantity information is maintained.

  • Name – Enter the name of the new product.

  • Unit Group – Click the Lookup button, then select Each and click OK.

  • Default Unit – Click the Lookup button, then select Each and click OK.

  • Currency – If you are working in a single currency environment, by default, your preferred currency appears in this field. Otherwise, lookup and select the Currency for this product.

  • Product Type – Select one of the following product types for this new product:

Note

The product type you choose is important because it triggers special program logic during transaction processing. While there are multiple options available in this list, when creating a sales order product, you must choose either Sales Inventory or Sales Non-Inventory.

    • Sales Inventory – Select this option if you are setting up a product that is integrated with the accounting system inventory control, or if it is using internal (UX Online) inventory control.

    • Sales Non Inventory – Select this option if you are setting up a product that is not integrated with the accounting system inventory control, and it is not using internal (UX Online) inventory control.

  • Subject – This field is optional. If your organization relates products to subjects, click the Lookup button to select the subject.

Note

You must have subjects set up in your system to use this feature. Please refer to Dynamics CRM user documentation for information on setting up subjects.

In the Accounting area, enter the following accounting setup information for this product:

  • Company – The system will automatically populate this field with the company record flagged as the default company in your set up. If you need to make a change, click the Lookup button to select the appropriate accounting system company for this product. This controls where accounting data will post during the posting process and controls the display of GL accounts available in the GL account lookup fields.

  • Reimbursable – Select Not Reimbursable. Do not select any of the other options for sales order products.

  • Primary GL Account – Click the Lookup button to select the GL account to which accounting data will post when you post UX Online transactions that include this product. This is typically a revenue account for product sales products.

  • AR GL Account – Click the Lookup button to select the correct AR account.

  • Cash Basis – Leave the default setting of No.

  • Control Accrual Basis via AR Utility – This field is disabled and not required for this product type.

  • Secondary GL Account – This field is disabled and not required for when the Primary GL Account is a revenue account.

  • AP GL Account – This field is disabled and not required for this product type.

In the Costs area, enter the product cost setup information as shown:

  • Default Price List– Leave this field blank. When you save this product record for the first time, this field will automatically display the Non Member price list. Product pricing is not controlled by this field. For more information, see Creating product prices.

  • Decimals Supported – Enter the number of decimal places needed for this product’s currency format. For example, the default value of 2 is for a 0.00 currency format.

  • List Price – Enter the list price of the product. This value is used in conjunction with the price record for products that use the Percentage calculation method and is the default value for price/amount in system created price records. For more information, see Creating product prices.

  • Single Currency – Applies only to customers in a multi-currency environment where the application parameter PAMultiCurrency.Enable = true. For those customers, mark this checkbox only if you want to limit system-created prices records for this sales product to the Currency entered for this product. For additional information, see Managing Single Currency Sales Products, Meetings and Exhibits.

  • Apply Freight? – This field serves three purposes: first, it is the indicator that this product will be eligible for order fulfillment processing; second, it is the indicator that this product is eligible for calculating freight charges; third, it is the indicator that this product is eligible for RMA (return merchandise authorizations).

    • Mark this checkbox if you want UX Online to calculate freight charges for this item when the Calculate Freight button is clicked during invoice transaction processing. (For more information on freight charges, see Freight Setup.)

    • Mark this checkbox if you want to use the Product Sales EasyPrint Packing Tickets and UX Online Order Shipping Fulfillment process for this product. (For more information, see Sales Order Fulfillment.)

    • Mark this checkbox if you want to use the UX Online RMA process for managing product returns. (For more information, see Product sales RMAs and returns setup overview.)

  • Is it a Bill Recipient? – This field is not applicable and is disabled for sales product setup.

In the Tax Product Info area, enter the following information:

  • Taxable – If this product is taxable, mark the Taxable checkbox . If this option is checked, UX Online calculates tax when the Ship To State field contains a State with sales taxes.

  • Tax Rate – Leave this field blank. This does not apply to product sales.

If you selected product type = Sales Inventory, in the Inventory and Backorder Information area, enter the following information:

Note

This section is not visible on the new product setup record unless product type = Sales Inventory.

  • Warehouse – This field is required for product type = sales inventory. Click the Lookup button to select the default warehouse that will be used to fulfill sales for this product.

  • Quantity on Hand – If you are using internal (UX Online) inventory control for this product, enter the quantity on hand. (For more information, see Organization Setup.) If you are using the accounting system inventory module for this product, this field is not used.

  • Current Cost – Leave this field blank.

  • Allow Backorder? – Mark this checkbox if the product type = Sales Inventory and you want to allow back order processing with this product in the back office.

  • Allow Partial Backorder? – Mark this checkbox , if you marked the Allow Backorder? option, and you want to allow partial back orders for this product in the back office. If your organization does not allow partial backorders, do not mark this option.

Note

The Allow Backorder? and Allow Partial Backorder? settings apply only to sales inventory transactions processed in the back office. These settings do not control backorders of sales inventory products purchased on the web. If a sales inventory product is published to the web, it is subject to both full and partial backorder by default.

In the Professional Development area of the General section, enter the following information:

  • Course – If this product setup is to support enrollment in a course via a product purchase, use the Lookup to select the course. For information about creating products for Professional Development certification, see Certification and Accreditation Setup.

In the Description section of the new product record, enter the following information as appropriate for your new product setup:

  • Kit Product? – If this product setup is a kit, mark this option. For example, a dinner place setting would be a kit product, but the plate, salad bowl, coffee cup and saucer would be kit components.

Note

A product can be both a kit product and a kit component product for a different kit product. For more information, see Creating a kit product.

  • Vendor – Enter the vendor for this product. This field is optional and informational only.

  • Vendor Part Number – Enter the vendor’s part number for this product. This field is optional and informational only.

  • URL – Enter a URL (that is, a web address) for this product. For example, you could enter the web address of the vendor’s online catalog page for this product.

  • Stock Weight – Enter the weight of one unit of this product. This value is used to calculate freight charges when the calculation method (PAShipping.Standard.CalculationType) is “shipmentweight.” You must enter the product’s weight in the unit of weight defined in the UX Online application parameters configuration record called “PAShipping.WeightUnits.” For more information, see Freight Setup.

Note

If this product setup is for a kit, do not enter a stock weight. When freight charges are calculated based on weight, the calculation for the kit will be based on weight of the kit component products – not the kit product.

  • Stock Volume – This field is not used.

  • Description – Enter a description of this product. This field is optional and informational only.

The Web section is used with Protech’s MX Online, and will be set as needed during that implementation. Do not change these settings.

  • Publish to Web – This is used to indicate whether the product is available for purchase online. Do not change this field.

  • Author Name – If this product is a book, enter the name of the author. This field is optional.

  • Cover – If this product is a book, enter the book format. For example, paperback, hard cover, or spiral bound.

  • Image – Do not change this field.

  • Language – This optional field can be used to support reporting and MX Online product search by language. There are no default options for this option set field, although typical values might include English, Spanish, and the like. If options for this field are required by your organization, contact your Protech representative or your System Administrator for customizing this field in your organization’s custom solution.

  • File Name – Specific file name for a digital media file that can be downloaded from the online store. Do not change this field. It will be set as needed during that implementation.

  • Promote – This indicates whether the product will be featured online. Do not change this field. This is used with Protech’s MX Online, and will be set as needed during that implementation.

Note

You cannot promote (feature) more than three products on MX Online.

  • Members Only – Do not change this field. This is used with Protech’s MX Online, and will be set as needed during that implementation.

  • Has Variants – Do not change this field. This is used with Protech’s MX Online, and will be set as needed during that implementation.

  • Category – This optional field can be used to support reporting and MX Online product search by category. There are no default options for this option set field, although typical values might include book, manual, logo, or topics such as Legal Issues. If options for this field are required by your organization, contact your Protech representative or your System Administrator for customizing this field in your organization’s custom solution.

  • ISBN – If this product is a book, enter the International Standard Book Number (ISBN), a 10-digit number that uniquely identifies books and book-like products published internationally. This field is optional.

  • Edition – Enter the edition for the published material, if applicable. This field is optional.

  • Number of Pages – Enter the number of pages for printed or downloadable material, if applicable.

  • Published On – Enter the published date for the product.

  • Downloadable – This indicates if this product is available for electronic download online. Do not change this field. This is used with Protech’s MX Online and will be set as needed during that implementation.

  • Web Member Related – Do not change this setting. This is used with Protech’s MX Online and will be set as needed during that implementation.

  • Download Available Days – This indicates the number of days a downloadable product is available for download when purchased online. Do not change this field. This is used with Protech’s MX Online, and will be set as needed during that implementation.

  • Quantity Discount – Used in MX OnlineProduct Catalog to determine if MX displays a pricing grid for multiple quantities. Do not change this setting. It will be set as needed during that implementation.

Click Save. After saving this record, other options on the Navigation Pane are activated:

  • Click Substitutes to view information about products that can be offered as substitutes for this product. See Working with substitute products for important information.

  • Click Price List Items to view system-created price list items for this product. No changes are needed to this list.

  • Click Prices to set up the pricing structure for this product. For more information, see Creating product prices.

  • Click Promotions to view promotion records created for this specific sales product. Do not create promotions from this location. See Creating a promotion record for more information about product-specific promotions.

Click Save & Close to save the product and return to the Active Products list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Creating product prices

You can define simple or complex price schedules for product sales transactions by setting up price records for your products.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to display a List View of Active Products. This list opens in a new window.

Locate and open the sales product record where you want to set up pricing. Click Prices in the product Navigation Pane to open the Prices Associated View of existing price records for this product.

Important Note

Pricing for additional benefit recipient charges is based on cycle start date of the related renewal billing record. The system will select the price record where the cycle start date falls within the price record date range of the additional benefit recipient product.

To create a new price record, click Add New Prices on the List View toolbar to create a new price record. In the General section of the Prices record, complete the price entry fields:

  • Price Level – Click the Lookup button to select the price level for this price record.

  • Name – Defaults to the name of the selected Price Level record.

  • Calculation Method – Select the price calculation method for this product: Flat Rate or Percentage. Select Flat Rate if the price is a flat amount. Select Percent to calculate the price as a percentage of the List Price entered in the product setup General section. Both calculation methods apply pricing to the product for the product during the date range and for the value range defined below.

  • Value Minimum – Enter the lowest quantity for which this price record applies. The minimum acceptable value is 1. For example, if this price applies to purchases of 10 or more units of the product, enter 10. To view a matrix of scenarios and expected results, see Price record transaction scenarios.

  • Start Date – Enter the starting date for which this price record applies. During transaction processing, this date is compared to the transaction date.

  • Factor – Leave this field blank. It does not apply to product sales price records.

  • Rate – Leave this field blank. It is not used for sales order products.

  • Currency – Defaults from the product setup currency.

  • Price/Percent of List Price – Enter the price or the percentage to multiply by the list price for this item, using the following guidelines:

    • If the Calculation Method for this price record is Flat Rate, enter the price of the product during the date range and for the value range set for this price record. For example, if you want to charge a flat rate of $100.00, enter 100.00 in this field.

    • If the Calculation Method for this price record is Percentage, enter the percentage that will multiplied by the List Price entered on the Product record. For example, if you want to charge 30% of the List Price, enter 30.00. If the list price is $100.00, the price returned will be $30.00. If you want to charge 150% of the list price, enter 150.00. If the list price is $100.00, the price returned will be $150.00.

  • Value Maximum – Enter the highest quantity for which this price record applies. For example, if this price applies to purchases of 20 or less units of the product, enter 20.

  • End Date – Enter the ending date for which this Prices record applies. During transaction processing, this date is compared to the transaction date.

  • Product – Displays the product you are currently working with.

Click Save & Close to save the price record and return to the Price Associated View. Repeat these steps until you have created all the price records required to support the pricing schedule for this product.

Note

We recommend that you verify that the price records you create do not conflict with one another (for example, that date ranges overlap or have gaps, or that the minimum/maximum value ranges overlap or have gaps).

To return to the product setup record, select the Product name in the Top Navigation Toolbar.

Price record transaction scenarios

This topic provides an example of how a price record will be selected during transaction processing.

Assume that you have a product—a coffee mug—with the following price records in the Member price list:

Calculation Method

Price/Percent of List Price

Value Minimum – Maximum

Start – End Date

Flat Price

$5.79

1 – 5

1/1/2016 – 1/31/2016

Flat Price

5.89

1 – 5

2/1/2016 – 5/31/2016

Flat Price

5.99

1 – 5

6/1/2016 – 12/31/2016

Flat Price

5.21

6 – 10

1/1/2016 – 1/31/2016

Flat Price

5.30

6 – 10

2/1/2016 – 5/31/2016

Flat Price

5.39

6 – 10

6/1/2016 – 12/31/2016

If you create an invoice for a member with a batch date of 4/26/2016, and add a product sales transaction for 3 coffee mugs, the batch date falls within the 2/1/2016 – 5/31/2016 date range, and the quantity is between 1 and 5, therefore the system will use $5.89 as the unit price.

If you create an invoice for a member with a batch date of 7/12/2016, and add a product sales transaction for 8 mugs, then the system will use 5.39 as the unit price (the batch date falls within the 6/1/2016 – 12/31/2016 date range and the quantity is between 6 and 10).

Creating a kit product

You can set up kit products, which you can use to sell several products as a single package. For example, you may want to sell several manuals with a particular workshop video as a kit, but you also want the video and each manual to be available for purchase individually. In addition, you may want to track inventory for each individual product.

Note

UX Online 8 does not support CRM Product Bundles for managing product kits and kit components.

A kit product can also be a component of another kit. For example, you can set up a kit of basic training materials that are used with several workshops, and then include that kit in the kits for each of those workshops.

In order to set up kit products, you must first set up the product records for each component of the kit. (For more information, see Creating a new sales order product.) You then can create the kit product, and associate each of the components with it.

Note

During a sales transaction, the price of a kit product is based on the price records set up for the kit product and not on the price records of the kit components. In a similar manner, the available inventory for a kit product is based on the inventory of the kit components.

Create a new product following the standard product setup process. For more information, see Creating a new sales order product.

If you are managing inventory for the kit, select Sales Inventory for the kit product type. If you are not managing inventory for the kit, select Sales Non-Inventory as the product type.

Important

If you are managing inventory for the kit, the kit and all of its components must have a product type = Sales Inventory.

If the kit product type = Sales Inventory, and you want to enable backorders for the kit, mark the Allow Backorder check box in the Backorder and Inventory Info section of the new product form.

Important

Do not check Allow Partial Backorder – partial backorder is not supported for product kits. For more information, see Managing inventory for kits.

In the product setup, mark the Kit Product? check box in the Description section of the new Product form.

Click Save to save the kit product setup and activate Navigation Pane access to Prices and Kit Components.

Click Prices in the Navigation Pane to create or modify price records for the kit product. For more information, see Creating product prices.

Click Kit Components in the Navigation Pane to add kit components. For additional information, see Adding kit components.

To return to the product kit setup record, select the Product name in the Top Navigation Toolbar. Save & Close the kit product once prices and kit components are complete.

Adding kit components

Click Kit Components in the Navigation Pane of the kit product to open the Kit Components Associated View of related kit component records. Click Add New Kit Components on the List View toolbar to open a new kit component record.

In the General section of the Kit Components record, complete all of the required fields as described below:

  • Component – Click the Lookup button to select an existing product that will be a component of this kit.

  • Name – Displays the component product name after you select it in the Component field.

  • Quantity – Enter the quantity of the selected component included with the kit.

  • Product – Displays the product kit product.

Click Save & Close to save this kit component and return to the list of components. Repeat these steps for each component in the kit.

When you have finished adding components to this kit, return to the product kit setup record by selecting the Product name in the Top Navigation Toolbar. Save & Close the kit product once prices and kit components are complete.

Modifying a kit’s components

You can modify the quantity of a kit component, add new components, or remove a component from the kit entirely. Any changes you make will affect new transactions only.

Managing inventory for kits

Inventory control is available for kits only when the kit product and each of its component products are created using product type = Sales Inventory.

Available inventory for a kit is based on the combined availability of the all required quantities of its component products. There is no partial backorder available for kits or its components when sold as a kit. For instance, in the scenario where a Sales Inventory kit is comprised of two Sales Inventory component products: Component A and Component B, and one complete kit contains 2 each of Component A and 3 each of Component B:

Number of Kits

Available

Component A

Available Inventory

Component B

Available Inventory

1

2

3

1

6

3

0

1

3

2

4

8

For kits that do not require inventory control create the kit product and each of its component products using product type = Sales Non-Inventory. If you add a Sales Inventory product as a component to a Sales Non-Inventory kit, there is no inventory control available.

Creating an invoice comment product

You can set up your system to allow users to enter comments on product sales invoices and packing tickets. To do this, you must create a comment product record.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to display a List View of Active Products. This list opens in a new window.

Click Add Product on the List View toolbar to create a new invoice comment record. The Product record appears. In the General section of the Product record, complete the following information:

  • Product ID – For a packing ticket comment, enter exact text ‘PACKINGTICKETCOMMENT’ to identify the product as a packing ticket comment. For an invoice comment, enter a short meaningful code that identifies the product as an invoice comment – anything other than ‘PACKINGTICKETCOMMENT’. You can have only one packing ticket comment (because product codes must be unique), but you can have multiple invoice comment products.

  • Name – Enter a name. The name you enter is used for report output, placing invoice comments on invoices and packing ticket comments on packing tickets. For packing ticket comments, enter a short meaningful name that easily identifies the comment as a packing ticket comment. For invoice comments, enter any short meaningful name that does not contain the words ‘Packing Ticket’.

  • Unit Group – Click the Lookup button, then select Each and click OK.

  • Default Unit – Click the Lookup button, then select Each and click OK.

  • Currency – If you are working in a single currency environment, by default, your preferred currency appears in this field. Otherwise, you will need to select the Currency.

  • Product Type – Select Comment.

  • Subject – This field is optional. If your organization relates products to subjects, click the Lookup button to select the subject.

Note

You must have subjects set up in your system to use this feature. Please refer to Dynamics CRM user documentation for information on setting up subjects.

In the Accounting area, enter the following accounting setup information for this product:

  • Company – The system will automatically populate this field with the company record flagged as the default company in your set up. If you need to make a change, click the Lookup button to select the appropriate accounting system company for this product. This controls where accounting data will post during the posting process and controls the display of GL accounts available in the GL account lookup fields.

  • Reimbursable – Select Not Reimbursable. Do not select any of the other options for invoice comment products.

  • Primary GL Account – Click the Lookup button to select the GL account for the comment product – typically the product sales revenue account. While no transaction GL will be created for an invoice comment, this is a required field.

  • AR GL Account – Click the Lookup button to select the correct AR account. While no transaction GL will be created for an invoice comment, this is a required field.

  • Cash Basis – Leave the default setting of No.

  • Control Accrual Basis via AR Utility – This field is disabled and not required for this product type.

  • Secondary GL Account – This field is disabled and not required for when the Primary GL Account is a revenue account.

  • AP GL Account – This field is disabled and not required for this product type.

In the Description section of the new product record, all fields are disabled except Description, where you can enter a description of this product. This field is optional and informational only.

Click Save & Close to save the product and return to the List View of Active Products. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Product sales RMAs and returns setup overview

UX Online can automatically create the invoice detail line items needed to manage product returns through RMAs (Return Merchandise Authorizations). For more information about RMAs, see Product sales RMA return overview.

If you want to use the RMA feature, you must meet the following setup guidelines:

  • Products that can be returned using RMA processing must have the Apply Freight? checkbox marked in the product setup.

  • If your organization charges a restocking fee for product returns, you must create a restocking fee product. For more information, see Creating a restocking fee product.

  • If the restocking fee is a percentage of the cost of the returned product (rather than a flat fee), you must set up the application parameter—PAOrders.RestockingPercent—to enable this calculation. For more information, see Setting up percentage-based restocking fees.

  • If you want to prevent users from deleting or canceling product sales invoice detail line items that have been processed for fulfillment (shipped), you must set the PAOrders.DisableCancelOnFulfilled application parameter to TRUE.

After setting up this information, you can use RMAs for product returns, and the system will automatically create an invoice detail line item that adjusts your customer’s invoice balance, creates the appropriate General Ledger detail, and if appropriate, adjusts inventory for the returned items. For more information, see Processing a product sales RMA return. (You can also process a product return manually. For more information, see Processing product returns manually.)

Creating a restocking fee product

If your organization charges a restocking fee when a customer returns a product, you must create a restocking fee product to automate the process of updating the product sales invoice with the appropriate fee and to manage the accounting information required for GL detail.

Restocking fees can be a flat rate or a percentage of the returned product’s cost; however, you cannot use both methods.

Important

You should create only one restocking fee product.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to display a List View of Active Products. This list opens in a new window.

Click Add Product on the List View toolbar to create a new restocking fee product record. In the General section of the Product record, complete the following information:

  • Product ID – Enter an ID for the product. (This ID must be unique.)

  • Name – Enter the name of the new restocking fee product, such as Restocking fee for product returns.

  • Unit Group – Click the Lookup button, then select Each and click OK.

  • Default Unit – Click the Lookup button, then select Each and click OK.

  • Currency – If you are working in a single currency environment by default, your preferred currency appears in this field. Otherwise, you will need to select the Currency.

  • Product Type – Select Sales Non-inventory.

The product type you choose is important because it triggers special program logic during transaction processing. While there are multiple options available in this list, when creating a restocking fee product, you must choose Sales Non-Inventory.

  • Subject – This field is optional. If your organization relates products to subjects, click the Lookup button to select the subject.

Note

You must have subjects set up in your system to use this feature. Please refer to Dynamics CRM user documentation for information on setting up subjects.

In the Accounting section, enter the following accounting setup information for this product:

  • Company – The system will automatically populate this field with the company record flagged as the default company in your set up. If you need to make a change, click the Lookup button to select the appropriate accounting system company for this product. This controls where accounting data will post during the posting process and controls the display of GL accounts available in the GL account lookup fields.

  • Reimbursable – Select Not Reimbursable. Do not select any of the other options for sales order products.

  • Primary GL Account – Click the Lookup button to select the GL account to which accounting data will post when you post UX Online transactions that include this product. This is typically a revenue account.

  • AR GL Account – Click the Lookup button to select the correct AR account.

  • Cash Basis – Leave the default setting of No.

  • Control Accrual Basis via AR Utility – This field is disabled and not required for this product type.

  • Secondary GL Account – This field is disabled and not required for when the Primary GL Account is a revenue account.

  • AP GL Account – This field is disabled and not required for this product type.

In the Costs area, enter the product cost setup information as shown:

  • Default Price List– Leave this field blank. When you save this product record for the first time, this field will automatically display the Non Member price list for the selected Currency.

  • Decimals Supported – Enter the number of decimal places needed for this product’s currency format. For example, the default value of 2 is for a 0.00 currency format.

  • Single Currency – Do not select. It is not applicable.

  • List Price – If you charge a flat amount as a restocking fee, enter the amount here. This will be the amount used for all system-created price records. If you charge a percentage of the returned item’s value, leave this field blank.

  • Apply Freight? – Leave this box unmarked. This does not apply to restocking fees.

  • Is it a Bill Recipient? – This field is not applicable and is disabled for Sales Non Inventory product setup.

In the Tax Product Info area, enter the following information:

  • Taxable – If restocking fees are taxable, mark the Taxable checkbox . Otherwise, leave this box unmarked. If this option is checked, UX Online calculates tax when the Ship To State field contains a State with sales taxes.

  • Tax Rate – Leave this field blank. This does not apply to restocking fee products.

In the Professional Development area of the General section, leave the Course field blank. This does not apply to restocking fee product setup.

In the Description section of the new product record, enter the following information as appropriate for your new product setup:

  • Kit Product? – Leave this field blank. This does not apply to restocking fee product setup.

  • Vendor – Leave this field blank. This does not apply to restocking fee product setup.

  • Vendor Part Number – Leave this field blank. This does not apply to restocking fee product setup.

  • URL – Leave this field blank. This does not apply to restocking fee product setup.

  • Stock Weight – Leave this field blank. This does not apply to restocking fee product setup.

  • Stock Volume – This field is not used in UX Online.

  • Description – Enter a description of this product. This field is optional and informational only.

The fields in the Web section of the new product record do not apply to restocking fee product setup.

Click Save. After saving this record, Prices are activated in the Navigation Pane. Click Prices to view system-created price records for this product. For more information, see Creating product prices.

Important

If you charge a flat amount for the restocking fee, you will need to verify the system-created price records. For more information, see Updating prices for a flat amount restocking fee product.

If the restocking fee is a percentage of the returned item’s price, price records are not required. However, you must configure the system to perform that calculation. For more information, see Setting up percentage-based restocking fees.

Updating prices for a flat amount restocking fee product

If the restocking fee your organization charges for product returns is a flat amount, you must have at least one price record for each price list. You can have multiple price records if different prices apply during different date ranges.

When you first created and saved the restocking fee product, the system automatically created a price list for each price list that is set up in the Product Sales Manager, and automatically created a price record for each price list using the value entered in the product list price as the price record amount. If the price differs for each price list or if your pricing is based on alternate date ranges, you will need to update the price records.

For information on modifying/creating price records, see Creating product prices.

Important

If you create multiple price records for different date ranges, verify that the date ranges do not overlap or have gaps.

Setting up percentage-based restocking fees

If your organization charges a restocking fee for product sales RMA returns, and if the restocking fee is a percentage of the cost of the returned product (rather than a flat fee), you must set up the application parameter – PAOrders.RestockingPercent – to enable this calculation.

If you configure the PAOrders.RestockingPercent parameter, UX Online will ignore any price records associated with the restocking fee product, and calculate the restocking fee using the percentage entered as the Config value in the application parameter record.

To access this setting, in the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters to view a list of required configuration records and their configuration values. This View opens in a new window.

Review the list to check whether the PAOrders.RestockingPercent parameter has already been created for you. If it has been created, double-click the record to open it and confirm the Config value, which represents the percentage of the returned product(s) value to be charged as a restocking fee. If appropriate, modify the Config Value and then follow the steps below.

If the parameter does not exist, click New on the toolbar to create a new application parameter.

Enter the setup information for the parameter:

  • Config Name or Key – Enter PAOrders.RestockingPercent.

  • Config Value – Enter the percentage of the returned products value to be charged as a restocking fee, in whole numbers only. For example, to charge a 5% restocking fee on the value of returned product(s), enter 5.

  • Description – Enter a description of this parameter (for example, “Restocking Fee Percentage”).

  • Owner – Displays the user ID of the user who created this record.

Click Save & Close to save your change and close the record. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

.

Working with substitute products

Substitutes are managed by product relationships in the Product Relationship Associated View of a sales product in UX Online 8. User navigation to Substitutes in UX Online 8 opens the Product Relationship Associated View.
For product substitutes in UX Online 8, the sales product where you create the product substitute relationship to another sales product, and the Direction you assign to that relationship, affects where the user can view related product substitute and whether or not the substitute product supports substitutes/variants in the MX Online Product Catalog when the related main product ‘Has Variants’ = true.

Important

To create a substitute product relationship that supports substitutes/variants in the MX Online Product Catalog when the related main product ‘Has Variants’ = true, open the sales product that is the substitute product.

 

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to display a List View of Active Products. This list opens in a new window.
Locate and open the substitute sales product record where you want to set up a substitute product relationship. Click Substitutes in the product Navigation Pane to open the Product Relationship Associated View of existing related records for this product.
To create a new relationship record, click Add New Product Relationship on the List View toolbar to create a new relationship record.

  • Product – Displays the current sales product. This field is not available for edit.

  • Related Product – Click the Lookup button to select main product for which this product is a substitute.

  • Sales Relationship Type – From the dropdown list, select Substitute.

  • Direction – From the dropdown list, select Uni-Directional or Bi-Directional.

Click Save to save the product relationship and return to the Product Relationship Associated View of the substitute product.

Important

Uni-Directional creates a one-sided relationship between two products. When you create a Uni-Directional relationship from the substitute product to the main product as described in this documentation, the relationship resides in the Product Relationship Associated View of the substitute product only. This approach supports substitutes/variants in MX Online. If you create a Bi-Directional relationship to a substitute product from the main product, the relationship to the substitute product resides in the main product only and does not support substitutes/variants in MX Online. Bi-Directional creates a reciprocal relationship between two products. The related substitute product is a substitute for the main product and the main product is a substitute for the substitute product. This reciprocal relationship resides in the Product Relationship Associated View of both the main product and the related substitute product. This approach supports substitutes/variants in MX Online.

 

Chapter 31: Freight Setup

Freight Shopper calculates shipping charges for product sales invoices by using standard prices that you set up.

This chapter includes topics that describe how to set up any freight products you need.

  • About standard freight

  • Application parameters used for standard freight

  • About freight products

  • Creating a standard freight product

  • Creating prices for a standard freight product

  • Creating a freight service record

About standard freight

You can set up UX Online to calculate the appropriate freight charges for any products you sell based on either the shipment weight or value. (Each product that you want to have a freight charge applied to it must have the Apply Freight option marked in the Product record. For more information, see Creating a new sales order product.)

Note

The option to calculate freight based on shipment weight or shipment value is a global setting. You will not be able to use weight for some products and value for others. All products will use the same method.

You can create standard freight products and associated prices to calculate shipping charges for product sales invoices. Each standard freight product that you set up also requires a standard freight service record.

Based upon the settings in your application configuration parameters, your freight products, and your freight service records, when you click Calculate Freight on an invoice, Freight Shopper will present you with all standard freight services available for the shippable products in the invoice.

The Freight Shopper window will display rates for each standard freight product using prices defined in your standard freight product setup. (For more information, see Creating a standard freight product.)

From this window, you will select the type of shipping you want to use for the order.

Application parameters used for standard freight

UX Online uses certain application parameters to support your organization’s standard freight processes. The way these parameters are configured will depend on your business requirements.

UX Online will be deployed with the correct application parameter configuration records for your organization based on the requirements and values determined during implementation. Do not change these values without consulting your Protech representative.

Use the following procedure to view these parameters. In the Navigation Tile Bar, select the Administration work area > UX Settings > UX Online Application Parameters This View opens in a new window. Locate and open the record you want to view. When you are finished, because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Important

Do not add or remove any configuration records from this list. The parameter values for these configuration settings are case sensitive.

General freight configuration settings

The following general freight configuration settings are used to determine whether taxes are applied to freight charges, and whether freight charges are applied to back orders.

Config Name

Description

Possible values

PABackOrders.ApplyFreight

Determines whether freight charges will be applied to fulfillment invoices created during back order processing.

true = Freight charges will be applied.

false = Freight charges will not be applied.

Standard freight configuration settings

The following standard freight product configuration settings are used for standard freight products.

Config Name

Description

Possible values

PAShipping.ActiveCarrier

Leave this field blank.

PAShipping.FreightIntegrationType

Leave this field blank.

PAShipping.Standard.
CalculationType

Determines whether freight charges are calculated based on the weight or value of the items shipped.

shipmentweight = Freight charges will be based on the weight of the items shipped. (This parameter is used in conjunction with PAShipping.WeightUnits parameter.)

shipmentvalue = Freight charges will be based on the value of the items shipped

PAShipping.WeightUnits

Determines the units for shipping weight, either US pounds or kilograms. (This parameter is used in conjunction with the PAShipping.Standard.CalculationType parameter.)

LBS = Shipping weight is measured in US pounds.

KGS = Shipping weight is measured in kilograms.

PAShipping.MarkupPercent

Sets the standard percentage markup for shipping charges. This is a system-wide markup to the prices created in all standard freight products.

A numeric value is required. For example, “5.0” means a 5% markup will be added to the calculated freight for standard freight products.

Enter 0 if there is no markup.

PAShipping.Web.ExcludeStandardShipping Determines whether standard freight options appear in the MX Online shopping cart.

TRUE = Standard freight options will not appear in the shopping cart.

FALSE = Standard freight options will appear in the shopping cart.

ShippingHandlingExtraFee

Sets the flat-fee markup for standard freight shipping charges. This is a system-wide markup to the prices created in all standard freight products.

A numeric value is required. For example, “10.00” means a flat fee of $10 will be added to the calculated freight for standard freight products.

Enter 0 if there is no markup.

About freight products

UX Online uses standard freight products to calculate standard freight rates. These freight products define the pricing for the freight calculation as well as the GL accounts for managing the accounting distribution for freight credits and debits.

You can create a standard freight product to use when you want the shipping vendor to bill the recipient for the shipping cost. You can set up a price for this freight product—for example, a processing fee—if necessary, even though the recipient will be billed by the vendor for the actual shipping cost. For information, see Billing the recipient for freight charges on a product invoice.

During implementation, your UX Online system was set up with your standard freight products; however, if your needs change, you may need to set up additional standard freight products. For more information, see Creating a standard freight product.

All standard freight products are used in conjunction with freight service records to calculate shipping costs. During implementation, your UX Online system was set up with your standard freight products and freight service records. For more information, see Creating a freight service record.

You must have at least one standard freight product record to calculate standard freight. Standard freight products also require price records for calculating the freight rate pricing. For more information, see Creating prices for a standard freight product.

Note

In a multicompany environment, shipping costs are not split or allocated among companies. The freight product should be set up for the accounting company that will bear the expense of shipping. If necessary, the accounting company that bears the shipping expense can make a journal entry to other departments and companies for overhead costs on a monthly basis.

Creating a standard freight product

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to display a List View of Active Products. This list opens in a new window.

Click Add Product on the List View toolbar to create a new freight product record. In the General section of the Product record, complete the following information:

  • Product ID – Enter an ID for the product. (This ID must be unique.)

  • Name – Enter the name of the new freight product, such as, Freight Charges.

  • Unit Group – Click the Lookup button, then select Each and click OK.

  • Default Unit – Click the Lookup button, then select Each and click OK.

  • Currency – If you are working in a single currency environment, by default, your preferred currency appears in this field. Otherwise, you will need to select the Currency.

  • Product Type – Select Freight.

Note

The product type you choose is important because it triggers special program logic during transaction processing. While there are multiple options available in this list, when creating a freight product, you must choose Freight.

  • Subject – This field is optional. If your organization relates products to subjects, click the Lookup button to select the subject.

Note

You must have subjects set up in your system to use this feature. Please refer to Dynamics CRM user documentation for information on setting up subjects.

In the Accounting area, enter the following accounting setup information for this product:

  • Company – The system will automatically populate this field with the company record flagged as the default company in your set up. If you need to make a change, click the Lookup button to select the appropriate accounting system company for this product. This controls where accounting data will post during the posting process and controls the display of GL accounts available in the GL account lookup fields.

  • Reimbursable – Select Not Reimbursable. Do not select any of the other options for sales order products.

  • Primary GL Account – Click the Lookup button to select the GL account to which accounting data will post when you post UX Online transactions that include this product. This is typically a revenue account.

  • AR GL Account – Click the Lookup button to select the correct AR account.

  • Cash Basis – Leave the default setting of No.

  • Control Accrual Basis via AR Utility – This field is disabled and not required for this product type.

  • Secondary GL Account – This field is disabled and not required for when the Primary GL Account is a revenue account.

  • AP GL Account – This field is disabled and not required for this product type.

In the Costs area, enter the product cost setup information as shown:

  • Default Price List– Leave this field blank. When you save this product record for the first time, this field will automatically display the Non Member price list.

  • Decimals Supported – Enter the number of decimal places needed for this product’s currency format. For example, the default value of 2 is for a 0.00 currency format.

  • Single Currency – Do not select. It does not apply to this product type.

  • List Price – The amount entered here will be the amount used for all system-created price records.

  • Apply Freight? – Leave this box unmarked. It is not used for freight products.

  • Is it a Bill Recipient? – If you are creating a Bill Recipient freight product to charge a flat fee for using the recipient’s freight carrier account for shipping the product, mark this checkbox . For all other freight products where charges are calculated by UX Online based on the shipment value or shipment weight, leave this checkbox unmarked.

In the Tax Product Info area of the General section, enter the following information:

  • Taxable – If shipping charges are taxable, mark the Taxable checkbox ☑. Otherwise, leave this box unmarked. If this option is checked, and the tax rate ‘Freight Taxable’ = True, UX Online calculates tax on shipping charges when the Ship To State field contains a State with sales taxes.
  • Tax Rate – This field is disabled. It does not apply to freight products.

In the Professional Development area of the General section, leave the Course field blank. This does not apply to freight product setup.

In the Description section of the new product record, leave all fields blank. They do not apply to freight product setup.

In the Web section, the only field that applies to freight product setup is the Publish to Web field. Do not change this field. It is used with Protech’s MX Online, and will be set as needed during that implementation. The remaining fields on this tab are not used for freight products.

Click Save. After saving this record, access to Prices in the Navigation Pane is activated. Continue with the setup of your standard freight product. See Creating prices for a standard freight product.

Creating prices for a standard freight product

When you create a standard freight product (see Creating a standard freight product), UX Online will create a price record for each price level in your system. You should verify these price records, and if necessary, create any additional price records you need (for example if you charge different amounts for different weight ranges).

Your standard freight product might require a single price record for each price level, or it might require several. For example, if your association calculates freight charges as a simple percentage of the value of the shipment, you might need only one price record for each price level. If you charge different flat amounts based on the weight of the shipment, you will need a different price record for each weight range. For examples of freight prices based on the weight and the value of the shipment, see Shipping price examples for calculating standard freight.

Note

When calculating freight charges, UX looks for the price record that matches the invoice price level and the volume range for the shipping weight or shipping value. UX does not consider price record date range for calculating freight.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to display a List View of Active Products. This list opens in a new window.

Locate and open the standard freight product record where you want to set up pricing, Click Prices in the Navigation Pane to open the Prices Associated View listing system-created price records for this standard freight product.

To create a new price record, click Add New Prices on the List View toolbar. In the General section of the Prices record, complete the price fields:

  • Price Level – Click the Lookup button to select the price level for this price record.

  • Calculation Method – Select the price calculation method for this freight product: Flat Rate or Percentage. Select Flat Rate if the price is a flat amount. Select Percentage to calculate the price as a percentage of the List Price entered in the product setup General tab. Both calculation methods apply pricing to the product for the product during the date range and for the value range defined below.

  • Value Minimum – Enter the lowest quantity for which this price record applies. The minimum acceptable value is 1. For example, if this price applies to purchases of 10 or more units of the product, enter 10.

  • Start Date – Enter the starting date, although date range is not a factor when selecting a price record for calculating standard freight.

  • Factor – Leave this field blank. It does not apply to product sales price records.

  • Currency – Defaults from the freight product currency.

  • Name – Displays the price level name for this price record.

  • Price/Percent of List Price – Enter the price or the percentage to multiply by the total value of the items to be shipped.

    • If the Calculation Method for this price record is Flat Rate, enter the price of the product during the date range and for the value range set for this price record. For example, if you want to charge a flat rate of $10.00, enter 10.00 in this field.

    • If the Calculation Method for this price record is Percentage, enter the percentage that will multiplied by the total value of the shipping items on an invoice. For example, if you want to charge 10%, enter 10.00. If the total value of the products on a sales invoice is $100.00, the freight charges will be $10.00.

  • Value Maximum – Enter the highest quantity for which this price record applies. For example, if this price applies to purchases of 20 or less units of the product, enter 20.

  • End Date – Enter the ending date, although date range is not a factor when selecting a price record for calculating standard freight.

  • Product – Displays the product you are currently working with.

Click Save & Close to save the price record and return to the Prices Associated View. Repeat these steps until you have created all the price records required to support the pricing schedule for this product.

Note

We recommend that you verify that the price records you create do not conflict with one another (for example, that date ranges overlap or have gaps, or that the minimum/maximum value ranges overlap or have gaps).

Shipping price examples for calculating standard freight

The following examples show how you might set up freight price records based on weight or shipment value.

Shipping prices based on weight – flat rate

The following table shows how you could set up prices for a freight product based on the U.S. Postal Service’s Media Mail rate. (Note: for all of these price records, the Calculation Method should be set to Flat Rate.) You will need a price record for each price list in your system.

Price record

Price

Value Minimum – Value Maximum

1

$1.59

1 – 1

2

2.07

1.01 – 2

3

2.55

2.01 – 3

4

3.03

3.01 – 4

5

3.51

4.01 – 5

6

3.99

5.01 – 6

7

4.47

6.01 – 7

8

4.81

7.01 – 8

9

5.15

8.01 – 9

10

5.49

9.01 – 10

Shipping prices based on value – flat rate

The following table shows how you could set up flat-rate prices for a freight product based on the value of the products on the invoice. This example assumes that your organization charges a flat rate of $5.00 for shipments worth less than $25.00, and $10 for shipments worth $25 to $100, and $20 for shipments worth $100 or more. (Note: for all of these price records, the Calculation Method should be set to Flat Rate.) You will need a price record for each price list in your system.

Price record

Price

Value Minimum – Value Maximum

1

$5.00

1 – 24.99

2

10.00

25.00 – 99.99

3

20.00

100.00 – 999,999,999

Shipping price based on value – percentage

The following table shows how you could set up a percentage price for a freight product based on the value of the products on the invoice. This example assumes that your organization charges 10% of the shipment’s value. (Note: for this price record, the Calculation Method should be set to Percent.) You will need a price record for each price list in your system.

Price record

Price

Value Minimum – Value Maximum

1

$10.00

1 – 999,999,999

Creating a freight service record

You must have a freight service record for each standard freight product you set up. For instance, if you have a freight product for flat rate freight charges and another freight product for percentage of invoice total freight charges, you will need two freight service records, each linked to the appropriate freight product.

Note

Freight service records are used to launch the Freight Shopper when calculating freight on a product sales invoice.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Freight to open the list of Active Freight records. Click New on the List View toolbar to create a new freight service record.

In the General section of the Freight Service record, enter the following information:

  • Name – Enter a brief name that describes the freight service, such as Standard Flat Rate Shipping.

  • Freight Type – Displays Standard by default. Do not change this setting.

  • Service Name – Enter text exactly as it appears here: dbo.PA_SP_FREIGHT_CalculateStandardFreight

  • Product – Click the Lookup button to select the standard freight product that you want to link to this freight service record.

  • Ship Rate Code – Leave this field blank.

  • Service Type – Click Stored Procedure.

Click Save & Close to save the freight service record and return to the Active Freight list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Chapter 32: Product Sales Transactions

UX Online allows you to create product sales transactions based on your organization’s specific requirements for inventory control and back order processing. This documentation reviews the organization settings requirements and provides detailed instructions for processing product sales transactions in UX Online using inventory control under two scenarios:

  • Inventory control with accounting system integration

  • Internal inventory control where there is no inventory integration with your accounting system

This information is divided into the following sections:

  • Inventory control with accounting system integration overview

  • Internal inventory with no accounting system integration overview

  • Back order options

  • Creating a product sales invoice

  • Canceling or deleting a product sales transaction

  • Calculating freight charges for a product invoice

  • Modifying freight charges for a product invoice

  • Billing the recipient for freight charges on a product invoice

  • Back orders on product sales invoices

  • Payments and product sales invoices overview

  • Back order processing overview

  • Replenishing available inventory

  • Flagging back-ordered invoices for fulfillment

  • Processing back-ordered invoices flagged for fulfillment

  • Verifying the new invoices created during back order processing

  • Flagging back-ordered invoices for cancellation

  • Processing back-ordered invoices flagged for cancellation

  • Product sales return options

  • Product sales RMA return overview

  • Processing a product sales RMA return

  • Processing product returns manually

  • Processing product kit returns manually

Inventory control with accounting system integration overview

You can set up a direct, real-time integration between UX Online and the inventory module of your Dynamics GP or Dynamics SL accounting system. This topic describes how this integration works.

Note

In order to use this feature, you must have the appropriate licenses for UX Online Inventory and your accounting system Inventory Control module.

When you use the integration between UX Online and your accounting system, sales transactions in UX Online that include products with a Sales Inventory product type will use the quantity information stored in your accounting system data. The system does not use the Quantity on Hand field on the product record when configured for integrated inventory control. Rather, the available inventory quantity for an item will be based on the quantity in the accounting system, less the unposted product sales of that item in UX Online. When the batch is posted, the quantity available in the accounting system will be updated with the quantities from the transactions. (The Quantity on Hand field in UX Online will not be updated.)

Besides keeping your accounting system inventory records updated, the integration also allows you to deal with quantity shortages on UX Online sales invoices. You can allow backorders and partial backorders when an invoice includes an item with a quantity shortage, and you will be able to process those backorders when your inventory is replenished in your accounting system. For more information, see Back order processing overview.

Important Note

Back order processing for product sales is an optional feature in UX Online. It is available only in conjunction with inventory control, but it is not required for inventory control.

If you want to use the accounting system inventory integration, you must select which accounting system to use in the Inventory System setting in your Global Setup Default record: Dynamics GP or Dynamics SL. For more information, see Organization Setup.

Note

This information may have already been set up for your organization by your Protech representative during your system implementation.

In addition to the global settings for inventory integration, you must be sure your UX Online product records are set up correctly. The set up to allow the accounting system inventory integration involves the following fields on the product record:

  • Product ID – The product ID you assign to a product in UX Online must exactly match the product ID for the product in the accounting system. This field links the UX Online record to the corresponding record in the accounting system inventory module.

  • Product Name – The product name you assign to a product in UX Online must exactly match the product’s name in the accounting system.

  • Product Type – Each product that you want to manage with integrated accounting system inventory must have Sales Inventory as the UX Online product type. This enables the system to use inventory control and back order processing for the product.

  • Warehouse – The warehouse records in UX Online must match the sites and item setup in the accounting system. UX Online accommodates as many warehouse sites as there are in the accounting system, but the sites and item setup must match in both systems.

In addition to these fields, you must set the Allow Back Order and Allow Partial Back Order options to meet your organization’s back order processing requirements. See Back order options for more information.

Note

Setting backorder options only controls backorders for transactions processed in the back office. If the Sales Inventory product is published to the web and purchased online, these options are ignored and the product is subject to backorder, regardless of these settings.

Internal inventory with no accounting system integration overview

If your system is set up to use internal inventory, the default inventory system setting on the Organizational Settings record will be Internal. (See Global Setup Default for more information.) Available inventory quantities are based on the Quantity on Hand field in each product record, less any unposted product sales. When batches are posted, this field is updated to reflect any changes due to those transactions.

Also, when your UX Online system is using internal inventory control, you must be sure your product records are set up correctly. Pay particular attention to how you set up the following fields on the product record:

  • Product type – Each product that you want to manage with internal inventory control must have Sales Inventory as the UX Online product type. This enables the system to use inventory control and back order processing for the product.

  • Warehouse – When you are using internal inventory, product sales processing is limited to a single warehouse site. During product setup, you must select this warehouse as the default warehouse for your sales inventory products.

In addition to these fields, you must set up the Allow Back Order and Allow Partial Back Order options to meet your organization’s back order processing requirements. See Back order options for more information.

Note

Setting backorder options only controls backorders for transactions processed in the back office. If the Sales Inventory product is published to the web and purchased online, these options are ignored and the product is subject to backorder, regardless of these settings.

Back order options

If you want to allow products to be back-ordered, or partially back-ordered when there are quantity shortages for transactions processed in the back office, you have to set the Allow Back Order option and the Allow Partial Back Order option on each product record to meet your organization’s needs. You can set up each item’s back order options individually, so you can have some items allow back orders but not partial back orders. You can set up other items to allow both back orders and partial back orders, and yet set up other items to not allow back orders at all.

Note

Setting backorder options only controls backorders for transactions processed in the back office. If the Sales Inventory product is published to the web and purchased online, these options are ignored and the product is subject to backorder, regardless of these settings.

There are two basic scenarios for processing a product sale with quantity shortages: the item is out of stock, or the quantity on hand is less than the quantity ordered. The rules that UX Online uses in these scenarios are the same whether your system is set up to use the accounting system’s inventory or internal inventory control.

Note

UX Online does not use the Allow Partial Back Order option unless the Allow Back Order option is also checked.

Scenario 1: Available inventory for a product is zero (that is, the product is out of stock). In this scenario, the result of entering this product on an invoice depends only on the setting of the Allow Back Order option.

Allow Back Order option

Allow Partial Back Order option

Result

Not marked

Not applicable

You will not be able to enter the product on a product sales invoice. The system will display a message instructing you to choose another product.

Marked

Not applicable

You will be given the option to back-order the product, or select another product.

 

Scenario 2: Available inventory is greater than zero but insufficient to fill the order. In this scenario, the result depends on the settings of both the Allow Back Order option and the Allow Partial Back Order option, as shown in the following table.

Allow Back Order option

Allow Partial Back Order option

Result

Not marked

Not applicable

You will not be able to enter the product on a product sales invoice. The system will display a message instructing you to choose another product.

Marked

Not marked

You will not be able to enter the product on a product sales invoice. The system will display a message instructing you to choose another product.

Marked

Marked

You will be given the option to partially back-order the product or select another product.

 

Note

If you are using the accounting system inventory integration, and have products at multiple warehouses, you may be able to fulfill the quantity ordered by selecting a different warehouse for the product when processing the order in the back office. This option is not available for purchases made online. For more information about selecting the warehouse for a product on a sales invoice, see Creating a product sales invoice.

Creating a product sales invoice

The process for creating a product sales invoice is the same, whether you are using the accounting system inventory integration or the system’s internal inventory control, with two exceptions:

As you enter product sales line items on the invoice, you may be required to deal with item quantity shortages by back ordering the product, depending on how the product is set up. For more information, see Back order options.

Create and save a new invoice, following the instructions in Invoices. Click New Transaction on the invoice grid Record toolbar and select Product Sales from the menu to open a new product sales transaction form.

In the Product Sales transaction record, complete the invoice transaction detail fields described below:

  • Product – If you know the product ID enter it here, or click the Lookup button on the Product field to select the product. See Managing Single Currency Sales Products, Meetings and Exhibits for additional information when selecting a sales product where Single Currency = true.

  • Description – By default, displays the name of the product you entered or selected through the Product lookup button.

  • Warehouse – If the selected product type = Sales Inventory, displays the default warehouse associated with the product you selected. If your system uses integrated account system inventory, you can select a different warehouse for this product by clicking the Lookup button. If you are using internal inventory control, do not change this field; product sales processing uses the warehouse site that was assigned when you set up the product.

Note

If the product type selected = Sales Inventory, click the Available Inventory button on the Record toolbar to view the quantity available at the selected warehouse. If your system uses the accounting system inventory integration, and the selected product is stocked at other warehouses, you may be able to avoid a back order transaction by selecting an alternate warehouse with sufficient inventory to fill the order.

Do not select another warehouse if your system is using internal inventory.

Continue entering the invoice transaction detail fields described below:

    • Transaction Date – Displays the batch date.

    • Batch Number – Displays the batch selected for the invoice.

Note

When you first create an invoice transaction detail item, you will not be able to change the batch number. However, if you are editing an invoice transaction detail item that has been saved, and if the batch is still open, you can select a different batch.

  • Quantity Ordered – Enter the quantity ordered. If the available quantity is less than the quantity ordered and the product is set up to allow full or partial back orders, a message will appear giving you the option to proceed with the back order or to select another product. For more information, see Back orders on product sales invoices.

  • Back Ordered – If you choose to back order all or part of the quantity ordered, this field displays the result of the quantity ordered less the available inventory. For example, if the available inventory is zero, the amount displayed is the quantity ordered.

  • Quantity Shipped – Displays the result of the quantity ordered less the quantity back ordered. For example, if the available inventory is zero and the item is fully back-ordered, the quantity shipped will be zero.

  • Overridden Price – If you want to sell this product for a different price than the default price, check Override Price.

  • Price – Displays the price of the product (which is calculated based on the price list selected for the invoice and the prices in the product record). If you checked the Override Price option, enter the override price per unit for this product.

  • Promotion – If you want to apply a promotion to this product sale, click the Lookup button to select the appropriate promotion code. The amount of the promotion will appear in the Discount field. For more information, see Promotion records.

  • Discount – If you select Yes for the Overridden Discount option, enter the dollar amount of the total discount. For example, if you selling five books at $15.00 each, and enter a discount of $10.00, the amount this product will be $65.00 (5 x $15 = $75.00, less discount amount of $10.00). You cannot enter a percentage discount here.

  • Overridden Discount – Select Yes if you want to override the Discount applied by the selected Promotion or enter a manual discount without a Promotion. This enables the Discount field for editing.

  • Amount – Upon Save of the transaction, displays the extended amount of this line. The amount is calculated from the quantity shipped and the price. In the case of a full back order where the quantity shipped is zero, the amount is 0.00.

  • Customer Account or Customer Contact – Displays the invoice customer (account or contact) in corresponding field. While these both fields can be edited, only one should be populated.

Important

Do not select both a Customer Account and a Customer Contact.

  • Tax – Upon Save, displays the calculated tax amount of this line item. The tax amount on taxable products is based on the invoice Ship To address, whether the Tax Exempt field on the invoice is blank, and whether the product setup is flagged as taxable. For example, if there is a tax product for Maryland Sales Tax, the product is a taxable item, the Ship To address is in Maryland, and the Tax Exempt field on the invoice header is blank, the system calculates the sales tax based on the currency amount in the Amount field, less the amount in the Discount field.

  • Charges – Upon Save, displays the extended amount of the invoice transaction detail. The extended amount is the result of the Amount less the Discount, plus the tax amount.

Leave the fields in the Delivery section of the General tab blank. These are used during order fulfillment processing. For more information, see Sales Order Fulfillment.

Click Save, then review the amounts in the following fields for accuracy:

  • Price

  • Amount

  • Discount

  • Tax

  • Charges

Click Save & Close to save your transaction detail entry and return to the invoice. Review the invoice detail line item and invoice totals to ensure that the invoice is correct.

Note

If an invoice includes back-ordered or partially back-ordered items, the product sales transaction appears with a yellow warning icon to indicate the back order.

Click Save & Close if you are finished and there are no other transactions to enter or payments to apply to this invoice. If you have a payment to apply, click Save to save the invoice and apply the payment (see Payment and Adjustment Transactions). If any items on this invoice are back-ordered, see Back orders on product sales invoices.

Canceling or deleting a product sales transaction

This section describes how to cancel or delete a product sales invoice transaction and the system rules that apply, based on batch status and payments within the invoice. This procedure reverses the original charges to create the appropriate reversing general ledger entries.

You will cancel a product sales transaction if its originating batch has been closed. You will delete a product sales transaction if its originating batch is still open.

Important

When the application parameter PAOrders.DisableCancelOnFulfilled is set to True, you will not be able to cancel a product sales transaction using the delete button if the product has been processed through order fulfillment (where the Shipped On date inside the invoice detail for the product transaction contains data).

From the account or contact’s record, open the product sales invoice that includes the transaction that needs to be canceled. Within the invoice, select the appropriate batch for this cancellation.

Note

If you make changes to any invoice in UX Online, you must first select an open batch. This is required to ensure that any changes to the amount of the invoice or payments made in the invoice are done in accordance to the rules established for updating your General Ledger accounts.

Click the product sales line item in the list of invoice detail line items to select it. Click the Cancel button on the Transactions grid toolbar.

A delete/cancel confirmation dialog box will appear. Click Yes to cancel this line item.

If the batch where this line item was originally entered is still open, the line item will be deleted and will no longer appear on the invoice. If the batch where this line item was originally entered is closed, the line item will be canceled and you will see a red X next to the product sales invoice detail line item.

If there was a payment on the invoice, you may either refund the credit card or cash/check payment, or you may enter another transaction of any type. Another option is to transfer the remaining money to another invoice if appropriate.

Note

When you cancel a product sales line item in an invoice, the Quantity field displayed in the list of invoice detail line items of the invoice changes to zero. If your organization’s business rules require that you be able to report the original quantity ordered to the customer, you can open the detail record and see the Quantity ordered. If the customer needs a cancellation receipt or confirmation showing the original quantity canceled, use the pa_quantityordered field in your report.

Calculating freight charges for a product invoice

When you have finished adding products to an invoice, you can calculate the freight charges (if any of the products have the Apply Freight option marked in the Product setup). UX Online will calculate the freight charges based on the standard shipping option you select in the Freight Shopper.

This list of available shipping options is dependent on the UX Online Application Parameter settings, the stored procedure Freight Service record setup, and the freight product setup.

Create a product sales invoice (see Creating a product sales invoice). Click Calculate Freight on the invoice Record toolbar to open the Freight Shopper.

Select the standard shipping method that you want to apply to this invoice and click OK.

Note

The list of available shipping methods includes all standard freight products that are linked to freight service records. If you created a freight product but did not link it to a freight service record, it will not appear here.

UX Online will calculate the freight charges (using the appropriate prices depending on price records for the selected standard freight product and the invoice price level), create a new detail invoice line for the freight charges, and update the balance due.

Note

If shipping charges are subject to sales tax, the respective Tax Rate record ‘Freight Taxable’ flag must equal Yes and the underlying freight product ‘Taxable’ flag must equal Yes.

Save & Close the invoice.

Note

When calculating freight charges, UX looks for the price record that matches the invoice price level and the volume range for the shipping weight or shipping value. UX does not consider price record date range for calculating freight.

Modifying freight charges for a product invoice

If you need to modify the freight charges for a product invoice—for example, if you have added additional product line items, or the customer has requested a different shipping method—you must calculate new freight charges.

Create a product sales invoice (see Creating a product sales invoice) or select an existing product sales invoice. Make the necessary changes to the invoice (that is, add or delete product line items, or select a different shipping method).

Click Calculate Freight on the invoice Record toolbar to open the Freight Shopper. Select the standard shipping method that you want to apply to this invoice and click OK.

The method the system uses to update the freight charges depends on whether the batch for the original freight charge line item is open or closed:

  • If the batch for the original freight charge line item is still open, the original line item will be updated to reflect the recalculated charges.

  • If the batch is closed, the original freight charge line will be canceled (you will see a red X next to the freight invoice detail line item) and a new freight charge line item will appear on the invoice.

Save & Close the invoice.

Billing the recipient for freight charges on a product invoice

By calculating freight and selecting “Bill Recipient” from the list of available shipping methods in the Freight Shopper, the system creates an invoice detail line item, and depending on the prices set up in your Bill Recipient freight product, applies a charge for this service. For more information, see Creating a standard freight product.

Back orders on product sales invoices

As you enter product sales line items on an invoice, you may be required to deal with item quantity shortages by back ordering the product.

Note

You can back order an item only if the Allow Back Order option on the product record is marked. You can partially back order an item only if both the Allow Back Order and Allow Partial Back Order options are marked.

If a Sales Inventory product is set up for back orders or partial back orders, the option to back order or partially back order an item occurs when you enter the Quantity Ordered. If the available quantity for an item (calculated as the quantity in inventory less any quantities on unposted transactions) is zero, a message will appear asking if you want to back order the item.

If the available quantity for an item is greater than zero, but less than the quantity ordered, a message will appear asking if you want to partially back order the item.

In either case, the following fields on the product sales invoice will be automatically adjusted to account for the quantity difference:

  • Back Ordered – Displays the result of the quantity ordered less the available inventory. For example, if the available inventory is zero, the back-ordered amount displayed is the quantity ordered.

  • Quantity Shipped – Displays the result of the quantity ordered less the quantity back ordered. For example, if the available inventory is zero and the item is fully back-ordered, the quantity shipped will be zero.

  • Amount – Displays the extended amount of this line item, adjusted to account for items back ordered. (The amount is calculated from the quantity shipped and the price per unit.) In the case of a full back order where the quantity shipped is zero, the amount is 0.00.

  • Tax – The calculated tax amount for the item does not include the back-ordered items, because it is based on the quantity shipped, not the quantity ordered.

  • Charges – Displays the extended amount after you save the invoice transaction detail. The extended amount is the result of the amount, less the discount and tax, if applicable. The extended amount for the item does not include the back-ordered items, because it is based on the quantity shipped, not the quantity ordered.

Note

If a kit item’s components are sales inventory items, and there is a shortage of the components, then the kit will be back ordered. You will not be able to sell a partial kit; however, if necessary, you can remove the kit item from the sales invoice and add the available components to the invoice.

Payments and product sales invoices overview

Customer payments for product sales invoices are entered the same way as payments for any other type of invoice. (For detailed instructions, see Payment and Adjustment Transactions.) However, if any items on the invoice are fully or partially back-ordered, the system will process the payments differently, and in the case of credit card payments and fully back-ordered invoices, you need to follow a different process.

Cash or check payments and back-ordered invoices

When you receive a customer payment in the form of cash or a check to apply against an invoice, you must apply the exact amount of the payment received to the invoice.

If any items on the invoice are back ordered—either fully or partially—this may result in a credit balance on the invoice. Later, when you process the back order, UX Online automatically creates a new invoice and transfers the credit balance from the original invoice to the new invoice. For more information, see Back order processing overview.

For example, assume you want to apply a check of $125 to an invoice order of five items that cost $25.00 each. The quantity available is 2, and the quantity back ordered is 3. When you enter the payment line item, the default amount in the Payment field will be $50.00 (equal to the extended amount for the quantity shipped). You must change the Payment amount to the amount of the check: $125.00. When you save this payment transaction, the invoice will have a credit balance of $75.00. When you process this back order, UX Online will automatically create a new invoice for the items remaining to be shipped and transfer the credit balance of $75.00 from the original back-ordered invoice (where you applied the payment) to the new invoice.

Credit card payments and partially back-ordered invoices

When you receive a customer payment in the form of a credit card to apply against a partial back-ordered invoice, the credit card payment amount on the invoice is the extended amount of the quantity shipped – not the full amount due for all items ordered. If the credit card authorization is approved, it creates a reference transaction in PayPal that can be used when you process the backorder for fulfillment. The reference transaction in PayPal is valid for approximately 12 months.

Later, when you process the back order, UX Online automatically creates a new invoice and creates and processes a new credit card transaction for the amount due. The customer’s credit card will show two transactions: the initial transaction for the amount due on the initial quantity shipped and a subsequent transaction when you process the back order for the remaining items ordered.

Note

Applying payments to the new invoices created during the back order process is controlled by the UX Online Application Parameter PABackOrders.ApplyPayments. If this value is set to ‘true’, the system will automatically apply payments to the new invoice. If this value is set to ‘false’, the system will not apply payments to the new invoice. This setting typically is set to ‘true’.

For example, assume you want to apply a $125.00 credit card payment to an invoice order of five items that cost $25.00 each. The quantity available is 2, and the quantity back ordered is 3. When you enter the payment line item, the default amount in the Payment field will be $50.00 (equal to the extended amount for the quantity shipped). Do not change the Payment amount. This is the amount that will be charged to the customer’s credit card for the quantity shipped. When you process this back order, UX Online will automatically create a new invoice with a line item for the 3 items remaining to be shipped, and a new credit card payment line item for the balance due of $75.00.

Credit card payments and fully back-ordered invoices

When you receive a customer payment in the form of a credit card to apply against a fully back-ordered invoice, do not enter a payment transaction. Create an activity in the invoice as a reminder to apply the credit card payment at the time you process backorders. Hold the credit card information in a secure location (such as a locked drawer or safe) – do not record the credit card information in the activity. When you process backorders, apply the credit card to the new invoice using standard credit card payment processes (see Payment and Adjustment Transactions).

Back order processing overview

After you have closed and posted all product sales batches and replenished inventory, you can fulfill any back orders you have in your system. The process of fulfilling back orders involves two procedures: First, you will select the back-ordered invoices that you can now fulfill. For more information, see Flagging back-ordered invoices for fulfillment. Next, you will launch the process in UX Online that automatically creates new invoices for the back-ordered products. For more information, see Processing back-ordered invoices flagged for fulfillment.

Important

If you are using the UX Online internal inventory system, you must manually update the Quantity on Hand on each product record before you begin the process of fulfilling back orders. For more information, see Replenishing available inventory. (If you are using the accounting system inventory integration, the quantity information on your product records will be updated by your accounting system inventory replenishment processes.)

If a customer decides that they do not want a back-ordered item, you can cancel the back-ordered invoice. To cancel back-ordered invoices, you must first flag the back-ordered invoices that you want to cancel. For more information, see Flagging back-ordered invoices for cancellation. Next, you will process the flagged invoices. For more information, see Processing back-ordered invoices flagged for cancellation.

Replenishing available inventory

The process for recording inventory replenishment depends on your organization’s method for inventory control.

If you are using the accounting system inventory integration, you will update your item quantities in the accounting system. Refer to your documentation for Microsoft Dynamics GP or Microsoft Dynamics SL Inventory module for more information.

If you are using the UX Online internal inventory system, you must manually update the Quantity on Hand on each product setup record when you receive new stock. Use the following procedure to record the receipt of new inventory items.

Important

Before you enter new item quantities, close and post all batches containing sales inventory product transactions. For more information on posting batches, see Integration with General Ledger.

Note

Internal Inventory for product kits is not replenished in the kit product, it is managed in the related kit component products.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Product Sales Settings > Product Setup to open the view of Active Products. This list opens in a new window.

Locate and open the Sales Inventory product record where you need to replenish inventory. In the Quantity on Hand field, enter the new quantity on hand value (existing quantity on hand plus the additional quantities being added to inventory).

Click Save & Close to save the product record and return to the Product list. Repeat steps for each product where you need to replenish inventory.

Flagging back-ordered invoices for fulfillment

When you have replenished your inventory and updated your product records with the new quantity on hand information, you can begin the processing back-ordered invoices. The first step in this process is to flag the invoices that you want to fulfill.

Important

You must close and post all product sales batches and replenish inventory before you begin processing back orders.

You can use the UX Backorder Report to view back-ordered invoices. (In the Navigation Tile Bar, select any UX work area and click Reports to open a list of UX Online reports. In the Reports list, locate and open the UX Backorder Report.)

Note

Because the order processing system does not differentiate between back-ordered invoices that are flagged to fulfill and those that are flagged to cancel, we recommend that you complete the back-ordered invoice fulfillment process separately from the back-ordered invoice cancellation process. Flag all of the back-ordered invoices that you want to fulfill, and then process them. Then you can flag and process the back-ordered invoices that you want to cancel.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > View and Edit Back Orders. Enter criteria to search by customer or product, and select Search Back Orders, or select Show All to display the list of all back-ordered invoice records that are ready for processing.

Note

An invoice is considered for back order processing if it includes any product sales line items with a back-ordered quantity greater than zero. Canceled invoice transactions and processed back order invoices will not be included in this list.

You can double-click the individual records to open the original invoice and edit the original transaction invoice detail line item if necessary. Select one or more records to flag for fulfillment. To select more than one record, press and hold the Ctrl key while clicking each record you want to select.

Click Flag to Fill on the back order list toolbar.

The Flag Back Orders Confirmation dialog appears indicating the number of records selected. Click Yes to continue.

The system adds a flag to the invoice indicating that this record is now eligible for processing. Note that an F appears in the Action column for each flagged record in the Back Orders list.

Note

If you have flagged an invoice for processing by mistake, you can remove the flag. Select the flagged records and click Clear Flag on the toolbar to clear the flag.

Processing back-ordered invoices flagged for fulfillment

After flagging the back-ordered invoices that you want to fulfill, you must launch the actual fulfillment process, which creates a new invoice for each flagged back-ordered invoice. The new invoice will include a product sales line item for each back-ordered line item on the original invoice.

You can launch the fulfillment process from two locations:

  • By clicking the Process Flagged Orders button on the toolbar in the View Back Orders list.

  • By returning to the Product Sales Manager menu and selecting Back Order Processing.

The process is the same for both. The following procedure shows the steps beginning from the View Back Orders list.

Note

The order processing system does not differentiate between back-ordered invoices that are flagged to fulfill and those that are flagged to cancel. If you have flagged some invoices to fulfill and some to cancel, they will both be processed. To maintain better control, Protech recommends that you flag and process each type of invoice separately: Flag invoices to fulfill and then process them, and then do the same for invoices that you want to cancel. Use the column sort functionality on the Action column to view all flagged invoices to make sure there are no invoices flagged to cancel before starting this process.

Important

Before you begin this process, be sure you have created a batch for the new invoices that will be created, closed, and posted.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > View and Edit Back Orders to display the list of all back-ordered invoice records that are flagged for processing.

Click the Process Flagged Orders button on the back order list toolbar.

  • In the Search Confirmation dialog, click the Lookup button on the Batch Number field and select the batch you created for this process, and then click Yes.

  • A confirmation message appears. If the number of records selected matches the number of records that you flagged, click OK to process back orders.

Note

If there are any quantity shortages found during this process, a message will appear in the Process Error column of the flagged item. If this occurs, the invoices that included these items will not be processed and will remain flagged for processing.

The system removes the processed invoices from the Back Orders list (you may need to refresh) and creates a new invoice for each back-ordered invoice. If the original backordered invoice had a credit balance, it will be transferred to the fulfillment invoice.

Verifying the new invoices created during back order processing

After processing back orders for fulfillment, we recommend that you review the new invoices that were created to verify that the product sales and payment amounts are correct. You can use the UX Backorder Fulfilled Invoices report to identify these invoices or you can verify the invoice in UX Online.

From any of the UX work areas on the Navigation Tile Bar, click Invoices.

In the View list, click Today’s Invoices. The newly created invoices will appear in the list of invoices created on that day. Double-click each invoice to open it and verify the product sales and payment line items. Depending upon the payment entered in the original back-ordered invoice, the system automatically creates the payment for the new invoice.

  • Cash or check payments on the back-ordered invoice: The system automatically transfers the credit balance on the original invoice with a “Transfer From” payment and applies it to the new invoice with a “Transfer To” payment.

  • Credit card payments on a partially back-ordered invoice: The system automatically creates a new credit card payment transaction in the new invoice and processes it for authorization.

  • Credit card payments on a fully back-ordered invoice: If you have processed a fully back-ordered invoice that the customer wanted a credit card payment applied to, you should have held the credit card information in a secure location. (For more information, see Payments and product sales invoices overview.) You can now apply that payment to the new invoice.

Flagging back-ordered invoices for cancellation

If a customer decides that they do not want the back-ordered items, you can cancel a back-ordered invoice.

Note

You will be able to flag a back-ordered invoice for cancellation, but you can not process the cancellation if the original invoice batch is open. The batch must be closed in order to process the cancellation.

UX Online uses the same process that is used to fill back orders. The difference in how the system processes a back-ordered invoice depends on the flag you select. In this instance, you are flagging the invoice to cancel the backordered invoice detail.

Note

Because the order processing system does not differentiate between back-ordered invoices that are flagged to fulfill and those that are flagged to cancel, we recommend that you complete the back-ordered invoice fulfillment process separately from the back-ordered invoice cancellation process. Flag all of the back-ordered invoices that you want to fulfill, and then process them. Then you can flag and process the back-ordered invoices that you want to cancel.

The first step in this process is to flag the invoices containing a backorder that you want to cancel.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > View and Edit Back Orders. Enter criteria to search by customer or product, and select Search Back Orders, or select Show All to display the list of all back-ordered invoice records that are ready for processing.

Note

An invoice is considered for back order processing if it includes any product sales line items with a back-ordered quantity greater than zero. Canceled invoice transactions and processed back order invoices will not be included in this list.

You can double-click the individual records to open the original invoice and edit the original transaction invoice detail line item if necessary. Select one or more records to flag for fulfillment. To select more than one record, press and hold the Ctrl key while clicking each record you want to select.

Click Flag to Cancel on the back order list toolbar. The Flag Back Orders Confirmation dialog appears, indicating the number of records selected. Click Yes to continue.

The system adds a flag to the invoice indicating that this record is now eligible for processing. Note that a C appears in the Action column for each flagged record in the Back Orders list.

Note

If you have flagged an invoice for processing by mistake, you can remove the flag. Select the flagged records and click Clear Flag on the toolbar to clear the flag.

The next step is to process the flagged invoices. See Processing back-ordered invoices flagged for cancellation.

Processing back-ordered invoices flagged for cancellation

After flagging the back orders that you want to cancel (see Flagging back-ordered invoices for cancellation for more information), the next step is to process the invoices flagged for cancellation. This process updates the originating invoice by changing the quantity ordered to the quantity actually shipped, changing the back-ordered quantity to zero, and the back-ordered flag is cleared in the invoice detail line item. The process also removes the invoice from the UX Online Product Sales Manager View and Edit Back Orders list.

Note

You will be able to flag a back-ordered invoice for cancellation, but you can not process the cancellation if the original invoice batch is open. The batch must be closed in order to process the cancellation.

You can launch the process from two locations:

  • By clicking the Process Flagged Orders button on the toolbar in the View Back Orders list.

  • By returning to the Product Sales Manager and selecting Back Order Processing.

The process is the same for both. The following procedure shows the steps beginning from the View Back Orders list.

Note

The system does not differentiate between invoices that are flagged to fill and those that are flagged to cancel when running this process. If you have flagged some invoices to fulfill and some to cancel, they will both be processed. To maintain better control, Protech recommends that you run Process Flagged Orders on invoices that are flagged to cancel separately from the invoices that are flagged to fill. Use the column sort functionality on the Action column to view all flagged invoices to make sure there are no invoices flagged to fulfill before running the process.

Important

Before you begin this process, be sure you have created a batch for the backordered invoices that will be canceled and that you have closed and posted all product sales batches. Backordered invoices in open batches are not eligible for cancellation.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > View and Edit Back Orders to display the list of all back-ordered invoice records that are flagged for processing.

Click the Process Flagged Orders button on the back order list toolbar.

  • In the Search Confirmation dialog, click the Lookup button on the Batch Number field and select the batch you created for this process, and then click Yes.

  • A confirmation message appears. If the number of records selected matches the number of records that you flagged. Click OK to process cancellation of the back orders.

Important

This action cannot be undone.

The system removes the processed invoices from the View Back Orders list. The original invoice quantity ordered is updated to the quantity shipped, quantity backordered to zero, and the back-ordered flag is cleared in the invoice detail line item.

Product sales returns options

You can process full or partial product sales returns for sales inventory and sales non-inventory items, using the RMA (Return Merchandise Authorization) process. See Product sales RMA returns overview and Processing a product sales RMA return for more information.

You can also process full or partial product sales returns manually. Kit product returns must be processed manually. See Processing product kit returns manually for more information.

Product sales RMA returns overview

You can enter and process product sales RMA returns for sales inventory and sales non-inventory product returns where the original invoice batch is closed, the EasyPrint Packing Ticket report has been run, and the product has been shipped. For sales inventory products, the process returns the products to inventory (whether you are using the integration with Microsoft Dynamics GP or Microsoft Dynamics SL inventory or internal inventory). In addition, it calculates the credit due to the customer for the returned product, calculates sales tax on the return, and creates new invoice detail line item for the return transaction.

Important

The RMA return process does not manage re-calculating freight charges.

The RMA return process cannot be used for returning kit products. See Processing product kit returns manually for more information.

Optional features include the ability to track user-defined RMA authorization numbers and to automatically create invoice detail line item for re-stocking fee charges. Depending on your organization’s requirements, a re-stocking fee can be a flat amount or it can be calculated as a user-defined percentage of the product returned value. Optional controls can be activated to prevent canceling or deleting the original product sales transaction once it has been processed for order fulfillment.

You can begin this process by clicking the RMA button, which appears on the product sales invoice detail line Record toolbar after the original transaction batch is closed and the item has been processed for order fulfillment. Clicking the RMA button opens the RMA Process window, where you can enter the quantity returned, an optional RMA #, and an optional re-stocking fee product.

Based on the information entered in the RMA Process window and your working batch, UX Online automatically performs the following actions:

  • Calculates the product return credit.

  • Calculates the discount credit, if a discount was applied to the original product sales.

  • Calculates the sales tax credit, if applicable.

  • For sales inventory products, updates the Available Inventory for the product.

  • Creates a new invoice detail line item containing the quantity returned, the RMA #, the product credit, the discount credit, if applicable, and the sales tax credit, if applicable.

  • Creates a new invoice detail line item containing charges for the re-stocking fee, if applicable.

  • Updates the invoice totals.

If freight charges were calculated on the original invoice, you will need to recalculate freight after processing the RMA, but before issuing any refund for the returned products. This will cancel the original invoice detail line item for the original freight charges and create a new invoice detail line item with the prorated freight charges for the net product order.

If full payment was applied to the invoice at the time of the original order, the invoice will have a credit balance for the returned product, less any restocking fees. The credit balance can be left on the invoice, refunded to the customer, or transferred to another invoice using standard UX Online processes.

Standard batch processing will create the necessary GL detail entries for posting in your accounting system.

You can create and process multiple RMAs against a single product sales transaction; however, the cumulative number of returned products cannot exceed the quantity shipped in the original transaction.

Processing a product sales RMA return

UX Online can automatically create the invoice detail line items needed to manage product return RMAs (Return Merchandise Authorizations) for sales inventory or sales non-inventory items.

Important

The RMA return process cannot be used for returning kit products. See Processing product kit returns manually for more information.

For a detailed description of what happens when you process an RMA, see Product sales RMA return overview.

You can create an RMA for a product sale if all of the following conditions are true:

  • The batch for the original product sale transaction is closed.

  • The UX Product Sales EasyPrint Packing Ticket report has been generated and exported.

  • The order has been processed as shipped, which updates the Shipped On field on the product sales invoice detail line item.

  • The order was not for a product kit and related kit components.

Your organization may use a manual process for managing product sales returns, rather than this automated process. For more information about the manual product return process, see Processing product returns manually.

Open the invoice containing the product sales transaction where you want to enter an RMA.

Double-click to open the invoice detail line for the product that is being returned. If the return is for product kit, you must process the return manually. See Processing product kit returns manually. Click the RMA button on the Record toolbar. (If the batch is still open, or the order has not been marked as shipped, the RMA button will not appear.)

In the RMA Process dialog, enter the following RMA information:

  • Return Quantity – Enter the number of items being returned.

  • RMA# – Enter an ID for this RMA.

  • Re-stocking fee – If your organization charges a restocking fee, click the lookup button to select the restocking fee product.

Click OK. UX Online will process the return and create a new invoice detail line item that contains the quantity returned, the RMA#, and any applicable restocking fee and sales tax credit.

Click Save & Close in the invoice detail line item to return to the invoice. Review the new restocking fee line item, if applicable.

If freight charges were calculated on the original invoice and if you want to refund all or part of those freight charges, you will need to recalculate freight. This will cancel the original invoice detail line item for the original freight charges and create a new invoice detail line item with the prorated freight charges for the net product order. You have the option to override the newly created freight charges. Review the re-calculated freight charges.

Verify the new invoice totals and then click Save & Close.

If the return results in a credit balance on the invoice, you can issue a refund or transfer the credit to another invoice. For more information, see Invoice credit balance adjustments overview.

Processing product returns manually

If your organization manages sales inventory products, accepts returns of sales inventory products, and is not using the RMA process, we recommend the following manual processes to manage product returns.

Important

If the application parameter PAOrders.DisableCancelOnFulfilled is set to True, you will not be able to cancel a product sales transaction using the delete button if the product has been processed through order fulfillment (where the Shipped On date inside the invoice detail for the product transaction contains data).

Create an activity on the originating invoice record when you first learn from the customer that they are returning a product. This is to remind you that the product return is on its way. Advise the customer to include the invoice number on the return so that you can track it when it arrives.

When the returned product arrives, process the return in UX Online. The procedure you should follow depends on whether the customer has returned all of the products in the product sales transaction (i.e., ordered five; returned five) or some of the products (i.e., ordered five; returned three) and whether or not the order was for a product kit.

Processing a full product return manually

This section describes the entries you should make in UX Online if a customer returns an entire order (for example, the customer ordered five books and returned five books), this is not a return of a product kit, and you are not utilizing the RMA process for product returns.

Important

Perform this process after you have received the returned items. When you perform the steps outlined below, UX Online immediately adjusts the item’s quantity available to include the returned items. If you do this before the items are received, then the quantity available in UX Online will not be correct. Inventory is not a consideration for returns of sales non-inventory items.

In the originating product sales invoice, select a batch and cancel the invoice detail line item for the returned product (not the payment line item). In this example, cancel the invoice detail line item for the five books. See Canceling or deleting a product sales transaction.

Important

If the application parameter PAOrders.DisableCancelOnFulfilled is set to True, you will not be able to cancel a product sales transaction using the delete button if the product has been processed through order fulfillment (where the Shipped On date inside the invoice detail for the product transaction contains data).

If freight charges were calculated on the original invoice and if you want to refund all or part of those freight charges, you will need to recalculate freight. This will cancel the original invoice detail line item for the original freight charges and create a new invoice detail line item with the prorated freight charges for the net product order. You have the option to override the newly created freight charges.

Review the re-calculated freight charges. They should be $0.00 when all products are returned.

Verify the new invoice totals.

If the customer made a payment for the product sale, issue a refund:

Create an Activity Note, documenting the return or close the original activity that you created when the customer notified you that they were returning the product.

Click Save & Close to save your changes and close the invoice. Close and post the batch.

If your organization works with inventory control that is integrated with Microsoft Dynamics GP or Microsoft Dynamics SL, when you post the batch, the reversing entry to the quantity on hand in the accounting system inventory is automatic. An inventory transaction is created for the reversal that you will need to post to update the quantity on hand in the accounting system. UX Online always considers the unposted inventory in the accounting system in its calculation of available Inventory so that you do not oversell the product.

If your organization works with internal inventory control, when you post the batch, the reversing entry to the available inventory and quantity on hand in the product record is automatic.

Processing a partial product return manually

This section describes the entries you should make in UX Online if a customer returns part of an order (for example, the customer ordered five books and returned two books), this is not a return of a product kit or kit component, and you are not utilizing the RMA process for product returns.

Important

Perform this process after you have received the returned items. When you perform the steps outlined below, UX Online immediately adjusts the item’s quantity available to include the returned items. If you do this before the items are received, then the quantity available in UX Online will not be correct. Inventory is not a consideration for returns of sales non-inventory items.

In the originating product sales invoice, select a batch and cancel the invoice detail line item for the returned product (not the payment line item). For example, if the customer originally ordered five books, cancel the invoice detail line item for the five books. See Canceling or deleting a product sales transaction.

Important

If the application parameter PAOrders.DisableCancelOnFulfilled is set to True, you will not be able to cancel a product sales transaction using the delete button if the product has been processed through order fulfillment (where the Shipped On date inside the invoice detail for the product transaction contains data).

Create a new Product Sales transaction for the same product, entering the number of products the customer is keeping as the quantity ordered. For example, if the customer ordered five books but returned two books, create a new transaction for three books. See Creating a product sales invoice.

Before your save the invoice detail line item for the three books, manually update the Date Shipped and Packing Ticket Printed fields in the Delivery Section, entering the information contained in the original invoice detail line item.

Important

If you do not manually update the Date Shipped and Packing Ticket fields, the newly created invoice detail line item will be included in the orders to be processed for shipping. Since the items have already been shipped, failure to enter this information will result in duplicate shipments.

If freight charges were calculated on the original invoice and if you want to refund all or part of those freight charges, you will need to recalculate freight. This will cancel the original invoice detail line item for the original freight charges and create a new invoice detail line item with the prorated freight charges for the net product order. You have the option to override the newly created freight charges.

Review the re-calculated freight charges.

Verify the new invoice totals. Issue a refund for the returned items:

Create an Activity Note documenting the return or close the original activity that was created when you were notified of the impending return by the customer.

Click Save & Close to save your changes and close the invoice. Close and post the batch.

If your organization works with inventory control that is integrated with Microsoft Dynamics GP or Microsoft Dynamics SL, when you post the batch, the reversing entry to the quantity on hand in the accounting system inventory is automatic. An inventory transaction is created for the reversal that you will need to post to update the quantity on hand in the accounting system. UX Online always considers the unposted inventory in the accounting system in its calculation of available Inventory so that you do not oversell the product.

If your organization works with internal inventory control, when you post the batch, the reversing entry to the available inventory and quantity on hand in the product record is automatic.

Processing product kit returns manually

Returning all product kits ordered

Use the following procedure when the customer is returning the entire product kit order (all components). This procedure assumes that the customer is returning a product kit created in a previous batch, where the original batch is Closed, GL Detail Created and Posted to the accounting system.

Important

If the application parameter PAOrders.DisableCancelOnFulfilled is set to True, you will not be able to cancel a product sales transaction using the delete button if the product has been processed through order fulfillment (where the Shipped On date inside the invoice detail for the product transaction contains data).

In the originating product sales invoice, select a batch and cancel the invoice detail line item for the returned product kit and each detail line item for the related kit components. See Canceling or deleting a product sales transaction.

If the customer made a payment for the product sale, issue a refund:

If freight charges were calculated on the original invoice and if you want to refund all or part of those freight charges, you will need to recalculate freight. This will cancel the original invoice detail line item for the original freight charges and create a new invoice detail line item with the prorated freight charges for the net product order. You have the option to override the newly created freight charges.

Review the re-calculated freight charges. Verify the new invoice totals.

Create an Activity Note documenting the return or close the original activity that you created when the customer notified you that they were returning the product.

Click Save & Close to save your changes and close the invoice.

If your organization works with inventory control, when you post the batch, the reversing entry to the available inventory and quantity on hand in the product record is automatic if the return is for a sales inventory product kit.

Returning some of the product kits ordered

Use the following procedure when the customer is returning some of the product kits ordered. For example, the customer ordered five kits and is returning all components that equate to two product kits.

Note

You cannot process the return of a partial kit (some, but not all, kit components). In this scenario, you must cancel the entire product kit and its components and create a new product sales transaction for the components that were not returned, manually overriding the price based on your organization’s business rules.

This procedure assumes that the customer is returning a product kit created in a previous batch where the original batch is Closed, GL Detail Created and Posted to the accounting system.

Important

If the application parameter PAOrders.DisableCancelOnFulfilled is set to True, you will not be able to cancel a product sales transaction using the delete button if the product has been processed through order fulfillment (where the Shipped On date inside the invoice detail for the product transaction contains data).

In the originating product sales invoice, select a batch and cancel the invoice detail line item for the returned product kit and each of the related kit components. See Canceling or deleting a product sales transaction.

Create a new Product Sales transaction for the same product kit, entering the number of kits the customer is keeping as the quantity ordered. For example, if the customer ordered five kits but returned two kits, create a new transaction for three kits. See Creating a product sales invoice.

Open each detail line item for the new product kit and each kit component and manually update the Date Shipped and Packing Ticket Printed fields in the Delivery Section, entering the information contained in the original product kit invoice detail line item.

Important

If you do not manually update the Date Shipped and Packing Ticket fields, the newly created invoice detail line item will be included in the orders to be processed for shipping. Since the items have already been shipped, failure to enter this information will result in duplicate shipments.

If freight charges were calculated on the original invoice and if you want to refund all or part of those freight charges, you will need to recalculate freight. This will cancel the original invoice detail line item for the original freight charges and create a new invoice detail line item with the prorated freight charges for the net product order. You have the option to override the newly created freight charges.

Review the re-calculated freight charges. Verify the new invoice totals.

Issue a refund for the returned items:

Create an Activity Note documenting the return or close the original activity that was created when you were notified of the impending return by the customer.

Click Save & Close to save your changes and close the invoice. Close and post the batch.

If your organization works with inventory control, when you post the batch, the reversing entry to the available inventory and quantity on hand in the product record is automatic if the return was for a sales inventory product kit.

Chapter 33: Sales Order Fulfillment

After the sale, UX Online Order Fulfillment processing provides your organization with the ability track the fulfillment of your product sales orders at both the individual invoice level and at a global level, where you can view all product sales invoices awaiting fulfillment.

Note

Only sales order products, where Apply Freight in the product setup equals Yes, are eligible for Sales Order Fulfillment processing.

The first step in sales order fulfillment is to print packing tickets, which automatically updates the invoice detail line items with the date you printed the ticket and the ticket job number. While your organization might not use packing tickets, this step is required to update the invoice detail line items.

The next step is to prepare your orders for shipment.

The final step is to run a process that updates the invoice detail line items with the date shipped.

This documentation describes the standard UX Online processes for managing order fulfillment:

  • Printing packing tickets

  • Preparing an order for shipping

  • Marking an order as shipped

Printing packing tickets

You can easily print packing tickets for orders in closed and posted batches to help the staff members responsible for shipping orders gather the correct items for each order. When you generate the UX EasyPrint Packing Ticket Report and export it to a PDF, UX Online updates the invoice detail line items with the date you printed it and the print job number, giving you an internal audit trail of that part of the order fulfillment process. This process also makes your orders eligible for Orders Shipping Fulfillment. Only invoice detail records in a closed and posted batch are eligible for reporting.

Important

When you run any UX EasyPrint report, you must export the results to a PDF to complete the system job that updates the invoice detail with the date and print job.

From any of the UX work areas on the Navigation Tile Bar, click Reports to open a list of UX Online reports. In the Reports list, locate and open the UX EasyPrint Packing Tickets in the Reports list to initiate the report.

  • In the Report Viewer, select No in the Reprint field, and then select NULL from the Select Print Job list.

  • Click Run Report to generate the packing ticket report.

  • Export the packing tickets to PDF or Print. Either option is required for UX Online to trigger updates to the appropriate invoices with the system date and packing ticket job number.

Note

Full cycle sales order processing requires that you run the UX EasyPrint Packing Ticket Report and export the results to a PDF. Only transactions where the Packing Ticket Printed field is updated by the UX EasyPrint Packing Ticket Report will be available to be marked as shipped. If your organization does not use packing tickets, you may choose not to print hard copies of the report, but you must run the report and export the results to PDF to update the invoice detail.

Preparing an order for shipping

After printing the UX EasyPrint Packing Tickets report, the next step in fulfilling orders is to prepare the order for shipping and ship the package. This step is not a UX Online activity but internal to your organization based on internal packing and shipping business requirements.

Note

If an item has a serial number, you can record the serial number of the item actually shipped in the Serial Number field in the Delivery section of the product sales invoice detail line item.

Marking an order as shipped

After you have packed and shipped orders, the next step is to mark each order as shipped in UX Online. You can use Orders Shipping Fulfillment View to see which orders have been shipped and which orders are still awaiting fulfillment. Only those orders where the Packing Ticket Printed field was updated by the UX EasyPrint Packing Tickets report will appear on list of orders awaiting fulfillment.

In the Navigation Tile Bar, select the Product Sales work area > Product Sales > Orders Shipping Fulfillment View.

Click the Show Orders to be Fulfilled button. If you want to limit the orders that are displayed in the list, select a customer or a product, then click the Show Orders to be Fulfilled button.

Note

You can view a list of shipped orders by clicking the Display Shipped Orders button at the top of the list view. In addition, you can double-click any invoice in this list to view the original invoice.

In the Currently Viewing Unshipped Orders list, select one or more items to be processed as shipped.

Click Process Orders as Shipped on the list toolbar. A message will appear, asking you to confirm this action. Click OK.

Marking an order as shipped removes the invoice from the list of unshipped orders and adds it to the list of shipped orders. It also updates the Shipped On field on the product sales invoice item with the date that you performed this process.

If the invoice includes items that are tracked by serial number, you can enter the serial number of the item that was shipped. (If you need to enter more than one serial number, you can enter them in the same field, separated by commas, or add them to the Notes area of the invoice.)

To confirm the results of this process, click Display Shipped Orders to view the list of invoice records that have been processed for shipment. Click the Date Shipped column header to sort the records by date to view your processed records.

Committees and Rosters

Part 8: Committees and Rosters

You can use UX Online to manage your organization’s committees and rosters.

This information is divided into the following chapters:

  • Chapter 34: Committee Manager

  • Chapter 35: Roster Manager

Chapter 34: Committee Manager

Use the Committee Manager to set up and manage your organization’s committees and sub-committees and their members. When you have your committees and sub-committees set up in UX Online, you can easily keep track of committee member terms and officers and communicate with committee members via e-mail.

Before you begin creating committees and assigning members to them, you should create committee categories if necessary and add the committee member titles your organization uses.

This information includes the following topics

  • Creating a committee category

  • Setting up committee member titles

  • Deleting a committee member title

  • Committee setup overview

  • Creating a committee

  • Committee members setup overview

  • Adding committee members overview

  • Assigning committee member new terms

  • Removing a committee member

  • Deleting a committee

Creating a committee category

You can use committee categories to create groups of committees that share common characteristics. For example, your organization might include joint committees, standard committees, executive committees, and political action committees. If you create categories and assign committees to them, you can create reports for specific committee categories or perform queries on those categories. (Creating and using committee categories is optional.)

You can create committee categories before you set up your committees, or you can create the categories and assign committees to them after you set up committees.

Important

Always follow guidance provided in the UX Online 8 – Customization Guidance document that is available in the Resource Center.

In the Navigation Tile Bar, select the Administration work area > Solutions > [your organization’s custom solution]. Select Entities to display a list of entity components.

Note

Only users with system customization security access will be able to set up committee categories.

In the left Navigation, click the expand caret next to Entities to expand the list of entities. Click the expand caret next to the Committee entity to display entity assets. Select Fields to display a list of entity fields.

Locate and double-click to open the pa_category field.

In the Options area at the bottom of the Field: Category of Committee window, you will see a list of existing items (categories). Click Add to create a new item.

On the right side of the Options area, the system defaults the Label name of the new item to “Item” and assigned an option value. Override the default label with the name of the new category you wish to add and override the option value with a unique value greater than 1000 so that custom options are readily recognizable. They will be preserved during the upgrade process.

Repeat steps for each category you want to add.

Use the Move Up and Move Down buttons located along the right side of this window to re-order the categories you created. You also can use the Sort Ascending button to sort the categories in ascending alphanumeric order or select the Sort Descending button to sort in descending alphanumeric order. The committee categories will appear in this order in the Category list on the committee record.

To define a default category to be used when creating a new committee, select the category in the Default Value field.

Click Save & Close.

Select Publish All Customizations on the toolbar. This will update the database to include the new categories.

Setting up committee member titles

If your organization uses specific titles for the roles committee members perform, such as President, Chairperson, or Secretary, you can add them to the Titles table.

Note

The titles you define here can also be used for chapter and region officers, not just committees.

To access this information, in the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Titles to open the List view of Active Titles. This list opens in a new window.

In the Titles list, click New on the List View toolbar to create a new title.

Enter the title name (for example, President or Chairperson).

If you want to create a custom report that sorts committee members in order according to their title sequence, enter a title sequence number for this title. For example, if you want the committee president to be listed first, regardless of his/her last name, enter 1 as the sequence when creating the title record for president.

Note

The base UX Committee Roster report sorts committee members alphabetically.

Click Save & Close to save this record and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Deleting a committee member title

If you have titles that are no longer being used, you can delete them. You cannot delete a title if it is assigned to any committee members, or to a chapter or region officer. If you try to delete a title that is currently being used, a message will appear informing you that the title cannot be deleted.

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Titles to open the List view of Active Titles. This list opens in a new window.

In the Titles list, click to select the title you want to delete.

Click Delete on the List View toolbar. A message will appear asking you to confirm deletion. Click OK to delete. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Committee setup overview

This section provides an overview of how to set up all of your committees in UX Online. As your organization grows and changes, you can add committees at any time.

Note

Before beginning your committee setup, we recommend that you review all of your existing committees and committee members to identify which committee and committee members you want to keep. This process may be done prior to conversion so only those committees that your organization uses with are set up in UX Online.

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Committees to open the List View of Active Committees. This list opens in a new window.

See Creating a committee category and Creating a committee for additional information on committee setup.

Creating a committee

Follow this procedure to create a committee or subcommittee. You can create a committee at any time.

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Committees to open the List View of Active Committees. This list opens in a new window.

Click New on the List View toolbar to create a new committee. In the General section of the Committee record, enter the general committee setup information:

  • Name – Enter the name of the committee, for example, Board of Directors.

  • Category – If necessary, select a committee category from the list.

  • Committee Code – Enter a code or abbreviated name for this committee. For example, the committee code for the Board of Directors could be BOD.

  • Sequence – Assign a sequence number to this committee if you want to be able to sort committees on reports according to an order you choose. For example, if you want the Board of Directors committee to appear first, assign 1 as the sequence number.

  • Parent Committee – If this is a subcommittee, enter or select the parent committee.

  • Type – If you did not enter a parent committee, this field will display Committee. If you entered a parent committee, this field will display Sub-committee.

  • Owner – Displays the user ID of the user who created this record.

  • Extended Description – Enter a description of this committee if appropriate.

Click Save. After saving this record, other options on the left navigation bar are activated.

The Web section is used with Protech’s MX Online, and will be set as needed during that implementation. Do not change these settings.

Click Save & Close to save this record and return to the list of committees. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Committee members setup overview

This section provides an overview of how to assign individuals to your committees in UX Online. As your organization grows and changes, you can add individuals to committees at any time.

Adding your committee members to the appropriate committee in UX Online allows you to target these individuals quickly for any type of communication using Quick Campaigns and Advanced Find.

In addition, having all your committee members organized on the appropriate committees also allows you to keep track of past committee members, current committee members, and nominees. As committee members’ term dates expire, they automatically appear on the Committee Members list as past members. As new members are added to a committee as nominees with upcoming terms, they are listed as nominees. As their term begins, they are automatically listed as current members.

Another timesaving feature in the committee manger is the Assign New Term process. This allows you to select specific individuals on a committee or all committee members, who have been elected to serve another term. This process creates a new committee member record with the new term, while maintaining a historical record of each term a committee member serves. This feature is available on the List View toolbar on all Committee Member list views, whether you are working from the view of all committee members, the view of committee members from within a committee, or the view within a contact record.. See Assigning committee member new terms for additional information.

When you work in the Committee Member list, click on committee member’s name to open their main contact record. To open the committee member record, select and click the row.

In the Committee Members list, you can limit this display to members of a particular committee using the View menu.

The View menu comes with five standard system views:

  • Active Committee Members – This displays all committee members whose status is Active. (A committee record can have an Active status even if their term has expired or has not started yet.)

  • Current Members – This displays committee members whose Term Begin date is prior to today’s date and Term End Date is later than today’s date.

  • Inactive Committee Members – This displays committee members who have had their record deactivated.

  • Member Elects and Nominees – This displays committee members who have a Term Begin date later than today’s date.

  • Past Members – This displays committee members who have a Term End date prior to today’s date.

In addition to the standard System Views, you may customize My Views which display based on your username. Developing these custom views is explained later in this documentation. (For more information, see Advanced Find and Saved Views.)

To organize the data displayed in this view, you may sort the data by selecting any of the column headers.

You may further limit the data displayed here to a particular committee by entering all or part of the committee name or committee code in the Find field. Enter the committee code or name here and click the Lookup button to retrieve data for that committee only.

Adding committee members overview

You can use three methods to add a contact to a committee:

Each of these options is explained in this section.

Add committee members using the committee record

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Committees to open the List View of Active Committees. This list opens in a new window. Open the committee record where you want to add committee members.

In the committee record Navigation Pane, click Committee Members to open the Committee Members Associated View. On the List View toolbar, click Add New Committee Member.

In the General section of the Committee Member record, enter the committee member setup information:

  • Committee Code – Displays the committee code of the committee you selected.

  • Committee – Displays the name of the committee you selected.

  • Member Type – Select the type of committee member: Member, if you are adding a current member; Nominee, if the member has been nominated, or if they have been elected but their term has not started yet; or Staff, if this contact is not a committee member, but a staff member for the committee.

Note

The system will automatically update any committee member’s member type when their terms begin or end. This update takes place nightly at 11:00 p.m.

  • Title – Select the position or title of the committee member if appropriate.

  • Contact – Select the individual you want to add to this committee.

  • Member Status – System controlled display of the committee member status based on their term start and end dates.

  • Term Begins – Enter the beginning date of the committee member’s term in MM/DD/YYYY format, or click the Calendar button to select the date. Note: If the term begins in the future, we recommend that you select Nominee as the Member Type.

  • Term Ends – Enter the ending date of the committee member’s term in MM/DD/YYYY format, or click the Calendar button to select the date.

  • Comments – Enter any additional information about the committee member if appropriate.

Click Save & Close to save this record and return to the list.

Add committee members using the Committee Members list

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Committee Members to display a list of existing committee members. This list opens in a new window.

Click New on the List View toolbar. In the General section of the Committee Member record, enter the general committee member setup information:

  • Committee Code – Enter the code of the committee you want to assign this contact to.

  • Committee – Click the Lookup button to select the committee you want to assign this contact to.

  • Member Type – Select the type of committee member: Member, if you are adding a current member; Nominee, if the member has been nominated for the committee, but has not been elected yet; or Staff, if this contact is not a committee member, but a staff member for the committee.

  • Title – Select the position or title of the committee member if appropriate.

  • Contact – Select the individual you want to add to this committee.

  • Member Status – System controlled display of the committee member status based on their term start and end dates.

  • Term Begins – Enter the beginning date of the committee member’s term in MM/DD/YYYY format, or click the Calendar button to select the date. Note: If the term begins in the future, we recommend that you select Nominee as the Member Type.

  • Term Ends – Enter the ending date of the committee member’s term in MM/DD/YYYY format, or click the Calendar button to select the date

  • Comments – Enter any additional information about the committee member if appropriate.

Click Save & Close to save this record and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Add a committee member using the Contact record

From any of the UX work areas on the Navigation Tile Bar, click Contacts to display a list of contact records. Locate and open the contact record that you want to add to a committee.

In the Navigation Pane of the contact record, click Committee Members to open the Committee Members Associated View, displaying a list of committees to which this contact is assigned, including current, past, and future committee assignments.

Click Add New Committee Member on the List View toolbar to open a new committee member record. In the General section of the Committee Member record, enter the general committee member setup information:

  • Committee Code – Enter the code of the committee you want to assign this contact to.

  • Committee – Click the Lookup button to select the committee you want to assign this contact to.

  • Member Type – Select the type of committee member: Member, if you are adding a current member; Nominee, if the member has been nominated for the committee, but has not been elected yet; or Staff, if this contact is not a committee member, but a staff member for the committee.

  • Title – Select the position or title of the committee member if appropriate.

  • Contact – Select the individual you want to add to this committee.

  • Member Status – System controlled display of the committee member status based on their term start and end dates.

  • Term Begins – Enter the beginning date of the committee member’s term in MM/DD/YYYY format, or click the Calendar button to select the date. Note: If the term begins in the future, we recommend that you select Nominee as the Member Type.

  • Term Ends – Enter the ending date of the committee member’s term in MM/DD/YYYY format, or click the Calendar button to select the date

  • Comments – Enter any additional information about the committee member, if appropriate.

Click Save & Close to save this record and return to the Committee Members Associated View for the contact record.

Assigning committee member new terms

This section explains how to assign committee members to a new term. Typically, non-profit organizations allow members to vote each year on who should server on specific committees. You can assign new terms to those committee members who are re-elected for the new term. You can perform this procedure for a single committee member or for multiple committee members, and for a single committee or for multiple committees, depending on your organization’s term and voting policies and procedures.

When you assign a new term to a committee member, each term is treated as a separate record, and a new committee member record is added to their contact record. Because of this, you can see a single committee member listed multiple times in the Committee Members list. For example, assume that Nancy Aalbers is serving a term on the Watersheds committee for the 2015 calendar year. If you use this procedure to assign her a new term on the committee for 2016, her name will appear twice in the list.

Note

Committee members whose terms have expired are not removed from the committee; their committee assignments, showing the terms they served, will still appear in the Committee Members list if you select the Past Members view.

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Committee Members to display a list of all committee member records.

If necessary, use the Find or View fields to find the particular committee or set of committee members you are assigning a new term. (For more information about using these fields, see Advanced Find and Saved Views.)

Select each committee member record that was re-elected for a new term. To select more than one committee member, press the Ctrl key as you click on each member. To select all the committee members shown, click the checkmark icon on the column heading bar.

In the List View toolbar, click Assign New Term.

In the Select New Term dialog, enter the new term beginning and ending dates in MM/DD/YYYY format, or click the Calendar button to select the dates. Click OK.

In the New Term Creation Confirmation dialog, review the information to verify your selections, and then click OK.

A dialog will appear showing the progress of adding new terms. When the process is finished, the Committee Members list will appear. After refreshing the list, verify that the new terms have been added for each committee member you selected.

Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Removing a committee member

If you have rights to delete members from a committee, you can use any of these three methods:

Note

Committee members whose terms have expired are not automatically removed from the committee; their committee assignments, showing the terms they served, will still appear in the Committee Members list if you select the Past Members view.

Remove members using the committee record

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Committees to open the List View of Active Committees. This list opens in a new window. Open the committee record where you want to delete committee members.

In the committee record Navigation Pane, click Committee Members.

Select the member you want to remove from this committee. To select more than one member, press the Ctrl key as you click each member.

On the List View toolbar, click Delete Committee Member.

In the confirmation dialog, click OK to confirm or Cancel to cancel this action and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Remove members using the Committee Members list

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Committee Members to display a List View of Active Committee Members. This list opens in a new window.

In the Committee Members list, select the contact’s committee assignment that you want to remove. To select more than one record, press the Ctrl key as you click each contact. (Remember that a contact can appear multiple times if they are assigned to more than one committee, or more than one term for a committee. Be sure to select the correct committee assignment.)

On the List View toolbar, click Delete.

In the confirmation dialog, click OK to confirm deletion and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Remove a member using the contact record

From any of the UX work areas on the Navigation Tile Bar, click Contacts to display a list of contact records. Locate and open the contact record that you want to add to a committee.

In the Navigation Pane of the contact record, click Committee Members to open the Committee Members Associated View, displaying a list of committees to which this contact is assigned, including current, past, and future committee assignments.

Select the committee assignment from which this contact should be removed. To select more than one committee assignment, press the Ctrl key as you click on each committee.

On the List View toolbar, click Delete.

In the confirmation dialog, click OK to confirm or Cancel to cancel this action and return to the Committee Members Associate View of the contact record.

Deleting a committee

Deleting committees from UX Online is only possible from one area and only available to those users who have the rights to delete committees.

Note

If the committee you want to delete has committee members associated with it, you will not be able to delete it until you remove all contacts from the committee. Also, if the committee is the parent committee for another committee, you will not be able to delete it unless you assign the subcommittee to another parent committee, or delete the subcommittee.

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Committee Manager > Committees to open the List View of Active Committees. This list opens in a new window. Select the committee record where you want to delete

On the List View toolbar, click Delete.

In the confirmation dialog, click OK to confirm or Cancel to cancel this action and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Chapter 35: Roster Manager

Use the Roster Manager to manage your organization’s roster groups, rosters, and roster members. Rosters give you the ability to group individuals, and they provide a simple way to target a group of contacts you want to communicate with. For example, you can use rosters to help manage promotional mailings, membership updates, annual conference information, community action forums, task force initiatives, and so on.

This chapter includes the following information:

  • Rosters setup overview

  • Creating a roster group

  • Creating a new roster

  • Adding roster members

  • Adding roster members using the Roster Members Utility

  • Removing a roster member

  • Assigning a roster to a different group

  • Deleting a roster

  • Deleting a group

Rosters setup overview

Because every roster must be assigned to a roster group, you will need to create Roster groups before you begin creating rosters and assigning members to them. The group code allows you to organize similar rosters within a common group. This is useful when you create reports, because you can use it to print information about a specific set of rosters.

As your organization grows and changes, you can add, deactivate, or delete rosters at any time.

Creating a roster group

Before you begin creating a roster, you must create roster groups. Each roster you create must be assigned to a group that shares common characteristics. For example, your organization might use rosters for mailing campaigns, task force rosters, special interest groups, and sponsors. By creating roster groups, you can create reports for specific roster groups, or perform queries on those groups.

As your organization’s needs change, you can add more roster groups at any time.

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Group to open a List View of Active Groups. This list opens in a new window.

To create a new group, click New on the List View toolbar. In the General section of the Group record, enter the general roster group setup information:

  • Group Code – Enter a group ID, or abbreviated nickname. For example, you could enter SIG as the group code for Special Interest Groups.

  • Sequence – Assign a sequence number to the group to define the order in which this group should display on reports.

  • Name – Enter the full name of the group.

  • Description – Enter a description of this roster group if necessary.

Click Save. Saving this record activates the following options on the Navigation Pane, where you can continue working with this record:

    • Click Roster Members to view all roster members attached to any roster within this group. You may also add members to any roster in this group from this tab.

    • Click Rosters to view rosters in this group, and to create rosters. When creating rosters from this area, the group in which you are currently working will be the default group for rosters you create.

Click Save & Close to save this record and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Creating a new roster

Follow this procedure to create a roster. You can create a roster at any time.

Hint

You also can create rosters from the Active Groups list by double-clicking the group you want to add a roster to, and then clicking Rosters in the record Navigation Pane.

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Rosters to open the List View of Active Rosters. This list opens in a new window.

To create a new roster, click New on the List View toolbar. In the General section of the Roster record, enter the general roster setup information:

  • Roster Code – Enter a short Roster ID for your Roster. For example, you could use 16FALLPROMO for the 2016 Fall Promotional roster.

  • Group – Select the appropriate group to categorize this roster.

  • Name – Enter the full name of the roster.

  • Owner – Displays the user ID of the user who created this record.

  • Sequence – Assign a sequence number to this roster if you want to be able to sort rosters on reports according to an order you choose. For example, if you want the 2009 Fall Promotional roster to appear first, assign 1 as the sequence number. If your organization does not utilize a roster sort sequence, then enter 1 for all rosters.

  • Description – Enter a full description of this roster if needed.

In the User Defined section of the new roster record, enter optional information on 10 additional fields used to track roster-specific information about the members assigned to this roster. There are 2 bit fields (UFB), 4 string (UFS) fields, 2 currency (UFC) fields, and 2 date (UFD) fields available to define as needed. Each roster can have its own set of user-defined fields.

  • To create a user defined field, click on the field type you want to create (bit, string, etc.), and enter a name that describes the data you want to track. For example, you could enter Annual Sales Revenue, Level of Education, or Years in the Industry. When you add members to this roster, these fields will appear on the roster member record so you can enter the necessary information about that particular roster member.

The Web section is used with Protech’s MX Online and will be set as needed during that implementation. Do not change these settings.

Click Save. Saving this record activates several options on the Navigation Pane:

  • Click Roster Members to view all roster members attached to this roster. You may also add members to this roster from this location.

Click Save & Close to save this record and return to the list. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Adding roster members

This section explains how to add individual members (contacts) and companies (accounts) to a roster. Rosters give you the ability to group individuals and companies and provide a simple way to target a group of contacts or accounts you want to communicate with. For example, you can use rosters to help manage promotional mailings, membership updates, annual conference information, community action forums, task force initiatives, and so on.

There are four ways in which a contact or account may be added to a roster:

  • Using the group record. You can use this method if you have just created a group and roster, and want to begin adding members to create the roster member list.

  • Using the roster record. You can use this method if you have just created the roster record and want to begin adding the list of members to the roster.

  • Using the contact or account record. You can use this method when you are working with a single contact or account record that you want to add to one or more rosters.

  • Using the roster members list. You can use this method when you want to add multiple members to multiple rosters.

You can also add a group of members to a roster using the Roster Members Utility. For more information, see Adding roster members using the Roster Members Utility.

Adding roster members using the group record

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Group to open a List View of Active Groups. This list opens in a new window. Open the group where you want to add roster members.

In the Group record, click Roster Members in the Navigation Pane to open the Roster Members Associated View. Click Add New Roster Member on the List View toolbar. In the General section of the Roster Member record, enter the general roster member information:

  • Group – Displays the group you selected to add roster members to.

  • Roster – Click the Lookup button to select the roster you want to add this member to.

  • Roster Code – Displays the roster code of the roster you selected in the lookup.

  • Member Contact – Click the Lookup button to select the individual you wish to add to this roster.

  • Member Account – Click the Lookup button to select the company you wish to add to this roster.

  • Comments – Enter any comments pertinent to this roster member.

Note

You cannot enter both a member contact and a member account. You must select one or the other.

In the User Defined area, enter additional information that your organization requires for this roster.

Click Save & Close to save this record and return to the Roster Members Associated View.

Adding roster members using the roster record

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Rosters to open the List View of Active Rosters. This list opens in a new window. Open the roster to which you want to add roster members.

In the Navigation Pane of the roster record, click Roster Members to open the Roster Members Associated View. Click Add New Roster Member on the List View toolbar.

In the General section of the Roster Member record, enter the general roster member information:

  • Group – Displays the group you selected to add roster members to.

  • Roster – Click the Lookup button to select the roster you want to add this member to.

  • Roster Code – Displays the roster code of the roster you selected in the lookup.

  • Member Contact – Click the Lookup button to select the individual you wish to add to this roster.

  • Member Account – Click the Lookup button to select the company you wish to add to this roster.

  • Comments – Enter any comments pertinent to this roster member.

Note

You cannot enter both a member contact and a member account. You must select one or the other.

In the User Defined area, enter additional information that your organization requires for this roster.

Click Save & Close to save this record and return to the Roster Members Associated View.

Adding roster members using the contact or account record

From any of the UX work areas on the Navigation Tile Bar, click Contacts or Accounts to display a list of contact or account records. Locate and open the record that you want to add to a roster.

In the Navigation Pane of the record, click Roster Members to open the Roster Members Associated View. Click Add New Roster Member on the List View toolbar.

In the General section of the Roster Member record, enter the general roster member information:

  • Group – Displays the group you selected to add roster members to.

  • Roster – Click the Lookup button to select the roster you want to add this member to.

  • Roster Code – Displays the roster code of the roster you selected in the lookup.

  • Member Contact – Click the Lookup button to select the individual you wish to add to this roster.

  • Member Account – Click the Lookup button to select the company you wish to add to this roster.

  • Comments – Enter any comments pertinent to this roster member.

Note

You cannot enter both a member contact and a member account. You must select one or the other.

In the User Defined area, enter additional information that your organization requires for this roster.

Click Save & Close to save this record and return to the Roster Members Associated View.

Adding roster members using the Roster Members list

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Roster Members to display a list of existing roster members. This list opens in a new window. Click New on the List View toolbar.

In the General section of the Roster Member record, enter the general roster member information:

  • Group – Click the Lookup button to select the roster group you want to add this member to. If you use the Lookup to select your roster first, the system will populate the group for you.

  • Roster – Click the Lookup button to select the roster you want to add this member to.

  • Roster Code – Displays the roster code of the roster you selected in the lookup.

  • Member Contact – Click the Lookup button to select the individual you wish to add to this roster.

  • Member Account – Click the Lookup button to select the company you wish to add to this roster.

  • Comments – Enter any comments pertinent to this roster member.

Note

You cannot enter both a member contact and a member account. You must select one or the other.

In the User Defined area, enter additional information that your organization requires for this roster.

Click Save & Close to save this record and return to the List. Because the list opened in a new window, click the “X” in the upper right hand corner of the window to close it.

Adding roster members using the Roster Members Utility

If you need to add a number of account or contact records to an existing roster, you can use the Roster Members Utility. You can import a list of accounts or contacts using either a saved query that you have created using Advanced Find, or you can import a list of accounts or contacts saved in a .csv (comma separated value) file.

You can only use this utility to add members to a roster that already exist in UX Online.

You can add records to a roster that already has roster members assigned. Any records that are already on the roster will not be duplicated.

Adding roster members using a saved query

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Roster Member Utility to initiate the process. Select Advanced Find View as the import type.

Important Note

If you are importing contact records using an Advanced Find View, the Advanced Find View must include column for ‘Full Name’.

If you are importing account records using an Advanced find View, the Advanced Find View must include a column for ‘Account Name’.

After selecting the import type, the Roster Member Utility dialog refreshes for adding your search criteria.

  • Advanced Find View – Use the Lookup button to select your saved query that displays the accounts or contacts you want to add to the roster.

  • Group – Use the lookup to select the Group for the imported records.

  • Roster – Use the lookup to select the Roster for the imported records.

  • Ignore Duplicates – If you want UX to ignore duplicates, select the Ignore Duplicates checkbox  to exclude any records that may already be a member of your selected roster.

Click Run to initiate the process. Once the process is completed, review the roster to verify that the records were added.

Adding roster members using a .csv file

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Roster Member Utility to initiate the process. Select CSV file as the import type.

Important Note

Any Excel document can be saved as a .csv file in order to use this utility. However, the records in the Excel document must already exist in the UX Online database. In addition, the Excel document must contain the “Account Number” or “Contact Number” field. This is the record ID, or unique identifier, that UX needs in order to associate the account or contact record to the roster.

The column heading for account records in the .csv file must = Account Number. The column heading for contact records in the .csv file must = Contact Number. The utility is looking for an exact match.

After selecting the import type, the Roster Member Utility dialog refreshes for adding your search criteria.

  • CSV File Name – Use the Browse button to select your saved .csv file of accounts or contacts you want to add to the roster.

Important

The .csv file should include only accounts or contacts but not both. If you need to import both account and contact records into a roster, you will need to complete this procedure twice – once with an account .csv file and once with a contact .csv file.

  • Group – Use the lookup to select the Group for the imported records.

  • Roster – Use the lookup to select the Roster for the imported records.

  • Ignore Duplicates – If you want UX to ignore duplicates, select the Ignore Duplicates checkbox  to exclude any records that may already be a member of your selected roster.

Click Run to initiate the process. Once the process is completed, review the roster to verify that the records were added.

Removing a roster member

If you have rights to remove members from a roster, there are four methods you can use:

  • Using the contact record. You can use this method if you have a single member you need to remove from one or more rosters.

  • Using the roster record. You can use this method if you have multiple members you want to remove from a roster.

  • Using the Roster Members list. This method works well if you have multiple members you want to remove from multiple rosters.

  • Using the group record. Use this method if you have multiple members you want to remove from multiple rosters within a roster group.

All methods require that you identify the roster member record and select Delete from the List View toolbar in each of the respective areas. A message will appear asking you to confirm removal of the selected roster member record. Click OK to proceed or Cancel.

Assigning a roster to a different group

If you decide that a roster should be in a different group, you can remove it from its current group and assign it to a different one at any time. You can do this for a single roster as described below or by editing multiple rosters simultaneously as long as they will all be reassigned to the same group.

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Rosters. Open the roster you want to reassign.

In the General section, click the Group Lookup button to select the Group for this roster.

Click Save & Close to save your changes and close the roster.

Deleting a roster

If you have a roster that you no longer use, you can delete it. Follow this procedure to remove a roster from UX Online.

Important

You must remove all roster members from the roster before deleting it.

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Rosters to view a list of existing rosters. This list opens in a new window. Open the roster you want to delete.

To verify that there are no members on this roster, click Roster Members in the Navigation Pane. If any members are still on the roster, click the check box next to the Member column heading. This selects all members on this roster. Then, on the List View toolbar, click Delete Roster Member.

A message will appear asking you to confirm removal of the selected members. Click OK to proceed, and then click Save & Close.

In the Rosters List, verify that the roster you want to remove is still selected. On the List View toolbar, click Delete.

A message will appear asking you to confirm removal of the selected roster. Click OK to proceed or Cancel to leave the roster in the system.

Deleting a group

If you have any roster groups that you no longer use, you can delete them. Follow this procedure to delete a roster group.

Important

You will not be able to delete a roster group if it includes any rosters. You can assign the rosters to different groups if you want to keep using them, or you can delete the rosters if you no longer need them.

In the Navigation Tile Bar, select the Membership work area > Committees/Rosters > Roster Manager > Group to view a list of existing groups. This list opens in a new window. Open the group you want to delete.

To verify that there are no rosters in this group, click Rosters in the record Navigation Pane. If there are, you must first delete them or assign them to a different group before you can delete this one. For more information about deleting rosters, see Deleting a roster.

When you have verified that there are no rosters in this group, click Save & Close.

On the List View toolbar, click Delete for your selected group. A message will appear asking you to confirm removal of the selected group. Click OK to proceed or Cancel to leave the group in the system.