Pension plan deduction

Dear friends,
The pension record (IT0169) is delimited for an employee within a pay period.
Still pension is deducting for the entire period.
The employee is going to be separated from company.Due to settlement employee has active status till end of pay period.
Where as IT0169 is delimited before end of pay period. But pay results shows full deduction ignoring the delimition of IT0169.
How the deduction can be controlled based on pension record validity??
Thanks & Regards
JIm

Hi Jimson
P0169 function parameter 1 set in your payroll schema determines the date on which employee would be eligible for deduction or not.
Either deductions would be taken in full or not taken at all which depends upon parameter 1.
Please look at parameter and update your infotype 0169 accordingly.
If paramater 1 is BEG then you need to have employee master data for 0169 delimited before just a date before to current pay period start date.
If paramater 1 is END then you need to have employee master data for 0169 delimited at any date before to current pay period end date.
If paramater 1 is CHK then you need to have employee master data for 0169 delimited before just a date before to current pay period payment date.
Thanks,
Ameet

Similar Messages

  • Pension Plan

    Dear all,
    We have a pension plan scenario:
    -/ 1% Rank Salary in Deduction
    -/ Divided by the average rate of contribution
    -/ < 5 service years: do not receive the capital investment in both original and profit
    -/ 5 u2013 8 service years: 25% investment include the original capital and profits accrued to the time of dismissal
    -/ 8 u2013 10 service years: 50% investment include the original capital and profits accrued to the time of dismissal
    -/ 10 u2013 15 service years: 70% investment include the original capital and profits accrued to the time of dismissal
    -/ over 15 service years: 100% investment include the original capital and profits accrued to the time of dismissal
    -/ if workers died while working in Group: inheritor will receive 100% investment including original capital and profit accruing to the workers immediately died
    So, pls give me solution. How can i configure? Pls give details for that.
    Thank you very much!
    Best Regards,
    Quanglv

    Hi Jimson
    P0169 function parameter 1 set in your payroll schema determines the date on which employee would be eligible for deduction or not.
    Either deductions would be taken in full or not taken at all which depends upon parameter 1.
    Please look at parameter and update your infotype 0169 accordingly.
    If paramater 1 is BEG then you need to have employee master data for 0169 delimited before just a date before to current pay period start date.
    If paramater 1 is END then you need to have employee master data for 0169 delimited at any date before to current pay period end date.
    If paramater 1 is CHK then you need to have employee master data for 0169 delimited before just a date before to current pay period payment date.
    Thanks,
    Ameet

  • Pension plans in portal

    Hi,
    We have pension plans and the employees should be able to change the data anytime.
    Open enrollment is for one month only and in that dental,medical,life plans are configured But only pension plans should exists for employees all time in portal.
    Can anyone suggest me how to solve this issue
    Thanks,
    Usha

    closed

  • Pension Plans

    Hi,
    We have pension plans.Our Customer requirement is that to change the pension plans by an employee at any time without any time restriction.
    But the open enrollment option is for only 1 month in a year.
    Can anyone suggest how I can solve this issue so that employee can only change pension plans at any time.
    Thanks,
    Usha

    closed

  • Difference between Pension plans and savings plans

    Dear Friends,
        I'm familiar with the configuration of savings plans. But I have no idea about the pension plans. I realize that some of the basic steps are common to both savings and pension plans but what is the main difference from a config perspective?.
    If any one can kindly explain the necessary steps to set up pension plans or if there is any document which talks about it please please let me know.
    I appreciate the help and thanks in advance.

    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Minimum and Maximum Number of Dependents
    Define Cost Variants:
    In this step you define cost variants to determine which factors influence the cost of a health plan for an employee. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual costs in this step. You simply define how costs vary according to:
    u2022 Plan
    u2022 Option
    u2022 Dependent coverage
    u2022 Employee data
    Before you start to define cost variants, you need to do the following:
    1. Determine how often costs vary for all the combinations of option and dependent coverage that you have defined in each plan.
    This indicates how many cost variants you need. You can use the same cost variant more than once, for example, if costs are always identical for the dependent coverages 'employee only' and 'employee plus family' within a plan, regardless of the plan option
    2. Determine how costs vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Variants
    Cost Rules:
    You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Rule
    Health Plan Attributes:
    In this step, you bring together all the definitions relevant to the health plan that you have made in the previous steps.
    You assign to each health plan:
    u2022 Its options
    u2022 Relevant dependent coverages
    u2022 The cost variants for the combination of options and dependent coverages
    IMG Path: Personnel Management  Benefits  Plans  Health Plans  Assign Health Plan Attributes
    Insurance Plans:
    In this step, you define general data for insurance plans
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Insurance Plan General Data
    Coverage Variants:
    In this step, you define coverage variants to determined which factors influence the coverage an employee is entitled to in a plan. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual coverage in this step. You simply define how coverage varies according to:
    u2022 Plan
    u2022 Coverage option
    u2022 Employee data
    Before you start to define coverage variants, you need to do the following:
    1. Determine how often coverage varies for different coverage options.
    This indicates how many coverage variants you need. Note the following:
    u2022 If a plan has set coverages (including salary multiples), you need a
    coverage variant for each.
    u2022 If a plan allows employees to choose any amount of coverage within a
    range, you need only one coverage variant.
    u2022 If a plan has options, you will need a coverage variant for each option.
    2. Determine how coverage varies according to employee data.
    This determines how you need to set up your variants using employee groupings. For each variant, you can specify a parameter group and coverage grouping to determine coverage
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans 
    Coverage Rules:
    In this step, you define the actual coverages for a plan.
    You need to define coverage for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
    Coverage can be defined as a flat amount or as a factor of salary
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Coverage Rules
    Cost Variants:
    In this step you define cost variants to determine which factors influence the cost of an insurance plan for an employee. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual costs in this step. You simply define how costs vary according to:
    u2022 Plan
    u2022 Coverage option
    u2022 Employee data
    Before you start to define cost variants, you need to do the following:
    1. Determine how often cost varies for different coverage options:
    u2022 If an insurance plan has set flat coverage options and flat costs, you need
    to define a cost variant for each flat cost.
    u2022 If you have set flat coverage options and the flat costs are directly
    proportional to the coverage stated in the flat cost, you need only one
    cost variant.
    u2022 If an employee can choose any amount of coverage within a range and the
    cost of the coverage is directly proportional to the coverage, you need
    only one cost variant.
    2. Determine how costs vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Variants
    Cost Rules:
    You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Rules
    Insurance Plan Attributes:
    In this step, you bring together all those parts of an insurance plan, that you have already defined in the previous few steps.
    You define the insurance plan options, then associate to each insurance plan:
    u2022 Cost variant
    u2022 Coverage variant
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Assign Insurance Plan Attributes
    Combined Coverage Limits:
    When you define coverages for plans such as insurance, you can set limits on the coverage amount. This is often used when the coverage is an amount dynamically calculated when the employee chooses her coverage.
    However these limits apply only to one plan and yet you might need to define limits which combine the coverages of more than one plan.
    In this chapter, you define these combined limits as follows:
    1. The limit that might span 2 or more plans is reduced to a mathematical equation, where there is an amount on one side and plan coverages on the other side. The two sides of this equation are then DIVIDED BETWEEN the two views in this chapter.
    2. The first view defines the limit in monetary terms which is one side of the equation. It also defines the operator (equals, is greater than, and so on).
    3. The second view defines the other side of the equation in terms of the plan coverages
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Combined Coverage
    Combined Coverage Limit Expressions:
    In this step, you enter the second half of the equation, as discussed in combined coverage
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Define Combined Coverage Limit Expressions
    Imputed Income for Selected Benefits:
    In this section of the IMG, you define the criteria needed to calculate Imputed Income.
    Imputed Income is based upon benefits paid for by the employer and calculated using rates set by the Internal Revenue Service (IRS). This value is then treated as taxable income for the employee
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Age Groups for Imputed Income
    Review Calculation Factors for Imputed Income:
    In this step, you check that the Imputed Income Rate Table entries are correct.
    The imputed income age groups are associated with the rates/factors set by the IRS
    IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Calculation Factors for Imputed Income
    Savings Plans:
    In this step, you define general data for savings plans.
    You have defined the relevant type, status, and provider for each plan in the Basic Settings section of the Benefits IMG
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Savings Plan General Data
    Employee Contribution Variants:
    In this step you define employee contribution variants to determine which factors influence the permitted employee contribution to a plan. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual contributions in this step. You simply define how contributions vary according to:
    u2022 Plan
    u2022 Option (only for plans in the plan category Miscellaneous)
    u2022 Employee data
    Before you start to define variants, you need to do the following:
    1. Determine how often employee contributions vary for plans and any plan options.
    This indicates how many contribution variants you need.
    2. Determine how employee contributions vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and employee contribution grouping to determine employee contribution
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Variants
    Employee Contribution Rules:
    In this step, you define the employee contribution limits for each plan.
    You need to define employee contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
    You can define minimum and maximum employee contribution in the following ways:
    u2022 As a fixed amount
    u2022 As a percentage of salary
    u2022 As a contribution unit
    In Payroll, the total employee contribution is the sum of these amounts
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Rules
    Employer Contribution Variants:
    In this step you define employer contribution variants to determine which factors influence the contribution the employer makes to a plan. Variants are plan-specific; each plan has its own variant(s).
    You do not enter any actual contribution in this step. You only define how contributions vary according to:
    u2022 Plan
    u2022 Option (only for plans in the plan category Miscellaneous)
    u2022 Employee data
    Before you start to define variants, you need to do the following:
    1. Determine how often employee contributions vary for plans and any plan options.
    This indicates how many contribution variants you need.
    2. Determine how employee contributions vary according to employee data.
    This determines how you need to set up your variants using employee groupings.
    For each variant, you can specify a parameter group and employer contribution grouping to determine employer contribution
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Variants
    Employer Contribution Rules:
    In this step, you define limits for the contributions made by the employer to employee plans. You so this for each employer contribution variant for each plan.
    You need to define employer contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
    You can define the employer contribution and the contribution limit in either of the following ways:
    u2022 As a fixed amount / as an amount per unit contributed by the employee
    u2022 As a percentage of employee base salary or employee contribution
    IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Rules
    Assign Savings Plan Attributes:
    In this step, you complete the definition of savings plans by bringing together the relevant elements that you have already defined:
    u2022 EE contribution variant
    u2022 ER contribution variant

  • Pension plans are not appearing under HRBEN0001

    Hi All,
    I have configured 3 pension plans and plan status for 2 plans are losed and one is open. I have set up everything correctly. But I am not able to see under Tcode HRBEN0001. Can anubody give me lights on this?
    What I understood is closed status will not reflect via HRBRN0001. Am I right or wrong?
    Regards,
    Purnima

    Hi Sarah,
    Yes, that person is eligible for that plan whose plan status is open. But when I am going through HRBEN0001 for that category of employee, I am not able to see that plan. I checked all configuration. Everything looks like OK. Can you please tell what I am missing?
    Regards,
    Purnima

  • Benefits Health Plans Deductions are not working

    Hi All,
    I configured health plans successfully and i am able to see all of my health plas from Open Enrollment and when i was trying to enroll into plans, the plans are showing wrong deduction amount for all my health plans.
    Instead of deducting one dollar, it is deducting 4 dollars
    Instead of deducting 3 dollars, it is deducting 12 dollars.
    so each and every deduction amount is multiplied by 4.
    I was checking each and every table, i haven't find any thing wrong, some one please help me to resolve this issue.
    Thanks in Advance.
    Regards,
    Abhiram.

    Hi Keeran,
    In the standard the contribution are taken depending on the employee pay period (payroll area). But I think you might be able to modify this process via a user exit, the best for your scenatrio, I think, is the one below:
    Definition name               PBEN_PAY0006
    Definition short text         Country exit for determination of EE contribution fixed per.
    Hope this help
    Sarah

  • HSA Plan deductions

    Hi
    We have configured the HSA plan as Savings plan (IT0169) and currently the deductions are on bi-weekly basis. we are running this very smoothly for past one year. So, if the employee wants to enroll in the HSA plan through any Adjustment Reason ( say Birth), the R/3 screen would say 'Pre Tax Contribution Bi-Weekly' and beneath that, employee can enter the amount he wants to pledge for the year.
    Now effective from 01/01/2008, we want the employee to see the Pre-Tax contribution amount as Annual and not bi-weekly anymore. To achieve that, I configured a new Variant under 'Define Employee Contribution Variants' for this HSA plan with contribution Criteria as 'Annually'. Since Variants are not date dependent, so under the 'Define Employee Contribution Rule' for the HSA plan and the new Variant ( which I had created in the previous node), created new entry , effective from 01/01/2008 with contribution type 'Amount' and pre-tax. Lastly, under the node 'Assign Savings Plan Attributes', I added the new variant for the HSA plan, effective from 01/01/2008.
    Till here, the configuration looks good. But the problem is , when I elect the HSA plan through an adjustment reason, (HRBEN0001 screen) it still shows the pre-tax contribution as Bi-weekly instead of Annually, though the plan start date is 01/01/2008. I am wondering what is it that does not let the new variant show that the contribution is Annually and not bi-weekly from 01/01/2008.
    I will appreciate if somebody suggests me a way out of this ASAP.
    Of course, helpful suggestions are rewarded.
    Thanks again.
    Wills

    Hi William,
    We have a similar requirement and I am having the same issue of the employee unable to see an annual contribution instead of the current Monthly.
    Did you get  a solution for the above problem ?
    Regards,
    Spinoza

  • Field and Table for Pension Plan

    Can anyone tell me what are the field name and table name in Pension plan

    Hi Harini,
    In Table VBUK you 3 different status related fields for  sales documents.
    Over all status field name GBSTK ( here it gives the total status of praticular sales document) here you see options
    A  Not yet processed      ( This means its complete open)
    B  Partially processed     ( This means the sales doc is partially processed)
    C  Completely processed  ( This means the sales doc is completly processed)
    Delivery status  and over all delivery status field name LFSTK and LFGSK respectively, these 2 fields will be same always ( here it gives the total status of praticular sales document) here you see options
    A  Not yet processed      ( This means its completly  open)
    B  Partially processed     ( This means the delivery doc is partially processed)
    C  Completely processed  ( This means the delivery doc is completly processed)
    So overall status can be  different then delivery or overall delivery status.
    If sales document has 100 quantity for 1 material, if delivery is done for 50 quantity.
    Then over all status field name GBSTK will be B  Partially processed and delivery and overall delivery will be C  Completely processed  .
    Regards
    vK

  • Re: Pension Contribution not deducting correctly

    Dear Gurus,
    When an employee is hired in the mid-month, the Employee and Employer pension contribution is not getting deducted properly.
    if the basic is greater than 6000 employer pension should deduct 541. it is not deducting correctly when the joining date is greater than 1st of the month.
    Kindly help to sort out this issue.
    Thanks
    Anbu

    For mid-month Hiree and Termination on Savings Plans and Pensions - there are certain SAP notes that need checked. I found one for Savings plan contribution -
    0000725626  -  Savings/ retirement plan not processed in first period 
    I have seen another note for India Benefits that may be of help to you.
    SAP Note 1160806 -PF and Pension contri.for mid-month joining & termin.
    Please verify that these are part of your code line. Although these may be old fixes, it is better to verify rather than assuming ECC6 has these already.
    Hope this helps,
    Roopa

  • Incorrect contribution value after rate change in pension scheme

    Hi Guys,
    I have come across a peculiar thing while changing the rates for the employee and employer contributions for a pension scheme.
    We have a pension scheme called "Opt60" which is implemented by having a recurring pre-tax deduction element. The formula attached for this element calculates the employee and employer contributions and directly feeds the parent element for employee contribution an indirectly feeds an employer contribution element(non-recurring and employer charge classification).
    The rates for the employee and employer contributions are stored in 2 globals (13% for EE and 12.5% respectively).
    Now, when running the quickpays from april to june correctly calculates the EE and ER contributions. But when i change the global values(EE= 18% and ER=9.8%) on 01-JUL-2011 in update mode. The EE and ER contributions are coming something else(incase of EE it is neither 13% nor 18%) for the month of July. But when i run quickpays for subsequent months like Aug, Sep, Oct, Nov and so on, they are correctly calculated at 18% for EE contributions and 9.8% for ER contributions.
    Also, if i do a balance adjustment for the month of July for EE and ER contribution then, for the next month ie.Aug, they are coming exactly same as July months and from now the subsequent months like Sep, Oct, Nov and so on, it is correctly calculated at 18% for EE contributions and 9.8% for ER contributions.
    Can you take a look at this and suggest me something i have be overlooking.
    Also, the Balance value used in the formula is of dimension ASGTD_YTD. Does this have an effect on the outcome of the above mentioned % contributions?
    With Regards
    Sachin S.

    Is the same WT being used for the pension deduction?
    Does that WT appear in the employee's RT?
    In the Benefits Processing part of your Payroll Schema, I presume that you are using function P0169 to process the Pension Plan.  What is the processing happening in function P0169?

  • Pension Contribution Calculation

    Hi all,
    I'm setting up Canadian defined contribution and defined benefit pension plans in SAPs benefits module under "Savings Plans".  The employee contribution for one plan should be 2.5% of earnings up to YMPE and 5% after that (where YMPE is $48,300 for 2011).  For example, someone with earnings of $60,000 would be able to contribute:
    2.5% of 48300 = 1207.5
    5% of (60000-48300) = 585
    1207.5 + 585 = $1792.5.
    Is there a way to satisfy the above requirements using the Employee Contribution Rules under Savings Plans?  How do I configure a 2.5% up to YMPE and 5% after YMPE?
    Thanks,
    Chirag

    Cher Rémi,
    With your help I was able to understand what my issue was.
    Under Payroll > Payroll: Canada > Benefits Integration > Define wage types for benefit plans:
    I realized the pension plan I was working with was using a compensation model for salary determination.  Because of this, it was necessary for me to create a corresponding cumulation wage type and assign it in the above path in the "Compens. wage type" field.
    Also, another thing that complicating my testing is the fact that we are dealing with outsourced payroll.  The payroll schema we are using for the outsourcing only runs gross payroll and does not populate table CRT, this only happens during import.
    Thank you once again for your help.
    Chirag
    p.s. If you are ever in Montreal, drinks are on me!!!

  • Benefits- Miscellanious plan

    Hello All,
    Pension Premiums Calculation -> Our pension plans are set up as Miscellaneous Plans.  The system is not calculating the employer premium. And also the Wage type is showing up for Full-time employees but not for Part-time, I couldn't escalate why it is showing up Full-time & not for Part-time.
    The schema was build for miscellanious plan in sub-schme UBE1 for table p0377 (process benefit 1st call fro paremaeter 1) and UBE2 for table P0377(process benefit 2nd call for Parameter 2). When I'm looking at payroll log for some reason it's processing Benfit 1st call and nor reading 2nd call (where in I believe that the first program grouping Fulltime & Part-time, so as the scheme is reading for parameter 1 it's displaying wage type for Full-time and as the system is not reading parameter 2 its's not displaying Part-time - not sure)
    Please help me to resolve this issue, it is very urgent for me to resolve. please help.
    Thanks in advance,
    Rajini

    As I mentioned to you before, the Health Plans (IT0167), Insurance Plans (IT0168) and Savings Plans (IT0169) are something that is set-up in SAP and that employees "subscribe" or "adhere" to, and for which a contribution is made either by the employee, the employer or a combination thereof.
    What you seem to want to set-up is a "Compensation Program" for short term and long term disability, since you mention that  the employer will pay Full Salary to an employee who is disabled but only for 14 days if the employee is an "outpatient" and only for 60 days if the employee is an "Inpatient".
    Two "Paid Absence" categories could possibly provide for that need: Outpatient Paid Absence and Inpatient Paid Absence.
    As for the Medical Expenses part of your requirement, you could possibly create a WT for  Medical Expense Refund (to be entered on IT0015), or a WT for Medical Expense Per-Diem (to be entered on IT0014) if there is a flat amount per day to be paid by the employer.
    SAP probably has a special Infotype for Short Term Disability, similar to the Maternity Leave (IT0080) that we use in Canada, but I can only suggest you to do a little search.  Out of the 91000 results from a Google search on "SAP Short_term_disability", this one looks like what you seem to want: http://help.sap.com/saphelp_46c/helpdata/es/bb/8a3ac94813d3119b430060b0671acc/content.htm

  • Pension Premium calculation

    Hi Experts,
    One of our customers pension plans are set up as miscellaneous plans. Their system is not calculating the employer premium correctly. It should calc on an ee's November 15th salary of the previous year. It is currently calculating on the 2005 November 15th salary for ee's.
    Kindly help me as how to resolve this ticket. this is high priority ticket.
    Thank You in advance,
    Tanuja.

    Cher Rémi,
    With your help I was able to understand what my issue was.
    Under Payroll > Payroll: Canada > Benefits Integration > Define wage types for benefit plans:
    I realized the pension plan I was working with was using a compensation model for salary determination.  Because of this, it was necessary for me to create a corresponding cumulation wage type and assign it in the above path in the "Compens. wage type" field.
    Also, another thing that complicating my testing is the fact that we are dealing with outsourced payroll.  The payroll schema we are using for the outsourcing only runs gross payroll and does not populate table CRT, this only happens during import.
    Thank you once again for your help.
    Chirag
    p.s. If you are ever in Montreal, drinks are on me!!!

  • Is it usual Internat'nl Plan behavior to use domestic data allotment 1st??

    Dear Folks,
    Just wrapping up a trip to Montreal, so I bought 20MB of international data (at an exorbitant $25) so I'd have 3G here.
    When I started using the iPad in Montreal, it started using up my domestic data allotment (what was left of my 250 MB/month subscription). Only after that was used up did it start eating into my 20 MB of international data.
    It was a pleasant surprise, to have a lot more MB available in Montreal than I expected. Made the $25 charge more palatable. But... Is that normal out-of-US behavior??? Or normal just for Canada? Or normal just for Montreal?
    I'm pleased but puzzled.
    pax / Ctein

    Yes. I noticed the same thing on two different trips. The first time I purchased the plan prior to going to Canada and noticed that the minutes came off my US limited plan first. Once it ran out the international data plan deductions happened.
    The second trip I waited till I was in Canada to see if I didn't need the international plan. I couldn't get access to the network without it so I purchased it (while at a WIFI hotspot) and same behavior as the first trip. Now that I am on the unlimited plan this works out really well for me!
    I was in multiple cities and multiple provinces, so it appears to be the case with a US iPad in Canada. Not sure about other international locations? Anyone?

Maybe you are looking for