AFC Bundler manual
Bundler Overview
Product offerings by Telecommunication companies include grouping of services into a special price for competitive and/or other strategic reasons. The grouping of services is called "bundling." AvaTax for Communications (AFC) handles these bundled products by assigning a transaction/service pair for the bundle. Even though this bundle can be structured using API calls, the AFC Bundler completes the task much more easily.
Introduction to AFC Bundler
The AFC Bundler application supports creating AvaTax for Communications bundle definition files. This program allows the user to select any number of valid AFC transaction/service pairs to be bundled.
Bundle Structure
A percentage specifies the portion of the entire bundle charges applied to each AFC transaction/service pair in a bundle. The application will then assign a transaction ID and service ID for that bundle. These assigned transaction and service IDs can then be passed to the AFC engine instead separate AFC transaction and service IDs when specifying a service to tax. An AFC bundle definition file can have an unlimited number of bundle definitions.
This interactive program works with AFC to make bundling of products an easy task. You will find using the Bundler will reduce time and increase accuracy of bundling of product pairings.
Bundling Set-up Step
This process flow is used with bundle definition files and the AFC engine.
Process Flow
Note: The system can use both AFC T/S types and AFC User-defined Bundle IDs.
AFC and AFC Bundler
Using the combination of AFC Bundler with the AFC engine provides additional versatility and flexibility.
|
AFC Configuration File |
Users can toggle user-defined bundling "on" and "off" in AFC by specifying an option in the configuration file. AFC will detect when bundling is toggled on and will then read the user-define bundle file and use the definitions within AFC. |
|---|---|
|
Filename Path |
The filename with path of the bundle definition file should be entered; for example: bundling=on bundlefile=c:\[some path]\EZtax.bdl
If the "bundlefile" setting is not supplied, then the bundle definition file MUST be named EZtax.bdl and MUST be placed in the same directory as EZtax.dat |
|
AFC Bundler |
Bundling is an enhancement to the system and will not affect the use of AFC’s current defined transaction and service types. |
|
User-Defined Bundles |
Each AFC transaction/service type in the user-defined bundle has a specified percentage of the total charge that is applied to the transaction/service type. |
|
Bundle Definition File |
AFC Bundler will create, edit and delete user-defined bundle definitions stored in a bundle definition file. |
|
AFC |
The AFC user can use either the Bundled transaction/service IDs or AFC transaction/service IDs when sending a transaction to AFC. |
AFC Bundler Functions
The AFC Bundler application creates AFC bundle definition files. These files are used by AFC to recognize your bundle and process them through the tax engine.
Transaction and Service Identification
|
User Defined |
Users can toggle user-defined bundling "on" and "off" in AFC by specifying an option in the configuration file. AFC will detect when bundling is toggled on and will then read the user-define bundle file and use the definitions within AFC. |
|---|---|
|
Bundle Specification |
The description must be 50 characters or less. Each bundle can have an unlimited number of AFC transaction/service IDs associated with it. The percentage is the percentage of the charge applied to the AFC transaction/service. |
|
T/S Type Calls in AFC |
AFC system can process both AFC T/S types and bundled T/S types together in making passes in AFC. |
System Set-Up
User Requirements
The user is only responsible for supplying the bundle definition file and turning on bundling in the configuration file. The user can then specified the bundle transaction and service IDs in a transaction sent to AFC instead of AFC transaction and service IDs.
No user software code interface to AFC needs to change for users to enable bundling.
File Structuring
|
User Defined |
EZtax.bdl is the formatted text bundle definition file. It is created by AFC Bundler. This file may be may be named differently, and the assigned name, with path, entered into the EZtax.cfg file; as shown below. |
|---|---|
|
Configuration File |
EZtax.cfg is a file of run-time configuration settings. This file must be in the same location as the working directory in order for the AFC system to find and load user-define settings. The option, bundling=on, must exist on one line in this file to turn bundling on. The option, bundlefile=z:\path\filename, should be included, where "z" represents the drive and "path" is the path to the bundle definition file. "Filename" may be any valid name; as example: EZtax.bdl |
Working with Bundle Files
Bundles can be created, saved and edited using the Bundler. This section defines how to create, save, maintain and update user defined bundle files.
How to Create a Bundle
You can create multiple bundles within a .bdl file. The file is used by AFC to rate all taxes within the each bundle for your company. One file may have an infinite number of bundles structured with multiple transaction and service type pairs.
Creating a Bundle
|
Step |
Action |
|---|---|
|
1 |
Click on the New Button located to the top right of the application.
|
|
2 |
Enter a name for your bundle. Click OK.
|
|
3 |
To add the bundle's transaction and service types for your bundle, click on the Add Button located below the T/S bundle items.
|
|
4 |
Select a transaction type by typing the first letter of the transaction. If the desired transaction is not visible in the input box then continue to use the same letter until it appears.
|
|
5 |
Select a service type by typing the first letter of the service. If the desired service is not visible in the input box then continue to use the same letter until it appears.
|
|
6 |
Indicate the percentage this T/S represents in the entire bundle package. Remember, the total must equal 100%.
|
The following image represents a complete Bundle. Notice the Transaction ID and Service ID for the new bundle. The proportion of the charges for each T/S is represented in a % within a bundle.
Note: The % allocation is limited to 7 digits plus the decimal point.
Additional Bundles
You may create more bundles for your various products and services offered. The Bundler will keep track of each bundle by listing the bundle name in the Bundle list box.
Saving the Bundle File
Several bundles may be created at one time in the Bundler application. All of these bundles are not ready for AFC until you save the .bdl file. The following steps complete this activity once you have your bundles named and T/S type pairs proportionally assigned.
Completing the Bundle File
|
Step |
Action |
||||||
|---|---|---|---|---|---|---|---|
|
1 |
The Bundler is equipped to remind you when a file has not been save or when unsaved changes were made. To save a bundle file, choose one of these methods.
|
||||||
|
2 |
Please select the most appropriate option.
|
Bundle File Location
Note the Bundle file must be renamed to EZtax.bdl and placed in the AFC database file directory. This is where the configuration file (EZtax.cfg) is going to look for this Bundle.Tax Types.
Updating a Bundle in Your File
Once a bundle file has been saved it can be changed or deleted. The bundle within the *.bdl file is updated when you make the changes and save the file. Anytime a change is made to a bundle upon exiting the Bundler, the program will verify your need to save the file.
The Process of Changing a Bundle
|
Step |
Action |
|---|---|
|
1 |
From the operating Bundler session, click File > Open.
|
|
2 |
Select the *.bdl file to change then click on the Open button.
|
|
3 |
Make any of the following Changes in the Bundler:
Once changes are made then either Save the file or Exit from the Bundler. When exiting the Bundler the program will verify if you want to save changes.
|
|
4 |
When satisfied with the changes created in the Bundler file then click OK.
|
Changes Complete
The changes made within the Bundler are saved in the file and the next pass to AFC will reflect any updated records.