Bill Commons

ME LD 1056

dead

An Act To Clarify The Tax Treatment Of Prepaid Wireless Telecommunications Service In Maine

Maine · 132 · lower

Quick answers

Did ME LD 1056 pass?

No. ME LD 1056 did not pass — it was defeated or died in the legislative process (2026-04-29). Latest recorded action (2026-04-29): Died in Possession of the Senate when the Legislature adjourned Sine Die and was PLACED IN THE LEGISLATIVE FILES. (DEAD)

What is ME LD 1056 about?

ME LD 1056 is a bill in the 132 titled “An Act To Clarify The Tax Treatment Of Prepaid Wireless Telecommunications Service In Maine”.

Introduced
Latest action
2026-04-29 — Died in Possession of the Senate when the Legislature adjourned Sine Die and was PLACED IN THE LEGISLATIVE FILES. (DEAD)
Bill type
bill
Last updated

Subjects

Sponsors

Not provided by source.

Committees

Not provided by source.

Action timeline

  1. 2025-03-12

    Received by the Clerk of the House on March 12, 2025.

    receipt

  2. 2025-03-12

    The Bill was REFERRED to the Committee on ENERGY, UTILITIES AND TECHNOLOGY pursuant to Joint Rule 308.2 and ordered printed pursuant to Joint Rule 401.

    referral-committee

  3. 2025-03-21

    Carried over, in the same posture, to the next special or regular session of the 132nd Legislature, pursuant to Joint Order SP 519.

  4. 2025-03-25

    Report of the Chair-Pursuant to Joint Rule 308.2

  5. 2025-03-25

    Representative SACHS from the Committee on ENERGY, UTILITIES AND TECHNOLOGY Reports a recommendation for a CHANGE OF COMMITEE.

  6. 2025-03-25

    Report was READ and ACCEPTED.

  7. 2025-03-25

    On motion of Representative SACHS, the Bill was REFERRED to the Committee on TAXATION.

    referral-committee

  8. 2025-03-25

    Sent for concurrence.

  9. 2025-03-25

    Report READ and ACCEPTED

  10. 2025-03-25

    The Bill was REFERRED to the Committee on TAXATION in concurrence

    referral-committee

  11. 2025-06-16

    CONSENT CALENDAR - FIRST DAY

  12. 2025-06-16

    Under suspension of the rules CONSENT CALENDAR - SECOND DAY.

  13. 2025-06-16

    The Bill was PASSED TO BE ENGROSSED as Amended by Committee Amendment "A" (H-747).

    reading-3

  14. 2025-06-16

    Sent for concurrence. ORDERED SENT FORTHWITH.

  15. 2025-06-16

    Report READ and ACCEPTED, in concurrence.

  16. 2025-06-16

    READ ONCE.

    reading-1

  17. 2025-06-16

    Committee Amendment "A" (H-747) READ and ADOPTED, in concurrence.

    committee-passage-favorable,passage

  18. 2025-06-16

    Under suspension of the Rules, READ A SECOND TIME and PASSED TO BE ENGROSSED AS AMENDED BY Committee Amendment "A" (H-747), in concurrence.

    reading-2,reading-3

  19. 2025-06-16

    Ordered sent down forthwith.

  20. 2025-06-17

    PASSED TO BE ENACTED.

    passage

  21. 2025-06-17

    Sent for concurrence. ORDERED SENT FORTHWITH.

  22. 2025-06-17

    On motion by Senator ROTUNDO of Androscoggin PLACED ON THE SPECIAL APPROPRIATIONS TABLE pending ENACTMENT in concurrence

  23. 2025-06-25

    CARRIED OVER, in the same posture, to any special or regular session of the 132nd Legislature, pursuant to Joint Order SP 800.

  24. 2026-04-29

    Died in Possession of the Senate when the Legislature adjourned Sine Die and was PLACED IN THE LEGISLATIVE FILES. (DEAD)

    failure

  25. 2025-03-21

    Refer Approved by Chairs/Leads - REFER TO OTHER

  26. 2025-03-21

    Reported Out - REFER TO OTHER

  27. 2025-04-22

    Work Session Held

  28. 2025-04-22

    Voted - OTP-AM

  29. 2025-06-16

    Reported Out - OTP-AM

Versions

Documents

Votes

Not provided by source.

Related bills

No related bills recorded for this bill.

Official source

Attribution

Data from openstates_bulk_csv, retrieved 2026-07-24T05:23:53.435176Z

Inspect retained evidence for changes recorded after evidence tracking began:

Use this data

Every field on this page is available from the free public API — no key or licence required. Fetch this bill as JSON: GET /api/v1/bills?jurisdiction=ME&identifier=LD 1056. See the API docs or the MCP server for AI assistants.

Known limitations

  • Sponsor party and chamber affiliation are not yet captured by this API.
  • Committee referrals are not yet captured.

See the methodology page for data sources and limitations.