FousTexas Comptroller Webfile
Get your Texas Webfile records through an API
Read the Transaction History and Return Summary for each taxpayer account in Webfile with one API call each. Then have a workflow check every account each weekday morning and email you the reports and payments still Submitted.
Works with your own Texas Comptroller Webfile account. Fous is an independent product.
What you can build on Webfile
Get Webfile transaction history
Build thisReads View Transaction History for one taxpayer account and tax type: the electronic reports and payments sent through Webfile.
- Takes
- Taxpayer number, tax type, period (optional)
- Returns
- Transaction type, date and time, reference number, period, end date, amount, status
Read a period's return summary
Build thisReads View Return Summary for one taxpayer account and period: the return data, payments and balance due on file.
- Takes
- Taxpayer number, tax type, period
- Returns
- Period, reported amounts, payments, balance due
List taxpayer accounts and tax types
Build thisReads the My Taxpayer Accounts table on the Webfile dashboard: each taxpayer account on your profile and its tax types.
- Takes
- Nothing
- Returns
- Taxpayer number, tax types
Make a payment only
Build thisUses Make a Payment Only to pay or prepay the current period, or a period with an open liability, by electronic check dated for the day you choose.
- Takes
- Taxpayer number, tax type, period, amount, payment date
- Returns
- Reference number, period, amount, payment date, status
Automate Webfile with a workflow
A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.
Reports and payments not yet Processed, every account
Build this- Starts
- Every weekday at 8:00 Central Time
- Step 1
- List the taxpayer accounts and tax types on your Webfile profile.
- Step 2
- For each one, get the transaction history for the current period.
- Step 3
- Keep the transactions whose status is still Submitted.
- Step 4
- Email you the list, one section per taxpayer account.
Balance due after filing, by taxpayer account
Build this- Starts
- When your system calls the workflow's webhook with the period you just filed
- Step 1
- For each taxpayer account you name, read the return summary for that period.
- Step 2
- Keep the periods with a balance due above zero.
- Step 3
- Post taxpayer number, period, payments and balance due to your accounting system's webhook.
New Processed payments, handed to accounting
Build this- Starts
- Every day at 18:00 Central Time
- Step 1
- For each taxpayer account you name, get the transaction history for the current period.
- Step 2
- Keep the Payment transactions that are Processed now and were not on the last run.
- Step 3
- Post reference number, period, amount and date to your webhook.
You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.
Once built, one call from your code
Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get Webfile transaction history” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "security.app.cpa.state.tx.us/get_transaction_history",
"input": {
"taxpayer_number": "32000000000",
"tax_type": "Sales and Use",
"period": "2609"
}
}'
{
"status": "completed",
"data": {
"taxpayer_number": "32000000000",
"tax_type": "Sales and Use",
"transactions": [
{
"transaction_type": "Return",
"date_time": "2026-10-19T14:02:00-05:00",
"reference_number": "000000418273",
"period": "2609",
"end_date": "2026-09-30",
"amount": 4812.37,
"status": "Processed"
}
],
"count": 1
}
}
An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.
Webfile’s own options
The Comptroller has no web API for Webfile. Businesses reporting many outlets, leases, schedules or authorities can file sales and use, motor fuels, natural gas and crude oil, and IFTA reports by EDI (ANSI ASC X12 813) after registering and passing a test. Large payers send payments through TEXNET. Everything else is Webfile.
| Option | What it covers | What it takes |
|---|---|---|
| EDI (ANSI ASC X12 813) | Files sales and use (including Direct Pay), motor fuels, natural gas and crude oil, and IFTA reports, with payment by electronic funds transfer. | Registration, enrollment and a successful test file. The Comptroller's EDI software is free and needs Windows 11 or later, or you can buy third-party software. |
| TEXNET | Payments by ACH debit, required for $500,000 or more paid in one tax in the preceding state fiscal year. | Payments of $1,000,000 or less are scheduled by 10:00 a.m. CT on the due date. |
| Webfile by hand | Original and amended returns, Make a Payment Only, View Return Summary and View Transaction History, one taxpayer account and tax at a time. | An eSystems account, with access added once per tax or fee and taxpayer using its Webfile number. |
Read on November 12, 2026: Electronic Data Interchange (EDI), File and pay, Sales tax Webfile main menu.
Signing in to Webfile
eSystems signs you in with a user ID and a case-sensitive password of 10 to 25 characters, and keeps a security question for password resets. You then add each taxpayer's access with its 11-digit taxpayer number and Webfile number. With Fous you sign in once through the eSystems sign-in with your own account: the login is sealed with AES-256, and an expired session is signed back in.
Worth knowing
- A Webfile number per tax and taxpayer
- Access is added once for each tax or fee and taxpayer. RT numbers cover every tax except franchise, XT numbers cover franchise tax reports and FQ numbers the Franchise Tax Questionnaire.
- History shows Webfile activity only
- View Transaction History lists the reports and payments sent through Webfile. A TEXNET payment shows as status TEXNET without its amount, and Submitted becomes Processed once the account is updated.
- Periods are written as YYMM, YYQ or YYYY
- Monthly periods read YYMM, quarterly YYQ and annual YYYY, with End Date as the period's last day. Ask for the period in that form when you build a method.
- The deadline is 11:59 p.m. Central Time
- Webfile returns are due by 11:59 p.m. CT on the due date. You can post-date the electronic check. A late return may carry a $50 penalty.
More in Government: US state and local tax
- Ohio Business Gateway
- MyFTB
- CDTFA Online Services
- Colorado Revenue Online
- Florida DOR eServices File and Pay
- Georgia Tax Center
- INTIME
- LaTAP
- Maryland Tax Connect
- MassTaxConnect
- Michigan Treasury Online
- Minnesota e-Services
- My DOR
- myconneCT
- MyDORWAY
- myPATH
- MyTax Illinois
- MyTaxes Kentucky
- NCDOR eBusiness Center
- New Jersey Tax Portal
- NY Business Online Services
- OH|TAX eServices
- TNTAP
- Virginia Tax Business Online Services
- Wisconsin My Tax Account
Other industries: SIDES E-Response, Uline, SAP Fieldglass, Henry Schein online ordering, Navigate, Legal Tracker.
Frequently asked questions
No. The Comptroller offers EDI (ANSI ASC X12 813) for sales and use, motor fuels, natural gas and crude oil, and IFTA reports, after registration and a test file, and TEXNET for ACH payments. Return summaries and transaction history are read in Webfile itself.
Open View Transaction History for the tax. Each transaction has a Reference Number that confirms it was transmitted, and a Status of Submitted (received) or Processed (completed and updated to the account).
Yes. You add access for each taxpayer and tax with its taxpayer number and Webfile number, and the My Taxpayer Accounts table lists them. A taxpayer account can also be assigned to several Webfile user profiles.
Filers who paid $50,000 or more in listed taxes such as sales and use must file electronically, and those who paid $10,000 or more must pay electronically. Missing either requirement adds a 5% penalty.
No. Fous is an independent product. You use it with your own eSystems account, and a method reads and does only what that account can.
Put Texas Comptroller Webfile behind an API call
Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Read nextTNTAPVirginia Tax Business Online ServicesWisconsin My Tax AccountSIDES E-ResponseHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Texas Comptroller Webfile (Texas Comptroller of Public Accounts). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.