Here is the text we could read:
JS Form ALEA-HTSF
Rev Jul.9.2018
Monthly Remittance Form for the
HIGHWAY TRAFFIC SAFETY FUND
ACT 2014-222 and Act 2018-517
For questions concerning the form contact Sherita Pace at 334-517-2944
OR
via email to Sherita.pace@alea.gov
onthly report of court costs collected pursuant to ACT 2014/222, effective July 1, 2014, and Act 2018-
517, effective July 1, 2018, for the month of:
, from the Municipal Court of
Month
,
Year
$
$
$
Sub-Total
Partial
Payments
Total
Number
Of
Cases
Disbursement
On Each Case
(for the first four
(4) months only-
on a per month
basis)
$15.00
Number
of Cases
Disbursement
On Each Case
$60.00
Sub-total
Partial
Payments
Total
Signature of Remitter and Title
Print Name of Remitter
Telephone Number
Alabama Law Enforcement Agency (ALEA)
Attn: Sherita Pace
PO Box 304115
Montgomery, AL 36130-4115
DUI/Interlock (for defendants
who own a vehicle and have
the interlock device installed)
Act 2014-222 cases prior to
July 1, 2018
DUI/Interlock (for convicted
defendants who own a vehicle
and have the interlock device
installed)
Act 2018-517 cases on or
after July 1, 2018
RAND TOTAL
ate
ourt ORI No.
heck No.
he costs SHALL BE REMITTED by the 10th of each month.
ake check payable to the HIGHWAY TRAFFIC SAFETY FUND.
ail the original form along with remittance check to:
U
M
G
D
C
C
T
M
M
Highway Traffic Safety Fund Act 2014-222 and Act 2018-517
This info page is part of the LIT Lab's Form Explorer project. It is not associated with the Alabama state courts.
To learn more about the project, check out our about page.
Downloads: You can download both the original form (last checked 2023-03)
and the machine-processed form with normalized data fields.
About This Form:
- Sourced from eforms.alacourt.gov (2023-03)
- Page(s): 2
- Fields(s): 9
- Average fields per page: 4
- Reading Level: Grade 10
- LIST Grouping(s):
Unknown
Use our Rate My PDF tool to learn more.
Go beyond the above insights and learn more about this or any pdf form at
RateMyPDF.com, includes: counts of difficult words used,
passive voice decetion, and suggestions for how to make the form more usable.
Identified Data Fields:
We have done our best to automaticly identify and name form fields according to our naming conventions.
When possible, we've used names tied to our question library. See e.g., user1_name.
If we think we've found a match to a question in our library, it is highlighted in green. Novel names are auto generated. So, you will probably need to edit some of them if you're trying to stick to the convention.
Here are the fields we could identify.
report_costs_pursuant was monthly_report_of_court_costs_collected_pursuant_to_act_2014_222__effective_july_1__2014__and_act_2018 (0.48 conf)year was year (0.28 conf)month was month (0.28 conf)signature_remitter_title was signature_of_remitter_and_title (0.34 conf)signature_date was date (1.00 conf)print_name_remitter was print_name_of_remitter (0.40 conf)court_ori was court_ori_no (0.49 conf)telephone_number was telephone_number (0.42 conf)check was check_no (0.40 conf)
We've done our best to group similar variables togther to avoid overwhelming the user.
Suggested Screen 0:
Suggested Screen 1:
report_costs_pursuantsignature_remitter_titlesignature_dateprint_name_remittercourt_oritelephone_number
Suggested Screen 2:
Create an Interactive Version of this Form:
The Weaver creates a draft guided interview from a template form, like the one provided here. You can use the link below to open this form in the Weaver.
To learn more, read "Weaving" your form into a draft interview.
Launch Form in Weaver