Prepaid Expiration Date Should Be AFTER 30 Days, Shouldn't It?

I don't understand this, so maybe someone can explain this to me...
I activated my phone and put $45 on it (Allset plan) on November 3.  I did this specifically on that date because I get paid on the 3rd of each month.  So, logically, I would like to PAY on the 3rd of each month.
I see my plan goes from Nov 3- Dec 2.  I had asked a rep online - while he was helping me with another unrelated issue - if this meant my next payment would be due Dec 3.  He said no, it means my phone will be shut off on Dec 3 if I haven't paid my next payment by Dec 2.
I calculated it out several months and, at this rate, my due date will be pushed up 1 day per month until the date will have changed so many times it will be meaningless.  Why is the 30th day the day you have to pay, and not the day after that?  It's a 30 day plan, after all.
Look I am not trying to be difficult but I am on a very tight budget and these dates are throwing me off.
Anyone help?

If the 30th day is Dec 2, which I agree it is, and the service is for 30 days, do you not think then that the 30th day is included in this?  In other words, your payment then would be due on the first day of the next cycle, which would be Dec 3 or the "31st day".
Otherwise, this is asking the client to pay for Nov 3 through Dec 1, which is 29 days.  Then pay for the next cycle on the 30th day of that cycle!   It makes more sense to me that the client is paying for a full 30 days (Nov 2- Dec 2), then pays for the next 30 day cycle on the day after that.  In other words, the last fully paid day of the 30 day cycle is Dec 2, so payment would be due Dec 3 at 12:01.
So if you paid on Dec 3 at 12:01 (hypothetically), that ought to start the new billing cylce.  If you do not pay by 12:01, then your service is shut off.  My check goes in at 12:01 on Dec 3, why isn't that good enough?
The only other solution is that I budget for 2 payments per month at some point, and I cannot afford to do that.  For instance, paying $45 on Nov 3, as I did, then paying another $45 on Dec 2, one day before I get paid again.  So that means I will have not only paid for 29 days, but will have paid twice in one pay period.
It doesn't make sense to me.

Similar Messages

  • Expiration date not displaying after upgrade from 2007 to 2013

    I recently upgraded from MOSS 2007 to 2013.  I have information management set up on a library of InfoPath forms.  For the forms that were created prior to the upgrade, the expiration date is displaying and actually get updated if I modify them. 
    But none of my forms that have been created after the upgrade, are displaying when the expiration date is, which should be one year from modify date.  If I modify the forms created prior to the upgrade, they reflect the new, update date.
    Are these new forms not getting the policy applied to them, and why not?  I am not sure why the older forms are getting updated, but not my new ones.
    Denise E.

    Hi Denise,
    According to your description, my understanding is that the Expiration date column was not displaying values after upgrading from SharePoint 2007 to SharePoint 2013.
    Per my knowledge, we can only use the date column which is added to the library or list or the Declared Recorded date to set the retention policy, so if the Expiration date is used in the retention policy then the Expiration date should be a column in the
    library or list.
    I recommend to check the retention policy in the library and see which column is used in the retention policy as the image below shows:
    After that, go to the Library settings to find this column.
    Could you please provide screenshots of the retention policy and the columns in the Library settings page?
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Start date should be after the dd.mm.yyyy or later error message.

    We have recently applied HR support packs 46 to 51 and now when updating Personal Data (IT0002), Bank Details (IT0009) or Addresses (IT0006), the following error message is displayed 'Start date should be after the 07.02.2010 or later'. Where the screens allow for a future date to be entered we have done so, but the same error message appears.
    Has anyone encountered this problem after apply support packs?
    Jason

    Hi,
    Check what is the date maintained in table V_T569R.
    With Reagrds
    Shyam V

  • Original GI date should display closest day when Saturday and Sunday comes

    Hi Guys,
    I am getting Original GI Date as After deducting Transit time from Original Delivery Date.
    But i want to fullfill  the below requiremnt also.
    the Original GI Date should be then the working day defined in the calendar of the shipping point. Thus if the calculation gives  Original GI Date to be Sunday 4.3.2012 then it should changed to the closest previous working date which is Friday 2.3.2012 (calendar 'YT').
    Any one help me how to execute the above requiremnt.
    regards
    reddy.

    Hi,
    Pass your GI date to below given FM, it will return you the day of the week.
    CALL FUNCTION 'DATE_COMPUTE_DAY'
    EXPORTING
    DATE = GI_DATE
    IMPORTING
    DAY = day_of_week_num
    EXCEPTIONS
    OTHERS = 8.
    the value returned by this FM in day_of_week_num will be between 1 to 7, 1 representing Monday and 6 = Saturday and 7 = sunday.
    Now if your working days are from monday to friday then simply check the value returned by this FM is it is 6 then you can subtract 1 for last friday or add 2 for next monday and in the same fashion if value returned is 7 then subtract 2 for last friday and add 1 for next monday in GI date.
    For adding and subtracting value from GI date you can use FM RP_CALC_DATE_IN_INTERVAL.  And if you need to check some settings related to Factory calander then you can use FM DATE_CONVERT_TO_FACTORYDATE.
    Regards,
    Durgesh.

  • Sales orders with expired dates should not consider in MRP

    Hi,
    My requirement is that when i m running MRP for sales order for which expiry date has already been lapsed or over.sysyem should not create any mrp elements(Planned order) for such Sales orders.
    We have maintained one Z table which gives the validity period(Expiry date) for sales order according to their respective division.
    if MRP running date lies after the date of expiry of sales order, system shoul not allow to run MRP for that sales order or it should pop some message while executing MRP run before saving it.
    How we can achieve this?
    Pls suggest.....
    Rgds,
    Yogesh Thorat..

    Since as per standard, there is no concept called validity period for sale order and you are maintaining in a zee table, definitely your requirement has to be met with user exit or function module or some enhancements.
    Perhaps, you can try with MRP Enhancements
    a)  LMDR2001  or
    b)  LMDZU001
    to meet your requirement.
    thanks
    G. Lakshmipathi

  • SharePoint Service Accounts - Passwords have expiration date when they are set to never expire

    The managed accounts in my farm all have the Enable automatic password change
    unchecked.  Also these same accounts in AD have the Password never expires
    checked. 
    If I use get-spmanagedaccount to view the accounts, some passwords show as already expired or have a future expiration date.  The automatic change is set to False and nothing is listed under the Change Schedule. 
    The strange thing to me is that the passwords listed as expired are still valid and haven't been changed.  I even ran an iisreset just to check and there were no issues.  When I look in CA the next password change area is blank for all accounts.
    My question is why do the accounts list a password expiration date if it's set to
    not automatically change passwords.  If you do change the password through AD you will see a new expiration date set for 90 days later.  I'm just wondering how much I should worry about the service accounts that are listed
    as having expired passwords even though the passwords aren't expired.  My sites and services are running but I'm just curious if this could potentially cause other errors.
    Thoughts?  Prayers?  Condolences?
    Jennifer Knight (MCITP, MCPD)

    I checked the My farm as well, you are correct. Even you did not select the automatic password change still it showed 90 days as expiry. 
    You don't need to worry about it, it will not hurt, one of the dev farm having account which  expired almost 10 months ago. :)
    you can double check with in central admin and you will see no expiration set over their.
    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

  • Batch Determination Expiration Date / Customer

    Hello Experts,
    Could you please give me a hand with his requirement?
    At this moment, there is a batch strategy determination in delivery according to expiration date, First Expiration Date, First Out, FEFO, and it is working fine.
    In addition to this configuration it is necesary that just for some customers the expiration date should not be under a year, otherwise they would not receive this products.
    Could you let me know if there is a standard way of achieving this?
    Thanks a lot for your help.

    Hello Lina
    Not fully clear about your requirement.
    Here are my suggestions:
    1) Bring in Customer into the access fields.
    Path: SPRO/IMG/Logistics - General/Logistics - General/Batch Management/Batch Determination and Batch Check/Access Sequences/Define Sales and Distribution Access Sequences
    If this does not work
    2)  Control Expiration date processing with custom code (User exit or BADI):
    Path: SPRO/IMG?Logistics - General/Logistics - General/Batch Management/Shelf Life Expiration Date (SLED)/Set Up Customer Exit to Calculate/Check the SLED or BAdI: Control of Shelf Life Expiration Date Processing
    Hope this helps.

  • Document Expiration Date Not Updating

    Hi,
    I’ve implemented a document retention policy based upon a custom date field. The custom date field is not for users to edit so it defaults to 1/1/1900 for new documents and I have written a console app that updates the custom date field to an appropriate
    date. The problem is that the expiration date, both for new and existing documents, doesn’t update. This is also the case if I update the document properties manually. In dev updating the custom date field, manually or via code,
     triggers an update in the expiration date but this isn’t happening in UAT. We’re using a content type hub in UAT although I can’t see how that makes a difference as the information management policies have been distributed correctly.
    Does anyone have an ideas as to why the expiration dates are not re-calculating?
    Thanks in advance
    Neil

    It is running and I've run it manually a number of times. But my understanding is that the job only updates new or amended expiration policies, it doesn't re-calculate for existing ones. That aside, the expiration date should update immediately when
    the field upon which is based is updated - at least that's the behaviour I've seen in development.

  • Password expire date back to 2011 from 2012  after assigned  a user profile

    Friends,
    I created a profile test as
    COMPOSITE_LIMIT UNLIMITED
    SESSIONS_PER_USER UNLIMITED
    CPU_PER_SESSION UNLIMITED
    CPU_PER_CALL UNLIMITED
    LOGICAL_READS_PER_SESSION UNLIMITED
    LOGICAL_READS_PER_CALL UNLIMITED
    IDLE_TIME 60
    CONNECT_TIME UNLIMITED
    PRIVATE_SGA UNLIMITED
    FAILED_LOGIN_ATTEMPTS 5
    PASSWORD_LIFE_TIME 120
    PASSWORD_REUSE_TIME           60
    PASSWORD_REUSE_MAX           30
    PASSWORD_VERIFY_FUNCTION NULL
    PASSWORD_LOCK_TIME 1
    PASSWORD_GRACE_TIME 7;
    the user default profile default PASSWORD_LIFE_TIME is 180 and password expired date is 1/7/2012. the test account was created in 7/11/2011.
    Now I assign test user to test profile successfully.
    However. expire date becomes 11/8/2011 1 from 1/7/2012 by select dba_users
    which wrong is in my profile or somewhere?
    As I think, the account password expired should be start after assigned new profile with PASSWORD_LIFE_TIME. but is seems expire date is start from original account created date.
    Thanks
    newdba
    Edited by: Oradb on May 24, 2012 1:56 PM

    I would think the expire time would be based on the last password change time which Oracle stores in the rdbms base table for user information (user$). Find a second user, alter the password, check the expire date, then assign the user to the new profile, re-check the expiration date. Post back. Behavior may vary between releases so include full Oracle version of test.
    HTH -- Mark D Powell --

  • Human task notification after due date/expiration date/...

    I would like to set a due date (or expiration date) to Human task, and set some notification before this time. Ok, it seemed very easy:
    - i set due date to 5 minutes in human task -> Deadlines
    - i set notifications in human task -> notification and in tab Advanced i set remind once 2 minutes before due date
    Nothing happens. Exactly same (nothing) happens when i do the same with expiration date.
    But what exactly is meaned under word "Reminder"?
    It's mail? (then where I have to set email adress? I tried to set a "to" field in human task -> notification -> tab Advanced -> notif. header attributes => nothing happened)
    It's worklist inbox message?
    Or what ist "reminder" and how it should remind me?
    Edited by: user1175491 on Dec 28, 2010 7:21 PM

    Hi,
    I don’t know if you’ve managed to resolve this issue yet and you mention you have emails working from BPEL, but I'm not sure if you've got any notifications working for the Human Task, if not then I have done some work with the human task notifications and although I’ve not tried to do what you’re doing, this is what I have learned.
    Firstly to receive any notifications you need to configure the Messaging Driver and Workflow Notification Properties…
    In Enterprise Manager expand [farm] -> SOA -> soa-infra
    Right click soa-infra and choose SOA Administration -> Workflow Notification Properties
    Underneath the page title (Workflow Notification Properties) is a note telling you to configure the Messaging Service Driver. Click the "Go to the Messaging Driver page" link.
    In the associated drivers section you will have a single entry for soa_server1 (or what ever it's called for you). In the right hand column there is a button for configuring the driver, click this.
    In the driver specific configuration, scroll down to OutgoingMailServer and enter the hostname or IP address of your mail server, then click Apply at the top of the screen.
    Now go back to the Workflow Notification Properties screen and choose “Email” from the notification Mode and enter some sensible email addresses in the Notification Service section. It’s useful to have real email addresses in here at the moment because any failures will be returned to this address.
    You now need to restart Weblogic for these changes to take affect.
    After the restart you can test the notifications by doing the following
    Back in Enterprise Manager expand [farm] -> SOA -> soa-infra
    Right click soa-infra and choose Service Engines -> Human Workflow
    Click on the Notification Management tab.
    You can click the "Sent Test Notification" button to make sure everything is working ok. This screen also allows you to monitor notifications for failures.
    Now that the notifications have been set up you can configure who gets notified on which events against your human task in JDeveloper.
    The email addresses for the users are retrieved from your identify provider for the relevant user, by default this is the internal LDAP directory. I’m not using this, so I’m not sure exactly how this will work. There are options in the worklist application for individual users, but I’m not using this either.
    Now that this is set up you can configure the human task within JDeveloper. On the notification tab you can decide who gets notified when. By default when a task is assigned to a user, the assignees are notified, you can play about with these settings to see what works best for you. Have a look at http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10224/bp_workflow.htm#BABBHDGF for more information.
    I’m not sure I’ve solved your problem, but I hope this at least helps.

  • Delivery Date should propose only working days (Excluding weekends and holidays

    Hello All
    I have one requirement here, where delivery dates should propose only working days and it should not allow to add weekends and holidays during the creation of sales order.
    I would like to know if there are any standard settings to be done in plant or shiping point?
    Kindly need all your input on this
    Thanks
    Naveen

    Hello All
    Same calendar has already been assigned in shipping point,plant and sales org and also in the calendar holidays been maintained, even though when we create a sales order it will accept weekends and holidays
    Thanks

  • Payment terms should calculate Payment due date based on working days

    Hi Experts,
    As we know that standard SAP calculates Payment due date= base line date + number of days maintained in payment terms. In this payment days are considered as calendar days and not the working days.
    Example: If base line date is Thursday, payment terms says 3 days then payment due date is calculated as Sunday ( which is not a working day as per the factory calendar I use). The requirement is that payment date should be calculated as following Tuesday considering Satuarday and Sunday are not working days as per the calendar.
    Can you please suggest how can we achieve this?
    Thanks,
    Ravi

    You can not acheive from config pooint of view but you can use BADI and get the solution
    use BAdI MRM_PAYMENT_TERMS to set terms of payment
    You can use this Business Add-In to change the following fields for the 
    terms of payment in the invoice document header:                        
    o  ZFBDT: Base date for due date calculation                            
    o  ZBD1T: Discount days 1                                               
    o  ZBD1P: Discount percentage 1                                         
    o  ZBD2T: Discount days 2                                               
    o  ZBD2P: Discount percentage 2                                         
    o  ZBD3T: Deadline for net condition                                    
    o  ZLSPR: Key for payment block

  • Need By Date Should be equal or after the effective start date- error in po_requisitions_interface_all

    Hi All,
    We have created a manual planned order for one buy item in ASCP workbench for some qty and released it.
    But, we are not able to get its requisition created in source.
    When we check the PO_Interface _Errors table, we found that it is errored out with error as --
    Need By Date Should be equal or after the effective start date .
    Can anyone please help me out to find the cause of this issue. Any help/pointer in this regard will be highly appreciated.
    Thanks,
    Avinash

    Hi Abhishek,
    We found the root cause of the issue.
    Its BPA was not having any Effective start date mentioned in its terms. So we put it as BPA creation date and ran the data collection and plan run.
    After that we were able to see its BPA release created without any error.
    Thanks,
    Avinash

  • HT4137 Good day! All of my data was deleted after i update my os to os5.1.1. from then on I didnt restore it again. Today, I accidentally restored my iphone and all of my recent photos were deleted. how can I retrieve it again? thanks!

    Good day! All of my data was deleted after i updated my os to os5.1.1. from then on I didnt restore it again. Today, I accidentally restored my iphone and all of my recent photos were deleted. how can I retrieve it again? thanks!

    If you have been regularly syncing/backing up your iPhone with iTunes or iCloud, you may try restoring it from the last backup.
    Read how to restore from a backup.
    http://support.apple.com/kb/ht1766
    Make sure to turn OFF automatic syncing in iTunes before connecting your iPhone.
    Preferences - devices - "check" prevent iPhone/iPod from automatic syncing

  • Why does my IPod shuffle stop after a few hours playing on shuffle when it should go for days?

    Why does my IPod stop playing after a few hours on shuffle when it should play for days?

    A few possibilities...  (Each numbered item is a separate thing to check or try.)
    (1) What does the shuffle's light do when you connect it to USB?
    (2) If the docking cable plug is not fully inserted, it may not have a good connection for charging.  Make sure the docking cable plug is fully inserted into the shuffle's headphones jack, as shown in this document
    iPod shuffle (4th generation): Not seen in iTunes
    (3) If there are other USB devices connected to your computer at the same time, try disconnecting other devices (including USB hub) so that the shuffle is the only device connected to a direct USB port, to see if that makes a difference (you can leave standard USB keyboard/mouse connected if used).
    (4) If you have a USB power adapter (such as from an iPhone, iPad, or other device), that plugs into the wall outlet, as a test, connect the shuffle's docking cable to the adapter and connect the shuffle.  Does it change from a power adapter?
    (5) Some newer Windows PCs (if you use Windows and not a Mac) may have a "feature" that shuts off full power to the USB port when a connected storage device is no longer mounted by the system.  An iPod is a storage device, and after syncing, iTunes unmounts the iPod's disk (if you are using automatic syncing).  If Windows shuts off full power to the USB port, the battery cannot charge.  To see if this is the problem, does the iPod appear in iTunes when it is connected, even though the battery is not charging?  If it does, select the iPod in iTunes so that you see its Summary screen.  There is an option (checkbox) there for Enable disk use.  If it's not already checked, check that box and Apply.  Enabling disk use keeps the iPod's disk mounted continuously, so Windows will keep the USB port at full power (and the battery will charge).  If the iPod now charges, there may be a way to disable this "energy saver" feature in Control Panels, so that you can turn OFF Enable disk use.  NOTE:  When Enable disk use is turned ON, you need to Eject the iPod in iTunes before physically disconnecting it.

Maybe you are looking for

  • How to Change the filed name in a standard SAP Transaction

    HI all, In the SAP Standard Display Vendor Transaction ie in XK03   there is an Screen with the Screen Number 220 In that Screen Number 220 there is a field by name Account memo I need to change that field name Accountmemo to DD Number. Please Sugges

  • Back order

    Dear sap gurus, According to my understanding: back order is a sale order which is not confirmed at a certain delivery date. kindly clarify the usage of back order. how to reserve a material for a particular sale order? kindly explain what is resched

  • Invalid Page fault in IMM32.dll on Japanese Win 98

    Hi First of all, let me say that I'm new to internationalization fundamentals. My Java application uses i18n.jar for internationalization support(primarily Japanese) and everything seems to be fine on all OSes(Win2k,NT,98,Solaris etc), except that in

  • Appleworks crash

    my appleworks continues to crash after I have trashed both preference files. Can I trash the 6.2.9 in osx and then install the appleworks which came with the ibook ( it was in os 9 ) and then update to 6.2.9 ?

  • Moving files to external hard drive

    Hi - I am getting a message that my start up disk is full. I don't know what to do. I thought I might move all of my videos onto my external hard drive but am not sure how to do that. Any help please ??