Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
While the Publishing module allows you to carry out most of the daily distribution activities, the Accounting module is where you handle the financial side of newspaper circulation.
There are two very different aspects to circulation accounting: the account side (e.g., carriers and dealers), and the subscriber side. It is important to understand that these are handled separately in Circulation.
Are billed in groups (known as “bill sources”) at regular intervals.
Are usually billed for past charges and credits.
Are independent contractors. With carrier collect subscribers, the carrier “buys” the paper wholesale (the account bill) and “sells” it retail (collecting from subscribers). With office pay subscribers, the carrier still buys and sells the paper, but the payment is received at the newspaper office. The wholesale is deducted from the retail, and the difference is credited to the carrier.
Use account rates, both for charges and credits. Subscriber rates do not affect account rates, unless the account rates are specifically based on a subscriber rate code.
Are sent renewal notices individually, according to their own expiration dates.
Pay in advance for future services (except in the case of grace owed).
Are customers who “buy” the newspaper from the carrier.
Use subscriber rates. If the subscriber is carrier collect, a rate may or may not be assigned (according to Business Rules).
Although accounts and subscribers do not directly influence one another, Circulation follows the same accounting steps for both:
Rating is used to determine account draw charges and office pay credits, and subscription rates for subscribers. Other charges and credits (such as tax) are also taken into account. This takes place (for accounts) in account billing processing and (for subscribers) subscriber payment processing.
Account bills or subscriber renewal notices are printed.
Account and subscriber payments are entered into the system.
Transactions are interfaced to the GL, either automatically or by printing reports. A transaction will either debit or credit a GL account. Any payment, charge and/or credit will have an offsetting entry (i.e., a transaction will debit one account and credit another).
These topics are discussed further in the following sections.
Accounts (carriers and dealers) are rated based on their draw. Rates may be copy rates (a rate per paper) or period rates (a rate per subscription or single copy equivalent). If using a copy rate, the draw charge for a month would be the total draw for that month times the copy rate. If using period rating, Circulation would use the formula:
(total draw * period rate) / number of days in period
Period rates may (based on Business Rules) vary by day of the week. In vary-by-day rating, each day of the week has its own period rate. For example, you could have a monthly rate of 4.00 per subscription for all Sundays in the month, 1.50 per subscription for all Mondays, 1.50 for all Tuesdays, etc. The above formula would still be used, but for each weekday separately.
Account rates can change based on draw type, delivery schedule, day of week, or (if allowed by Business Rules) the rate code of the subscriber being delivered. So, a single account may receive different rates for different types of draw. See Account Rates in the Setup Manual for more information.
Payments made by subscribers and carriers/dealers are often by credit card. To process the credit card payment and insure that the credit card information is valid, payment authorization is typically done using a third party authorization vendor such as Braintree, Payway Complete or Cybersource. The vendor authenticates the card information with the financial institution issuing the card and, when the payment is accepted, posts the credit card charge or refund. Authorization is usually done in real time so that the user knows immediately whether the payment has been authorized. The text of the authorization messages that display in Customer Service and iServices during this process can be defined in .
To avoid compromising sensitive data, credit card numbers associated with payments are typically not accessible in Circulation. Instead, a token provided by the authorization vendor is displayed, along with the last four digits of the card number. This is known as tokenization. Most tokenized environments also feature off-site credit card storage where the full credit card numbers are not stored in Circulation at all. In environments where credit card numbers are not tokenized and off-site, NAVIGA strongly recommends encrypting the numbers in the database (see in the Setup Manual).
An additional level of security is offered if you use Circulation’s Hosted Order Page (HOP). With a HOP solution, no credit card information is actually entered in Circulation or iServices, even through the user interface. Instead, the HOP is called from the credit card authorization provider’s system and entered in a separate browser window. Using a HOP places Circulation out of scope for compliance with PCI (Payment Card Industry) standards. Circulation supports credit card entry via a HOP for Braintree, Payway Complete, Cybersource and other vendors.
Note:
Real-time credit card authorization and the Hosted Order Page are a licensed, add-on options in Circulation. Contact Newscycle Support for licensing information. In addition, the use of third-party solutions requires a separate contract with the service provider.
Most real time payment authorization solutions use Circulation’s Payment Authorization Service (PAS), a web service that communicates between Circulation and the authorization vendor. (The exception is viaWarp.) To use the PAS, the Business Rule— Which product integration is used for real-time payment authorization? (Payment Auth - Account and Payment Auth - Subscrib sections) should be set to “DTI”.
Business Rules in the Payment Auth - Account and Payment Auth - Subscrib sections determine the host name, URL, payment authorization vendor and other parameters for the Payment Authorization Service. See Tech FAQ #13 for information in installing the Payment Authorization Service.
In a tokenized environment, full credit card numbers are typically not stored in the Circulation database, even in encrypted form. Instead the PAS sends back a token, also known as a vault ID, which is the ID of the record where the number is stored in the vendor’s credit card vault. In this environment a masked credit card number is stored in Circulation for display purposes. A masked credit card number will typically be displayed as ************0123
, with only the last four digits visible to the user. See in the Setup Manual for more information.
Note:
In some cases, such as conversion or Lockbox Processing, not even a masked credit card number may be provided with the vault ID. In these cases “VAULTED VALUE” is stored as the credit card number.
The diagram below illustrates how credit card numbers are tokenized by the credit card vendor, and a token returned via the PAS.
Business Rules in the Payment Auth - Account and Payment Auth - Subscrib sections determine the host name, URL, merchant ID, public and private keys, and other parameters used by the PAS with a payment authorization vendor. They are specific to the vendor (Braintree, Cybersource etc.).
If you currently store credit cards in Circulation but are moving to a tokenized solution, see Circulation FAQ 105 for the steps involved in encrypting and vaulting your current numbers. Additional Circulation FAQs detail the steps needed to implement a specific solution, such as Braintree or viaWARP.
Note:
When moving to an off-site credit card environment, including the Hosted Payment Page, be sure you have a Credit Card Account record defined with a blank credit card type and associated GL account.
In some cases, a credit card vendor may not pass back a credit card type and there are not enough digits in the masked number to determine the credit card type (and hence the GL account to be used).
This can also happen when importing vaulted payments via Lockbox Processing. See Credit Card Account in the Setup Manual for more information.
Circulation’s HOP uses the credit card tokenization process described above for credit card authorization and storage, but it also removes data entry of credit card information from Circulation. It does this by displaying a separate third party browser window when entering a payment in Customer Service, Batch Payments or iServices. An example of a HOP is shown below.
Once the credit card information is entered, the rest of the payment can be completed within Circulation or iServices. A token (and typically a masked credit card number) is returned to Circulation, as with other tokenized solutions. The architecture of the HOP is illustrated below.
If using a HOP solution, the Business Rule Which off-site credit card storage and authorization service do you use? (Pymt Auth - General) must be set to “Hosted Page”. The HOP vendor is configured by another Business Rule in the same section, Which hosted page credit card authorization service do you use?
As with tokenization, additional Business Rules in the Payment Auth - Account and Payment Auth - Subscrib sections determine settings for specific hosted page vendors. Circulation FAQs are available for most vendors, detailing the specific setup needed.
This section shows account and subscriber rating side by side. The two examples illustrate how accounts and subscribers influence each other in the GL, even though they are not directly related.
An office pay subscriber pays a discounted 29.20 for a flat rate 3-month subscription beginning January 1, 2007. The expiration date is April 1, 2007. The full cost for three months is 30.10. The newspaper uses a single copy rate.
The copy rate is calculated as the subscription amount paid divided by the actual number of copies the subscriber will receive. Assuming a 7-day subscription (and every day is a publishing day), the copy rate would be 29.20 / 90 days (31 days in January and March, plus 28 days in February), or 0.324444. In addition, Circulation calculates the average discount rate (0.90 / 90 days) as 0.01.
Assuming no changes (i.e., new payments or renewals), the unearned revenue at the end of January would be 19.14 (or 59 days * 0.324444). The total earned revenue would be 29.20 - 19.14, or 10.06. The discount earned would be 0.31 or 0.90 - 0.59 (59 days times 0.01 average discount rate).
On the account billing side, the account is charged and then credited for delivery to office pay subscribers. Assuming that the account is rated per copy, and the rates are 0.29 charge and a 0.39 credit, at the end of January the account would have earned 3.10 from this subscription.
The general ledger entries would be as shown below.
A carrier collect subscriber begins a 7-day subscription on June 1, 2007. Being carrier collect, it is up to the individual carrier to set the rates and collection periods (the newspaper may have rating guidelines or have other policies, but they are not reflected in Circulation).
This account has a monthly period rate that varies by day. Sundays are 4.00 per month for this subscription. Wednesdays are 1.75 per month, and all other days are 1.50 per month. So, for this month, the account would be charged 4.00 + 1.50 + 1.50 + 1.75 + 1.50 + 1.50 + 1.50 = 13.25 for this subscription.
The general ledger entries would be as shown below.
Subscribers receive rates based on subscription period (for example, 18.00 for 3 months). To do subscriber accounting, however, Circulation must boil down these period rates into a copy rate. This is a simple rate per day for the subscription. For example, with a flat 3-month rate at 18.00, assuming there are 90 days in the period, the copy rate would be 18/90, or 0.20 for each paper. The copy rate is used in calculating and in other places.
You may, depending on rating setup, have your copy rates vary by day (for example, charge more for your larger Sunday paper than for other days of the week). This may be important in cases where the subscription is extended for things such as missed delivery. With a single copy rate, an extra day is simply added to the subscription period. So, if a subscriber misses the Sunday paper, it is very likely she will end up receiving an extra Wednesday paper or Monday paper. But if the copy rates vary by day, the subscriber can be credited appropriately for missed day. Perhaps Sunday costs 0.40 and the other days cost 0.20—so our subscriber will receive two extra papers during the week or an extra Sunday, depending on what days the subscription is extended.
The following examples illustrate how Circulation calculates the copy rate for a varying weekly rate and a varying monthly rate.
Imagine a rate “1week” was set up to vary by day, as follows:
Circulation would calculate a total of 1.63 for this weekly rate. If a subscriber with this rate made a payment of 20.00, he would be able to buy 12 weeks, and have 0.44 left over. Thus, an extra Sunday or two extra non-Sunday days could be added to the subscription.
Now imagine another rate, “3month”, is set up to vary by day. With monthly, quarterly, and yearly rates that vary by day, the days are weighted by percentages, rather than amounts. Let’s say the total period rate is 18.00, and the percentages are entered as:
Circulation would calculate the copy rate for each day using the following formula:
where “average aggregate days” is the average number of times each day of the week appears in the period, weighted by percentage. We get this figure by multiplying the number of times each day appears by the percentage for that day. So, if our example 3-month rate started October 7, 2005, the average aggregate days would be as follows:
So our copy rates would be:
(percentage * period rate) / average aggregate days
Sunday
13 * .37 = 4.81
Monday
13 * .10 = 1.3
Tuesday
13 * .10 = 1.3
Wednesday
13 * .10 = 1.3
Thursday
14 * .10 = 1.4
Friday
13 * .13 = 1.69
Saturday
13 * .10 = 1.3
TOTAL
= 13.1
Sunday
(.37 * 18) / 13.1 = .508396
Monday
(.10 * 18) / 13.1 = .137404
Tuesday
(.10 * 18) / 13.1 = .137404
Wednesday
(.10 * 18) / 13.1 = .137404
Thursday
(.10 * 18) / 13.1 = .137404
Friday
(.13 * 18) / 13.1 = .178626
Saturday
(.10 * 18) / 13.1 = .137404
Sunday
0.40
Monday
0.20
Tuesday
0.20
Wednesday
0.23
Thursday
0.20
Friday
0.20
Saturday
0.20
Sunday
37%
Monday
10%
Tuesday
10%
Wednesday
10%
Thursday
10%
Friday
13%
Saturday
10%
This section guides the user through the menu options that are available under the Account Billing menu.
Note: The "CreditCardSurcharge" feature is a licensed add-on. Please contact Naviga Global Support to license this feature.
Merchants sometimes add a small surcharge percentage to payments made by credit card, to help recoup the processing fees from the credit card company. Circulation can assess a surcharge percentage on subscriber credit card payments, based on the product and credit card type.
The surcharge is based on the total payment amount, including the term cost, tip, tax and cash adjustments. When a surcharge applies to a payment, a cash subscriber payment adjustment is created for the surcharge amount.
In order to add a surcharges to credit card payments, you must:
Activate “CreditCardSurcharge” add-on in Add On Activation.
You can allow certain users permissions to waive the credit card surcharge using the “CCSurchargeOvrd” security item in Transaction Security setup.
Define a subscriber payment adjustment code for credit card surcharges. This code should be set up as a cash adjustment that does not update the expire date or the wallet. Once defined, the new payment adjustment code should not be used for any other purposes outside of credit card surcharges.
Select the new payment adjustment code for the Business Rule— What is the subscriber adjust code used for storing subscriber credit card surcharges? (Subscriber Payments section).
You may also wish to define a separate credit GL account for storing surcharge revenue (the debit GL account will be Cash).
In Credit Card Account setup (see Credit Card Account in the Setup Manual), set the actual surcharge percentage for the applicable products and credit card types. You can also specified whether the surcharge amount is taxable.
Credit card surcharges can be applied to payments entered in Customer Service, the Customer Service API, or the Circulation API, as well as credit card auto renews. Payments added in Batch Payments in the Accounting module or in iServices Subscriber do not currently qualify for surcharges.
When a credit card payment is entered in Customer Service for a publication and credit card type flagged for surcharge in Credit Card Account setup, a warning message displays when accepting the payment, listing the surcharge amount. The user can click Yes to continue, or No to cancel the payment (if the user has credit card override permissions in Transaction Security and clicks No, the payment will still be entered, but without the surcharge).
If you accept the surcharge, the surcharge amount will be added to the total payment amount. The surcharge information can be displayed by viewing the payment transaction and clicking on the Adj button to the right of the Adjustment field.
Note: When the subscriber is on a combo subscription, the credit card surcharge adjustment will be added to the primary subscription.
If a subscriber is on credit card auto pay for a publication and credit card type that has a surcharge defined, the surcharge amount will automatically be calculated and added to the payment during Auto Payments processing. This includes subscribers who started or changed to credit card auto renew in iServices Subscriber.
If surcharges apply to credit card payments brought in via Lockbox Processing or the Subscriber Activity Import, you can import the surcharge as a payment adjustment (the surcharge must be calculated outside of Circulation). Place the total surcharge value (surcharge amount plus surcharge tax, if applicable) in the Adjustment Amount field. The file map used must be set up to assign the subscriber payment adjustment code used for surcharges to the Adjustment Amount field.
Credit card surcharges will display on the Subscriber Payment Journal as subscriber payment adjustments. The journal also has an adjustment recap. If you import credit card payment authorizations/declines and apply surcharges, the Tran Amount should include the surcharge amount.
Some examples below illustrate how surcharge amounts are calculated and added to payments.
Assume:
Publication Taxable: Yes
Surcharge: 3%
Surcharge Taxable: No
Payment amount = 48.00
Tip amount = 2.00
Tax = 6%
In this example:
The payment amount entered for the credit card would be 50.00 (48.00 term amount plus a 2.00 tip)
The surcharge would apply to the entire initial payment amount of 50.00. 3% of 50.00 = 1.50
The final payment amount would be 51.50 (a 50.00 payment with a 1.50 surcharge)
The tax would be 6% of 48.00 = 2.88
The total payment amount applied towards the subscription would be 48.00 - 2.88 = 45.22
Assume the same scenario as Example 1, but with Surcharge Taxable = Yes. In this case:
The payment amount entered for the credit card would be 50.00
The surcharge would apply to the entire initial payment amount of 50.00. 3% of 50.00 = 1.50
The surcharge would be taxed. 6% of 1.50 is .09
The total surcharge would then be 1.50 + .09 = 1.59
The final payment amount would be 51.59 (a 50.00 payment with a 1.59 surcharge)
The tax on the subscription would be the same as before: 6% of 48.00 = 2.88
The total payment amount applied towards the subscription would still be 48.00 - 2.88= 45.22
If you wish to refund the surcharge amount during a permanent stop, you will need to override the default refund amount to add back in the surcharge value. Note that the Business Rule— What is the maximum variance from the calculated amount that an operator may enter for the refund paid? will govern the maximum amount you may manually override the refund.
When a credit card surcharge is assessed for a payment, the credit GL account specified in Subscriber Payment Adjustment setup will be credited for the surcharge amount. The GL account specified for the publication and credit card type in Credit Card Account setup will be debited for the amount (along with the term payment and tax amount).
The credit/debit entries for a typical payment with a surcharge are shown below. Assume a payment for $100 term, county tax is 10%, surcharge on credit card payment is 1.5%, and surcharge is not taxed.
Options in the Accounting module enable you to enter account payments, apply miscellaneous charges and credits, and produce account bills. This module also contains subscriber accounting options, which you can use to enter subscriber payments and print renewal notices.
Topics covered in this section are as listed below:
Account (carrier/dealer) and subscriber accounting lifecycles are described below.
In order to print account invoices and enter account payments, you must:
Enter any papers returned or draw adjustments made for the account. Also, enter any miscellaneous charges (for rubber bands, for instance) or credits for the account. This is an ongoing process; the account bill for a period will reflect all of the returns, adjustments and charges dated in that period.
Before you start a billing run, make sure there are no suspended account payment batches by printing the Batch Audit Journal. Also, check the Publishing Run Status to make sure the last day’s run is completed, and print the Summary Age Analysis.
Calculate any interest and bond charges.
Select the bill sources or individual carriers you want to bill (for example, home delivery carriers).
Process the billing. Draw charges and delivery credits are automatically calculated by Circulation and added to the returns, draw adjustments, miscellaneous charges, etc. Recurring charges are also calculated automatically.
Print the Billing Journal to check the billing. If corrections need to be made, undo and process the billing again.
Print invoices and, if desired, deposit slips for the accounts.
When all errors have been corrected for the billing run, and the invoices have been run, close the billing.
After the bills are sent out, payments will be received from the accounts either by cash, check, credit card (payment entry), or direct deposit into a bank account (lockbox processing). These payments must be entered into Circulation and then transferred to the general ledger.
If some payments are not applied to an invoice during payment entry, you must apply the unapplied amount to an invoice or balance later (if Business Rules allow).
Accounts with office pay credits in excess of their draw charges must be paid. You can do this by direct deposit, interfacing with accounts payable software, or printing out the Credit Journal and manually entering the credits in accounts payable.
In order to print subscriber renewals and enter subscriber payments, you must:
Print renewals for subscribers. You can also e-mail renewals, or export renewal information to a file so that the renewal notices can be generated outside of Circulation.
Enter payments when they arrive. Process auto payments for auto renew subscribers, and do lockbox processing for subscribers who make payments directly into a bank account.
Print the Batch Audit Journal to make sure there are no suspended batches, and the Payment Journal to check for errors in the payments.
Process the payments.
Some customers may be entitled to refunds. If so, enter them in batch refunds and print the Refund Journal. You can do refunds independently of subscriber payments.
Some subscribers who have a credit to their account may stop delivery and not claim their refund; other subscribers may have delivery stopped while in grace. Both refunds and grace can to be written off for these subscribers, if desired.
Use the Billing Journal to check over the amounts that will be charged (or credited) to accounts in this billing run. For each account in the billing run, the journal will list the charges and credits that were processed (including draw charges), and office pay subscribers on the route. Bill processing control totals are included at the end of the report.
Business Rules determine the default sort order, truck sequence, and truck departure order for the Billing Journal. Business Rules also determine whether payment notes print, whether accounts with zero balances or zero billing activity should print, and the placement of blank lines. Finally, Business Rules determine the sort sequence that should be used for printing office pay subscribers.
The format for this journal is defined in Business Rules and by selecting Setup | Accounting | Account Billing | Bill Format
. See Bill Format in the Setup Manual for details.
Select Billing Journal from the Account Billing menu to display the Account Billing Journal window. All of the active billing runs that are ready to produce the Billing Journal are displayed.
Select the billing run(s) for which the journal should print (click the appropriate checkbox(es) in the Process column).
Enter the sort parameters for the Billing Journal. If one of the billing runs you are printing the journal for is a selected accounts billing, the journal will automatically sort by account.
SORT ORDER
predefined
Indicate whether the Billing Journal should be sorted by account, name, route, district, zone, region, area, or truck. You can also sort by publication and then district, zone, region or area.
TRUCK SEQUENCE
setup
If the sort order is by truck, enter the truck sequence in which you want the journal to print. The truck sequence is the pattern that describes which routes are dropped from which trucks on a given day. Examples are “daily” and “Sunday”.
TRUCK DEPARTURE
setup
Enter the truck departure sequence in which you want the journal to print when the sort order is “Truck”. The departure sequence is the departure pattern trucks follow on a given day, for example “City” or “Monday”.
Click Continue to produce the journal. It is recommended that you save your Billing Journal as a spool file. Once close billing, the spool file is the only way to reprint or view this particular report in the billing run.
This section explains how account and subscriber accounting impacts the general ledger. For more information about the GL, see Introduction in the Accounting section of the Setup Manual.
Note:
Circulation can export GL entries to the cmgltran.d
file in /dti/exchange/cm
. You can pull this file into your general ledger application). Or, you can produce the GL Interface Journal, which details the Circulation GL entries for the month.
Because there are some crucial differences between the two, we present GL accounting for carrier collect and office pay billing methods in separate sections. For simplicity, assume that one of your carriers has only carrier collect subscribers, and another has only office pay.
With both office pay and carrier collect subscribers, it is important to realize that subscriber billing and payment functions independently from account billing and payment. The newspaper might have a promotional discount for its subscribers, but the carriers will receive the same amount for delivering the paper (unless the account rates are specifically tied to the subscriber rate code).
With carrier collect subscribers, the carrier delivers the papers, collects the money, and then is billed by the newspaper for the wholesale value of the papers delivered. The carrier’s revenue is what is collected (retail value) minus what is paid to the paper (wholesale value).
In regard to the general ledger, two major actions take place:
Draw Charge. The bill the carrier receives for the papers contains draw charges. This is what the newspaper charges the carriers for papers they receive, and so it is credited to Account Revenue. Since the money is due but not yet paid, it is debited from Accounts Receivable. Other charges and credits, such as return credits and miscellaneous charges (rubber bands, etc.), also show up on the carrier’s bill. They debit or credit their own GL accounts.
Account Payment. When the carrier sends in the payment, Accounts Receivable is credited, thus balancing it out. The Cash in Bank Account or the Credit Card Account (depending on method of payment) are debited. The net effect of the draw charge and account payment is that money has moved from Cash in Bank or Credit Card to Account Revenue.
With office pay subscribers, the GL accounts are a little more complex. The carrier delivers the papers, but the subscriber pays directly to the newspaper. Since this payment is usually for papers that have not yet been delivered (18 weeks into the future, for example), it is unearned revenue. As the papers are delivered, the revenue becomes earned. Earned revenue is typically calculated at the end of each fiscal period in Circulation (see Unearned Revenue).
While revenue is being earned, the carriers are earning credit. This credit, called office pay credit, is the difference between the (retail) rate the carriers are given for delivering the paper and the draw charge (wholesale value) of the paper. It is equivalent to the money the carrier collect carrier receives directly from the subscriber.
In regard to the GL account, four major actions take place with Office Pay subscribers:
Subscriber Payment. Since the subscriber payment is for future goods and services, the Unearned Revenue Account is credited (if part of it is grace owed, however, that part is credited to the Subscription AR Account). Since the money is on its way to being revenue, the Cash in Bank Account or Credit Card Account (depending on the method of payment) are debited for the same amount.
Earned Revenue. As the papers are delivered, the Unearned Revenue Account is debited, and the Subscriber Revenue account is credited. Subscriber Revenue reflects money earned from subscribers. Some of that money will, of course, go to the carrier.
Draw Charge. The draw charge for the office pay carrier is the same as for the carrier collect carrier, above. The Revenue Account is credited, and the Accounts Receivable Account is debited.
Office Pay Credit. To pay the carrier, the Delivery Expense money is debited, and Accounts Receivable credited. This might make it look like the carrier isn’t getting any money at all, but don’t worry: the money debited from Accounts Receivable is less than the money credited to it. The difference is what the carrier earns, his or her office pay credit. This amount will eventually go to Accounts Payable (where a check will be cut) or be deposited directly into a carrier bank account.
The net effect of these debits and credits is that money is being taken out of the Cash in Bank or Credit Card Accounts and going to Subscriber Revenue. Money (for office pay credits) is also being taken out of Delivery Expense and going to Account Revenue and Accounts Payable. At most newspapers, Subscriber Revenue and Delivery Expense will roughly cancel each other out, and so the true net effect will be that money is going from Cash in Bank or Credit Card to Account Revenue (newspaper share) or Accounts Payable (carrier share).
If the carrier has both office pay and carrier collect subscribers, the total draw charge for the carrier collect and office pay subscribers is subtracted from the office pay credit. If the credit exceeds the charges, a carrier will receive a check from the newspaper; if not, the carrier will have to make a payment.
Use this option to select companies or bill sources (or individual accounts) for a billing run. There are two types of billing runs:
A standard billing run to bill all accounts for a company/bill source combination and billing date. This cannot be started until final transaction processing is completed for the last date to be billed and all batches of miscellaneous charges/credits, draw adjustments, returns, and payments have been entered and accepted (no batches suspended). All accounts in the bill source will be billed.
Selected accounts billing (also known as “dummy” billing). You can select individual accounts to bill by entering “n” in All Accounts. Circulation will not check to make sure the billing date is valid, and only check for suspended batches that apply to the selected accounts. After you have printed invoices, you should Undo the selected accounts billing.
This method is useful when carriers quit in the middle of the month, and you want to send a bill to them. Circulation calculates the charges (allowing you to print a bill) and then “undoes” them. When the real billing run is processed, the charges will appear again. By this time, the carrier may have made a payment to offset the charges.
If you are doing a selected accounts run, the windows will be slightly different when you process the billing journal, invoices, deposit slips, and other Account menu items.
You may have more than one standard billing run open at the same time, as long as they do not select the same accounts.
Note:
You may or may not be able to start a billing run if there are suspended payment, miscellaneous charge, return or draw adjustment batches, as governed by Business Rules.
Choose Selection from the Account Billing menu to display the Account Billing Selection window.
Click Add and complete the following fields.
COMPANY
setup
Enter the company ID for the group of accounts being billed.
ALL ACCTS
yes/no
All Accounts is always set to “y” in the graphical version of this menu option—all accounts will be selected for the billing run. In the character version of this menu option, you can enter “n” if you are billing selected accounts, testing new rates, etc.
BILL SOURCE
setup
Enter the bill source for the group of accounts being billed. This field will default to “*” and skipped when billing selected accounts.
BILL DATE
date
Enter the billing date for the group of accounts being billed. This date must be specified as a billing date in the statement calendar (see Statement Calendar in the Setup Manual).
NEXT BILL DATE
date
The next billing date, based on the billing calendar for the bill source entered, is displayed. This field will be left blank for selected accounts billing.
BILL PRD (period)
setup
ADV PRD (advanced bill period)
setup
Enter the advance billing period(s) if some of these carriers are set up to be billed in advance.
DESCRIPTION
open (30)
Enter a description of the group of accounts being billed.
STATUS
display
Click Accept and then Continue to select the accounts for billing. In the example shown, a billing run has just been selected for the bill source “Dealer”. Notice that there are two other billing runs active—the billing run for bill source “Rack” has just been processed, and the Billing Journal has been produced for a selected accounts billing run for an account (Meadows).
If you are billing selected accounts (i.e., you entered “no” in All Accts), another window will appear. Click Add and enter the accounts that should be included in this selected accounts run.
Recurring charges and credits are set up and assigned a billing period in which they should be included on the account’s bill. For example, insurance might be added every third week, bond premiums every week, and mileage the first week. Charges are assigned to bill periods for each account in Distribution | Account Setup | Account | Specifics | Recurring Charges
. An example of billing periods might be:
If you do weekly billing and are selecting for the third week of the month, you would enter an asterisk (*) in Bill Period and select “3” and “Every”, so that insurance and bond charges will appear on the account bills. You would not select “1” because mileage credits should not be included in this billing run.
To include recurring charges for accounts being billed in advance, you would enter the advance billing periods to include. For example, if you are selecting bills for the third week of the month, the advance billing period would be the fourth week. Only those charges set up to allow advance billing are added to the account’s bill.
This option allows you to export invoice information for single copy and home delivery accounts for formatting outside of Circulation.
Notes:
This option is controlled by the Account Export section of Business Rules.
Formats for Invoice Export are created using the Bill Format option in Setup (see in the Setup Manual).
For a list of data elements that can be used for Invoice Export, see in the User Manual.
Select Invoice Export from the Account Billing menu to display the Invoice Export window.
Select one or more billing runs (click the appropriate checkbox(es) in the Process column).
Enter a sort order, truck sequence, and truck departure.
Click Continue to export the invoice information.
Certain states that tax newspaper subscriptions allow tax on the delivery cost to be excluded. In Circulation, the delivery cost is equivalent to the credit paid to the account for delivery. For example, if a subscription costs 20.00, the tax is 2%, and the account is credited 5.00 to deliver the subscription, we would wind up with:
This option, Trans Exclusion, calculates the delivery cost exclusion. A report is created as part of the process. Another option, Tax Exclusion, can be run to deduct taxes for subscriptions in which the delivery cost exceeds the cost to the subscriber from the transportation exclusion (see for more information).
Note:
The Transportation Exclusion Report is part of the Taxing add-on option. Contact the Naviga Support Center if you wish to purchase the Taxing add-on.
The tax exclusion amount will be incorrect if accounts are charged and credited for office pay subscriptions. To produce accurate exclusion figures, you must set up account rates so that accounts are only credited (not charged) for office pay. Also note that in order to find the subscriber tax authority, an account tax authority needs to be set up and attached to the accounts; the tax for the tax authority should be a charge of zero (unless accounts are actually taxed).
A subsidy amount can be added to the transportation cost, based on the Business Rule— “What is the daily subsidy amount which should be added to the remit on payment trans cost calculation?” (Transportation Cost section) or, if defined at the route level, the Route Subsidy field in the Route Setup Utility.
A Business Rule— Should transportation costs be excluded? (Account Finance section), determines whether Transportation Exclusion will be run. If so, invoices, deposit slips, or the Billing Journal must be run before Transportation Exclusion can be run. Once Transportation Exclusion has been processed, invoices, billing journals, and deposit slips can no longer be generated for the billing run.
To calculate the delivery cost exclusion, the report will total the route’s draw credits, and multiply that total by the subscription tax percentages for the tax authority. The tax percentages will be based on the subscription tax authorities. To find the tax authorities, the report will use the carrier’s publication address or the carrier’s address (depending on how the Business Rule— Which address should be used for determining an account’s taxability?, is set). If it is set to “publication”, the publication address will be used; if it is set to “account” or “route”, the carrier address will be used.
Select Trans Exclusion from the Account Billing menu to display the Account Transportation Exclusion window.
Select the account billing run for which to calculate the transportation cost.
In some cases, carriers are given deposit slips so that they can deposit payments directly into the newspaper bank account. This option creates deposit slips for all carriers with a debit balance.
Business Rules determine the following for deposit slips: the length (in lines), the line on which printing should start, and the starting position (characters across) for printing.
Select Deposit Slips from the Account Billing menu to display the Account Deposit Slips window. All of the active billing runs that are ready to produce deposit slips are displayed.
Select the billing run(s) for which deposit slips should be printed (click the appropriate checkbox(es) in the Process column).
Click Continue to produce the deposit slips. See for information about how to load forms and configure your printer for this task.
Once a billing run is processed, select this option to print the actual invoices that will be sent to the accounts.
The format for this invoice is defined by selecting Setup | Accounting | Account Billing | Bill Format
—see Bill Format in the Setup Manual for details.
Business Rules determine the default sort order, truck sequence, and truck departure order for invoices. Business Rules also determine whether payment notes and remit addresses are printed, whether accounts with zero balances or zero billing activity are printed and have invoice numbers, whether scan lines are printed, and the placement of blank lines. Business Rules determine whether office pay subscribers are printed on a separate page, and the sort sequence that should be used for printing office pay subscribers.
Finally, Business Rule—What should display for an override label in account billing for Invoice Date and Bill Date? determine the label to be displayed on the invoices.
Note:
Invoices can also be printed on carrier/dealer bundle tops. See for details.
Select Invoices from the Account Billing menu to display the Account Invoices window. All of the active billing runs that are ready to produce invoices are displayed.
Select the billing run(s) to include (click the appropriate checkbox(es) in the Process column).
Enter the sort parameters for the invoices. If one of the billing runs you are printing invoices for is a selected accounts billing, the invoices will sort by account.
Click Continue to produce the invoices.
Account Setup determines whether accounts are billed in advance of or after delivery. If before, the bill will contain an estimate of next period’s billing (which the carrier/dealer pays), the actual charges and credits for this period, and a reversal (adjustment) for the bill that was paid last period. For example, if a monthly advance-bill account receives a bill at the end of June, the bill will contain an estimate of charges and credits for July, the actual figures for June, and a reversal for the June estimate that was paid in May.
If invoices are sent to carrier/dealers via bundle tops (see ), not all of them may receive a bundle top on the date that invoices are included. For example, a carrier may no longer be active, or may not deliver on that day of the week. These invoices, then, will need to be printed and sent separately using this option. Missed Invoices must be run after bundle tops, and before the next billing run is started.
Select Missed Invoices from the Account Billing menu to display the Missed Account Invoices screen.
Select Add and choose the products and publishing dates for which invoices should be printed.
Then, press F1 and select Continue. The missed invoices will be formatted like standard invoices, but only accounts who did not receive a bundle top will have an invoice.
Note: Once they are processed, missed invoices can be reprinted by selecting UNDO FINAL TRAN PROC
, running Transaction Processing again for the final time, and generating bundle tops again.
When all account billing processing, invoicing, and reporting has been completed for the billing run being processed, select this option to close the billing run. The general ledger is then updated and prepared for entry of information for the next account billing period.
All history pertaining to the billing is updated, and changes to this billing run are only possible if you undo the close (see ). To produce a report of the general ledger entries generated by this option, print the General Ledger Interface Journal for the appropriate bill batch or bill date (after closing account billing). See .
If you are running a selected accounts billing (see ), Business Rules determine whether you can Close it. Typically, you would Undo the selected accounts billing rather than selecting Close.
Select Close from the Account Billing menu to display the Close Account Billing window.
All of the active billing runs that are ready for closing are displayed. Select the billing run or runs to close.
Click Continue to execute the billing close. The Close Account Billing report will be produced, displaying control totals from the billing run.
Bundle tops are the primary method by which newspapers communicate delivery changes to carriers. To increase efficiency and save in printing and mailing costs, account invoices can be printed on the bundle tops for a certain publication and date. If this method is used, account invoices will not need to be printed and mailed as a separate process.
Note: Not all carrier/dealers may receive a bundle top. The option will print invoices for these accounts.
In order for invoices to print on bundle tops, the billing run must be flagged for bundle tops for a certain publication and date. This is done here, in Invoices On Bundle. A Business Rule— Are account invoices printed on the bundle tops? (Account Invoice section), determines which publications can be entered. The publishing date must be an open or future date (i.e., final transaction processing not completed).
Select Invoices On Bundle from the Account Billing menu to display the Invoices on Bundle screen.
Select Modify, highlight the billing run and press Enter. The run must at least be processed (it may be closed). Selected accounts (dummy) billing runs can be flagged if they have been processed.
On the next screen that is displayed, enter the publication and publishing date on which the invoices are to print on the bundle tops. More than one entry may be necessary for a billing run—for example, if the accounts in the billing run deliver more than one publication.
After all of the publications and dates have been defined, press F4 and select Exit. You can then flag other billing runs for printing on bundles, or press F4 and select Exit again to exit to the main menu.
When bundle tops are produced during the publishing run on the date entered, invoices will print after the bundle top messages (and after the route list, if a route list is also printed). The invoice format is based on your bill format (i.e., they will be formatted like your standard invoices). If an account delivers multiple routes, the invoice will appear with the billing route’s bundle top.
A key option on the Account Billing menu is Processing. When you select this option, Circulation gathers and then processes the information required to create account bills, and creates control totals for this billing run.
Business Rules determine whether unapplied payments should be automatically applied (to the new charges) during account bill processing.
Note: Never enter account payments when a billing run is in process.
You can process the account bills only for a single bill source and a single billing date. You can also run a selected-accounts billing of a selected group of accounts at any time.
Select Processing from the Account Billing menu to display the Account Billing Processing window. All of the active billing runs that are ready for processing will be displayed.
Select the billing runs that should be processed (click the appropriate checkbox in the Process column).
Click Continue to process the billing run.
After processing is completed, a processing report appears. This report lists error messages and control totals.
For every account in the billing run, billing processing determines the draw and returns for each route for which the account is to be billed, and rates these draws and returns using account rating to determine the draw charges and credits the account receives. Piece and weight bonuses are also calculated based on the draw. If you have Business Rules set to apply unapplied payments, any unapplied payments will be applied to the new charges.
Recurring charges and credits that are in the specified bill periods are also selected, along with levies (if any are defined). This information, combined with the miscellaneous charges and credits entered since the last billing run, are used in printing the Billing Journal, invoices, and general ledger entries.
If an account is advance bill (defined in Account Setup), bill processing will estimate the charges and credits for the next period, and reverse out charges and credits for the last period. For example, say you are running billing on the last day of June, and an advance bill account was billed 50.00 for June (in May). Circulation calculates the actual charges and credits for that account in June and finds that they total to 40.00. A 10.00 credit would then show up on the account’s invoice, along with the estimated charges for July.
At the end of account bill processing, Circulation has combined control totals of all of the transactions processed in the billing. These control totals print on the Account Billing Processing Report, and also at the end of invoices, the Billing Journal, and the Close Account Billing Report. See the following table.
* The Invoice Count, Statement Count and Total Count control totals appear on Account Invoices, the Account Billing Journal, the and the Close Account Billing report.
During billing processing, all account charges and credits are calculated and general ledger account numbers assigned. If any errors are encountered, messages are displayed so you can correct them: Undo the current billing run, make the necessary corrections, and begin the billing process again by selecting Selection.
The next step in processing account bills is to print the Billing Journal so you can verify the billing information (i.e., all accounts look correct) before printing invoices.
Enter the billing period to include in this billing. The bill period determines what charges are included in the billing. See . Note: In the character version of this menu option, bill periods can be multi-selected. In the graphical version, they cannot.
This field displays the status of all active billing runs. See for an explanation of the various statuses.
Click Continue to run the report. The report will also create GL transactions (see for details).
Invoice Count *
Count of all invoices produced. Any bill with current activity is considered an invoice.
Statement Count *
Count of all statements produced. Any bill with no current period activity is considered a statement.
Total Count *
Total of Invoice Count plus Statement Count.
Balance Forward
Total of Balance Forward (previous balance) for all accounts.
Current
Total of outstanding current aging period balances from all accounts. This contains all of the charges and credits that have just been processed.
Period 1
Total of outstanding age period one balances from all accounts (see Age Period in the Setup Manual for more information about aging periods).
Period 2
Total of outstanding age period two balances from all accounts.
Period 3
Total of outstanding age period three balances from all accounts.
Period 4
Total of outstanding balances beyond age period three from all accounts.
Balance
Total of outstanding balances for all accounts.
Payments
Total of all payments picked up in this billing run. This includes payments (both applied and unapplied) and cash adjustments. This also includes any discount amount related to any other payment type.
Debit Memos
Total of all checks issued to carriers through Accounting - Interface to AP and picked up in this billing run.
Draw Charges
Total of all account draw charges, less any account draw delivery credits (e.g., Office Pay or Complimentary delivery credits) billed for dates prior to the billing date.
Return Credits
Total of all return credits less any returns charges (reversals of delivery credits).
Misc Charges
Net total of all miscellaneous charges and credits picked up by this billing run.
Other Charges/Credits
Total of various types of charges and credits picked up or created by this billing run which do not fall into any of the specific charges/credits categories listed here. This includes net charges for non-return draw adjustments, automatically generated adjustments for backdated carrier collect-office pay conversions, carrier tips, TM delivery credits, taxes, finance charges, minimum daily service charges, weight and piece bonus credits, and interest on recurring charge balances.
Substitute Charges/Credits
Net total of draw charges/credits for substitute carriers during this billing run.
Recurring Charges/Credits
Net total of recurring charges and credits created during this billing run.
Levy Charges
Net total of account levies charged during this billing run.
Advance Draw Charges
Total of all advance billed draw charges less any advance billed draw delivery credits (e.g., office pay delivery credits). These amounts are based on estimated draw for the next billing period.
Advance Misc Charges
Net total of all advance billed recurring charges and credit created during this billing run.
Reverse Charges
Total of all advance billed draw charges and miscellaneous charges billed during the last billing period that are being reversed out on this period’s bills.
Total Charges
Net total of draw charges, return credits, misc charges, other charges/credits, recurring charges/credits, advance draw charges, and reverse charges.
This section guides the user through the menu options that are available under the Account Payments menu.
SORT ORDER
predefined
Indicate whether the invoices should be sorted by account, account group, name, route, district, zone, region, area, truck, distribution code or depot (see Distribution Code and Depot in the Setup Manual for more information about distribution codes and depots, respectively).
You can also sort by publication and then district, zone, region or area.
TRUCK SEQUENCE, TRUCK DEPARTURE
setup
Enter the truck sequence and truck departure sequence in which the invoices should be printed when the sort order is “Truck”.
If the sort order is not “Truck”, these sequences enable the system to print the correct truck on the invoice.
This option allows you to quickly determine the current stage in the billing run for each of your company/bill source combinations. Selected accounts billing runs (runs with only a few accounts individually selected) will also be displayed. The following table lists the possible statuses, and indicates whether they are a required step of the account billing run.
To view billing run statuses, select Billing Run Status from the Account Billing menu to display the Billing Run Status window. Click Done to exit the window.
You may have a situation where you want to reopen a closed billing run—for example, you may want to print another set of invoices, or a selected accounts billing run may have been closed accidentally. Use Undo Close to reopen:
The last billing run for a company/bill source combination, provided that a billing run is not currently active
A selected accounts billing run (billing run for selected individual accounts), in the case where Business Rules allow you to close selected accounts billings
Undo Close will simply reopen the billing run; it will not undo billing processing.
Select Undo Close from the Account Billing menu to display the Undo Account Billing Close window. All of the closed billing runs that may be reopened are displayed.
Select the account billing run for which you want to undo the close (by clicking the appropriate checkbox).
Click Continue. You will be prompted about continuing with the undo close.
Click Yes to reopen the billing run. A report will list any errors that occurred during the undo close.
A drop credit is a flat fee paid to an account for each home address delivered, without regard to the number of pieces that are delivered to the address. Drop credits are not used with single-copy routes.
Drop rates are associated with a product. Normally, the product with the highest drop rate determines the drop credit paid to the account, although product priorities can be established to override this calculation.
Daily drop rates are defined in Drop Rates setup (see Drop Rates in the Setup manual), and you indicate that an account is paid on a per-drop basis in Account setup. Drop credit priorities can be defined in the Deliverable record.
Select Create Drop Credits from the Account Billing menu to display the Create Drop Credits window.
Click Add and complete the following fields.
COMPANY
setup
Enter the company for which to create drop credits.
BILL SOURCE
setup
Enter the billing source for which to create drop credits.
BILL DATE
date
Enter the bill date for which drop credits will be created.
CHARGE BATCH
open
Enter the name of the charge batch that will be created.
Click OK and then Continue to create the drop credits. A processing report will be displayed.
Interest can be calculated for certain account recurring charges, usually bonds. For example, you may require accounts to pay a monthly bond amount, but give them interest on the amount. To do this, you would:
Set up a recurring charge code (such as “bond”) to charge a certain amount on account invoices in each specified billing period. If you want a single, one-time charge (say 50.00) you could still have it be a recurring charge, but make the maximum charge 50.00. For more information about specifying charge amounts, see Account in the Setup Manual.
Set up a miscellaneous charge code (such as “bondint”) that does not update Accounts Receivable, but updates the balance of the charge code in step 1 (“bond”). For more information about setting up charge and credit codes, see Charge/Credit Code in the Setup Manual.
Calculate the interest each month (or whatever your interest period is) using this option. You specify the interest percentage here, and the amount is added to the associated recurring charge’s account during billing processing.
When the carrier leaves the route, you can find the total amount that was charged for bond (the recurring charge plus interest) by running the Charge/Credit Report. Then you can enter a miscellaneous credit for the account. The miscellaneous credit code (for example, “bondout”) should update the bond charge (“bond”), but also apply to AR.
Business Rules determine whether the interest calculation should include previous unbilled interest, the current recurring charge amount, and whether unbilled miscellaneous charges and credits that update this charge account.
Note:
Interest calculations may increase a account’s “maximum amount” (see Account in the Setup Manual) for a recurring charge balance. For example, if the account’s “maximum amount” is 150.00, interest calculations might cause the total to be 152.00.
If you do give interest on bonds (or any other charges), calculating interest should be part of your account billing run.
To perform the interest calculation:
Select Interest Calculation from the Account Billing menu to display the Bond Interest Calculation window.
Click Add and complete the following fields.
COMPANY
setup
Enter the company for which interest should be calculated.
BILL SOURCE
setup
Enter the bill source for which interest should be calculated. A bill source is a group of carriers which you want to bill together (examples are Carrier and Dealer).
CHARGE BATCH
open (10)
Enter a batch name for the interest charges.
CHARGE DATE
date
Enter the date when the interest charges should be created.
CHARGE CODE
setup
Enter the charge code(s) for which the interest should be calculated. The only valid charge codes to use are the ones that update the balance of another charge code. Press F2 for a lookup of valid choices.
PERCENTAGE
decimal (11)
Enter the interest percentage; for example, enter 3 for 3%.
BILL PERIOD
setup
Enter the bill period of the recurring charges that should be included in this interest calculation, such as “every”, “weekly” or “monthly”. Interest will only be calculated on charges in this bill period.
Click OK and then Continue to perform the interest calculation.
When the calculation is complete, the Bond Interest Calculation Report is displayed, listing the accounts where interest was applied.
It may be necessary to undo billing processing due to numerous errors that must be corrected (you must also undo the billing run in the case of a selected accounts billing). Any information created by the billing processing will be removed. Select this option any time before selecting Close.
Select Undo Processing from the Account Billing menu to display the Account Billing Undo window. All of the open billing runs are displayed.
Select the billing runs that should be undone (by selecting the appropriate checkbox).
Click Continue. At this point, you will be prompted about whether the billing run should be undone.
Click Yes to continue. All charges created by the billing run will be reversed, and the undo process will produce the Account Billing Undo report, which lists the control totals for the canceled billing.
Use this option to reverse the drop credits created generated by Create Drop Credits. This may be necessary if an error was encountered—the process can be undone, the error corrected, and the process rerun.
Select Undo Drop Credits from the Account Billing menu to display the Undo Drop Credits window.
Click Add and complete the following fields.
COMPANY
setup
Enter the company for which to undo drop credits.
BILL SOURCE
setup
Enter the billing source for which to undo drop credits.
CHARGE BATCH
open
Enter the name of the charge batch that will be undone.
BATCH DATE
date
Enter the date of the batch of drop credits that will be undone.
Click OK and then Yes to confirm that you want to undo the drop credits.
Click Continue to finish the process.
Use this option to export all of the information necessary to perform corporate billing for selected accounts.
If individual single copy chain stores maintain their own accounts receivable, but the corporate office prefers to make payments on behalf of the stores, you can use this option to prepare a summarized statement for corporate billing that includes payment information, aging, charges details, and invoice details for those stores. To accomplish this, you must assign each store to an account group, and then run this option on the account group. All of the accounts that belong to the account group will then be included in the Statement Export file. The export file uses file mapping.
Select Statement Export from the Account Billing Menu to display the Account Statement Export window.
Click Add and complete the following fields.
COMPANY
setup
Enter the company for which statement information should be exported.
BILL SOURCE
setup
Enter the bill source for which statement information should be exported. A bill source is a group of accounts you bill together (examples are Carrier, Dealer, NIE, etc.).
TRUCK SEQUENCE
setup
Indicate the truck sequence to ensure the export of correct trucking information for the account bill route.
SELECTION TYPE
predefined
Indicate whether this export should sort by group area, region, reason, zone, district, truck, account group, or account.
SELECTION
setup
Enter a specific selection based on the Selection Type entered.
AGING CRITERIA
predefined
Select an aging period to include (e.g., 1st, 2nd, etc.) or select all aging periods.
START DATE END DATE
date
Enter a date range for the export.
FILE FORMAT
setup
Enter a user-defined format that has been set up in File Map
.
FILE NAME
open (30)
Enter the file name of the file in the /dti/exchange/cm
directory.
FILE OPTION
predefined
Select append to add this information to the existing file, or replace to replace the existing file.
Click OK and then Continue to export the information.
In some cases, carriers deposit payments directly to a bank, and the bank sends payment information to the newspaper. The information is then read by Circulation, and the payments are applied to account balances. This is known as lockbox processing. The format of the lockbox file is defined in File Map.
Circulation reads payment data from the file /dti/exchange/cm/lockbox.d
. You must therefore place the payment information from the bank into this file.
Select Lockbox Processing from the Account Payments menu to display the Account Lockbox Processing window.
Click Add and complete the following fields.
COMPANY
setup
Enter the company for these payments.
READ OPTION
predefined
Indicate whether to edit or commit this information. Select commit to create payment records. Select edit to view a report showing the number of records processed (and errors)—you must then run Lockbox Processing again and set this field to commit.
CASH BATCH
open (10)
Enter a batch ID for these payments.
DESCRIPTION
open (30)
Enter a description of this batch.
SPLIT BY TYPE
yes/no
Select this checkbox if you want to separate payments into two different batches: a cash batch and a credit card batch.
CC BATCH
open (10)
Enter a batch ID for the credit card payments. Be sure it does not match the ID entered in Cash Batch.
DESCRIPTION
open (30)
Enter a description of the credit card batch.
BANK
setup
Enter the ID of the bank where payments were deposited.
APPLY METHOD
predefined
Indicate how the payments should be applied: automatic, invoice, or none.
FILE FORMAT
setup
Select the file map you want to use for these payments.
BPAY FILE
yes/no
Indicate if this file is from the BPay form of online banking.
FILE NAME
open (30)
Enter the name of the input file.
Click OK and then Continue to process the lockbox payments. A suspended but applied batch of account payments is created.
The Account Lockbox Processing report will be created, listing the lockbox payments that were processed.
To validate entries, print the Payment Journal before accepting these payments.
Restart this suspended batch of payments by selecting Payment Entry and entering the batch ID and default information. If you make any changes to the batch, the changes will reapply when you accept them.
Newspapers sometimes have carriers pay bond charges as security for their routes. The bond money is returned when the carrier leaves the route. This function allows you to create and print bond letters to your carriers and, optionally, create charges for the bond deposit that will appear on the letter.
Typically, some or all home delivery carriers are required to pay bonds. There are several different ways that you can set up bonds:
The bond can be a recurring charge. For example, the carrier would pay 5.00 every month. The bond charge code would be set up in Setup | Accounting | Account Billing | Charge/Credit Code
. The bond amount would be set up for each carrier in Setup | Distribution | Account Setup | Account | Specifics | Recurring Charges
.
The bond can be a recurring charge but with a maximum (defined in Setup | Distribution | Account Setup | Account | Specifics | Recurring Charges
) so that it functions like a one-time charge. For example, for a 100.00 bond, you can create a recurring charge for 50.00 with a maximum of 100.00. Hence, the charge would be used only twice.
You can make the bond a percentage of draw, rather than a flat rate (this is defined with the charge code). This method could work with either of the methods listed above.
The bond can be a miscellaneous (one-time only) charge, such as 50.00 on the first bill. The bond charge code is set up in the same place as the recurring charge, but the amount is entered in Misc Charge Credit | Misc Charge. You can also create a miscellaneous charge with this option by setting Create Charges to “y”. For each carrier, the bond amount will be assessed as:
(Carrier Collect Draw) x (Wholesale Rate) x (Factor)
Business Rules determine the factor that the carrier’s rate is multiplied by to create the initial bond deposit. The maximum amount for the bond is also established in this function, which is the total draw times the wholesale rate:
(Total Draw) x (Wholesale Rate)
If you want to give the carrier interest on a miscellaneous bond charge, you will have to transfer the miscellaneous charge to a recurring charge account (interest can only be calculated on recurring charges). To do this, define a recurring bond charge, and define another charge that uses the miscellaneous charge GL account but updates the balance of the recurring charge (see Charge/Credit Code in the Setup Manual for more information).
You can make the bond a floating percentage of draw. For example, if the bond is 50% and the draw is 200, the bond would be 100.00, which the carrier would pay initially. If the route draw went up to 300, the carrier would be charged an extra 50.00. To do a floating percentage, follow method 3 with a recurring charge, but leave the maximum at “0”. Then answer the Business Rule— By what factor should the account’s rate be multiplied to calculate the initial bond deposit?, with a factor. The bond amount will be:
(factor) x (percentage) x (route draw)
When you select CREATE BOND CHARGES, Circulation selects any accounts within that bill source that have a total recurring charge of zero. This means that only new accounts will be selected.
Select Create Bond Charges from the Account Billing menu to display the Create Bond Charges window.
Click Add and complete the following fields.
COMPANY
setup
Enter the company for which these bond letters apply.
BILL SOURCE
setup
Enter the bill source for which these bond letters apply. A bill source is a group of carriers which you want to bill together (examples are Carrier, Dealer, and Route).
BILL DATE
date
Enter the billing date for which these bond charges should appear.
DELIVERY DATE
date
Enter the date that these letters should be delivered.
DUE DATE
date
Enter the date that payments for these bond charges are due.
CHARGE CODE
setup
Enter the charge code for creating bond charges. If you will give the carrier interest on the bond, this must be a miscellaneous charge code that updates a recurring charge code (and also updates Accounts Receivable). When the carrier leaves the route and collects the bond money, a miscellaneous credit can update this same recurring charge code.
CHARGE BATCH
open (10)
Enter a unique name for these charges.
TRUCK SEQUENCE
setup
Enter the truck sequence that should be used to determine truck related information that prints in these letters.
TEMPLATE PATH
open (40)
Enter the directory and file name of the letter template (generalized form of the letter). You may define more than one letter template to, for example, send different letters for different bill sources or for different types of bond charges. Newscycle provides a sample template file named “billing/bonddep/template”. The process of creating a template is described below (this will need to be completed before initially creating bond charges).
CREATE CHARGES
yes/no
Indicate if miscellaneous charges (bond charges) should be created. Run this option the first time with Create Charges set to “n” to insure the right bond charge amounts are being calculated.
Click OK and then Continue to print the bond letter and create the bond charges (if you selected Create Charges).
Follow the steps in the following table to create the template (generalized form) for a bond letter. You can customize the letter for individual bill sources by taking advantage of the method explained in step 4.
1
Select PROGRESS EDITOR from the Utilities menu.
2
At the parallel lines, retrieve the sample template file by depressing F5 (or CTRL-G) and enter the following: billing/bonddep/template
Then press F1.
3
The sample template will be displayed. Save the file under a new name by accessing the top strip menu (press Esc-M) and selecting FILE | SAVE AS.
We suggest that you save the file in the custom directory: /custom/file_name_you_select
.
Then press F1. Be sure to save your template file in the /custom
directory (or another safe directory).
If it is saved back to its original location, it will be overwritten when software upgrades are installed.
4
Press F3 (or Ctrl-T) to enable insert mode so you can insert characters within in a line of text. Press F3 again to disable insert mode.
5
In addition to the body of the letter, you customize the letter for individual carriers by printing the contents of certain fields. These are listed in table below. Enter these field names within the curly bracket symbols: {}.
6
When you have finished editing the letter, press F6 (or Ctrl-P) to save the letter. To later edit this letter, first load and display it on screen by replacing the reference to billing/bonddep/template in step 2 above with /custom/file_name_you_select.
7
Press F8 (or Ctrl-Z) to clear the screen.
8
Enter “run sysinit” and then press F1 to exit to the Circulation main menu.
9
Reference this new template by /custom/file_name_you_select when processing the bond deposit letters.
DeliveryDate
Letter delivery date.
Month
Month and year of delivery date.
StartDate
Start date of the carrier.
Drop1
First line of the drop location.
Drop2
Second line of the drop location.
CarrierID
Carrier’s account number
Truck
Truck number from the truck sequence files.
Address1
Carrier’s name.
Address2
Carrier’s address.
Address3
Carrier’s address.
Address4
Carrier’s address.
Address5
Carrier’s address.
Address6
Carrier’s address.
DueDate
Due date of payment.
DS1
First draw delivery schedule.
DS2
Second draw delivery schedule.
DS3
Third draw delivery schedule.
DS4
Fourth draw delivery schedule.
DS5
Fifth draw delivery schedule.
CC1Draw*
Carrier collect draw total for first delivery schedule.
CC2Draw*
Carrier collect draw total for second delivery schedule.
CC3Draw*
Carrier collect draw total for third delivery schedule.
CC4Draw*
Carrier collect draw total for fourth delivery schedule.
CC5Draw*
Carrier collect draw total for fifth delivery schedule.
DS1Rate
Rate for the first delivery schedule.
DS2Rate
Rate for the second delivery schedule.
DS3Rate
Rate for the third delivery schedule.
DS4Rate
Rate for the fourth delivery schedule.
DS5Rate
Rate for the fifth delivery schedule.
CC1Total
Carrier collect total amount of rate times first delivery schedule.
CC2Total
Carrier collect total amount of rate times second delivery schedule.
CC3Total
Carrier collect total amount of rate times third delivery schedule.
CC4Total
Carrier collect total amount of rate times fourth delivery schedule.
CC5Total
Carrier collect total amount of rate times fifth delivery schedule.
ALL1Draw**
Draw total for first delivery schedule.
ALL2Draw**
Draw total for second delivery schedule.
ALL3Draw**
Draw total for third delivery schedule.
ALL4Draw**
Draw total for fourth delivery schedule.
ALL5Draw**
Draw total for fifth delivery schedule.
ALL1Total
Draw total for first delivery schedule times its rate.
ALL2Total
Draw total for second delivery schedule times its rate.
ALL3Total
Draw total for third delivery schedule times its rate.
ALL4Total
Draw total for fourth delivery schedule times its rate.
ALL5Total
Draw total for fifth delivery schedule times its rate.
CCTotal
Carrier collect total amount of all delivery schedules.
ALLTotal
Total amount of all delivery schedules.
DS3Rate
Rate for the third delivery schedule.
DS4Rate
Rate for the fourth delivery schedule.
DS5Rate
Rate for the fifth delivery schedule.
CC1Total
Carrier collect total amount of rate times first delivery schedule.
CC2Total
Carrier collect total amount of rate times second delivery schedule.
CC3Total
Carrier collect total amount of rate times third delivery schedule.
* Only Carrier Collect draw is included in the “CC” Carrier collect draw totals.
** The draw types included in the “ALL” Draw Totals are: Office Pay, Paid Complimentary, Unpaid Complimentary, Samples and Service.
Most publications have fiscal periods that end on the same date as a billing period (often the last day of the month). Because it is necessary to do an account billing run in order to update general ledger accounts, a fiscal period that does not end with a billing period creates a challenge.
In these cases, you should run the Accruals option to force a “premature” billing run, so that GL accounts can be updated for reporting purposes. However, it will also create reversal transactions on the following day. When the real billing run takes place, the transactions placed in the GL will be canceled out by the reversal transactions—except for the transactions that took place between the accrual billing run and the real billing run, and which were therefore not reversed.
For example, suppose the fiscal period ends on February 5, but the account billing period ends on January 31. On January 31, an account billing run would take place, and the GL accounts would be updated for reporting. Then, on February 5, accruals would be run, creating GL transactions for February 1-5. Reverse transactions (dated February 6) would also be created, so that when account billing is run on February 28, the entire month of February will be billed.
For more information about account billing runs, see Selection.
Performing an account accruals run involves the following steps:
Set up a date for the accruals billing run by selecting Setup | Accounting | Account Billing | Accrual Calendar (in the character interface). The date should be the date on which you run your accruals. Be sure the date is set for the correct bill source code (the one for which you are doing accruals). See Accrual Calendar in the Setup Manual for details about the Accrual Calendar. Note: This is the only step performed in the character interface. The remainder of the steps are performed in the Graphical Accounting module.
Open an accrual billing run by selecting Account Accruals | Selection in the Graphical Accounting module. You will be able to enter only those dates that are set up in the Accrual Calendar.
Process the billing in Account Accruals | Processing.
Optionally, run the Accrual Journal (Account Accruals | Accrual Journal) so that you can preview the information that will be sent to the General Ledger and Undo the accrual processing, if necessary.
Run Create Accruals (Account Accruals | Create Accruals) to create the GL entries and complete the accrual process.
If it is necessary to reverse the accruals (because mistakes were made), select Undo Accruals.
To open an account accruals run:
Choose Selection from the Account Accruals menu. The Account Accrual Selection window appears, showing all of the open runs, both accrual and billing.
Click Add and complete the following fields:
COMPANY
setup
Enter the company ID for the group of accounts being selected.
ALL ACCTS
display
All accounts will be selected.
BILL SOURCE
setup
Enter the bill source for the group of accounts being selected.
BILL DATE
date
Enter the billing date for the group of accounts being selected. This date must be specified as a billing date in the accrual calendar (see Accrual Calendar in the Setup Manual).
NEXT BILL DATE
date
The next billing date, based on the accrual calendar for the bill source entered, is displayed.
BILL PRD (period)
setup
ADV PRD (advanced bill period)
setup
Enter the advance billing period(s) if some of these accounts are set up to be billed in advance.
DESCRIPTION
open (30)
Enter a description of the group of accounts being selected for accrual billing.
STATUS
display
Click OK to finish the selection.
Click Accept and then Continue to exit the window.
To process an account accruals run:
Choose Processing from the Account Accruals menu. The Account Accrual Processing window appears, showing all of the account accrual selections that are ready to be processed.
To process a selection, select the Process checkbox next to the selection and click Continue.
To run the Accrual Journal:
Select Accrual Journal from the Account Accruals menu. The Account Accrual Journal window appears, showing the processed account accruals that can be selected.
Select the Process checkbox next to the accrual run for which you want to generate the journal.
Enter the following sort parameters:
SORT ORDER
predefined
Indicate whether the Accrual Journal should be sorted by account, account group, area, depot, district, name, region, route, truck, or zone. You can also sort by publication and then district, zone, region, or area.
TRUCK SEQUENCE
setup
If the sort order is by truck, enter the truck sequence in which you want the journal to print. The truck sequence is the pattern that describes which routes are dropped from which trucks on a given day. Examples are “daily” and “Sunday”.
TRUCK DEPARTURE
setup
Enter the truck departure sequence in which you want the journal to print when the sort order is “Truck.” The departure sequence is the departure pattern trucks follow on a given day, for example “City” or “Monday”.
Click Continue to produce the journal.
Use this option when you need to reverse the accrual processing for any reason.
Select Undo Processing from the Account Accruals menu. The Undo Account Accrual Processing window appears, showing the processed account accruals that can be selected.
Select the Process checkbox next to the accrual process you want to undo.
Click Continue to undo the accrual process.
Use this option to create the GL entries and complete the accrual process.
Select Create Accruals from the Account Accruals menu. The Account Accruals window appears.
Select the Process checkbox next to the accrual process for which you want to create accruals.
Click Continue to create the accruals.
Use this option to undo the Create Accruals process.
Select Undo Accruals from the Account Accruals menu. The Account Accruals window appears.
Select the Process checkbox next to the accruals you want to undo.
Click Continue to undo the accruals.
Accounts with debit balances may pay the newspaper via automatic withdrawals from a bank account. The withdrawals are created by this option, Bank Draft Payments, and are essentially the reverse of Direct Deposit: all accounts who owe more than a certain amount (specified at run time) and have bank account information defined for them in Account Setup will have payments exported to an ASCII file, which will be sent to the bank. The accounts will also have a payment created in Circulation for the amount withdrawn. The ASCII file will be in either a standard Canadian banking format—CIBC (see Appendix B for the format) or Bankers Automated Clearing Services format—BACS (see Appendix B for the format).
Select Bank Draft Pmts from the Account Payments menu to display the Bank Draft Processing window.
Click Add and complete the following fields.
COMPANY
setup
Enter the ID of the company for which to make account withdrawals. The company ID must be valid for the bank entered below.
BILL SOURCE
setup
Enter the ID of the bill source for which to make account withdrawals (enter “*” to multi-select bill sources).
BATCH
open (10)
Specify a batch ID for the batch of account payments that will be created by this process.
DESCRIPTION
open (30)
Enter a short description of this payment batch.
PAYMENT DATE
date
Enter the date on which the automatic payments should be automatically withdrawn from the carrier’s bank account.
CUTOFF DATE
date
The cutoff date is used to determine which payments are due at the time of file creation (i.e., so that the entire credit balance is not included). It must be the same as or earlier than the payment date.
BANK
setup
Enter the bank where the carrier’s payment money will be deposited into the newspaper’s account.
SHORT DESCRIPTION
open (10)
Enter some descriptive information (such as “Tribune”) for the account’s bank statement.
BALANCE MINIMUM
decimal (10)
Enter the minimum debit balance that an account must have in order to have an automatic withdrawal. Accounts with credit balances or debit balances for less than this amount will not be included, even if bank information is defined for them.
Click OK and then Continue to create a suspended batch of automatic withdrawals. A processing report will list the number of records, the amount exported, and any errors that occurred.
The payment batch can now be accepted in Payment Entry. The entry method must be “combined”. Upon accepting this batch, accounts who qualify for automatic withdrawal will be exported to /dti/exchange/cm/secure/paymentMMDDYY-xxx
.
The lifecycle of an account payment is outlined in the diagram below. Payments can be entered and applied to carrier/dealer accounts using this option. However, payments do not have to be applied here. If a payment does not have a corresponding charge, for example, it is considered unapplied. The Payment Journal includes information about both applied and unapplied payments.
When payments are applied, they offset charges created in account billing processing. When billing processing is run again, new charges are created. Depending on Business Rules, unapplied payments can be applied to these new charges automatically during bill processing. This can also be done using the Apply Unapplied (specific payments) or Apply All Unapplied (all unapplied payments) options. The last steps for the payment are to create a general ledger transaction for it, along with other carrier/dealer accounting information, using Payments To GL. General ledger transactions can then be exported to a file using the Export GL option.
Business Rules determine, among other things, whether:
Payments should be entered and applied as a combined or separate process, or either one.
Payments are applied automatically, manually by invoice, or either method.
A check number is required.
Credit card payments are allowed in payment entry, and if so the credit card authorization vendor (Payway Complete, Cybersource, Braintree, etc.). If using a hosted payment page for entering credit card data, the host name and URL are also specified in the Business Rules.
In Payment Entry, you can enter and apply account payments. The steps you take to verify the accuracy of account payment entries depends on whether you are entering and applying payments in one or two steps:
If entry and application are done in two steps, you should enter the batch, suspend it (by selecting Suspend rather than Accept), and then print the Payment Journal. Examine the cash batch entries and correct any errors by restarting the batch and modifying the payments. Then, accept the entered batch and apply it. Entry and application as two steps means that you must handle each account payment twice (i.e., once to enter and once to apply).
If entry and application are done in one step, you forego the opportunity to print the Payment Journal in between entry and application. You can, however, print the journal after the payments have been applied, and correct any errors by selecting Cancel Payment.
Payment adjustments are also entered in Payment Entry. For example, if a payment was entered incorrectly in a previous batch, you can make an adjustment to correct the error.
Before you begin entering payments, calculate the total amount of payments, coupons, and adjustments in this batch. This will give you the control totals for each category. The control totals are compared against what you actually enter, which can prevent entry errors.
Select Payment Entry from the Account Payments menu.
Note:
If an account billing run is in progress, Circulation displays a warning message with the bill source that is being billed. Do not enter payments for that bill source (whether or not the payments are within the billing period), or the accounts will become out of balance.
Enter the batch header information, such as batch control totals and defaults for payment entry (described below). Click OK when you have finished. If you are restarting a suspended batch, enter the batch ID and click OK; the rest of the fields will default.
BATCH
open (10)
Specify the batch ID for the payments you are entering.
DESCRIPTION
open (30)
Enter a description of this batch of payments.
BATCH DATE
date
Type the date on which you are entering this batch. The current date defaults.
BANK
setup
Enter the ID of the bank to which these payments will be deposited.
COLLECTOR SCHEME SCHEME DATE
setup setup date
These optional fields allow you to enter payments for some or all accounts on a truck as a single payment. This would be applicable if a truck driver collects payments from single copy outlets along their route. • In Collector, enter the ID of the collector (typically, the driver) who collected the payments from the account. • In Scheme, enter the truck sequence from which you will select accounts for payments. You will typically have special truck sequences set up for payments. • In Scheme Date, enter the basis date for selecting routes (and their corresponding accounts) for the truck sequence.
ENTRY METHOD
predefined
Specify the entry method for these payments: combined entry and application, entry only, or application only. Depending on Business Rules, only one of these options may be available. If you enter and apply payments in two steps, use entry both to enter payments and restart suspended batches. Then use application to apply the batch.
APPLY METHOD
predefined
Indicate how you will apply payments: • Automatic—The payment will be applied to the oldest open invoices, with leftover amounts going to the next oldest invoice, and so on. • Invoice—The Invoices window opens during payment entry, and you select the invoice to which you are applying the payment. Depending on Business Rules, only one of these options may be available. This field is not active if you are only entering (not applying) payments.
CASH TOTAL
integer (14)
Enter the total amount of all payments in this batch.
ADJUSTMENT TOTAL
integer (14)
Enter the total amount of adjustments in this batch.
COUPON TOTAL
integer (14)
Enter the total amount of coupons in this batch.
Enter individual payments by clicking Add and completing the fields in the Payment Entry panel. When you click OK, the payment is added to the Payments table on the right side of the window, and the cash, coupon, and adjustment amounts are updated automatically. Continue entering payments in this manner.
PAYMENT DATE
date
Enter the date this payment was made. The default is the current date.
ENTITY
setup
TYPE
predefined
Indicate the type of payment—cash, check, or credit card.
If you select cash, no additional details need to be entered.
If you select “check”, the Check Detail window will appear for entry of the check number. You also have the option of changing the account holder name.
PAYMENT AMOUNT
decimal (8)
Enter the amount of this payment.
COUPON AMOUNT
decimal (8)
Enter the coupon amount, if any, included in this payment.
ADJUSTMENT
yes/no
If you are making an adjustment for an account, enter charge (charge the account) or credit (credit the account).
ADJUSTMENT AMOUNT
decimal (10)
If you are making an adjustment for an account, enter the amount of the charge or credit here.
SUBSCRIPTION
Sometimes, carrier collect subscribers make “over-the-counter” payments directly to the newspaper (rather than the carrier). Since carrier collect subscribers do not, by definition, pay the newspaper, this payment is treated as an account payment. If this is an over-the-counter subscriber payment, enter the name, account number, or phone number of the subscriber making the payment. This payment will appear under the payment section of the account’s bill with the name and address of the subscriber. Note: If you populate this field and the remarks field, only the remarks will be printed on the account’s bill.
REMARKS
Enter any remarks about this payment. The remarks will appear on the Payment Journal and may appear on invoices (as determined by Business Rules).
When you have finished entering the payments for a batch, if the cash amount entered does not equal the cash total entered in the Batch Entry panel, an out-of-balance condition exists. Coupon values and adjustment values are not included in the cash total (they have their own control totals). You will be given the option of updating the cash total.
When the entered payments are correct, click Cancel and then Accept (in the header) to accept the batch. If you are applying a batch that was entered as a separate step, click Apply instead and indicate which payments should be applied. All of the control totals must match at this point—otherwise Circulation will not allow you to accept the batch (you must Suspend, Reject, or Modify the batch).
It is possible to enter a payment that covers some or all of the accounts on a truck. This method could be used, for example, to enter payments truck drivers collect from single copy outlets along their route.
In order to enter payments by truck, you must select a truck sequence in the Collection Scheme field when entering the batch information. This determines the accounts that display for a truck (based on the scheme date entered). Special truck sequences may be defined just for account payment entry, or existing truck sequences used in Publishing can be selected. A collector is also specified.
Note:
If the payment amount is different than the balance for the selected routes, the collector assigned to the account in Account Setup (typically the collector selected here) is charged for the difference.
To enter a payment for the truck, enter the truck ID in the Entity field. The Select Accounts popup window displays, listing the accounts delivering routes on the truck. If the truck contains relay trucks, accounts on those trucks will be displayed as well. Check all accounts for which payments have been collected, or click Select All to select all accounts on the truck. Click OK to accept the account selection.
Note:
If the Apply Method is “Invoice”, each account will show the open items outstanding. If the Apply Method is “Automatic” or the entry method is “Entry”, the accounts will be displayed on one line with only the total balance showing.
The total balance for all the selected accounts will default in the Payment Amount field, but can be changed.
Suppose you are entering a batch of payments from four accounts, and the total amount of checks and cash is 700.00. One account also has a coupon for 5.00, and another account, who was shorted one day last week and had to buy extra papers at the grocery store, has a credit adjustment of 10.00. At this newspaper, payments are entered and applied in a combined process, and applied to specific invoices. The example below illustrates how the batch entry panel would be entered for this batch.
Since your apply method is by invoice, for each payment you enter, the Apply Invoices window will open, listing the open invoices for this account. You can then select one or more invoices to which the payment should be applied.
Select the appropriate checkbox(es) and click OK to continue. If this window does not open, it is because the account has no open invoices. Print the Summary Age Analysis Report or the Detail Age Analysis Report to check the status of carrier accounts.
If an invoice is not selected, the payment amount will remain unapplied. Likewise, if the payment amount is greater than the invoice amount, the leftover amount will remain unapplied.
For example, say the carrier made a payment of 500.00. The oldest invoice (for 494.75) could be selected, but 5.25 of the payment would be left over. If there were a next-oldest invoice, you could apply the 5.25 toward that.
Note:
Account payment adjustments are applied to the “oldest” balance, while miscellaneous charges/credits are applied to the current balance.
As we continue with our example, we enter a payment for Chris Bragg—a check for 200.00. Chris has also sent in a 5.00 holiday coupon, so we enter this in the Coupon Amount field. Another carrier, Rhonda Coon, was shorted 10.00 when her payment was entered last month; so an adjustment credit for 10.00 is entered. After all of the payments have been entered and the control totals equal the entered totals, you accept the batch.
Next, you print the Payment Journal and check your entries. Any payments that were entered incorrectly can be canceled using Cancel Payment, and then reentered in another batch.
Certain routes may request a statement of activity in between billing periods. For example, a large single copy outlet might be billed on a monthly basis, but require preliminary invoices each week. Trial Billing will produce these invoices, based on activity in a date range, without updating any information in Circulation.
Although trial billing invoices will give an accurate report of activity within the date range, it is important to note that:
The trial billing will have no effect on the carrier/dealer’s account. The invoices are the only thing produced—no charges or any other records are created. Therefore, this process cannot replace account billing.
The invoices will not be an exact reflection of the carrier/dealer’s account. Some items, such as payments and advance charges/credits, will not be included. There will be no balance forward on the invoices, only a total of charges/credits for the date range.
Draw charges and credits
Returns and draw adjustments
Miscellaneous charges and credits, including bonus and TM delivery credits
Recurring charges and credits. When defining the recurring charge codes, be sure to set Print Bal On Bill to “n” (trial billing does not update recurring charge balances).
Substitute charges
Levy charges
Back credits
The invoices will not contain payments, coupons, tips, or messages.
You can run Trial Billing as often as you like. Both the processing and invoice creation are completed by this one option.
Select Trial Billing from the Account Billing menu to display the Trial Account Billing window.
Click Add and complete the following fields.
COMPANY, BILL SOURCE
setup
Enter the company for which to run a trial account billing.
ALL ACCOUNTS
yes/no
Enter “n” if you want to run trial billing for a single account.
ACCOUNT
setup
If you entered “n” above, enter the account number for which you want to run trial billing.
BILL SOURCE
setup
Enter the billing source for which to run trial account billing.
USE PENDING DRAW
yes/no
Indicate if you want to include pending draw in the trial billing. If you select this checkbox, you will be able to enter a future date range beyond where final transaction processing has been run for the publication delivered by the route.
START DATE, END DATE
date
Enter the date range for the trial account billing. Only draw charges, returns, miscellaneous charges, etc. for this date range will be included. Unless Use Pending Draw is selected, all days within the range must be unbilled and published (final transaction processing must be run through the end date).
BILL PERIOD
setup
Enter the billing period to use for recurring charges. Because normal billing periods will have recurring charge amounts for the whole period, we recommend defining a special billing period and recurring charge codes for trial account billings. The recurring charge amounts should reflect the trial billing period (e.g., 1 week rather than 1 month). All recurring charges and credits, including advance charges, will reflect the current period only.
SORT ORDER
predefined
The standard invoice sort orders are available for trial invoices: account, depot, distribution code, district, name, publication/area, publication/district, publication/region, publication/zone, route or truck.
TRUCK SEQUENCE, TRUCK DEPARTURE
setup
Enter the truck sequence and truck departure sequence in which the invoices should print when the sort order is “Truck”. If the sort order is not “Truck”, these sequences enable the system to print the correct truck on the invoice.
Click OK and the Continue to create the invoices. A processing report will be displayed first (similar to the Account Billing Processing report, but without balance forward or aging totals), and the invoices next. The processing report file name is entered in the View & Print Options window. The invoice file name will be the first five characters of this name, plus “INV”, plus the extension. For example, if the processing report is saved as TRIALPROC.15, the invoices will be saved as TRIALINV.15
.
Once payments are applied, they cannot be modified in Payment Entry. You must then cancel the payment by using this option and entering a separate batch of payment cancellations. Payment cancels are automatically applied to a carrier’s account as negative amounts. A cancel payment cannot be entered unless it matches a payment amount for that particular carrier.
Note:
Payment cancellations should not be entered when a billing run is in process.
Select Cancel Payment from the Account Payments menu to display the Cancel Payment batch screen.
Enter batch default information on the sign-on screen.
BATCH ID
open (10)
Enter an ID for this batch of account payment cancellations.
DESCRIPTION
open (30)
Enter a description of this batch.
CANCEL DATE
date
Type the date on which you are entering this batch. The current date defaults.
Select Accept to accept the default information and display the Account Payment Cancel Batch screen.
Enter the payment cancels for each account, one after another.
ACCOUNT
setup
Specify an account (enter the carrier/dealer’s name, ID, social security number, telephone number or route ID).
CHECK
open (8)
Enter the check number of the original payment. Enter “*” to include all check payments.
AMOUNT
decimal (11)
Enter the amount of the account payment.
DATE
date
Enter the date this payment was made (you can leave DATE blank).
CASH BATCH
setup
Enter the batch ID in which the account payment was initially entered, or enter a question mark to include all batches.
Circulation will search for a payment that matches the criteria you have entered. If it finds a match, it will allow you to enter more payment cancels; if it cannot find a match, you will have to reenter the payment information.
When you have finished entering payment cancels, press F4 and select ACCEPT to apply the payment cancels to the accounts and return to the main menu.
A credit card company might not accept all account credit card payments sent to it by your newspaper. Cancel payment transactions must then be entered in Circulation for rejected credit card payments. To streamline this process, you can select Cancel Credit Payment and import a list of rejected credit card payments from an ASCII file; a cancel payment batch will automatically be created for the payments.
Before running this option, the ASCII file must be placed in the /dti/exchange/cm
directory and named cancelccpmt.d
. For the required format for the ASCII file, see Appendix B.
Select Cancel Credit Payment from the Account Payments menu to display the Cancel Account Credit Card Payments window.
Click Add and complete the following fields.
Click OK and then Continue to begin processing. The ASCII file will be read and, if you selected the “commit” option, a batch of payment cancellations will be created. After processing is complete, a processing report is displayed, listing the payments processed and any errors that occurred.
The Payment Journal will record all payments (both applied and unapplied) and payment cancellations entered in a specific batch or date range. One way in which the journal can be used is to verify account payments before a batch is applied.
Select Payment Journal from the Account Payments menu to display the Payment Journal window.
Click Add and complete the following fields.
Click OK and then Continue to produce the report.
The Applied Payment Journal lists accounts that have had payments or credit memos applied to invoices on a certain date or within a certain date range. This includes payments applied in payment entry, account bill processing, or the two “apply unapplied” options.
Select Applied Journal from the Account Payments menu to display the Applied Payment Journal window.
Click Add and complete the following fields.
Click OK and then Continue to produce the journal.
When you apply account payments, any amount that is not applied to an invoice is considered “unapplied”. Typically, you will have Business Rules set to apply unapplied payment amounts automatically during account bill processing, when new charges are created. Likewise, you will typically set Business Rules to apply credit memos (typically account delivery credits) that are also created in account bill processing. However, if you want to apply unapplied payments and credit memos as a separate step, you can use this option, to apply payments and credit memos to an individual carrier’s outstanding balance.
Select Apply Unapplied from the Account Payments menu to display the Apply Unapplied screen.
Complete the following fields.
Enter the accounts, one after another, that should have unapplied payments applied. When finished, press F4 to exit to the main menu.
Select this option to create the general ledger transactions associated with account payments. Exporting these transactions using the Export GL option is the final step for account payments.
Note:
Business Rules determine the level of detail that transactions are created for the general ledger (account, detail, or summary).
Select Payments To GL from the Account Payments menu to display the Interface Payments to GL window.
Enter a batch ID in Cash Batch, or click the lookup icon to select one or more from a list.
Click OK and then Continue to begin the interface.
Apply All Unapplied is a method of applying all unapplied carrier amounts for one or more companies and bill sources.
For example, you might select this option before processing account bills to pay off outstanding invoices in one aging period which are offset by a credit in another aging period. There is no consideration of date—you simply enter the company and bill source (or enter “*” to multi-select) and click OK and then Continue. Circulation will automatically apply all unapplied payments and credit memos in carrier accounts.
Prenotification files are used to prepare automated currency exchanges with banks. Typically, a prenotification file is sent to a bank to verify that all of the bank and account information is correct before transactions are sent. This option generates a prenotification file in Bankers Automated Clearing Services (BACS) format that is used to verify carrier/dealer account information before submitting direct deposits.
Select BACS Pre-Notify from the Account Payments menu to display the BACS Prenotification window.
Click Add and complete the following fields.
Click OK and then Continue to produce the file.
Enter the billing period to include in this selection. The bill period determines what charges are included in the accrual billing. Enter “*” for a multi-select window. See for more information about bill periods.
This field displays the status of the billing run. See for an explanation of the various statuses.
Specify an account, account group, or truck: • Account—Enter the carrier/dealer’s name (or part of the name), ID, social security number, telephone number, route ID, or invoice number. • Account Group—Enter the account group ID. You must use an entry method of “combined” and an apply method of “invoice”. When you enter an account group ID, open invoices for accounts in that account group will be displayed for selection. • Truck—If you selected a collection scheme when adding the batch information, you can enter a truck ID in this field. This option is documented on .
If you select “credit”, the Credit Card window opens for entry of the credit card number, validation value, expiration date, and authorization number. The fields in this window vary based on Business Rules, your selected credit card authorization vendor, and whether you are using the Hosted Order Page. See for more information on credit card authorization.
READ OPTION
predefined
Indicate whether to commit or edit the credit card payments in the ASCII file. If you choose “Commit”, cancel payment transactions will be created. If you choose “Edit”, only the processing report will be created (you can then look the report over for errors before committing).
BATCH DESCRIPTION
open (10) open (30)
If the field above is set to “commit”, enter an ID and description for the batch of account payment cancellations that will be created by this process.
CANCEL DATE
date
Type the date on which you are entering this batch. The current date defaults.
COMPANY
setup
Enter the ID of the company for which you are applying unapplied payments.
BILLING SOURCE
setup
Enter the ID of the billing source for which you are applying unapplied payments.
APPLICATION DATE
date
This is the date that the payments will show up in the general ledger as “applied.” You will usually enter today’s date here.
APPLICATION MODE
display
Indicate whether the Invoice or Automatic application mode is to be used.
PAYMENT TYPE
predefined
If “Invoice” is selected as the application mode, then the payment type must be identified here. Select Unapplied Payments or Credit Memos.
If you select “Credit Memos,” a popup window will appear during entry where you can specify the invoice number.
BANK
setup
Enter the bank to which this prenotification file will be sent. The bank must have an electronic file format of BACS.
FILE NAME
open
Enter a name for the prenotification file.
This section guides the user through the menu options that are available under the Misc. Charge/Credit menu.
This section guides the user through the menu options that are available under the AP/Direct Deposit menu.
Business Rules determine whether a check number, source code, and reason code are required for a subscriber payment. Business Rules also determine the default source code, reason code, and bank, the number of days a payment can be backdated, whether a payment should auto-start a former subscriber, the draw adjust code to be used when a payment converts a subscriber from carrier collect to office pay, and (when this takes place) the number of days after expiration that the expire date should default as the effective date. Finally, Business Rules determine the processing vendor for credit card payments.
If a payment (or payment adjustment) is made for a subscriber on a promotional rate, the subscription will “step up” to the rate defined as the next rate after the promotional. This will happen regardless of the payment amount. This means that subscribers who make larger payments will stay on promotional rates longer.
If the discounted rate should be offered for a set time period (such as one year), marketing terms should be used. With a marketing term, the subscriber remains on the rate until the full term has completed. Small payments will not “step up” the rate until the marketing term has ended, while a large payment will only buy up to the marketing term length on the discounted rate (the remainder of the payment will be applied to the “step up” rate).
See Subscription Rates in the Setup Manual for more information on promotional rates and marketing terms.
This section guides the user through the menu options that are available under the Subscriber Payments menu.
Rewards programs are promotional offers, such as Air Miles, that give consumers credits for purchasing a product. Rewards will be generated for subscribers when a payment is entered for them if they:
Are signed up for a rewards program, and
Their rate term is set up to give a reward amount for that program.
If payments are imported via Subscriber Lockbox or the Subscriber Activity Import, those processes will also generate rewards. Likewise, Auto Payments will generate rewards as part of the auto renew process. If a payment is subsequently modified, the reward amount will change accordingly, and if a payment is deleted the rewards will be removed. If a payment is canceled a negative reward will be created to cancel out the original reward. Unlike manually entered rewards, generated rewards do not create Reward transactions.
This section guides the user through the menu options that are available under the Subscriber menu.
REPORT TYPE
predefined
Indicate whether payments to be included in the journal should be selected based on batch or date range.
BATCH
setup
If you are selecting payments based on batch, enter the batch ID to include in the journal.
COMPANY
setup
Enter the company whose payments should be included in the journal.
BILL SOURCE
setup
If you are selecting payments based on date range, enter the billing source whose payments should be included in the journal, or an asterisk (*) for all billing sources.
START DATE, END DATE
date
If you are selecting payments based on date range, enter the range of dates here. All payments entered on or between these dates (within the company and bill source defined) will be included in the journal.
PRINT PRIVATE DATA
yes/no
Indicate whether private banking and credit card information (such as account numbers and credit card numbers) should be displayed on the journal.
DISPLAY OPTION
predefined
If you answered “yes” in PRINT PRIVATE DATA, indicate here whether private credit card and banking information should be masked (only the last four digits shown) or displayed in full. Note that users without the proper security will not be able to see private data even if “full” is selected.
ALL BANKS
yes/no
Select this checkbox if all banks should be included. Otherwise, specify the bank in the bank field.
BANK
setup
If you are selecting payments based on date range, enter the bank for which payments should be included in the journal (payments made to other banks will not be included).
PRINT ADDITIONAL DETAIL
yes/no
Indicate if you want an additional line to be printed displaying each payment’s create user, create date, create time, modify user, modify date, modify time, batch description, and batch status (accepted or suspended).
SORT BY
predefined
Indicate whether the journal should sort by carrier account number or by payment sequence (order in which the payments were entered).
REPORT TYPE
predefined
Indicate whether the journal should include a date range or an entry session (a single date).
APPLICATION DATE
date
If the journal is being run for an entry session, enter the application date here. All payments and credit memos applied on this date will be included in the report.
COMPANY
setup
If the journal is being run for a date range, specify the company that should be included.
BILLING SOURCE
setup
If the journal is being run for a date range, specify the billing source that should be included.
START APPLICATION DATE, END APPLICATION DATE
date
If the journal is being run for a date range, enter the start and end dates here. All payments or credit memos applied on or between these dates will be included in the report.
Single copy outlets may send “proof of sale” documents, listing the amounts for copies sold by the outlet. These proof of sale amounts can be imported into Circulation via the Proof of Sale Adj option. Importing proof of sale amounts will not change a dealer’s balance. However, it will create offsetting charge and payment (credit) records, effectively moving part of the balance (equal to the sold amount) to the proof of sale date. These offsetting entries will also display on the dealer’s invoice.
Importing proof of sale amounts is entirely optional. If choosing to import them, you may wish to define charge and credit codes to use for proof of sale, or use existing codes. A Proof of Sale file map must also be defined (see Appendix B). See About Sold / Shrink Copies for more information on sold copies.
Place a file containing the proof of sale adjustments in your dti/exchange/cm directory
.
Select Proof of Sale Adj from the Account Payments menu in Graphical Accounting. The Proof of Sale Adjustment Import screen displays.
Select Add and enter information about the proof of sale batch, in the fields described in the table below.
CASH BATCH DESCRIPTION
open (10) open (30)
Specify a batch name and description for this batch of proof of sale adjustments. The amounts are imported into the system as an account payment batch.
CHARGE CREDIT
setup
Select the charge and credit code that should be used to create the offsetting entries for the sold amounts
BATCH DATE
date
Specify the entry date for the proof of sale batch. If the import file has no date field, this date will also be used as the date for the payment (credit) and charge transactions.
BANK
setup
Select the bank that should be associated with the payments.
FILE FORMAT
setup
Select the file format for the import. Only file maps with a “ProofOfSale” usage can be selected.
FILE NAME
open (45)
Enter the file name containing the proof of sale amounts. The file must exist in your dti/exchange/cm directory.
Click OK and then Continue to import the payment adjustment amounts. If a company and/or bill source are included in the file, payments will only pay off account charges for that company/bill source. The payment batch will initially be suspended.
Restart and accept the payment batch in Payment Entry. The entry method will be “ProofOfSale.” Payments cannot be added to a “ProofOfSale” batch, nor can a batch be manually added with this entry method.
Newspapers sometimes interface miscellaneous credits to the AP system between billing periods (so, for example, a check for a contest prize can be sent immediately). This can be done via Misc. Charges Export. In order to be exported, a miscellaneous credit must be unbilled and part of an accepted batch.
Select Misc. Charges Export from the Misc. Charge/Credit menu to display the Misc. Charge/Credit Export window.
Click Add and complete the following fields.
COMPANY, BILL SOURCE
setup
Enter the company and bill source for which to interface miscellaneous credits, or enter “*” to multi-select companies and bill sources.
START DATE, END DATE
date
Enter the date range for which to export miscellaneous credits. Only miscellaneous credits entered within this date range will be exported.
MINIMUM AMT
decimal (10)
Enter a minimum amount for the interface. Only miscellaneous credits that are equal to or greater than this amount will be interfaced.
DUE DATE
date
Enter the due date for the carrier check to be cut by the AP system.
CHARGE CODE
setup
Enter the miscellaneous credit code that should be interfaced, or enter “*” to multi-select credit codes. Only miscellaneous credits can be selected, not charges.
Click OK and then Continue to run the interface. A processing report will display the number of records exported and any errors. Credits for the miscellaneous credit codes selected will be exported to the file /dti/exchange/cm/misccredsMMDD
, where “MMDD” are the month and day of the due date entered. The format of the file is based on Interface to AP format defined in the Business Rules (see Appendix B). A debit transaction will also be created for the carrier’s account, which will be picked up during the next account billing and debited from the carrier’s account balance.
When complaints are entered in Customer Service, they can be flagged to charge the carrier. An actual charge, however, is not created until the charges are reviewed in this option.
Complaints are entered in Services | Customer | Transaction | Add | Complaint
. The operator indicates whether the carrier should be charged for the complaint.
A batch of miscellaneous charges is created for complaints within a certain date range using this option, Charge For Complaints. Complaints can also be modified here. Charges will not be created for complaints that have an “n” in the CHG column or a charge amount of zero.
Complaints from the batch can be modified or deleted in Misc. Charge/credit | Misc. Charge.
The charges are accepted in Misc. Charge/credit | Misc. Charge and are ready to be billed.
Select Charge For Complaints from the Misc. Charge/Credit menu to display the Complaint Batch screen.
Set parameters for the charges to be included in this batch.
PRODUCT
setup
Enter a publication for the batch. Only complaints entered for this publication will be included.
START DATE, END DATE
date
Enter a date range for the batch. Only complaints entered during this date range will be included.
DISTRICT
setup
Enter the district that you want included in the batch or enter “*” for a multi-select window. Only complaints for routes in these districts will be included.
ROUTE TYPE
predefined
Enter the route type you want included in the batch or enter “*” for a multi-select window. Only complaints for routes of these types will be included. See Route Type in the Setup Manual for more information.
RATE SOURCE
predefined
Indicate whether default complaint charge amounts should be based on Entry (the default is entered with the batch in the next field, COMPLAINT RATE) or Setup (the amounts entered in Complaint Charge Setup will be used, and COMPLAINT RATE will be skipped).
COMPLAINT RATE
decimal (9)
Enter the default amount that should be charged for each complaint (this can be overridden during review).
BATCH
open (10)
Assign an ID to the batch that will be created for these complaints charges.
DESCRIPTION
open (30)
Enter a description of this batch.
BATCH DATE
date
Enter the date for the miscellaneous charges created in this batch. This date determines when the charges get billed.
REVIEW ALL
yes/no
Indicate if you want to review all complaints (“y”) or only complaints that were flagged to charge the carrier (“n”).
Select Accept to begin reviewing complaints. If you select Reject, the batch will be rejected. If the same parameters are entered again, the same complaints will appear.
All complaints that fall within the defined parameters will appear on the screen. Select Review to edit complaints: you can modify the charge code or amount, and change the “charge carrier” flag. Charges that are accepted into the batch (Chg set to “y” and Amount > 0) will not appear in any subsequent batches.
Once editing is completed, select Accept to create the batch of charges.
Miscellaneous charges are occasional charges (and credits) that are not applied on a regular basis. Regular charges (such as a monthly charge for rubber bands) should be set up as recurring charges (see Account in the Setup Manual), which are automatically applied by bill period. Miscellaneous charges must be entered manually, using this option.
An example of miscellaneous charges and credits entered for an account is given below:
Mileage +17.00 New paper bag -3.00 Subscriber Tip +5.00
Like other charges, miscellaneous charges must be set up with a charge code (see Charge/Credit Code in the Setup Manual). The charge code describes the charge and indicates whether it is a debit (charge) or credit to the carrier account. It also defines the GL accounts involved with the charge and may have a default charge amount (this amount can be overridden).
Miscellaneous charges and credits are entered in batches.
Select Misc. Charge from the Misc. Charge/Credit menu to display the miscellaneous charges window.
Enter default batch information in the Batch Entry pane.
BATCH
open (10)
Assign a batch ID to the batch of miscellaneous charges/credits you are entering.
BATCH DESCRIPTION
open (30)
Enter a description for this batch of charges/credits.
PRODUCT
setup
Enter the product for which these miscellaneous charges/credits apply. Only carriers who deliver this product may be charged or credited.
BATCH DATE
date
Specify the entry date that should be given to this batch (the current date defaults).
CONTROL TOTAL
decimal (14)
A control total is the net total for the batch you are processing. This is total amount of charges minus the total amount of credits (use a “-” sign if the credits exceed the charges). For example, if you have:
5.00 charge 10.00 charge 15.00 credit 3.00 charge
The control total would be 3.00. Enter the control total for this batch of miscellaneous charges/credits.
Click OK to accept the batch defaults.
Click Add to enter misc. charges or credits one at a time, or click the Wizard icon ()to run the miscellaneous charges utility. This utility will populate a miscellaneous charge/credit batch for selected accounts, based on edition, route type, and management level (see Misc. Charge/Credit Wizard for more information).
You can now enter the charges and credits, one at a time. The following table describes the charge/credit entry fields.
ACCOUNT
setup
Enter the account name, ID, social security number, telephone number, or route ID.
COMPANY
display
The company will be displayed.
ROUTE
setup
Enter the route associated with this charge. If a route ID was entered in ACCOUNT to locate the account, it defaults here. The route is displayed if this carrier only delivers one route.
BILL ACCOUNT
setup
More than one account may qualify for charges and credits for this route. For example, you may want to enter a charge for the delivery carrier of the route, even though the carrier is no longer billed for it (Business Rules determine whether this is allowed). If more than one carrier/dealer qualifies for charges/credits, enter the billing account here. Otherwise, the account entered in the ACCOUNT field will be displayed.
CHARGE CODE
setup
Enter the miscellaneous charge/credit code. This code will determine whether the entered amount is a charge or credit.
AMOUNT
decimal (10)
Enter the amount of this miscellaneous charge/credit. A suggested amount may default. Do not enter amounts with minus signs. Circulation determines whether the amount entered is a charge or a credit based on the charge/credit code entered in Charge Code.
DESCRIPTION
open (30)
A description of the miscellaneous charge or credit defaults from the code. You can modify this description.
After entering a charge/credit, click Add Another to add additional charges/credits to the batch, or click OK.
After all of the charges and credits have been entered, click Accept to accept the batch and exit to the main menu. If you click Reject, the batch will be rejected. You may also Suspend the batch and restart it later. Once a batch is accepted, the charges and credits are applied to the carriers’ accounts during account bill processing. In order to be accepted, the control total for a batch must equal the total of actual charges and credits entered.
The Miscellaneous Charge/Credit Wizard populates a batch by creating a flat amount or per-piece charge/credit for a group of accounts selected by edition, route type, and management level (area, region, zone, or district). For example, you may want to give all delivery carriers a per-piece credit for working on a difficult route.
Answer the questions on the card.
What is the charge date?
Enter the effective date for these charges or credits. Note: In order for per-piece calculations (below) to occur, there must be draw on this date.
What charge code will be used for this selection?
Enter the code to be applied to these charges or credits. This code will determine whether the entered amount is a charge or credit.
What is the rate type?
Enter per piece (charge or credit is applied to each newspaper delivered) or flat amount (charge or credit is applied to each account selected). If you enter “per piece”, the next two questions will become active.
What is the calculation method?
Enter the type of draw to which the per-piece charge or credit will apply. You can enter: • Gross—The regular home delivery or single-copy draw for the day. • Net—The gross draw, plus returns and draw adjustments for the day. • Adjusted—Only the returns and draw adjustments for the day. • Gross + Adjusted—To include both gross and draw adjustments for the day (returns will not be included in the calculation).
What % of the draw should be used in the calculation?
Enter the percentage of the draw that will receive this per-piece charge or credit.
What is the charge amount?
Enter the amount of this charge. Do not enter amounts with minus signs; Circulation determines whether the amount entered is a charge or a credit based on the charge/credit code entered above.
What is the description for the charges?
A description of the charge or credit defaults from the charge/credit code. You can modify this description.
Click Next to display the second card, where you will select the routes for which miscellaneous charges will be created.
Answer the questions to create the selection criteria (described below).
Include all editions? Which edition are these charges for?
Enter the edition to which these charges apply, or include all editions.
Include all route types? Which route type should be used?
Enter the route type to which these charges apply, or include all route types.
Include all management levels? Which management level should be used?
Enter the management level (area, region, zone, or district) to which these charges apply, or include all management levels.
Which [management entity] should be used?
If you specified a management level for the previous question, select the area, region, zone, or district for which these charges will be created.
Include all trucks? Which truck sequence should be used? Which truck should be used?
Select this checkbox if you want to include all trucks. Choose the truck sequence that should be used. Enter the truck ID, enter “*” to multi-select trucks.
Include all delivery carriers?
Select this checkbox if you want to include all delivery carriers.
Include non delivery carriers?
Select this checkbox if you want to include non-delivery carriers (such as agents, trainees, etc.)
Include all non delivery carriers? Which account type should be used?
Select this checkbox if all non-delivery carriers should receive the charge or credit. Otherwise, deselect it and choose the account type (agent, trainee, etc.) that should receive the charge or credit.
Click Add to save the selection criteria. If you have more criteria to enter, answer the questions again, then click Add again to save those criteria.
When you have finished entering criteria, click Commit. You will be returned to the Miscellaneous Charges window, where the selection results of the Wizard will appear in the table.
Continue to add, modify, or delete individual items in the batch as needed.
Accept, reject, or suspend the batch as usual.
Using this option, you can cancel any miscellaneous charges or credits that were erroneously entered. A cancel creates a reverse transaction (it does not delete the original charge or credit). You can still cancel charges or credits after they have been processed in account bill processing.
Select Cancel Misc. Charge from the Misc. Charge/Credit menu.
Specify a previously entered miscellaneous charge batch by entering a batch name in Batch ID. Then select Accept to accept the information that is displayed.
The charges and credit will display next. Select Cancel and scroll to the charge or credit that should be canceled. Then press Enter to cancel that charge or credit from the batch. Press F4 and then Accept to accept the cancellations.
Use this option to produce the Charge and Credit Journal, a report that lists all miscellaneous charges entered in a specific batch or date range. The journal can be used to record miscellaneous charge entries. If a miscellaneous charge is cancelled, both the charge (or credit) and the cancellation will show up on the report.
Select Charges Journal from the Misc. Charge/Credit menu to display the Charges and Credit Journal window.
Click Add and complete the following fields.
COMPANY
setup
Enter the company for which to print miscellaneous charges and credits, or enter “*” to multi-select companies. Only accounts belonging to this company will be included.
BILL SOURCE
setup
Enter the bill source for which to print miscellaneous charges and credits, or enter “*” to multi-select bill sources. Only accounts with this bill source will be included.
REPORT TYPE
predefined
Indicate if charges should be included in the journal by date range or batch.
BATCH
open (10)
If Report Type is batch, enter the batch ID here.
START DATE, END DATE
date
If Report Type is date range, enter the beginning and ending dates of the date range.
SORT OPTION
predefined
Specify how the report should be sorted: by account name (alphabetical), charge code or account number.
BILLING OPTION
predefined
Indicate whether the report should include charges that have been billed, not billed, not billed and apply-to-AR-now, or all charges. Apply-to-AR-now charges are charges/credits that are immediately applied directly to the carrier’s balance for aging purposes (not applied at the end of the billing period, as are most charges/credits). Charge codes can be set up to be apply-to-AR-now. See Charge/Credit Code in the Setup Manual for more information.
Click OK and then Continue to produce the report.
Typically, account credits are interfaced to an Accounts Payable system at the end of a billing period (see Interface to AP). However, some newspapers give accounts advances on certain recurring credits, such as mileage. In order to do this, the credits may have to be interfaced between billing periods, using the Mid-Month Payment Export feature.
In order to use this feature, you must set up a new billing period for mid-month credits. You should then modify account setup for all accounts involved, changing the bill period for all applicable recurring charges to the new mid-month period. Account billing should not be run for the mid-month bill period. This will prevent the recurring credits from being applied to the account’s balance twice.
Credits for the recurring credit codes selected will be exported to the file /dti/exchange/cm/midmonthpmtMMDD
, where “MMDD” are the month and day of the due date entered. The format of the file is based on Business Rules (see Appendix B). A debit transaction will also be created for the account, which will be picked up during the next account billing and debited from the account’s balance (billing will be crediting the account for the full recurring credit, but the account has already received a portion of it, so that portion must be debited).
Select Midmonth Pmt Export from the AP/Direct Deposit menu to display the Recurring Mid-Month Payment Export window.
Click Add and complete the following fields.
COMPANY, BILL SOURCE
setup
Enter the company and bill source for which to interface recurring credits, or enter “*” to multi-select companies and bill sources.
PROCESS DATE
date
Enter the date for which to export recurring credits. Only recurring credits active on this date will be exported.
MINIMUM AMT
decimal (10)
Enter a minimum amount for the interface. Only recurring credits that are equal to or greater than this amount will be interfaced.
DUE DATE
date
Enter the due date for the check to be cut by the AP system.
RECURRING CHARGE CODE
setup
Enter the recurring credit code that should be interfaced, or enter “*” to multi-select recurring credit codes. Only recurring credits can be selected, not charges.
Click OK and then Continue to run the interface. A processing report will list accounts that had recurring credits exported.
Accounts with credit balances can have their credit amounts deposited directly to a bank account, using this option. Direct Deposits will write an ASCII file containing credit amounts for all accounts that have a credit balance and who have bank account information set up (see Account in the Setup Manual for more information). As part of this process, the credits will be offset in carrier/dealer accounts by debits. The ASCII file will be located in /dti/exchange/cm/secure
and the file name will be depositMMDDYY-xxx.d
(see Appendix B for the formats). You can then send this file to the bank. Newspapers with direct deposit programs usually require carrier/dealers in the program to have accounts at a bank where the newspaper has an account.
Note:
Contact the Naviga Global Support Center in the early planning stages as custom programs may need to be written to accommodate the format of the file going to your bank.
Select Direct Deposits from the AP/Direct Deposit menu to display the Account Direct Deposits window.
Click Add and complete the following fields.
COMPANY
setup
Enter the ID of the company for which to make account deposits. The company ID must be valid for the bank entered below.
BILL SOURCE
setup
Enter the ID of the bill source for which to make account deposits (enter “*” to multi-select bill sources).
BANK
setup
Enter the ID of the bank that will process the direct deposit file; this will determine the Cash in Bank account that will be credited with the direct deposits. See Bank in the Setup Manual for details.
DEPOSIT DATE
date
Enter the date you are making the deposit for (the current date defaults).
SHORT DESCRIPTION
open (30)
Enter a short description to print on the account’s bank statement.
PRENOTIFICATION
yes/no
Indicate whether a prenotification file should be generated. This file will include all accounts with a start date greater than or equal to the deposit date; it will list account information but not amounts.
The prenotification file can be used by the bank to verify that the account information is correct. When first setting up a direct deposit program, we recommend that you create a prenotification file with DEPOSIT DATE set to an early date such as 01/01/1900 to select all accounts.
BALANCE MINIMUM
decimal (10)
Enter the minimum credit balance an account must have to be included.
Click OK.
Click Review if you want to review the deposits that will be made.
The “Credit Balance Review” screen will be displayed.
Click Continue to process the direct deposit. The ASCII file will be created, and all exported credit will be offset with debit memos. An Account Direct Deposits report will be created, showing the number of records processed and any errors that occurred.
When Circulation exports account credits in Interface to AP, each account’s vendor ID in the Accounts Payable system is included in the export. Vendor IDs can be specified when accounts are set up, or they can be automatically imported with this option. For the required format for the vendor import file, see Appendix B.
To run the import, select Add and enter the file name containing the vendor IDs—the file can have any name (12 characters or less) but must be located in the /dti/exchange/cm
directory. Then select Continue. Each account ID in the imported file will be matched with accounts in Circulation. If a match is found, the account’s vendor ID will be updated with the vendor ID in the import file. If there is no match, the account ID in the import file will be listed in an error log that displays after the import has processed. The standard viewing and printing options are available for this report.
Select this option to print a journal listing accounts that had credits interfaced to a general ledger system or a direct deposit file.
Select Credit Journal from the AP/Direct Deposit menu to display the Account Credit Journal window.
Click Add and complete the following fields.
COMPANY
setup
Enter the ID of the company for which direct deposits or AP invoices were made, or enter “*” to indicate all companies.
BILL SOURCE
setup
Enter the ID of the bill source for which direct deposits or AP invoices were made, or enter “*” to indicate all bill sources.
START DATE, END DATE
date
Specify the period to cover in the report. Credits that were interfaced via Interface to AP or Direct Deposits during this date range will appear on the report.
Click OK and then Continue to produce the journal.
Accounts that have a credit balance (such as carriers with mostly office pay subscribers) need to have their credit transferred to Accounts Payable (in the general ledger) so that they can be paid. This option transfers account credit balances to the general ledger (via an ASCII file) and automatically writes them off in Circulation. There are four scenarios that might exist for credit transfer:
You use SBS. Circulation places the credit transactions in an ASCII file called apcheck.d
in /dti/exchange/cm
(see Appendix B for the format). SBS then pulls in this file.
You interface account credits to Compu-Share, Lawson or Dunn and Bradstreet, three popular AP systems. This option also creates an ASCII file called apcheck.d
, but the format of the file will be different. Note that the Dunn and Bradstreet format will also contain direct deposits (so Direct Deposits will not need to be run).
You have another GL system that can pull in ASCII files. You can use one of the above formats, but you will most likely need a custom program to change the format to fit your general ledger system.
You enter GL transactions manually. You still need to run this option, so that Circulation can write off account credits.
Business Rules determine whether the ASCII file is created and which format should be used. In order to interface credits to Accounts Payable, accounts must have a vendor ID and a vendor company assigned. The vendor ID and company are used by the general ledger to identify the account. Vendor and company IDs are specified during account setup (see Account in the Setup Manual). Vendor IDs may also be imported into Circulation (see Vendor Import).
Note: Circulation will append apcheck.d
each time you run the Interface to AP. You should rename this file or move it to a different location to avoid interfacing duplicate transactions.
Select Interface to AP from the AP/Direct Deposit menu to display the Interface to AP window.
Click Add and complete the following fields.
COMPANY
setup
Enter the company for the accounts being interfaced.
BILL SOURCE
setup
Enter the bill source for the accounts being interfaced.
BALANCE MINIMUM
decimal (10)
Enter the minimum balance that an account must have in order to transfer it to Accounts Payable.
INVOICE DATE
date
Enter the date the invoices (credit transactions) should be created in AP. Only carrier credits up to and including this date will be interfaced.
AP CLEARING ACCOUNT
setup
Enter the AP clearing account number. This is the GL account that will be credited (Accounts Receivable will be debited).
INTERFACE TO AP
display
The format for the AP interface (as defined in Business Rules) is displayed here.
DUE DATE
TERMS CODE
LIABILITY ACCOUNT
BILLING RUN DATE
GL ACCOUNT
GL DEPARTMENT
PRODUCT
PROJECT
date open (2) open (12) date open (6) open (3) open (6) open (15)
These fields are active only if you interface account credit balances using an interface other than DTI Standard. This information is used by Compu-Share, PeopleSoft II, and other systems.
Click OK.
If you want to review the credits before running the interface, click Review (see Credit Balance Review for more information).
Click Continue to interface the account credits. An ASCII file will be created (if specified in Business Rules), and debit memos will be created in Circulation to charge the account for the amount interfaced to AP. An AP Interface Program report will then be displayed, listing the number of records processed and any errors that occurred during the process. For example, if the vendor ID or vendor company ID is blank for an account in Circulation, an error message informs you that the record cannot be interfaced.
After clicking OK in the Interface to AP window, you can click the Review button to review the credits interfaced to AP before running the interface.
The Credit Balance Review window allows you to modify or delete individual credits.
Click Reject All to reject the entire batch (nothing will be interfaced) or OK to interface the batch. If a batch is rejected or a credit is reduced, the remaining credits will be retained and can be interfaced at a later date.
The Vendor Export interfaces only vendor information for new accounts. If vendor information is modified for existing accounts, the information may need to be changed in the Accounts Payable system manually. This can be done using the Vendor Change Report, which lists all accounts that have had setup information modified on or after a cutoff date.
Note:
If any setup has been modified for an account, the account will be listed on the report, even if there was no change to vendor information. For example, if only the account’s contract date is modified, the account will still display on the report.
Select Vendor Change Report from the AP/Direct Deposit menu.
Select Add and enter a “from” date. All accounts modified on or after this date will appear on the report.
Indicate if you want to exclude billing changes. This checkbox allows the report to ignore changes in the Account Billing table. This will eliminate instances in which the only change is that account billing has been run. This checkbox is active only when the Business Rule, To which system should vendor information be interfaced? (Account Setup section), is set to “DTI Standard 2.”
Indicate if you want to export the data. If you enter “yes” in the Export Data field, a .CSV file containing the vendor change information will be exported.
Select Continue to generate the report.
Rather than managing account vendor information in your Accounts Payable system, it may be maintained in Circulation and then interfaced using this option. The Business Rule— To which system should vendor information be interfaced? (Account Setup section), determines the format of the export.
Select Vendor Export from the AP/Direct Deposit menu.
Select Add and enter a “from” date. All accounts added on or after this date with vendor information will be exported.
Select Continue to run the export. Vendor information for new accounts will be appended to the vendorexport.d
file in /dti/exchange/cm/secure
.
Circulation calculates the subscription term based on the rate code and payment amount. Suppose the following rate table was set up for a specific subscriber rate code:
Based on a subscriber’s payment amount and the rate code, Circulation calculates the subscription term and length. For example, suppose two subscribers with this rate code make payments of 45.00 and 116.00:
Subscriber #1 pays 45.00. Circulation displays the length and term as 3 months.
Subscriber #2 pays 116.00, Circulation figures the number of days based on 9 months (100.00) + 1 month (15.00) + 1 day (1.00). Whenever a rate term is not matched exactly, Circulation displays the term as “days”.
If the subscriber has a pending grace owed transaction, a message displays that grace is being paid off. This creates an odd amount payment, and the term’s length will be returned as days.
In some cases, subscribers deposit payments directly to a bank, and the bank sends payment information to the newspaper. Use this option to read these subscriber payments, known as lockbox payments, into Circulation. In order to be read, the file sent from the bank must be put in /dti/exchange/cm
. The file can be in the standard lockbox format (see ) or a user-defined format. If user-defined, the format must be set up in advance in File Map setup (see in the Setup Manual).
In addition to standard lockbox payments, charges for bonus days created by are also imported via Lockbox Processing.
Note:
Contact the Naviga Global Support Center in the early planning stages of lockbox processing as custom programs may need to be written to accommodate the format of the file coming from your bank.
Business Rules determine whether the lockbox scanline is verified against the scanline check digit, and whether the bank number should be verified (using the standard US banking system formula for bank numbers).
Select Lockbox Processing from the Subscriber Payments menu to display the Subscriber Lockbox Processing window.
Click Add and complete the following fields.
Click OK and then Continue to process the lockbox payments. The Subscriber Lockbox Processing report will be produced, listing the number of records that were processed and any errors that occurred.
If Read Option is set to “commit”, a suspended batch of subscriber payments will also be created. You must restart this batch of payments by selecting Batch Payments (see ) and entering the batch ID and header information (the payment records will then be processed when Payment Processing is run). During the commit process, the sublockbox.d
file will be renamed to sublockbox.[date].[batch].d
, where [date] is the lockbox payment date and [batch] is the batch ID. A processing report will also display, listing any errors that occurred during the process. If a subscriber ID in the lockbox file does not exist in the system, it must be resolved in Resolve Payments (see ).
Transaction Security is added to the "Auto Accept Batch" field so that it may be regulated at the user level to enable or disable access to the field.
If any Security is applied to the Security item, users who are part of the Security ID will have access to the “Auto Accept Batch” field, while users who are not part of the Security ID would not, and the field will be greyed out.
Use this option to enter subscriber payments that are received by the newspaper. These payments can only be from office pay subscribers; if a carrier collect subscriber makes a payment over the counter, the payment must be entered as an account payment (see ). If a payment is entered for a carrier collect subscriber using this option, Circulation will automatically change the subscriber to office pay.
Subscriber payments can be entered at any time. The steps involved in entering and processing subscriber payments are given below:
Select Batch Payments and enter a batch of subscriber payments (or enter payments individually in Customer Service). A batch is a group of payments entered a session; batches have IDs and control numbers for greater accuracy and organization. Payments entered in Customer Services (or iServices) are automatically added to their own batch.
You may Accept the batch of payments, or Suspend it. Suspended batches can be restarted at a later time (for instance, after the Payment Journal has been reviewed).
Print the to verify the accuracy of the payments entered.
When you have verified that the batch and payments are correct, select to process the subscriber payments. Expire dates will be extended, and general ledger entries made.
Note:
A Customer Service or iServices payment batch can only be selected in Batch Payments if there are no users currently accessing the batch in those modules. Once the batch is opened in Batch Payments, users in Customer Services or iServices will not be able to access it until it is accepted or suspended.
An occupant may pay for an entire group of subscriptions with one payment. For example, let’s say Benton College buys free subscriptions for all of its instructors. A single check for 1500.00 from the Dean’s Office might pay for 75 subscriptions. Circulation has the ability to enter and distribute group payments. So, the 1500.00 payment mentioned above can be tracked as a group payment that is split 75 ways. Of course, the payment could also be broken up and entered as 75 individual payments; but the Group Payment feature allows for better tracking and more efficient entry. The procedure for entering group payments is given below.
Note:
Business Rules determine whether all subscribers that have subscriptions billed to the occupant should be listed, or only office pay subscribers who have not made a payment for their last renewal. It also determines whether the payment is initially split evenly among all subscribers (“automatic”), or whether each subscriber begins with a zero amount (“manual”).
Group payments are entered along with regular payments in Batch Payments. Currently, group payments can only be entered in character Circulation (not in the Batch Payments option in Graphical Accounting). Rather than adding the payment by selecting Add, the Group option must be selected from the strip menu. The Group Subscriber Payments screen will display.
Select Add and enter the name, phone number, or subscription ID of the occupant making the group payment (in order to qualify for group payments, this occupant must be the bill-to occupant for at least two subscribers). Then enter the payment amount and other payment information.
The subscriptions billed to this occupant will be listed in the Group Subscriber Payment Distribution screen. Select Modify to enter or change the payment amount for an individual subscriber.
When the entire payment is accounted for, select Accept to accept the group payment and return to the Group Subscriber Payments screen. You can then enter more group payments, or select Accept again to return to the Batch Subscriber Payments screen. Each individual group subscriber will be listed, but marked with a “*GP” to indicate that the payment is part of a group.
With Auto Payments, we move from the account to the subscriber side of accounting. See .
Auto renew subscribers have their subscription renewed automatically—from a bank account, a credit card, or a PayPal account—at the end of their renewal period. The subscription continues to be renewed until they inform the paper otherwise. Hence, a normal renewal notice is not sent to auto renew subscribers (though an auto renew notification can be sent—see ). Auto renew subscribers have special auto renew terms which are set up by the newspaper. They are also assigned to auto renew billing groups. See Publication in the Setup Manual for more information.
During a new start, subscribers can be flagged as auto renew subscribers. They can also be transferred to auto renew status with a billing change. Bank account, credit card, or PayPal account information is entered for the customer at this time.
When you select this option, Auto Payments, Circulation automatically creates a suspended batch of credit card, bank draft, or PayPal payments for auto renew subscribers whose subscriptions will expire within a certain number of days (based on the auto renew terms). Auto renew information may also be exported to an ASCII file to produce statements.
You may print the Payment Journal to verify the payment entries included in this batch (see ).
To restart the batch created in Auto Payments, select Batch Payment and enter the batch name (see ). You can modify the auto renew payment entries before you Accept the batch. Once accepted, Circulation creates an ASCII file containing the auto renew information in your /dti/exchange/cm
directory. Credit card auto renews can be in various formats, as governed by Business Rules. Bank draft auto renews can also be in various formats, as determined by bank setup.
Bank draft files are usually sent to the newspaper’s bank. The newspaper has to further prepare the credit card file for the various credit card companies (outside of Circulation).
When is run, the batch is processed and the auto renew subscriptions in the batch are renewed (i.e., the subscribers’ expire dates are extended). The auto renew transactions are looked upon as subscriber payments.
We recommend that you print the Payment Journal again to verify the auto renew transactions.
Select Auto Payments from the Subscriber Payments menu to display the Automatic Subscription Payments window.
Click Add and complete the following fields.
Click OK and then Continue to process the auto renews. An Automatic Subscription Renewals report will be created, listing the number of subscriptions that were auto renewed and any errors that occurred in the process. Auto renew statements may also be exported (see below).
NavigaPay is a payment gateway wrapper that has been added for one-time and recurring payments. NavigaPay is an integrated payment hub for many vendors, such as Edgil Payway, Stripe, Braintree, etc. This feature has been added to the system to allow general request parameters to be sent to the selected payment vendor through the use of Naviga Pay.
Auto renew subscribers can be sent statements, similar to renewal notices, when their subscription automatically renews. To create the statement, auto renew information is automatically exported to an ASCII file when Auto Payments is run. The ASCII file can then be imported into word processing software to produce the actual statements.
The subscription is being renewed by Auto Payments.
The subscriber’s auto renew type (bank draft or credit card) is being exported, as governed by Business Rules.
The Send Statement flag was set to “y” in the subscriber’s start or billing change.
The file will be exported to /dti/exchange/cm
and be named autorenewsmmdd
, where mm
is the number of the month and dd
is the day.
The Batch Audit Journal shows subscriber payment batches entered within a date range that are currently unprocessed. This includes batches that have been suspended (payment processing skips over suspended batches) and unsuspended batches that are still unprocessed. Suspended auto renew and lockbox batches will also appear on this report.
You typically run this report before creating the at the end of the fiscal period, to ensure that all subscriber batches have been processed.
Select Batch Audit Journal from the Subscriber Payments menu to display the Subscriber Batch Audit Journal window.
Click Add and enter the dates for which to run the journal. All suspended batches entered on or between these dates will be included.
Click OK and then Continue to create the journal.
When subscriber payments are imported into Circulation from a lockbox file, some subscribers in the file might not have valid subscription IDs. When this happens, the batch can still be accepted and the payments processed. The invalid subscriptions will be assigned a subscription ID of zero, and those payments will not be processed.
Note:
Subscriber lockbox payments with an invalid subscriber ID will appear on the Subscriber Payment Journal with a subscriber ID of zero and a name of “Unassigned Payment”. The bank totals will also contain a separate total for unresolved payments.
Select Resolve Payments to resolve payments by assigning them to a valid subscriber. There is also a Resolve Payments report to aid in balancing the GL in cases where payments were made in a prior fiscal period but resolved in the current period (see ). In order to view or edit payments in Resolve Payments, the lockbox payment batch must first be accepted.
Select Subscriber Payments | Resolve Payments
to display the Resolve Payments screen.
Complete the following fields.
The unresolved payments that meet the criteria entered are displayed. Select Modify and enter the subscription ID on one or more payments. You can also modify the term and length for these payments.
When finished, press F4 and select Exit to exit to the main menu.
This option takes all subscriber payments that have been entered into the system (on or before the specified date) and applies them to subscriber accounts. This usually results in an extended expiration date for the subscriber. Payments in suspended batches are not processed. Payment processing should be run daily, before transaction processing is run.
Note:
You must update Unearned Revenue at the end of each fiscal period, before processing subscription payments belonging in the next fiscal period. See for more information. Also note that fiscal periods should be defined before payments are be processed—we recommend defining fiscal periods for at least one year in the future.
Select Payment Processing from the Subscriber Payments menu to display the Subscriber Payment Processing window.
Click Add.
Enter the product and date for processing the payments.
Click OK and then Continue to begin payment processing. All unsuspended payments and/or canceled payments entered on or before the transaction date are processed, and the new expiration date is assigned to the subscription. If a subscriber is changing from carrier collect to office pay, a billing change transaction is created. The new expiration date is created and, if applicable, appropriate back credits are given to the carrier/dealer when the billing change transaction is processed.
During Payment Processing, Circulation attempts to process payments for the date entered, along with any payments from earlier dates. Therefore, Circulation tries to process any problem payments every time Payment Processing is selected, until the payment processes successfully or is deleted.
After the processing is completed, a report is displayed listing general information about the processing and any errors that occurred. Any payments with errors should be corrected, and then this option should be run again to process them.
All subscriber payments entered within a date range appear on the Payment Journal, whether entered in Customer Services or Batch Payments, or created with the auto renew or lockbox features. Payment cancels and NSFs will also be included. Payments that have not yet been processed also appear on the Payment Journal.
Note:
For credit card payments, the credit card number will only appear on the report when being run by a user that has security to view credit card information (see in the Setup manual).
Likewise, bank numbers for bank draft auto renew subscribers will only appear if the report is run by a user that has security to view bank account information. If a batch of payments contains group payments, the individual payments in the group will be listed as normal, with a payment type of “G-PMT”.
The group payments themselves will be listed at the end of the report. The VaultID and Email Address of PayPal auto renew subscribers will only appear if the report is run by a user that has security to view PayPal private data.
The Subscriber Payment Journal should be printed before Payment Processing, to verify that the payments that have been entered are correct. It is also a good idea to print the journal after payment processing, to confirm that there were no processing errors.
The tax on the Activation and Printed Bill Fees for each subscriber will be shown in the Subscriber Payment Journal. An overview of fee tax collected by each tax authority and fee type is displayed at the end of the report.
Select Payment Journal from the Subscriber Payments menu to display the Subscriber Payment Journal window.
Click Add and complete the following fields.
Click OK and then Continue to create the report.
Premium days are bonus days such as holidays where the subscriber receives the paper on a day that is not normally a delivery day, or receives a special edition of the paper (see ). Premium days have special charges special charges associated with them, which are deducted from a premium day wallet rather than the subscriber’s balance.
When entering a payment for a subscriber, any premium day amounts included in a term will be part of the term amount purchased. The premium amount, however, is placed in the subscriber’s wallet rather than being used to buy days. For example, say a 4-week term is $20 and contains a $1 premium day, while a 13-week term is $50 and contains two $1 premium days. A $21 payment would be required for the 4-week term, with $1 being placed in the wallet. A $52 payment would be required to purchase a 13-week term, with $2 being placed in the wallet.
Note: For combo subscriptions, a separate wallet amount is tracked for each component publication with premium days.
Once the bonus day is published and delivered, the premium amount is deducted by the subscriber’s wallet by running Bonus Day Adjustment (see ) and importing the bonus day adjustment file in Lockbox Processing.
If no payment is made by the subscriber, premium day costs will still be subtracted from the wallet, and the wallet balance will be included in grace owed and grace paid amounts. A typical subscriber going into grace will have a zero wallet balance, and any premium days delivered while they were in grace will therefore create a negative wallet balance.
A subscriber’s premium day wallet cannot be adjusted manually by entering payment adjustments—it can only be adjusted by the bonus day adjustments, which use a payment adjustment code that has Update Wallet set to “y”, and certain subscriber transactions.
If a subscriber who paid for a premium day temp stops and does not receive the premium day paper, the money for the premium day will be removed from the wallet and be used to extend the expire date when the subscriber restarts. Likewise premium days missed between a move out and move in transaction will be deducted from the wallet and used to buy days. In the case where the restart or move in extends the new expire date out past another premium day, the wallet will be updated. Likewise when transactions such as delivery schedule changes, billing changes, transfers and complaints extend the expire date to cover a premium date, the premium amount will be included in the expire change. Wallet amounts can also be included in transfer out transactions.
In some cases a subscriber does not receive a purchased bonus day paper for reasons other than the transactions described above. For example, a bonus day could be defined and purchased, and then removed (or the premium amount could be changed after the payment is made). In this case the wallet amount not used for the premium day is considered an uncommitted amount. Uncommitted amounts from the subscriber’s wallet are added to payment amounts when the subscriber makes a payment, just as unallocated amounts in the subscriber’s balance are added.
Finds the subscriber’s current wallet total.
Calculates the number of premium days still scheduled before the subscription expire date.
Subtracts the scheduled premium days from the wallet total to determine the uncommitted amount.
For example, say a subscriber pays $1 for a premium day, and the premium day amount is changed later to .75 in Bonus Day Setup. When the bonus day occurs, .75 will be deducted from the wallet, leaving .25 uncommitted. That uncommitted amount will be added to the payment amount when buying the next subscription period.
Note:
Uncommitted wallet amounts will not be included in the payment amount when Auto Payments generates auto renew payments.
Use this option to enter subscriber payments in batches.
You also enter adjustments here. An adjustment is typically an amount paid for other than subscription purposes. A check for a promotional coffee mug, for instance, would be an adjustment. Adjustments can also be non-cash. An example of a non cash adjustment might be a subscriber who missed a week’s worth of papers, and so has the expire date adjusted an additional week.
Select Batch Payments from the Subscriber Payments menu in Graphical Accounting to display the Subscriber Payment Batch screen.
Before payments can be entered, defaults and batch information must be set for this batch of payments, in the Batch Entry panel. These fields are described below.
Click the OK button below the Batch Entry panel to accept the batch information.
You can now enter the payments, one at a time. Click the Add button in the Subscriber Batch Payments panel to enter a payment.
Enter payment information in the Subscriber Batch Payments fields, described in the table below.
If the payment is a check (based on the Pay Type field), the Check Info window opens. Enter the check number in the Check Number field. The bill-to subscriber name displays in the Holder Name field.
If this is a credit card payment, a window opens for the credit card number and other information—the fields in this window vary based on Business Rules, your selected credit card authorization vendor, and whether you are using the Hosted Order Page. See for more information. Note:
If you are using the character version of Batch Payments and the Hosted Order Page, use the Vaulting Service to obtain a vault ID for the credit card payment, and enter it in the Vault ID field. See for details.
If this is a bank draft payment, the Bank Draft Info window displays. Enter the bank routing number and account number here. Additional fields may also be required, based on your bank draft interface format.
If the payment includes an adjustment, the Adjustment window opens. One or more adjustments may be entered here (press F2 in the Code field to display a list of valid codes). You can set up some adjustment codes to credit the Cash Total (for cash adjustments) and others to credit the Adjustment Total (non cash adjustments). Be sure to select an appropriate code for your adjustment. Enter a minus sign with negative amounts. See in the Setup Manual for more information about adjustment codes.
Click the OK button to add the payment to the batch, or the Add Another button to add the payment and begin entering the next payment. (If you click OK and then decide to enter another payment, you can just click the Add button.) You can also modify or delete payments added to the batch (authorized credit card payments, however, cannot be deleted). The payment is listed in the Subscriber Batch Payments grid on the right side of the screen.
As you enter subscriber payments, the amount displayed in the Total field (above the Subscriber Batch Payments grid) changes. If you enter coupon and/or non cash adjustment amounts, those totals change also. When you finish entering payments for a batch, Total Cash and Control Cash should be equal. Otherwise, the batch is out of balance. The same is true of the coupon and adjustment totals.
After all payments have been entered, click the Accept button below the Batch Entry panel to enter the batch of payments into the database (the payments will be applied to subscriber accounts during ). If the totals for the payments do not match the control totals entered with the batch, you will be prompted to update the control totals. You may also suspend the batch by clicking the Suspend button. To reject the batch, click the Reject button (all of the payments will be lost).
If a payment batch is suspended, you can print the Payment Journal to verify payments, and restart it at a later time. To restart a suspended batch, go into Batch Payments and select the suspended batch in the Batch field (rather than entering a new batch ID). The batch will then display with its payments, and can be accepted.
If you accept a batch and later find that a payment was entered incorrectly, you must cancel the payment in Customer Service (see ) and then reenter it.
The Resolve Payments option, above, is used to resolve payments that were imported from a lockbox with an invalid subscriber ID. The Resolve Journal can be used to balance to the GL in cases where these payments were imported from lockbox in one fiscal period, and resolved in another. For example, a payment of 20.00 might be interfaced in September but not resolved until October. It would appear in the totals of the Payment Journal in September, but the GL entry would not appear until October.
Select Subscriber Payments | Resolve Journal
to display the Resolved Fiscal Overlap Payment Journal window.
Click Add and complete the following fields.
Click OK and then Continue to produce the report.
Circulation considers printing a renewal notice a transaction (this allows the system to distinguish subscribers who have received their 1st, 2nd, and 3rd renewal notices for a period, etc.). Select this option to reverse renewal notice transactions. This is a necessary step when errors occur during renewal notice printing.
Undoing renewal notices is not recommended if the renewal notice batch has already been sent to the printer.
You can also use this option to undo an eBill batch, if you e-mail electronic renewal notices via the Send eBill option.
When you undo renewals, the Printed Bill Fee is deleted along with the renewal transaction. Refer , and .
Select Undo Renewal Notices from the Subscriber menu to display the Undo Renewal Notices window.
Click Add and enter the product, run date, and other information about the undo process in the fields described in the table below.
Click OK and then Continue to undo the renewals.
Note: The 'Vindicia Capture'
feature is a licensed add-on. Please contact Naviga Support to license this feature.
Vindicia is a solution for recurring billing that rectifies failed payment transactions. Vindicia Retain is designed to handle billing for auto-renew credit card transactions that the client couldn't get from the application and won't try to get from the customer or subscriber again.
Using Vindicia Retain not only enables the capture of unsuccessful transactions, but it also offers subscribers an extended lifetime. Instead of a subscriber discontinuing service due to a failed transaction, Vindicia Retain may capture that transaction, enabling the site to continue billing for consecutive periods as if the site had successfully caught the transaction itself.
Basically, there are three parts to the Circulation-Vindicia integration.
Send Payments—Sending failed payment transactions to Vindicia.
Get Payments—Obtaining an update on the status of those payments from Vindicia.
Cancel or Refund Payments—to intimate Vindicia to stop attempting to capture if the subscriber stops, if a one-time payment is received, or if a billing change occurs in order to update auto renew information.
In character Circulation, select Vindicia Payments from the Accounting menu to display the Vindicia Payments Pull-out menu.
Business Rules define the maximum number of days to attempt transaction processing and the quantity of records sent or received from Vindicia.
What is the maximum number of days Vindicia Retain will try transaction processing? This BR specifies the number of days we will allow Vindicia to attempt a failed payment on their end. When this number of days has elapsed, we consider that the payment was not successfully captured by Vindicia and make the required system updates.
What is the limit for records in one file sent or received from Vindicia Retain?
This BR specifies the number of records we will get in a single file when we retrieve the payment records from Vindicia.
This is used to send information about unsuccessful payment transactions to Vindicia.
Go to Character Accounting > Vindicia Payments > Send Payments.
Select Add and enter the Cutoff Date. The system will choose all failed Auto Payment credit card records with payment dates up to this cutoff date.
Select Continue to send the payments to Vindicia.
After the records have been processed, Vindicia will return an acknowledgment, indicating whether the request was successful or had any errors. A typical acknowledgement response is as follows:
This is used to determine the status of the unsuccessful transaction records that we send to Vindicia in the Send payments functionality.
Vindicia will attempt to process the unsuccessful transactions for the number of days specified in the BR—What is the maximum number of days Vindicia Retain will try transaction processing? (Pymt Auth - Vindicia section) before providing the status of the transactions to our system.
When Vindicia makes a successful payment, the subscriber's suspended billing change transaction is deleted, and a payment transaction is created to indicate that the payment was successfully completed. If Vindicia is unable to process a successful payment for a record, the suspended billing change transaction for that subscriber is deleted, and the subscription will now be discontinued from AutoPay.
Note:
The suspended billing change transaction cannot be modified or deleted, and the options are disabled until the Vindicia Retain process is completed.
The billing change transaction can be deleted only if the status returned after the Vindicia Retain process is 'Failed', 'Cancelled', or 'Refunded'.
Go to Character Accounting > Vindicia Payments > Get Payments.
Select Add and complete the following fields.
Select Continue to fetch the status of the records from Vindicia.
After the records have been processed, Vindicia will return an acknowledgment, indicating whether the request was successful or had any errors. A typical fetch response is as follows:
This is used to send refunds or cancel responses to the payment requests that were sent to Vindicia.
If Vindicia processes the refund/cancel request before making a successful payment against a record, Vindicia will no longer attempt to make payment for the record and the status of the record will be Cancelled. However, if Vindicia processes a refund/cancel request after the payment against that record is successfully processed, the payment must be refunded by Vindicia, and the status of the record will be Refunded.
If a subscriber chooses to Permanently Stop a Subscription after submitting unsuccessful transactions to Vindicia, a refund/cancel request will be sent, which will either cancel the payment or stop the payment attempt.
Go to Character Accounting > Vindicia Payments > Cancel Payments.
Select Add and enter the Cutoff Date. The system will choose all failed Auto Payment credit card records with payment dates up to this cutoff date.
Select Continue to send cancel or refund request to Vindicia.
After the records have been processed, Vindicia will return an acknowledgment, indicating whether the request was successful or had any errors. A typical acknowledgement response is as follows:
When a transaction is processed in the application, NavigaPay Bank Draft payments will have the status “Settlement Pending”. The ACH Status Update Utility process is designed to fetch the details of the Bank Draft payments made and update them in the application accordingly. refer to .
In Graphical Accounting, select Subscriber Payments | ACH Status Update
.
Click Add and enter the Product and the Date Range.
Click OK and then Continue to update the status of the payment.
Once the payment has been processed by the vendors, the status will be updated accordingly. If a payment fails, a “Payment Decline” record is created.
The Vindicia Report includes all of the records that have been sent to Vindicia, as well as the current status and refund details as of the run-date.
The 'Totals By Status' section of the report is summarized based on the five statuses described below.
Failure. These are the records for which Vindicia has not been able to capture the payment. If the Vindicia process was not successfully completed, the default state is set to Failure.
Cancelled. If a Circ Customer Service activity occurs, such as the Subscriber making a payment, a billing change, or being Perm Stopped while Vindicia is trying to capture the payment, Vindicia will cancel any pending attempts, and the records will have the Cancelled status.
Refunded. If a Circ Customer Service activity occurs, such as the Subscriber making a payment, a billing change, or being Perm Stopped after Vindicia has been able to capture the payment, the records will have the Refunded status.
Captured. If Vindicia has been able to capture the payment successfully, the records will have the Captured Status.
Pending. The records for which Vindicia is attempting to capture the payment will have a Pending Status. This status will be shown in the report until the value set in the Business Rule— What is the maximum number of days Vindicia Retain will try transaction processing? ( section) has been reached.
Select the Vindicia Report from the Subscriber Payments menu to display the Vindicia Report window.
Select Add and complete the following fields.
Click OK and then Continue to produce the report.
Click the Wizard icon () to display the first card of the wizard, which is used to enter charge information.
(see Setup Manual) can be configured under:
Character Setup > System > Security > Transaction Security > AutoAccptBatch
Each individual payment will be treated by Circulation as a regular payment, except that users will not be able to cancel individual payments that are part of a group (the whole group payment must be canceled—see ). Group payments entered for a bill-to occupant can be viewed in the Show | Group Payments
option in Customer Service.
The statement contains more detailed information than an auto renew notice (see ), and is in a format similar to the Detailed Export 2 renewal notice format. A Business Rule in the Subscriber Payments section determines whether the export should contain credit card, bank draft, or all auto renew subscribers. Only subscribers who meet the following criteria will be exported:
Section: Setup > Rules > Business Rules > Sections >
1 Year
120.00
9 months
100.00
6 months
70.00
3 months
45.00
1 month
15.00
1 day
1.00
START DATE, END DATE
date
Enter the date range for fetching the status of the records sent to Vindicia.
PAGE SIZE
integer (3)
Enter the maximum number of records on one page to be fetched.
PAGE NUMBER
integer (7)
Enter the page number at which all created pages will be received. For example, if Vindicia has processed 740 records and the Page Size is set to 100, entering Page Number as 0 would return 8 files sequentially, with 100 records on each page from Page 0 through Page 6, and 40 records on Page 7.
This section guides the user through the menu options that are available under the Fiscal Close menu.
This section guides the user through the menu options that are available under the Fiscal Close - GL submenu.
Renewal notices are notices sent to current office pay subscribers from whom you have received at least one payment and whose expiration date is approaching.
Invoices are bills sent to new start and bill subscribers (subscribers who start immediately and pay for their subscription later, and are therefore initially in grace). For example, an office pay subscriber might start a subscription and, two weeks later, pay for three months. The invoice would be for three months, but the subscriber at that point would owe for only two weeks.
Renewal notices and invoices have the same format, and they are printed together using this option. Circulation will print renewals or invoices for subscribers:
Who were flagged for invoice or renewal when their new start was entered,
Who have the delivery type you specify,
Whose expire date minus the current date is less than the days required for a notice number (or invoice number), and
Whose notice number or invoice number is selected to print.
The “notice number” mentioned above corresponds to the number of renewals sent to this subscriber for payment; i.e., “1st notice”, “2nd notice”, or “3rd notice”. Each notice number should be set up to be sent a certain number of days before expire. The days can vary depending on the publication, delivery method and other factors. For details, see Publication in the Setup Manual.
eBill subscribers, who receive an electronic rather than printed renewal notice, can be managed in one of two ways:
They can be e-mailed a renewal notice (in HTML or text format) via the Send eBills option.
They can be exported to a file, either in a special eBill format, or in one of the standard renewal notice export formats, as defined by the Business Rules. Both eBill subscribers and/or “promotional eBills” (subscribers who are not on eBill but who are receiving a notice number specified in the Also Include Renewal Periods field for the eBill delivery method in Renewal Delivery Publ setup) can be included in this file, based on the Business Rule Which subscribers should be included in the ebill export file? The file can be used to generate and send electronic renewal notices outside of Circulation (for example, in PDF format).
Creating invoices and renewal notices with this option also creates subscription transaction records, such as “1st Renewal” or “1st Invoice”. These records are displayed in the Transactions portion of the Customer Service window. They tell Circulation the notice number for a subscriber. For example, to qualify for a 2nd renewal notice, a subscriber must have a “1st Renewal” transaction.
Notes:
Renewals will not be printed for temporarily stopped subscribers.
If subscribers have paid for grace days after their expire date, the grace paid days will be added to the expire date when determining whether the subscriber should be selected for renewals.
If you charge for bonus days using the “premium day” method (see Bonus Day Adjustment), subscription rates will include premium amounts for bonus days that occur within the term. In addition, if the Business Rule Should premium day detail be exported in renewals? is set to “Yes”, premium day information will be exported when using the Detailed Export 2 format or viewing dynamic renewal notices in iServices or Customer Service.
If you use PostWare and the Detailed Export or Detailed Export 2 format for renewal notices, and choose to include grace, the grace-owed records exported at the end of the renewal file will not be included in mail labels and associated mail reports. Only invoices and renewal notices will include grace owed.
Grace-owed records exported at the end of the renewal file will include all grace-owed amounts; not just those for the selected rate code.
Renewal notices can be viewed in HTML or PDF format in iServices Subscriber (see the iServices Subscriber Manual for details) and in Customer Service (see HTML (dynamic) renewal notices).
It is recommended that the Business Rule—Limit renewal payment terms to last paid term and rates with longer terms? (Subscriber Billing section), be set to Yes only if you are using weekly rate terms in the Subscriber Rate Code Setup. The system calculates a term depending on the number of days calculated for purchase (regardless of actual term, "1 month" etc.). As a result, even though there are always only seven days in a week, the length of a one-month term might differ from month to month, leading to certain terms disappearing for certain renewals.
Before processing renewal notices for the first time, verify that there is at least one notice number set up for both invoices and renewals for each delivery method. Also, verify that at least one subscriber rate term is set up to print on renewals and invoices.
Subscribers on home delivery routes will have their notices and invoices delivered by their carrier/dealer, if the route they are on is set up to deliver renewals (see Home Delivery Route in the Setup Manual) and their renewal delivery method has not been overridden. If carriers deliver the renewal notices and invoices, Circulation calculates delivery credits by using the number of renewal notices/invoices delivered by a carrier/dealer and the delivery credit rate. Credits are processed during account billing. In order to generate credits, an account rate for the specified product with a draw type of “TMC” must be defined.
The subscriber has chosen not to opt out of Print Bill fees.
The subscriber is not set up for AutoRenew or E-Billing.
Subscribers are not included by the Business Rule— "How many days should elapse before a subscriber is eligible to receive another printed bill fee?". This rule prevents another printed Bill Fee from being charged to a customer within a specified number of days. Since each renewal term may only have one printed bill fee, this rule will only apply if the specified number of days exceeds the end of the current renewal period.
The subscriber must not have an unpaid Printed Bill fee.
The subscriber is due for an invoice or renewal.
Note:
Once the renewal notices have been processed and the above criteria have been met, the customer will get a new renewal notice and be charged a new Printed Bill Fee. This will appear on the Customer Services | Transactions | Renewal Notice and Customer Services | Financial | Fees.
You should run this option frequently to give all of your subscribers enough time to send in payments before their expiration dates.
Print the Batch Audit Journal to verify there are no suspended subscriber payment batches.
If applicable, select Auto Payments to create a batch payments for subscribers with the automatic renewal option.
Select Payment Processing to verify that all subscriber payments have been processed.
Select Renewal Notices to print subscriber invoices/renewal notices. Verify that “Number of Errors” = 0 (as displayed on the last renewal notice). If there are any errors, select Utilities | System | Process Log Report
to print a list the errors. You may select Undo Renewal Notices, correct the problems and, when error-free, print the renewal notices again by selecting Renewal Notices.
Note:
If you export renewal notices, the errors sent to the process log will be listed in the export file. See Renewal Notice Export Formats.
Information printed on the renewal notice or invoice includes:
Subscriber name and address
Bill-to name and address
Subscriber ID, or account number
Renewal periods and rates. If the subscriber was given a quote, only the quoted period and rate may be printed (see Price Quotes).
Messages (see below)
Expiration date. The expiration date will not be printed on start and bill invoices (the expire date on these invoices is the day the subscription begins)
Route, if applicable
Publication name (optional, based on Business Rules)
User-defined general message, if desired
The total number of renewals printed is displayed on the last renewal notice
Note:
If you export renewal notices, a recap will be included that shows the number of bills generated by delivery method, the notice numbers, and a total number of bills processed. It will also list the errors sent to the process log, rather than displaying the number of errors. See Renewal Notice Export Formats.
Four types of messages can be printed on renewal notices, as shown below. Since some renewal notice forms (see the table that follows) cannot accommodate all messages, the message printing order is as shown.
Tax messages (if applicable for the subscription).
Renewal messages (defined by selecting Setup | Business | Publication | Specifics | Renewal Periods
). These may contain one or two lines of information.
Rate messages (defined by selecting Setup | Accounting | Subscription Rates | Rate Code
).
General messages (as entered in this option).
Post Card and Old Post Card
There is room to print two lines of messages; for example, one taxing authority (if applicable) and only one line of the Renewal message. If the subscription has a purchase order number, that number is printed instead of the Renewal message. If the subscription is not subject to tax, one line of the Renewal message and the Rate message or General message may be printed.
Mailer
There is room to print three lines of messages. If the subscription is taxable, up to two lines of Tax messages and one line of the Renewal message will be printed. If the subscription is taxable in one tax authority, one Tax message and up to two lines of the Renewal message will be printed (or, if only one line of the Renewal message is set up, that line and the Rate message or General message may be printed).
Envelope
There is room to print two lines of messages. It follows the hierarchy shown above; i.e., two lines of Tax messages are printed, if applicable, or two lines of the Renewal message are printed (if two are set up), and so on.
Canadian Mailer
There is room to print eight lines of messages: up to three Tax messages, two lines of Renewal messages, the Rate message, and the General message.
Tax Envelope and Two Tax
Same as Mailer, above.
Other Envelope
There is room to print two lines of messages. It follows the hierarchy shown above; i.e., two lines of Tax messages will be printed, if applicable, or two lines of the Renewal message will be printed (if two are set up), and so on.
Other Mailer
There is room to print five lines of messages. It follows the hierarchy shown above.
Instead of printing renewal notices, you may choose (in Business Rules) an export format that places renewal notice information in an ASCII file in /dti/exchange/cm
. The file name will be renewalsmmdd
, where mm and dd stand for the month and the day. Five export formats are available (see Renewal Notice Export Formats in Appendix B).
Export. This is a fixed length format
Export Delimited. This format contains the same information as the export format, but is pipe (|) delimited rather than fixed length.
Detailed Export. This pipe delimited format contains additional information, such as the last renewal date and grace owed amounts.
Detailed Export 2. This format is similar to the Detailed Export, but contains some different information, such as payment history and Fees-related fields Note: Fees-related fields are only displayed if FeeManagement add-on is activated.
eBill. If renewal notices are run for all renewal types or the renewal type of “eBill”, subscribers who have a renewal delivery method of “eBill” will not appear on the renewal notices (or be in the renewal notice export, if an export is used). Instead, these subscribers will be exported to a separate ASCII file, in a special eBill format. If the carrier or mail renewal delivery methods are set up to export subscribers picked for renewal or invoice to the eBill file (as defined in Renewal Delivery Publication setup), they will be exported to the eBill file in addition to printing on the renewal notices.
Business Rules determine the following things for invoices and renewal notices: the format that should be used (postcard, mailer, etc.), whether the publication name, Zip PostNet barcode, and carrier route should be printed, whether renewals should be printed for subscriptions automatically switched to carrier collect, how many days an office pay subscriber must be temp stopped before the last invoice or renewal is resent, whether term amounts are based on the subscriber’s expire date or last payment effective date, and (if using expire date) whether the expire date should be adjusted for temp stopped periods.
There are also some Postalsoft considerations: whether renewals should be sorted via Presort, if so what the job file name is and how long sort information should be kept, and whether Presort or Circulation should provide carrier route information on the notices.
For eBill renewal notices, Business Rules determine whether eBill e-mails are sent directly from Circulation, which subscribers should be exported to the eBill file, and the format of the eBill file.
Select Renewal Notices from the Subscriber menu to display the Renewal Notices window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the product for which to print subscriber renewal notices. Enter “*” to multi-select products.
RUN DATE
date
Enter the date for which renewal notices should be run. This date, along with the subscriber’s expiration date, determines whether a renewal is printed for the subscriber.
NOTICE NUMBER
predefined
Enter the renewal or invoice notice number (1st, 2nd, etc.) to include. Enter “*” to multi-select notice numbers.
PRINT INVOICES
yes/no
Indicate whether invoices should be printed.
PRINT RENEWALS
yes/no
Indicate whether renewal notices should be printed.
INCLUDE PENDING RATE CHANGES
yes/no
If subscription-length pricing is being used, select this checkbox if you want pending rate changes to be considered when valuing subscription terms.
SEPARATE BY GROUP
yes/no
If your renewal notice format is an export, indicate whether renewal notices should be exported to separate files, based on renewal group. See Renewal Group in the Setup Manual for more information.
NUMBER OF PAYMENTS
integer (3)
Subscribers can be selected for renewal notices based upon how many payments they have sent in since their start. Enter a payment range (between 0 and 999) here.
GENERAL MESSAGE
open (30)
Optionally, enter a general message to print on all renewal notices/invoices.
PRINT BY ROUTE
yes/no
Indicate whether the renewal notices/invoices for subscribers on home delivery routes should be printed in route order. Select this checkbox if carriers deliver renewal notices for their routes.
If you do not select it, all renewal notices print in Zip code order (or, if sorted by Presort, in Standard A class order). You cannot print by route if you entered “*” in Product.
GENERATE CREDITS
yes/no
If you selected Print By Route, the Print By Route window will open with this and the following three fields. Indicate whether to automatically generate credits for carriers for delivery of renewal notices. You may print a report of renewal notices delivered by your carriers for delivery credit by selecting Reports | Route | Delivery Credit.
DELIVERY DATE
date
If you selected Print By Route, enter the date that the carriers will be given the notices for delivery. A Business Rule (Subscriber Billing section) determines the days of the week that are valid for route delivery.
DEPARTURE
setup
If you are printing by route, indicate the truck departure order that should be used (routes print by truck, and trucks print in departure order sequence).
TRUCK SEQUENCE
setup
If you are printing by route, indicate the truck sequence that should be used (this determines with what truck and in what order within the truck a route will print).
PRINT GRACE OWED
yes/no
This and the following field are open for entry only if you are exporting renewal information in the Detailed Export or Detailed Export 2 formats (a Business Rules consideration). Indicate whether the export should include subscribers (active or stopped) that owe grace. If you select this checkbox, the ASCII file created by the detail export will also contain subscribers that owe grace, along with their grace owed amount.
TYPE
predefined
If you selected print grace owed, indicate which grace owed subscribers should be included in the export file: those that renewed their subscription at least once, were start-and-bill and never renewed their subscription, or both.
PRINT REBILLS
yes/no
REASON
setup
If you are printing rebills, enter the rebill reason code.
ALL RATE CODES RATE CODE
yes/no setup
Indicate whether renewal notices should be printed for all rate codes and, if not, enter the rate code for which to print renewals (enter “*” to multi-select). Renewals will be printed only for subscribers assigned to the rate codes entered here.
ALL START REASONS START REASON
yes/no setup
Indicate whether renewal notices should be printed for all reason codes and, if not, enter the reason code for which to print renewals (enter “*” to multi-select). Renewals will be printed only for subscribers whose start had one of the reason codes entered here.
ALL RENEWAL TYPES
yes/no predefined
Indicate whether renewal notices should be printed for all renewal delivery methods (carrier, mail, and eBill). If this field is set to “n”, a specific renewal delivery method can be entered in Type. If a specific renewal type is entered, only subscribers with that renewal delivery method will be selected for renewals.
ALL DELIVERY TYPES
yes/no setup
Indicate whether renewal notices should be printed for all delivery types (all route types, plus mail). If you enter “n” here, a Delivery Types window will open, allowing you to select specific route types and/or mail (renewal notices will be printed only for the delivery types selected).
Click OK and then Continue to print the renewal notices. See Printing Forms for information about printing forms. Renewal notices and invoices are printed in the following order: mail with barcode, mail without barcode, and then route delivered renewal notices and invoices. If you use PostWare for renewal notices, the mail notices will be printed in Standard A sort order. The format of the notices (postcard, mailer, etc.) is determined by Business Rules. If one of the “export” formats is being used, renewal notice information will be placed in an ASCII file in /dti/exchange/cm
.
If you are using PostWare to sort your renewal notices Standard A class mailing order (a Business Rules consideration), PostWare will produce different reports according to how your job file is set up. Among reports that could be produced are: a Mail Sort Listing, Form 3602 (statement of mailing), Job Summary, and Qualification Report. These reports will be saved to spool and can be printed from the View/Print Utility.
Once invoices/renewal notices have printed, verify that “Number of Errors” = 0 (as displayed on the last renewal notice). If there are any errors, select Utilities | System | Process Log to print the errors and then make any corrections.
If you have run renewal notices and/or invoices for a day and need to run them again, select Undo Renewal Notices so that another renewal notice will be generated for subscribers who have already received one.
To give a brief example of how subscribers are selected for renewal notices, let’s assume that renewal notices are run for 12/3 for notice numbers 1 and 2, and the renewal and invoice notice periods are as follows:
1
20
1
0
2
5
2
-8
3
-10
Assume further that our newspaper publishes every day and has the following office pay, carrier-delivered subscribers:
Ella started a subscription on Nov. 30 and has not received an invoice.
Renee started a subscription on Nov. 27 and received an invoice on Nov. 28.
Conrad’s subscription expires Jan. 15.
Julia’s subscription expires Dec. 12, and she has not received a renewal notice.
Abdul’s subscription expires Dec. 5, and he has not received a renewal notice.
Heidi’s subscription expired Nov. 22, and she has received two renewal notices.
Ella would qualify for invoice 1. Renee has already received invoice 1 and cannot yet receive invoice 2 (no invoice prints). Conrad’s expire date is too far out for a renewal. Julia will receive renewal 1 and Abdul renewal 2. Heidi would qualify for renewal 3, but we are not printing renewal 3 in this run.
Some newspapers print invoices for their carrier collect subscribers, which they give to their carriers. The invoice tells the carrier how much to collect from the subscriber for a particular period. This is useful, for example, in cases where the newspaper wants to extend promotions to carrier collect subscribers, or has a number of carrier collect subscriber rates. CC Invoice Export is the option that produces carrier collect invoices. It writes invoice information to an export file, which can then be imported into a word processor or other system for invoice printing.
Carrier collect invoices can be created for all carrier collect subscribers on routes in the area selected.
Carrier collect invoices can be created for carrier collect subscribers who have had certain activity before or after a particular date (the billing date) within the period—this is known as “in between” billing. The reason code of a transaction determines whether it should cause a carrier collect invoice to be generated.
In order to print carrier collect invoices, the Business Rule, Are carrier collect invoices produced? (Account Finance section), must be set to “y”. The Print CC Invoices field in Route Setup (see Home Delivery Route in the Setup Manual) determines whether invoices will be created for a particular route. And the next field, Bill When, determines whether the invoices are created in arrears or advance. These two terms are also used in account billing, and have a similar meaning:
If a route prints in arrears, the amount on the carrier collect invoice is based on the subscriber’s draw in the current period. This will be the actual draw for days published, and projected draw for unpublished days (not pending draw—unprocessed transactions will not be taken into account).
If the route prints in advance, the amount on the carrier collect invoice is based on the subscriber’s projected draw in the next period.
If the actual draw turns out to be different from the projected draw (for example, because of a delivery schedule change or temporary stop), there will not be an adjustment on the next period’s invoice—it is up to the carrier to modify the amount collected accordingly.
When it generates invoices, CC Invoice Export will bill carrier collect subscribers for a certain billing period. The amount owed that appears on the invoice will be calculated using the subscriber’s rate, in the same way an office pay subscriber is rated (see About Subscriber Rating for more information).
Billing periods for carrier collect invoices are independent from account billing periods and must be set up in advance, using the CC Invoice Calendar (see CC Invoice Calendar in the Setup Manual). The billing dates themselves must also be set up, on the CC Run Date Calendar (see CC Run Date Calendar in the Setup Manual). Only one billing date should be set up per billing period.
The billing date is entered when CC Invoice Export is run, and indicates the billing period that should be used. The billing date also defines what transactions are picked up when “in between” billings are done—our next topic of discussion.
As mentioned before, CC Invoice Export can be run to include all carrier collect subscribers (the regular billing) or subscribers with transactions before or after the billing date, based on the reason code of the transaction (“in between” billing). If running an “in between” billing, you can specify whether transactions with transaction dates before the bill date (Before Batch) or after the bill date (After Batch) should be considered.
Whether or not a transaction causes an invoice to be generated is governed by the reason code. Two fields in Reason Code setup, Generate Arrears and Generate Advance, control this (see Reason in the Setup Manual). Generate Arrears is used when CC Invoice Export is run for arrears; Generate Advance is used when this option is run for advance. Each field has four possible settings:
Before Batch. Transactions with this reason code will cause an invoice to be created if the transaction date is before the bill date and CC Invoices is run with the Before Batch option. The bill will reflect the amount owed from the start of the billing period to the transaction date.
After Batch. Transactions with this reason code will cause an invoice to be created if the transaction date is after the bill date and CC Invoices is run with the After Batch option. The bill will reflect the amount owed from the transaction date to the end of the billing period or (if running for advance) the end of the next billing period.
Both. Transactions with this reason code will cause an invoice created in both the “before” and “after” scenarios described above.
Never. Transactions with this reason code will never cause an invoice to be generated.
Different transaction types will typically have different settings. For example, it makes sense to set a stop reason code to “Before Batch”. Then, if CC Invoices is run before the bill date, an invoice will be printed for the stopped subscriber, and the carrier can collect sooner (before the subscriber moves out of town, for example). In contrast, it makes more sense to set up start reason codes to “After Batch”—this insures that start transactions occurring after the bill date will produce invoices for that period (if you wait until the next bill date, the amount owed in the current period will not be included in the invoice). You may want other transactions, such as reroutes, set to “Both”.
Three common scenarios for “in between” billing are given in the following illustration.
To generate carrier collect invoices, follow the procedure below:
Select CC Invoice Export from the Subscriber menu to display the Carrier Collect Invoice Export window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the product for which you are generating carrier collect invoices.
RUN DATE
date
Enter the billing date for the invoices. This date must be set up in advance on the CC Run Date Calendar. Note that you do not have to be generating the invoices on this date—the run date is simply used to indicate the billing period to use and determine what transactions to include, if this is an “in between” billing.
COLLECTION TYPE
predefined
Indicate whether invoices should be created for routes that bill in arrears (for current billing period) or advance (for the next billing period).
RUN TYPE
predefined
Indicate whether invoices should be created for all subscribers (regular billing), or only subscribers with transactions that have transaction dates before the billing date (before batch) or after the billing date (after batch) and applicable reason codes.
START DATE, END DATE
date
If this is an “in between” billing (i.e., “before batch” or “after batch” are entered in the field above), enter the date range for the billing. Only transactions with transaction dates within this date range will be considered.
SELECTION AREA
predefined
Indicate the area for which you are generating carrier collect invoices. You may pick certain routes, include all routes in an area, region, distribution zone or district, or include all routes.
SELECTION
setup
Enter an area, region, zone, district or route, or enter * to multi-select areas. If you entered “all” above, this field will not open.
Click OK and then Continue to generate the invoices.
When processing is complete, the file ccinvddmm
(where d
=day and m
=month) will be created in /dti/exchange/cm
. See Appendix B for the format of this file. The Carrier Collect Invoice Export report will be produced, listing information about the process.
READ OPTION
predefined
Indicate whether to edit or commit this information to the database. Enter “commit” to create payment records. If you enter “edit” the file will be read but only an error report will be created. We recommend that you run Lockbox Processing in “edit” mode at least once to verify that there are no potential errors. The 7 fields below will be active only if you are committing information.
BANK
setup
Enter the ID of the bank where the payments were deposited.
SOURCE
setup
Enter the source code for the payments, such as “bank”.
REASON
setup
Enter the reason code for the payments, such as “renew”.
DEFAULT DATE
date
You may enter a default payment date for the lockbox payments. When interfacing payments, Lockbox Processing will use the following hierarchy when assigning the payment date:
1) Use the payment date interfaced, if provided (the standard subscriber lockbox does not contain the payment date).
2) Use the default date entered here.
3) Use the batch date interfaced, if provided (the standard subscriber lockbox does have a batch date).
4) Use the file date interfaced, if provided.
5) Use the current date.
CREATE AUTORENEW
yes/no
Indicate whether a payment should switch a subscriber to auto renew, if bank draft or credit card information is interfaced. If this checkbox is selected and a bank number and account number are interfaced, a billing change will be created to switch the subscriber to bank draft auto renew.
Similarly, if a credit card number and expiration date are interfaced, a billing change will switch the subscriber to credit card auto renew. The auto renew term will be picked based on the payment amount (if the amount does not match an auto renew term, no auto renew will be created). The subscriber’s rate will be changed to an auto renew rate, and any tip or payment adjustment interfaced with the payment will be included in subsequent auto renews.
Note that the standard subscriber lockbox format does not contain credit card or bank draft info. Also note that billing changes will be created when the payment processes (in Payment Processing). The billing changes will then be processed in Transaction Processing.
AUTO ACCEPT BATCH
yes/no
Indicate if you want all open batches to be accepted automatically.
Transaction Security controls whether the default answer can be changed. See "Auto Accept Batch" Transaction Security.
BATCH
open (10)
Enter a batch ID for these payments.
DESCRIPTION
open (30)
Enter a description of this batch.
BPAY FILE
yes/no
Indicate if this file is from the BPay form of online banking.
INPUT FILE FORMAT
setup
Enter the format of the lockbox file being interfaced. Enter “Sublockbox” if you are using the standard lockbox format. Or, enter a user-defined format that has been set up in FILE MAP.
BPAY FILE
yes/no
Indicate if this file is from the BPay form of online banking.
INPUT FILE NAME
open (16)
Enter the file name of the lockbox file in the /dti/exchange/cm
directory. The default file name for the standard lockbox format is “sublockbox.d”; default file names for other formats can be defined in File Map. The default can be changed.
PRODUCT
setup
Enter the product for which to create automatic renewals. Enter “*” to multi-select products.
RUN DATE
date
Enter the date for which to create this batch. Circulation will include credit card (or bank draft) auto renew subscribers whose expire date minus this date is less than or equal to the number specified in Auto Renew Terms setup.
RENEWAL TYPE
predefined
Specify what kind of automatic renewals should be included in this batch: credit card, bank draft, prenotification, or PayPal.
If you select prenotification, Circulation will pull all bank draft auto renew subscriptions that have started within the date range specified. A file named “notifyMMDDYY-nnn” (where “MMDDYY” represents the month, date and year of the export, respectively, and “nnn” represents an incrementing sequence number that distinguishes files exported on the same day) is created in /dti/exchange/cm listing the new auto renew subscriber information but with a zero amount.
The Pre-Notification feature will do the verification in real-time through NavigaPay instead of transmitting the data to the bank. See Note below.
BILLING GROUP
setup
If this batch is for bank draft or prenotification, enter the auto renew billing group to include, or enter “*” to multi-select groups. Only subscribers assigned to the billing groups selected can be auto renewed. See Publication in the Setup Manual for more information about auto renew billing groups.
BANK
setup
If this batch is for bank drafts or prenotifications, enter the bank where auto renew money will be deposited into the newspaper’s account.
SHORT DESCRIPTION
open (10)
If this is a bank draft or prenotification batch, enter some descriptive information (such as “Tribune”) for the subscriber’s bank statement.
START DATE, END DATE
date
If this batch is for processing prenotifications, specify the date range during which new bank draft auto renew subscribers should be selected.
INCLUDE PENDING RATE CHANGES
yes/no
If subscription-length pricing is being used, select this checkbox if you want pending rate changes to be considered when valuing subscription terms.
AUTO ACCEPT BATCH
yes/no
Indicate if you want all open batches to be accepted automatically. Transaction Security controls whether the default answer can be changed.
BATCH
open (10)
Assign a name to this batch of auto renews (this name will be used when the batch is restarted in payment entry).
DESCRIPTION
open (30)
Enter a description of this batch.
ALL RESOLVED
yes/no
Indicate whether to list all unresolved payments, or only payments made in a specific lockbox batch.
BATCH
setup
If resolving payments for a specific lockbox batch, enter the batch name here.
BANK
setup
Enter the bank for which to resolve lockbox payments, or enter “*” to multi-select banks.
CUTOFF DATE
date
If All Resolved is set to “y”, enter a cutoff date for resolving payments. Only unresolved payments interfaced on or before this publishing date will be listed.
PRODUCT
setup
Enter the product for which to process payments.
SELECTION DATE
date
Enter the selection date for which to process payments. All unsuspended payments entered on or before this date will be processed (including lockbox and auto renew payments). When subscriber payments are processed, they are posted to general ledger accounts. Make sure that all payments entered for a month are processed with a process date within the same month so the GL Interface Journal matches the Payment Journal.
BATCH
setup
If you are running the journal for a particular payment batch, enter the batch name here. If you are running the journal for a date range, enter “*”.
PRODUCT
setup
Enter the product for which to print subscriber payments.
CASH PAYMENTS
yes/no
Indicate whether cash payments should be included in the Payment Journal.
BANK DRAFT PAYMENTS
yes/no
Indicate whether bank draft payments should be included in the Payment Journal.
BPAY PAYMENTS
yes/no
Indicate whether BPay payments should be included in the Payment Journal.
CREDIT CARD PAYMENTS
yes/no
Indicate whether credit card payments should be included in the Payment Journal.
PAYPAL PAYMENTS
yes/no
Indicate whether PayPal Express Checkout payments should be included in the Payment Journal.
BANK
setup
Enter the bank for which subscriber payments should be listed, or enter a “*” to multi-select banks. The bank displays on the Payment Journal for any auto renew bank draft payments.
PRINT PRIVATE DATA
yes/no
Indicate whether private banking and credit card information (such as account numbers and credit card numbers) should be displayed on the journal.
DISPLAY OPTION
predefined
If you answered “yes” in Print Private Data, indicate here whether private credit card and banking information should be masked (only the last four digits shown) or displayed in full. Note that users without the proper security will not be able to see private data even if “full” is selected.
START DATE, END DATE
date
If you are running the journal for a date range, enter the dates here. All payments entered (or created) on or between these dates will be included in the journal. If the payments you enter during a month are also processed in the same month, you may want to print the Payment Journal for the month and balance it with the GL Interface Journal.
SORT OPTION
predefined
Indicate if this report should sort by subscriber name, payment sequence, date, or operator.
PROCESS STATUS
predefined
Indicate if this report should include only processed payments, only unprocessed payments, or both.
EXPORT
yes/no
Select this checkbox if you want to create an export file.
FILE FORMAT
setup
Select the file map to use for this export. A file map must be set up previously.
FILE NAME
open
You can accept the default file name or modify it.
BATCH
open (10)
Create an ID for the batch of subscriber payments you are entering. If you are restarting a suspended batch (such as an auto renew batch), enter the batch ID here and the remaining batch information will default.
DESCRIPTION
open (30)
Enter a description of this batch.
BATCH DATE
date
Enter the date of this batch. This date is used as the default payment date, which may be overridden.
CASH CONTROL
decimal (11)
Enter the control total for this batch of payments. “Cash” includes the subscription payments, any tips, and cash adjustments, but does not include coupons or non-cash adjustments.
COUPON CONTROL
decimal (11)
Enter the total of coupon amount for this batch of payments.
ADJUSTMENT CONTROL
decimal (11)
Enter the net total of non cash adjustment amounts included in these payments. If this is a negative number, enter a minus sign with the amount.
BANK
setup
Select the bank into which this batch of payments will be deposited, or accept the default.
SHORT DESCRIPTION
open (10)
If you are restarting an auto renew bank draft batch, the short description that will print on the bank statement defaults (see Auto Payments). You may keep this default, or enter another short description.
SOURCE, REASON
setup setup
Select a source and reason code for these payments, or accept the defaults.
TYPE
display
This field displays the type of payment being entered (single or group). Currently, only single payments can be entered via the graphical interface. Group payments can be entered in character Circulation—see Entering Group Payments.
SUBSCRIBER
setup
Enter the subscriber’s last name (or part of their last name), telephone number or subscription ID. Circulation will search for an exact match. If multiple matches are found, they are displayed in a scrollable window so you can select the correct subscriber. If the subscriber has more than one subscription, the subscription information is displayed in the same way.
PAY DATE
date
The date entered on the Batch Payments screen displays. You may change this date. Note that payments cannot be entered for a fiscal period that has been closed (see Close Period (Subscriber) for more information).
EFFECTIVE
date
Enter the date on which the payment should go into effect. This field is not active for office pay subscribers. For subscribers changing from carrier collect to office pay, enter the start date for the office pay status. If this date is before the last publishing date, back credit is issued to the carrier/dealer(s) using the draw adjustment code established in Business Rules. Business Rules determine how far back to search for this customer’s previous expiration date. If found, that date is displayed. If not, the next publishing date is displayed (and can be changed).
PAY TYPE
predefined
Indicate whether the payment is a check, cash, credit card or bank draft payment. If “Bank Draft,” “Check,” or “Credit Card” are selected, a window will open for additional information, as described in the steps below.
AMOUNT
decimal (6)
Enter the amount of the payment (without tip, coupon or adjustment). The amount may default from the previous payment (as determined by Business Rules); the default can be overridden.
COUPON
decimal (6)
Enter the coupon amount, if any, with this payment. The amount entered is added to the payment amount to determine the length of the subscription.
TIP
decimal (6)
Enter the amount of the tip, if any, included with this payment. If the subscription is delivered by multiple carriers, the tip will be distributed evenly between them or based on the number of days delivered, as governed by Business Rules. For example, a 5.00 tip for a subscription delivered by a Sunday carrier and a Mon-Sat carrier could be divided evenly at 2.50 per carrier, or by days at 0.71 (Sunday) and 4.29 (Mon-Sat). Press F5 to override these amounts and enter your own tip distribution. A Charge Code (see Publication in the Setup Manual) and a Charge GL Account (see CR GL Account in the Setup Manual) must exist for tips before processing.
ADJUSTMENT
yes/no
Check this field if the subscriber payment includes an adjustment. If so, the Adjustment window (shown below) will open for entry of the adjustment code and amount.
TERM, LENGTH
display or integer
The subscription term and length (based on the rate code and the amount of the payment) are displayed. If an exact match is found, the exact term and length display. If not, Circulation calculates the number of days that the amount of payment can buy. You may override these terms and lengths. Note: If a subscription term contains bonus days with premiums (Paying for Premium Days), the total premium amount is included in the term cost and will be placed in the subscriber’s premium day wallet.
REMARKS
open
Enter any remarks that pertain to this payment. Remarks appear in the Payment Journal and are retained in history.
PRODUCT
setup
Enter the product for which to list resolved payments, or enter “*” to multi-select products.
BANK
setup
Enter the bank for which to list resolved payments, or enter “*” to multi-select banks.
CREDIT CARD PAYMENTS
-
This field is not active.
PRIOR PERIOD CUTOFF DATE
date
Enter a cutoff date for listing resolved payments. Only resolved payments interfaced in a period ending on or before this date will be listed.
RESOLUTION START DATE, RESOLUTION END DATE
date
Enter the resolution date range. Only payments resolved with in this date range will be listed in the report.
SORT OPTION
predefined
Indicate whether the report should sort by subscriber name, payment sequence, date, or operator.
PRODUCT
setup
Enter the product for which to reverse renewal notice transactions.
RUN DATE
date
Enter the date for which renewal notices should be reversed for this product.
UNDO PRINTED BILLS, UNDO EBILLS
yes/no
If an eBill batch exists for this product and date, these fields are active. Check Undo Printed Bills to undo renewal transactions for non-eBill subscribers. Check Undo eBills to undo an eBill batch.
EBILL BATCH
setup
If Undo eBills is checked, enter the eBill batch that should be deleted.
An eBill batch can be undone as long as e-mails have not yet been sent for it.
DELETE GRACE EXPORT TRANSACTIONS
yes/no
If grace owed transactions were exported with the renewal information (Print Grace Owed was checked in Renewal Notices) this field opens.
Flag the checkbox if grace owed export transactions should be removed with the renewal transactions.
START DATE, END DATE
date
Enter the date range for fetching the status of the records sent to Vindicia.
EXPORT DETAIL
yes/no
Indicate if you want to export the Vindicia Report.
FILE NAME
open (25)
Enter the name of the file to be exported.
The Send eBills option can be used to e-mail electronic renewal notices to eBill subscribers who qualify for renewal. The e-mail can be in HTML or text format, and Circulation uses templates to determine the e-mail content. If you do not support the eBill renewal delivery method, or if your eBill renewal notices are generated outside of Circulation, you do not need to use this option.
Below is an example of an eBill e-mail. Note that only one amount appears on the notice—the amount of the subscriber’s current rate term. If the subscriber makes a payment in iServices by clicking the Make a Payment link, all of the qualifying rate terms will display.
In order to e-mail renewal notices to your eBill subscribers, you must:
Have the Business Rule— Should E-bill emails be sent from Circulation to E-bill subscribers? (Subscriber Billing section) set to “Yes.”
Have the Business Rule— Which mode should Send eBills be run in? (Email section) set to “Live.”
Customize the eBill e-mail templates to reflect your publication’s look and feel. Different templates can be utilized, based on the notice number and whether you are sending renewals or invoices. See E-mail Templates for information on customizing these templates.
Run Send eBills in test mode, as described in “Testing eBill e-mails” below.
Run Renewal Notices, which creates an eBill batch as part of the process. Send eBills is run for a particular eBill batch. Once an eBill batch is created, it can be deleted by Undo Renewal Notices, as long as the e-mails have not been sent.
See FAQ #115 for more information about eBill renewal notices.
Follow the procedure below to send eBill e-mails.
Select Send eBills from the Subscriber menu to display the Send eBills window.
Specify the product and run date for the eBills, and then select the eBill batch (only unsent eBill batches for that product and date can be selected).
Check Send Emails to actually send the e-mails. If left unchecked, no e-mails will be sent, but the processing report will display.
Note:
If the Business Rule— Which mode should Send eBills be run in? is set to “Test,” e-mails will not be sent even if Send Emails is checked. Instead, a window will display prompting for the number of test e-mails to send, the test e-mail address, and whether or not the notices in the batch should be marked as sent.
Select OK and then Continue to run the Send eBill process. When complete, a processing report will display, showing processing messages and listing accounts selected for eBill e-mails.
If e-mails are sent, they will be in HTML or text format using the e-mail template matching the bill type (invoice versus renewal notice) and number. The e-mail “from” address, name, and BCC address will be based on Business Rules. The subject will by default be “Bill now available.” However, that text is stored in a resource message and can be modified using Circulation’s Translation feature.
Once the e-mail is sent for a subscriber, it will be flagged as sent, so that the eBill e-mail cannot be sent again.
Before sending eBill e-mails in a live environment, Newscycle recommends carrying out a testing program, as outlined below.
Copy the renewal notice e-mail templates to your custom template folder and modify them to meet your publication’s look and feel.
Set the Business Rule— Should E-bill emails be sent from Circulation to E-bill subscribers? to “Yes” and Which mode should Send eBills be run in? to “Test.”
Find some test subscribers with a renewal delivery method of “eBill” who are due to receive their renewal notices or invoice.
Run Renewal Notices with “eBill” selected for the Renewal Type.
Run Send eBills with the Send Emails checkbox flagged. You will be prompted for testing information (the number of subscribers to test and test e-mail address, such as your own e-mail address).
Confirm that the correct number of eBill renewal notices were e-mailed to the test address, and that the format and content are correct. Be sure to check all of the links in the e-mail, and view the e-mail with different e-mail clients (such as Outlook and Gmail).
A newspaper may wish to export available refunds created in Circulation for use by another software program. For example, the export could be used to create letters to customers with an available refund. This option, Avail Refund Export, will export available refunds to an ASCII file in the /dti/exchange/cm
directory. Available refunds can be exported based on the date of the available refund and the refund amount. Once a subscriber’s available refund is exported, they will have a RefundExprt transaction, which will prevent the available refund from being exported again.
Select Avail Refund Export from the Subscriber menu to display the Available Refund Export window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the product for which to export available refunds.
START DATE, END DATE
date
Enter a date range for the export. Available refunds created within this date range will be included in the export based on this date range.
RUN TYPE
predefined
Indicate whether refunds that are over or under the limit entered below should be exported.
REFUND LIMIT
decimal (7)
Enter a refund limit. Available refunds over or under this limit (depending on what is entered in Run Type) will be exported. To export all refunds, set Run Type to “over” and enter zero here.
ALL STATES STATE
yes/no setup
Enter the state or states to include, or select all states.
FILE NAME
open (15)
Enter a file name. Available refunds will be exported to this file in the /dti/exchange/cm directory.
PRINT DETAIL
yes/no
Indicate whether the processing report should list the available refunds exported.
Click OK and then Continue to export the available refunds. The available refunds will be exported to the file name specified; see Appendix B for the format. A processing report will list the available refunds exported (if Print Detail was selected) as well as totals.
A refund may be available to subscribers who are permanently stopped (the amount would be the remainder of their subscription). The subscribers, however, may never claim this refund, and after a certain number of days (defined in Business Rules) the publication can “write off” this refund. Business Rules determine how many days a refund may be kept available.
When you select this option, Circulation finds all refunds that can be written off, based on the number of days a subscriber refund should be maintained as available. For example, if the number of days is “180”, only refund amounts that have been maintained as available for longer than 180 days will be written off. A report will be created as part of the process, and refund writeoff information may be exported to an ASCII file in the /dti/exchange/cm
directory (see Appendix B).
Select Refund Writeoff from the Subscriber menu to display the Refund Writeoff Report window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the product for which to write off available refund amounts.
CUTOFF DATE
date
Enter the cutoff date for writing off refunds. Any available refund whose transaction date plus the writeoff days from Business Rules is on or before the cutoff date will be written off. For example, if the writeoff days is 30 and the available refund transaction date is September 15, the cutoff date must be on or after October 15 in order to write off the refund.
ACTIVE SUBSCRIBERS
yes/no
Indicate whether refunds should be written off for active subscribers. If this checkbox is not selected, refunds will be written off only for inactive subscribers.
RUN TYPE
predefined
Specify whether refunds for amounts over or under a certain amount should be written off, or both.
ALL STATES STATE
yes/no setup
Select the state or states to include, or select All States.
WRITEOFF LIMIT
decimal (10)
If Run Type is “over” or “under”, enter the refund amount limit here. For example, if RUN TYPE is “over” and Writeoff Limit is 20.00, only available refunds of over 20.00 will be written off. If a refund writeoff limit has been entered in Publication Setup (see Publication in the Setup Manual), it will be displayed here and cannot be changed.
WRITEOFF
yes/no
Indicate whether to write off available refund amounts. Print the Refund Writeoff Report to review the items that will be written off before selecting this checkbox.
G/L TRAN DATE
date
If transactions should be written off (i.e., WRITEOFF is selected), enter the general ledger date for these writeoff transactions.
SOURCE
setup
Enter a source code for this writeoff, such as “accntg”.
REASON
setup
Enter a reason code for this writeoff, such as “old”.
EXPORT, FILE NAME
yes/no, open (15)
If refund writeoff information should be exported to an ASCII file, select Export and enter additional information in the Export Header Information panel. Then, in file name, enter the file name.
Click OK and then Continue to proceed with the writeoff. As part of the writeoff process, the Refund Written Off report will be created, listing subscribers who have had available refunds written off. Once they have been written off, the “refund available” transactions change to “refund writeoff” (RefundWOFF) in the subscribers’ transaction history window.
Some newspapers send notices to subscribers in grace, informing them of the grace amounts they owe. This can be done using this option to export a list of grace-owed subscribers and amounts to an ASCII file. This file can then be imported into another application (such as a word processor) to print the actual bills.
Business Rules determine the minimum grace-owed amount that will be included in the export. Subscribers whose grace owed is below this minimum will not be included.
Select Grace Owed Export from the Subscriber menu to display the Grace Owed Export window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the product whose grace owed information should be exported. Enter “*” to multi-select products.
RUN DATE
date
Enter the date on which to base the export. Grace owed amounts will be selected and exported as of this date.
GRACE OWED TYPE
predefined
Indicate whether Circulation should export only start & bill subscribers (subscribers who have not made a payment), only renewal subscribers, or both.
FILE FORMAT
setup
Select the file map to use for this export. A file map must be set up previously.
FILE NAME
open
You can accept the default file name or modify it.
Click OK and then Continue to run the export. The ASCII file will be named gracemmddyyyy-sss
(where “mm
” and “dd
” are the month and day, “yyyy
” is the year, and “sss
” is a sequence number) and will be located in /dti/exchange/cm
(see Appendix B for the file format). Exporting grace creates grace export transactions for the subscribers included.
Use this option to enter refunds for subscribers. You can enter a refund for any subscriber (based on Business Rules), but a warning will appear unless the subscriber has an available refund, which means the subscriber has a stop transaction with a balance.
For a list of subscribers with available refunds, print the Available Refunds Report.
Business Rules determine the amount by which a refund may vary from the refund amount due (if the subscriber has an available refund) and how many days a refund may be kept available. Business Rules also determine whether refunds are interfaced with SBS (DTI Standard format), Compu-Share, Dunn and Bradstreet, Great Plains, JD Edwards, Lawson, or PeopleSoft software systems and, if so, whether different vendor information should be supplied for each subscriber.
Note:
You will not be allowed to modify or delete a refund batch if it contains credit card refunds that have already been authorized (i.e., through real-time credit card authorization in Customer Service).
Select Batch Refunds from the Subscriber menu to display the Subscriber Refund Batch screen.
Enter batch default information in the fields on this screen.
BATCH
open (10)
Enter a name for this batch of refunds.
DESCRIPTION
open (30)
Enter a description for the batch.
REFUND DATE
date
Enter the date these refunds should be applied to the general ledger. This will be the GL transaction date.
SOURCE
setup
Enter a source code for the refunds. This is the party that originated the refund.
REASON
setup
Enter a reason code for the refunds. The code indicates why the refund has been given.
SELECTION OPTION
predefined
To make refund entry more efficient, the system can automatically add subscribers with available refunds to the batch. In this field, indicate whether to automatically include all subscribers with available refunds, or only those subscribers who have requested a refund as part of their stop. Select entry here if no refunds should be automatically added.
PRODUCT
setup
If you entered “all” or “requested” in Selection Option, this and the following three fields will open. Indicate the product for which available refunds should be automatically added to this refund batch.
REFUND TYPE
predefined
Indicate whether this batch may contain cash refunds, credit card refunds, bank draft refunds, or all.
BANK
setup
If the refund type is “bank draft”, enter the bank to which these refunds will be sent.
SHORT DESCRIPTION
open (10)
If the refund type is “bank draft”, enter a short description (e.g., “refund”) for the subscriber’s bank statement.
CUTOFF TYPE, CUTOFF AMOUNT
predefined
Refunds can be automatically included based on the amount of the refund. In Cutoff Type, indicate whether refunds should be included based on whether they are over or under the amount, which you then enter in Cutoff Amount.
CUTOFF DATE
date
Refunds are automatically added based on their available refund date. Only available refunds created before the date in Cutoff Date will be automatically added to the batch.
TOTAL CASH TOTAL
integer (7) decimal (11)
These two fields will open only if Selection Option is set to “manual”. Indicate how many refunds you will be entering and the total cash amount of the refunds.
OVERRIDE CC FILE NAME
y/n
This field and the next are active only when interfacing credit card refunds to ICVerify. If you use ICVerify and want to override the default credit card file name, enter “y” here, and the file name in cc file name. The file will be saved in the secure directory. If you enter “n”, the default file name of ccrefund.d will be used.
CC FILE NAME
open (30)
If applicable, enter a name for the ICVerify credit card file. The default is the batch ID.
Select Accept to accept the batch defaults.
The refund entry screen will display next.
Depending on what was entered in Selection Option, some subscriber refunds may already be added to the batch. If not, enter refunds for each subscriber, one at a time; you may also need to delete some refunds if they were added by the system but you do not wish to give a refund to the subscriber. The following describes the columns on this screen.
SUBSCRIBER
setup
Enter the subscriber’s name, telephone number, or subscription ID. If more than one matching subscriber exists, a window opens so you can select the correct one. If no refund is due, a warning appears.
REFUND TYPE
predefined
Indicate whether this refund should be applied to a bank draft, credit card, or cash. If the refund is to a bank draft, a Bank Draft window will open so that you can enter the bank number, account number, and authorization number. If the refund is to a credit card, a Credit Card window will open so that you can enter the card number, expiration date, and authorization number.
NAME
display
The subscriber name is displayed.
AMOUNT
decimal (7)
W/OFF?
yes/no
If the amount being refunded is less than the available refund, entering “yes” here will write off the entire balance.
PRODUCT
display
The product name is displayed.
ADDRESS
yes/no
If the refund should be mailed to an address other than the customer’s delivery address, set this field to “y” and enter the refund name and address in the window that opens.
When you have entered all refunds, press F4 and select Accept. You may also Suspend the batch and come back to it at a later time. If you interface the refunds to SBS, PeopleSoft, Compu-Share or Lawson, additional fields for vendor information will open up after you Accept the batch of refunds. Depending on how Business Rules are set up, you may be prompted for vendor information for each subscriber in the batch individually, or only once (with the same vendor information used for all subscribers).
If the total number or amount of refunds entered does not match the total number or amount entered for the batch, you must either modify the refund information or the batch totals.
After they are entered in Circulation, the refunds should be transferred to Accounts Payable in the general ledger, so that refund checks can be issued. This can be done manually by printing the Refund Journal and entering the refunds into Accounts Payable.
If you interface refunds to another application (as determined by the Business Rule— To which system should refunds be automatically interfaced?), an ASCII file will be created for the refunds. This file will be named aprefund.d
and be located in /dti/exchange/cm/secure
. If the subscriber payment was via credit card, the refund will instead be exported to a special credit card file, ccrefund.d
. See Appendix B for the refund file format.
If credit cards are exported in the Edgil format, credit card refunds will be exported to the file edgilrefcc[pub].mmddyyyy[x]
, where [pub] is the publication ID, [mmddyyyy] is the month, day and year, and [x] is a sequence number. The file will be in the Edgil credit card payment format (see Appendix B), but the transaction code is “CR” (for credit).
In the case of SBS and PeopleSoft, a vendor file, apvendref.d
, will also be created in the same directory. This file contains the vendor information and can be used to create vendor IDs and vendor company IDs in your general ledger system. Information in all files is appended, not written over; therefore when you read these files into your general ledger system you should remove them from /dti/exchange/cm
. The format for the vendor file is the same format used with carrier credit transfers to Accounts Payable (see Appendix B). If you use PeopleSoft, no vendor file is created.
Refunds can be entered for combo subscriptions, using one of the component publications of the combo.
If a combo with a balance is perm stopped, available refunds are created for each component publication, and these in turn can be accepted as individual refunds by Batch Refunds. However, as long as the combo refunds are in the same refund batch, they are interfaced as a single refund. This means, for example, that a subscriber’s credit card will only be credited with one amount.
If manual refunds (refunds for subscribers that have no available refund) are entered for subscribers with active combo subscriptions, the manual refund will reduce the balance of all component products, and be interfaced as a single refund. If the combo is perm stopped, the refund will be only for the individual component product, and each product’s refund will be interfaced separately.
If a combo has pending payments, cancel payments, or transfer transactions, manual refunds will not be processed but will be placed in a separate refund batch with a batch name that starts with “RB.” Once the transactions are processed the “RB” batch can be accepted and the refund transactions will be created. If some, but not all, of the component products in the combo have unprocessed billing change, combo change, or expire transactions, or if the expire dates of the component products are out of sync, refunds will likewise be put in the “RB” batch.
When accepting an “RB” batch, if some refunds in the batch still have the pending transactions or out of sync expire dates described above, they will be moved to a new “RB” batch and not be processed. If none of the refunds in the batch can be processed, the user will not be allowed to accept the batch.
Note:
This option should be used only by sites that use batch files to authorize payments. If your site uses real-time payment authorization or stores credit-card information off-site, you should not use this option.
Credit card payments are typically sent to a credit card company via specialized credit card processing software. The credit card company then sends back an authorization number, or else declines the payment. A similar process is used with bank drafts. Pymt Authorization allows declines and authorization numbers for credit card and bank draft payments to be interfaced from another system via an ASCII file. If payments are interfaced with an authorization number, the number will be updated in the payment record. If there is no authorization number (i.e., the payment is declined), a Payment Decline transaction will be created.
A standard file format currently exists for credit card cancels (see Appendix B). If you wish to authorize credit card payments with this option, or authorize/cancel bank draft payments, you will need to set up a user-defined file format via File Map using the Payment Authorization usage (see Appendix B) or use a third-party, licensed interface. This same format can then be used for both credit card cancels and payment authorizations.
Select Pymt Authorization from the Subscriber Payments menu to display the Cancel Subscriber Payment Authorization window.
Click Add and complete the following fields.
INPUT FILE FORMAT
setup
Enter the file format that you will be importing payment authorizations with. User-defined formats must be set up in advance in File Map. The standard credit card cancel format is “SubCancelCC”.
INPUT FILE
open (30)
Enter the file name in the /dti/exchange/cm
directory. This will default from File Map.
READ OPTION
predefined
Indicate whether to commit or edit the credit card payments in the ASCII file. If you choose “Commit”, cancel payment transactions will be created (for declines) and payment authorization numbers will be populated (for authorizations). If you choose “Edit”, only the processing report will be created (you can then look the report over for errors before committing).
BATCH DESCRIPTION
open (10) open (30)
If the field above is set to “commit”, enter an ID and description for the batch of subscriber payment cancellations that will be created by this process.
CANCEL DATE
date
Type the date on which you are entering this batch. The current date defaults.
EXPORT, EXPORT FILE
yes/no open (30)
Indicate whether payment declines should be exported to an ASCII file, and if so, the file name. Only declines (not authorizations) will be exported. See Appendix B for the export file format.
Click OK and then Continue to begin processing. After processing is complete, a report lists the payments processed and any errors that occurred. This report is similar in format to the Cancel Credit Card Payment report.
The Refund Journal lists all subscribers who have been paid refund amounts within a specified date range or in a specified batch. Subscribers who have available refunds but no refund payment transaction do not show up on the report. The Refund Journal will, however, include subscribers in suspended refund payment batches.
Select Refund Journal from the Subscriber menu to display the Subscriber Refund Journal window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the product for which to list subscriber refunds.
REPORT TYPE
predefined
Indicate whether you want the report to print for a batch, an entry date range, or a transaction date range.
BATCH
open (10)
If you are printing the journal for a specific batch, enter the batch name here.
START DATE, END DATE
date
If you are printing the journal for an entry or transaction date range, enter the date range here. Print a monthly Subscriber Refund Journal to balance with the General Ledger report.
REFUND TYPE
predefined
Indicate whether bank draft refunds, cash refunds, credit card refunds, manual refunds, PayPal refunds, or all should be listed in the journal.
SORT OPTION
predefined
Indicate if you want the report sorted by subscriber name, account, refund sequence, or operator.
SUSPENDED ONLY
yes/no
Select this checkbox to include only suspended batches in the report; do not select it if you want to include all batches.
BILL TO ADDRESS
yes/no
Indicate whether the subscriber’s bill-to address should appear on the report along with their delivery address, if the two are different.
EXPORT
yes/no
Select this checkbox if you want to create an export file.
FILE FORMAT
setup
Select the file map to use for this export. A file map must be set up previously.
FILE NAME
open
You can accept the default file name or modify it.
Click OK and then Continue to produce the report.
When you run the Auto Notice Export, Circulation creates an ASCII file of subscribers with subscriptions that expire within a certain number of days (defined in Setup—see Publication in the Setup Manual). This file can then be incorporated into a form letter using your word processor. See Auto Notice Export Format for the formats.
When it searches for subscribers who should receive an auto-renew notice, Circulation will use three values: the run date that you specify, the expiration date for the subscriber, and the number of notice days specified in setup. If a subscriber has already had an auto-renew notice for this expiration date, that subscriber will not be selected.
If the expire date minus the run date is less than or equal to the notice days, the subscriber will be selected for an auto-renew notice:
Subscriber Expiration Date - Run Date <= x Where x = number days from Auto Renew Term
For example, if the run date is 12/15, and auto-renew notices are generated 4 days before the expiration date, an auto-renew credit card subscriber with an expire date of 12/18 would be selected (18 - 15 <= 4). So would a subscriber with an expire date of 12/12, provided a notice had not already been sent (12 - 15 <=4). A subscriber with an expiration date of 12/21, however, would not be selected (21 - 15 > 4).
Any unprocessed payment, auto-renew, or transfer-in transactions may push the expire date beyond the run date.
An auto-notice transaction has been sent since the last auto renew and a message will be sent to the log file for any skipped subscribers.
Select Auto Notice Export from the Subscriber menu to display the Auto Renew Notice Export window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the publication for which you will send auto-renew notices.
RUN DATE
date
Enter the date on which the notices will be printed. This field defaults to the current date.
RENEWAL TYPE
predefined
Indicate whether you want to select subscribers who pay by Bank Draft, Credit Card, PayPal, or All. If you select All, all types of auto-renew subscribers will be selected.
NOTICE TYPE
predefined
Indicate if this export should include only Trial End, Auto-Renew, or both notices.
Trial End — returns a list of auto-renew subscriptions that have a Trial active on them)
Auto-Renew — returns regular auto-renew subscriptions, and
Both — returns a combination of the two subscriptions mentioned above.
BILLING GROUP
setup
Select the auto-renew billing group from which you want to select subscribers.
INCLUDE PENDING RATE CHANGES
yes/no
If subscription-length pricing is being used, select this checkbox if you want pending rate changes to be considered when valuing subscription terms.
PRINT RATE CHANGE ONLY
yes/no
Indicate if the export should include only those subscribers whose next auto-renew will be at a different rate.
PRINT BY ROUTE
yes/no
Indicate if the notices should be exported in route order. This is helpful if the notices will be delivered by carriers. If you do not export the notices by route, they will exported in mail sort order (by Zip code, street, and house number).
GENERATE CREDITS
yes/no
If the notices will be delivered by carriers, indicate whether carriers should receive Targeted Marketing credits for the delivery. You must have a TM rate defined for your product in order to do this (see Account Rates in the Setup Manual).
DELIVERY DATE
date
If the notices will be delivered, enter the delivery date.
USE FILE MAP
yes/no
Select this checkbox if you want to create an export file.
FILE FORMAT
setup
Select the file map to use for this export. A file map must be set up previously.
FILE NAME
open
You can accept the default file name or modify it.
Select Continue to create the file. As part of the process, a report will be created listing any errors that occurred during processing, and other information. An auto-renew transaction will be created for the subscription.
Fiscal periods may be “closed”, meaning that payments and cancel payments can no longer be entered for the closed period. By closing fiscal periods, it will be easier to balance Circulation reports to the general ledger.
This option allows you to close a fiscal period for account payment-related activity for a company/bill source combination. The Close Period option on the Fiscal Close - Sub menu allows you to close a fiscal period for subscriber activity (see Close Period (Subscriber)). Closing a period is optional, but it will prevent the back-dating of account payments across fiscal periods. It functions similarly to the Subscriber Fiscal Close option.
The Close Period option affects the following account payment-related options in Circulation:
Batch Payments—When entering a batch of payments, if a payment is prior to the most recent fiscal close date, the following message will appear: “Enter date after fiscal period close of [date] for company [company ID] bill source [bill source ID]”.
Lockbox Payments—A message will appear on the processing report if a payment has a date prior to the fiscal close date.
Cancel Payments—If a cancel payment is entered with a date prior to the fiscal close date, they system will automatically change the date to one day after the fiscal close date.
Account Billing—A warning will be displayed if an account billing is selected for a company/bill source combination that has not been closed for the period.
Other options on the Fiscal Close - Carr menu are standard Accounting and Reporting options that have been duplicated here for convenience.
Note: Suspended and unprocessed batches will prevent you from closing the fiscal period.
Once a period is closed, payments and cancel payments can no longer be entered for the period.
Select Close Period from the Fiscal Close - Acct menu to display the Account Fiscal Close screen.
Select Add and complete the following fields.
COMPANY
setup
Enter the company ID.
BILL SOURCE
setup
Enter the bill source ID.
PREVIOUS DATE
display
The previous fiscal close date is displayed.
CLOSE DATE
date
Enter the fiscal period close date.
Select Continue to close the fiscal period.
Your publication may have a grace period for subscribers who have passed their expire date without any new payments. For a certain number of grace days, then, the subscriber is receiving “free” papers. If they later send in a payment, the cost of these days (the “grace owed” amount) may be deducted from the payment (depending on Business Rules). For example, if a customer paid for three months of the Daily Bulletin, but had two weeks of grace, the subscription would only last for two and a half months.
Another situation arises when a customer in grace does not end up sending in a payment—they become permanently stopped after being in grace a specified number of days. At some point this grace amount must be “written off”—that is, the amount must be transferred from Subscription Accounts Receivables to Bad Debt in the general ledger.
Use this option to write off grace. Grace can be written off in the GL, in Customer Service, or in both places. For example, you might want to write off grace in the GL for fiscal reporting reasons but retain it in Customer Service in case the subscriber later sends a payment (allowing the grace owed to be paid).
The number of days subscribers stay in grace before they are stopped, and the number of days that must elapse before a grace owed amount can be written off, are tied to the subscriber’s credit status. All grace amounts where the grace end date plus the number of days specified in Setup is less than or equal to the cutoff date, will be written off.
Note:
Grace will not be written off for subscribers who have pending (unprocessed) payments.
Select Grace Writeoff from the Subscriber menu to display the Grace Writeoff Report window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the product for which Grace Owed transactions should be written off, or enter “*” to multi-select products.
CUTOFF DATE
date
Enter the cutoff date on which the writeoff selection should be based.
ACTIVE SUBSCRIBERS
yes/no
Indicate whether grace should be written off for active subscribers. If this checkbox is not selected, grace will be written off only for inactive subscribers.
SEPARATE WRITEOFF
yes/no
Indicate whether grace should be written off separately for Customer Service or the GL. If this checkbox is not selected, grace will be written off in both places.
SELECTION TYPE
predefined
You can choose to write grace off only in the GL, in which case the grace owed amount would still appear for the customer and be deducted from payments in Circulation. If so, enter General Ledger here. If, conversely, grace should be written off in Circulation but not in the GL, enter Customer Services. If grace should be written off in both places, enter “*” (note, however, that grace owed will only be written off for Customer Service if the grace period has ended). This field will only be active if Separate Writeoff, above, is selected.
WRITEOFF
yes/no
Indicate whether grace owed transactions should be written off. You may want to run this option initially without Writeoff selected to see which grace owed amounts will be written off.
G/L TRAN DATE
date
If transactions should be written off (i.e., Writeoff is selected), enter the general ledger date for the writeoff transaction.
SOURCE
setup
If grace will be written off, indicate the party that originated the writeoff (for example, “DM”).
REASON
setup
If grace will be written off, indicate a reason for the writeoff.
CHANGE CREDIT STATUS
yes/no
Indicate whether to change the credit status of subscribers whose grace is written off. Circulation will change the credit status to the Stop Credit Status setting of the subscriber’s current credit status, as defined in Credit Status setup (see the Setup Manual).
IS WRITEOFF NOW UNPAID
yes/no
When this checkbox is selected, in addition to performing the usual grace writeoff processing, a suspended batch of draw adjustments will be created to change the draw from “paid” to “unpaid” for AAM purposes. The name of the batch will be “GW” followed by the GL Tran Date entered (yymmdd format) followed by a four-digit sequence number. This checkbox is active when: • The Active Subscribers checkbox is not selected • The Selection Type is * (all) or Customer Services • The Writeoff checkbox is selected • Transaction Security, GraceWOffUnpaid, is activated
Click OK and then Continue to proceed with the grace writeoffs. The Grace Writeoff Report will be produced as part of this process. When Grace Owed has been written off, the Grace Owed transaction changes to Grace Writeoff in the subscriber’s transaction history window.
Fiscal periods may be “closed”, meaning that subscriber payments, refunds and auto renews can no longer be entered for the closed period. By closing fiscal periods, it will be easier to balance Circulation reports to the general ledger. Running Fiscal Close is optional.
Payments, including payments entered in Customer Service and Batch Payments, as well as payments imported via lockbox or Telemarketing Import
Cancel payments and NSFs
Auto renews
Refunds and refund writeoffs
Grace owed transactions and grace writeoffs
In order to close a fiscal period, all payment and refund batches for the period must be accepted, and payment processing must be run up to the last day of the period.
Fiscal periods are closed using the Close Period option, located on the Fiscal Close - Sub menu. Other than Close Period and Holding Acct Setup, the options on this menu are standard options duplicated here for convenience.
Once a period is closed, payments, auto renews, refunds and grace owed cannot be entered for the period.
Select Close Period from the Fiscal Close - Sub menu to display the Fiscal Close Date window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the product ID for which you are closing the fiscal period, or enter “*” and multi-select products.
PREVIOUS DATE
display
The last fiscal close date is displayed here.
CLOSE DATE
date
Enter the last date of the fiscal period that you are closing. Note that this date is not validated against the fiscal calendar.
CHANGE TRAN DATES
yes/no
Select this checkbox if you want to change the transaction date on all unprocessed payment transactions to the fiscal close date entered, plus one day.
Click OK and then Continue to close the fiscal period. Once the fiscal period is closed, payments, refunds, etc. can no longer be entered for that period.
Some states allow a subscription’s delivery cost to be exempted from taxes (see Trans Exclusion for more information). Newspapers that take advantage of this exemption may be required to inform subscribers of their delivery cost. Most office pay subscribers can receive this information via their invoice or renewal notice (transportation cost is included in the renewal export formats—see Appendix B). For the remaining subscribers, a special notice must be sent. This option, Trans Cost Export, exports delivery cost information to an ASCII file, which can be used to create the notices.
Note:
The Transportation Cost Export is part of the Taxing add-on feature. Contact the Naviga Global Support Center if you wish to purchase the Taxing add-on.
The Transportation Cost Export will include the following subscribers:
Auto renew subscribers who have auto renewed within the date range entered.
New office pay subscribers who have sent in a payment within the date range entered, but have not yet received an invoice.
All carrier collect subscribers who were active within the date range. In order to do this, the carriers must be credited for the carrier collect draw (the credit amount should be the tax on the transportation cost).
All subscribers (such as newspaper employees) assigned to a certain rate code.
Note: Subscribers who are tax exempt will not be included in the export.
As part of the export, a TM product set up to credit carriers for delivery of the notices can be processed.
Select Trans Cost Export from the Subscriber menu to display the Trans Cost Export window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the product for which to export delivery costs.
START DATE, END DATE
date
Enter a date range for the export. Subscribers will be included in the export based on this date range.
RATE CODE
setup
Enter the rate code used for newspaper employees. Subscribers with this rate code will be included in the export. Leave this field blank if employees should not be specifically included.
UPDATE TM
yes/no
Indicate whether a TM product should be processed as part of the export.
TM PRODUCT, DELIVERY DATE
setup date
If UPDATE TM is selected, enter the ID of the TM product that should be processed for delivery credits. This TM product must be set up in advance and should be flagged for delivery credits. Also enter the delivery date for the notices—the TM delivery credits will be based on this date.
Click OK and then Continue to run the export. Delivery cost information will be exported to the file /dti/exchange/cm/TCEXPORT
(see Appendix B for the file format).
Circulation’s GL Interface Journal can be used to enter Circulation GL transactions manually into the general ledger system. However, some sites prefer to interface GL information automatically, via an ASCII file. This option, Export GL, exports GL transactions to a file in the /dti/exchange/cm
directory. This file contains information from all programs that interface to the GL, including Account Billing Close, Subscriber Payment Processing, and Unearned Revenue. Information is appended, not written over; therefore, when you read this file into your general ledger system you should remove it from /dti/exchange/cm
. See Appendix B for the file format.
Transactions can be exported by Export GL as often as you wish, and for any date range. Once transactions are exported, the records are marked as posted in Circulation, so that they will not be exported again. A Business Rule— Should general ledger transactions with a zero amount be exported? (General section) determines whether GL transactions that have zero amounts are exported.
Export GL is located on the Fiscal Close - GL menu. The GL Interface Journal and Audit GL Journal are also duplicated here for convenience.
Select Export GL from the Fiscal Close - GL menu to display the Export GL window.
Click Add and complete the following fields.
Click OK and then Continue to export the general ledger transactions.
The Audit GL Transactions option allows GL transaction information to be exported for auditing purposes. For example, if a discrepancy in balancing is found, this option could be used to export the GL transactions that were posted on a specific date or in a specific batch or have a specific journal code (or, more likely, a combination of criteria).
This option uses file mapping. The file map usage of “AuditGLTrans” is used, and the file is exported to the /dti/exchange/cm directory.
In Graphical Accounting, select Fiscal Close | Fiscal Close-GL | Audit GL Trans
.
Click Add and complete the following fields.
Click OK and then Continue to export the information.
The option exports information about credit card subscribers due to auto renew. Credit Card Expires exports similar information, but does not create an Auto Notice transaction.
Select Credit Card Expires from the Subscriber menu to display the Credit Card Expires window.
Click Add and complete the following fields.
Click OK and then Continue to export the credit card auto renew information. The Expiring Credit Cards report will appear, listing the number of records exported and (if Print Details is selected) the auto renew subscribers. See Appendix B for the standard export format.
Barcodes, if you are set up for barcode printing (see in the Setup Manual). See Circulation FAQ #113 for instructions on how to print Intelligent Mail (IM) barcodes.
If a route type change has been done to a group of routes (see ), you might want to reprint renewal notices for subscribers on the routes affected. If so, select this checkbox.
The default value can be set in the Business Rule— Should batches that are imported or created by the system be accepted automatically? (). This determines if system-generated or imported batches should be accepted automatically.
Have e-mail configuration settings defined. This includes the type of e-mail sent (text or HTML) as well as the e-mail protocol, style set, BCC recipient, “From” name and address, and other attributes. E-mail settings are configured by website in .
If a refund is due, that amount is displayed here. The available refund is the subscriber’s account balance. This includes the subscriber’s wallet amount, if they have paid for undelivered premium days (see ). It may be necessary to override this amount. For example, a customer begins a “3 month satisfaction or 100% refund” subscription and, after one month, stops the subscription and wants the 100% refund. Amount shows the refund amount for two months, so you must override this to reflect the entire three months. The amount will display in the Refund column of the .
PRODUCT
setup
Enter the publication for which auto renew information should be exported, or enter “*” to multi-select publications.
CUTOFF DATE
date
Enter the auto renew cutoff date, using the format MM/DD/YYYY (month, day, and year). Subscribers with an expire date that falls in or before this month will be included in the export.
PRINT DETAILS
yes/no
Indicate whether the auto renew information should be displayed as a report after the export is complete.
PRINT PRIVATE DATA
yes/no
If PRINT DETAILS is selected, indicate whether private banking and credit card information (such as account numbers and credit card numbers) should be displayed on the report.
DISPLAY OPTION
predefined
If you selected PRINT PRIVATE DATA, indicate here whether private credit card and banking information should be masked (only the last four digits shown) or displayed in full. Note that users without the proper security will not be able to see private data even if “full” is selected.
GENERATE TASKS
yes/no
Indicate whether tasks should be created. In order to create tasks, a task type and event must be defined for the report in Task setup.
FILE FORMAT
setup
Specify the file map to use for the export. The standard file map, CCExpireExp
, will default.
EXPORT FILE NAME
open (12)
Specify a file name. The standard file name, ccexp.th, will default when the CCExpireExp file map is used. The information will be exported to this file in the /dti/exchange/cm/secure
directory.
EXPORT TYPE
predefined
Indicate whether GL transactions should be exported for a batch or a date range.
UPDATE
yes/no
If this checkbox is selected (the default), then GL transactions are updated with “Posted = yes
” and “PostedDate = today
”. If you run Export GL with this checkbox unselected, GL transactions will not be updated. Field security determines who has access to this checkbox.
UNPOSTED ONLY
yes/no
If Update is selected, this checkbox is automatically selected and skipped.
BATCH NUMBER
setup
If exporting transactions for a batch, enter the GL batch number here. Note that this is the number of the GL batch, not the name of a batch entered by a user.
COMPANY
setup
Enter a company or “*” to multi-select.
JOURNAL
predefined
If exporting transactions for a date range, enter the journal code (type of transaction) to export, or enter “*” to export all journal codes. Press F2 for a lookup of all available journal codes.
START DATE, END DATE
date
If exporting transactions for a date range, enter the start and end date of the period that should be exported.
SUMMARIZE
yes/no
Select this checkbox if you want to produce a summary version of the GL Export. This creates an export file of the total debit and credit entries per GL account for the defined period.
BY DATE
yes/no
Select this checkbox to sort GL records by GL company ID, journal code, GL transaction date, and GL account ID.
FILE FORMAT
setup
Specify the file map to use for this export. The standard format is “GLExport” (which has a File Map usage that is also named “GLExport”). Note: In order for the file-mapped format to be used, the Business Rule, Which file format should be used for the general ledger export?, must be set to “DTI Standard.”
FILE NAME
open (12)
Enter the file name the GL transactions should be exported to the /dti/exchange/cm
directory. The default file name is cmgltran.d
AUDIT TYPE
predefined
Indicate whether GL Transactions or Source Transactions should be searched. Note:
Currently, only the GL Transactions option is supported. Note:
The Source Transactions option will require that the Business Rule, Should a link to the source transaction be created when creating general ledger transactions? (General section), is set to “Yes” to create a GL transaction link (i.e., source information) every time a transaction is written to GL. The default setting is “No,” but it must be changed to “Yes” before Circulation will begin accumulating this information.
ALL GL ACCOUNTS
GL ACCOUNT
yes/no
setup
Select All GL Accounts or indicate which GL accounts to include in the search.
ALL POSTED BATCHES
STARTING POSTED BATCH
ENDING POSTED BATCH
yes/no
setup
setup
Select All Posted Batches or enter a range of batch sequence numbers from which to search.
ALL POSTED DATES
STARTING POSTED DATE
ENDING POSTED DATE
yes/no
date
date
Select All Posted Dates or enter a range of posted dates from which to search. This is the date on which the GL transaction was posted.
ALL GL TRAN DATES
STARTING GL TRAN DATE
ENDING GL TRAN DATE
yes/no
date
date
Select All GL Tran Dates or enter a range of GL tran dates from which to search. This is the date on which the transaction was entered into the GL.
JOURNAL
predefined
Select the journal code (type of transaction) to export, or enter “*” and multi-select journal codes.
SORT BY
predefined
Indicate whether the export should sort by GL Account, Posted Batch, GL Source, or GL Tran Date.
FILE FORMAT
setup
Specify the file map to use for this export. The file mapping usage is “AuditGLTran.” The data elements that can be used with this type of file map are given below.
FILE NAME
open (12)
Enter the name of the file to be exported to the /dti/exchange/cm directory.
It may be useful to print this journal (in particular, before an account billing run) to determine what batches of account payments are still suspended or unapplied. Account billing cannot be run if there are suspended batches (although it can be run if batches are unapplied).
Select Batch Audit Journal from the Account Payments menu to display the Cash Batch Audit Journal window.
Click Add enter the date range for the journal. Suspended or unapplied batches that were entered on or between these dates will be included in the journal.
Click OK and then Continue to produce the report.
Use this option to import miscellaneous charges and credits from an external file. For example, if account delivery credits are stored in a separate system, they can be imported into Circulation rather than manually entered.
The file format of this import is determined by file mapping (MiscChgCredImp
usage). See Appendix B for a list of data elements available for this format.
Create an ASCII file containing the account ID, route, draw, and charge/credit amount.
Select Misc. Chg/Cr Import from the Misc. Charge/Credit menu to display the Misc. Chg/Cred Import window.
Click Add and complete the following fields.
PRODUCT
setup
Enter the product for which charges/credits are being imported.
BATCH DATE
date
Enter the batch date that should be used for the batch of miscellaneous charges/credits.
CHARGE CODE
setup
If charge/credit codes are not supplied in the external file (e.g., if the Fixed Length format is used or if this information is missing from the Comma Separated file), the code entered here will be used instead.
BATCH
open (10)
Specify an ID for the miscellaneous charge/credit batch that will be created.
BATCH DESCRIPTION
open (30)
Enter a description of the batch.
FILE FORMAT
setup
FILENAME
open (30)
Enter the name of the import file in the /dti/exchange/cm directory
.
Click OK and then Continue to import the charges or credits. The charges/credits will be imported, and a suspended miscellaneous charge batch created (the batch can be accepted in Misc. Charge). The account’s primary route will be used in the charge batch. If the account belongs to more than one bill source, the first bill source found will be used. A processing report will display the number of records exported and any errors.
Balance Writeoff is a mass writeoff utility that can be used to zero out invoices of all accounts of a certain bill source responsible for routes with a certain single copy type. This utility zeros out the invoices by creating a suspended batch of payment adjustments.
This may be used, for example, with dealers who manage racks. For GL purposes, the dealers are charged for the rack draw and credited for the amount collected from the rack. However, the amount collected typically doesn’t equal the draw charge (because of rack pilferage), and so the dealers accumulate a debit balance. Balance Write Off can be used to write off that pilferage amount, crediting dealer Accounts Receivable and debiting another GL account.
Balance Writeoff must be run for a particular invoice date. It will zero out the dealer’s invoice for that billing period by creating offsetting credit or debit entries. For example, if a dealer has a balance from 02/29/12 and another balance from 03/31/12, and you enter an invoice date of 02/29/12, Balance Writeoff will only create a credit for the amount from 02/29/12.
Select Balance Writeoff from the Misc. Charge/Credit menu to display the Balance Write Off window.
Click Add and complete the following fields.
COMPANY
setup
Enter the company to which the dealers belong.
BILL SOURCE
setup
Enter the bill source to which the dealers belong. Enter “*” to multi-select bill sources.
SINGLE COPY TYPE
setup
Enter the single copy type, such as “rack,” for the writeoff. Dealers delivering routes with this single copy type will have their invoice written off. Enter “*” to multi-select single copy types.
INVOICE DATE
date
Enter the date on which the writeoff should be based. Account invoices will be written off as of this date.
BATCH, BATCH DESCRIPTION
open (10) open (30)
Designate a batch ID and enter a description for the batch of credits that will be created by this process. The batch ID must be unique—there cannot be an existing batch with the same ID.
BILLING PRODUCT
setup
Enter the publication for which invoices should be written off. Only the dealers delivering this publication will have their invoices written off. Note, however, that if a carrier/dealer delivers multiple publications that are billed on the same date, the entire invoice (for all publications) will be written off.
BATCH DATE
date
Enter the date on which this batch should be processed. This date determines when the writeoff will occur. Note that the credits created by the process will be in the current aging period for the carrier/dealer (while the invoice being written off may be in an older aging period).
BANK
setup
Identify the bank to use for these adjustments. The default specified in Business Rules (Account Payments section) will default, but it can be changed.
BALANCE TYPE
predefined
Identify the type of balances to write off: invoice, credit memo, or both.
CREDIT ADJUST CODE
setup
If the balance type is invoice or both, identify the credit adjust code to use with the payment adjustments.
DEBIT ADJUST CODE
setup
If the balance type is credit memo or both, identify the debit adjust code to use with the payment adjustments.
Click OK and then Continue to write off the account balances. After the process is complete, a report will list the total number of accounts processed and total amount written off for each bill source. A suspended cash batch is created with cash transaction records for the open invoices and/or credit memos. Use the Account Payments | Payment Entry option to accept this batch.
Select the file format to use for the import. At least one format for the MiscChgCredImp usage must be defined in .